Hello, could someone PLEASE provide me with a stock or source for stock firmware for the AT&T LG G8 Thinq (LMG820UM). I've looked everywhere and can only find the U.S. Cellular, Verizon, Sprint, and T-mobile versions (everything except what I exactly need )!!!! The carrier's already unlocked. I wanna unlock the bootloader, flash custom ROMs like LineageOS (and TWRP) and root it and be able to revert back and LOCK the bootloader safely. I have LGup and other tools (though I don't know exactly what everything's for, such as firehose and other bootthings). I don't think cross flashing works and I don't want to do it anyway. Thanx!
PHANX0M said:
Hello, could someone PLEASE provide me with a stock or source for stock firmware for the AT&T LG G8 Thinq (LMG820UM). I've looked everywhere and can only find the U.S. Cellular, Verizon, Sprint, and T-mobile versions (everything except what I exactly need )!!!! The carrier's already unlocked. I wanna unlock the bootloader, flash custom ROMs like LineageOS (and TWRP) and root it and be able to revert back and LOCK the bootloader safely. I have LGup and other tools (though I don't know exactly what everything's for, such as firehose and other bootthings). I don't think cross flashing works and I don't want to do it anyway. Thanx!
Click to expand...
Click to collapse
Haven't seen anyone post their qfil backup of ATT rom, but it may be around. Yeah you won't find a kdz file of att rom because att doesn't allow that publicly.
Do you have att now? I'm guessing from what you say that you do, but you would like a kdz so you can go back if needed?
If you do have att, use qfil to back up ea partition individually, or use (I prefer) the bkerler edl utilities (search google), they take some effort to get up and running, but do a great job once done.
If u don't have att now... why would u want it? U may want to use them as a carrier but I'm pretty sure they still check the device imei, and if it's not one sold by them, some things *may* be restricted. I don't use them, only what I've read from others.
maybe you could explain better exactly what you want to do.
Yeah I have the AT&T phone now, and I want the kdz but don't know how to extract that ) :
And what do you mean they don't have it publicly? What if I extract it and post it?
Do you know anywhere where I could find them? I have and android 10 one with a broken screen (which I use Vysor for) and a working android 11 one.
PHANX0M said:
Yeah I have the AT&T phone now, and I want the kdz but don't know how to extract that ) :
Click to expand...
Click to collapse
you can't extract the kdz, that's not possible. You'll never find an ATT or Sprint kdz, they are simply not available, never will be, never have been.
The only thing you can do is back up what you currently have. Using qfil (look in guides section and you'll find how to set that up and use it) is probably the simplest option. You'll have to back up ea partition, and be sure to name them appropriately, as the back up doesn't do that.
Once you've done that, assuming the sim is unlocked, you can do other things you mention you want. But if the sim is not unlocked, you have to do that first, because flashing a different rom does not unlock it.
good luck
AsItLies said:
you can't extract the kdz, that's not possible. You'll never find an ATT or Sprint kdz, they are simply not available, never will be, never have been.
The only thing you can do is back up what you currently have. Using qfil (look in guides section and you'll find how to set that up and use it) is probably the simplest option. You'll have to back up ea partition, and be sure to name them appropriately, as the back up doesn't do that.
Once you've done that, assuming the sim is unlocked, you can do other things you mention you want. But if the sim is not unlocked, you have to do that first, because flashing a different rom does not unlock it.
good luck
Click to expand...
Click to collapse
So if I flash something custom, and then flash the backed up EA partition, it'll have the AT&T ROM/firmware again? I assume the bootloader has to be unlocked for this?
PHANX0M said:
So if I flash something custom, and then flash the backed up EA partition, it'll have the AT&T ROM/firmware again? I assume the bootloader has to be unlocked for this?
Click to expand...
Click to collapse
You'll have to flash back all the att partitions, not just some part of them. The device won't boot otherwise. And no, the boot loader does not have to be unlocked. Look in the guides section for the 'cross flashing' guide, it will explain what you need to do to make that happen, and you'll need a kdz you want to crossflash to. If you decide to x flash to a stock rom.
If all you wan to do is a custom rom, make sure the version of whatever rom you have, including if it's the att one, matches with the custom rom you want to use.
One note though re custom roms on LG devices; you will never be able to have Volte. That's an issue for US people especially, and other countries are getting there also.
LG, in it's infinite wisdom, has their ims stack (needed for volte to work) all over the rom, people have tried to port it, but it's a proprietary implementation, and has not, and probably never will be, ported. So, if you need volte, then your only option is a stock LG rom.
There's only ONE firehose for LG G8 Thinq all models, right? (If I even need to use that thing)
What are the EXACT things I have to back up to be able to revert back to AT&T ROM/Firmware?
So I know the T-Mobile version doesn't work with VoLTE (I've tried it myself and customer service told me I had to have them disable 3G blocker). But will the factory unlocked ROM work with it on an AT&T phone?
Even if I can't do this, is there ANY other way to go back to AT&T stock ROM/Firmware if I flash something else?
AsItLies said:
You'll have to flash back all the att partitions, not just some part of them. The device won't boot otherwise. And no, the boot loader does not have to be unlocked. Look in the guides section for the 'cross flashing' guide, it will explain what you need to do to make that happen, and you'll need a kdz you want to crossflash to. If you decide to x flash to a stock rom.
If all you wan to do is a custom rom, make sure the version of whatever rom you have, including if it's the att one, matches with the custom rom you want to use.
One note though re custom roms on LG devices; you will never be able to have Volte. That's an issue for US people especially, and other countries are getting there also.
LG, in it's infinite wisdom, has their ims stack (needed for volte to work) all over the rom, people have tried to port it, but it's a proprietary implementation, and has not, and probably never will be, ported. So, if you need volte, then your only option is a stock LG rom.
Click to expand...
Click to collapse
There's only ONE firehose for LG G8 Thinq all models, right? (If I even need to use that thing)
What are the EXACT things I have to back up to be able to revert back to AT&T ROM/Firmware?
So I know the T-Mobile version doesn't work with VoLTE (I've tried it myself and customer service told me I had to have them disable 3G blocker). But will the factory unlocked ROM work with it on an AT&T phone?
Even if I can't do this, is there ANY other way to go back to AT&T stock ROM/Firmware if I flash something else?
PHANX0M said:
There's only ONE firehose for LG G8 Thinq all models, right? (If I even need to use that thing)
What are the EXACT things I have to back up to be able to revert back to AT&T ROM/Firmware?
So I know the T-Mobile version doesn't work with VoLTE (I've tried it myself and customer service told me I had to have them disable 3G blocker). But will the factory unlocked ROM work with it on an AT&T phone?
Even if I can't do this, is there ANY other way to go back to AT&T stock ROM/Firmware if I flash something else?
Click to expand...
Click to collapse
Yes there's only one firehose file, and it does need to be used to when using Qfil. And you need to use Qfil to back up ALL PARTITIONS (not just some, all).
I can't help with specific carrier requirements, I only have used Mint. You'll have to ask the carrier what will and won't work.
No, there is no way to go back to att stock firmware. Period. No Other Way than whats already been indicated, from a back up.
AsItLies said:
Yes there's only one firehose file, and it does need to be used to when using Qfil. And you need to use Qfil to back up ALL PARTITIONS (not just some, all).
I can't help with specific carrier requirements, I only have used Mint. You'll have to ask the carrier what will and won't work.
No, there is no way to go back to att stock firmware. Period. No Other Way than whats already been indicated, from a back up.
Click to expand...
Click to collapse
Thank you for all the information thus far. If I restore the backup it can be completely as it was before and functional, including all data and everything? Do I have to unlock bootloader for this? And can I restore a backup from another phone (of the same model)?
Also, if I use the OPEN_CA ROM it'll let me use VoLTE?
Sorry, I'm only used to working with Xperia . Flashtool with Xperifirm was so much easier
PHANX0M said:
Thank you for all the information thus far. If I restore the backup it can be completely as it was before and functional, including all data and everything? Do I have to unlock bootloader for this? And can I restore a backup from another phone (of the same model)?
Also, if I use the OPEN_CA ROM it'll let me use VoLTE?
Sorry, I'm only used to working with Xperia . Flashtool with Xperifirm was so much easier
Click to expand...
Click to collapse
If you restore the backup the phone should then be back to 'stock'. The data partition backup would be probably in excess of 40 gig, no one backs those up.
No, the bootloader only needs to be unlocked if you want root access, this doesn't require root.
Volte depends on numerous things, 1 obviously being that the phone is capable of it, then the carrier has to have that capability, and it has to allow your specific device to use it on their network. I haven't used the open_ca rom so can't say, but have used the us_open in the States, and with Mint mobile it has definitely worked, as has vowifi.
good luck
AsItLies said:
If you restore the backup the phone should then be back to 'stock'. The data partition backup would be probably in excess of 40 gig, no one backs those up.
No, the bootloader only needs to be unlocked if you want root access, this doesn't require root.
Volte depends on numerous things, 1 obviously being that the phone is capable of it, then the carrier has to have that capability, and it has to allow your specific device to use it on their network. I haven't used the open_ca rom so can't say, but have used the us_open in the States, and with Mint mobile it has definitely worked, as has vowifi.
good luck
Click to expand...
Click to collapse
Thank you very much, I've not found such accurate and digestible information elsewhere!
But just to be sure.... I DON'T need to backup the userdata partition? And if I do.... Can I restore it from my old Broken G8 Thinq (which's android 10) to my new one (which's android 11) if I like the apps and stuff better (Both're AT&T). Would I have to unlock the carrier of the old one first (the new one is already unlocked)?
What if it were the same android version? What if it were different preinstalled carrier?
Also does that mean someone can get all my data with use of simple EDL?
PHANX0M said:
Thank you very much, I've not found such accurate and digestible information elsewhere!
But just to be sure.... I DON'T need to backup the userdata partition? And if I do.... Can I restore it from my old Broken G8 Thinq (which's android 10) to my new one (which's android 11) if I like the apps and stuff better (Both're AT&T). Would I have to unlock the carrier of the old one first (the new one is already unlocked)?
What if it were the same android version? What if it were different preinstalled carrier?
Also does that mean someone can get all my data with use of simple EDL?
Click to expand...
Click to collapse
Sorry, I can't be of much help with something like this. I've never tried to back up user data because it's just too much data and I would just prefer to reinstall the apps. Yes, someone could put the device in edl mode and pull off the user data, but if it's a stock device, it will be encrypted.
AsItLies said:
Sorry, I can't be of much help with something like this. I've never tried to back up user data because it's just too much data and I would just prefer to reinstall the apps. Yes, someone could put the device in edl mode and pull off the user data, but if it's a stock device, it will be encrypted.
Click to expand...
Click to collapse
So you're saying if the ROM (whether stock or not) supports encryption, the data pulled will be useless? And could I restore other partitions backed up from ANOTHER of the same device (whether different android version or not)?
And it's only encrypted if there's a lock code/pattern?
And if the bootloader was unlocked someone could just flash a custom recovery and bypass the lockscreen right?
Also luckily Mint doesn't read the IMEI like greedy AT&T
Related
I am certain my G4 is TWN, from the box and the software version. But what are the actual differences to the European H815? Specifically, can I flash European KDZs or use the EU command for flashing a rooted /system image?
Code:
dd if=/data/media/0/system.rooted.H81510c-EU.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Thanks
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Thank you for this. I do not want to unlock it just yet, since I bought it from a local vendor and I have a 2 year warranty with them. I see there is already a rooted image for v10d TWN, so I will flash that soon (are you sure the parameters for the dd command are the same?).
Sidenote, it would be nice if we could compile our own KDZs and make rooted ones.
metalboy94 said:
Thank you for this. I do not want to unlock it just yet, since I bought it from a local vendor and I have a 2 year warranty with them. I see there is already a rooted image for v10d TWN, so I will flash that soon (are you sure the parameters for the dd command are the same?).
Sidenote, it would be nice if we could compile our own KDZs and make rooted ones.
Click to expand...
Click to collapse
I can't really comment on the all the parameters in that command string except to say that it's one I used and it worked well. Whether those numbers would need to be modified for the 10D image or not I can't say - I would suggest you ask the author of that original rooting thread.
BTW you can't unlock the bootloader on the TWN version just now in any case. I tried the official method over the weekend and was told the TWN version was not supported. There's unofficial unlock method available for any G4 variant yet either but people are working on it.
wadken1 said:
I can't really comment on the all the parameters in that command string except to say that it's one I used and it worked well. Whether those numbers would need to be modified for the 10D image or not I can't say - I would suggest you ask the author of that original rooting thread.
BTW you can't unlock the bootloader on the TWN version just now in any case. I tried the official method over the weekend and was told the TWN version was not supported. There's unofficial unlock method available for any G4 variant yet either but people are working on it.
Click to expand...
Click to collapse
Probably the parameters aren't different between firmware images, because they depend on the partition table of the device.
Now waiting for a version of Xposed that is confirmed not to drain battery. Thanks again!
I'm running xposed now with about 10 modules. I don't see any great battery drain.
wadken1 said:
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Click to expand...
Click to collapse
Hang on, I can flash MM into my TWN? I missed that, how does that work? Is there a thread?
wadken1 said:
I have a the TWN version too damn it. - that's what happens when you buy from a global vendor over the internet .
Good news is that you can flash the EU rooted system image. I did and it worked fine.
Bad news is that you can't unlock the boot loader (yet), which means no TWRP or custom roms and flashing a stock Marshmallow leaves you without root and no way to downgrade.
Cheers
BTW I don't know of any differences between the EU and TWN devices other than the version coding - to me it just seems to be a way for LG to control their different markets.
Click to expand...
Click to collapse
I did the same thing, buying online and getting stuck with TWN. I came from a GS6 and was thinking "I'll wack an AOSP ROM on the G4 and I'll have the perfect phone". Now I'll probably never buy another LG even though I actually like the G4 but when we pay close to $1k for a phone we should be able to do what we like with it!
There is a thread for stock marshmallow which you can install with flash fire but there's no root available with that option just now.
wadken1 said:
There is a thread for stock marshmallow which you can install with flash fire but there's no root available with that option just now.
Click to expand...
Click to collapse
I've tried to find the correct thread but could you point me in the right direction?
Thanks
gz5ztg said:
I've tried to find the correct thread but could you point me in the right direction?
Thanks
Click to expand...
Click to collapse
Sorry. Missed this while I was away.
The thread I'm talking about is http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-rom-t3233049
BUT be warned you will lose root !!. So far as I know just now there is no way to get root on stock MM without an unlocked bootloader. This may have changed inthe last couple of days - you'll need to read around the forum.
ALSO there is no sure way back to L is you decide you can't live without root (I certainly couldn't so I'm waiting for further developments). I think I read that someone here more-or-less accidentally managed to recover back to L but I didn't really have time to take in all the details so futher reading needed if you want to take the risk.
wadken1 said:
Sorry. Missed this while I was away.
The thread I'm talking about is http://forum.xda-developers.com/g4/development/stock-h815-20a-stock-rom-t3233049
BUT be warned you will lose root !!. So far as I know just now there is no way to get root on stock MM without an unlocked bootloader. This may have changed inthe last couple of days - you'll need to read around the forum.
ALSO there is no sure way back to L is you decide you can't live without root (I certainly couldn't so I'm waiting for further developments). I think I read that someone here more-or-less accidentally managed to recover back to L but I didn't really have time to take in all the details so futher reading needed if you want to take the risk.
Click to expand...
Click to collapse
Okay thanks, maybe I will wait. This is going to sound like a completely noob type question but what is it that you are doing that you couldn't live without that requires root?
gz5ztg said:
Okay thanks, maybe I will wait. This is going to sound like a completely noob type question but what is it that you are doing that you couldn't live without that requires root?
Click to expand...
Click to collapse
Here's a few of the things I use which need root:
TI Backup
LMT Launcher
Bubble UpnP
FX Explorer (with root)
Gravity Box (xposed) to give expanded desktop
Llama + Secure settings (allows for automated control of airplane mode, gps and others which have been denied by google for default seetings)
Buidprop editor - allows altering a number of settings but especially DPI
Greenify advanced functions
Amplify
Better Battery Stats
Flashfire
Busybox
Viper4Android
SE Linux Mode Changer (needed to allow Viper to work)
Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible
NOTE: The below IS NOT Boost Mobile stock, it's sprint will update when I figure out Boost Stock
The sprint stock does fully work with the Boost Mobile device, LTE/data services seems to not work until you do a Factory Reset (in settings). ##72786# didn't work. It is now working for me fully after the factory reset from settings. The boost apps automatically install after the factory reset and after the celluar setup on first boot.. My Boost, etc.
After a few times of flashing and re-setup I've ended up with HFA error 701 which asks me to contact service provider to configure the device for service. Fixed by turning phone off for 20 minutes to an hour and the activation processed correctly.
If your experience differs, let us know!
Restoring to Stock
Install Motorola Drivers
Download RSDlite v6.2.4: http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Download the Sprint firmware file: https://androidfilehost.com/?fid=673368273298975628
Rename the zip to sperry.zip, the reason for this is to avoid the long file name error in RSD in some locations
Let the flashing process complete
Some people reported RSD not working in Windows 10, this is not fully true, install all moto and android drivers and it will show up fine as seen in below image
http://imgur.com/a/vdQxG
Thanks!,
rootjunky for RSD mirror
moto firmware team for the e4 stock 7.1.1
Have you check if this phone have gsm bands?
USA or International Variant?
zoofie666 said:
Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible
If you would like me to test anything you can hit me up on Discord: Zoofie#6780 and we can brainstorm
Click to expand...
Click to collapse
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.
Mensarius said:
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.
Click to expand...
Click to collapse
Read the root thread
@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.
amarc78 said:
@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.
Click to expand...
Click to collapse
You can only boot it
mendelgordon said:
You can only boot it
Click to expand...
Click to collapse
Yeah, I came to that conclusion. Just read it elsewhere also. I'm going to see what I can do about building twrp.
is it possible to take backup of Moto E4 stock rom with RSD lite ?
kartik verma said:
is it possible to take backup of Moto E4 stock rom with RSD lite ?
Click to expand...
Click to collapse
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.
amarc78 said:
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.
Click to expand...
Click to collapse
For the international variant?
mendelgordon said:
For the international variant?
Click to expand...
Click to collapse
I have the Boost Mobile variant.
Is there anyone with the Boost Mobile variant that made a working system and boot backup? If so, could you please upload it for me? Mine got corrupted somehow and won't restore.
@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
The weirdness with the activation on Sprint/Boost seems to be normal, because I had trouble with two phones recently. The first was a retail unlocked e4 (to be used on Sprint), done before rooting, and activated at a Sprint corporate store last week by a rep who had trouble. The second phone was a retail unlocked Moto g4 Play (also to be used on Sprint), that I rooted first, got the SIM and back-end computer part taken care of by a rep at the same store yesterday, and did the rest myself.
hitokage004 said:
@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
Click to expand...
Click to collapse
Yeah, I know all about that. I've already made a stock rom zip with sprint firmware but I want Boost so I can make a zip for that.
Sent from my LGLS755 using XDA Labs
I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.
CodyF86 said:
I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.
Click to expand...
Click to collapse
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!
amarc78 said:
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!
Click to expand...
Click to collapse
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes
SykkNyzz said:
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes
Click to expand...
Click to collapse
Hey, don't you have a LG volt?
Hello guys, i have two questions:
a) after you unlock bootloader on this device, is it possible to flash the non boost (international e4) rom on it? if so, have you done it?
b) i used to have a moto e2 from boost mobile (xt1526) and did this with the unlocked international e2 rom (xt1527) and i was able to use my gsm networks with it as i dont live in the U.S and CDMA bands dont work in my country, would it be possible with this device too? Because GSM bands are embeded in snapdragon chipsets, so flashing a stock unlocked firmware should make it work, but i want to know if you have tried it
Good afternoon friends. I still have a problem on my phone "your device has failed a routine safety ..." after I locked the bootloader. I gave it unofficial for repair, they could not do anything there. But now, for some reason, my phone does not load in edl9008 mode, but there is dowmload mode as on other lg devices (in theory, it should not be). So the question is, how to flash the phone via download mode to any other firmware? The main thing for me is that it starts and I can return twrp to restore my native firmware. Yesterday I tried it through uppercut, lgup didn't work. Does anyone have any knowledge of how to download kdz to this phone?
i wish someone would leak at least one sprint KDZ firmware
blaze2051 said:
i wish someone would leak at least one sprint KDZ firmware
Click to expand...
Click to collapse
Don't think you'll ever see, in your lifetime, a sprint kdz. Nor will you see an at&t one.
It's very important to do some research, initially, before messing with your phone. It's common knowledge that these kdz don't exist, and, that is why we always want to do a full backup of our device, especially when the kdz isn't (nor will ever be) available.
So where are u now? what's the situation? I ask because there are sprint backups around (from individual personal devices), that, if done carefully, can be used to fix a device without messing up the imei and s/n.
AsItLies said:
Don't think you'll ever see, in your lifetime, a sprint kdz. Nor will you see an at&t one.
It's very important to do some research, initially, before messing with your phone. It's common knowledge that these kdz don't exist, and, that is why we always want to do a full backup of our device, especially when the kdz isn't (nor will ever be) available.
So where are u now? what's the situation? I ask because there are sprint backups around (from individual personal devices), that, if done carefully, can be used to fix a device without messing up the imei and s/n.
Click to expand...
Click to collapse
phone is good i made more than one backup just it would be nice just to throw LGup and flash instead of using Qfil or other means of backup
I understand I can convert to EU.... However, I don't wish to do that. I just want to root my stock TMOBILE ROM.
My sim is unlocked and I have the unlock.bin from OnePlus for my phone. For anyone who has rooted TMOBILE stock ROM, which boot.img did you patch? I've read that AA boot image can work, but no firsthand accounts confirming this.
Ideally, I'd like to use my own boot.img but I can't find a tutorial or guide anywhere advising how to obtain my boot.img without root.
Thanks!
use AA boot img, but recommend unlocking Bootloader and backing up your tmo modem a/b imgs
How to guide
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Use partitions backup (app) to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
galaxyuser88 said:
Use partition magic to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
Click to expand...
Click to collapse
What is partition magic? An app? Software?
Pain-N-Panic said:
What is partition magic? An app? Software?
Click to expand...
Click to collapse
Sorry meant to say partitions backup. Which is an app.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Pain-N-Panic said:
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Click to expand...
Click to collapse
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
galaxyuser88 said:
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
Click to expand...
Click to collapse
Yep, confirmed, 9pro and my computer can talk. The whole MSM thing is what is worrying me. In the MSM tool, it says it is the TMO -EU MSM. So, once it does it's thing and flashes it all, it should wipe the phone, it would be on the EU rom?
From there, I would need to follow the steps, unlock BL, flash modems, and then download oxygen updater to be able to locally download updates and install?
I flashed my device using the Indian MSM Tool and I am unable to revert back the stock T-Mobile flash using the T-Mo MSM Tool. Now my mobile radio will not enable. I tried flashing multiple T-Mobile modems that are posted on here and that did not fix the issue. So let me summerize.
Can someone guide me to 1) Flashing back to the T-Mobile stock firmware from the IN version, and or 2) Help me get my radios working again. I'd be willing to donate to whoever can help me resolve this issue!
Thanks!
Thanks, unfortunately it didn't work for me. My IMEI, MAC Addresses, and fingerprint functionality is still working. Now it's not recognizing my SIM card at all.
@FizzyAps @craznazn Do yall have any suggestions? Seems yall are the all stars here!
ripclap said:
Thanks, unfortunately it didn't work for me. My IMEI, MAC Addresses, and fingerprint functionality is still working. Now it's not recognizing my SIM card at all.
@FizzyAps @craznazn Do yall have any suggestions? Seems yall are the all stars here!
Click to expand...
Click to collapse
India MSM is known to screw things up and make devices think they are LE2120 instead of whatever it originally was, but at the same time, that's what makes it able to also flash ColorOS over to Oxygen easily...
I remember people solving something like issue on this forum, might need to search extensively.... I haven't had my OP9P for over 6 months now probably, so I can't help much... best of luck!
bencozzy said:
Is it possible to pop a different sim in to see if it recognizes it? Could be the sim.
Click to expand...
Click to collapse
I tried 2 others but no luck.
craznazn said:
India MSM is known to screw things up and make devices think they are LE2120 instead of whatever it originally was, but at the same time, that's what makes it able to also flash ColorOS over to Oxygen easily...
I remember people solving something like issue on this forum, might need to search extensively.... I haven't had my OP9P for over 6 months now probably, so I can't help much... best of luck!
Click to expand...
Click to collapse
[]
I really hate to say this. But I don't think there's no coming back from India os. I did the same thing not once but twice. I called T-Mobile and used my insurance. Only way. Read the topic in this forum bout the India msm tool. Idk if u noticed how much different the India os is from the eu and global os. But if there's away I wanna know also. Cause now the only msm tool your going to be able to use is the India one. But you can update to the a12 one of the color or oxygen I can't remember but ur modem will come on everything will be fine for a few days then it will start messing up again.
ripclap said:
I flashed my device using the Indian MSM Tool and I am unable to revert back the stock T-Mobile flash using the T-Mo MSM Tool. Now my mobile radio will not enable. I tried flashing multiple T-Mobile modems that are posted on here and that did not fix the issue. So let me summerize.
Can someone guide me to 1) Flashing back to the T-Mobile stock firmware from the IN version, and or 2) Help me get my radios working again. I'd be willing to donate to whoever can help me resolve this issue!
Thanks!
Click to expand...
Click to collapse
have you read this thread yet?
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
amaroney55 said:
I really hate to say this. But I don't think there's no coming back from India os. I did the same thing not once but twice. I called T-Mobile and used my insurance. Only way. Read the topic in this forum bout the India msm tool. Idk if u noticed how much different the India os is from the eu and global os. But if there's away I wanna know also. Cause now the only msm tool your going to be able to use is the India one. But you can update to the a12 one of the color or oxygen I can't remember but ur modem will come on everything will be fine for a few days then it will start messing up again.
Click to expand...
Click to collapse
I think you're right. I'm going to RMA it with Oneplus.
I thought with my persist, modest1, and modemst2 I could SMT flash it and restore those files but I get a OnePlus write protection using edl and the OEM Unlocking option will not enable in the OS now. Hopefully they warranty repair it. That's my only concern. It's fairly new lol
Sorry I am just going on what that one thread was saying. And my experience I had to make TMobile believe that it was the phone breaking. Be sure to switch it back to the TMobile os. If the msmtool doesn't work fastboot flash it back before u take it back. The 2nd time they went through my phone saw I had the xda app they really started questioning me. I grabbed my phone back and said umm why u looking in my phone privacy dude. You're concern is only with network and data not my apps files and folders. But just save ya some trouble
amaroney55 said:
Sorry I am just going on what that one thread was saying. And my experience I had to make TMobile believe that it was the phone breaking. Be sure to switch it back to the TMobile os. If the msmtool doesn't work fastboot flash it back before u take it back. The 2nd time they went through my phone saw I had the xda app they really started questioning me. I grabbed my phone back and said umm why u looking in my phone privacy dude. You're concern is only with network and data not my apps files and folders. But just save ya some trouble
Click to expand...
Click to collapse
I'll just flash it clean to where it doesn't even boot lol
Maybe its a bit off topic... but what do we learn about it? NEVER buy a carrier branded device if you want play with root. The lower price is not worth. I learned that over 10yrs ago xD
RheinPirat said:
Maybe its a bit off topic... but what do we learn about it? NEVER buy a carrier branded device if you want play with root. The lower price is not worth. I learned that over 10yrs ago xD
Click to expand...
Click to collapse
Yea I learned my lesson
What sucks is I have the modemst1, modemst2, and persist image backups but I cannot unlock it to upload. I am trying to modify the MSM Tool settings.xml to patch the modemst and persist images and I almost had success using the SMT Downloader but I think I don't have the offset bytes set properly to match the partition table.
Try this, worked for me from In back to TMO....
File on MEGA
mega.nz
TheGhost1951 said:
Try this, worked for me from In back to TMO....
File on MEGA
mega.nz
Click to expand...
Click to collapse
Internet explorer user spotted. xD
ekin_strops said:
Internet explorer user spotted. xD
Click to expand...
Click to collapse
Beg your pardon, I used the Indian MSM to unbrick before I was aware of it changing my TargetID to IN. Now I have to use a modded MSM tool to flash TMO firmware. I use Python3 to extract the .ops file, then open settings.xml, remove the "Target" line at the bottom encrypt back to a .ops file with the name out.ops and then flash that with the MSM tool. Then it will flash the TMO firmware and you are good to go.......
- op6 user - its destroyed now
but as i see that u cant use any other msm but the indian one? right?
i destroyed my op6 system and partations before,
OnePlus Agency, tried to fix it but no luck, i fixed it by msm but not the normal one
if 9pro msm is the same as op6 so you should do this
first, take twrp backup of EFS and MODEM partations and VENDOR ( idk if vendor is important but for precaution )
take another backup of EFC and MODEM by any root apps for precaution too
use the t-mobile msm flashtool and press on verify
the SMT mode should be able to use now
go to options, turn on the COM box or whatever
start flashing with SMT, but i think its high risk bc idk what error you get by normal flashing
keep in mind that SMT Mode will reFlash all known partations and hidden, hidden like MODEM, EFS, etc
my story with this is long, but funny for me, and big lesson..
thx for allah
@ripclap
edit: forget to tell that u have to restore the EFS backup, u should root t-mobile version or idk if u can restore it with some apps without root i dont remember
with op6 old firmware there is something called nvBackupUI it allow us to backup EFS and Restore it by one file
i know this maybe too old now but it may help
edit2:
some links about backup and restore EFS
1- https://community.oneplus.com/thread?id=278167
2- https://www.getdroidtips.com/how-to-backup-or-restore-qcn-efs-on-qualcomm-devices/
3- https://www.droidthunder.com/how-to-backup-efs-imei-on-android-phones/
ALL of this is for SMT Mode, because it may clear the EFS partation and Root is needed to restore it, idk if there is non root method, do ur own search