Database Users

XT1625 (Non-Prime Exclusive) only reboots into TWRP Recovery

Hello all,
Apologies for some brevity. Wrote a long, overly-detailed post before my browser crashed and left me frustrated as hell. I'll still try to be clear with my problem and my device information.
The Problem
During a trial-and-error process of getting my G4 (2016) unlocked, flashed, and rooted I've ended up in an odd predicament. The phone will not boot straight into Android-- it has to explicitly enter the Bootloader and be told to START. Otherwise (either by reboot or by powering on from off) it will enter the TWRP recovery. I don't know enough about the boot process to speculate as to why this is happening, but I can assume it's something I've done incorrectly during my myriad of errors on the process.
Device Information (Fastboot)
Code:
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.45R ATHENE_RETUSA_CUST
Product/Variant: athene_13mp XT1625 16GB P2A
Serial Number: ZY223CKDPQ
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
Console [NULL]: null
Battery OK (Charging)
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
System Unlock/Recovery/Root Summary
Bootloader has been unlocked with Official Motorola Unlocker Tool
TWRP Recovery flashed successfully (downloaded from twrp_athene_20160526.img)
Bootloader Warning Message overwritten (tried several logo.bin before finding a good one)
SuperSu installed using the Guide on rooting w/ TWRP and SuperSu via MANDATORY SYSTEMLESS ROOT.
Can anyone speculate and help me figure out what the issue is with this phone? I can't find stock firmware for the XT1625 yet or I would most definitely be willing to wipe everything, and start from scratch to experiment with the issue. I am also very foolish in that I did not IMMEDIATELY make a backup of the device upon successful TWRP flash, but did shortly after-- no backups I can restore from will fix this issue.
Thanks,
jwarner112

volume button sticking?

hi jwarner112,
if you have successfully bootloader unlocked your phone, you can enter fastboot mode of your phone by pressing both power+volume down button at the same time. but before you do this, you need to make sure you install the following items on your computer:
make sure to install the latest motorola drivers on your computer. here is the link to the drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
after installing the latest motorola drivers, download and install rsdlite for windows(latest version 6.2.4). here is the link to the latest rsdlite:
http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
finally download the latest stock firmware for motorola xt1625 non-prime exclusive (athene) from here:
http://rootjunkysdl.com/files/Moto%20G%204th%20Gen%20XT1625/Firmware/ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip.
After downloading this firmware, put your phone in fastboot mode by pressing on power+volume down button at the same time. once the phone enters into fastboot mode, now plug the device into your computer via usb.
now open the latest version of rsdlite on your computer and click on "show device". it should detect your device in fastboot mode, which is necessary to flash the stock firmware file which you have downloaded. click on the "..." button in rsdlite to browse to the stock firmware file and once you find it (make sure you open the file while it is in ".zip" format), decompress and flash it. Remember, this will wipe everything on your phone and will be more like a complete factory data reset.
Now the flashing process should be going on and once it is over, you will restore everything back to normal. Note that bootloader will still be unlocked, but root will gone and twrp recovery will be gone. Like before, flash your twrp, but before you do a root of your phone make a complete backup of your phone in twrp recovery so that you have a good place to start if root goes bad.
Also make sure when you install root, use the latest version 2.76. I accidentally installed the older versions of supersu, which didnt support systemless root and ended up soft bricking my phone. Here is the link to the latest version of root that is compatible with systemless root on the moto G4:
http://download.chainfire.eu/supersu-stable
Prior to flashing supersu, make sure you go to the adb terminal in twrp and type in the systemless root command so that it will force a systemless root installation of supersu. In order to do this, in TWRP go to Advanced and open the Terminal, and in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded (version 2.76 or higher) and swipe to flash it and reboot.
Once all of this is done, I hope you have a working phone with bootloader unlocked, twrp recovery, and systemless root. if you still have problems attaining this features in your phone, please let us know! otherwise, hit me a thanks!
Good Luck!

mikeruss said:
volume button sticking?
Click to expand...
Click to collapse
I don't believe this is the issue because I've got two identical phones with the same behavior. It seems intuitive to me that the error lies in the process.

fastboot oem fb_mode_clear
Should fix the issue.

