Unable to boot - One (M8) Q&A, Help & Troubleshooting

Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)

JunkTardis said:
Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)
Click to expand...
Click to collapse
best thing is go to recovery factory reset and flash viper again
get to recovery by power vol down just in case you dont know

JunkTardis said:
Okay so this is my first thread here, so I apologize if this has already been covered. My problem is this.
I have an unlocked bootloader and TWRP recovery installed. I installed VenomROM without a hitch. Phone has been working superbly for the entire time. I decided in developer options to give ART a try, so I switched from Dalvik to ART. The phone requested that I reboot the device, so I did. But now the device refuses to boot into the OS at all. The HTC splash screen comes up, then the ViperONE bootscreen and it just hangs on this. If I do a hard reset using the power and vol up key to reboot, it just repeats the procedure over again. If I leave it for a prolonged period it doesn't do anything, just stays hanging. I have connected it via USB and tried using fasboot recovery commands and fastboot bootloader commands but it just says 'error device not found'.
Is there any way to enable Dalvik through USB or reboot back into TWRP?
Essential info:
HTC One M8
Latest TWRP Recovery
USB Debugging (Not enabled, cant enable it if I cant get into the phone)
Click to expand...
Click to collapse
there is 2 flashable zips in nexus 5 forum to swap between dalvik and art cant see why they shouldnt work can all ways ask and just side load them and flash them in recovery

jaythenut said:
best thing is go to recovery factory reset and flash viper again
get to recovery by power vol down just in case you dont know
Click to expand...
Click to collapse
That did not work at all, the entire phone was completely frozen on the Venom bootscreen. I did manage with some fiddling to get into Recovery. I did Power+VolUp to force reboot the device, then when the screen went black very quickly switched and did Power+VolDown to enter HBOOT and go to TWRP from there. Painstaking, and took a few goes. Luckily I still had my VenomRom on the USB Stick and after trying multiple different options in TWRP I made sure I had a backup of my data, and reinstalled Venom fresh with a full wipe. I tried doing just an install over it, as that's worked in the past - but the issue persisted. A full wipe was required.
For future until this bug is resolved, if you want to try ART on the One M8 with Venom, make sure to have a nandroid backup to hand as always. Mine was 2 days out of date, but no real loss to me
Thanks for your help!

Do an adb pull you should still have adb access at the boot screen.
/data/property/persist.sys.dalvik.vm.lib is a textfile containing one of two values: 'libart.so' or 'libdvm.so'. You can change from ART to Dalvik simply by editing this file.
Ex: adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'
It's because deodexed roms can't use art
Sent from my HTC One_M8 using Tapatalk

graffixnyc said:
Do an adb pull you should still have adb access at the boot screen.
/data/property/persist.sys.dalvik.vm.lib is a textfile containing one of two values: 'libart.so' or 'libdvm.so'. You can change from ART to Dalvik simply by editing this file.
Ex: adb shell 'echo libdvm.so >/data/property/persist.sys.dalvik.vm.lib'
It's because deodexed roms can't use art
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
That has actually helped me, and I appreciate it. I'm relatively experienced and comfortable in doing a lot of Android things such as bootloader unlocking and editing system files but I had no clue that deodexed roms can't use ART. I should submit a warning to the VenomDevs to grey out or hide the option in Developer Options or at least provide a warning

Related

[Q] HTC One V Recovery doesn't work, Phone Stuck

