Database Users

Proper Bootloader Unlock Guide for CM12.1 (A501CG)[Asus Zenfone5-T00J-WW] (NO FREEZE)

Hello,
I can see many of users are facing problems in unlocking bootloader. Here is proper guide to unlock bootloader. These steps are tried by me on 3 zenfone WW T00J and they are working like charm. As I don't know state of your bootloader (Locked/unlocked/messed up) so I will be starting from beginning where your bootloader is restored to default state before unlocking. Since I am using Cyanogenmod 12.1 ROM So I will suggest you flash it first due to its kernel.img , boot.img etc once it boots , after that u can flash other roms.
DO IT ON YOUR OWN RISK. THESE STEPS ARE FOR ZENFONE 5 A501CG T00J WW(from India) 1.6Ghz 2GB 16/8GB .
However Same procedure applies with different SKU like TW CN etc. All u need to use your own firmware files.
I assume You Have Android Debug Bridge v.1.0.32.zip And All Intel Drivers Installed. If not Try Google or Other ROM threads to download.
STEPS TO BRING YOUR BOOTLOADER TO LOCKED STATE, THIS WILL NEED FLASHING OF STOCK ROM AND ALL YOUR DATA WILL BE ERASED ON INTERNAL STORAGE SO BACKUP FIRST.
Download UL-ASUS_T00F-WW-2.22.40.54-user.zip From ASUS WEBSITE.
Steps -
1). Extract boot.img, fastboot.img, and recovery.img from the zip downloaded from Above Asus Firmware zip file.
Place them in ADB folder. Also Copy the whole zip to same adb folder.
OPEN ADB prompt by shift + right click and select open command window here in same folder.
2). Boot your phone in Fastboot mode and do exactly as following,
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot erase userdata
fastboot erase data
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
3). Now select recovery from fastboot menu and press power to boot into recovery mode.
4). Press and hold volume down then tap volume up at dead droid splash for recovery menu.
Select adb sideload
and type
adb sideload UL-ASUS_T00F-WW-2.22.40.54-user.zip
Wait Until it downloads on your phone and is installed. It usually takes 20-25 minutes to boot into phone. As this is the first time phone is booting after complete format expect it time taking.
Boot into Phone And Congrats You Have Locked your bootloader properly which is ready to unlock properly
Now Flash This Cyanogenmod as said step by step and boot into it and you will experience no freeze issue. After booting you can even change your rom.
http://forum.xda-developers.com/general/rooting-roms/rom-cyanogenmod-12-1-asus-zenfone-5-t3252789
Enjoy.
Regards
Press Thanks If i Helped. xD
@venturajpo , @pintuvirani , @Fernando0258 , @eragon21

I disagree with this information.
From my perspective screen freezes and reboots happening due to device revision. What i mean is there are few different revisions of Zenfone 5 models.
For example, boot unlock files is compatible with first revision so second revision will get freezes.
It is not fault of bootloader unlock.

Dear maggi I too own the same device as you (same model, cpu speed and ram cap) expect I brought mine form dubai and I experience freeze issues quite often even on stock after un-locking bootloader yet I unlock mine from. 78 stock rom so I'll try your method and see what's happens :fingers-crossed:

what about the no camera problem that some users are experiencing

herecomesmaggi said:
Hello,
I can see many of users are facing problems in unlocking bootloader. Here is proper guide to unlock bootloader. These steps are tried by me on 3 zenfone WW T00J and they are working like charm. As I don't know state of your bootloader (Locked/unlocked/messed up) so I will be starting from beginning where your bootloader is restored to default state before unlocking. Since I am using Cyanogenmod 12.1 ROM So I will suggest you flash it first due to its kernel.img , boot.img etc once it boots , after that u can flash other roms.
DO IT ON YOUR OWN RISK. THESE STEPS ARE FOR ZENFONE 5 A501CG T00J WW(from India) 1.6Ghz 2GB 16/8GB .
However Same procedure applies with different SKU like TW CN etc. All u need to use your own firmware files.
I assume You Have Android Debug Bridge v.1.0.32.zip And All Intel Drivers Installed. If not Try Google or Other ROM threads to download.
STEPS TO BRING YOUR BOOTLOADER TO LOCKED STATE, THIS WILL NEED FLASHING OF STOCK ROM AND ALL YOUR DATA WILL BE ERASED ON INTERNAL STORAGE SO BACKUP FIRST.
Download UL-ASUS_T00F-WW-2.22.40.54-user.zip From ASUS WEBSITE.
Steps -
1). Extract boot.img, fastboot.img, and recovery.img from the zip downloaded from Above Asus Firmware zip file.
Place them in ADB folder. Also Copy the whole zip to same adb folder.
OPEN ADB prompt by shift + right click and select open command window here in same folder.
2). Boot your phone in Fastboot mode and do exactly as following,
fastboot flash fastboot fastboot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot erase userdata
fastboot erase data
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
3). Now select recovery from fastboot menu and press power to boot into recovery mode.
4). Press and hold volume down then tap volume up at dead droid splash for recovery menu.
Select adb sideload
and type
adb sideload UL-ASUS_T00F-WW-2.22.40.54-user.zip
Wait Until it downloads on your phone and is installed. It usually takes 20-25 minutes to boot into phone. As this is the first time phone is booting after complete format expect it time taking.
Boot into Phone And Congrats You Have Locked your bootloader properly which is ready to unlock properly
Now Flash This Cyanogenmod as said step by step and boot into it and you will experience no freeze issue. After booting you can even change your rom.
http://forum.xda-developers.com/general/rooting-roms/rom-cyanogenmod-12-1-asus-zenfone-5-t3252789
Enjoy.
Regards
Press Thanks If i Helped. xD
@venturajpo , @pintuvirani , @Fernando0258 , @eragon21
Click to expand...
Click to collapse
@herecomesmaggi, I think what tank0412 says is true. I have A501CG 1.6Ghz model. First, I used the bootloader provided in the first post of rr thread. I faced screen freezes while playing COC (note: I never faced screen freeze outside games). Then, I followed the quanganh's method of copying if.bin. Screen freeze is still there, but the frequency is greatly reduced. Also, the last time I faced screen freeze I was playing fm and the fm kept playing despite screen freeze. Which means that the os itself didn't get stuck just the screen froze. What could I say from this is, there are several versions of bootloader and using the right one will solve the screen freeze problem. Or if we could find how the bootloader unlocker works.. May be ASUS uses parts from different manufacturers and they are somehow linked to bootloader(It seems unlikely. Just an idea as nothing else is working!).

