Database Users

Lolipop OTA capture

Update 2 after some fiddling I found that after flashing Pico Capps hdxposed is needed to make the play store work on this build http://forum.xda-developers.com/showthread.php?t=2618158
Update 1 New lolipop ota, this appears to be based on lolipop 5.1 and as such requires xposed unofficial by romracer if you want to use xposed Xposed for 5.0 would not flash for me. Same upgrade steps as before just this one instead of the bottom one and change your xposed package
https://mega.nz/#!i5RRCKQZ!NC291mcIo-2yzr23j8Vg_mLZ11ECql4lL_xen6xwXuM
update-kindle-devpreview_ariel-20.5.2.2_user_522041550.bin

siegesoldier said:
this is the developer preview, sorry if the title is a little misleading. Thanks to http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Use at your own risk.
https://www.dropbox.com/s/38i2lqq5p...review_ariel-20.5.2.0_user_520033250.bin?dl=0
Hopefully someone can figure out how to make this thing boot when flashed from TWRP
Click to expand...
Click to collapse
Important update, the instructions below are not to be followed !!! They are historical ...
Same drill as in here :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
Replace the original META-INF/com/google/android/updater-script with the one from the zip below. Remove "images" directory. This will ensure that your bootloader stays 4.5.3 and unlocked. When TWRP asks to add root, say yes.
If for some reason you lose TWRP (recovery), reflash it from within 5.0. Since you have root, no biggie. I'll play with this a bit too, but later.

I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.

siegesoldier said:
I tried yours and tried my attempt. I'm getting a bootloop with both, let me know if you have any luck. TWRP protects itself from getting replaced.
Click to expand...
Click to collapse
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip).
The trick is that you install Lollipop, install root, and install the new bootloader separately. It should boot OK and you should have root in 5, but you'll lose TWRP (it won't be able to boot since the bootloader will probably be signed). To get TWRP back you'll need to downgrade to 4.5.3

bibikalka said:
OK. Does it flash successfully? Does it ask to install root? If it does and bootloops, the bootloader probably needs to be updated too. You could try to flash the new bootloader (just grab my uboot_4.5.3.zip, replace both files in /images, and re-zip
Click to expand...
Click to collapse
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen

Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?

siegesoldier said:
Currently booting to home screen but then back to the fire screen, etc. Probably my fault for not clearing the cache or a factory reset. I'm not at a computer at the moment but any ideas on how to fix this?
Click to expand...
Click to collapse
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Upon reflection, there is a chance you have a bit of a soft brick. If the factory reset option does not come up, it may end up a little tricky to fix things. I wonder if you'd be able to connect via adb before it reboots.

bibikalka said:
Turn it off with a long press of "power" button. Then press "power" and "vol+" together, this should get you into the Amazon recovery. It should offer you a factory reset option. Your system should be pretty much stock Lollipop, so I don't see why it should be doing what it does ...
Actually, does it now have stock Amazon recovery or TWRP ? My suspicion is that it should have flashed recovery during the first upgrade cycle.
Click to expand...
Click to collapse
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.

siegesoldier said:
it appears to have TWRP but it will not boot to it with holding keys. I can get the device to appear in ADB but I can not authorize it. Appears to not actually be rebooting. just crashing to fire screen for some reason then back to launcher etc. I may be able to try again at home with a usb port that it remembers.
Click to expand...
Click to collapse
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement

I think TWRP just blocked it from updating. Oh well, if the ports at home don't work, I was eventually going to get it replaced anyway since I had a blue discoloration on my screen. Glad to be of some moderate use to the community instead of a leecher for once. May the next person have some luck!

bibikalka said:
I wonder if Lollipop does not update recovery at all, and just uses the one from 4.5.4 You do have your old settings around, so there is a chance that prior USB authorization will help. It looks like one should have updated to stock recovery while in TWRP as the last step, after updating the bootloader, ir order to be able to do a factory reset in a situation like this.
If it comes to worst, Amazon reps never ask "did you brick the device yourself?". They only ask if you can get to the home screen, and if not, proceed with the replacement
Click to expand...
Click to collapse
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen

siegesoldier said:
ok I was able to get adb on a previously used port. I do not have root though. What are my options? What recovery should I flash? I also have a replacement kindle coming tomorrow so this is mostly for science now. I am also able to get into bootloader.
erased cache via fastboot. stuck on fire instead of boot to homescreen
Click to expand...
Click to collapse
So no adb anymore? I am not sure how SuperSu comes in, there gotta be su program somewhere.
Anyway, the great news is that JMZ is going to be back soon. That's going to boost our tinkering capabilities by 300%

siegesoldier said:
Yes it flashes successfully and asks to install root. Looks like I'll be trying that tonight, thanks!
Edit we have a winner.
Flashed lolipop without bootloader
Installed su
Reboot to recovery
Installed superuser flashable zip
Flashed uboot file with lolipop images folder
Fire has booted and is currently doing the very long lolipop upgrading screen
Click to expand...
Click to collapse
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.

bibikalka said:
And then soft brick ...
So I wonder now if one could do this :
install 5.2.0 via TWRP
install supersu.zip
and here it gets very tricky:
without any reboots, replace TEE1, UBOOT, and recovery to stock versions 5.2.0
The hope is to end up in 5.2.0 with root. If things fail, then booting into 5.2.0 recovery (which must be installed!!!) should give one an option to do 1) factory reset 2) downgrade to stock 4.5.3 as in here : http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
The problem is that I don't see a way to boot into 5.2.0, and then flash GAPPS after (since your TWRP was replaced by stock recovery earlier). So one would have to install GAPPS those via something like Titanium backup if root does work.
Please, if you already had 1 warranty replacement, don't do this. And, if you replace TEE1 and UBOOT (5.2.0) but not recovery, then you won't have any way to recover.
Click to expand...
Click to collapse
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.

