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?
Related
Just got a One X.
Unlocked the boot loader.
Installed CWM (v5.8.4.0 from fast boot)
Then when i navigate to the rom it says its completed update? seems to take only 30 seconds when I reboot it brings me back in CWM.
Basically I can mount the phone phone through clock work mod and see the rom/zip file but it installs as update and just keeps popping back into clockwork mod? am I able to just get this back to normal?
finding update package...
opening update package...
installing update...
finishes after 15 seconds? saying install from sdcard complete. have I missed a step?
Help me please guys I feel the information I followed as done away with a boot.img?
Cheers,
Gary
gdwelsh said:
Just got a One X.
Unlocked the boot loader.
Installed CWM (v5.8.4.0 from fast boot)
Then when i navigate to the rom it says its completed update? seems to take only 30 seconds when I reboot it brings me back in CWM.
Basically I can mount the phone phone through clock work mod and see the rom/zip file but it installs as update and just keeps popping back into clockwork mod? am I able to just get this back to normal?
finding update package...
opening update package...
installing update...
finishes after 15 seconds? saying install from sdcard complete. have I missed a step?
Help me please guys,
Cheers,
Gary
Click to expand...
Click to collapse
Did you flash the boot image of the rom??
anks257 said:
Did you flash the boot image of the rom??
Click to expand...
Click to collapse
I extracted the boot image from the downloaded rom and placed that in to the fastboot folder? I followed these instructions mate, I think ive messed up the boot?
Copy the CM10 ZIP file to your phone’s internal SD card.
On the PC, extract the Fasboot.zip. You will get a folder named Fastboot.
Extract the boot.img file from the cm10_endeavoru-ota-eng.noeri-028.zip file and place it into the Fastboot folder.
Turn your phone off.
Boot to Fastboot Mode. Hold down the Volume Down and the Power buttons until the screen turns on to enter Bootloader Mode.
In Bootloader Mode, highlight Fastboot Mode using the Volume keys and select it by using the Power button.
Connect your phone to your PC via USB cable.
Open a command prompt on your PC and navigate it to the Fastboot folder.
In the command prompt, type fastboot devices to check if your device has successfully connected to your PC. Your phone’s serial number should appear on the screen.
Flash the boot.img by typing the following in the command prompt:
fastboot flash boot boot.img
Go back to your phone and select Bootloader to go back to the main Bootloader menu.
In Bootloader Mode, highlight Recovery using the Volume keys and select it by using the Power button to boot into ClockworkMod Recovery.
Select Wipe data/factory reset > Yes.
Select Install ZIP from SD card > Choose ZIP from SD card > select the cm10_endeavoru-ota-eng.noeri-028.zip file > Yes.
Select Go back > Reboot system now.
Ive then updated to a newer cwm as per this thread - http://forum.xda-developers.com/showthread.php?t=1594819
I dont think i can enter fast boot no longer? I can still mount things, but dont know what else.
Try clearing the cache and the dalvik cache in cwm.. did you do that??
anks257 said:
Try clearing the cache and the dalvik cache in cwm.. did you do that??
Click to expand...
Click to collapse
Yeah done that, I dont think I have flashed the boot img for the rom? is possible to do this from cwm?
gdwelsh said:
Yeah done that, I dont think I have flashed the boot img for the rom? is possible to do this from cwm?
Click to expand...
Click to collapse
Nope, that must be done through command prompt
anks257 said:
Nope, that must be done through command prompt
Click to expand...
Click to collapse
Do i have any options then??
gdwelsh said:
Do i have any options then??
Click to expand...
Click to collapse
yes, reboot into bootloader and reflash the boot image!
anks257 said:
yes, reboot into bootloader and reflash the boot image!
Click to expand...
Click to collapse
Forgive me how do I get in to bootloader when it stuck in cwm?
gdwelsh said:
Forgive me how do I get in to bootloader when it stuck in cwm?
Click to expand...
Click to collapse
selsct reboot system.
As soon as the phone reboots press the vol down + power buttons, and phone will reboot into bootloader.
Also if that isnt working, connect phone to pc and in cmd enter 'fastboot reboot bootloader'
anks257 said:
selsct reboot system.
As soon as the phone reboots press the vol down + power buttons, and phone will reboot into bootloader.
Also if that isnt working, connect phone to pc and in cmd enter 'fastboot reboot bootloader'
Click to expand...
Click to collapse
Omg, that was what my panic was, I didnt think I could get back into bootloader :s how stupid do i feel. I thought it was just cycling through.
gdwelsh said:
Omg, that was what my panic was, I didnt think I could get back into bootloader :s how stupid do i feel. I thought it was just cycling through.
Click to expand...
Click to collapse
hehehe.. happens. brain stops working in such a panic. Been there, done that!
so now im in fastboot usb do i just flash the boot.img from the rom.zip folder?
That then loads a android screen with animation, but I assume I then need to install the rom?
yep...
also after flashing boot, type 'fastboot erase cache' (just in case)
anks257 said:
yep...
also after flashing boot, type 'fastboot erase cache' (just in case)
Click to expand...
Click to collapse
What I dont understand and please correct me, is how come the phones running if I have not installed an rom? I mean i thought id wiped everything and only installed a boot image? yet i am able to use it?
I just entered fastboot reboot not the erase? should i go back through and do it? cheers for the help too. I thought i'd wasted £200
gdwelsh said:
What I dont understand and please correct me, is how come the phones running if I have not installed an rom? I mean i thought id wiped everything and only installed a boot image? yet i am able to use it?
I just entered fastboot reboot not the erase? should i go back through and do it? cheers for the help too. I thought i'd wasted £200
Click to expand...
Click to collapse
Your bootloader and recovery are independent of your rom. you will be able to access them even without a rom installed.
the erase cache fuction is not necessary.
Just flash your boot image again.. and try installing the rom again.
---------- Post added at 11:31 PM ---------- Previous post was at 11:30 PM ----------
Also have you updated your hboot?? or is it the old one?
I dont think I updated the hboot? should I bother?
I am using the CM10 rom? I know its down to each tastes and requirement but is this a decent one? phone runs smoother than my LG 4X HD P880 despite that scoring more in benchmarks.
I still technically have not installed the rom through CWM? I just used cmd prompt to flash a boot image then it started up.
gdwelsh said:
I dont think I updated the hboot? should I bother?
I am using the CM10 rom? I know its down to each tastes and requirement but is this a decent one? phone runs smoother than my LG 4X HD P880 despite that scoring more in benchmarks.
I still technically have not installed the rom through CWM? I just used cmd prompt to flash a boot image then it started up.
Click to expand...
Click to collapse
You can update the hboot if you want. All the sense based JB roms work only on the upgraded hboot. Though AOSP roms work on all hboots. So upto you.
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
I just got my htc one last night,I have s off and it says it unlocked.my problem is when i go command prompt to install open recovery it shows that it wrote twrp then i click recovery it shows its booting into recovery but then it just restarts to the splash screen,Ive tried many times to get into recovery and just brings me back to htc screen phone boots fine.Ive tried to use goo manger to get into recovery which also shows entering recovery mode then it just starts up normal.So im not sure what the heck is going on.So info would be greatly apprecitaded.or should i use philz recovery does one work better then the other.I am also running 4.2.2 not sure if that matters or not
I'm also having this problem. I'm running android 4.3. I've tried TWRP and Clockwork Mod. I achieved S-Off and an unlocked bootloader with firewater.
fuzzylax said:
I just got my htc one last night,I have s off and it says it unlocked.my problem is when i go command prompt to install open recovery it shows that it wrote twrp then i click recovery it shows its booting into recovery but then it just restarts to the splash screen,Ive tried many times to get into recovery and just brings me back to htc screen phone boots fine.Ive tried to use goo manger to get into recovery which also shows entering recovery mode then it just starts up normal.So im not sure what the heck is going on.So info would be greatly apprecitaded.or should i use philz recovery does one work better then the other.I am also running 4.2.2 not sure if that matters or not
Click to expand...
Click to collapse
Use Clock Work Mod. TWRP has been having issues with so many devices.
Did you do " fastboot erase cache " before flashing the recovery. I have used twrp since day one with out any issues. I hate cwm because of the super slow backups. Twrp finishes in 1/4 the time. Also twrp looks much better.
cmlusco said:
Did you do " fastboot erase cache " before flashing the recovery. I have used twrp since day one with out any issues. I hate cwm because of the super slow backups. Twrp finishes in 1/4 the time. Also twrp looks much better.
Click to expand...
Click to collapse
i havent tried that will give it a shot .I deleted sdk and trying to reinstall it but for some reason its not loading the page to dl it.So if anyone has a file for that would be cool,where is the fastboot erase cache at im not seeing it any were.back in the day when i had the thunderbolt I never had this much problems
fastboot erase cache is a command you enter in fastboot mode. Just like when you flash the recovery with fastboot flash recovery name_of_recovery_file.img
You dont need the whole sdk. I assume the drivers are still installed? All you need is this https://www.dropbox.com/s/ipa8tsjdmcacxul/miniadb.zip. Just extract the files to a folder named adb. Then put your recovery .img file in the adb folder too. Then open your cmd prompt to that folder and do the commands.
fuzzylax said:
I just got my htc one last night,I have s off and it says it unlocked.my problem is when i go command prompt to install open recovery it shows that it wrote twrp then i click recovery it shows its booting into recovery but then it just restarts to the splash screen,Ive tried many times to get into recovery and just brings me back to htc screen phone boots fine.Ive tried to use goo manger to get into recovery which also shows entering recovery mode then it just starts up normal.So im not sure what the heck is going on.So info would be greatly apprecitaded.or should i use philz recovery does one work better then the other.I am also running 4.2.2 not sure if that matters or not
Click to expand...
Click to collapse
Did you use the VZW version of TWRP from here? http://forum.xda-developers.com/showthread.php?t=2416431
No issues like mentioned before. I've heard philz works well but haven't tried it. You can even use an app called flashify to flash either. Fastboot is better and less risky, but I've used flashify and it works.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
cmlusco said:
fastboot erase cache is a command you enter in fastboot mode. Just like when you flash the recovery with fastboot flash recovery name_of_recovery_file.img
You dont need the whole sdk. I assume the drivers are still installed? All you need is this https://www.dropbox.com/s/ipa8tsjdmcacxul/miniadb.zip. Just extract the files to a folder named adb. Then put your recovery .img file in the adb folder too. Then open yourt to that folder and do the commands.
Click to expand...
Click to collapse
so i still have know idea what is going on with this.I dl the miniadb from drop box [thanks for that by the way] extracted to new folder called adb dropped and dragged file openrecovery-twrp-2.5.0.0-m7 to the adb folder,held down shift and got into cmd typed in fastboot erase cache and hit enter it shows that it wrote it ,then I typed fastboot flash recovery openrecovery-twrp-2.5.0.0-m7 add the .img to the end hit enter and says every thing went ok.so I unplug cable hit power button went into recovery hit power button again.it shows that it is going into recovery then just goes to splash screen and boots normal.I have usb debug checked,S is off and says unlocked.So im stumped hopefully you will see what im doing wrong with my procedure..thanks again for the info you have have given me so far.
are their suppous to be spaces between fastboot flash recovery
That is the wrong recovery for this phone. Use this one http://flyhalf205.com/getdownload.php?file=recoveries/openrecovery-twrp-2.6.3.4-m7vzw.img from the post above by brholt6. Also make sure you do the fastboot erase cache command before flashing the recovery. And yes there should be spaces.
Code:
fastboot erase cache
Then
Code:
fastboot flash recovery name_of_recovery.img
fuzzylax said:
so i still have know idea what is going on with this.I dl the miniadb from drop box [thanks for that by the way] extracted to new folder called adb dropped and dragged file openrecovery-twrp-2.5.0.0-m7 to the adb folder,held down shift and got into cmd typed in fastboot erase cache and hit enter it shows that it wrote it ,then I typed fastboot flash recovery openrecovery-twrp-2.5.0.0-m7 add the .img to the end hit enter and says every thing went ok.so I unplug cable hit power button went into recovery hit power button again.it shows that it is going into recovery then just goes to splash screen and boots normal.I have usb debug checked,S is off and says unlocked.So im stumped hopefully you will see what im doing wrong with my procedure..thanks again for the info you have have given me so far.
Click to expand...
Click to collapse
cmlusco said:
That is the wrong recovery for this phone. Use this one http://flyhalf205.com/getdownload.php?file=recoveries/openrecovery-twrp-2.6.3.4-m7vzw.img from the post above by brholt6. Also make sure you do the fastboot erase cache command before flashing the recovery. And yes there should be spaces.
Code:
fastboot erase cache
Then
Code:
fastboot flash recovery name_of_recovery.img
Click to expand...
Click to collapse
Dude you rock!!!! I know when i was using my s4 that the twrp worked best for that phone.Cant belive thats all it was.so just to make sure,I need to flash su then I should do backup of stock image just in case something goes wrong.So my next questions is do i nedd to do anything elese to flash kitkat rom on phone like flash differnt radio or anything?again thank you for your time and all the info you have provided.
Yes, flash su and then do a backup. If you use a kk rom you should flash kk 3.11.605.1 firmware.
perfect got it goin think its starting to come back to me doing the htc...lets hope
Rooted my phone using Temporary CWM method, installed Titanium Backup and restored from my old phone. Selected All Apps and Data. Rebooted my phone and I assume that it is now stuck in a bootloop. It gets to the ASUS and Intel Inside screens, then I get a spinning circle forever (well, at least 3 minutes).
Where do I go from here? Reflash the ROM and start over and don't restore system data? Is there an easier/quicker way?
Thanks
Go to fastboot mode by holding the power and volume up button,connect USB cable be sure that you installedmusb and fastboot driver.go to folder of fastboot and hold shift key then right click open command window here and type:fastboot erase cache then enter fastboot reboot and voila..
Thanks for the reply, but that didn't do it.
I was able to execute the commands, but still no luck. I got into recovery to try and wipe from there, but got the dead android. I them held power up and tapped vol up to get into recovery. tried to wipe cache from there and the phone just sat there for 3-4 minutes with nothing. Now when I get into recovery, I get a flashing dead android, and the power/vol up trick doesn't work. I can still boot into fastboot.
Di I just need to reflash the stock image? Or is there something else I can do?
arrosen said:
Thanks for the reply, but that didn't do it.
I was able to execute the commands, but still no luck. I got into recovery to try and wipe from there, but got the dead android. I them held power up and tapped vol up to get into recovery. tried to wipe cache from there and the phone just sat there for 3-4 minutes with nothing. Now when I get into recovery, I get a flashing dead android, and the power/vol up trick doesn't work. I can still boot into fastboot.
Di I just need to reflash the stock image? Or is there something else I can do?
Click to expand...
Click to collapse
I had the same problem as yours and it took 3 hours before i figured it out and managed to run the phone normally.I downloaded all the files,drivers and latest prerooted system img. here in this forum.you can download it there and there is the instruction how to do it.
To Begin :
1. on Fastbootmode connect your device and on the flashtool folder hold shift key and right click and go to open command here,be sure that downloaded images are in the same folder.Recovery img.,Boot Img. and the big pre-rooted System img.
2. type fastboot devices then hit enter key - the device nos. should appear and you can start now to flash...
a. fastboot -w then hit enter this will erase the system
b.fastboot flash system system.img then hit enter key
c.fastboot erase userdata then hit enter key
d. fastboot erase cache then hit enter key
e. fastboot reboot then hit enter key..
THANK YOU!!!
Thank You, Thank You, 1000 times, Thank You.
I did everything you mentioned, with a few small exceptions
1. Make sure you have the lastest version of Fastboot
2. Instead of step b above, I did the following. Not sure if it was needed or not, but it worked for me
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
3. At the end, after I did a Fastboot Reboot, I got the dreaded dead android again. I nearly cried. However, I rebooted again, and everything seemed to work. Note that on the first boot, it may take 2-3 minutes for the OS to come up.
4. All of the files and great insight can be found here: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
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.