tank0412 said:
I disagree with this information.
From my perspective screen freezes and reboots happening due to device revision. What i mean is there are few different revisions of Zenfone 5 models.
For example, boot unlock files is compatible with first revision so second revision will get freezes.
It is not fault of bootloader unlock.
Click to expand...
Click to collapse
May be what you are saying is true. But my method solve problems for 3 zenfones that were unlocked. Please feel free to search and provide exact problem source. I think Asus company itself is in play here.. ;D
Sent from my ASUS_T00J using Tapatalk

eragon21 said:
@herecomesmaggi, I think what tank0412 says is true. I have A501CG 1.6Ghz model. First, I used the bootloader provided in the first post of rr thread. I faced screen freezes while playing COC (note: I never faced screen freeze outside games). Then, I followed the quanganh's method of copying if.bin. Screen freeze is still there, but the frequency is greatly reduced. Also, the last time I faced screen freeze I was playing fm and the fm kept playing despite screen freeze. Which means that the os itself didn't get stuck just the screen froze. What could I say from this is, there are several versions of bootloader and using the right one will solve the screen freeze problem. Or if we could find how the bootloader unlocker works.. [emoji14] May be ASUS uses parts from different manufacturers and they are somehow linked to bootloader(It seems unlikely. Just an idea as nothing else is working!).
Click to expand...
Click to collapse
If you can please refer to my earlier post where I cried for help for same problem. In COC when i searched 10-15+ villages for loot it definitely freezed. I tried with all kernels methods, windroica, zenphone blog etc etc. Then I found this method. Please follow it and install the rom as instructed then please report. May be this could help you.
P. S. I am sure it will help you.
Sent from my ASUS_T00J using Tapatalk

jiyaad1 said:
Dear maggi I too own the same device as you (same model, cpu speed and ram cap) expect I brought mine form dubai and I experience freeze issues quite often even on stock after un-locking bootloader yet I unlock mine from. 78 stock rom so I'll try your method and see what's happens :fingers-crossed:
Click to expand...
Click to collapse
Please try it, I know this will work. Mine fingers are crossed too.. I don't know technical problems but I know that this method solve freeze and random reboots of 3 zenfones that were useless after bootloader unlock.
Sent from my ASUS_T00J using Tapatalk

One question and maybe noob.
What is the difference between the unofficial bootloader unlock and the official
If i unlock with the official unlocker and after install CM it should work, or not?

herecomesmaggi said:
If you can please refer to my earlier post where I cried for help for same problem. In COC when i searched 10-15+ villages for loot it definitely freezed. I tried with all kernels methods, windroica, zenphone blog etc etc. Then I found this method. Please follow it and install the rom as instructed then please report. May be this could help you.
P. S. I am sure it will help you.
Sent from my ASUS_T00J using Tapatalk
Click to expand...
Click to collapse
okay sure. I'll try.

venturajpo said:
One question and maybe noob.
What is the difference between the unofficial bootloader unlock and the official
If i unlock with the official unlocker and after install CM it should work, or not?
Click to expand...
Click to collapse
Mine didn't work that's why i posted these steps. Hope it could work for you. No dev yet found a true cause of this mysterious freeze issue.

did you try this solution in the 16gb variant? because i think most 16gb users experience the no camera bug

YujinYuz said:
did you try this solution in the 16gb variant? because i think most 16gb users experience the no camera bug
Click to expand...
Click to collapse
Yes I have 16GB Variant and I have am not having any no camera bug.. Btw what is it.?? My asus is, 1.6Ghz,16GB, 2GB, T00J WW

herecomesmaggi said:
Yes I have 16GB Variant and I have am not having any no camera bug.. Btw what is it.?? My asus is, 1.6Ghz,16GB, 2GB, T00J WW
Click to expand...
Click to collapse
yes. my phone's specs are 1.6Ghz 16GB ROM and 2GB RAM except my model number is T00J-D

YujinYuz said:
yes. my phone's specs are 1.6Ghz 16GB ROM and 2GB RAM except my model number is T00J-D
Click to expand...
Click to collapse
So that means when u unlock bootloader camera doesn't work.. If I am right then, It shouldn't be working with any of playstore camera app either as there is no hardware detected type of situation.
Have you tried to reach asus technicals in this regard.?? Try asking them ur official bootloader unlock method.
And by the way have tried my method..?

herecomesmaggi said:
So that means when u unlock bootloader camera doesn't work.. If I am right then, It shouldn't be working with any of playstore camera app either as there is no hardware detected type of situation.
Have you tried to reach asus technicals in this regard.?? Try asking them ur official bootloader unlock method.
And by the way have tried my method..?
Click to expand...
Click to collapse
can i see a screenshot of the model number of your phone?
yes, any camera app doesnt work on my phone. i havent tried contacting asus yet.

YujinYuz said:
can i see a screenshot of the model number of your phone?
yes, any camera app doesnt work on my phone. i havent tried contacting asus yet.
Click to expand...
Click to collapse
Here it is

herecomesmaggi said:
Here it is
View attachment 3602829
Click to expand...
Click to collapse
hmm. it seems that you have a different device model than i have. no wonder i get a camera not found error.

YujinYuz said:
hmm. it seems that you have a different device model than i have. no wonder i get a camera not found error.
Click to expand...
Click to collapse
My device is T00J, WW But after flashing cyanogenmod it shows T00F as it is in its build.prop

herecomesmaggi said:
My device is T00J, WW But after flashing cyanogenmod it shows T00F as it is in its build.prop
Click to expand...
Click to collapse
oh.. okay. i guess it's still different from mine coz my model is T00J-D

I Made A Terrible Mistake!

