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
Related
Hi guys! This bootloader unlock version is only for ARGENTINIAN models.
You can donate me (PAYPAL LINK COMING SOON) and @cerg2010cerg2010 through paypal.
@cerg2010cerg2010 PAYPAL EMAIL: [email protected] OR QIWI: +79157840294
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
No more secure boot error!
I thank my friend @cerg2010cerg2010 for helping me out in patching the aboot.
Supported Model:
Code:
H440AR
-> Steps:
(1) Downgrade to v10a or v10d version of Android.
(2) Root your device.
(3) Download this patched aboot file. Click Here for v10a. Click Here for v10d.
(4) Connect your phone to the computer. In command prompt, type "adb shell".
(5) Transfer the aboot file into /sdcard/ folder.
(6) Type "su" to enter the root shell. Then type "dd if=/sdcard/<file_name_you_downloaded_in_3rd step> of=/dev/block/<your aboot partition>".
(7) Restart your phone by typing "reboot".
You have unlocked your bootloader!
Refer Notes for more information.
-> Notes:
1) The aboot_5120_patched.bin or aboot_10d_patched.bin is the patched version of aboot partition of your device. Secure boot validation has been patched such that secure boot is always valid, so you can flash your own TWRP and Custom ROM.
2) Don't upgrade to any updated version of Android if you get any through OTA update. It might brick your device.
I'll give it a try soon, hopefully if the guys here are correct 4g/lte should work now. Thanks a lot!
Edit: apparently this fixed the issue regarding LTE using argentinian bands, I'll keep testing it but so far it holds even after a call and a low signal area it just switches from lte to 3g and so on (which wasn't working with the other aboot)
Korelev said:
I'll give it a try soon, hopefully if the guys here are correct 4g/lte should work now. Thanks a lot!
Edit: apparently this fixed the issue regarding LTE using argentinian bands, I'll keep testing it but so far it holds even after a call and a low signal area it just switches from lte to 3g and so on (which wasn't working with the other aboot)
Click to expand...
Click to collapse
Thanks for confirming!
You did it!!!! Many Many Thanks!!!! T.T
69PerTTu69 said:
You did it!!!! Many Many Thanks!!!! T.T
Click to expand...
Click to collapse
Hey, I'm trying to download the Argentinean aboot, but the link is dead. Can anyone help me with it ?
mayankjet said:
Hey, I'm trying to download the Argentinean aboot, but the link is dead. Can anyone help me with it ?
Click to expand...
Click to collapse
They aren't broken
69PerTTu69 said:
They aren't broken
Click to expand...
Click to collapse
My bad.
links are not working for me
edit: apparently they are now
Quick question: by unlocking the bootloader I should be able to later flash a custom recovery and then root the phone, right? As the argentinian version seems to be unrootable via kingroot (which is what the general thread recommends). Do I got this right, or is there a simple version to root it? Thanks.
Kon22 said:
Quick question: by unlocking the bootloader I should be able to later flash a custom recovery and then root the phone, right? As the argentinian version seems to be unrootable via kingroot (which is what the general thread recommends). Do I got this right, or is there a simple version to root it? Thanks.
Click to expand...
Click to collapse
First you need to be on Lollipop.
Root it by using Kingroot.
Unlock the bootloader.
Flash TWRP 3.1.1.0
Flash MM v20b zip proposed by Korelev.
Flash Supersu.
Now you have a rooted MM.
walterfuster said:
First you need to be on Lollipop.
Root it by using Kingroot.
Unlock the bootloader.
Flash TWRP 3.1.1.0
Flash MM v20b zip proposed by Korelev.
Flash Supersu.
Now you have a rooted MM.
Click to expand...
Click to collapse
I tried rooting it using Kingroot with no success, both with the APK and the app on PC. Running stock lollipop, obviously. I assumed the argentinian version (H440AR) couldn't be rooted via kingroot, which is why I'm wondering if the only way is to simply unlock bootloader, flash TWRP and then flash SuperSU.
Kon22 said:
I tried rooting it using Kingroot with no success, both with the APK and the app on PC. Running stock lollipop, obviously. I assumed the argentinian version (H440AR) couldn't be rooted via kingroot, which is why I'm wondering if the only way is to simply unlock bootloader, flash TWRP and then flash SuperSU.
Click to expand...
Click to collapse
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this. Kingroot converts your phone in a turtle.
walterfuster said:
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this, Kingroot convert your phone in a turtle.
Click to expand...
Click to collapse
Huh, that's odd then, that Kingroot couldn't do it. I'll keep looking into it, then. Thanks for the help, will report back.
walterfuster said:
The thing is, you can't unlock the bootloader without first having su permissions.
AR device version shouldn't be a problem.
Mine is Argentinian too and I easily rooted it.
Try with an older version of Kingroot. You can easily find it around apk's sites.
If no luck, try flashing an H440N kdz (I'm on POL v10i) with LG Flash Tool 2014, and see what happens.
You can do a dirty flash if you don't want to lose your data.
P.S.: I even switched from Kingroot to SuperSU. I highly recommend this. Kingroot converts your phone in a turtle.
Click to expand...
Click to collapse
Hello there. I managed to use kingroot to root one of the two spirits I have (the other one still doesn't budge, for whatever reason) and indeed it turns the phone into a turtle. I was wondering, is it possible to flash superSU without flashing marshamallow before? Not that I'd mind flashing it, but without the ability to use an SD card as internal storage the main advantage is gone, and I wouldn't wanna have MM if it hurts battery time or fluidity of the phone.
Kon22 said:
Hello there. I managed to use kingroot to root one of the two spirits I have (the other one still doesn't budge, for whatever reason) and indeed it turns the phone into a turtle. I was wondering, is it possible to flash superSU without flashing marshamallow before? Not that I'd mind flashing it, but without the ability to use an SD card as internal storage the main advantage is gone, and I wouldn't wanna have MM if it hurts battery time or fluidity of the phone.
Click to expand...
Click to collapse
If I don't get wrong, you want to stay on a SuperSU rooted LP, right?
Well, you can get that, not by flashing, but by replacing Kingroot with SuperSU.
you'll have to do the following:
https://forum.xda-developers.com/a3...place-kingroot-kinguser-t3308989/post65167979
P.S.: If you decide to stay on LP for definitely, I highly recommend you apply the Tomo's tweaks.
They get the most of Spirit running LP:
https://forum.xda-developers.com/lg...formance-battery-saving-t3217133/post63121297
So if I get this right I should be able to use custom roms after doing this procedure? I've been asking about in the LOS14.1 rom thread but people talking about a bluescreen when they ran out of signal in the argentinian model scared me off. I cant get a new phone atm in case I brick this one. Nobody could give me a definitive answer about it so far.
Niku200 said:
So if I get this right I should be able to use custom roms after doing this procedure? I've been asking about in the LOS14.1 rom thread but people talking about a bluescreen when they ran out of signal in the argentinian model scared me off. I cant get a new phone atm in case I brick this one. Nobody could give me a definitive answer about it so far.
Click to expand...
Click to collapse
Yes, following this procedure can get your bootloader unlocked. Also LOS does have that blue scrren error, only if you don't have network service. However it's not that big of a issue. You can prevent blue screen by using airplane mode.
mayankjet said:
Yes, following this procedure can get your bootloader unlocked. Also LOS does have that blue scrren error, only if you don't have network service. However it's not that big of a issue. You can prevent blue screen by using airplane mode.
Click to expand...
Click to collapse
I knew about that workaround but signal is pretty unstable where I live. Specially when I travel and I like to use spotify while doing so. I'd like to avoid it as much as I can. I guess I'll give it a go and if it fails I can go back flashing a stock firmware.
Niku200 said:
I knew about that workaround but signal is pretty unstable where I live. Specially when I travel and I like to use spotify while doing so. I'd like to avoid it as much as I can. I guess I'll give it a go and if it fails I can go back flashing a stock firmware.
Click to expand...
Click to collapse
Okay.
So, I've been trying to download this several times but I'm always hit with a trafic limit from the person who shared it. Would somebody share me the files somehow?
I picked up the Moto E4 recently and rooted it. The OTA has been sitting in limbo because I didn't wanna get screwed and get stuck in an non-root attainable update. As soon as I got root, pulled it, and here ya are. I have included a list to procure as well.
Link for download HERE
I hope it helps.
emtee40 said:
I picked up the Moto E4 recently and rooted it. The OTA has been sitting in limbo because I didn't wanna get screwed and get stuck in an non-root attainable update. As soon as I got root, pulled it, and here ya are. I have included a list to procure as well.
Link for download HERE
I hope it helps.
Click to expand...
Click to collapse
Could you possibly make a back up and upload it for me before you make any system modifications. I have boost but my original backup got corrupted somehow and I want to make sure what I'm running is the right firmware. I also want a backup of that original firmware. If you could also do me another favor and pull the oem.img and modem.img and upload them along with the recovery.img? I'm making stock ROMs and for some reason a rom made with what I thought was Sprint firmware works fine, but one made with what I thought was Boost firmware gives me a boot loop for some reason and I'm trying to figure out why? I'd really appreciate it. If you don't know how to pull the imgs I can instruct you, it's really simple. Thanks!
This is the older update, right? Not a new one...
ATTACK said:
This is the older update, right? Not a new one...
Click to expand...
Click to collapse
I just bought the Verizon varient. It updated today. I plugged into my PC and ran Kingroot. It asked to "try new root strategy", something it did not ask before. Root still fails though.
"This is the older update, right? Not a new one..."
Probably, it will bring NCQ26.69-33 to NCQ##.##-35 for Boost. (According to meta file in zip)
"I also want a backup of that original firmware"
Since I've already rooted, unrooted, lost cell service, lost system, and, just today, bringing it back to a usable state, I can vouch for the NCQ26.69-33 located here
Use the RSD XML-to-flash tool. Found it on Google somewhere.
My best advice is to use the "dm-verity-opt-encrypt.zip" located in root guide before any flash, especially if it entails a system related modification (ie magisk, scripts, etc). If ya get a non-flashable state, flash the boot.img again in twrp, reboot and redo the flash "dm-verity-opt-flash.zip"
Many thanks for kartik verma for posting the OEM device files link.
ATTACK said:
This is the older update, right? Not a new one...
Click to expand...
Click to collapse
DragonFire1024 said:
I just bought the Verizon varient. It updated today. I plugged into my PC and ran Kingroot. It asked to "try new root strategy", something it did not ask before. Root still fails though.
Click to expand...
Click to collapse
Using Motorola's company website to get the unlock key and using fastboot to flash, as stated in the rooting guide, is most thorough. Less 3rd party spam too
I have Boost but digging in the device files has shown a lot of 'verizon' being in various system files. Sprint, is Sprint, especially in prepaid flavors, imho.
...35? I have NCQ26-69-48 on a Boost E4. So yeah, older firmware.
Yes, the newest Boost firmware is this one from the link posted above.
SPERRY_SPRINT_7.1.1_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1.6 GiB
The one without 7.1.1 in the name is Sprint.
Sent from my Moto E (4) using XDA Labs
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img ,
{{{ bootloader "NO NEED" This Work Before Just Because v48 and v56 have the same bootloader version }}} , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
EDIT HELLO
Things Have Changed Dont Try To Downgrade Bootloader or The Phone Will Get Hard Bricked , Why well bootloader versions on new firmwares have been upgraded please check all the information on the Bootloader/Fastboot
MODE Of The Phone Which Version You Have , Now For Example If You Are On Version NCQS26.69-64-5 you will need SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml full package then extract and now you will need SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml extract it too , Now Just Move The 2 Oems Images And 4 System Images And Boot Image To SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml Folder Next Look for RSD_Lite_Motorola_XML_To_Batch_Script on Google Download it And Watch The Video Of Rootjunky on how to use it. Very Simple Wish All Of You Luck And im Not Responsible Of Any Damage Of Your Phone Use This Guide On Your Own Terms.
ozmage said:
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img , bootloader , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
Click to expand...
Click to collapse
I flashed the Sprint firmware and had data working on my XT1766 after it got it's carrier update, the Sprint firmware does not soft brick the phone as I flashed it and can confirm it doesn't soft brick it, so you are incorrect in saying that.
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
dlinderaz said:
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
Click to expand...
Click to collapse
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
madbat99 said:
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
Click to expand...
Click to collapse
I restored the entire thing after flashed the indicated files causing the error message.
dlinderaz said:
I restored the entire thing after flashed the indicated files causing the error message.
Click to expand...
Click to collapse
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
madbat99 said:
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
Click to expand...
Click to collapse
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
dlinderaz said:
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
Click to expand...
Click to collapse
Keep in mind I have the virgin mobile version (sprint xt1766). Don't know which one you have. Some have had trouble with rsdlite on Windows 10, it worked fine for me though.
I used rsdlite from here
The newest one, 6.2.4 I think
Apn Xt1766
I just want to add apn and want to use hot spot again
As the phone is updated on latest build ..
I don't want the root access..
What's should I try then from previous build , can anyone
Guide me easy steps plz.
Xt1766 how to get working apn
Will anyone confirm
danishamini.saifi said:
Will anyone confirm
Click to expand...
Click to collapse
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
madbat99 said:
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
Click to expand...
Click to collapse
Thanks, ill try and share the result.
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
danishamini.saifi said:
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
Click to expand...
Click to collapse
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
madbat99 said:
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
Click to expand...
Click to collapse
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
danishamini.saifi said:
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
Click to expand...
Click to collapse
N/A will be there. But you can flash a new boot logo to kinda hide it. Instead of a black screen, any logo you want, maybe with a white strip at the top to hide it. I'll get you a link.
Here are some good ones. https://forum.xda-developers.com/mo...om-boot-logos-converted-t3759320/post75787882
And here is the guide to make your own
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212/post74118155
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
danishamini.saifi said:
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
Click to expand...
Click to collapse
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
madbat99 said:
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
Click to expand...
Click to collapse
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
dlinderaz said:
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
Click to expand...
Click to collapse
Ota updates will likely always fail if you have twrp, or have modified the system in any way. The ota performs many checks (assert props) to see if the system is clean. If any asserts fail, the ota will fail. Even restoring the stock recovery doesn't guarantee the ota will work.
If you mess up your device I'm not responsible, it works for me, and for others. I will help as much as i can, but it is on YOU, the user to follow the prerequisites and read carefully. This zip was created in collaboration with @TxanMoe and myself
This zip can be used to return to the stock rom(for the most part, you'll still have fastboot,root,twrp) as long as you can get into TWRP recovery on the device. It also flashes the modem bands needed for working Sprint LTE(bands 25,26,41, ect.."all the Sprint bands")
Prerequisites:
1. Activate with Sprint first if you intend to use the converted US998 on Sprint!
2. You already crossflashed to US998 if not follow the guide here "Frankenstein method" [https://forum.xda-developers.com/lg...sflashing-t3780969/post76510671#post76510671]
3. You followed the bootloader unlock, root, TWRP "WTF" thread here https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
(US998 to LS998) Downloads: (Sprint LS998 system,boot,modem)* MAKE SURE TO FLASH MAGISK, NO-VERITY OPT ENCRYPT, AND RCD DISABLER BEFORE LEAVING RECOVERY!!*
Sprint 20b
https://drive.google.com/file/d/1aQojUcchnEruHwnecfaVGToxZbmj-UX3/view?usp=drivesdk
Sprint 21a(may security patch)
https://drive.google.com/file/d/1JCalyu7mt8DW6wMWbgGViqj0oi9eUSr7/view?usp=drivesdk
*Instructions*:
a. Make a backup in TWRP of system,boot,and data before proceeding!
b. Reboot to TWRP and wipe data (factory data reset)
c. Install the SPRINTLS998.zip (20b or 21a)from TWRP (Do NOT leave recovery yet)
d. Flash Magisk, no verity encrypt, and RCD disabler(you should already have these files if you followed the WTF thread)
e. Reboot
d. Once booted up you need to connect to WiFi. go to settings, update profile and prl. Reboot
quantemplation said:
For anyone who flashes back to Sprint but needs to edit the APNs still, you can type this in command prompt(from PC)
Code:
adb shell
su
am start -n com.lge.hiddenmenu/com.lge.hiddenmenu.ModemProtocol.ModemProtocolMain
Then go to PDP Setting
Then go to APN setting
Click to expand...
Click to collapse
be sure to thank his post here
https://forum.xda-developers.com/showpost.php?p=76633700&postcount=45
JonnyTrulove said:
@JWnSC thanks to the help of some of you great people in this thread I have had the chance to do this conversion twice now. Both times it worked great but I did have to update the APN settings before getting mobile data to work for me. I know you were kind enough to include screenshots of the right APN settings but I just wanted to share that both times I used the ##SCRTN## dialer code to force OTA provisioning and it worked, so I thought you may want to add that option to your first post. Might be a good option for someone that's in hurry to get connected.
Only negative I can think of is that you would not have tethering unless you were subscribed or you manually added the "Dun" provision to the APN later.
Just wanted to share in case you thought it was worth adding to your original post. If not, no biggie. Thanks
Click to expand...
Click to collapse
Special thanks:
@TxanMoe for finding the bootloader exploit and helping me along the way
@ChazzMatt for his in depth Guides and help in this forum
@SGCMarkus for TWRP recovery for this device and all the roms he provides
@quantemplation
@JonnyTrulove
and to any others I may have missed..
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP(wipe data) install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
SilverZero said:
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
Click to expand...
Click to collapse
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
JWnSC said:
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
Click to expand...
Click to collapse
Yeah...it sucks we need this...sprint not allowing access to kdz is a load of bs...it is much appreciated that we have you helping to support us sprint users...i am looking back at my past lg phones now to see if i can find the process of creating a working kdz...one of the people i think in the g2 or g3 forums actually created a kdz using the untouched signed lg files and it was fully flashable to get back to 100% stock...i don't know if too much has changed since then to do this again...but it would be nice to have for some...me...i won't be doing anything that removes my bootloader unlock and root...but those with warranty may want to have that ability...thanks to all that have contributed to making this a great device...i missed root on a level people outside these forums may never understand
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
cre4per said:
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
Click to expand...
Click to collapse
Right. change "_COM#" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
JWnSC said:
Right. change "_ whatever com #" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
Click to expand...
Click to collapse
perfect will give it a try, hoping this will let me get volte back on mydevice
JWnSC said:
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
Click to expand...
Click to collapse
Could you lock the bootloader after this? Or will it show an error?
guapinoy said:
Could you lock the bootloader after this? Or will it show an error?
Click to expand...
Click to collapse
Bootloader would still be unlocked but the message after every boot would disappear and you won't be able to enter fastboot. (After you do the system update)
I thought after installing the latest update it would lock the bootloader...it didn't, but it did remove the text after every boot saying to lock bootloader and you won't be able to enter fastboot after. Activating developer options will show the boot is still unlocked. It does change the software info to LS99821a instead of US99820a
To lock the bootloader, you could probably flash the other Sprint zip(without flashing magisk ect..) and just sprint recovery or the factory zip. Reboot to bootloader from twrp and lock it that way. Then do the Sprint system update *I have to do more testing tho I don't recommend doing this until it's tested*
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
You can't update profile/ prl on US998 firmware(or at least I couldn't). Backup your setup and try DotOS if you already have working lte. This thread is mainly for users to get lte back. I'm not running the stock Sprint firmware. I switched to stock firmware first to get lte working and switched back to us998 rom.
If you wipe data and flash the SprintLS998.zip you won't have any issues. It already contains the Sprint modem, system, and boot. No need to flash the modem from the other thread.
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Lurien said:
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Click to expand...
Click to collapse
???
If you flash the Sprint modem you'll have all the Sprint bands.
It's just the US998 does not have LTE bands 26 & 41. So you have to flash the Sprint modem to get them. If the LS998 normally has LTE band 13, then you'll have that.
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
jamesd1085 said:
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
Click to expand...
Click to collapse
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
JWnSC said:
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
Click to expand...
Click to collapse
How did you install? Because twrp is there it failed on mine
jamesd1085 said:
How did you install? Because twrp is there it failed on mine
Click to expand...
Click to collapse
I flashed the factory back to stock.zip and went to settings, system update.
Not worth it imo...I was testing the factorysprint.zip to make sure it worked. I can make a flashable zip later(to only include system, modem,boot)..I don't think much changed. Looks like it was just an update to disable fastboot and access to recovery
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
SilverZero said:
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
Click to expand...
Click to collapse
I had to connect to wifi when i updated profile...it kept telling me to contact carrier when i tried to update through data connection
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