[Zenfone 3 ZE552KL] Won't boot to system - Asus ZenFone 3 Questions & Answers

Hi,
After doing some unlocking, installing recovery then rooting. I was able to complete root process but i had an issue where my sim cards were not detected. Foolish me, i tried to do a factory reset in the settings and it turns out that my system was not recovered back. Now, it is looping on TWRP and can't boot back to system. Not sure what to do next...
Done fixing: i flash back the original recovery. Stock recovery automatically proceed with "erasing" then it autoreboots. Hope this help others encountering the same problem. To prevent this, just don't do factory reset via system setting when having custom recovery.

jhonny173 said:
Hi,
After doing some unlocking, installing recovery then rooting. I was able to complete root process but i had an issue where my sim cards were not detected. Foolish me, i tried to do a factory reset in the settings and it turns out that my system was not recovered back. Now, it is looping on TWRP and can't boot back to system. Not sure what to do next...
Done fixing: i flash back the original recovery. Stock recovery automatically proceed with "erasing" then it autoreboots. Hope this help others encountering the same problem. To prevent this, just don't do factory reset via system setting when having custom recovery.
Click to expand...
Click to collapse
hello, the same thing happen to my phone and i want to ask where can i get the original recovery file?

Related

Stock on Samsung Logo with Custom Lock Image

I had Mint Jelly2.1 installed and everything was working fine.
it started when I had used the APK Hide It Pro. I was in the process of hiding videos and I noticed that my phone got rebooted and got stock in the Samsung boot up image with the Custom Lock image.
I tried nandroid restore, 2 images, but both also failed to restore / bootup.
I tried re-installing ROM and it was successful but during reboot, it will still get stock on the boot image.
Last step.
I used ODIN to restore the stock ROM and ODIN was able to install and reset. And my phone rebooted but still got stock on the Samsung Logo with CUstom Lock Screen.
What else can I do to fix this?
Thank you.
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
I had tried to restore/flash from recovery before ODIN and it all Failed.
Anyway, the last step ODIN restore and it was still stock at the Samsung Logo with Lock image.
I left the phone to charge the whole night and this morning when I turned it on, it was able to start properly with ODIN stock ROM.
I tried to go to recovery, and can only be done manually, and it was not the TWRP recovery but the stock one, with very small characters.
I tried to install Mint Jell2.1 right away but just reboots.
I realized that I might need to root it again and downloaded the Tool and re-loki'ed/rooted and installed TWRP.
Now, I am able to install Mint Jelly 2.1 and restoring all my apps.
I appreciate the comment.
Thank you.
scott14719 said:
Boot into recovery and do a factory reset. I assume you now have 3e stock recovery because of ODIN. This might or might not help. If you have any questions about recovery, please use the search function for information. If for some reason you still have a custom recovery (TWRP or CWM), try re-flashing an AT&T ROM and Kernel again. Everything you try is at your own risk. Good luck.
Click to expand...
Click to collapse
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
CZ Eddie said:
Yeah, every single time I ODIN back to stock, I get stuck at the splash screen also. And rebooting to 3E (factory) recovery and "restore factory defaults" works great.
Click to expand...
Click to collapse
I can confirm this works happened to me yesterday.
leoj85 said:
I can confirm this works happened to me yesterday.
Click to expand...
Click to collapse
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
I got stuck to 1st boot image of Samsung with Lock Custom Icon.
I did format data/factory reset/clear cache/dalvik.. all of the wipe ootions.
I flashed a new ROM, successful, rebooted pass the logo and booted fine. I did not change any settings yet and I rebooted to check if it will get stuck again and sure after reboot, it got stuck again on the 1st image that shows up : Samsung Logo with the Lock Custom Icon.
qwer43 said:
I am running out of options. I thought I am already out of this stuck on Samsung Logo with Custom Lock icon.
I had ODIN to stock I337UCUAMDL and reset, Ran Loki patch / installed TWRP, intermittently it will get stuck.
I flashed Shoshock 1.9, was able to reboot and setup basic settings.
I manually reboot to check if it was able to fix the problem, but no.
I am stuck again and don't know what is the next step for trouble shooting it.
any advise will be appreciated.
Thank you.
Click to expand...
Click to collapse
IMPORTANTwhen using*twrp*recoverydo not choose "format data"(that option will ask you to type "yes")what if i did?rom will not boot past "padlock" boot screen orrom will not boot on second reboot*help!! I did, I did*1. sigh2. d/l odin3. d/l odin stock restore MDL4. let it do its thang5. after its complete it will be stuck at padlock6. should have "rtfm" huh?*7. pull battery8. hold home button, vol-up, power at same time9. when phone vibrates, release power, while still holdingvol-up, and home button10. you will now be in "stock recovery"11. wipe factory reset then wipe cache12. reboot*13. swear you will never "ignore instructions"