Hello there!
So, I'm using Zenfone 5 (2G) Running on Official Lolipop
I had my phone bootlooped back in that time, then I flashed a wrong recovery version, it was KitKat version that I flashed, I got into Recovery Mode.
I tried to sideload update packages (both KitKat and Lolipop ROM) and it showed me some error like can't mount /cache (invalid arguments), I expected this as losing partition (If I'm not wrong)
And now I can't even get into droidboot at all, here is the responds from following things I do :
Recovery button combination : Works (Gets to the recovery)
Power button : Shows USB logo
Droidboot button combination : Shows manufacturer logo forever (Stuck)
But, as I said, I tried to sideload the packs and it fails...
Could someone help me? Maybe some easy way to fix this? For a note, I tried bunch of tutorials to fix my device, the last one was xFSTK thing.. I followed every single step correctly and ended up with an error.
Thanks before

kelvinvalencio said:
Hello there!
So, I'm using Zenfone 5 (2G) Running on Official Lolipop
I had my phone bootlooped back in that time, then I flashed a wrong recovery version, it was KitKat version that I flashed, I got into Recovery Mode.
I tried to sideload update packages (both KitKat and Lolipop ROM) and it showed me some error like can't mount /cache (invalid arguments), I expected this as losing partition (If I'm not wrong)
And now I can't even get into droidboot at all, here is the responds from following things I do :
Recovery button combination : Works (Gets to the recovery)
Power button : Shows USB logo
Droidboot button combination : Shows manufacturer logo forever (Stuck)
But, as I said, I tried to sideload the packs and it fails...
Could someone help me? Maybe some easy way to fix this? For a note, I tried bunch of tutorials to fix my device, the last one was xFSTK thing.. I followed every single step correctly and ended up with an error.
Thanks before
Click to expand...
Click to collapse
Try this:
Download a flashable custom rom, put the rom *.zip file in the same folder with ADB.
Go into recovery TWRP, connect your phone to your computer.
Push rom *.zip file to your phone's internal storage with this command in ADB:
push [file.zip] /sdcard/.
Then flash that rom file with TWRP.

Well, sir, how can I get into TWRP? I can't even droidboot... My recovery that I flashed was stock

deleted.

kelvinvalencio said:
Hello there!
So, I'm using Zenfone 5 (2G) Running on Official Lolipop
I had my phone bootlooped back in that time, then I flashed a wrong recovery version, it was KitKat version that I flashed, I got into Recovery Mode.
I tried to sideload update packages (both KitKat and Lolipop ROM) and it showed me some error like can't mount /cache (invalid arguments), I expected this as losing partition (If I'm not wrong)
And now I can't even get into droidboot at all, here is the responds from following things I do :
Recovery button combination : Works (Gets to the recovery)
Power button : Shows USB logo
Droidboot button combination : Shows manufacturer logo forever (Stuck)
But, as I said, I tried to sideload the packs and it fails...
Could someone help me? Maybe some easy way to fix this? For a note, I tried bunch of tutorials to fix my device, the last one was xFSTK thing.. I followed every single step correctly and ended up with an error.
Thanks before
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557

tank4k said:
can u open droid boot?
Click to expand...
Click to collapse
No

paktepu said:
Try this
http://forum.xda-developers.com/zenfone-5/general/zenfonetoolkit3-24-40-87-t3406557
Click to expand...
Click to collapse
Got your post.. Didn't download..
I want to make sure one thing.. Does this work on TW SKU? Because It's writen that your file is integrated with WW SKU

kelvinvalencio said:
Got your post.. Didn't download..
I want to make sure one thing.. Does this work on TW SKU? Because It's writen that your file is integrated with WW SKU
Click to expand...
Click to collapse
Basicly the procedure to debrick is same. You need to load bootloader temporary since you have a broken droidboot including your partition. I already have same problem with you before.
Yeah its different, you cant use ww to fix this. Find on official zentalk tw forum for complete detail. Shakalaca post that.
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
Basicly the procedure to debrick is same. You need to load bootloader temporary since you have a broken droidboot including your partition. I already have same problem with you before.
Yeah its different, you cant use ww to fix this. Find on official zentalk tw forum for complete detail. Shakalaca post that.
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks a lot!
Anyway, I've got few questions left..
Yesterday, I did download zip files from this debrick thread (Should be familiar with you) http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
My question is, does this work the same as your files? And, could I do something about it? Like re-use by recycle again the files I've downloaded with something that might help my phone? You know.. 900 MB is not something very small for me.. And maybe I could download separated files that is required.. And make the use of Debrick files I downloaded?
And.. May I have the link of Shakalaca's post, if you don't mind? Thanks a lot, like a lot!

kelvinvalencio said:
Thanks a lot!
Anyway, I've got few questions left..
Yesterday, I did download zip files from this debrick thread (Should be familiar with you) http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
My question is, does this work the same as your files? And, could I do something about it? Like re-use by recycle again the files I've downloaded with something that might help my phone? You know.. 900 MB is not something very small for me.. And maybe I could download separated files that is required.. And make the use of Debrick files I downloaded?
And.. May I have the link of Shakalaca's post, if you don't mind? Thanks a lot, like a lot!
Click to expand...
Click to collapse
Yes you can do manual from that link but from step 8 download tw.zip.
Cek pm for shakalaca
Sent from my ASUS_T00F using XDA-Developers mobile app

paktepu said:
Yes you can do manual from that link but from step 8 download tw.zip.
Cek pm for shakalaca
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey um, I followed the Debrick one. The problem comes when I ran Debrick.dat, from the Cloverview mode (Press vol down and connect to pc). While the Debrick program runs, the phone "boots". Shows up USB logo and it goes red. Few seconds after then, the program closes, leaves the phone on red USB logo. Is this something normal?
Btw that link can't help.
Sent from my EG680 using XDA-Developers mobile app

Didn't you try reboot from bootloader. If it solves, it means normal. You must thank to intel for this problem.
---------- Post added at 09:07 PM ---------- Previous post was at 09:03 PM ----------
DogeLordTR said:
Didn't you try reboot from bootloader. If it solves, it means normal. You must thank to intel for this problem.
Click to expand...
Click to collapse
OK, I'm really stupid, sorry for time waste.

