Related
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Teichopsia said:
http://forum.xda-developers.com/showthread.php?p=30480411
Sent from a dream.
Click to expand...
Click to collapse
Im sorry but I dont understand. I cannot enter hboot no mater what i do and don't you need to enter hboot to reflash it?
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
2nd edit: if you are new, then read the guide in post#7
http://forum.xda-developers.com/showthread.php?p=30007255
Sent from a dream.
Teichopsia said:
True, but I'm hoping you are doing something wrong.
Pull battery, wait a few minutes, place back in. Press and hold Volume down, then power button. Does it go into hboot? If not.
Read this.
http://forum.xda-developers.com/showthread.php?p=20382502
Edit: you are the first report with that issue after trying to flash that rom. My bet (that is, if you are new), you are not doing something wrong.
.
Click to expand...
Click to collapse
I really appreciate the help Teichopsia , but I've tried the power /volume - method many times and it still wont go to hboot. if it helps this is the 5 time i have have flashed a rom on my phone (and it is rooted) and yes sadly i had to be the first person to be unlucky enough to get my phone bricked from the blackout rom :crying:
i think i could get out of this mess if i could only get into hboot.
reading the method you linked to me will it work if i cant even get to the hboot screen? my phone only stays of the white htc logo screen for about 3 seconds then it goes to a lit black screen
on a side note should i report what happened to team blackout to see if they have any soloutions?
The only thing I can think of is trying to get into hboot without the sd card and sim card.
The rest is beyond my knowledge.
You'll need to wait for someone more knowledgable than myself to help you.
Remember, first press and hold the volume down button, while holding that down press the power button. Do not release either button till it shows the hboot. If that doesn't work, pull the battery for five minutes and try again. If you did this part exactly like that, then you can skip it.
Well, you already posyed your issue here, just wait for someone to help you. Glevitan is bound to show up sooner or later.
Sent from a dream.
I would see if you can send commands to it from adb while its in the blacked out state. adb is pretty easy to use and can be found easy online. if you get it installed type "adb devices", if it recognizes your device type "adb reboot bootloader" or "adb reboot recovery".
Novius vi said:
hello all,
I am new here and I have been searching the forums for a few days as well as the internet but I could not seem to find one that had my same problem, but if there is can you please direct me to it and apologies for that.
I was installing a new rom, the Blackout ICS Incredible v3.0.0 FULLY WORKING!!! [4.0.4][Sense 3.6], onto my inspire i did a full wipe using FULL_WIPE_1.5_EXT4_.zip and I cleared the caches. the install i thought went well because it went to 100% and i even chose what kind of background i could as well as choosing to over clock my processor. The phone the restarted after all of that and it went to the htc screen then faded to black, after about ten minutes of it being black screen i pulled out the battery.
Now when i try to recover it it wont go into hboot and it just goes to the htc white screen then it quickly fades to a black screen and stays like that.
so my question to you all is a Jtag the only way i can save my phone or is there something else i can do?
Click to expand...
Click to collapse
i also have the same problem. i'm using a DHD. and to add to that, my volume rocker is broken. i wonder why the warning not to select reboot immediately after installation wasnt part of the download as a readme or something. i may have just lost a perfectly good phone as a result
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Gizmoe said:
I can confirm as a third user and one knowledgable in flashing roms that the ICS blackout does the same thing to my phone. I can also confirm that pulling the battery and then trying hboot just results in the white htc screen instead of just popping up hboot. I was able to boot into recovery from the white htc screen by using adb and doing the "adb reboot recovery" command. I am able to restore my backup just fine so you guys will be able to fix it. it must just have a bad boot image for the version of hboot that we have installed.
Click to expand...
Click to collapse
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Use this guide its very easy. if you have already used your phone on your pc and the drivers are installed all you need to do is download the easyadb and follow the instrucions to where is says to type adb.exe. once it is started just type adb devices to make sure it sees your device and then adb reboot recovery
Ignore the fact the instructions are written for a xoom as it will work for any android device with the drivers already installed, which they should be from rooting, syncing and all the other stuff you have probably already done on pc.
UPDATE: I reinstalled ICS blackout but instead of wiping myself i just let aroma installer do it and everything went fine this time. I noticed the aroma installer reformats everything to ext4. its not mentioned in the op as a requirement but seems thats the case. Hboot version has nothing to do with it like i previously commented. It really is a cool rom with both ics and sense. I have only tried the sense version so far
Hope this helps?
Novius vi said:
Im sorry but this is the first time i have ever done something like that can you give me a step by step instruction how to do it or a link that says how, i dont want to sound lazy but I scared to mess up my phone even more
Click to expand...
Click to collapse
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power button. Do not do press them both at the same time. I realize you wrote that your volume rocker seems or is broken but I wrote above just in case-- when I first tried to root my phone, I was pushing them both at first and thought my rocker was broken....
Since you rooted the phone originally-- not sure how you did it. But if you go to this link you can download recovery flash. Read the "readme" file:
http://forum.xda-developers.com/showpost.php?p=29208930&postcount=10
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Three of us confirmed that hboot was inaccessible even after battery pull. I am no stranger to this device as well. The only fix was using adb reboot. Also if you actually reformat your partitions to ext4 before install, then aroma will install correctly. It's just not mounting anything if it's still in ext3 format. Definitely better to just do the full wipe within aroma though. I do agree with not hitting restart from aroma but someone already mentioned that a few posts up.
Thank you thank you thank you
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Novius vi said:
After putting it into abd it recognized it and then i was able to put it into hboot. Im not out of the woods yet, but after not being to see hboot in so long, well its just amazing to see it again
ok now its in hboot it gives me 4 choices
bootloader
Reboot
Reboot Bootloader
power down
apologies again but just for reassurance which one should i select?
THANK YOU GUYS for getting me this far!!!
special thanks to Gizmoe for suggesting the adb route
Click to expand...
Click to collapse
Select bootloader to get to recovery option.
1shukla said:
Just in case-- to get into recovery you must press and hold the volume down for a few seconds and then hold the power
Assuming you can get into recovery-- then reload the blackout ROM but you MUST let the aroma installer wipe and format do not use any other wipe/format tool. Then do NOT press the "FINISH" button-- instead press the back arrow-- you want to go back to flash recovery and reboot from there. If you press finish (like I did multiple times, the phone will just lockup).
Best of luck!
Click to expand...
Click to collapse
I did exactly as you said I pressed finished and it asked if i wanted to reboot i said no. then it sent me back to recovery mode crossing my fingers hoping to see that it works:fingers-crossed:
Now, just manually reboot.
Sent from a dream.
You saved my phone!!
Thank you guys sooo much this Rom is great once I got past that minor issue
My phones working better than ever I even oced it a little bit
Again I am eternally grateful to you guys and team black out for this great Rom!
Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
mex2309 said:
Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Click to expand...
Click to collapse
U should definitely go back to stock via odin first before even trying to install cwm and flashing a custom rom.
Sent from my SGH-I727 using xda app-developers app
T.J. Bender said:
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
Click to expand...
Click to collapse
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
I think its a gonner...
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
mex2309 said:
I think its a gonner...
Click to expand...
Click to collapse
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
mex2309 said:
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
Click to expand...
Click to collapse
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
Sounds similar to what I just went through... Except I didnt do anything in recovery before mine started looping. Curious to know what rom you were running as well.
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
mex2309 said:
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
Click to expand...
Click to collapse
I'm trying to wrap my head around that, and not coming up with anything valid. Wiping the caches would cause a much longer boot time, battery stats, at most should only cause you to need to remove and reinsert the battery.
Just about the only thing I could come up with would be that when you wiped the caches, was that your phone was trying to reload all that data back into the cache and was getting brain dead.
More information is needed from others that have had the same issue, on the same ROM, or different does not matter, but detailed info as to what exactly was done prior to the boot loop issues.
If my phone gets stuck in a boot loop, usually after I flash someting in Odin or whatever, if I hit factory reset it fixes itself.
It doesn't bother me since all my stuff is backed up though.
You should Odin back to stock then flash cwm
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
just got a phone off of craigslist.. saw that it booted up, so i figured i might be able to fix it. cost me $100.
just finished ODINing it, but it just continues to bootlop. not sure what to do next.
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
hechoen said:
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
Click to expand...
Click to collapse
already did that.. flashed CWM, ran recovery and installed rom. no go. now i see the cyanogen boot screen, but it won't get past that. this is kind of strange.
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
mistabeo said:
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
Click to expand...
Click to collapse
I did what I could to try to replicate your situation. Which version of CWM are you installing? I went through several different versions up to the latest and found that the phone was having an issue with CWM itself. (possibly corrupted driver, but not 100% sure on that, as the phone does get recognized by the computers.)
But when I got to the latest CWM, and it started doing similar to yours, what I did was the following.
#1 : reinstall drivers
#2 : plugged the phone into the USB 2.0 slot on my laptop.
#3 : removed the battery, sim card, SD card
#4 : tried to power on the phone holding the power button for approximately 20 seconds. (nothing)
#5 : put in the battery while still plugged in, and powered on.
#6 : After phone booted up, and computer recognized the phone, I removed the battery. Phone stayed on.
#7 : waited while the computer re installed the ADB drivers, after driver install success, I unplugged the phone. Of course it powered down.
#8 : Restarted the laptop, put the battery back in the phone, and held vol + and - and power. Phone rebooted into recovery, but got into a boot loop when trying to recover.
#9 : downloaded TWRP recovery and put it on the SD card for the phone. Restarted the phone into recovery and installed TWRP recovery.
#10 : Rebooted phone into TWRP recovery. wiped all cache, installed latest STOCK ROOTED ROM.
The phone has been stable and working just fine, no wifi or blue tooth issues, calls are as normal, texting is as normal. LTE speeds as normal.
I have since switched all my devices over to TWRP recovery and have had ZERO issues.
I flashed a Paranoid Android ROM and now the 7 won't boot past the logo. When going to the boot loader I can't select other options and the power will not initiate the 'Start' sequence to continue with boot.
It will, however, respond to the 3-finger salute and shut down. I can then press the power button and start a normal boot (meaning that the button does work).
I will say I probably forgot to wipe or something, but it is an unusual situation that I can't even enter recovery.
I am also having plenty of issues with Win8 and drivers (granted I am still using the Evaluation one), so getting to fastboot for manual intervention is not working right now.
Has anyone encountered a situation where you are in Bootloader and NOT be able to execute fastboot commands?
I had the same problem.
Dawezilla said:
I flashed a Paranoid Android ROM and now the 7 won't boot past the logo. When going to the boot loader I can't select other options and the power will not initiate the 'Start' sequence to continue with boot.
It will, however, respond to the 3-finger salute and shut down. I can then press the power button and start a normal boot (meaning that the button does work).
I will say I probably forgot to wipe or something, but it is an unusual situation that I can't even enter recovery.
I am also having plenty of issues with Win8 and drivers (granted I am still using the Evaluation one), so getting to fastboot for manual intervention is not working right now.
Has anyone encountered a situation where you are in Bootloader and NOT be able to execute fastboot commands?
Click to expand...
Click to collapse
I had the same problem with PA and being unable to execute fastboot commands. An easy fix for me was to use the Nexus root toolkit to boot into temporary CWM. I was able to wipe and re-flash PA and it was fixed. Unfortunately, you said you can't do this because of Windows 8 problems... This actually happened to me a couple times though, and once I was able to get into recovery. Try this. Make sure your 7 is absolutely unplugged from anything, so it can't even be charging. Get to the bootloader with the 3-finger salute and see if you can use the volume buttons to get to recovery. If you can, and it actually take you to recovery, thats great, but most of the time for me it got stuck at the Google screen. So if this doesn't work you may have to figure out whats wrong with Windows 8 first. Hope I could help!
Did you make a back up? Did you Flash clockwork mod or a custom recovery image? If not do what he said.
Sent from my Nexus 7 using xda app-developers app
pbone771 said:
I had the same problem with PA and being unable to execute fastboot commands. An easy fix for me was to use the Nexus root toolkit to boot into temporary CWM. I was able to wipe and re-flash PA and it was fixed. Unfortunately, you said you can't do this because of Windows 8 problems... This actually happened to me a couple times though, and once I was able to get into recovery. Try this. Make sure your 7 is absolutely unplugged from anything, so it can't even be charging. Get to the bootloader with the 3-finger salute and see if you can use the volume buttons to get to recovery. If you can, and it actually take you to recovery, thats great, but most of the time for me it got stuck at the Google screen. So if this doesn't work you may have to figure out whats wrong with Windows 8 first. Hope I could help!
Click to expand...
Click to collapse
UPDATE:
With WUGS Nexus Root Toolkit 154 I was able to do a complete system restore from the boot loader screen. Even though I could not use the three buttons individually to change options OR initiate the displayed option.
I did have to reload Win7 on my machine *just as well I only has the trial one anyway) and the drivers picked up fine. This issue is independent of the Nexus7.
The bottom line is that the Bootloader, even though it seemed frozen, was still accessible via Fastboot commands.
Ryan_Shea said:
Did you make a back up? Did you Flash clockwork mod or a custom recovery image? If not do what he said.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
HAd backup. Was with TWRP. BUT could not get to Recovery mode. All good now though.
With WUGS Nexus Root Toolkit 154 I was able to do a complete system restore from the boot loader screen. Even though I could not use the three buttons individually to change options OR initiate the displayed option.
I did have to reload Win7 on my machine *just as well I only has the trial one anyway) and the drivers picked up fine. This issue is independent of the Nexus7.
The bottom line is that the Bootloader, even though it seemed frozen, was still accessible via Fastboot commands.
Glad to hear it. There is an updated boot loader in the forum somewhere that fixes the "unable to boot in to recovery via fast boot" which can save a lot of hassle if you happen to boot loop again. Makes it a hell of a lot easier to recover. I had the same issue when I first rooted too. Had to just full wipe and recover to stock because I rooted first and then unlocked the boot loader which made the root not stick so when I tried to flash the first ROM got a boot loop and couldn't get to recovery, such a pain in the ass the nexus is.
Sent from my Nexus 7 using xda app-developers app
Hello.
Thank you in advance for your help. This is my problem. Fews days ago the button-on-off was broken. I somehow managed to live with that problem. Untill I decided to open the phone and see if I can fix it. I noticed then that is if I remove the battery and put it on again; the phone would boot on its own. I opened the phone and checked it from inside I couldn't see anyhing abnormal. Probably the button needs to be replaced.
while I was assembling the phone, the battery was removed while the phone was booting. Afterwards, the phone didn't want to boot anymore given the fact that the button remains useless. I read on some posts that if I plug the Usb cable to the PC the phone would boot, but nothing happened.
So here's where I am stuck. If anyone knows how I can boot the phone despite the button being broken and the USB trick not working. please help
Try using adb reboot fastboot to boot to fastboot and then change with the volume keys to reboot.
Sent from my GT-I9100 using xda app-developers app
stuck on google screen
xDeadaheaDx said:
Try using adb reboot fastboot to boot to fastboot and then change with the volume keys to reboot.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your help, here's what I have done :
I have had the button replaced. the button works now fine. but the phone is stuck on the google screen and doesn't boot. I have access to Fastboot mode. I've tried to unlock it to be able to copy some recovery file. but i got the message (Failed: erase...).
I tried wipe/reset. when I do wipe cache partition, it formats the partition, i don't know what effects does it have. are all the data wiped? including the ROM? ...but it has no effect and the sysgtem just boots and goes back to the frozen google screen and when I perform factory reset it goes back to the robot with the red triangle screen.
Anyway, I tried the only option left which is "apply update from ADB" the phone goes into adb mode and waits for the update to be sent.
the phone is obviously recongnized in my computer as an ADB interface. i wrote the command <adb sideload update.zip> the update.zip is actually the official 4.1.2 ROM downloaded from google sites and renamed. After the execution of the command, the file was sent, I had then a big hope that this would be the end of my nightmare, at the end of the sending. The phone reacts and displays the following
Finding update package
Verifying update package,
Installation aborted
So this is where I am stuck. If any one can Help please. by the way NS is on the officla 4.1.2 ROM and not rooted and locked
Thank you
Try Nexus Root Toolkit from http://wugfresh.com/nrt
It has lots of tools and options which might help you.
Sent from my Nexus S using Tapatalk