[Q] Bootloop on restore-backup and problems encrypting with cwm

Hi. First post so apologies if I get anything wrong. Please let me know and I'll happily correct.
Picked up a SM-N9005 and successfully flashed CWM and rooted using heimdall. I then ran into two problems.
First I tried to Encrypt the device - (I need this for my ActiveSync device permissions to work so I can get office emails) and the device wouldn't encrypt. It starts the process (asks for a password confirmation only, not a new password), and then powers off and on back to brightly colored password screen.
So, I thought it might be the rooting process that had caused the issue. so I did a cwm backup and a factory reset. (foolishly ignoring the the message on the rooting thread OP). The phone still didn't encrypt so I decided to download the stock rom and revert to the old recovery.img. The plan was to go to the stock recovery, encrypt and then reflash cwm.
While waiting for the stock rom to download I (still foolishly) decided to restore all my apps and data since it clearly wasn't the problem. and... bootloop.
So my questions are :
1) Is there any way to fix the bootloop without reflashing the whole stock rom?
2) How do I encrypt the phone? Is this a clockworkmod issue?
3) How do I backup the phone - would a Titanium backup zip work or am I just going to put my phone into a loop again?
Thanks
-------------------
Further edit. I had a pit I pulled down when I first got the phone (I've bricked them before). Adding to @Nani's response below. I've tried flashing the stock rom and I get a PIT upload failure. It doesn't recognize the PIT and hiemdall can't detect a PIT on the device.
tahnoonp said:
Hi. First post so apologies if I get anything wrong. Please let me know and I'll happily correct.
Picked up a SM-N9005 and successfully flashed CWM and rooted using heimdall. I then ran into two problems.
First I tried to Encrypt the device - (I need this for my ActiveSync device permissions to work so I can get office emails) and the device wouldn't encrypt. It starts the process (asks for a password confirmation only, not a new password), and then powers off and on back to brightly colored password screen.
So, I thought it might be the rooting process that had caused the issue. so I did a cwm backup and a factory reset. (foolishly ignoring the the message on the rooting thread OP). The phone still didn't encrypt so I decided to download the stock rom and revert to the old recovery.img. The plan was to go to the stock recovery, encrypt and then reflash cwm.
While waiting for the stock rom to download I (still foolishly) decided to restore all my apps and data since it clearly wasn't the problem. and... bootloop.
So my questions are :
1) Is there any way to fix the bootloop without reflashing the whole stock rom?
2) How do I encrypt the phone? Is this a clockworkmod issue?
3) How do I backup the phone - would a Titanium backup zip work or am I just going to put my phone into a loop again?
Thanks
Click to expand...
Click to collapse
We are now a few to have encounter this bootloop issue.
At this time there's no good way ... I had to hard reboot a few times and the only workaround i found is that boot loop occurs only when phone is on (meaning there's no boot loop in "Plane Mode"). So i hope a fix/patch will be provided soon by Samsung thru a new firmware. By the meantime i try not to reboot when "Plane Mode" is off.
What i do know is I tried a lot of configurations with no result :
- reboot with SD card removed => bootloop
- reboot with SD card removed and in "Secured Mode" => bootloop