paktepu said:
Yes you can do manual from that link but from step 8 download tw.zip.
Cek pm for shakalaca
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Hey um, I have contacted Shakalaca and until today I have not retrieved any reply. This problem haven't been solved. Any idea? I see you know a lot about this, and you're very popular arround here.

This happened with my Asus Zenfone 5 (T00j). Tried every solution available on net without sucess, finally took it to Service Center and they had to replace the motherboard

[Solved] Exploring LG G4 Root-Injection, exFAT, VoLTE issue ... H81210n Rogers/Fido

*See the Addendum at the bottom of this OP for The Solve*
This thread has arisen from a particular issue that was originally thought to have arisen* by flashing a pre-rooted system image that was prepared following the method outlined by Senior Member hackarchive in "Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks" (https://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586).
*later proved by Senior Member steadfasterX to be an erroneous assumption.
The issue: The H812 LG G4 (that has an un-lockable bootloader) that came from the carrier (Canada's Roger's/Fido) with Marshmallow (H81220x) installed. It was rolled back to Lollipop H81210h originally with the pre-rooted H81210n system image flashed after - the reason: both the stock and pre-rooted 'h' versions did not have the last stagefright vulnerability patch whereas the 'n' version did, hence an added level of security. However, no one had a confirmed Roger's/Fido stock H81210n kdz (Rogers/Fido is the only carrier in Canada that has the VoLTE option included and operational for the LG G4) that anybody could find a link to and when an exFAT formatted SD card was put in the pre-rooted 'n' version, it failed to recognize the format (no problem with FAT32) whereas it was recognized in the rooted earlier released 'h' version. The 4gb restriction size of FAT32 did not allow the backup of the system image with Senior Member steadfasterX's "TWRP-in-FiSH" (https://forum.xda-developers.com/g4/development/locked-twrpinfish-locked-g4-devices-t3573048) to the external sd card given the FAT32 size restriction. The exFAT recognition issue originally appeared to have arisen with the pre-rooted 'n' version when the missing original stock kdz was installed through the refurbish method with LGUP-NEW without an SD card installed or when the original system image was extracted OR, as steadfasterX has suggested, it was originally for a phone with a different kernel.
At the suggestion of steadfasterX and thanks to his work on this issue, the effort to reverse-engineer and revert to stock from the root-injection method itself has been undertaken. The work is all his, the testing to date and soft-bricking getting to this point, are mine.
Make no mistake ... this is a work-in-progress and soft-bricks and other risks, always a possibility
What you have here is a link to steadfasterX's latest revision to help unravel this issue that should not change anything if the DEBUG setting is left as it is: DEBUG=1. Follow his instructions exactly. I have run this version with DEBUG=1 with absolutely no problems and no issues rebooting after - no actual changes were made to the phone when the DEBUG=1 mode was used.
Note: Changing the 1 to a 0 will allow actual execution of the script and is not advised at this time*.
* Not advised at all as it will = Soft Brick.
Refer to the following link: https://forum.xda-developers.com/showpost.php?p=72837723&postcount=343
but please, post to this thread only if you are interested in helping/testing/solving or have any questions etc.
Thanks.
S.
Addendum: Credit for The Solve ...
Full credit for the solve goes to ReeS86- refer to his post @ReeS86
Special Thanks to all the work by steadfasterX he put into helping us get to this point.
For a quick and easy method to get an exFAT formatted SD card recognized in the pre-rooted Rogers/Fido H81210n system image: see the Addendum in my post @sdembiske

yea thats better here then there
ok lets see where it goes...
happy bricking
.

steadfasterX said:
yea thats better here then there
ok lets see where it goes...
happy bricking .
Click to expand...
Click to collapse
Here's a link to the DEBUG=1 log from revert_root_injection.sh v0.2:
https://paste.omnirom.org/view/be1a8f21
No issues/problems in executing or rebooting from the script in DEBUG=1 mode. :good:

sdembiske said:
Here's a link to the DEBUG=1 log from revert_root_injection.sh v0.2:
https://paste.omnirom.org/view/be1a8f21
No issues/problems in executing or rebooting from the script in DEBUG=1 mode. :good:
Click to expand...
Click to collapse
ok!
so now pls gimme this on your rooted device:
boot in TWRP
Code:
adb shell
mount /system <-- may complain that it is already mounted. if so ignore ;)
tar cvzf /tmp/init.tar.gz /system/etc/init.d/
exit
adb pull /tmp/init.tar.gz .
then e.g. upload the init.tar.gz here as a attachment .
.

steadfasterX said:
ok!
so now pls gimme this on your rooted device:
boot in TWRP
Code:
adb shell
mount /system <-- may complain that it is already mounted. if so ignore ;)
tar cvzf /tmp/init.tar.gz /system/etc/init.d/
exit
adb pull /tmp/init.tar.gz .
then e.g. upload the init.tar.gz here as a attachment ..
Click to expand...
Click to collapse
Here you go.

sdembiske said:
Here you go.
Click to expand...
Click to collapse
ok so far so good.
now it is "safe" to DEBUG=0 ..
give it a try :fingers-crossed:
and upload the log from the ext sd afterwards again..
.

steadfasterX said:
ok so far so good.
now it is "safe" to DEBUG=0 ..
give it a try :fingers-crossed:
and upload the log from the ext sd afterwards again...
Click to expand...
Click to collapse
No go this time either. Softbricked same as last time on the reboot - however, this time TWRP didn't freeze up and allowed the reboot from inside. Pulling the battery and trying normal power up gave the same result. No sound and couldn't get past the spinning lg logo. It'll take me a bit of time to get up and running again.
Here's the link to the log: https://paste.omnirom.org/view/19951ee0