siegesoldier said:
Yes I've used my warranty replacement so I'll be waiting until the official release before breaking my kindle again . How do you stop TWRP from preventing the recovery from being flashed? I noticed it gave a message about protecting itself.
Click to expand...
Click to collapse
Interesting, at what stage of the update did this happen? 5.2.0 file system is slightly packaged and is pain in the neck to peak into, but in 4.5.3 the recovery is updated via a pretty specific command install-recovery.sh , and I cannot find any references to this in updater-script. So I wonder at what stage will this be run. Also, there is no direct image for recovery, one has to reconstruct it as the commands below do. A bit messy ...
install-recovery.sh
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:5888256:6d9d1bbc4172c107db3228ed8d9f97111219c617; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:5370112:c2c686ada1b194050a3c8f05e2102345df48e9ce EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery 6d9d1bbc4172c107db3228ed8d9f97111219c617 5888256 c2c686ada1b194050a3c8f05e2102345df48e9ce:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Edit: It kind of looks like /system/etc/install-recovery.sh will be run at every boot. So I wonder if TWRP just renames it to something and calls it "protection". I guess one can double check the file system after 5.2.0 update while still in TWRP, and see what happened to recovery files.

Help
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.

hawkazn said:
If someone can please help me. I downloaded the update to 5.0, unzipped it, replaced the updater script, but when I zip it back and try to flash it says that it failed. Am I doing something wrong.
Also, if someone has the zip file already and wouldn't mind uploading and sharing it, I would appreciate it.
Thanks for all the help.
Click to expand...
Click to collapse
Last time this procedure ended up with a soft brick. Are you sure you want to pursue this route?

Help
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?

hawkazn said:
Maybe not, but if someone can help me with something else. The developer preview for the camera is extremely sharp and the 4.5.4 really isn't. Is there a way to make it crystal clear and sharp?
Click to expand...
Click to collapse
Meaning exactly what? It'd be possible to replace the camera app, one for another. Do you think some other system stuff is involved such as some sort of settings?
You'll have to find a way to mount the big 5.2.0 system update file as a filesystem, then you could read what's in there, including the camera stuff.

TWRP help
So I downloaded the zip file for 5.0 and it flashed and asked to install super user. I had to download the apk for supersu and then update it.
But the problem is that I lost my twrp. I push the volume + and power and it just reboots. I also lost my play store. Any thoughts how to get twrp back on?

Bricked Nexus 6P

