https://threatpost.com/another-linux...access/137800/
Would be awesome if that works
I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9
S8ntsHaz3 said:
I played around a little and this happened...
https://photos.app.goo.gl/TiEXrdKmWydRM8RZ9
Click to expand...
Click to collapse
Unlock critical is allowed and already known thing but this is for flashing bootloader and stuff. It doesn't help us at all for now.
There are already many rooted tmobile g7 sold in China.
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
anyone tried it yet?
kasuma_asuma said:
anyone tried it yet?
Click to expand...
Click to collapse
So it's a fake post for one (actually not exactly fake I would say more clickbait then anything) two I believe the T-Mobile version is the G710TM, three we have a gimped fastboot as in it doesn't work at all. And four I think our only option is something to do with LAF
---------- Post added at 11:22 AM ---------- Previous post was at 11:21 AM ----------
curster said:
I found a possible root it looks like it will work with any lg g710 Oreo. Is this not the case?
https://www.androidinfotech.com/2018/06/root-lg-g7-thinq-lmg710-oreo.html
Click to expand...
Click to collapse
No it's not the case see my previous answer
We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.
alecthenice said:
We should be able to get around this gimped fastboot by incorperating that boot.img from the EM varient into an "update" once the phone is cross flashed. To 710EM it will have "adb update" command (it will also think the update is for itself since the firmware matches what were flashing we can put this into a flashable.zip (im like 75% sure this is how its done). Then use the command "adb update boot /path to patch boot/" alternatively could we incorperate our patched boot.img into a kdz and flash it with a patched LGup? Once the phone is rooted with magisk we could use the twrp app to flash twrp and fastboot commands wont be extremely relevant
The problem is, how to remove or get around the correct oem unlock allowed verification system. Unpacking a .img and editing is not a problem, i am just not exactly sure what to edit.
Click to expand...
Click to collapse
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
So for dm-verify I know how to manually get around that and the patch thats floating around via flashable.zip. What do we need to extract from the .up or .kdz? Im pretty sure there is a full kdz dump for the 710EM in a thread I read through just last night? I really believe the only obstacle we have is making the bootloader unlock through a command line independent of the official unlock code. This should be able to be acheived by editing that in a way to where it doesnt check much like dm-verity. Then you can flash your (patched by deletion) boot.img run fastboot oem unlock ( btw did you know that "fastboot oem flashing unlock critical works) **could run that then flash an unlock.bin, then fastboot oem unlock unlock.bin** I am working with a 710pm varient. And am speaking from experience rooting the v30 ls version currently using G7 as daily driver
This leaves me thinking that we have lots of wiggle room here (also leaves me thinking how weird LG is for having a lot of variation within G7)
LameMonster82 said:
I'm will definitely get root on every other device but there's two things that stop us.
1) it's impossible to extract anything from a kdz and a .up file (LGs way of updating)
2) dm-verify (but it's possible to get around)
Click to expand...
Click to collapse
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
View attachment 4667707
GROOVYJOSHCLARK said:
I use LG Firmware Extract to get the DLL's out, the problem is theres no firmware yet for the LG G7 Sprint version:
Click to expand...
Click to collapse
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.
LameMonster82 said:
Amazingly this week I was able to extract everything from any kdz file. The problem is that repacking requires certificate and we don't have it.
Click to expand...
Click to collapse
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.
GROOVYJOSHCLARK said:
Yes but we will figure it out eventually. I'm on Sprint myself and actively trying to figure out the LG cross flashing issue.
Click to expand...
Click to collapse
So, do you want to cross flash or just the Sprint firmware
LameMonster82 said:
So, do you want to cross flash or just the Sprint firmware
Click to expand...
Click to collapse
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian
runningnak3d said:
There is no cross flashing on the G7 (or V35 or V40) unless you want a brick. LG got smart after the V30 WTF exploit and now uses a different RSA cert for every model.
Don't take my word for it, please feel free to try -- make sure you have insurance
-- Brian
Click to expand...
Click to collapse
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.
GROOVYJOSHCLARK said:
Yes but we will figure it out eventually so we can flash the EM firmware and unlock the bootloader then root and install TWRP then AOSP. I am waiting on my octoplus box to arrive then I'll be testing cross flashing for others to sort out what's needed.
Click to expand...
Click to collapse
Awesome! But octoplus will not allow you to cross flashing, right?
any news on this ? would love to change my T-mobile software. and get the fingerprint to work for that matter
Related
I am currently working on a root method for the SM-A205U and desperately need the stock default.prop file. If anyone wants to provide one it would greatly be appreciated.
A205U boost mobile
ATGkompressor said:
I am currently working on a root method for the SM-A205U and desperately need the stock default.prop file. If anyone wants to provide one it would greatly be appreciated.
Click to expand...
Click to collapse
What build do you need ?
Ok did you find the file you were looking for ?
ATGkompressor said:
I am currently working on a root method for the SM-A205U and desperately need the stock default.prop file. If anyone wants to provide one it would greatly be appreciated.
Click to expand...
Click to collapse
This sounds interesting
physwizz said:
This sounds interesting
Click to expand...
Click to collapse
So, using Linux, Superr's kitchen to unpack (free as well) and Frija for latest firmware.... in under an hour you can have what you need. Am i missing something?
mindlery said:
So, using Linux, Superr's kitchen to unpack (free as well) and Frija for latest firmware.... in under an hour you can have what you need. Am i missing something?
Click to expand...
Click to collapse
@ATGkompressor
A205U Boost mobile
physwizz said:
@ATGkompressor
Click to expand...
Click to collapse
I also have the file he is looking for but I don't think that's going to help . Until someone cracks the Bootloader I think this phone will remain unrootable till that is achieved .
Do you need the prop file still??
A205U Boost mobile
Ok guess you have the file you were looking for already . Are you making any progress on a root solution for the A205U or is it a lost cause ?
mindlery said:
So, using Linux, Superr's kitchen to unpack (free as well) and Frija for latest firmware.... in under an hour you can have what you need. Am i missing something?
Click to expand...
Click to collapse
Being that im restricted on time and what not... You (or anyone) with those tools could possibly unpack the system image and set ro.oem_unlock_supported=1 in default.prop, repack and flash through Odin. It would have to be flashed as a .tar because i have yet to figure out the level of lz4 compression they are using on the stock firmware. If we could meet those criteria we could theoretically get the bootloader unlocked.
One more thing, if not careful vbmeta will check against the trustzone for the keys they signed the firmware with. I have the offset address that the key resides at within the AP file. Each carrier has their own 8 digit key, so long as they match vbmeta in both AP & BL. But watch out for the fota.zip because its encrypted and any changes within are prohibited without the password to decrypt.
If someone is willing to work with me... I think we can unlock this bootloader!
Ok i'll grab it for you. I don't have the same device so i'll leave the edits to you. Gimme a few...
Probably went a bit overboard here. I got 5 of them plus recovery, boot and vbmeta. If you need more let me know.
https://drive.google.com/file/d/1MvMDowrrgK2tbBobTigHB5H4odJPOzaa/view?usp=sharing
As i stated in the metro thread uou will need to find combination firmware and run some tests with it to see if it has oem unlock or high lvl debugging to be able to bypass the bootloader lock and apply root
I also states if slmeone can find me bootloader 5 android 10 combination firmware i would see what i could do to get bootloader unlock and root
allenjthomsen said:
As i stated in the metro thread uou will need to find combination firmware and run some tests with it to see if it has oem unlock or high lvl debugging to be able to bypass the bootloader lock and apply root
I also states if slmeone can find me bootloader 5 android 10 combination firmware i would see what i could do to get bootloader unlock and root
Click to expand...
Click to collapse
I found A205u bootloader 5 android 10 https://drive.google.com/drive/folders/1dSmtNSIKSZDHvMgjrUSfCHdXN16aMKiQ?usp=sharingare.
Here's what this is gonna take to get to a point to unlock:
Going into all the firmware files AP, CP, etc. And using a hex editor to modify the signature key from a carrier that has oem unlock support set to true. As long as the key in each image flashed matches the previous one, a flash error won't occur. The trick is that FOTA has this same security measure but it's encrypted and I'm not certain that by changing that key, ecryption gets broken...? Idk
Even just replacing the system image from a oem supported carrier with a key change should work. But the full job would get done by modifying all the binaries.
I do have the offset address of the signature keys but it's an older firmware package. I will begin working on it if i have support from at least one other person to independently confirm.
Also: QPST is a viable option but don't hold me to that one.
ATGkompressor said:
Here's what this is gonna take to get to a point to unlock:
Going into all the firmware files AP, CP, etc. And using a hex editor to modify the signature key from a carrier that has oem unlock support set to true. As long as the key in each image flashed matches the previous one, a flash error won't occur. The trick is that FOTA has this same security measure but it's encrypted and I'm not certain that by changing that key, ecryption gets broken...? Idk
Even just replacing the system image from a oem supported carrier with a key change should work. But the full job would get done by modifying all the binaries.
I do have the offset address of the signature keys but it's an older firmware package. I will begin working on it if i have support from at least one other person to independently confirm.
Also: QPST is a viable option but don't hold me to that one.
Click to expand...
Click to collapse
Sounds like fun
ATGkompressor said:
I will begin working on it if i have support from at least one other person to independently confirm.
? I would appreciate the opportunity to help anyway I can. I have the 205u metro and windows 7 desktop. I'm not a pro but I'm not a noob either. Let's make this phone useable.
Click to expand...
Click to collapse
ddougg said:
ATGkompressor said:
I will begin working on it if i have support from at least one other person to independently confirm.
? I would appreciate the opportunity to help anyway I can. I have the 205u metro and windows 7 desktop. I'm not a pro but I'm not a noob either. Let's make this phone useable.
Click to expand...
Click to collapse
Cool, if u have a link to the latest firmware we can start there.
Click to expand...
Click to collapse
peter couniaz said:
What build do you need ?
Ok did you find the file you were looking for ?
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/galaxy-a20/how-to/a205-bootloader-unlock-twrp-root-t4189197
a205 bootloader offset Boost variant only!- FCE2C4
there yall go....this address will lead you to what i theorize can be done to root this device.this makes it possible to use another firmware package possibly by changing what is at that address.
So basically, I require one file from the community : ramdisk_recovery.img. I would like it to be 100% not tempered, original, extracted from the latest .185 rom for C432 region for model CLT-L29. I have discovered a new method of rooting by using the sdcard method, however I have no way of getting the update.app from anywhere else. What I will do is replace the ramdisk_recovery.img within update.app with the patched version (patching the file using magisk manager) and flash it. This MIGHT brick your phone, however I am not certain. I hope I can get this file ASAP, as I might just found a perfect way to get out of Huawei's restrictions.
If you can write up a tutorial on getting that file from a phone (unlocked bootloader but unrooted), I can try to get it for you. (Having said that my device was a China region device which I rebranded to 432 when I received it, in case that makes a difference)
jfbaudio said:
If you can write up a tutorial on getting that file from a phone (unlocked bootloader but unrooted), I can try to get it for you. (Having said that my device was a China region device which I rebranded to 432 when I received it, in case that makes a difference)
Click to expand...
Click to collapse
Afaik you can try adb dump ramdisk_recovery.img or by extracting the img from an update.app file. If you had root, you could try to redownload the update using HWProxy method, cancel the update and go to root/data/update and copy it's contents to a PC. i will keep looking for a method so feel free to try any method
jfbaudio said:
If you can write up a tutorial on getting that file from a phone (unlocked bootloader but unrooted), I can try to get it for you. (Having said that my device was a China region device which I rebranded to 432 when I received it, in case that makes a difference)
Click to expand...
Click to collapse
Hello. Any luck so far?
AnotyClaws said:
Hello. Any luck so far?
Click to expand...
Click to collapse
I don't have root (work phone and remote management prevent that). What's the exact adb command? I get "unknown command" using adb dump ramdisk_recovery.img. The phone does show up for adb devices.
jfbaudio said:
I don't have root (work phone and remote management prevent that). What's the exact adb command? I get "unknown command" using adb dump ramdisk_recovery.img. The phone does show up for adb devices.
Click to expand...
Click to collapse
Hmmm. I will keep you updated. I found a method but the problem is, you need to downgrade to android 9, which I suppose you can't since it's your work phone.
AnotyClaws said:
Hmmm. I will keep you updated. I found a method but the problem is, you need to downgrade to android 9, which I suppose you can't since it's your work phone.
Click to expand...
Click to collapse
ah yes that's right... I can't downgrade. If you're still working on this when I replace this phone for work this fall, I'll revisit this
[Recovery][BKL][EMUI 8.x][Unofficial]TWRP 3.2.1-0 working recovery from View 10
Backup your stock recovery per this post. If you are too lazy, I can upload my backup from .104 build (C432) to Mega. Download twrp_bkl_0.7.img from this post and place it in same directory with your ADB. After successful backup as precaution...
forum.xda-developers.com
This is the easy way to it.
I've been trying to flash my G900 (AT&T version), So far I've tried LGUP, LGUP Dev and The official LG flashing tool, My main goal here is to at least remove AT&T from the device as it's throwing me errors when I try to update from Android 10 to Android 11. Any suggestions? I've searched around and there doesn't seem to be much about thus specific device.
Divine_42O said:
I've been trying to flash my G900 (AT&T version), So far I've tried LGUP, LGUP Dev and The official LG flashing tool, My main goal here is to at least remove AT&T from the device as it's throwing me errors when I try to update from Android 10 to Android 11. Any suggestions? I've searched around and there doesn't seem to be much about thus specific device.
Click to expand...
Click to collapse
What are you trying to flash exactly, and how are you trying to flash it?
iBowToAndroid said:
What are you trying to flash exactly, and how are you trying to flash it?
Click to expand...
Click to collapse
Well basically I'm trying to crossflash the device with a clean firmware/OS
I have confirmed numerous times it should work fine, as the devices are identical; only distinction is firmware.
I have used all the LG flashing tools I can find, They all see, connect and flash, only to fail with an error, that's either blank or changes every time.
Divine_42O said:
Well basically I'm trying to crossflash the device with a clean firmware/OS
I have confirmed numerous times it should work fine, as the devices are identical; only distinction is firmware.
I have used all the LG flashing tools I can find, They all see, connect and flash, only to fail with an error, that's either blank or changes every time.
Click to expand...
Click to collapse
So which firmware are you trying to flash, exactly?
I have tried anyway with LGUP. A bug for protection does not allow anything. I want to upgrade to 11. Nothing at all. The dll I extract it from the Firmware and neither. Firmware from Lg-firmwares.com for this AT&T Velvet 5G.
dude you'll never install anything LG directly gives you since you can't unlock the bootloader
swaguduzo said:
dude you'll never install anything LG directly gives you since you can't unlock the bootloader
Click to expand...
Click to collapse
Uhhhh, the bootloader doesn't need to be unlocked in order to flash stock firmware. That applies to almost every model from every manufacturer
swaguduzo said:
dude you'll never install anything LG directly gives you since you can't unlock the bootloader
Click to expand...
Click to collapse
I understand what they say about bootloader unlocking. It is true the majority, the vast majority do not need it. But this AT&T device has made my life impossible to do so. I also can't find a way to unlock bootloader.
Please, someone who can give me a good tip, of what I have to do. On the other hand, can someone explain to me how to extract the KDZ from my own phone. I'm not talking about downloading a KDZ but about making a backup of the device itself. As you know, the bootloader is not unlocked and I would need a tool that allows it without having to root it.
I attempted to convert my t-mobile oneplus 9 to international firmware by first flashing the Indian firmware.
I mistakenly downloaded the oneplus 9 PRO Indian msm.
I didn't realize this as the file has a very similar name. Lemonade_22.I.07_210412 vs Lemonadep_22_I.07_210412
I've tried everything since then, with no success. I tried to flash the correct oneplus 9 indian msm but it says incorrect device.
So I'm stuck with the oneplus 9 pro Indian firmware and can't get back to indian oneplus 9 firmware....
I have been developing and flashing android devices since the early days of Cyanogenmod... dozens of devices. And guess what? I did EXACTLY the same thing as you.
The link I downloaded from said it was Oneplus 9 firmware, and given the filenames being virtually identical, I never noticed it was the Oneplus 9 PRO firmware.
So don't feel too bad. Even experienced people can make mistakes when trying to flash phones!
I am working on a solution, but so far no luck because:
1. Msm Tool will not flash the Oneplus 9 firmware as it thinks it is the incorrect device (why did it let us flash the incorrect device firmware before???)
2. The bootloader is re-locked and the OEM Unlocking feature is greyed out in Developer options, therefore fastboot can't be used to re-flash the correct firmware.
3. The System Update "local upgrade" feature does not find ZIP files in the root folder and will not allow us to browse to the correct file.
So for now, we are stuck. I think solving #3 will be the solution. If we can make the "local upgrade" work, we should be able to flash the stock firmware ZIP.
@Derek6091 @mightysween did you fix it yet? I had my device screw up so bad today that the only MSM I could use on my global unit was the Indian 9 Pro firmware and I have gotten my device mostly working.
You can see my drama with it and how I finally got it working here.
[SOLVED] Can anyone help me unbrick? I have tried lite firehose, MSM for global, MSM for Indian 9 Pro, none work
I modded the global MSM so that it will flash to this frankenphone. https://forum.xda-developers.com/t/all-of-those-stuck-on-indian-firmware-rejoice-i-modded-the-global-msm.4442473/ EDIT: For anyone else trying this and getting unsupported...
forum.xda-developers.com
I can get it working with 11.2.10.10 but not OOS 12, in OOS 12 the touchscreen doesn't work and it shows dual SIM icons so it's still doing something that makes it think it's a foreign variant. I ended up just going back to StagOS where I was before everything got mucked up.
Unfortunately the MSMs still see it as an Indian variant so I can only flash the Indian OP9P firmware to it, tried all the other MSMs and none work. I have been reading threads here and people claim they got it back to global but I tried all of the suggestions and none of them restored the device enough to where the global MSM Tool didn't see it as an Indian model and refuse to flash so I think we are stuck with this frankendevice.
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Nice glad you figured it out.
go17lyonjon said:
Nice glad you figured it out.
Click to expand...
Click to collapse
haha yeah I was a dog with a bone, wasn't gonna drop it lol.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Derek6091 said:
@EtherealRemnant Yes I had to do oem unlock while on the Indian firmware. If your phone has the oem unlock greyed out, there's a guide on how to fix that with a simple command line.
Then I unlocked bootloader, flashed lineage recovery then a custom ROM. Haven't tried to get back to stock rom, and I don't think we can.... But I love this rom I'm currently on which is stagos.
Feel free to message me for any questions you may have!
[ROM][OOS Cam][Android 12.1]StagOS 12.1[lemonade][FINAL][08/09/2022]
Hey another day another rom, that's what you might be thinking. but we at stag aim towards elegance. We are learners just like everyone out there, This is small project we have started which helps us learn every single day. Why Stag, you might...
forum.xda-developers.com
Click to expand...
Click to collapse
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
mightysween said:
I can't find a working command line fix for the greyed out OEM unlock... which one did you use?
Click to expand...
Click to collapse
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
mightysween said:
Excellent. How did you do it? I would like to try with the T-Mobile MSM
Click to expand...
Click to collapse
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Derek6091 said:
Go to your home screen on your phone and connect to computer with usb debugging and run this command in cmd,
adb shell pm disable-user com.qualcomm.qti.uim
Then go to developer options and oem unlock should be able to toggle.
Click to expand...
Click to collapse
Perfect... thanks.
EtherealRemnant said:
You have to use the Oppo Decrypter tools. Decrypt the OPS file and open settings.xml. At the bottom of it there's a Target area. I just edited that to IN instead of O2 and re-packed it.
Click to expand...
Click to collapse
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Manually flashing partitions in Fastboot does work, FYI. So it is possible to go back to stock that way once the bootoader is re-unlocked.
I wonder where the "target" data is stored on the actual device. If it is simply a numerical/text value in an accessible partition, seems like it would be pretty easy to make a TWRP flashable that can change it.
mightysween said:
Nice...
I tried it with the T-Mobile MSM but it still failed on "unsupported target". Did you only change the text value for O2 to IN, or did you need to change the numerical Target ID as well?
I am pretty content leaving this phone on StagOS anyway, but would be nice to figure out a way to return to T-Mobile stock after recovering from a brick.
Click to expand...
Click to collapse
Strange that it didn't work for you. That was indeed all I changed. Did you change it to what the unsupported target message said your device was? I was comparing the settings between India and global and besides the change of target ID, the target number on India was 3 instead of 1. No idea if that makes a difference though because I didn't try it.
You made sure to re-encrypt and replace the OPS, right?
Also yeah you can flash with fastboot, it doesn't fix that flag though and when I tried to go back to OOS 12 with the messed up flag it thought my device was a dual SIM device so there was no signal and the touchscreen didn't work. Happened twice. With the modified MSM I went back to global and am running OOS 12 right now.
EtherealRemnant said:
@Derek6091 I have modded the global firmware so that it will flash on a device recognized as the Indian variant. If you would like to give it a shot (I already tested it on my own device and am happy to say, it worked perfectly and my device is back on global firmware), here's the link
LE2115_11.2.4.4_India_fix.zip
Compressed (zipped) Folder
1drv.ms
Click to expand...
Click to collapse
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
taintsx said:
Do you still have this file ? I flashed the OnePlus 9 pro indian firmware in msm since it's the only thing that worked and I want to go back to global
Click to expand...
Click to collapse
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
EtherealRemnant said:
All you have to do to go back to global is download the full OTA for your device and flash it with the system updater.
Click to expand...
Click to collapse
Yea I tried that and had touchscreen not responding issues
taintsx said:
Yea I tried that and had touchscreen not responding issues
Click to expand...
Click to collapse
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
EtherealRemnant said:
Then use the downgrade package. It will wipe your phone again but I will get you back to full OOS11 firmware and that issue won't happen.
Click to expand...
Click to collapse
Yea i tried that with
[OnePlus 9][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
downgrade indian version 11.2.5.5 , unfortunately it just tells me it cannot read the file when i attempt to sideload
You can manually update to latest Android 11 (April patch)
Bootloader unlock may be required.
Download the ROM https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml.zip
Unpack the zip and enter bootloader (turn the phone off and press and hold volume down and power it on)
Flash everything EXCEPT radio.img. Failure to do it will result in NO SIM error!
Everything is better with this version ROM. Do not update to Android at this time because it's a mess.
I manually upgraded to A12 on my XT2141-2 as soon as I was able. The only issue I've had was SIM not detected with 1 specific Lsposed module enabled, disabling that one module resolved that though. And ofc not having Gravity Box yet kinda sucks but I've had a blast with new theming possibility with A12 thanks to Repainted and Project Themed apps.
Could you elaborate on any issues you experienced yourself?
Sorry to have to ask this, but what happens if I somehow screw things up? unless I'm mistaken there's no TWRP for this phone (yet) to help with recovery...and how might I go about backing things up before I try to flash a new ROM build on my device? (Still new to things)
edit: addition: probably a stupid question, but I've only ever flashed the `boot.img` file, am I supposed to "fastboot flash" every file over?
ruq said:
Sorry to have to ask this, but what happens if I somehow screw things up? unless I'm mistaken there's no TWRP for this phone (yet) to help with recovery...and how might I go about backing things up before I try to flash a new ROM build on my device? (Still new to things)
edit: addition: probably a stupid question, but I've only ever flashed the `boot.img` file, am I supposed to "fastboot flash" every file over?
Click to expand...
Click to collapse
will this unlock verizon edge 5g
jakethesnake24 said:
will this unlock verizon edge 5g
Click to expand...
Click to collapse
No. Everything I've read states that Verizon Phones are hard-locked-down and cannot be rooted, unless there exists or is discovered at some point in the future an exploit to crack such phones. Sorry if that means you're out of luck.
I believe the preferred way of having a rootable phone is to always outright purchase it independently of any carrier. I purchased mine unlocked at a Best Buy.
In case anyone is reading this and getting a 404 on the OG post link for the ROM I found it under this updated link.