I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.

ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
Good idea. I know some of the stock Motorola LTE versions were updated with the first stagefright vulnerability patch and it was able to be ported over into to copies of stock versions that didn't have it. Refer to the Miscellaneous section in the following thread https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
You may want to check with recognized contributor lost101, author of that thread for any suggestions.
The other approach might be to try and get the Roger's-Fido/VoLTE app/settings off the the 'h' version and see if they can be incorporated into the stock 'n' version that does handle exFAT but doesn't have VoLTE as it is carrier specific, although, I think your approach might bring more fruitful results quicker.

ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
sdembiske said:
Good idea. I know some of the stock Motorola LTE versions were updated with the first stagefright vulnerability patch and it was able to be ported over into to copies of stock versions that didn't have it. Refer to the Miscellaneous section in the following thread https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
You may want to check with recognized contributor lost101, author of that thread for any suggestions.
The other approach might be to try and get the Roger's-Fido/VoLTE app/settings off the the 'h' version and see if they can be incorporated into the stock 'n' version that does handle exFAT but doesn't have VoLTE as it is carrier specific, although, I think your approach might bring more fruitful results quicker.
Click to expand...
Click to collapse
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
.
Sent from my LG-H815 using XDA Labs

All this trouble because no bootloader unlock... what a shame
---------- Post added at 10:27 AM ---------- Previous post was at 10:21 AM ----------
ReeS86 said:
I'm curious what security fixes and other fixes were present between the h and n versions of the Rogers H812 system software. It seems to me a good option may be to install 10h KDZ and then root, then copy any libstagefright files needed from the 10n KDZ and check to see if the vulnerabilities are fixed. I might try this out because I had no issues with the 10h firmware including the exFAT working correctly while rooted.
Click to expand...
Click to collapse
What is the difference between H and N versions?

steadfasterX said:
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Will try and get to it sometime over the long weekend that we have coming up here and give it a shot as well as providing the DEBUG=1 log on a v10h .
Thanks again.

sdembiske said:
Will try and get to it sometime over the long weekend that we have coming up here and give it a shot as well as providing the DEBUG=1 log on a v10h .
Thanks again.
Click to expand...
Click to collapse
You may could ask the maintainer of :
https://forum.xda-developers.com/g4/development/h815-freedom-rom-t3630056/post72866870
He made an installer for his ROM which let you select VoLTE so he may now what is needed to activate it. I know it's for the h815 but it should be similar..
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Well my first try on this would be:
Backup v10n
Flash v10H
Restore v10n system image only
See what happens. Normally there are low chances that this brick anything but there are still no guarantees..
Btw I would like to see a DEBUG=1 run on a v10h..
I wonder if there are diffs in the root injection..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
As suggested, here are the revert_root_injection logs (x2 - DEBUG =1 and DEBUG=0), plus the TWRP recovery log of system image restore of the 'n' version from 'h' internal.
Same problem with revert-root-injection when the DEBUG option was set to "0" to execute - i.e., soft brick ... lol.
And, perhaps not unexpected, the exFat formatted card was still not recognized but what did surprise me is that none of my settings, apps etc., were restored on the 'n' system image restore after.
Link to logs: https://gist.github.com/sdembis/89de74e401def3ed0e091c565a19e0e9
I then restored all (excluding system image) from my backup in external after the first restore attempt - it failed on the Data restore but everything was back to normal from what I could tell on the reboot.
PS: I pm'ed both you and ReeS86 the response from the rom author you suggested I contact re: the VoLTE install. He was very helpful and sounds like a good guy. Thanks for the suggestion. Much appreciated.
Best,
S.

sdembiske said:
As suggested, here are the revert_root_injection logs (x2 - DEBUG =1 and DEBUG=0), plus the TWRP recovery log of system image restore of the 'n' version from 'h' internal.
Same problem with revert-root-injection when the DEBUG option was set to "0" to execute - i.e., soft brick ... lol.
And, perhaps not unexpected, the exFat formatted card was still not recognized but what did surprise me is that none of my settings, apps etc., were restored on the 'n' system image restore after.
Link to logs: https://gist.github.com/sdembis/89de74e401def3ed0e091c565a19e0e9
I then restored all (excluding system image) from my backup in external after the first restore attempt - it failed on the Data restore but everything was back to normal from what I could tell on the reboot.
PS: I pm'ed both you and ReeS86 the response from the rom author you suggested I contact re: the VoLTE install. He was very helpful and sounds like a good guy. Thanks for the suggestion. Much appreciated.
Best,
S.
Click to expand...
Click to collapse
Hm the following is not clear for me:
You have restored the system image of N to H as suggested. Ok. And then? Does it soft brick as well?
the recovery log shows the backup only.. But it wouldn't be helpful anyways or do you had an error while restoring?
Yes using the revert script on H was 99% sure that it soft bricks as well that's why I said DEBUG=1 but it seems u like it so.. nvm
Thx to the log It looks like the root method between H and N is not different btw..
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Hm the following is not clear for me:
You have restored the system image of N to H as suggested. Ok. And then? Does it soft brick as well?
the recovery log shows the backup only.. But it wouldn't be helpful anyways or do you had an error while restoring?
Yes using the revert script on H was 99% sure that it soft bricks as well that's why I said DEBUG=1 but it seems u like it so.. nvm
Thx to the log It looks like the root method between H and N is not different btw..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
No, neither of the restores resulted in a soft brick. The first restore of the 'n' backed up system image (from internal) went fast with no issues but didn't have the apps and settings that I backed up - that is the TWRP log I attached in my last post. The 2nd restore (all except system image from external), done right after the first, failed on restoring Data but I was able to reboot from within TWRP and all settings and apps were back as they should have been.
Here is the link to that log: https://gist.github.com/sdembis/160047faa4b22717edf36658e5e42ea7
Any ideas as to why the reversion is failing and whether it might be able to be overcome?
Thanks again,
S.
.

sdembiske said:
No, neither of the restores resulted in a soft brick. The first restore of the 'n' backed up system image (from internal) went fast with no issues but didn't have the apps and settings that I backed up - that is the TWRP log I attached in my last post. The 2nd restore (all except system image from external), done right after the first, failed on restoring Data but I was able to reboot from within TWRP and all settings and apps were back as they should have been.
Here is the link to that log: https://gist.github.com/sdembis/160047faa4b22717edf36658e5e42ea7
Any ideas as to why the reversion is failing and whether it might be able to be overcome?
Thanks again,
S.
.
Click to expand...
Click to collapse
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?
.

steadfasterX said:
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?.
Click to expand...
Click to collapse
Sorry, I didn't check it because the other problem, namely exFAT was no longer recognized was still present. I'll re-check everything today.

