Database Users

[Q] Bootlop after unlocking bootloader + flashing cwm

Hi Everyone, I'm new to the Nexus 4, and I unlocked the bootloader and installed the CWM Recovery using this guide. http://au.ibtimes.com/articles/53036...at-install.htm
Everything went correctly and after I installed CWM and wanted to reboot my device, it asked to remove the stock recovery, I said Yes (there was no mention of this in the article, but i remembered how annoying this was with a previous device, so i agreed to that), as I needed to install Superuser from a ZIP, i selected No when i was prompted to root the device (from CWM). after those two questions, the phone rebooted, and now it's in a bootloop (on the bubbles boot screen, (4.4.2). Is there any way to fix this?.

Try going into recovery and doing a factory reset or wipe cache.

It's a bug with Nexus devices and bootloader unlocking. After unlocking the bootloader, you need to do a full reboot before going back in and flashing a custom recovery. See the article below about the bug. You need to re-flash the stock recovery to get out of the bootloop.
http://www.androidpolice.com/2013/1...locking-your-nexus-or-gpe-devices-bootloader/

I think my system portion is corrupt... Any chance of saving it?

I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.

Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.

PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail

Bumping to see if anyone else can help...

Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom

Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good

Downgrading from Nougat to Marshmallow

I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk

Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !

hutzdani said:
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
Click to expand...
Click to collapse
Yeah, so many stories of expensive paperweights when trying the downgrade. I suspect they're having some major issues with the 6p factory image, since the 5x has been posted for nearly two weeks. I've got mine working pretty well, with really good battery and ARISE sound actually working system-wide. I suspect we may see the factory image when this month's security update is rolled out - at least I hope so, given we're already into September.

That's what I figured. Looks like I'm staying on N. Thanks!
Sent from my Nexus 6P using Tapatalk

@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.

Great thanks! I'll give it a go
Sent from my Nexus 6P using Tapatalk

RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Works fine, thanks!

RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?

srt4mn said:
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
Click to expand...
Click to collapse
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.

RoyJ said:
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
Click to expand...
Click to collapse
Thanks! I'll give it a shot here after I figure out this bootloader usb data cable issue.
EDIT:
Got back to 6.0.1 after following your instructions, thanks again!!

Worked like a charm. Thanks @RoyJ!

No problem, glad it worked for everyone.

I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.

bmwkeith said:
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
Click to expand...
Click to collapse
So your in PN MM with new nougat modem and bootloader ?

dutchy716 said:
I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey so I actually bricked my first Nexus 6p doing this but I have been fine with my replacement. The Key is to update your twrp to 3.0.2-2 (make sure you do this). I then from Android 7 did a full backup in Twrp and then in the bootloader flashed the MTC20F factory image and it rebooted just fine. I guess in Twrp 3.0.2-1 there is an efs partition problem that is causing the bricks; my old bricked nexus 6p was on 3.0.2-1. So just please make sure you flash 3.0.2-2 twrp

ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
Yes, and everything is working fine.

ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.

rndll said:
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
Click to expand...
Click to collapse
Yes. Already try it and everything is working fine.

What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.

NedbuR said:
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
Click to expand...
Click to collapse
Did you sideload 7.0 or upgrade from the beta program?
Sent from my Nexus 6P using Tapatalk

Please help, possible bricked phone???

Hey guys so my phone appears to me to be bricked. I have a rooted angler on stock 7.0.0 (NBD90X, Oct 2016). I have ElementalX kernal.
A few weeks ago I was looking in to putting on MultiROM. After I flashed the custom TWRP recovery for MultiROM, the recovery wouldn't work. It just goes to the TWRP blue startup screen and freezes. I have been procrastinating on flashing a functioning recovery ever since. I know, I'm an idiot. Lesson learned. Well the November security update was pushed to my phone a few days ago. I ignored it. Last night I wanted to see if the update included 7.1 or if it was just security update, so I tapped on the update notification and it automatically downloaded the updates without prompt (which I did not want to do.)
Well an hour later my phone died. When I plugged in to the charger, it immediatly started up by itself and booted to the non-functioning recovery and froze. It does this every time I try to boot the device now. I booted in to the bootloader and tried plugging in to my PC to flash a working recovery, but the device will not get picked up by the PC anymore. I don't believe it's a driver issue I use adb all the time with this same device and pc.
Also want to add, factory reset from bootloader went to google startup animation, but then just shut off as soon as it was done. Also, when I select shutdown from bootloader with it plugged in to charger, it will turn off and stay off but does not appear to be charging in any way.
Well that's the backstory. Any help you all can provide is very much appreciated. Turns out the battery in my backup phone is only good for a couple hours anymore. You all know how helpless we are without our phones, ha! Please help! Is it bricked?

I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.

RoyJ said:
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
Click to expand...
Click to collapse
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Edit: If you can boot to bootloader your device should be read with 'fastboot devices' - if it isn't, delete any Android / Nexus / Google drivers. **Reboot your PC** and install them again. After you install them again reboot your PC one more time and try again.