Hello. I have a Nexus 6P on Verizon. I don't know the firmware version. I just know it is 6.0.1. I rooted it a while ago, then unrooted it to take advantage of the Android Pay promotions. I wanted to root again. I installed TWRP. In the TWRP, it said it could install SuperSu for me. I swiped it and it said it installed successfully. However, the phone will not turn on. It is stuck on the android start up screen. I used command prompt and fastboot and typed the "fastboot flash boot.img" (Not exactly like that but something pretty much like that). It did not work. How can I fix it? Do I need to factory reset? Is there a way to not lose my files? Thank you.

flashing the boot.img will give u back the recovery. so now boot into recovery and do a factory reset. u should still have your files in your internal memory.

Gobbling_Monkey said:
Hello. I have a Nexus 6P on Verizon. I don't know the firmware version. I just know it is 6.0.1. I rooted it a while ago, then unrooted it to take advantage of the Android Pay promotions. I wanted to root again. I installed TWRP. In the TWRP, it said it could install SuperSu for me. I swiped it and it said it installed successfully. However, the phone will not turn on. It is stuck on the android start up screen. I used command prompt and fastboot and typed the "fastboot flash boot.img" (Not exactly like that but something pretty much like that). It did not work. How can I fix it? Do I need to factory reset? Is there a way to not lose my files? Thank you.
Click to expand...
Click to collapse
I had the same issue.. I think. I downloaded the original .img files which I found somewhere on the forum. Luckily TWRP has a Flash image feature as well and flashed system.img, Bootloader.img and radio.img. Flashed PureNexus 6.01 and PureNexus Gapps and the latest angler vendor.zip and thank goodness that worked! No idea why ADB was not flashing except for the configuration for USB ADB was turned off on the ROM originally.
Good luck! It was a big sigh of relief for me as I thought I had totally bricked it.

Gobbling_Monkey said:
Hello. I have a Nexus 6P on Verizon. I don't know the firmware version. I just know it is 6.0.1. I rooted it a while ago, then unrooted it to take advantage of the Android Pay promotions. I wanted to root again. I installed TWRP. In the TWRP, it said it could install SuperSu for me. I swiped it and it said it installed successfully. However, the phone will not turn on. It is stuck on the android start up screen. I used command prompt and fastboot and typed the "fastboot flash boot.img" (Not exactly like that but something pretty much like that). It did not work. How can I fix it? Do I need to factory reset? Is there a way to not lose my files? Thank you.
Click to expand...
Click to collapse
Why did you allow TWRP to install that version of SuperSU? It isn't compatible. The only way to get your phone booting again is by flashing the factory images. Don't bother performing a factory reset (as suggested by someone else in this thread), it won't help. You've installed an incompatible version of SuperSU to your system partition, only overwriting that system partition with the stock image is going to help you. You could also flash a custom ROM.
Sent from my Nexus 6P

Heisenberg said:
Why did you allow TWRP to install that version of SuperSU? It isn't compatible. The only way to get your phone booting again is by flashing the factory images. Don't bother performing a factory reset (as suggested by someone else in this thread), it won't help. You've installed an incompatible version of SuperSU to your system partition, only overwriting that system partition with the stock image is going to help you. You could also flash a custom ROM.
Sent from my Nexus 6P
Click to expand...
Click to collapse
Hello. Well I already did try factory resetting. And it did not work of course. And I should have researched before I did that to know I shouldn't. But how do I flash the stock image? I tried using this video.
https://www.youtube.com/watch?v=zrAuJFUmeUA
It is the video I used to root my phone in the first place. In it, I think the guy said he is flashing a new image or something like that. It did not work. Also, what do I do about not knowing what firmware version I have? All I know for sure is that it's one of the 6.0.1 ones. Will it not work if I flash the wrong version? Thank you. Also, sorry for not knowing what I'm doing.

Gobbling_Monkey said:
Hello. Well I already did try factory resetting. And it did not work of course. And I should have researched before I did that to know I shouldn't. But how do I flash the stock image? I tried using this video.
https://www.youtube.com/watch?v=zrAuJFUmeUA
It is the video I used to root my phone in the first place. In it, I think the guy said he is flashing a new image or something like that. It did not work. Also, what do I do about not knowing what firmware version I have? All I know for sure is that it's one of the 6.0.1 ones. Will it not work if I flash the wrong version? Thank you. Also, sorry for not knowing what I'm doing.
Click to expand...
Click to collapse
Flash the latest version of the firmware.
Do not wipe the "user" partition. I think that's what it's called.
Install TWRP then SuperSU Beta 67.
DO NOT LET TWRP INSTALL SU!!!!