steadfasterX said:
The idea of restoring the system image (ONLY this!) from N to H :
this was a test to see if you have the VoLTE working afterwards - was VoLTE working?.
Click to expand...
Click to collapse
Thinking this through a little - as the rooted Roger's/Fido 'h' version does have VoLTE, I would expect it to have VoLTE when the 'n' version system image with VoLTE is restored over that 'h' version. I am going to try instead taking the 'n' version without VoLTE but recogning exFat that I've rooted and restore the system image from the pre-rooted 'n' version with VoLTE but not recognizing exFat, to see if VoLTE is present. If it is, I suspect that exFAT will still not be recognized as it was with the retored 'n' version over the 'h' version, I would only end up with the same problem I have now with the pre-rooted 'n' version - VoLTE with no exFAT recognition.
Or, did you mean restoring the rooted 'n' version system image without VoLTE over the rooted 'h' version with VoLTE and exFAT recognition?

I was able to loop mount both the bell H812n and Rogers H812n rooted system images and run KDiff3 on both of the root directories. It seems there are a few config files here and there that reference VoLTE as well as the odd missing file between the two. I'm going to keep digging maybe I'll find something about ExFAT as well.
Edit: Looks like the rooted system image posted to the Canadian G4 thread is from Videotron in Quebec. Still don't see anything about ExFAT...

Lg V20 stuck on Your device is corrupt. Visit link g.co/abh

Yesterday my v20 started restarting from nowhere. I had this issue before too. I never tried to root my phone never changed recovery nothing its 100% stock. After those restarts i tried to format it with lgup and between the process phone restarted again and now i am in to this annoying boot loop where i can only access fastboot. I cant access download mode nothing else my phone doesn't even turn on. Please help me to get back to normal. I have his 400$ brick laying around, :crying: :crying:

https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222

My phone doesn't boot in download mode.
XblackdemonX said:
https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
Click to expand...
Click to collapse
I have access to only fastboot mode where oem unlock is unavailable and usb debugging is also unavailable.:crying:

If your phone wasn't rooted, then your NAND has become corrupt. LG has extended the warranty due to bootloops. Open a ticket with them.
-- Brian

Any way to fix that?
runningnak3d said:
If your phone wasn't rooted, then your NAND has become corrupt. LG has extended the warranty due to bootloops. Open a ticket with them.
-- Brian
Click to expand...
Click to collapse
I live in India And I imported phone from USA it's a T Mobile Unit. What are the options? Anything can be done at hardware level ? Without changing the entire motherboard?