RoyJ said:
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Click to expand...
Click to collapse
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.

Nebul0us said:
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Click to expand...
Click to collapse
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.

RoyJ said:
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
Click to expand...
Click to collapse
Okay so I left the phone on the charger with the frozen screen in twrp multirom edition. After that rebooted in to the bootloader. I then selected the factory option. If loaded the google animation like before, but this time actually booted up the system. The notification bar had two diagnostic tools that said tap to run...one was called sims i think? Anyways I held power button and did a hard reboot. It booted up fine. I then used twrp manager to install 3.0.2.2....then i used fastboot to flash 3.0.2.3 that i had a copy of. Things seem to be working fine now. Close call. I'm not sure what the factory option is in the bootloader, but it's not factory reset and it was the only way I could boot. I think the phone was trying to boot to recovery to install the latest updates and I had to boot to factory to get it out of "update mode," if you will...
Does anyone know what the factory option is in the bootloader?
Thanks for your help RoyJ

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Factory options is meant to restart the system with some manufacturers apps available just so you can test certain functions of the phone, mostly to see if all sensors and hardware are working properly.

Soft bricked Zenfone 3 still have TWRP

I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.

Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.

android_101_ said:
Do you have an official recovery? If yes, you can recover back your device again. Just use 'adb sideload <filename>' to do this.
I've also trying to unroot my device and end up in boot logo, but after flash the official ROM, it's finally work again. Also my data (/data) isn't formatted.
Click to expand...
Click to collapse
I only have the Twrp recovery.

Canukboy said:
I only have the Twrp recovery.
Click to expand...
Click to collapse
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?

wang1chung said:
TWRP supports adb sideload but there's no point flashing stock recovery, TWRP is superior in every way.
Go into TWRP, plug in your USB cable and it'll mount your sdcard . Copy the firmware onto the sdcard and install it. Perform a wipe cache/dalvik and reboot.
How are you removing root?
Click to expand...
Click to collapse
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.

Canukboy said:
I used a app called KingRoot while I was on the bus, it caused the phone to freeze, after about 10 mins I hard reset the phone and it has not worked since.
I tried to sideload the stock rom, but it will not accept it. I think I may have something to do with the bootloader. I think my TWRP recovery could be in the Android partition, but I am unsure.
Click to expand...
Click to collapse
Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.

Forget sideloading it, edit the update script in the firmware, see this
thread, part 1, step 2-4.
Then copy the firmware to your sdcard (like I mentioned above) and install it. You can use the guide here, tip #4. You should read the entire guide afterwards.
if TWRP loads when you select recovery, it's on the correct partition. You'll have to reinstall TWRP after you flash the stock Rom again as it'll update recovery as well. Then create an nandroid backup, tip #2 and you're set.
Click to expand...
Click to collapse
Hy Wang.. I followed your guide - modified updater-script, but I can't install the stock rom .zip from TWRP.
It says "can't extract updater-binary", I tried few times thinking that the file is corrupt, but the result still same.
FYI, I use stock ROM "UL-ASUS_Z012D-WW-14.2020.1709.68-user.zip", and TWRP 3.1.1.
Please help me if you have experienced it before. Thanks

@rzahunn
I've never had that error before and you're on the latest version of TWRP so I'm going to guess it has to do with your modification of the updater script.
You edited updater-script not updater-binary, correct? There are two files with similar names

There's a detailed guide by @kyle_l88 on how to return to stock.
Here's the link: https://forum.xda-developers.com/zenfone-3/development/how-to-to-stock-rom-recovery-zenfone-3-t3666223
Do note that the original recovery link is dead. The updated link is: https://mega.nz/#F!LIhwiCia!b_pyuHXS9E7f2VbyXcLyXA

TWRP Bootloop
Sorry if my reply is irrelevant, but I need some helps.
I am also using Zenfone 3, but stuck in TWRP bootloop.
I cannot flash using fastboot (not detected on PC), reflashing ROM doesn't help either.
I've tried all the possible methods I found on Google, such as dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota method but still has no luck.
Restoring backup would end me in TWRP too.

@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.

wang1chung said:
@Xytce
Are you factory resetting after you flash? Clearing cache and dalvik? It will take 5-10min to boot up initially after that.
Otherwise, try the guide Rizzed referenced.....as long as you have the correct firmware and TWRP flashes successfully, there's no reason it shouldn't work that I can think of.
Click to expand...
Click to collapse
I've managed to fix the bootloop after following the guide. I missed that somehow, thanks for pointing that to me.
I've thanked you (pressed the Thanks button).

dm verity
Canukboy said:
I have a Zenfone 3 that while trying to unroot I have soft bricked. I can get into TWRP recovery, but after installing the tizen ROM, I can not boot into it, but can still access the TWRP recovery. Is there a toolkit or any suggestion you might have as to how I could fix this issue.
Click to expand...
Click to collapse
does it hangs on logo then start again? then reflashing the rom then flashing the dm verity zip again hope it works