Listen man, not to throw more rain on an already crappy day for you.... But the amount of "I don't know's" you're throwing out kinda lends itself to the fact that you shouldnt be toying with your phone in the first place.
EVERYONE has to elarn and start out somewhere, but it seems you need to really go over the basics before doing further damage.
Read this once. twice. and then a 3rd time. then one more time just for good measure...
Then start tinkering and fix the issue. But do NOT do anything, until you READ.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.

In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app

nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.

nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.

MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...

nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.

v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.

nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:

@nhatminhng How did you get your phone fixed? is your phone unlocked?

tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.

nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.

tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.

tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.

v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.

v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

[HELP] Moto G PLus 4 booting only in recovery, not system

Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.

d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk

avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.

d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk

avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.

d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.

d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.

==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).

nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.

d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.

d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:

avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step

d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.

avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".

d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.

d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.

nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.

d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you

d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.

nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?

How the hell do you resotre from bootloops without a full firehose restore? FFS

I've been on OOS A11 stable for a while. I could flash modules, kernels, whatever, left and right no problems. Straight from Ex kernel manager, from fastboot, from whatever.
So I end up doing a full restore for something I was testing. Unlock bootloader again, blah blah all that stupid noise
Any time i touch the boot.img, the whole system goes to crap and stays stuck on animation bootloop.
if i try to boot the magisk patched boot.img its fine. i then proceed to flash it, its still fine. this is the only thing that will either boot or flash... the first time
now, if i try to flash any damned other friggin thing, it takes a crap. try to boot original boot.img? nope, flash it? nope. flash slot_a, slot_b slotless, change slot? no. boot or flash the same exact patched boot you had? no. only full firehose reset.
how the hell do you actually recover this garbage bootloop crap without full reload. something is corrupting the ramdisk?
i am so sick of Android 10 and 11 and SAR bullcrap.
please excuse my rage. its been constant full wipes and data restores FOR SOMETHING SO SIMPLE AS THE DAMNED BOOT.IMG. good forbid you boot a stock kernel .
please understand, this is not from a mod,. or any module, or magisk rom. full clean wipe and install. its been about 9 hours of wipes and testing. not an end user

Tilde88 said:
I've been on OOS A11 stable for a while. I could flash modules, kernels, whatever, left and right no problems. Straight from Ex kernel manager, from fastboot, from whatever.
So I end up doing a full restore for something I was testing. Unlock bootloader again, blah blah all that stupid noise
Any time i touch the boot.img, the whole system goes to crap and stays stuck on animation bootloop.
if i try to boot the magisk patched boot.img its fine. i then proceed to flash it, its still fine. this is the only thing that will either boot or flash... the first time
now, if i try to flash any damned other friggin thing, it takes a crap. try to boot original boot.img? nope, flash it? nope. flash slot_a, slot_b slotless, change slot? no. boot or flash the same exact patched boot you had? no. only full firehose reset.
how the hell do you actually recover this garbage bootloop crap without full reload. something is corrupting the ramdisk?
i am so sick of Android 10 and 11 and SAR bullcrap.
please excuse my rage. its been constant full wipes and data restores FOR SOMETHING SO SIMPLE AS THE DAMNED BOOT.IMG. good forbid you boot a stock kernel .
please understand, this is not from a mod,. or any module, or magisk rom. full clean wipe and install. its been about 9 hours of wipes and testing. not an end user
Click to expand...
Click to collapse
1st remove that swear word before a mod sees it, I can see you're frustrated but there's no need for that, people don't owe you here, they help out of the good of their hearts, nothing more.
2nd be very specific, what are you trying to flash? Sounds like you've been flashing a lot which in itself will eventually become a problem, think of it like filling a glass of water a little each time you do.
Run the remove magisk modules command from adb during boot.
I have the commands in my root/payload thread in guides.
If you've flashed a dodgy kernel or boot img then that's all you need to repair, no need for a full restore.
Fish the stock boot img then follow the below, after that you can flash what you like, just pick one and stick with it.
Here's the command and process
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules

dladz said:
1st remove that swear word before a mod sees it, I can see you're frustrated but there's no need for that.
2nd be very specific, what are you trying to flash? Sounds like you've been flashing a lot.
Run the remove magisk modules command from adb during boot.
I have the commands in my root/payload thread in guides.
If you've flashed a dodgy kernel or boot img then that's all you need to repair, no need for a full restore.
Here's the command and process
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
yes ill look through the OP and clean up swears.
i cant adb because it doesnt boot... the issue is not magisk modules. this is a clean install. always is a clean install.
i am not an end-user, those basic steps would have been done already, thank you
the issue is, the somehow, upong flashing anything other than one specific modified boot.img, the system takes a crap. and then, no other boot.img will boot, including the stock one, or the very boot.img it was on. this is again, on a clean full data and system wipe, and full clean install with the mdm tool. no modules

Tilde88 said:
yes ill look through the OP and clean up swears.
i cant adb because it doesnt boot... the issue is not magisk modules. this is a clean install. always is a clean install.
i am not an end-user, those basic steps would have been done already, thank you
the issue is, the somehow, upong flashing anything other than one specific modified boot.img, the system takes a crap. and then, no other boot.img will boot, including the stock one, or the very boot.img it was on. this is again, on a clean full data and system wipe, and full clean install with the mdm tool. no modules
Click to expand...
Click to collapse
Then you have your answer. The boot img is crap.
How are you flashing it and why are you flashing it?
Boot it then directly install with the correct canary version of magisk.
Run the command anyway, it does clear up a lot of crap, won't hurt.
Plus you don't need to be able to boot to run it, you need to be able to be in the boot process (bootloop animation)
Where did you obtain the patched boot img?