No. Order an H918 with a cracked screen and clean IMEI off of eBay (actually it doesn't even have to have a clean IMEI, you can use the one from your current phone), and replace the board.
-- Brian

runningnak3d said:
No. Order an H918 with a cracked screen and clean IMEI off of eBay (actually it doesn't even have to have a clean IMEI, you can use the one from your current phone), and replace the board.
-- Brian
Click to expand...
Click to collapse
Board replacement is the only solution ?
I am in a similar situation.
having tried all the possible ways mentioned here in this forum, I am left with no other options
though I have a working download mode
tried flashing the ROM from other variants like US996 10F using LGUP Patched [The Rom flashed100% and boots up well, but FC in 10sec before i could do anything.
Please help!
Thank you

uccfar said:
Board replacement is the only solution ?
I am in a similar situation.
having tried all the possible ways mentioned here in this forum, I am left with no other options
though I have a working download mode
tried flashing the ROM from other variants like US996 10F using LGUP Patched [The Rom flashed100% and boots up well, but FC in 10sec before i could do anything.
Please help!
Thank you
Click to expand...
Click to collapse
runningnak3d said:
If your phone wasn't rooted, then your NAND has become corrupt. LG has extended the warranty due to bootloops. Open a ticket with them.
-- Brian
Click to expand...
Click to collapse
The above is still true, if this didnt happen immedately after/during rooting/flashing something or using a dd command (while also rooted) your board is dying and you need a new one.

V20 I can't update my V20
Hi, I have a v20 h918 with twrp installed and I can't update the Android version, I get an android lying with an open cover and it says below: error. Can you help me please? Thank you

17promise28 said:
Hi, I have a v20 h918 with twrp installed and I can't update the Android version, I get an android lying with an open cover and it says below: error. Can you help me please? Thank you
Click to expand...
Click to collapse
@princedede on telegram let's see if we can fix it

Thank you ! :good:

Need a Loader File to unbrick Moto G7.

Hi,
I accidentally applied an OTA in my rooted device and then Did somethings that caused a brick. Now my device is detected in the PC as Port 3 (Qualcomm HS-USB QDLoader 9008) and since Motorola is
not providing the Blankflash file needed to rescue the device, the only way to rescue my device is to generate a Loader.img from any of the good people who are using a Motorola g7.
Somebody Please help me out.
I will post the steps below.
1. Get another exact variant of your device and INSERT an SD Card on it. The device chipset must be the same. Thus, if your device (bricked) is MSM8269, the required device CPU has to be MSM8269, too.
2. Root the working (exact variant) device and install Terminal Emulator on it.
3. Download and install Busybox on the device. You may download Busybox from here
4. Once BusyBox is installed, launch/open it and run/install its dependencies/files by clicking on the appropriate key.
5. Now, launch/open Terminal Emulator on the device and follow these procedures:
a. On Terminal EmulatorType:
Code:
su
and hit/tap the Enter key. You will be prompted to GRANT Terminal emulator a Root Access, click GRANT.
b. Then, type:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
and hit/tap the Enter key.
6. Wait few minutes or until Terminal Emulator completes the process.
7. Now, check the Root Folder/Directory of the SD Card inserted on the phone. You will notice that a file named Loader.img has been created.
GOOD! That's your Qualcomm device Unbrick file.
I have referred this article here
https://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html?m=1
Someone please be kind enough to post a Loader for Moto g7 as there are many people who needs it.
Thanks in advance.

Here is my Loader.img for:
Model Number (SKU): XT1962-1
Baseband Version: M632_12.52.01.86R RIVER_NA_CUST
Bootloader: MBM-2.1-river_retail-b89272e-190401
Kernel: 4.9.112-perf+ #1 Mon Apr 1 21:51:39 CDT 2019
Build #: PP029.114-16-5-2
https://drive.google.com/open?id=1Bb45SC7YU2NnyIlGsHJKbbnq7mKHQ1aj
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: a1a03e2225dd723c5c3549568ad7f4b1
Good luck!

skuppej said:
Here is my Loader.img for:
Model Number (SKU): XT1962-1
Baseband Version: M632_12.52.01.86R RIVER_NA_CUST
Bootloader: MBM-2.1-river_retail-b89272e-190401
Kernel: 4.9.112-perf+ #1 Mon Apr 1 21:51:39 CDT 2019
Build #: PP029.114-16-5-2
https://drive.google.com/open?id=1XYk5ulnZO_k7srEAo76FsBHG9DNrbYS6
Good luck!
Click to expand...
Click to collapse
Thanks a lot skuppej. You saved my phone. Let me try with this file and post the results for other people here.:good::good::fingers-crossed::fingers-crossed::fingers-crossed::victory::victory::victory:
Thanks a lot again for spending the time needed to extract the Loader file. Only if there were more people like you.

thanks for the loader.img - im not unbricked yet
Thank you for taking the time to generate the loader.img file skuppej. (and Phillen13 for posting a possible solution)
I hard-bricked my XT1962-1 with magisk somehow, and it only shows up in windoze dev manager as the qualcomm 9008 com3:
i used rufus and then diskimagerev2 to write the image to a 8GB card, but then had no luck getting the phone to do anything using the buttons. i will try to write the loader.img using my linux box and see what happens.
the referenced article is a bit weak when it comes to the step of booting the loader.img and i have not been able to find any secondary reference for using a loader.img as a process for recovering.
i would like to know what the file size (and ideally a MD5 hash) for the loader.img its possible that the 165M file on GD is too small?
i tried a 16GB card and imaged with disk imager in ubuntu, inserted card into phone, and could not see any action no lights etc, by holding down the power button for various time lengths, then holding down power and vol down buttons.. the only response i discern is the windows sound of a USB device being inserted three tones down, then recognised three tones up. (Qualcomm HS-USB QDLoader 9008 in DevMan as COM3
to respond below, yes i used unofficial TWRP then magisk to patch boot.img and got a bunch of red errors...

Phillen13 said:
Hi,
I accidentally applied an OTA in my rooted device and then Did somethings that caused a brick..
Click to expand...
Click to collapse
May I ask how you successfully rooted your Moto G7?
I successfully unlocked my bootloader but when I used Magisk to patch the boot.img I got stuck in bootloops that finally required a phone reset to get out of.
So, how did you root your G7? Did you use the unofficial twrp? (As far as I know there's no official twrp yet).
Thanks.

Phillen13 said:
Thanks a lot skuppej. You saved my phone. Let me try with this file and post the results for other people here.:good::good::fingers-crossed::fingers-crossed::fingers-crossed::victory::victory::victory:
Thanks a lot again for spending the time needed to extract the Loader file. Only if there were more people like you.
Click to expand...
Click to collapse
No problem! But I am still dubious. Did this actually work for you? I've been in a pickle and had to use a loader.img file for a previous phone and it worked, but I just want to make sure what I produced is good.
khawks said:
Thank you for taking the time to generate the loader.img file skuppej. (and Phillen13 for posting a possible solution)
I hard-bricked my XT1962-1 with magisk somehow, and it only shows up in windoze dev manager as the qualcomm 9008 com3:
i used rufus and then diskimagerev2 to write the image to a 8GB card, but then had no luck getting the phone to do anything using the buttons. i will try to write the loader.img using my linux box and see what happens.
the referenced article is a bit weak when it comes to the step of booting the loader.img and i have not been able to find any secondary reference for using a loader.img as a process for recovering.
i would like to know what the file size (and ideally a MD5 hash) for the loader.img its possible that the 165M file on GD is too small?
i tried a 16GB card and imaged with disk imager in ubuntu, inserted card into phone, and could not see any action no lights etc, by holding down the power button for various time lengths, then holding down power and vol down buttons.. the only response i discern is the windows sound of a USB device being inserted three tones down, then recognised three tones up. (Qualcomm HS-USB QDLoader 9008 in DevMan as COM3
to respond below, yes i used unofficial TWRP then magisk to patch boot.img and got a bunch of red errors...
Click to expand...
Click to collapse
I will try making another loader.img and checking/comparing the hashes. I feel you man!
maybeme2 said:
May I ask how you successfully rooted your Moto G7?
I successfully unlocked my bootloader but when I used Magisk to patch the boot.img I got stuck in bootloops that finally required a phone reset to get out of.
So, how did you root your G7? Did you use the unofficial twrp? (As far as I know there's no official twrp yet).
Thanks.
Click to expand...
Click to collapse
For me, on both G7's I've owned, I updated to the latest OTA, unlocked the BL, installed unofficial TWRP, and then just flashed magisk.zip in TWRP. Crazy to me that other people are running into issues with this! My phone is US Retail, purchased directly from Motorola.
---------- Post added at 12:07 PM ---------- Previous post was at 11:12 AM ----------
I re-generated the loader.img and compared the MD5 and it was the same as the last one I generated.
Updated my link & added the MD5.

skuppej said:
No
For me, on both G7's I've owned, I updated to the latest OTA, unlocked the BL, installed unofficial TWRP, and then just flashed magisk.zip in TWRP. Crazy to me that other people are running into issues with this! My phone is US Retail, purchased directly from Motorola.
Click to expand...
Click to collapse
I'm one of those who ran into loads of trouble following the instructions from
https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
I was wary of using the unofficial twrp but will do so now. Thanks.
My bootloader is already unlocked but when I needed to reset the phone to get out of the bootloops I lost my ota system update. Is there a way to flash the system updates after rooting?

Yeah I don't recommend following those older instructions...the latest magisk.zip flashes just fine in TWRP....
When it comes to it, I'm hoping I won't have any trouble flashing the latest OTA from https://mirrors.lolinet.com/firmware/moto/river/official/RETAIL/ or from LMSA (I'd probably try this first..since it seems like it would be more 'official')
Right now I am on PP029.114-16-5-2 which I think is the latest...at least OTA didn't want to go any further before I rooted etc.
If you are having trouble with OTA and you don't mind losing your data, I'd do a full magisk uninstall, re-lock of the bootloader/flash using LMSA files.

loader.img failing MD5
I downloaded loader.img using this link: (Thank you skuppej)
xxxx://drive.google.com/file/d/17Wd...GkJygj25PjEYJU - hmm cant post links yet thats ridiculous
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175
actually downloaded it twice and both times failed MD5 hash:
my check....a1a03e2225dd723c5c3549568ad7f4b1
so i added the file to my google drive (assuming that GD uses hash checking, pretty sure it does with file & sync). I am now figuring out how to generate MD5 data on my google drive to see if its good. OK google drive MD5 fails as well.
i have ran into this kind of thing before, skuppej would you be willing to put the loader.img into a container such as a .zip file and out that on your GD please?

khawks said:
I downloaded loader.img using this link: (Thank you skuppej)
xxxx://drive.google.com/file/d/17Wd...GkJygj25PjEYJU - hmm cant post links yet thats ridiculous
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175
actually downloaded it twice and both times failed MD5 hash:
my check....a1a03e2225dd723c5c3549568ad7f4b1
so i added the file to my google drive (assuming that GD uses hash checking, pretty sure it does with file & sync). I am now figuring out how to generate MD5 data on my google drive to see if its good. OK google drive MD5 fails as well.
i have ran into this kind of thing before, skuppej would you be willing to put the loader.img into a container such as a .zip file and out that on your GD please?
Click to expand...
Click to collapse
That's odd!
OK NP, I've updated https://forum.xda-developers.com/showpost.php?p=79702551&postcount=2 with the .zip and the MD5 for both.
I was able to download it/extract/get matching MD5 sums from an external location, so it should all be good..

skuppej said:
No problem! But I am still dubious. Did this actually work for you? I've been in a pickle and had to use a loader.img file for a previous phone and it worked, but I just want to make sure what I produced is good..
Click to expand...
Click to collapse
I have not tried flashing it till now. Been busy with work. I will let you know once I have finished. Thanks for the updated .zip file .You are really a very helpful person.

trying loader.img
Phillen13:
Did you find time to try the loader.img file?
The MD5 hash for the .zip file matches, but I am having trouble getting the loader.img file itself to agree with:
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175 ----my check....a1a03e2225dd723c5c3549568ad7f4b1
It would be helpful to have more members messing with this.
K.

khawks said:
Phillen13:
Did you find time to try the loader.img file?
The MD5 hash for the .zip file matches, but I am having trouble getting the loader.img file itself to agree with:
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: ec2ff9fd90ba8869a1cc5d9021d8f175 ----my check....a1a03e2225dd723c5c3549568ad7f4b1
It would be helpful to have more members messing with this.
K.
Click to expand...
Click to collapse
Hi khawks. I just generated another and checked the MD5 and it is actually a1a03e2225dd723c5c3549568ad7f4b1, the same as you have checked.
So I guess the new Loader file in the zip is the correct one..extremely sorry for the wild goose chase! I must have confused it with the old one

anyone else had luck getting loader.img to boot?
I have not been able to get my G7 to boot (holding vol down and power keys) (or all three) using a UHS-1 8GB card or a class 4 16gb card with loader.img on it.
Anyone else have any luck?

skuppej said:
Here is my Loader.img for:
Model Number (SKU): XT1962-1
Baseband Version: M632_12.52.01.86R RIVER_NA_CUST
Bootloader: MBM-2.1-river_retail-b89272e-190401
Kernel: 4.9.112-perf+ #1 Mon Apr 1 21:51:39 CDT 2019
Build #: PP029.114-16-5-2
https://drive.google.com/open?id=1Bb45SC7YU2NnyIlGsHJKbbnq7mKHQ1aj
MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e
MD5: a1a03e2225dd723c5c3549568ad7f4b1
Good luck!
Click to expand...
Click to collapse
So I was able too boot using this Loader file..... but I'm stuck from that point. The bootloader shows as locked, won't allow me to unlock it, won't allow me to boot anything, and most fastboot commands return FAILED (remote failure). Does anyone have any advice on how to proceed from this point?

TerrestrialHost said:
So I was able too boot using this Loader file..... but I'm stuck from that point. The bootloader shows as locked, won't allow me to unlock it, won't allow me to boot anything, and most fastboot commands return FAILED (remote failure). Does anyone have any advice on how to proceed from this point?
Click to expand...
Click to collapse
Could you please post specific into such as the size and class of your SD card you used to put the loader.img on?

khawks said:
Could you please post specific into such as the size and class of your SD card you used to put the loader.img on?
Click to expand...
Click to collapse
Yeah, I used a 128GB Class 10 which I had empty. I used this software to put the image on the SD card: https://www.balena.io/etcher/
I then completely turned my phone off, and then booted using Power/VolDown with the card inserted.

I'm wondering if the BL version needs to match? OTAs I've noticed do change BL versions..
I'll give it a shot myself if I can find a spare microsd card somewhere

skuppej said:
I'm wondering if the BL version needs to match? OTAs I've noticed do change BL versions..
I'll give it a shot myself if I can find a spare microsd card somewhere
Click to expand...
Click to collapse
I think there's a good possibility that my problem is related to the bootloader version. I had just flashed the PPOS29.114-16-7-2 version stock rom.
Anyone here have that version, and might be willing to create a Loader.img file? Hell, I'd appreciate it enough to send them some bitcoin in gratitude, or whatnot.

TerrestrialHost said:
I think there's a good possibility that my problem is related to the bootloader version. I had just flashed the PPOS29.114-16-7-2 version stock rom.
Anyone here have that version, and might be willing to create a Loader.img file? Hell, I'd appreciate it enough to send them some bitcoin in gratitude, or whatnot.
Click to expand...
Click to collapse
I would help if I know how.
I just checked and I have PPO29.114-16-7-2 installed. Note that it is PPO29 not "PPOS29". Mine has no S in case that makes a difference.