Related
My phone is currently sitting with a "S/W upgrade" screen after a series of stupid events. I flashed recovery using ROM Manager before I had read that it fake flashed. I rebooted into recovery and installed CM7 nightly. Rebooted and it's stuck in a boot loop. So I finally see all the warnings against that so I figure I need to get a real recovery so I use the awesome guide from TGA_Gunnman. I follow all the instructions and it appears from the log on my PC that the CM recovery flashed successfully. I pull the cord, reinsert my battery and my phone just sits in the S/W upgrade screen. It's been like that for 30 minutes now.
What do I do?
I thought I'd done something wrong with my G2x because that happened to me too. Remove your battery and USB. Then insert your battery again. When you turn it on, make sure to hold both the power button and the volume down button until you see text that says android. If you, like me, thought you just had to hold the volume down and tap the power button (like my Nexus One), that might be your issue.
Sent from my Nexus One using Tapatalk
just disconnect usb, and go to recovery Power+vol down...
.....and congrats !
yep, I thought I bricked it too.. When you were done at the green screen where it said press any button, thats where you press whatever you want and then unplug the cord. Then, put the battery back in and hold down vol then power, don't let go until "android" pops up.. You did it man, just missing your last step..
Moved to proper forum
I can get to the Recovery screen, but I cant select any of the options....volume lets me scroll, but cant find anything to select any of the options....kinda new at this
power button to 'action' your selection... at least it works for me.
usajlh said:
My phone is currently sitting with a "S/W upgrade" screen after a series of stupid events. I flashed recovery using ROM Manager before I had read that it fake flashed. I rebooted into recovery and installed CM7 nightly. Rebooted and it's stuck in a boot loop. So I finally see all the warnings against that so I figure I need to get a real recovery so I use the awesome guide from TGA_Gunnman. I follow all the instructions and it appears from the log on my PC that the CM recovery flashed successfully. I pull the cord, reinsert my battery and my phone just sits in the S/W upgrade screen. It's been like that for 30 minutes now.
What do I do?
Click to expand...
Click to collapse
The "S/W upgrade" stays on, that's normal. See if your terminal window has completed whatever stuff it is doing. If you get a completed message, you are good to go and can safely pull out the USB chord even if your phone still says "S/W upgrade". Put back your battery and hold Power+Vol DOWN button and see if you get into cmw recovery.
so im trying to fix my friends phone and this is weird..
im able to go to cwm, wipe it all and flash a new rom.. it flashess successfully but when i reboot it goes back to the s/w update screen..it happens with any rom i flash.. its been sitting there for a while.. how long should i wait?
Once you flash the ROM you shouldn't be getting that screen...Does your friend has the G2x or 2x and which ROM did you flash?
Sounds like you screwed up the boot image. Go into APX mode again and reflash the recovery package making sure it completes, you hit a key to close the terminal window, and you hold the volume buttons the entire time. Then go into recovery and factory reset and clear the Dalvik cache. Then if you still get the S/W update screen you are going to need to go to the thread about fixing bricked phones and use the KDZ method to reflash the entire GB OTA package. There is also a new method to reinstall the entire OTA package using NVFlash but you have to hold the volume buttons down for about ten to fifteen minutes while everything flashes.
So, been running CM10 for a long time on tab. Decided to go back to stock, and downloaded the JB stock rom. Flashed via ODIN. Everything seemed to go OK, except that after the flash the screen went black for ages, and didn't reboot. So I hard powered it off. Probably what did it, but it wasn't going anywhere for about 15 minutes, so figured it was the next step.
Now, I get the battery charging icon. The system goes through the Galaxy Tab 2 7.0 white logo, the swirling then glowing Samsung logo, and then loops through that forever.
It wouldn't be such a problem if I could back into ODIN and do another flash, but I can't get into download mode (normally I do it via adb but that isn't working since there is no USB connection at all). Tried all combinations, power/up, power/down etc. It just boot loops as above. I'm pretty sure I bricked it, but just wanted some confirmation.
Been doing this on and off for a long time, and it's the first time I've ever got stuck like this.
Thanks in advance.
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
ketut.kumajaya said:
Plug USB charger, your device will boot into charge mode. From charge mode you can boot into recovery by keep holding VOLUME UP button and than press POWER button. Clear data and cache in recovery, reboot.
Click to expand...
Click to collapse
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
sl0ttedpig said:
Thanks, but I tried all combinations of Power/Volume UP and Power/Volume DOWN, it just goes through a normal boot cycle until it starts looping.
I guess it's possible I'm not using the right timing. I'm assuming that you hold Volume UP or DOWN and then press and hold Power until the screen goes black, and then release? I've done it like that many times, and also continued to hold everything down as the logo appears, and then system goes back to the battery charging icon as if it powers off again. I sound like such a noob when I type stuff like that!
I saw ODIN successfully write system.img, boot.img, and recovery.img, so I'm thinking any CWM recovery I had on there is toast.
Click to expand...
Click to collapse
You must pull usb cable before start.
You can try to re-flash.
tuxafgmur said:
You must pull usb cable before start.
You can try to re-flash.
Click to expand...
Click to collapse
Well, don't I feel like the idiot!
How did I not think to disconnect the USB before trying this? tuxafgmur, your first "Thanks" has been registered, I've got it from here!
P.S. Welcome to the forum!
it sounds strange. never heard of such a strange boot problem. anyway it could be that while transferring boot.img it became damaged due to some error. i know you probably tryed but you may try and connect it to linux or mac os x in order to check if you could retrive more data about the tab. for example the mac could find if it is totally corrupted. normally when i plug my samsung devices it ask me to add the samsung-modem also if they are turned off. meybe if it happens the same to you you can try to adb fastboot it also if i doubt myself about it working, but give it a shot
i hope my bad english is not preventing you to understand what i'm saying!
give us new feedback!
Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.
if you are SOFF u can go for RUU?
Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really
Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita
Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app
exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.
Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know
DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go
piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?
Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.
dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies
dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..
Edit: PROBLEM SOLVED! However I'll keep this up just in case anyone runs into a similar issue, I'll go ahead and quote the post that brought my tablet to life. As simple as it may be, it helped!
pjim said:
Hold the power button until it turns off. After it turns off, press and hold volume down, then BRIEFLY press the power button while still holding volume down.
You can't really hold them together sometimes, I don't know why.
Hold volume down, press power and release, while holding volume down. Should go into bootloader then.
Click to expand...
Click to collapse
Okay, so in case I'm missing something, I'll keep it quick and say my tablet (WiFI version) wont boot to the system, and no button combo will boot it into the bootloader. It goes straight to the nvidia screen no matter what, and won't get past the boot animation.
In case that doesn't cover it, and more info is needed, I'll give the complete rundown of all that happened.
I just got my tablet a few days ago, however I immedietly unlocked the bootloader, and rooted it, and was fine with that for a while. Eventually I got sick of Lollipop due to lack of support for some Xposed modules and other apps that didn't support 5.0. So I decided to boot into recovery and flash THIS CarbonROM. But it didn't boot past the CarbonROM logo, so I forced a shutdown and booted into recovery (vol down + power) and figured I had to flash the KitKat OTA, then the ROM. So I flashed THIS OTA onto my tablet in CWM, then after booting I booted back into CWM and flashed CarbonROM. It booted just fine. I then went into ES File Explorer and deleted the system apps I didn't want (calender, the stock launcher, etc.) and it worked fine. I then booted back into CWM to clear cache and Dalvik Cache, to clean up any app data that might have been left behind. After booting it stayed on the "Android is upgrading" screen for almost 20 minutes. So I decided to hard reboot it. After doing that, I'm where I am now. The tablet won't boot past the CarbonROM logo, and although I can manually power it down, no matter what I do, I can't boot it into bootloader. I have gotten to the bootloader from a powered off state plenty of times before, in fact it's my preferred method of doing so. But now it skips straight to the Nvidia screen, followed by the CarbonROM screen, and never boots.
Also, I had just flashed the ROM, and had never enabled adb debugging.
Any possible solution would be greatly appreciated, as like I said I just bought the tablet days ago.
Try connecting it to your pc, boot it up, and try running "adb reboot revovery" after it's been running for a bit
ailima said:
Try connecting it to your pc, boot it up, and try running "adb reboot revovery" after it's been running for a bit
Click to expand...
Click to collapse
I seem to get a "error: device offline" message when I try that.
I have used adb and fastboot before this issue so I know my drivers and adb files are just fine :/
Edit: When I unplug the usb from the tablet it makes the low battery noise. I think it's booted to the system but stuck at the CarbonROM logo for some reason. I did delete the stock launcher without installing a new one...
Edit: Since I had just flashed the ROM, I had not yet gone into developer options and enabled adb debugging. I had only done it before I flashed the ROM.
FoxyDrew said:
I seem to get a "error: device offline" message when I try that.
I have used adb and fastboot before this issue so I know my drivers and adb files are just fine :/
Edit: When I unplug the usb from the tablet it makes the low battery noise. I think it's booted to the system but stuck at the CarbonROM logo for some reason. I did delete the stock launcher without installing a new one...
Edit: Since I had just flashed the ROM, I had not yet gone into developer options and enabled adb debugging. I had only done it before I flashed the ROM.
Click to expand...
Click to collapse
Hold the power button until it turns off. After it turns off, press and hold volume down, then BRIEFLY press the power button while still holding volume down.
You can't really hold them together sometimes, I don't know why.
Hold volume down, press power and release, while holding volume down. Should go into bootloader then.
pjim said:
Hold the power button until it turns off. After it turns off, press and hold volume down, then BRIEFLY press the power button while still holding volume down.
You can't really hold them together sometimes, I don't know why.
Hold volume down, press power and release, while holding volume down. Should go into bootloader then.
Click to expand...
Click to collapse
I literally love you right now.:laugh:
Seriously thank you, I thought I was screwed. I just wonder why it works like this. I'll have keep it in mind for the future haha, thanks:good: