Related
Ok So I tried Flashing the recovery through rom manager and when it downloaded it asked for su permission I Pressed allow clockwork gave me an error stating i did not have enough rights to flash recovery rom manager force closed and the phone turned off and now when I try restarting I get a boot loop at the LG screen. When I press Vol- + power it says S/W Upgrade Please wait while upgrading but does not do anything after that its been on the screen for more than 20 minutes any ideas how i could fix this?
Are you rooted?
Have u tried a battery pull? After that try to boot up to bootloader by holding power+vol down(u shouldnt get the update thing after battery pull). Make sure it says s-off. It seems like ur not rooted correctly since u got the permissions error
Yea I Rooted Using One Click method I was able to use root for other programs like titanium back up tried a battery pull already and tried holding vol down + power but it takes me to the upgrading screen
I'd give the nvflash method a shot. When I flashed cwm, I specified the wrong file and couldn't boot. Once I figured that out and got it right it booted up fine.
edwards33 said:
Ok So I tried Flashing the recovery through rom manager and when it downloaded it asked for su permission I Pressed allow clockwork gave me an error stating i did not have enough rights to flash recovery rom manager force closed and the phone turned off and now when I try restarting I get a boot loop at the LG screen. When I press Vol- + power it says S/W Upgrade Please wait while upgrading but does not do anything after that its been on the screen for more than 20 minutes any ideas how i could fix this?
Click to expand...
Click to collapse
You'll need to have the recovery flashed using the NVFlash method as previously stated. The Rom Manager method seems pretty worthless to me so far. Also, have your USB cable unpugged when trying to boot to recovery.
Great news I pulled the battery while it still said upgrading I turned on by holding volume down and power and I held until and android Icon came up and it rebooted itself and loaded as if I had done a master reset thanx for the tips
Sent from my LG-P999 using XDA Premium App
Awesome, glad to hear it.
I just rooted my One S using this thread: http://forum.xda-developers.com/showthread.php?t=2008440. I flashed Clockworkmod touch recovery and installed the latest CM10 Nightly. I ended up installing the standard Clockworkmod recovery (non touch) through ROM manager once my phone was up and running. Everything on my phone was working great until I let my battery run all the way down to the point my phone shut off. I plugged my phone in and it automatically booted to recovery. I waited a little bit for the phone to charge and selected "reboot system now" from recovery. My phone did not boot and only goes to recovery. When it reboots, it briefly flashes a green stripe twice in the upper third of the screen prior to booting all the way but never shows the HTC screen or anything other than recovery. I tried reflashing the ROM in recovery, formatting every partition in recovery, entering fasboot using ADB, rebooting using ADB, and nothing seems to get my phone to do anything other than boot to recovery. I tried running the latest RUU and it fails (presumably because it can't enter fasboot). I tried pressing and holding volume+, -, and the power button at the same time, I tried holding just the volume down button while holding the power button, but no luck so far.
Is there a way to reflash the recovery from ADB while the phone is in recovery? Is there any other way I can force my phone into fastboot? Can I safely use the method in this thread http://forum.xda-developers.com/showthread.php?t=1990043 to "unbrick" my phone by entering commands via ADB shell while in recovery rather than in terminal emulator? Thanks in advance for all the collective XDA wisdom that I'm sure will help get my phone back up and running.
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
chilaca91 said:
Hey I had the same problem about a week ago. Are you sure you used the latest the RUU file?
Click to expand...
Click to collapse
I'm using RUU_Ville_U_ICS_40_S_TMOUS_2.35.531.7_Radio_1.08ts.50.02.16_10.08e.50.04L_release_279577_signed.exe. I don't think it would matter which one I used though because it gives me an error that says it can't connect to the phone.
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
chilaca91 said:
Try holding down the power button for 10 sec and then let go of the power and hold down the volume button. I had to do this a couple of times until I finally got into the bootloader
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Amazing! That did the trick. Thanks a ton for that info. I knew it would be something simple.
I also had a similar problem. Seemed to occur only when I had the USB cable plugged into the phone. Once I removed it, I could then get into fastboot. Once I was in fastboot, I simply plugged the USB cable back in, and everything worked flawlessly.
All that crap you got wouldn't have happened if you use TWRP instead of CWM.
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
Suddenly my phone (z710e) jumped into a loop boot.
It's not rooted, no custom stuff, no custom bootloader.
It loads fine, but after 1-2 seconds reboots.
I've already tried to unbrick it with no result, computer can't see my phone.
Help with an advice or a link or anything useful will be great!
Thanks!
S1R1N said:
Suddenly my phone (z710e) jumped into a loop boot.
It's not rooted, no custom stuff, no custom bootloader.
It loads fine, but after 1-2 seconds reboots.
I've already tried to unbrick it with no result, computer can't see my phone.
Help with an advice or a link or anything useful will be great!
Thanks!
Click to expand...
Click to collapse
If i remember correctly you can wipe cache from the stock recovery. Boot into hboot by holding down volume down and power. Use the volume buttons to highlight recovery and press power. Then you will see a little android or a red exclamation in a triangle. Press the volume buttons and power until options appear on the screen. If it gives you wipe cache, them wipe it. Other wipe options may/will remove your personal data so use caution and know the risks
Sent from my nexus 7 using Tapatalk
heavy_metal_man said:
If i remember correctly you can wipe cache from the stock recovery. Boot into hboot by holding down volume down and power. Use the volume buttons to highlight recovery and press power. Then you will see a little android or a red exclamation in a triangle. Press the volume buttons and power until options appear on the screen. If it gives you wipe cache, them wipe it. Other wipe options may/will remove your personal data so use caution and know the risks
Sent from my nexus 7 using Tapatalk
Click to expand...
Click to collapse
unfortunately power+volume doesn't work.. it just boots as usual (
S1R1N said:
unfortunately power+volume doesn't work.. it just boots as usual (
Click to expand...
Click to collapse
did you remove first the battery and then put it back?
S1R1N said:
unfortunately power+volume doesn't work.. it just boots as usual (
Click to expand...
Click to collapse
Okay, remove your battery then replace after 10 seconds. Then hold volume down first, then while volume down is still depressed begin holding power as well. If you see the htc splash screen then it has failed. Battery pull and try again. Have you ever used adb on this device?
Sent from my Desire S using Tapatalk
Edit: removed incorrect data.
heavy_metal_man said:
Okay, remove your battery then replace after 10 seconds. Then hold volume down first, then while volume down is still depressed begin holding power as well. If you see the htc splash screen then it has failed. Battery pull and try again. If it fails after 3 battery pulls then your device has fast boot enabled in its settings. Have you ever used adb on this device?
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
it doesn't matter if you have fastboot enabled
you can still have access to the bootloader when removing battery and putting it back
heavy_metal_man said:
Okay, remove your battery then replace after 10 seconds. Then hold volume down first, then while volume down is still depressed begin holding power as well. If you see the htc splash screen then it has failed. Battery pull and try again. Have you ever used adb on this device?
Sent from my Desire S using Tapatalk
Edit: removed incorrect data.
Click to expand...
Click to collapse
I've tried to remove battery and reboot before, nothing changed.
adb - no, did not used
Solution was - to disassemble it and assemble... After that phone booted normally. :victory:
Thank you all for your replies!
Hi there,
Kindly help... I successfully installed B512 on my TL10 using force upgrade method, afterwhich I changed recovery to TWRP 3.0.2 using mobopx v2.2, which was also successful. And then I installed SuperSU 2.46 via TWRP, then cleared cache/dalvik. But upon rebooting system, I get a blank screen, even after waiting for more than 15 minutes.
And so I tried going to TWRP (Vol+ and power), which was successful, in order to boot to bootloader, with the intention of loading back the stock bootloader via adb, so that I can force install B512 from my microSD card again. It seemed to install fine...
However, at this point, I cannot reboot to bootloader (Vol- and power) anymore, I only get blank screen. Trying recovery (Vol+ and power) doesn't work either. Rebooting normally gives me the same. I cannot by any means connect via adb now.
Is there any way to unbrick my phone at this point?
Thanks so much. Cheers.
Works entrance for the recovery (Vol+ and Vol- and Power)?
rakrakrak said:
Works entrance for the recovery (Vol+ and Vol- and Power)?
Click to expand...
Click to collapse
No bro...
eusagc said:
However, at this point, I cannot reboot to bootloader (Vol- and power) anymore, I only get blank screen. Trying recovery (Vol+ and power) doesn't work either. Rebooting normally gives me the same. I cannot by any means connect via adb now.
Click to expand...
Click to collapse
What happens when you do a Vol up + power?
CloudCompute said:
What happens when you do a Vol up + power?[/QU
The phone "doesn't want to turn off" bro. It has fully discharged, but as soon as I plug the charger in, it immediately powers up. When it does, now it shows the Huawei logo. But it's stuck there, and if I press the power button for a few secs, it will power down, but immediately power up again...
Click to expand...
Click to collapse
eusagc said:
CloudCompute said:
What happens when you do a Vol up + power?[/QU
The phone "doesn't want to turn off" bro. It has fully discharged, but as soon as I plug the charger in, it immediately powers up. When it does, now it shows the Huawei logo. But it's stuck there, and if I press the power button for a few secs, it will power down, but immediately power up again...
Click to expand...
Click to collapse
Let it get fully charged first. Then remove the charger and keep the Vol up and power button pressed for ~10 secs or more, and see where it takes you.
Click to expand...
Click to collapse
CloudCompute said:
eusagc said:
Let it get fully charged first. Then remove the charger and keep the Vol up and power button pressed for ~10 secs or more, and see where it takes you.
Click to expand...
Click to collapse
Ok dude, will do. Thanks!
Click to expand...
Click to collapse
CloudCompute said:
eusagc said:
Let it get fully charged first. Then remove the charger and keep the Vol up and power button pressed for ~10 secs or more, and see where it takes you.
Click to expand...
Click to collapse
Done bro. Although I must say, I'm kinda back like yesterday when the phone is just helplessly discharging until it drops dead. Pressing vol+ and power restarts the phone, but I'm still stuck at the logo...
Click to expand...
Click to collapse
CloudCompute said:
Done bro. Although I must say, I'm kinda back like yesterday when the phone is just helplessly discharging until it drops dead. Pressing vol+ and power restarts the phone, but I'm still stuck at the logo...
Click to expand...
Click to collapse
You seem to be in a sticky situation bro. Your recovery seems to be broken because in stock recovery Vol up + power should ideally take you to recovery and not restart. If you could somehow boot into fastboot mode then it could open up some options to bring your phone to life.
With no way to connect to the phone the only options left are the hardware buttons. I am sure you'd have tried them already, but just in case you have not, try the other 2 key combinations also, Vol down + power and Vol up + Volume down + power, for ~10 secs, to check if any of these either forces a factory reset or boots the phone into fastboot mode.
eusagc said:
Hi there,
Kindly help... I successfully installed B512 on my TL10 using force upgrade method, afterwhich I changed recovery to TWRP 3.0.2 using mobopx v2.2, which was also successful. And then I installed SuperSU 2.46 via TWRP, then cleared cache/dalvik. But upon rebooting system, I get a blank screen, even after waiting for more than 15 minutes.
And so I tried going to TWRP (Vol+ and power), which was successful, in order to boot to bootloader, with the intention of loading back the stock bootloader via adb, so that I can force install B512 from my microSD card again. It seemed to install fine...
However, at this point, I cannot reboot to bootloader (Vol- and power) anymore, I only get blank screen. Trying recovery (Vol+ and power) doesn't work either. Rebooting normally gives me the same. I cannot by any means connect via adb now.
Is there any way to unbrick my phone at this point?
Thanks so much. Cheers.
Click to expand...
Click to collapse
Go back to stock recovery reflash stock rom make sure you have a unlocked bootloader......all remember that Google is your friend.....
CloudCompute said:
You seem to be in a sticky situation bro. Your recovery seems to be broken because in stock recovery Vol up + power should ideally take you to recovery and not restart. If you could somehow boot into fastboot mode then it could open up some options to bring your phone to life.
Click to expand...
Click to collapse
That's correct bro. Although it appears from adb that I was able to install the stock recovery, I cannot access it with Vol+ and power.
CloudCompute said:
With no way to connect to the phone the only options left are the hardware buttons. I am sure you'd have tried them already, but just in case you have not, try the other 2 key combinations also, Vol down + power and Vol up + Volume down + power, for ~10 secs, to check if any of these either forces a factory reset or boots the phone into fastboot mode.
Click to expand...
Click to collapse
Yes, I did. And I can't even boot to bootloader after all that... The phone only seems to charge, but is stuck at the logo.
I'm ready to send this to Huawei's service center. Is there anything more I can do at this point before I do that? Thanks so much.
stinka318 said:
Go back to stock recovery reflash stock rom make sure you have a unlocked bootloader......all remember that Google is your friend.....
Click to expand...
Click to collapse
Thanks bro, but that's what I did, or at least was planning to do. After rooting B512 via TWRP, the phone got stuck at the logo. And so I tried to install stock recovery, which it did, in order to reflash the stock ROM. But at this point I'm still stuck at the logo, and I can't access recovery and BL anymore. The BL is unlocked right from the start...
eusagc said:
Thanks bro, but that's what I did, or at least was planning to do. After rooting B512 via TWRP, the phone got stuck at the logo. And so I tried to install stock recovery, which it did, in order to reflash the stock ROM. But at this point I'm still stuck at the logo, and I can't access recovery and BL anymore. The BL is unlocked right from the start...
Click to expand...
Click to collapse
Did you try volume down and then plug USB in on computer then command prompt fast boot reboot it may work.
eusagc said:
I'm ready to send this to Huawei's service center. Is there anything more I can do at this point before I do that? Thanks so much.
Click to expand...
Click to collapse
Go ahead, send it to Huawei service centre. They'll have ways to reach the internal memory after opening up the device.
stinka318 said:
Did you try volume down and then plug USB in on computer then command prompt fast boot reboot it may work.
Click to expand...
Click to collapse
Thank you for this suggestion brother. I tried exactly as you described, however, the phone looks badly discharged, and while the screen was blinking/showing the red battery icon, it doesn't seem to want to charge. I waited around 5 minutes, but nothing seems to progress from here.
And so now, I moved the USB cable to a proper charger, and now it seems to be charging, with the LED light a steady red, and the screen the normal red circle with "0%" inside. It seems to be charging at the moment, although I really have to wait until it shows "1%" until I can surely say so.
One thing that's different now is that the phone hasn't turned on (by itself) yet. And at least this looks promising.
I'll let you know what happens in a while... Thank you!
eusagc said:
Thank you for this suggestion brother. I tried exactly as you described, however, the phone looks badly discharged, and while the screen was blinking/showing the red battery icon, it doesn't seem to want to charge. I waited around 5 minutes, but nothing seems to progress from here.
And so now, I moved the USB cable to a proper charger, and now it seems to be charging, with the LED light a steady red, and the screen the normal red circle with "0%" inside. It seems to be charging at the moment, although I really have to wait until it shows "1%" until I can surely say so.
One thing that's different now is that the phone hasn't turned on (by itself) yet. And at least this looks promising.
I'll let you know what happens in a while... Thank you!
Click to expand...
Click to collapse
Charging's at 4% now... And the phone hasn't turned on so far... Looks promising...
eusagc said:
Charging's at 4% now... And the phone hasn't turned on so far... Looks promising...
Click to expand...
Click to collapse
All well now?
CloudCompute said:
All well now?
Click to expand...
Click to collapse
I was out of town for the past few weeks and didn't have time to do this. I'm back now and plan to work on this tonight. Thank you bro, I'll let you know how it goes...