4.4 OTA update. Stuck at splash screen

Ok do I did search first but can't find anyone with the same problem.
Started with stock 4.3 rooted, unlocked,TWRP.
Got the update notification, told it to update. It auto rebooted to TWRP and applied the update with no error. When it was done (assuming it was done progress bar finished) it went to the main TWRP menu. I told it to reboot and it just sits at the new 4.3 splash screen animation. I assumed it may take a bit so I let it sit for about 20min with no change. Rebooted it a couple times, also tried applying the update again via twrp (errors out as i woukd expect). Wiped dalvik and cache. Didn't do a factory wipe because I'd like to avoid that but still no change.
Any suggestions? Should I manually load the full 4.4 package via TWRP?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Same exact setup... Say exact issue... Oh and before rebooting I wiped Dalvik and Cache as "Sandard Operating Proceedure" ... I'm going to just do a clean flash at this point....
Tracy
Hi
I have the same problem. had a rooted 4.3, and after the update the screens remains on the splash thing. restarted a couple of times, did wipe data, factory reset, and it still remains stuck at the boot. What should i do. pls help
step944 said:
I have the same problem. had a rooted 4.3, and after the update the screens remains on the splash thing. restarted a couple of times, did wipe data, factory reset, and it still remains stuck at the boot. What should i do. pls help
Click to expand...
Click to collapse
Prior to the installation of the OTA it is safer to re-install stock recovery. Root is lost but re-installing a custom recovery and SuperSu bring back root.
gunner1937 said:
Prior to the installation of the OTA it is safer to re-install stock recovery. Root is lost but re-installing a custom recovery and SuperSu bring back root.
Click to expand...
Click to collapse
How can i install stock recovery?
You *could* unzip the factory image and then fastboot the recovery.img file. A lot easier is to download the wugfresh nexus root toolkit and use that:
http://www.wugfresh.com/
ty, but do u think it works, because i cant open my nexus 10 memory from the pc, since it is stuck at start up
Wug's toolkit has an option to restore to stock from a bricked system. All you need to be able to do is to get to the bootloader (press the power button while holding down both volume buttons -- you should get a dead android with a red triangle on chest).

Help, TWRP wont recover get past boot screen

So Ive been running CM13 and TWRP, when supersu tries to install via twrp and boot loops the phone, went to reinstall the os but had an issue with twrp and now twrp wont boot up proper, and the os wont let me get past setup because of the stupid dropdown menu. before I factory reset is there a way to odin in and repair the recovery?
thanks
edit: eventhough the rooting process is so long, im just going to flash stock and start over. thanks.

Is there anyway to enable SDCARD Upgrades from adb?

So, my stupid completely stock A2017U started bootlooping (hey, did LG make these?). cache wipe, factory reset all didn't help, so I'm down to trying to do the full SD upgrade. However, the phone won't stay booted long enough for me to get into settings to enable OEM unlocking. Is there a way to do it from adb in recovery? The phone stays booted perfectly fine in recovery, so I'm guessing something got corrupted in a system partition somehow (emmc cell failure maybe?).
If not, I'll have to EDL it first, but I'd rather stay official if possible.
adb sideload is giving me problems, but it maybe that I don't have enough memory for that.
I take it you are not rooted? Reason I ask is I just experienced a boot loop after updating SuperSU. The solution was to install the previous version of SuperSU from recovery.
MyronAz said:
I take it you are not rooted? Reason I ask is I just experienced a boot loop after updating SuperSU. The solution was to install the previous version of SuperSU from recovery.
Click to expand...
Click to collapse
No, I'm stock everything. If I could get the damn thing to boot up enough again to get into settings, I could enable OEM Unlocking and then use the sd card method. But it won't stay up that long through the setup wizard.

Categories

Resources