dladz said:
Then you have your answer. The boot img is crap.
How are you flashing it and why are you flashing it?
Boot it then directly install with the correct canary version of magisk
Click to expand...
Click to collapse
friend, please see below. again, i can see that you are under the assumption that i am doing basic noob things...
i am pulling my boot.img, and running it in magisk. patch in magsk. fastboot boot bootpached.img, it works. fastboot flash boot bootpatched.img. it works. reboot. still boots.
flash anything else, and death. if i flash from fkm, exkm, fastboot, always the same. if i try radioactive, blu, elemental, always the same. if i flash back the original boot.img that i pulled, it does not revive, same boot loop (without any system, and thus no adb). if i flash the same bootpatched.img, same thing.
is magisk beta branch not yet supported? it may be that i have been using beta instead of canary... but i remember reading beta branch supporting 11.\
i dont know how else to express to you A. i am not a normal end-user, and B. there is no system boot, and thus there cannot be an ADB...
C:\Users\Tilde\Downloads\1>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
)See how this is empty(
C:\Users\Tilde\Downloads\1>
not to mention, I have NOT isntalled ANY modules. This command will not do anything. FULL wipe, FULL flash. nothing in between. there is nothing to clean...

Tilde88 said:
friend, please see below. again, i can see that you are under the assumption that i am doing basic noob things...
i am pulling my boot.img, and running it in magisk. patch in magsk. fastboot boot bootpached.img, it works. fastboot flash boot bootpatched.img. it works. reboot. still boots.
flash anything else, and death. if i flash from fkm, exkm, fastboot, always the same. if i try radioactive, blu, elemental, always the same. if i flash back the original boot.img that i pulled, it does not revive, same boot loop (without any system, and thus no adb). if i flash the same bootpatched.img, same thing.
is magisk beta branch not yet supported? it may be that i have been using beta instead of canary... but i remember reading beta branch supporting 11.
Click to expand...
Click to collapse
They both support 11.
You keep saying flash, im suggesting you boot, not flash.
Fastboot boot "name of boot.img"
How big is the boot img? What model device to you have?
Also when you do flash are you flashing to both slots??
Also its not a case of being a noob, there's only a certain amount of things you can do.

Tilde88 said:
friend, please see below. again, i can see that you are under the assumption that i am doing basic noob things...
i am pulling my boot.img, and running it in magisk. patch in magsk. fastboot boot bootpached.img, it works. fastboot flash boot bootpatched.img. it works. reboot. still boots.
flash anything else, and death. if i flash from fkm, exkm, fastboot, always the same. if i try radioactive, blu, elemental, always the same. if i flash back the original boot.img that i pulled, it does not revive, same boot loop (without any system, and thus no adb). if i flash the same bootpatched.img, same thing.
is magisk beta branch not yet supported? it may be that i have been using beta instead of canary... but i remember reading beta branch supporting 11.\
i dont know how else to express to you A. i am not a normal end-user, and B. there is no system boot, and thus there cannot be an ADB...
C:\Users\Tilde\Downloads\1>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
)See how this is empty(
C:\Users\Tilde\Downloads\1>
not to mention, I have NOT isntalled ANY modules. This command will not do anything. FULL wipe, FULL flash. nothing in between. there is nothing to clean...
Click to expand...
Click to collapse
Dude, you need to chill. Good luck finding your own way, maybe learn to be more grateful when somebody is offering help.

dladz said:
They both support 11.
You keep saying flash, im suggesting you boot, not flash.
Fastboot boot "name of boot.img"
Also when you do flash are you flashing to both slots??
Also its not a case of being a noob, there's only a certain amount of things you can do.
Click to expand...
Click to collapse
hi. look. i appreciate you trying to help... but you are not reading my replies. i have coutnless times explained that yes i am running fastboot BOOT ... i ALSO (meaning in addition AFTER failing a boot) do attempt a fastboot FLASH boot.
again, i thank you for your attempt at helping, but you are dismissing everything i say. i see that you help a lot of people with this basic information, but understand, it is not applicable to this case. thanks anyway

dladz said:
Dude, you need to chill. Good luck finding your own way, maybe learn to be more grateful when somebody is offering help.
Click to expand...
Click to collapse
you are parroting information at me. information that i have already explained. again, thank you for your effort, but you are far too dismissive, and do not read what i type. take care.

Tilde88 said:
hi. look. i appreciate you trying to help... but you are not reading my replies. i have coutnless times explained that yes i am running fastboot BOOT ... i ALSO (meaning in addition AFTER failing a boot) do attempt a fastboot FLASH boot.
again, i thank you for your attempt at helping, but you are dismissing everything i say. i see that you help a lot of people with this basic information, but understand, it is not applicable to this case. thanks anyway
Click to expand...
Click to collapse
It's your boot img and or the way you're flashing it / booting it.
I'm done with your attitude.
Good luck.
PS I've been in bootloops for the same reason and it's worked for me..

dladz said:
It's your boot img and or the way you're flashing it / booting it.
I'm done with your attitude.
Good luck.
PS I've been in bootloops for the same reason and it's worked for me..
Click to expand...
Click to collapse
and i have explained in detail that it is not working as usual. thus, your usual steps do not do anything. again. thanks anyway, but you are refusing to read. have a nice day.

i think this is solved. something was bugging the database i am working on. was not boot.img related at all, it is SAR in the end. this is why even after flashing stock boot.img it would do nothing, because it was a /system issue with the something deprecated or not yet ready for SAR/a10-11

Tilde88 said:
i think this is solved. something was bugging the database i am working on. was not boot.img related at all, it is SAR in the end. this is why even after flashing stock boot.img it would do nothing, because it was a /system issue with the something deprecated or not yet ready for SAR/a10-11
Click to expand...
Click to collapse
You said you wiped? Like I said be specific.
Nvm you're done now

dladz said:
You said you wiped? Like I said be specific.
Nvm you're done now
Click to expand...
Click to collapse
correct, i did wipe, and i informed you as such so as to deter you from the "disables modules" path you were stuck on, as this was irrelevant.

Tilde88 said:
correct, i did wipe, and i informed you as such so as to deter you from the "disables modules" path you were stuck on, as this was irrelevant.
Click to expand...
Click to collapse
If you wiped then how could SAR have affected it?
If it's in system then it wouldn't have.
Again!!! Be specific. You left that part out.
Don't worry about it.

dladz said:
If you wiped then how could SAR have affected it?
If it's in system then it wouldn't have.
Again!!! Be specific. You left that part out.
Don't worry about it.
Click to expand...
Click to collapse
i kept doing it kinda like blind instinct. just part of my setup process. didn't even realize i was triggering event.