aznindguy4u said:
hi jwarner112,
if you have successfully bootloader unlocked your phone, you can enter fastboot mode of your phone by pressing both power+volume down button at the same time. but before you do this, you need to make sure you install the following items on your computer:
make sure to install the latest motorola drivers on your computer. here is the link to the drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
after installing the latest motorola drivers, download and install rsdlite for windows(latest version 6.2.4). here is the link to the latest rsdlite:
http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
finally download the latest stock firmware for motorola xt1625 non-prime exclusive (athene) from here:
http://rootjunkysdl.com/files/Moto%20G%204th%20Gen%20XT1625/Firmware/ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml.zip.
After downloading this firmware, put your phone in fastboot mode by pressing on power+volume down button at the same time. once the phone enters into fastboot mode, now plug the device into your computer via usb.
now open the latest version of rsdlite on your computer and click on "show device". it should detect your device in fastboot mode, which is necessary to flash the stock firmware file which you have downloaded. click on the "..." button in rsdlite to browse to the stock firmware file and once you find it (make sure you open the file while it is in ".zip" format), decompress and flash it. Remember, this will wipe everything on your phone and will be more like a complete factory data reset.
Now the flashing process should be going on and once it is over, you will restore everything back to normal. Note that bootloader will still be unlocked, but root will gone and twrp recovery will be gone. Like before, flash your twrp, but before you do a root of your phone make a complete backup of your phone in twrp recovery so that you have a good place to start if root goes bad.
Also make sure when you install root, use the latest version 2.76. I accidentally installed the older versions of supersu, which didnt support systemless root and ended up soft bricking my phone. Here is the link to the latest version of root that is compatible with systemless root on the moto G4:
http://download.chainfire.eu/supersu-stable
Prior to flashing supersu, make sure you go to the adb terminal in twrp and type in the systemless root command so that it will force a systemless root installation of supersu.
Once all of this is done, I hope you have a working phone with bootloader unlocked, twrp recovery, and systemless root. if you still have problems attaining this features in your phone, please let us know! otherwise, hit me a thanks!
Good Luck!
Click to expand...
Click to collapse
This fixed the issue for me. That is to say, I was able to flash the stock firmware for MPJ24_139-48 and from there re-flash recovery, logo, and systemless root.
Thank you!

Downgrade from nougat G model to b10

Hey guys,
I updated my axon to official nougat, unfortunately I cannot live without my xposed modules so I decided to go back to b10.
I have the bootloader unlocked, but after I flashed nougat my twrp recovery got replaced with the factory one. For some reason I cannot boot the phone into fastboot to flash twrp again so I can revert back to b10.
PS: I tried to downgrade with applying the update.zip b10 package from stock recovery and for some reason it doesnt work.
May I ask you guys what am I missing here to complete the task ? what am I doing wrong ?
Regards

Hi, i had the same problems, this answer helped me:
* Enable USB Debugging
* 'adb reboot edl' (I thing this only applies to european models)
* Put twrp image next to axon7tool and rename it to "recovery.bin"
* Use axon7tool to flash the recovery image: 'axon7tool -w recovery' ( Remember to use zadig if you run into problems communicating with your device )

I have been trying this for the past hour . I tried with qualcomm drivers , i tried zadig but it doesnt work. When i execute the axon7tool command and it doesnt work

I've managed it. Just grab the official software update from ZTE's support website, whack that file on ya SD Card and then go to "System Update" in settings and it should appear there with an "upgrade" button.

I put update.zip on the sd and did what you said but it doesn't appear the upgrade. I tried from recovery mode as well and I get an error about footer

the update.zip (which is provide by OTA) will to work. Try the full firmware from this thread:
https://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817

Can't unlock FRP, can't relock bootloader, can't flash

Hello,
today to my utmost rage i accepted system update, as i never had problems with getting the phoned rooted etc. after updates. But little did I know it was emui 5.0 along with android 7.0 update which pretty much rekt me.
The details of my phone:
HUAWEI VNS-L21
VNS-L21C09B336
kernel 4.1.18-g5e26674
Can provide more if needed.
The only thing I did was to get TWRP through SRKTool from here, xda, and rooting through it. And it worked flawlessly to my needs.
After the update I lost twrp, so without searching back then i tried to get it back through SRKTool to no avail. Downloaded newer SRKTool, same thing.
Then I started searching for more information regarding how to root my phone, during which I found out that I'm PHONE Unlocked FRP locked at fastboot.
And of course my "Disable OEM lock" in developer options is greyed out.
I tried p9toolkit from here, I tried command syntaxes in adb's fastboot, everything with USB debugging, nothing did anything. I can't flash either new TWRP or Revolution Recovery because the FRP lock isn't letting me flash anything, and for some reason i can't relock bootloader. I have correct unlock code, command line syntaxes just failed and p9toolkit produced errors saying that my unlock code is wrong (which is not true, I checked at huawei's site) or my phone is locked/unlocked depending on me trying to lock it or unlock it.
Even the built in recovery fails to get the package when I try to restore with it.
The boot message that "my device can't be trusted" is of course still present.
Feeling defeated I did a factory reset along with both wipes, hoping that'll let me change OEM lock in dev options and will clean the phone of many root related settings, but OEM lock is still greyed out.
Basically it seems the phone is locked in some kind of limbo of having bootloader unlocked but locked when you try to flash anything, because of FRP, and I can't relock to unlock FRP...and so on.
I would be extremely grateful if someone could help with sorting this out, basically I only want root, but it's just a mess overall.

Did you already try to dload an UODATE.APP file? If not:
1) create a folder on your external SD card named DLOAD
2) Download your firmware's update.zip file and extract it
3) put the extracted update.app file in the dload folder
4) boot phone with volume up + volume down + power
5) this will relock bootloader, install stock Android, stock recovery, stock boot (basically make every single thing stock) do you can start over again by rooting nougat!

