Related
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
When you plug in the usb to the computer do you get any change in windows device manager? like an unrecognized kindle fire (yellow triangle) under usb or similar?
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...
seecay said:
Looks like you might need to reflash. Don't forget to do a wipe/factory reset...
Click to expand...
Click to collapse
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium
stewtang said:
I can't get to recovery and my pc doesn't recognize the kindle, so I can't reflash
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
That's a strange problem. Have you tried to reinstall the drivers or use a different PC? If it can get into the boot animation, you should theoretically be able to get into recovery/TWRP... Sounds like a bad flash may have happened so try a newer/older build. I hope it goes ok...
Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.
Thepooch said:
Use this to replace the the one in kfu driver folder http://db.tt/vXXeuL10 and rerun the driver bat, that will get adb going again. Try reboot recovery to enter recovery or use kfu to set your bootmode to recovery. Bootloader? fff will take you to recovery as well.
Click to expand...
Click to collapse
I replaced the file and still shows ADB status as offline and boot status as unknown. The computer makes the noise that a device is connected once the kindle reaches the CM screen but the that is it, ADB is still offline. Also, the kindle fire logo at start up is no longer blue, it has reverted to the stock orange color.
stewtang said:
I flashed cm10.1 and latest gapps after rooting with kfu and going to twrp to flash zips. After rebooting the kindle stays on the rotating CM splash screen. Is there anything I can do to revive my kindle. I can't get my PC to recognize it and I can't get to recovery. I have the correct drivers installed bc i used the kfu only a few hours ago. Any help would be greatly appreciated
Click to expand...
Click to collapse
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...
guruizzy said:
I have the same problem with CM 10.1 with the splash screen. It loads through FFF 1.4 and gets to the spinning splash screen which appears to be half off the screen and just sticks there. I used the 0102 version of the JB 4.2.1 CM10.1 SGT7 rom by twapriv. When I flashed it using TWRP 2.2.2.1 it said "successful". I try to install the 121212 Gapps zip and it wouldn't work, saying unable to unzip. However, after a reboot the splash screen does what I just mentioned.
It appears we aren't the only ones though (http://forum.xda-developers.com/showthread.php?t=2051331&page=24) according to stewtang's post. I guess I'll retry to flash an older version and see if that works. Anyone have this problem and found a fix for it?
Hah! OMG I so totally didn't realize that stewtang was the OP, LAWLEROFLCOPTEROMGWTFML...
Click to expand...
Click to collapse
Any luck getting into recovery? If so, how did you do it?
stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
I have always been able to get into recovery. However, I did find that my /system/bin/sh file and all other system files are completely missing. I have yet to fix this, as this could be some of my problems. I don't know I'm still a noob at this. I have reflashed TWRP 2.2.2.1 while in fastboot mode using a factory cable. I just bought one for $6 on ebay from a US seller. Using this cable I find that the KFU works more like it should. It actually tells what boot mode status is currently instead of just saying unknown.
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether? Again, uber noob here.
guruizzy said:
I know I did something wrong or out of order when I tried to root my KF because it is very difficult to do an ADB PUSH command successfully. It takes a few reboots and then a trial and error until it works right. As for the latest 0102 update for CM10.1 and SGT7, I haven't been able to get passed the cyanogen splash screen.
I would like to know if that update includes all the files necessary to run JB 4.2.1 or is it a completely different OS altogether?
Click to expand...
Click to collapse
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.
jma9454 said:
So a question for both of you. Did you do a clean install (wipe everything but SD card)? Also does it hang on the CM screen or does it endlessly reboot? Did either of you have previous ROMs installed?
When I installed CM10.1 on my friend's kf, at first that happened. I don't know what happened, but it took me a couple tries before it worked. Try redownloading the ROM and Gapps, and remember to wipe everything beforehand, and wiping cache before flashing Gapps.
Click to expand...
Click to collapse
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Sent from my Galaxy Nexus using xda premium
stewtang said:
Any luck getting into recovery? If so, how did you do it?
Click to expand...
Click to collapse
Looks like you may not have FFF so you probably can't get into TWRP... Have a look at this thread.
http://forum.xda-developers.com/showthread.php?t=1428428
stewtang said:
Yes. I performed a clean install and unfortunately I am unable to re-flash anything. When the kindle boots it endlessly stays on the cm splash screen and I can't enter recovery or use the kfu.
Click to expand...
Click to collapse
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?
jma9454 said:
So for you, when you turn on from off, possibly from a hard force-restart, what do you see? The original orange kf logo? And it goes straight to the swirling cm logo?
Click to expand...
Click to collapse
Yes that is what I see, but before I flashed it the kindle fire logo was blue.
Sent from my Galaxy Nexus using xda premium
I had the same thing happen to me when I flashed my kindle fire demo unit with CM10.1, it turned out to be some sort of an issue with the twrp recovery when I reflashed it with the cotr recovery that the kindle fire utility program also has as a alternate this worked just fine. I did notice that when I tried to use twrp to wipe my unit it didn't seem to fully wipe the unit. doing the same thing under cotr took longer.
The reason I think it was twrp is that no matter what version of CM10.1 I used be it a nightly or the M3 experimental build, it would still just show the distorted logo and never finish booting. this happened even after I wiped the /system and cleared cache and dalvik cache.
After I flashed cotr recovery I did the same thing again using the exact same zip files for CM10.1 and gapps and it worked this time.
I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?
I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.
andreasS2 said:
I have a similar problem with you guys. My Kindle is showing the orange logo and then continues to the CyanogenMod animation where it loops infinitely. The logo is also off center, half of it is off the screen. I cannot enter the recovery mode in any way. KFU shows it as online but unknown boot status. ADB shows it as offline.
Any suggestions on how to fix it? Will I need a factory cable?
Click to expand...
Click to collapse
yadspi said:
I'm in the same boat, tried soupkit in linux and no dice, windows recognize a device while the CM logo is looping but the kindle drivers or adb drivers do nothing.
Click to expand...
Click to collapse
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.
soupmagnet said:
In both of your cases, if you don't have FireFireFire installed which will allow you to access recovery with the power button, you need a factory cable. And remember to factory reset next time.
Click to expand...
Click to collapse
I did, I was going to sell it with CM10, I rebooted, did a factory reset, reinstalled cm.zip and gapps.zip and rebooted....lost firefirefire and stuck on CM logo. If I buy or make the factory cable, will it be easy to "revive"?
Edit: Saw it on eBay for $4.45 free shipping
I tried to root my N7 (2013) today and i ended up with a black screen.
I used these instructions, but got a bootloop on the Nexus Logo.
http://forum.xda-developers.com/showthread.php?t=2382051
So i tried to do a factory reset via TWRP, without luck (errors in twrp)
I couldn't even mount to get an ROM on the device.
Then i tried to do a factory restore with the *.img files from:
http://forum.xda-developers.com/showthread.php?t=2381582
Still no boot (only nexus logo).
So i tried to do a factory reset via the stock recovery.
After this all i got is an black screen.
First i thougt it was hardbricked. But i recognized that the device manager from windows 7 shows the device.
could not get adb to work while it shows "Android ADB Interface"
But if i turn it off and boot with volume down pressed i can get into bootloader ("android bootloader interface" at device manager)
And then i can connect via fastboot. but still nothing on the screen...
Is there more to restore than recovery/system/boot ? any display driver or kernel, so that the screen will start working again?
Otherwise i will go to the store and get me a new one.
Have you tried to reflash twrp? Or flash cwm instead? Mine didn't want to take twrp but flashed cwm without issues.
Sent from my SCH-I535 using Tapatalk 4
If you can get into bootloader (ie. fastboot sees the device), you should be able to at least throw the stock image back on there by running the included flash-all script provided by Google.
You should be able to replace the recovery as well. TWRP2 works nicely for me. Maybe download your copy again (http://techerrata.com/browse/twrp2/flo) and check the md5 has to make sure your download is good. Then flash with "fastboot flash recovery <*.img>". From there you can then install whatever you want.
As long as you can get into the bootloader, your options are many.
i just tried the flash-all script provided by google.
But still just a black screen...
I could flash a custom recovery, but i think this would not help the display problem.
if no one else have an idea for a solution i will lock the bootloader and bring it to the store tomorrow.
edit: got a new one. already rooted and with working twrp.
Hello,
I have a kindle fire 2 and recently rooted it using this guide, http://forum.xda-developers.com/show....php?t=2075959, and then I used this guide, http://forum.xda-developers.com/show...light=recovery, to add twrp so I can flash CM. Everything seemed to go well except that I am unable to enter recovery mode. When booting normally it works fine and loads into the kindle OS but obviously, I want to replace that. I have tried searching the forums and trying a few different things but so far nothing has worked. I'm open to any suggestions or ideas.
You try "adb reboot recovery"? Or a similar from a terminal or adb shell like this: su -c "reboot recovery"
That should get it to recovery, if it doesn't then consider reflashing recovery and check the md5sum of the files this time to make sure it's intact.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You try "adb reboot recovery"? Or a similar from a terminal or adb shell like this: su -c "reboot recovery"
That should get it to recovery, if it doesn't then consider reflashing recovery and check the md5sum of the files this time to make sure it's intact.
Click to expand...
Click to collapse
I tried this already and made sure to check the md5sum. Ill try reflashing again. Thanks for the help! Hmm the reboot recovery seems to give me a red triangle.
twrp
lysol_disinfectant said:
Hello,
I have a kindle fire 2 and recently rooted it using this guide, http://forum.xda-developers.com/show....php?t=2075959, and then I used this guide, http://forum.xda-developers.com/show...light=recovery, to add twrp so I can flash CM. Everything seemed to go well except that I am unable to enter recovery mode. When booting normally it works fine and loads into the kindle OS but obviously, I want to replace that. I have tried searching the forums and trying a few different things but so far nothing has worked. I'm open to any suggestions or ideas.
Click to expand...
Click to collapse
Flash 2.6.3.1 I had issues not booting into twrp with 2.6.3.0 and had to search other places to find 2.6.3.1 for hte kf2. After I flashed to the update from ADB it booted recovery just fine.
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Try flashing the recovery again. Download it from the link provided here and confirm the md5 checksum for the zip file.
http://forum.xda-developers.com/showthread.php?t=2694564
Sent from my HTC One_M8 using XDA Premium 4 mobile app
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
some reason doing twrp from terminal on hte m8 gets us stuck (it did for me at least.)
just reflash the insecure boot image.. fastboot flash boot blah.img
that should get you back up
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
darll said:
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
Click to expand...
Click to collapse
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
PirateP3t3 said:
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
Click to expand...
Click to collapse
I followed the instructions on the TWRP site:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
But that left me in a TWRP bootloop. Can you please give me step by step instructions on how to get out of this bootloop?
Thanks!
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, then swipe for a factory reset (Advanced wipe cannot properly wipe cache and dalvik after fastboot erase cache)
then go to advanced, select cache, dalvik and system and swipe to wipe those partitions.
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
exad said:
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, advanced, select cache, dalvik and system
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
Click to expand...
Click to collapse
Thanks for the detailed instructions. I opened fastboot on my PC with phone plugged in and entered the code but the cmd prompt just says <waiting for device>
Do you have the HTC drivers installed on your PC with HTC sync uninstalled?
Does it say fastboot USB on your phone?
Sent from my HTC One_M8 using xda app-developers app
Update: I ended up just installing the Viper ROM and the system rebooted fine. It's strange that I couldn't reboot the device to get out of recovery without having to install a custom ROM.
Sent from my HTC6525LVW using Tapatalk
No it's not. You flashed recovery to the boot partition.
Sent from my HTC One_M8 using xda app-developers app
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
I hav custom cm11 Kitkat ROM installed on it...
but after I installed the rom, and again tried to reboot
into TWRP recovery, it is just stuck on the blue color
TEAMWIN screen... Please help how to fix it...!
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Maxxour said:
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Click to expand...
Click to collapse
You need cwm recovery to factory reset from cm roms.
Also you need to be in FASTBOOT mode for it to detect your device.
Boot to fastboot, erase cache, reinstall twrp.
Next time reset/wipe from recovery.
ashyx said:
You need cwm recovery to factory reset from cm roms.
Click to expand...
Click to collapse
cwm recovery or cm recovery?
Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.
I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.