Hi Y'all, sometime lurker, first time poster.
I got an HTC One V (CDMA, Virgin Mobile) today and given the relative ease of rooting my old Droid Inc I thought it would be a breeze to do this phone as well, but I did not do enough research and messed it up. Here is what I did as best as I can recall:
I unlocked the bootloader without a problem using Fastboot.
Then I flashed CWM recovery through hasoon2000's all in one tool, but it didn't work. I believe I did not flash the correct CWM (CDMA). I tried reflashing stock recovery, and then CDMA CWM recovery, but I couldn't get past the white HTC with the red warning message.
Because I couldn't get recovery to work, I thought maybe I should flash the kernel. I was using hasoon2000's all in one tool, but I did not realize that it would try to boot into recovery in the middle of flashing the kernel (yeah, I'm a noob and an idiot).
So now it won't load into the standard ROM anymore, it just gets stuck on the HTC White screen with the Red Warning. I can get it to load the bootloader, and I tried flashing the kernel from the all in one tool through fastboot, but it didn't work.
Is there any way I can save my phone or am I out of luck?
Thanks for any help you can provide.
Get the stock boot.img and put it in your fast boot folder and go to cmd prompt and type
C:\fastboot
Fast boot flash boot boot.IMG
Make sure your in fastboot
Sent from my One V using xda app-developers app
Thanks XxlemonxX. I did that a few times and it didn't seem to stick.
But! While I was fastloading I went ahead and did the Superboot step found here:
http://forum.xda-developers.com/showthread.php?t=1598964
And the phone restarted! Huzzah! Now I just have to see if I can get a recovery actually working...
OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?
jimmymcsnakes said:
OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?
Click to expand...
Click to collapse
That is an old cwm. thats how it operates. Once your booted into the system you can install rom manager from play store and then you can update cwm so you wont have to enable the power button for use. But anyway seems you cant boot into a stable system right now. So If you are willing to follow theses instructions you can get back to factory conditions.
1. get the fastboot package if you dont have it. http://www.mediafire.com/?4dx982z93w8z7wk and put those files in a folder in the C drive.
2. Get the ruu from here its the top one if you are virgin mobile US. http://www.filefactory.com/f/0eafb9c43276c308/ look for RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
3. This is how your going to get the stock recovery and stock kernel. run the ruu but dont do anything with it just yet. After the ruu is opened and is at the welcome screen just click and drag the window down out of the way and open ANY folder and type %temp% in the address bar of that folder and press enter. You will see a bunch of folders with titles like this "{B2B09672-51AB-4EF6-BDDF-50CB9719052B}" This is just an example. While in that temp folder just do a search for rom.zip and when you find it you can copy that file to your desktop and then just click cancel in the ruu welcome screen for now.
4. Open the rom.zip file with 7zip. You must use 7zip. The built in windows zip program wont work. Once its opened with 7zip, extract these two files 'recovery_signed.img' and 'boot_signed.img'. This is your stock recovery and stock kernel. Extract those to the fastboot folder.
5. You must somehow get your device into the bootloader again. I had the same symptoms as you did with the dark screen and dim red text. I just kept playing with the volume down during boot and eventualy got there. DO NOT USE VOLUME UP!!
6. Once your in the bootloader choose fastboot and plug your device in and it should now say fastboot usb at the top of the bootloader screen. Now run theses commands.
7. Commands to run.
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
8. Now while in bootloader fastboot usb still just run the ruu and follow all instructions. Make sure you have atleast 30% battery while performing this. And if all goes well you will be back to square one.

Nexus 7 2013 stuck at Google screen

So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.
[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.
anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state
hard reset ?
hard reset always works for me. 20 seconds
krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Is your device rooted? If not that is just rediculous on asus's part
slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.
I would return it..I'm sorry to hear that I have had troubles myself with two devices so far
krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?
I have no way to enable usb debugging since I cant tun on the device, right?
krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.
Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you

[Q] Wiped internal memory (recovery and ROMs can't mount)

I'm a dummy.
First off, I'm still S-On.
I was attempting to flash a GPe ROM using TWRP and figured I'd wipe my phone while I was waiting for ROM to download. I clicked 'Wipe' and after not very carefully choosing my option and typing 'yes' (bottom right button, the one that nukes everything) I found that I couldn't keep my Recovery partitions running because they couldn't mount to the internal storage. TWRP just flickers before finally rebooting into a loop and Philz runs for about 20 seconds while giving me errors that it can't open or mount to `cache/recovery/...` before rebooting into the loop.
I've tried formatting the directories in Philz in separate 20 second windows by hand and have managed to make my way through the list (/cache, /data, /system, etc) to no avail. The errors that Philz gives that it can't open or mount to `/cache/recovery/...` are gone, but there is still only 20 seconds that I'm able to use it before rebooting into a loop. I've tried booting into recoveries with `fastboot boot boot/recovery.img` but those only stay running as long as the flashed recoveries (BTW I've downloaded all the recoveries and ROMs I'm trying multiple times).
It seems like the only thing I have at my disposal right now is Fastboot; ADB works in the 20 second windows, but I haven't been able to find anything on how to fix this and can't do much by myself in 20 seconds; I've tried to use RebootRUU, but as far as I can tell that just brings me to a black screen with HTC and gives me access to Fastboot.
I have no idea what to attempt next, does anyone have any thoughts or pointers? Thank you.
JustLikeThat said:
I'm a dummy.
First off, I'm still S-On.
I was attempting to flash a GPe ROM using TWRP and figured I'd wipe my phone while I was waiting for ROM to download. I clicked 'Wipe' and after not very carefully choosing my option and typing 'yes' (bottom right button, the one that nukes everything) I found that I couldn't keep my Recovery partitions running because they couldn't mount to the internal storage. TWRP just flickers before finally rebooting into a loop and Philz runs for about 20 seconds while giving me errors that it can't open or mount to `cache/recovery/...` before rebooting into the loop.
I've tried formatting the directories in Philz in separate 20 second windows by hand and have managed to make my way through the list (/cache, /data, /system, etc) to no avail. The errors that Philz gives that it can't open or mount to `/cache/recovery/...` are gone, but there is still only 20 seconds that I'm able to use it before rebooting into a loop. I've tried booting into recoveries with `fastboot boot boot/recovery.img` but those only stay running as long as the flashed recoveries (BTW I've downloaded all the recoveries and ROMs I'm trying multiple times).
It seems like the only thing I have at my disposal right now is Fastboot; ADB works in the 20 second windows, but I haven't been able to find anything on how to fix this and can't do much by myself in 20 seconds; I've tried to use RebootRUU, but as far as I can tell that just brings me to a black screen with HTC and gives me access to Fastboot.
I have no idea what to attempt next, does anyone have any thoughts or pointers? Thank you.
Click to expand...
Click to collapse
Try flashing the stock recovery and then factory reset in bootloader then try custom recovery again.
Darknites said:
Try flashing the stock recovery and then factory reset in bootloader then try custom recovery again.
Click to expand...
Click to collapse
I've been trying the only AT&T one that I can find and I get a black screen for a couple of minutes, then a picture of the phone with a red triangle and exclamation point...
JustLikeThat said:
I've been trying the only AT&T one that I can find and I get a black screen for a couple of minutes, then a picture of the phone with a red triangle and exclamation point...
Click to expand...
Click to collapse
Hmm not sure then, only other thing I can think of is ruu but looks like you tried that.
Sent from my HTC One_M8 using Tapatalk
That's OK. Press volume up and down a few times and select factory reset eventually. It takes a few tries and it will show up
SaHiLzZ said:
That's OK. Press volume up and down a few times and select factory reset eventually. It takes a few tries and it will show up
Click to expand...
Click to collapse
I've always been able to select factory reset in bootloader, but it doesn't do anything
JustLikeThat said:
I've always been able to select factory reset in bootloader, but it doesn't do anything
Click to expand...
Click to collapse
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery stockrecovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<<Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to go now.
JustLikeThat said:
I've been trying the only AT&T one that I can find and I get a black screen for a couple of minutes, then a picture of the phone with a red triangle and exclamation point...
Click to expand...
Click to collapse
That just means you have a stock recovery installed but no update to install, press volume up and the power button to enter the stock recovery when you see the red triangle.
ashyx said:
That just means you have a stock recovery installed but no update to install, press volume up and the power button to enter the stock recovery when you see the red triangle.
Click to expand...
Click to collapse
That just caused it to try to boot again :/
SaHiLzZ said:
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery stockrecovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<<Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to go now.
Click to expand...
Click to collapse
Holy balls thank you so so much!!!!!! You are a scholar and a saint!
JustLikeThat said:
Holy balls thank you so so much!!!!!! You are a scholar and a saint!
Click to expand...
Click to collapse
Quick question, is it always best practice to always clear out your cache? is there any risk in clearing it?

Z00A stuck on Error! msg during boot, can't access recovery

So here's the deal, I tried to format the cache partition of a stock, non-rooted and non-unlocked bootloader Zenfone 2 (Z00A) through recovery, and it somehow failed/got stuck. After about 1h, I shut down the phone via long-pressing the power button and now it won't boot.
Booting it just leads to an "error!' message and stay there. Trying to go back to recovery does the same thing, I can get to the initial fastboot screen, but selecting recovery mode and pressing power+vol up after the reboot doesn't lead to recovery at all. Instead, every 5 or 10 seconds, the screen clears to black for 1 sec and the same error message shows up.
I tried to get access to it through ADB, but it won't show up in the device list under either the fastboot screen or the Error! message screen on which it stays stuck. Also, the phone was setup so that it didn't allow USB debugging, but I doubt that matters, given that it can't even load Android at all.
Is there something I can do about it? Any tip is greatly appreciated, I looked around XDA and Reddit but didn't find anything that really helped.
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
ultramag69 said:
When you get to the Error screen, hold power and press up volume button. It should get you to recovery...
You can also clear the cache in fastboot mode using the command "fastboot erase cache". It will ask if you want to format/erase cache, say yes and it should clear your cache in a few seconds...
Click to expand...
Click to collapse
Thanks, I had tried various variations of that approach but the issue was a bit more complex than that. In the bootloader, the phone was detected by Windows and drivers from Asus installed properly. ADB wouldn't list the phone, but fastboot did. However, any operation by fastboot was denied access because USB debugging was not enabled prior to the phone going down. Otherwise, as you mentioned, fastboot erase cache would have worked fine.
In the end, I found another post on XDA by Theja which linked to a post in Spanish. The modified ADB and fastboot packet there contains a batch file that manages to bypass this issue and installs CWR, from which clearing the cache is possible. Upon reboot, Asus replaces CWR with the original recovery and things look back to normal.
Sweet, as long as you got it back up and running...
ultramag69 said:
Sweet, as long as you got it back up and running...
Click to expand...
Click to collapse
Hehe, thanks. I'm pretty happy indeed, was already considering the need for a new phone.
However, I must say that finding this toolset worries me a little bit. I thought the whole point of disabling USB debugging was to ensure that people can't perform low-level operations on the phone via fastboot/adb. In this case, this protection is somehow bypassed. I didn't have time to read through the entire batch file, nor am I proficient-enough in Android to make sense of it all, but I wonder how it was done...
In any case, I now have USB debugging left on. It increases convenience and the ability to recover things if problems occur, and it seems like the security benefits are not that strong anyways.

Boot-Looped device. I'm willing to try anything at this point.

So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
addisontodd said:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
Click to expand...
Click to collapse
it's seems like me , it's been a month i can't boot it up .
sfhub said:
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
Click to expand...
Click to collapse
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
addisontodd said:
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
Click to expand...
Click to collapse
what if you try
fastboot boot twrp.img
I've bootlooped so many times I don't know where to start.
So you flashed the factory IMG from your bootloader correct.
Fastboot -w will wipe without wiping system.
Then reflash your whole system. I would redownload from the Google site through Skipsoft...the easiest way. When it asks to keep or flash new recovery you want to flash the stock recovery.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
You'll have to reroot afterwards which you can also do through skipsoft.
Profit... Thank me if I helped.
It's a Hardware issue. Installing system again will not fix it. Send it to LG for a repair. My phone had the same issue.

Categories

Resources