I did not try it because I have no idea how to find the correct firmware for my phone, I have used the firmware finder from xda but the amount of results pretty much overwhelmed me so I didn't try anything with it, as i would probably get my situation worse.
EDIT: i found this site http://hwmt.ru/oth/HWFF/info/view.php?find_model= and there is update.zip of seemingly the same version as mine, is this the correct file http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v87119/f2/full/update.zip?

Need help raising it from the graveyard

Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?

Mairtrus said:
Hello everyone.
I managed to brick my p9 lite (VNS-L31C432 dual sim) by flashing the rollback package over B161 (I know B160 is for DS, I just missed the correct update.app twice). The current status of my phone right now is:
- Phone won't boot, is stuck at "Phone is booting now"
- VolUP + VolDOWN + Power combination doesn't access to dload. If I have it connected via usb to my computer it kinda enter to dload but an usb plug symbol appears and does nothing
- Can unblock/rebock bootloader
- Can access to TWRP 3.0.2-0
- Can access to Fastboot and flash partitions, however when I do it TWRP lose the ability to mount them and they appear as 0MB partitions (I have to change fs to EXT2 then to EXT4 to make them work again).
So, from where should I start to try to recover my phone?
Click to expand...
Click to collapse
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers

Dadditz said:
Hello,
unlock again the bootloader then use correct rollback package (or flash L31C432OEMinfo_bin dual sim file with TWRP) and DLOAD correct firmware this time...
If you are unsure just ask...
Cheers
Click to expand...
Click to collapse
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...

Mairtrus said:
Thanks, pal, but I already fixed it, doing a lot of trial-errors
If someone who had the same problems I had is reading this, what you really need to do is:
As Dadditz said, flash first your correct oem info, then unlock the bootloader
If you can't access dload, find the full-ota package for the exact same version of MM you previously had (before the brick, of course). Unzip the UPDATE.APP and then use UpdateExtractor to get BOOT, SYSTEM, RECOVERY, RECOVERY2 and CUST. Flash all of them via Fastboot.
If you try to boot and it gets into eRecovery, then it's a good sign. Put the UPDATE.APP from the previous step in the dload folder of your SD, use the dload method and let the install run. It will probably fail at the end, this seems to be normal.
You phone will boot and it will probably feel like it's working ok again, but I bet there are chances that a some stuff doesn't work or even appear at all (first time the fingerprint config didn't appeared to me, second time was the google account login). Turn off the phone, install the correct version of TWRP, wipe cache/dalvik, then do a factory reset (dunno if both are needed, I just did it this way and it worked ok).
Reboot you phone. Now it should really be working ok again.
If you little P9-Lite refuses to update to a newer version, use Firmware Finder to upgrade whatever version FullOTA-MF-PV you want to (in my case, I did to B370).
Enjoy
I'm still wondering why installing the wrong rollback package messes up with the recovery2 partition...
Click to expand...
Click to collapse
Yep, factory reset + wipe cache did the work..
Cheers

Soft Bricked PRA-LX1 (I guess? :D)

Alright here goes another post from another stupid user who did things without understanding
I know there are hundreds of other threats with the same question,I tried to check them but they are damn many and I am confused. I hope no moderator gets angry at me.
I have PRA-LX1 which had EMUI 8 working fine. and then I decided that I am too young to have an old Android and decided to go for LineageOS 17.1 from DarkJoker360. After couple of unsuccessful attempts and some minor things I ave a phone that goes into fastboot, but not TWRP. keeps bootlooping (I tried a stock recovery for oreo and then was able to shut it down when it prompted eRecovery page, otherwise it kept looping). Bootloader unlocked. (I was able to get so many different TWRPs to work on the phone just few hours ago, and I guess I did not do anything that bad either. )
I saw these posts about getting the boot.img and other images from some Huawei Firmware finder, but not sure how to get them and I am not sure how can I check the exact model of the phone (I guess it is PRA-LX1xxxxxx)
Sorry if I am not giving enough info, I would appreciate if you ask

Resolved. I am not sure what was the issue, but I did followings (writing down just in case this will be helpful).
PRA-LX1 c464. Bootloader unlocked. I was not able to get into TWRP. I was able to get into fastboot. eRecovery from Huawei was not doing anything (cannot get info from server it said).
Then I downloaded the FullOTA-MF
dload method was getting interrupted after 5%.
Then I extracted System.img kernel.img, recovery_ramdis.img and ramdiks.img. and flashed these in order.
System – fastboot flash system SYSTEM.IMG
Ramdisk – fastboot flash ramdisk RAMDISK.IMG
Kernel – fastboot flash kernel KERNEL.IMG
Recovery – fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
Then at reboot it was getting stuck at 0% loading (Warning To avoid system error please do not press and hold the power button) on some EMUI page. Waited for half an hour and rebooted. again stuck. went into bootloader and flashed a TWRP. this time I get into TWRP.
From there dload method to go back to EMUI and installed LineageOS afterwards.