Develop Bugs

Progress: Boost Mobile Moto E4

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

MODEM went crazy after upgrading MIUI to [Global 10.3.5.0] from [China 9.6.12]

Hi, I'm begging you all for help.
Please, even if you don't know the answer, share any sort of advice.
I'm not a newbie (25+ years story of Unix/Reversing), but I know nothing about radio.
Here's a list of symptoms:
1) Sometimes the WIFI MAC Address comes up as 02:00:00:00:00:00 and IMEI isn't available, then they both magically come up (without rebooting, after the SIM Is read - see n. 2)
2) It keeps powering ON & OFF the SIM and switching between Connected , No Signal , Emergency. Sometimes taking the SIM out & back in helps. Selecting the Preferred Network Type from the modem debug screen keeps it connected for long periods.
3) It won't search for alternative networks to Register Manually
3) IMS Registration is showing as Not Registered always, even while it's connected: Voice + Data (?!?)
4) From the Debug Info only 1 cell appears as SRV = R+N and has a CELL ID, so it seems it connects only to 1 cell at a time.
I can't post screenshots as I lost my old username here, so I signed-up again.
Nothing works, it was a new phone. I wanna die.
Thank you all for your help.
Thanks.

I have problems with modem and camera wgen updating ta android 9.
I would recomend you to rollback to 10.2.1.0
I would use this method
1. Backup your media files to your computer
2. Unlock bootloader
3. Download fastboot china version of 10.2.1.0 and Flash it with mi flash (choose wipe but dont lock!)
4. Flash orange fox twrp with fastboot
5 wipe all partitions exvept internal storage with orangefox
6. Download 10.2.1.0 from xiaomi.eu and flash it with orangefox
Tell me is you want direct links to all files that you need.
If you still have problems after downgrading I can prove my persist and modem files
Good luck

eliaztheone said:
I would recomend you to rollback to 10.2.1.0
Click to expand...
Click to collapse
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)

DoYouWantFriesWithThat said:
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
Click to expand...
Click to collapse
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...

eliaztheone said:
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
Click to expand...
Click to collapse
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone

DoYouWantFriesWithThat said:
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
Click to expand...
Click to collapse
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?

eliaztheone said:
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
Click to expand...
Click to collapse
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump

DoYouWantFriesWithThat said:
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
Click to expand...
Click to collapse
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..

eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I tried it following this guide to restore the Persist partition (https://forum.xda-developers.com/xi...guide-restoring-persist-partition-to-t3906424 - via Fastboot, not EDL) , and right after flashing the SIM was working fine on 4G/LTE and the phone didn't present any problems.
Then I opened up Google-Maps and gave it permission to read the GPS and it went crazy: not reading the SIM anymore, rebooting, etc. And turning GPS off now won't help. So I guess the problem is with the Modem and the fact that it connects to only 1 Cell - no idea why.
@eliaztheone

eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I am on 10.2.1.0 - Android 8.1 now. In addition to what you suggested I restored the persist.img via Fastboot (not EDL) following this guide on XDA .
Right after flashing the phone didn't present any problems (SIM/4G was working without hiccups). As I opened up Google-Maps and gave it permission to read the GPS it went crazy: not reading the SIM anymore, rebooting, etc. Turning GPS off now won't help, it constantly reboots - I have to use Airplane Mode.
So I guess the problem is still in the Modem. Maybe it's the fact that it connects to only 1 Cell, apparently.
@eliaztheone if you can provide the files I'll try one last time. Thank you.

I will upload them tonight hopefully. You need to be on 10.2.1.0 oreo xiaomi.eu version.
You also need to be rooted with magisk so you can restore them with partition backup and restore
---------- Post added at 07:33 PM ---------- Previous post was at 07:28 PM ----------
Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img

Take your time, thank you.
While inspecting the ramdump I noticed the following:
[ 21.864464] [c:1] [p:<003975, android.vending>] Fatal error on the modem.
[ 21.864522] [c:1] [p:<003975, android.vending>] modem subsystem failure reason: rflm_diag_error.cc:361:[email protected]_qlnk.cpp:1090 [9,3] RF stuck in QLINK start s.
[ 21.864530] [c:1] [p:<003975, android.vending>] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.​
There's many SELinux odd log entries too, not sure if that's normal. When I disabled SELinux from the terminal the 4G immediately picked up...totally weird
eliaztheone said:
[/COLOR]Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Click to expand...
Click to collapse
I'll try to flash it, thank you.
I am on 10.2.1.0 oreo xiaomi.eu. Do you think it makes sense to try a custom ROM ?
Thank you.
EDIT:
- I flashed modem_fix_ysl.zip but it didn't have any effect.
- I find the ramdumps from the china ROM much cleaner and errorless than the Xiaomi.eu ROM, just saying

I have sent you a pm

Have you guys found a solution? I have the exactly same problem on Mi Max 3 4/64Gb version. I'm on MIUI Global Stable 10.3.5.0. I was on China stable and had issues,so i flashed Global Stable fastboot rom using Mi Flash Tool(flash all option),and It doesn't solve the problem.I have unlocked bootloader,and no previous system backup.
Also i tried flashing NON-HLOS.bin file from Global Stable fastboot ROM using command : fastboot flash modem NON-HLOS.bin
Also i tried something that worked on my old redmi 4,after NON-HLOS.bin flash,executed fastboot commands :
fastboot erase modemst1 and modemst2,but no luck because of "partition is write protected" error.
Have you found what's the cause of this problem?Is it hardware?Is it corrupted modem files?Will custom rom solve it? Please, any help,any suggestion will be appreciated. I'll try everything to fix it. Thank you in advance.

@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.

DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Thank you man, I'll try everything you said tommorow. The device hardware is awesome,and i really want to support xiaomi,only if they had solution for this problem. Also i think keeping ARB on unlocked bootloader is a bad decision,it really makes this whole process harder.
I'm hoping you get you phone fixed and looking forward to see how this will end.
Thanks for helping me man.
(Sorry for bad English)
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
Maybe someone's QCN file can help us?

DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Maybe someone's QCN file can help us?[/QUOTE]
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.

@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.

DoYouWantFriesWithThat said:
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
Click to expand...
Click to collapse
I found some article that shows how to flash QCN file form DIAG mode,and how to enter that mode. I'll try and keep you updated.

Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.[/QUOTE]
Did EDL flash solved the problem?

LG G8 LMG820UM AT&T STOCK FIRMWARE/KERNEL

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

Question T-Mobile NETWORK UNLOCK PAID SOLUTION

I have OnePlus 9 pro t mobile, I was using eu rom normally, when eu network problem gave, I returned to tmo via msm in hopes that the network problem would be solved. but i keep getting this error t mobile team They said that there is no problem, the network can be unlocked, please try again. , please help someone , i checked the imei on the back of the device and the same inside . If anyone has encountered this problem before, can you tell me the solution? Whatever the solution is, I'm ready to do it, I couldn't solve the problem no matter what I did, eu network didn't work, I tried custom rom, but the result is that I can't get the same network and I don't have a t mobile sim card. Please someone help with this. Is there any file that I can remove this lock on the computer? My English is a bit bad, sorry about that. I'm ready to give 50 euros to the person who can solve this problem, please help.

Under settings/about phone/status what do you see?

TheGhost1951 said:
Under settings/about phone/status what do you see?
Click to expand...
Click to collapse

selimo21 said:
View attachment 5814737
Click to expand...
Click to collapse
Have you tried going into settings/system and resetting network settings?

TheGhost1951 said:
Have you tried going into settings/system and resetting network settings?
Click to expand...
Click to collapse
yes i tried and no result

Something happened to the phone, now I'm getting this error, what happened? can someone help?

Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO

TheGhost1951 said:
Search in threads for TMO non-halos.img and flash it in fastboot mode. It flashes the modem and radio for TMO
Click to expand...
Click to collapse
I couldn't find the file you mentioned, can you help me? can you link the file

[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
Quick Google search

TheGhost1951 said:
[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
Quick Google search
Click to expand...
Click to collapse
I flashed it and the result is wrong, I still get the error you see above.

selimo21 said:
I flashed it and the result is wrong, I still get the error you see above.
Click to expand...
Click to collapse
Time to MSM to your original model number....

TheGhost1951 said:
Time to MSM to your original model number....
Click to expand...
Click to collapse
i did the result did not change , if i flash custom rom can i fix network eg pixel experience rom ?

How long was it working on Eu rom before it gave you a problem? Maybe you temporarily sim unlocked the phone for 30 days and that ran out?
OnePlus says you must go through tmobile to get it unlocked. Tmobile does need it on their network for a day or so to be able to unlock it. (They tried to do mine manually but there was no data for my phone and there is an exchange that takes place on their server so it has to be online).

Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.

I also had the same problem on OP9. It happened after playing with modemst partition.

joecool1029 said:
Looks like the efs may be somewhat corrupt. Hope you backed up modemst1/modemst2 partitions like the conversion thread suggested you do. You'll want to flash these both back on and then problems should be resolved. You cannot use someone else's partitions, has to be yours.
MSM'ing will not help this situation. Need to unlock permanently using t-mobile's unlock in original ROM after you've restored those partitions. It blows an efuse when it does this, no custom rom can be used as a workaround.
Click to expand...
Click to collapse
Unfortunately I don't have my own modem backups. but someone else has a backup, what can i do? please help me
ElitePotato said:
I also had the same problem on OP9. It happened after playing with modemst partition.
Click to expand...
Click to collapse
did you solve the problem? I have someone else's backup, do I have a chance to use it, please help

I have all the modem related imgs for A12 TMO if needed OP9P

TheGhost1951 said:
I have all the modem related imgs for A12 TMO if needed OP9P
Click to expand...
Click to collapse
Thank you very much for this. Finally, I'm thinking of taking a twrp backup and installing it. I've tried everything with modem backups and the result is unsuccessful I hope someone can fix this problem.

selimo21 said:
Something happened to the phone, now I'm getting this error, what happened? can someone help?
View attachment 5814789
Click to expand...
Click to collapse
Take ur SIM out then restart and connect to a US VPN and try again

L0ND0NB0Y said:
Take ur SIM out then restart and connect to a US VPN and try again
Click to expand...
Click to collapse
unfortunately i tried that too. this problem happened because i deleted modemst1 and modemst2 file in eu rom. I guess the tmo unlock application cannot read the phone's information so the unlock is refusing to bind.

Question Requesting param.bin from someone with working T-Mobile OnePlus 9 Pro stock

Hey all,
My phone has an issue where it's stuck on target IN, but I discovered with the help of retryfail that the target ID is in the param.bin partition. Does anyone have a param.bin they can dump from their phone using EDL or something? This would help me get back to stock.
Thank you,
razercortex

razercortex said:
Hey all,
My phone has an issue where it's stuck on target IN, but I discovered with the help of retryfail that the target ID is in the param.bin partition. Does anyone have a param.bin they can dump from their phone using EDL or something? This would help me get back to stock.
Thank you,
razercortex
Click to expand...
Click to collapse
I'd like the as well if anyone has it for LE2127 TMO c.22 firmware. But if you use a modded msm tool to accommodate the IN TargetID wouldn't the param img get written over and get you back to stock?

If I borrow my wife's phone long enough, I can get it. She has the same LE2127 9 Pro....

Here you go....

if it works, let me know and include the steps you took....please!

Hi all,
In order to use the file, unlock bootloader, then reboot to fastbootd. From fastbootd, run "fastboot flash param param.bin". You will be able to run stock TMO MSM after this. It doesn't really matter what FW version you are on, you can flash it anyway as long as it's a TMO device.

razercortex said:
Hi all,
In order to use the file, unlock bootloader, then reboot to fastbootd. From fastbootd, run "fastboot flash param param.bin". You will be able to run stock TMO MSM after this. It doesn't really matter what FW version you are on, you can flash it anyway as long as it's a TMO device.
Click to expand...
Click to collapse
You successfully got rid of Target is IN with this? How do you check it?

Yaaaaaaa....!!!!!!

TheGhost1951 said:
if it works, let me know and include the steps you took....please!
Click to expand...
Click to collapse
You'll need to generate new unlock token after you flash this, otherwise you won't be able to unlock bootloader.

TheGhost1951 said:
You successfully got rid of Target is IN with this? How do you check it?
Click to expand...
Click to collapse
Try to flash regular TMO MSM.

TheGhost1951 said:
Yaaaaaaa....!!!!!!
Click to expand...
Click to collapse
I'm so happy for you bro!!

TheGhost1951 said:
Yaaaaaaa....!!!!!!
Click to expand...
Click to collapse
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.

Oh my god. I've been dealing with this stupid indian thing for months, I gave up on trying anymore. No matter what I did , I could never get a normal UNMODDED TMobile msm to run for me.
But I got it now.
Followed the steps above. Unlocked bootloader, went into fastbootd and flashed the param.bin from above, and immediately after that I shut the phone off right from fastbootd mode. Started my TMobile msm tool , plugged it in and we are good!

I'm shocked at how easy of a solution this was, I was trying so many other long drawn out trial and errors and it was truly this easy

razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
hold on...

razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse

razercortex said:
Also, while you're at it, is it possible for you to retrieve persist.img as well? I think mine broke, not allowing for use of FP sensor.
Click to expand...
Click to collapse
I encourage you to make a new How-To thread in this forum with instructions on how to fix the target IN problem. There are a quite a few people who are stuck on IN after using the Indian MSM tool. I saw it being asked a bit in the OnePlus telegram group a few months back too. Good work.
It's one more thing off the list for us to have complete control of our device. Since we have the last "real" OnePlus phone with msm tool, the development on this device may go on for a long, long time

Sorry guys, I pulled my param.bin file because deep inside some settings my wife's name was on my phone. I used her param.bin because it was pure TMO... Personal reasons and security reasons as well... hope y'all understand. and as it is I have now gone with flashing my phone to global...... i actually like it better. Got away from a branded phone!

Appreciative said:
I encourage you to make a new How-To thread in this forum with instructions on how to fix the target IN problem. There are a quite a few people who are stuck on IN after using the Indian MSM tool. I saw it being asked a bit in the OnePlus telegram group a few months back too. Good work.
It's one more thing off the list for us to have complete control of our device. Since we have the last "real" OnePlus phone with msm tool, the development on this device may go on for a long, long time
Click to expand...
Click to collapse
I'm going to refrain from doing so because it can potentially cause side effects, but if anyone wants to do so, by all means.

TheGhost1951 said:
Sorry guys, I pulled my param.bin file because deep inside some settings my wife's name was on my phone. I used her param.bin because it was pure TMO... Personal reasons and security reasons as well... hope y'all understand. and as it is I have now gone with flashing my phone to global...... i actually like it better. Got away from a branded phone!
Click to expand...
Click to collapse
At least we know it's possible now. Do you think we need a pure virgin new in box param or do you think there are specifics to the device and that's why he ( @razercortex ) needed persist also? (I was under the impression that persist was device specific)
I also understand your reservations @razercortex, I suppose we can point people here when it comes up, they can read the thread and understand the risks. I'm not stuck on IN but I knew it was possible to undo something the msm package did and I'm glad to see @TheGhost1951 was finally able to undo it. I knew he felt the same way about undoing whatever was done by the IN msm. Maybe someone can piece together a custom repair msm using a virgin param...but maybe I'm getting ahead of myself