I've unlocked the bootloader, flashed twrp from pc and I was going to flash the supersu zip. Unfortunately, when I went in recovery (twrp) and flashed the supersu zip(installation process didn't show any problem) I clicked reboot and the phone didn't boot! It just turns off(no led or similar). I have fastboot and twrp access, I tried flashing omnirom using the adb sideload command, everything went fine but still when pressing reboot nothing happens! I even tried to boot manually (after flashing the ROM) with the physical button but still nothing(this time the led blinked twice).
I used the latest version of twrp for Athene, version 2.82 of supersu if this could help.
Edit: was it necessary to flash a different kernel, as it was a nougat rom? The rooting guide I followed didn't mention that.
Edit: Everything worked fine before Supersu, the problem must be related to Supersu but how can I solve?
Generally, on stock Nougat ROMs (not custom ROMs in general), you will need a custom kernel if you want to root. Else, the strict anti rooting protections in the stock Motorola kernel on Nougat devices will trip and stop you from booting your device.
You could try clearing the misc partition as described here (I've not tried it, so be very careful) https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 to try to reset the boot issue.
If that doesn't work, we may have to repair with a stock ROM flash via fastboot. Can you remember what stock ROM you last had?
I appreciate there are a lot of rooting guides (albeit most are out of date), for future reference, here's a guide that still works: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
echo92 said:
Generally, on stock Nougat ROMs (not custom ROMs in general), you will need a custom kernel if you want to root. Else, the strict anti rooting protections in the stock Motorola kernel on Nougat devices will trip and stop you from booting your device.
You could try clearing the misc partition as described here (I've not tried it, so be very careful) https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325 to try to reset the boot issue.
If that doesn't work, we may have to repair with a stock ROM flash via fastboot. Can you remember what stock ROM you last had?
I appreciate there are a lot of rooting guides (albeit most are out of date), for future reference, here's a guide that still works: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Click to expand...
Click to collapse
The stock rom was the stock one with android Nougat 7.0, I don't remember any other information Moreover there is a omni rom now, as i wrote before.
Edit:
The device is Motorola Moto G4 XT1622
Stefano Barbotto said:
The stock rom was the stock one with android Nougat 7.0, I don't remember any other information Moreover there is a omni rom now, as i wrote before
Click to expand...
Click to collapse
When you flashed omnirom via ADB side load, did you erase /system, /data, cache and dalvik before flashing omnirom?
Latest stock ROM for EU is here by the way https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
echo92 said:
When you flashed omnirom via ADB side load, did you erase /system, /data, cache and dalvik before flashing omnirom?
Latest stock ROM for EU is here by the way https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
No I didn't, I know I should have done this, though
Edit: So, should I try with the partitions or directly flash stock rom? What do you suggest? The xda page related to partitions was related to another issue....
Stefano Barbotto said:
No I didn't, I know I should have done this, though
Edit: So, should I try with the partitions or directly flash stock rom? What do you suggest? The xda page related to partitions was related to another issue....
Click to expand...
Click to collapse
Okay, the partitions page was an idea to get you out of the TWRP boot issues you had.
For now though, the priority is to get your device running, you could try reflashing omnirom after erasing /system, /data, /dalvik and /cache ( so removing your stock system and data, I hope you backed up). Try booting with the custom ROM. Since you've got TWRP access, this would be easiest, you can always copy files to your device whilst in TWRP and connected via USB.
If that doesn't get your device running or you want to revert back to stock, them flash the stock ROM in fastboot.
echo92 said:
Okay, the partitions page was an idea to get you out of the TWRP boot issues you had.
For now though, the priority is to get your device running, you could try reflashing omnirom after erasing /system, /data, /dalvik and /cache ( so removing your stock system and data, I hope you backed up). Try booting with the custom ROM. Since you've got TWRP access, this would be easiest, you can always copy files to your device whilst in TWRP and connected via USB.
If that doesn't get your device running or you want to revert back to stock, them flash the stock ROM in fastboot.
Click to expand...
Click to collapse
I didn't even back up the rom from twrp, I totally forgot. I only have information backed up from the motorola account(which is not the back up of the rom, of course). Anyway, I'll try flashing and tell you, thanks for the help
echo92 said:
Okay, the partitions page was an idea to get you out of the TWRP boot issues you had.
For now though, the priority is to get your device running, you could try reflashing omnirom after erasing /system, /data, /dalvik and /cache ( so removing your stock system and data, I hope you backed up). Try booting with the custom ROM. Since you've got TWRP access, this would be easiest, you can always copy files to your device whilst in TWRP and connected via USB.
If that doesn't get your device running or you want to revert back to stock, them flash the stock ROM in fastboot.
Click to expand...
Click to collapse
Tried to flash the stock rom you seggested in fastboot mode (followed the instructions in the link you provided), everything worked fine but the phone dosn't boot and remains connected and blinks....I don't know what else to do.
Stefano Barbotto said:
Tried to flash the stock rom you seggested in fastboot mode (followed the instructions in the link you provided), everything worked fine but the phone dosn't boot and remains connected and blinks....I don't know what else to do.
Click to expand...
Click to collapse
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
echo92 said:
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
Click to expand...
Click to collapse
Here is the output from the command "fastboot getvar all":
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.06
(bootloader) product: athene_13mp
(bootloader) board: athene_13mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY2239WC6B
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A40BEC0000000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 354123071313730
(bootloader) meid:
(bootloader) date: 06-02-2016
(bootloader) sku: XT1622
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 5:47:54 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:7.0/NPJS25.
(bootloader) ro.build.fingerprint[1]: 93-14-10/10:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.221.10.athene.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62.01R ATHENE_EMEA_D
(bootloader) version-baseband[1]: SDS_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-g9b51918 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld26) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Mon Aug 28 09:30:48 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VB1.06-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.06-0-g0edfb0d
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.422s
echo92 said:
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
Click to expand...
Click to collapse
As for the outputs of the flashing commands, I couldn't copy them, as I used the OEM flash provided by the author of the post(the window opened and closed automatically) rather than manually inputing the commands in the prompt. I'll try manually and tell you
echo92 said:
Hmm, what outputs did you receive from the flashing commands, were they all reporting [OKAY]? How long did you leave your device to boot?
Are you still able to boot to bootloader? If so, can you re-connect your device to your computer, and in the ADB terminal, type 'fastboot getvar all' (without the quotes) and post the output here please? You may wish to omit your IMEI that's included in these device variables.
Can you hold down the power button for 2-3 minutes, try a hard shutdown, then try to reboot?
Click to expand...
Click to collapse
As for the outputs from the flashing commands, I wasn't able to copy them, as I used the "OEM flash" file (from the author of this link :https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138) which automatically opened and closed the prompt
Stefano Barbotto said:
As for the outputs from the flashing commands, I wasn't able to copy them, as I used the "OEM flash" file (from the author of this link : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138) which automatically opened and closed the prompt
Click to expand...
Click to collapse
Okay, that script should work and looking at the getvar log, it looks like the firmware flashed okay (your bootloader, baseband and system all match), so I'm confused as to why your device is failing to boot...
Can you try manually flashing and reporting back if you get all [OKAY] responses? By manually flashing, I mean copying each command into the ADB terminal in sequence, then executing each command, seeing the [OKAY] before proceeding. That way, we can be sure we have stock fully and no trace of root which might be tripping the checks. I'd like to see the output if possible
echo92 said:
Okay, that script should work and looking at the getvar log, it looks like the firmware flashed okay (your bootloader, baseband and system all match), so I'm confused as to why your device is failing to boot...
Can you try manually flashing and reporting back if you get all [OKAY] responses? By manually flashing, I mean copying each command into the ADB terminal in sequence, then executing each command, seeing the [OKAY] before proceeding. That way, we can be sure we have stock fully and no trace of root which might be tripping the checks. I'd like to see the output if possible
Click to expand...
Click to collapse
I really, extremely apologize for being so dumb : I forgot to unzip the stock rom file, so the files weren't recognised while I was entering the commands. The phone is now perfectly working, thanks again for the great help!
By the way, If I wanted to to root the device, how should I install another kernel?
Stefano Barbotto said:
I really, extremely apologize for being so dumb : I forgot to unzip the stock rom file, so the files weren't recognised while I was entering the commands. The phone is now perfectly working, thanks again for the great help!
By the way, If I wanted to to root the device, how should I install another kernel?
Click to expand...
Click to collapse
If you flashed TWRP you can install the kernel with twrp.
Stefano Barbotto said:
I really, extremely apologize for being so dumb : I forgot to unzip the stock rom file, so the files weren't recognised while I was entering the commands. The phone is now perfectly working, thanks again for the great help!
By the way, If I wanted to to root the device, how should I install another kernel?
Click to expand...
Click to collapse
Woo, we got your device working
If you're still interested in rooting on stock Nougat and flashing a custom kernel (I use ElementalX here for reference, but other custom kernels suitable for Nougat 7.0 stock Motorola athene ROMs should work, like vegito), assuming your bootloader is unlocked:
1)Download ElementalX and your choice of root manager onto your device. ElementalX v1.04 is designed for stock Motorola 7.0 ROMs : https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
2)Flash or boot TWRP. Up to you which TWRP build you use, I prefer shreps' TWRP 3.1.1 athene (https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 ) but the official builds should suffice.
Boot your device to the bootloader and connect your device to your computer. In the ADB terminal, flash TWRP to your recovery partition if you see yourself using TWRP a lot, remember to boot into recovery after flashing to ensure TWRP is not overwritten by the stock recovery (assuming your device is still in the bootloader mode following the flash, use the volume keys on your device after flashing TWRP to select Recovery on your device, then press Power to boot into recovery). You may boot as normal afterwards.
Alternatively, you can temporarily boot in TWRP, which should keep your recovery partition stock but mean you'll have to require a computer to use TWRP.
To boot into TWRP, boot your device to the bootloader and connect to your computer. Copy the TWRP image to your ADB folder. In the ADB terminal type:
Code:
fastboot boot <name of TWRP image>
The <name of TWRP image> should be the full file name (without the greater than/less than signs), you can start typing the first letters of the image name and press Tab on your keyboard to auto-complete if the file is present in the same folder (which it should be if copied to your ADB folder). Ensure that the file name has the correct file name extensions, you may wish to enable file extensions in Windows File Explorer to check, tab auto-complete will do this for you.
3)In TWRP, back up your device using the Backup option (usually everything except cache which should be the default selection).
3a)Also, make a separate backup of the boot partition - this 16 MB partition contains your clean, stock kernel (if you fully flashed the stock firmware).
4)Tap Install in TWRP, and navigate to your Download folder or wherever your ElementalX zip is stored. Flash ElementalX as directed by the installer. After flashing, wipe cache/Dalvik (should appear as an option on screen).
5)After flashing ElementalX, you can choose to flash your choice of root manager or reboot first to check your device is still running. If it's still working, then you can reboot to TWRP (either by rebooting to recovery or using a PC to temporarily boot). Flash your root manager in TWRP (same way as you flashed ElementalX) and then reboot, you should have a stock ROM rooted and booting
A few things to note:
As you'd have TWRP and root, OTA stock updates won't work, and taking an OTA update would soft bootloop your device in TWRP. There are ways to get around this, but you may wish to disable the Motorola updater to stop you being nagged/accidentally downloading the OTA update https://forum.xda-developers.com/moto-g4-plus/help/how-disable-notification-update-t3459587
If you want OTA updates, you'd have to revert to stock fully, but we'll get to that when the time comes.
Rooting with SuperSU may mean that SafetyNet fails - this is Google's anti-tamper/anti-rooting detection, and thus some apps may fail to work. You may use SuperSU hide https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855 or magisk's built-in magiskhide to hide the root manager from detection.
If you have any issues whilst rooting, you may choose to use the backups you made in 3)
If you want to switch custom kernels or change root manager, then I recommend:
a)Uninstall root via your root manager's uninstall procedure. For example, SuperSU has an uninstall function in the SuperSU app, magisk requires a TWRP flashable uninstaller.
b)Reboot into TWRP (if not already in TWRP)
c)Restore the stock kernel backup you made above in 3a). This should remove traces of root from your kernel that may conflict with your new kernel and cause chaos.
d)Flash your new custom kernel of choice followed by your root manager.
e)Wipe cache/Dalvik and reboot.
Good luck
echo92 said:
Woo, we got your device working
If you're still interested in rooting on stock Nougat and flashing a custom kernel (I use ElementalX here for reference, but other custom kernels suitable for Nougat 7.0 stock Motorola athene ROMs should work, like vegito), assuming your bootloader is unlocked:
1)Download ElementalX and your choice of root manager onto your device. ElementalX v1.04 is designed for stock Motorola 7.0 ROMs : https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
2)Flash or boot TWRP. Up to you which TWRP build you use, I prefer shreps' TWRP 3.1.1 athene (https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337 ) but the official builds should suffice. Flash TWRP to your recovery partition if you see yourself using TWRP a lot, remember to boot into recovery after flashing to ensure TWRP is not overwritten by the stock recovery (use the volume keys your device after flashing TWRP to select Recovery on your device, then press Power to boot into recovery). You may boot as normal afterwards.
Alternatively, you can temporarily boot in TWRP, which should keep your recovery partition stock but mean you'll have to require a computer to use TWRP.
To boot into TWRP, boot your device to the bootloader and connect to your computer. Copy the TWRP image to your ADB folder. In the ADB terminal type:
Code:
fastboot boot <name of TWRP image>
The <name of TWRP image> should be the full file name (without the greater than/less than signs), you can start typing the first letters of the image name and press Tab on your keyboard to auto-complete if the file is present in the same folder (which it should be if copied to your ADB folder). Ensure that the file name has the correct file name extensions, you may wish to enable file extensions in Windows File Explorer to check, tab auto-complete will do this for you.
3)In TWRP, back up your device using the Backup option (usually everything except cache which should be the default selection).
3a)Also, make a separate backup of the boot partition - this 16 MB partition contains your clean, stock kernel (if you fully flashed the stock firmware).
4)Tap Install in TWRP, and navigate to your Download folder or wherever your ElementalX zip is stored. Flash ElementalX as directed by the installer. After flashing, wipe cache/Dalvik (should appear as an option on screen).
5)After flashing ElementalX, you can choose to flash your choice of root manager or reboot first to check your device is still running. If it's still working, then you can reboot to TWRP (either by rebooting to recovery or using a PC to temporarily boot). Flash your root manager in TWRP (same way as you flashed ElementalX) and then reboot, you should have a stock ROM rooted and booting
A few things to note:
As you'd have TWRP and root, OTA stock updates won't work, and taking an OTA update would soft bootloop your device in TWRP. There are ways to get around this, but you may wish to disable the Motorola updater to stop you being nagged/accidentally downloading the OTA update https://forum.xda-developers.com/moto-g4-plus/help/how-disable-notification-update-t3459587
If you want OTA updates, you'd have to revert to stock fully, but we'll get to that when the time comes.
Rooting with SuperSU may mean that SafetyNet fails - this is Google's anti-tamper/anti-rooting detection, and thus some apps may fail to work. You may use SuperSU hide https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855 or magisk's built-in magiskhide to hide the root manager from detection.
If you have any issues whilst rooting, you may choose to use the backups you made in 3)
If you want to switch custom kernels or change root manager, then I recommend:
a)Uninstall root via your root manager's uninstall procedure. For example, SuperSU has an uninstall function in the SuperSU app, magisk requires a TWRP flashable uninstaller.
b)Reboot into TWRP (if not already in TWRP)
c)Restore the stock kernel backup you made above in 3a). This should remove traces of root from your kernel that may conflict with your new kernel and cause chaos.
d)Flash your new custom kernel of choice followed by your root manager.
e)Wipe cache/Dalvik and reboot.
Good luck
Click to expand...
Click to collapse
Just a question: I already have twrp on my device(I normally access by powering off phone, then power+volume down keys, then I select recovery from the menu and I am in twrp), how do I know if it is already flashed to my recovery partition? Should I flash twrp from pc in fastboot mode again and then boot into recovery after flashing, as you wrote? Thanks in advance for the reply
Stefano Barbotto said:
Just a question: I already have twrp on my device(I normally access by powering off phone, then power+volume down keys, then I select recovery from the menu and I am in twrp), how do I know if it is already flashed to my recovery partition? Should I flash twrp from pc in fastboot mode again and then boot into recovery after flashing, as you wrote? Thanks in advance for the reply
Click to expand...
Click to collapse
If you've already got TWRP on your device and can not into it, then it's already flashed to your recovery partition. No need to flash it again.
Just boot into TWRP and follow from step 3 (backing up your device)
echo92 said:
If you've already got TWRP on your device and can not into it, then it's already flashed to your recovery partition. No need to flash it again.
Just boot into TWRP and follow from step 3 (backing up your device)
Click to expand...
Click to collapse
I can into it via the fastboot menu but not directly with the combination of power + volume down buttons(this sends me in fastboot mode). If I haven't misunderstood, this means it's already flashed to my recovery partition, is it right?
Stefano Barbotto said:
I can into it via the fastboot menu but not directly with the combination of power + volume down buttons(this sends me in fastboot mode). If I haven't misunderstood, this means it's already flashed to my recovery partition, is it right?
Click to expand...
Click to collapse
Volume down and power button combinations should always send you to the bootloader/fastboot mode (won't let you boot directly to recovery), then you can select recovery from the fastboot menu. If it's as you described, then yes, you already have TWRP flashed to your recovery partition and you're doing things correctly.
What I wrote in step 2) assumed your device was already booted into the bootloader mode to flash/boot TWRP. Hence, you can use the volume and power keys as you described to boot into TWRP recovery. I'll add that to make the procedure clearer
For clarity's sake:
Powered off device > Pressing the power and volume down keys > Bootloader/fastboot mode.
In bootloader/fastboot mode, select recovery from the fastboot menu with the volume keys. Press Power key to select
If you see:
TWRP logo - you have TWRP flashed to your recovery partition
OR a green Android on its back with No Command - that's stock recovery.
Related
I was under the impression that fastboot boot twrp.img no longer worked in recent android versions. I recall reading this for a couple of devices. However, out of curiosity, i tried it and it worked today. I am running 7.0 nougat and fastboot booted twrp to back up all partitions using the latest twrp.
If I am wrong mods please delete.
Milly7 said:
I was under the impression that fastboot boot twrp.img no longer worked in recent android versions. I recall reading this for a couple of devices. However, out of curiosity, i tried it and it worked today. I am running 7.0 nougat and fastboot booted twrp to back up all partitions using the latest twrp.
If I am wrong mods please delete.
Click to expand...
Click to collapse
I can confirm that it does indeed work.
Try "adb reboot bootloader" to get into the bootloader. Then make sure that you renamed the image to twrp, then you can do fastboot boot twrp.img and it will work. Just be sure to be using TWRP 3.0.2-1, that one works with Nougat and encryption
I have few questions:
When booted to TWRP using fastboot boot (without flashing), in which partition TWRP is temporarily stored? Is is boot partition? After booting into TWRP (without flashing), if I take backup of boot partition, will it be stock version?
panijsr said:
I have few questions:
When booted to TWRP using fastboot boot (without flashing), in which partition TWRP is temporarily stored? Is is boot partition? After booting into TWRP (without flashing), if I take backup of boot partition, will it be stock version?
Click to expand...
Click to collapse
I don't know the answer to your first question. It just replaces the stock recovery until a reboot.
Assuming that you are using a stock rom, the backup will be the stock boot of the monthly security update that is currently installed.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
I don't know the answer to your first question. It just replaces the stock recovery until a reboot.
Assuming that you are using a stock rom, the backup will be the stock boot of the monthly security update that is currently installed.
Click to expand...
Click to collapse
It does not modify the recovery partition, even temporarily. That is why, we are able to backup stock recovery, before actually flashing TWRP. It must be residing either in boot or cache partition, until next boot.
fastboot boot recovery.img should work as recovery is a boot image (header, sig, kernel, ramdisk)
Now to know where downloaded data are stored on the device, you'd have to look in fastboot device side code (based on https://source.codeaurora.org/quic/la/kernel/lk/tree/app/aboot) but could be that some code is not published.
fastboot boot involves a download command, followed by a boot command, while fastboot flash involves a download followed by a flash command.
Looks like it's stored in RAM, see https://source.codeaurora.org/quic/la/kernel/lk/tree/app/aboot/aboot.c#n221 and control is then given to this physical address where the kernel and ramdisk (initial rootfs which contains init the first userland program being execed) are.
Downloads can't be stored in cache (100MB), it's too small for a max download size (472MB). From a quick read of the protocol description, it's not clear to me how bigger images are downloaded (system is 1.9GB).
See:
Code:
[email protected]:~$ fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-ROW-VN1
(bootloader) version-baseband:angler-03.81
(bootloader) version-bootloader:angler-03.69
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:ENU7N15DEADBEEFCAFE
(bootloader) kernel:lk
(bootloader) product:angler
Edit: so I was curious and looked at the code, for IMG bigger than max download size, the file is sent in chunks. And it probably still is uploaded into RAM. Which is Ok as we have 3GB RAM. There's no CRC check though neither for transport nor by rereading written data. For system, that's probably taken care of by dm-verity which kicks in at boot and autocorrects simple mmc error. But it would have been good to see during flash how many inconsistencies were detected.
Hey everyone.
Following Situation:
-Device Wont Boot
-Unlocking Bootloader not enabled in Developer Settings
-Device Locked
-Can install either stock or TWRP recovery
-TWRP cannot install Lineage OS nor Stock Rom
-Current OS was Stock Nougat from ZTE
-EDL Bootable
-Bootloader bootable
-Can access ADB and Fastboot
fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) cmdlog:eek:K
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4029000
(bootloader) variant:AILSA_II eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x32000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd1a533000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x180000000
(bootloader) serialno:3ac4000
(bootloader) kernel:lk
(bootloader) product:AILSA_II
all:
finished. total time: 0.230s
Basically I can boot everything except the OS itself, it won't let me install any ROMs, fastboot oem unlocking does NOT work.
Does anyone know exactly how to resurrect my phone?
I can of course provide more information as needed.
(Please move if this is not the correct forum, I didn't want to post in Custom Roms and Development because it looks that is only for posting Roms, not issues with the device)
Thanks in advance!
What have you tried?
What did you do that caused this?
Sent from my ZTE A2017U using Tapatalk
Did you try edl roms?
WesTD said:
Did you try edl roms?
Click to expand...
Click to collapse
That's sort of the last thing you should try lol
---------- Post added at 10:30 PM ---------- Previous post was at 10:23 PM ----------
FroschDev said:
Hey everyone.
Following Situation:
-Device Wont Boot
-Unlocking Bootloader not enabled in Developer Settings
-Device Locked
-Can install either stock or TWRP recovery
-TWRP cannot install Lineage OS nor Stock Rom
-Current OS was Stock Nougat from ZTE
-EDL Bootable
-Bootloader bootable
-Can access ADB and Fastboot
fastboot getvar all:
Basically I can boot everything except the OS itself, it won't let me install any ROMs, fastboot oem unlocking does NOT work.
Does anyone know exactly how to resurrect my phone?
I can of course provide more information as needed.
(Please move if this is not the correct forum, I didn't want to post in Custom Roms and Development because it looks that is only for posting Roms, not issues with the device)
Thanks in advance!
Click to expand...
Click to collapse
All right...
-What TWRP version do you have? If you have anything other than 3.1.1-0 (or 3.2.0-0) simply go to the TWRP page, download TWRP 3.1.1-0 (for Axon 7 or ailsa_ii, be sure) and put it in the internal storage. Then go to Install, Install image, select the TWRP-3.1.1-0.img, flash to Recovery. After it installs don't reboot, go to the Reboot button on the lower right hand corner and hit Recovery.
You should boot into TWRP 3.1.1-0 after that.
To install LOS, first wipe data, system, dalvik and cache (not internal unless your files are on an SD card). then flash the Universal Bootloader. After that, install the modem for your own phone model (see at the back of the phone), then again Install image, and install the same TWRP 3.1.1-0.img that you installer before, to Recovery. Then flash Magisk 14.5 or .3 or .0, or SuperSU 2.79, and then reboot to system
EDIT: I just noticed WesTD is kinda right. If your phone has a locked bootloader you'll have to get into EDL and flash a full stock ROM.
If the BL is unlocked then just flash TWRP
All right...
-What TWRP version do you have? If you have anything other than 3.1.1-0 (or 3.2.0-0) simply go to the TWRP page, download TWRP 3.1.1-0 (for Axon 7 or ailsa_ii, be sure) and put it in the internal storage. Then go to Install, Install image, select the TWRP-3.1.1-0.img, flash to Recovery. After it installs don't reboot, go to the Reboot button on the lower right hand corner and hit Recovery.
You should boot into TWRP 3.1.1-0 after that.
To install LOS, first wipe data, system, dalvik and cache (not internal unless your files are on an SD card). then flash the Universal Bootloader. After that, install the modem for your own phone model (see at the back of the phone), then again Install image, and install the same TWRP 3.1.1-0.img that you installer before, to Recovery. Then flash Magisk 14.5 or .3 or .0, or SuperSU 2.79, and then reboot to system
Click to expand...
Click to collapse
I did try that, but with no success.
EDIT: I just noticed WesTD is kinda right. If your phone has a locked bootloader you'll have to get into EDL and flash a full stock ROM.
If the BL is unlocked then just flash TWRP
Click to expand...
Click to collapse
Bootloader is locked, I honestly have no idea why the phone stopped working anyways. I have not tried flashing anything before that happened, that's why I never unlocked the bootloader.
I would love to try EDL Rom flashing, but it seems I need a Windows PC for that and I only got access to Linux PCs.
My dad insisted on returning the phone for repair anyways and just sent it in without my consent, so I guess I have to wait for up to two months now for it to reach my
service provider, then to get sent to ZTE where they will either flash a new firmware or replace the motherboard and eventually coming back home..
Looks like I gotta use a broken Avus A24 with defective battery now for a while..
But thanks for your help anyways guys!
FroschDev said:
I did try that, but with no success.
I would love to try EDL Rom flashing, but it seems I need a Windows PC for that and I only got access to Linux PCs.
But thanks for your help anyways guys!
Click to expand...
Click to collapse
Can't you find a Windows PC? You can fix your phone if you can
WesTD said:
Can't you find a Windows PC? You can fix your phone if you can
Click to expand...
Click to collapse
he just said his dad sent it to ZTE for repair
I've been doing this crap for nearly a decade now and the only time I've ever had so much trouble was back with the Evo 3D before they had that bootloader update that would only let you half-unlock or whatever and you had to intentionally corrupt the bootloader to flash a lower version.
I've been through 6 damn versions of twrp on this device, will not accept pin on new versions so 3.1.1.0-plotter works but it doesn't flash anything error 255. I update and again, will not accept my pin, wrong password it says.
I have been rebooting for the past 2 hours with nothing to show for it but twrp and being able to actually boot the stock rom (this was a problem at first, would boot loop into recovery). Somewhere along the line I got 'bad key' ID and don't know how the hell I did that but I continue to get '(bootloader) Image not signed or corrupt' in cmd.
What the actual **** is up with this phone? And how can I just get a nice AOSP non-gapps rom?
I've used the toolkit to re-flash stock rom so that is where I sit. Please help.
negativzeroe said:
I've been doing this crap for nearly a decade now and the only time I've ever had so much trouble was back with the Evo 3D before they had that bootloader update that would only let you half-unlock or whatever and you had to intentionally corrupt the bootloader to flash a lower version.
I've been through 6 damn versions of twrp on this device, will not accept pin on new versions so 3.1.1.0-plotter works but it doesn't flash anything error 255. I update and again, will not accept my pin, wrong password it says.
I have been rebooting for the past 2 hours with nothing to show for it but twrp and being able to actually boot the stock rom (this was a problem at first, would boot loop into recovery). Somewhere along the line I got 'bad key' ID and don't know how the hell I did that but I continue to get '(bootloader) Image not signed or corrupt' in cmd.
What the actual **** is up with this phone? And how can I just get a nice AOSP non-gapps rom?
I've used the toolkit to re-flash stock rom so that is where I sit. Please help.
Click to expand...
Click to collapse
U hardbricked your phone
dhinesh_cool said:
U hardbricked your phone
Click to expand...
Click to collapse
How? I'm up and running stock rom, got TWRP, and have Magisk installed for root so I can use it for now.
negativzeroe said:
How? I'm up and running stock rom, got TWRP, and have Magisk installed for root so I can use it for now.
Click to expand...
Click to collapse
First of all don't use toolkits. Learn the manual way, it's much safer. I'm not really sure that I understand your post correctly. The official TWRP recovery (3.2.1.0) isn't able to decrypt your data partition, that's why it asks for a pin. Just skip the step, go to Wipe and reformat /data (it's the part where you have to confirm with "yes", not just swipe).
Be aware that all of of your data stored in internal storage will be wiped.
Also make sure to enable OEM unlocking in developer options before you start.
After that your data partition should be decrypted and you should be able to install a custom rom.
Warning:
Make a nandroid backup of all your partitions incl.EFS before and backup also persist.
If you want to return to stock there I a high risk to lose IMEI,VoLTE,4G or all of them if you don't have everything backed up.
Here's how to backup persist:
https://forum.xda-developers.com/g5-plus/how-to/dev-fixing-baseband-t3806064/page2
The needed commands are
Code:
adb shell
dd if=/dev/block/mmcblk0p30 of=/sdcard/persist.img
for backup and
Code:
adb shell
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p30
for restoring.
Sent from my Moto G5 Plus using XDA Labs
OK I know how to do it the manual way. I've been doing this since 2009. Not to appear like a douche but I'm not new to root/rom/etc. Just this phone. Granted I've been away for a bit due to a work-issued Verizon Pixel, but I've gone through this process on Nexus devices, LG, HTC, etc. I've done everything I know to do but it's not doing...
I used the toolkit because I was lazy and only for the unlock itself, which was successful.
The official TWRP recovery (3.2.1.0) isn't able to decrypt your data partition, that's why it asks for a pin. Just skip the step, go to Wipe and reformat /data (it's the part where you have to confirm with "yes", not just swipe).
Click to expand...
Click to collapse
Here is the problem. If I skip, I can't do **** to my partitions, wipe, install etc.
Make a nandroid backup of all your partitions incl.EFS before and backup also persist.
Click to expand...
Click to collapse
Another problem. I did this but during trying to wipe data and install rom, it nuked my backups. I didn't know this, and now persist is gone. I found the guide to restore so that isn't an issue. Personally I thought Volte always made my call quality suck anyway.
Also I currently cannot boot recovery.....
Code:
~fastboot flash recovery twrp-3.2.1-0-potter.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16290 KB)...
OKAY [ 0.369s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.315s]
finished. total time: 0.685s
~fastboot reboot recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
fastboot: usage: unknown reboot target recovery
EDIT also Idk if it's important but it says 'n/a' where 'bad key' used to be on the "we hate you for unlocking" boot screen.
EDIT 2 I can with adb reboot recovery from within the os, when trying to back up, unable to mount storage.
EDIT 3 downgraded back to 3.1.1.0 and I can back up. I'll work with this and see what I get.
EDIT 4, can flash minor zips to no effect (no-verify), can back up, can wipe data and system partitions. Cannot install a rom. Error 7. I've confirmed that this is a plotter rom.
EDIT 5. Okay I can install Resurrection Remix NOUGAT, but cannot install any OREO roms. For whatever the **** reason I have no idea.
negativzeroe said:
OK I know how to do it the manual way. I've been doing this since 2009. Not to appear like a douche but I'm not new to root/rom/etc. Just this phone. Granted I've been away for a bit due to a work-issued Verizon Pixel, but I've gone through this process on Nexus devices, LG, HTC, etc. I've done everything I know to do but it's not doing...
I used the toolkit because I was lazy and only for the unlock itself, which was successful.
Here is the problem. If I skip, I can't do **** to my partitions, wipe, install etc.
Another problem. I did this but during trying to wipe data and install rom, it nuked my backups. I didn't know this, and now persist is gone. I found the guide to restore so that isn't an issue. Personally I thought Volte always made my call quality suck anyway.
Also I currently cannot boot recovery.....
Code:
~fastboot flash recovery twrp-3.2.1-0-potter.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16290 KB)...
OKAY [ 0.369s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.315s]
finished. total time: 0.685s
~fastboot reboot recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
fastboot: usage: unknown reboot target recovery
EDIT also Idk if it's important but it says 'n/a' where 'bad key' used to be on the "we hate you for unlocking" boot screen.
EDIT 2 I can with adb reboot recovery from within the os, when trying to back up, unable to mount storage.
EDIT 3 downgraded back to 3.1.1.0 and I can back up. I'll work with this and see what I get.
EDIT 4, can flash minor zips to no effect (no-verify), can back up, can wipe data and system partitions. Cannot install a rom. Error 7. I've confirmed that this is a plotter rom.
EDIT 5. Okay I can install Resurrection Remix NOUGAT, but cannot install any OREO roms. For whatever the **** reason I have no idea.
Click to expand...
Click to collapse
u want latest twrp for flashing oreo
Right but newest twrp cannot modify partition because it cannot decrypt data. Password incorrect.
Edit, used this one and after several times manually wiping data and rebooting back to recovery it eventually works: https://forum.xda-developers.com/showpost.php?p=75306024&postcount=76
I got a second hand nexus 10, when it boots up it is on cyanogen mod:
kernel 3.4.67-cyanogenmpd-gedbec95 [email protected] #1 mon nov 18 18:16:58 pst 2015
build date mon nov 16 18:04:11 PST 2015
build number: cm_manta-userdebug 5.1.1 LMY48Y 89d47a5074 test-keys
SELINUX Status Enforcing
When I boot the device it runs the rom and has TWRP 3.0.2-0 installed. When I boot into TWRP and select factory reset and even go as far as wiping system the device reboots back to the ROM. When I uninstall apps or try to flash factory roms the device accepts the files such as recovery.img etc but then reboots to the ROM with the apps I removed still there. It is like whatever I try to do to it it always reverts back to the current ROM and always reboots in the same state, even if I have enabled USB debugging, this disappears on reboot.
I have tried to flash recovery, radio, kernels, system etc etc and the device says it takes them but on reboot it always reverts to the ROM. Nothing I do can change anything on this device.
I have tried a different OS, different USB cable, flashing via sideload, bootloader, fastboot. It is always the same.
Any ideas?????
Further to my last, something strange about this device is that I cannot re lock the bootloader. I am begining to think the bootloader is somehow corrupt, but attempts to flash the stock bootloader do not work. Anything I flash says it has been flashed but upon reboot its back to square 1. I have even gone as far as to unmount the system partition in TWRP and delete several critical system files, and again, on reboot they appear again. Any ideas anyone?
nokiaman2002 said:
Further to my last, something strange about this device is that I cannot re lock the bootloader. I am begining to think the bootloader is somehow corrupt, but attempts to flash the stock bootloader do not work. Anything I flash says it has been flashed but upon reboot its back to square 1. I have even gone as far as to unmount the system partition in TWRP and delete several critical system files, and again, on reboot they appear again. Any ideas anyone?
Click to expand...
Click to collapse
To restore to stock i used "Nexus Root Toolkit" i pushed on "Flash Stock + lock" and then u select the image and follow the indications on screen. It is like ADB commands just it has a GUI so maybe it is easyer.
steveyyyy said:
To restore to stock i used "Nexus Root Toolkit" i pushed on "Flash Stock + lock" and then u select the image and follow the indications on screen. It is like ADB commands just it has a GUI so maybe it is easyer.
Click to expand...
Click to collapse
I have tried that, still the same. I do not think there is anything I have not tried! All I want to do is put Kali Nethunter on it. I have even opened up the device to check for water damage and its dry inside. I have even tried a different usb cable, port, operating system.
nokiaman2002 said:
I have tried that, still the same. I do not think there is anything I have not tried! All I want to do is put Kali Nethunter on it. I have even opened up the device to check for water damage and its dry inside. I have even tried a different usb cable, port, operating system.
Click to expand...
Click to collapse
But the device still turns on, what does the bootloader tell? U could use the download mode (powerbutton + volum down). I never used download mode so i can't tell how it works. But on other samsung devices you could send the firmware to the device with "Odin".
steveyyyy said:
But the device still turns on, what does the bootloader tell? U could use the download mode (powerbutton + volum down). I never used download mode so i can't tell how it works. But on other samsung devices you could send the firmware to the device with "Odin".
Click to expand...
Click to collapse
There is no odin download mode on this device just the bootloader which accepts fastboot commands.
nokiaman2002 said:
There is no odin download mode on this device just the bootloader which accepts fastboot commands.
Click to expand...
Click to collapse
The bootloader, if it shows up, what exactly does it tell, does it have some strange behavior like if u push vol up or down it doesn't change text. Maybe retry to flash stock with another PC.
Bootloader looks normal with all the usual options of reboot bootloader, start recovery, and start system. Bootloader state is always UNLOCKED even tho I can try to set it to LOCKED using fastboot. That is what leads me to think the bootloader is corrupt. I have tried another pc, and another usb cable. It is like any command send to it is being ignored but the bootloader is saying OK THATS FINE. I have tried flashing another bootloader and flashing another recovery and flashing boot.img from stock. On reboot it always reverts to TWRP 3.0.2-0 no matter what. I can fastboot reboot a custom recovery or stock and it works, but any commands sent there are dealt with the same way. I may as well buy another from ebay as this thing I have wasted a lot of time on.
fastboot getvar all: Shows bootloader SECURE YES, so the bootloader is secure and will not allow much flashing
(bootloader) product: manta
(bootloader) variant: wifi-only
(bootloader) serialno: R32D1014MET
(bootloader) version-hardware: 8
(bootloader) version-bootloader: MANTAMF01
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: enabled(1)
(bootloader) signing: yes
(bootloader) boot partition- type: raw, size: 0x0000000001000000
(bootloader) recovery partition- type: raw, size: 0x0000000001ff0000
(bootloader) metadata partition- type: raw, size: 0x0000000000010000
(bootloader) misc partition- type: raw, size: 0x0000000000400000
(bootloader) cache partition- type: ext4, size: 0x0000000021000000
(bootloader) system partition- type: ext4, size: 0x0000000032000000
(bootloader) userdata partition- type: ext4, size: 0x0000000352c00000
--> if you are here because you flashed a custom ROM and on the first boot get "to start Android, enter your password" You probably only have to do MAIN below.
To tell if you are encrypted go to Settings/Security&Location/Advanced/Encryption&credentials.
Any phone that has been flashed with a stock zip (via RSDlite or command line) is encrypted. That is Lenovo/Motorola's way.
Set up a working custom ROM if you don't have one:
RSDlite a stock ROM - I suggest
XT1635-02_ADDISON_RETAIL_8.0.0_OPNS27.76-12-22-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
from lolinet
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
or whatever might match your country.
Don't let it OTA but boot immediately back to bootloader.(hold vol-dn&pwr)
Flash TWRP from computer (fastboot flash recovery twrpimg.img)
Boot to TWRP.
Wipe Advanced [check: dalvik,system,data,cache] , and flash a custom ROM and gapps, and boot to it.
At this point you will have your custom ROM but it will be encrypted.
Continue with MAIN:
MAIN: Most people with a custom ROM just do this step:
Summary: do fastboot erase userdata and then boot your ROM. That's all!
Detail:Have a working custom ROM that's encrypted.
In TWRP, back up Internal Storage to your computer if there's anything you need to save on it(like Titanium Backup folder).
Boot to bootloader, connect via USB, and from computer, run:
Code:
fastboot erase userdata
Then, Boot your system: (since you are already at bootloader, use volup/dn to get to START and press power).
It will start out fresh as non-encrypted.
You are DONE.
Many thanks for getting me started on this!!! @fablebreton !!! <-------------------
I suspect this will work on any Android phone with TWRP though of course I haven't tested it.
Typical terminal log:
Code:
F:\MOTO Z PLAY\TWRP-adb-fastboot-platform-tools>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 2.527s]
finished. total time: 2.527s
F:\MOTO Z PLAY\TWRP-adb-fastboot-platform-tools>