Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
undecidable said:
Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
Click to expand...
Click to collapse
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
BerndM14 said:
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
Click to expand...
Click to collapse
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
---------- Post added at 06:21 AM ---------- Previous post was at 06:10 AM ----------
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
philz_touch_6.26.6-m8.img
philz_touch_6.41.6-m8.img
philz_touch_6.43.6-m8.img
Maybe you have wrong version if you use international version.
Download newest one here and reflash. That is IF you use international.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8
BerndM14 said:
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
Click to expand...
Click to collapse
A system reset is no problem. I already did one before starting, and it is new. So no data/apps to lose.
Yes, spent about 6 hours searching last night. Haven't come across anything like it.
Plus, there doesn't seem to be a CWM thread for the HTC One M8 - there are threads for TWRP and Philz (CWM Advanced).
got info below nevermind =oD
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
Click to expand...
Click to collapse
I'm not using philz, I'm using standard CWM:
http://clockworkmod.com/rommanager
which is the recommendation in the Cyanogenmod instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_m8
So I think my version of CWM is correct.
BerndM14 said:
Yeah just linked the same to you now as well. Where did you get that version from then?
Nevermind, I got where you downloaded it from http://forum.xda-developers.com/showthread.php?t=2708520
So you're on Verizon?
Click to expand...
Click to collapse
No, I have the international version, and the recovery is from
http://clockworkmod.com/rommanager
the last line on the page, labelled M8.
I think it is the official version.
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
BerndM14 said:
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
Click to expand...
Click to collapse
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
undecidable said:
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
Click to expand...
Click to collapse
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
BerndM14 said:
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
Click to expand...
Click to collapse
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
undecidable said:
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
Click to expand...
Click to collapse
https://www.google.co.za/search?q=w...ite:forum.xda-developers.com&biw=1920&bih=979
Tossed in plenty of keywords into google, of course doing it normally gives a lot of results from other sites too but I just decided to narrow it down to xda(Most sites refer help questions to xda anyways so...)
I think it's better to use Google for searches anyways, it records info from a lot of sites. XDA works on a "keyword" basis it seems and most people when making threads don't really add any keywords to it so finding it is difficult. Heck, I even had issues finding HTC__622 in a thread where I knew for a FACT HTC__622 was mentioned at least 4 times, the results in xda itself turned up nothing.
I didn't even bother to try and search within xda for this issues, went the Google route and narrowing it down to xda, much better :good:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
BerndM14 said:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
Click to expand...
Click to collapse
Thanks. I did try an XDA search from G, but you are just better at it
There is code that gets executed when you plug in the power cable:
it shows the battery charging.
The battery charging icon that is showing just before boot into CWM recovery is different from the normal battery charging icon (that I can see when I have settings /power / fastboot on).
I wonder if CWM changes that code? If that is the case, flashing TWRP might not fix it - will soon know.
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
This build is for Developement Purposes only
Do not distribute outside of HTC
without HTC Permission...
Click to expand...
Click to collapse
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
....
Will now try flashing philz.
Click to expand...
Click to collapse
Philz does exactly the same as CWM - not surprising given that it is CWM based.
So have returned to TWRP, which is at least usable.
Any idea how to file a bug against CWM?
Philz I can do on their forum here.
undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
Click to expand...
Click to collapse
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
BerndM14 said:
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
Click to expand...
Click to collapse
Yes, found the post for Remove Red Text on Splash screen early this morning. Seems to be related to Root, and separate from the TWRP issue.
I have to wonder if the TWRP problems aren't caused by the initial flashing of CWM. Anyway will post the issue on the TWRP forum tomorrow and see what they say.
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
I have to say, this is the last HTC phone I buy - Samsungs are so much friendlier to flashing. Also I greatly dislike the big Tampered sign.
Reason for flashing recovery this time is I wanted root so I could remove garbage from the phone.
I don't flash ROMs much. High learning curve and risky. I do just one flash: from stock to CyangenMod. so much nicer it is worth it. I have to say if I had to choose between my old S3 with CyanogenMod and a stock M8, it would be the S3. If I can't get the garbage off the M8, I will just put it in a drawer till CyM goes stable for it.
Solved: Power Down reboots into Recovery
undecidable said:
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
Click to expand...
Click to collapse
The solution! From the Philz M8 thread.
http://forum.xda-developers.com/showthread.php?p=53464839
An earlier version of Philz: 6.26.6-m8.zip.
The earlier version doesn't have the problem.
Thanks to @donmarkoni
Related
Hey, I rooted, s-off/hbooted my phone and used Clockworkmod to install a ROM.
Now it won't go away no matter what I've tried and I want to be able to turn my phone off and charge it without seeing that annoying recovery screen.
I've backed up all my apps on to SD, wiped data and factory resetted with CWM and the phones built in factory reset yet it still comes back to haunt me.
What do I need to do to make this go away and revert my phone back to it's original out of box state?
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Install the correct HTC RUU for your desire hd.
prank1 said:
Install the correct HTC RUU for your desire hd.
Click to expand...
Click to collapse
Much appreciated, you get my first thanks.
For anyone else in need here's where I got mine (every other ROM and RUU is there too)
http://forum.xda-developers.com/showthread.php?t=868610
Just to be sure, can I just put the RUU on my storage card and use CWM recovery to install it?
Thanks for the.. thanks lol
I don't know but it really doesn't matter, better if you flash it from bootloader. If you were eng hboot s-off then your dhd will become 100% stock (if you installed the correct htc ruu). If you were radio s-off you will still have s-off afterwards. I don't think this affects warrentee issues as long as you have installed the correct rom.
On another note, I am sure I read somewhere some instructions on how to calibrate your battery and fix this problem. But you may have to do a little searching for it.
Sent from my Desire HD using XDA App
even on stock the phone goes into recovery anyway just it don't show the recovery screen. reason it does so i've read is for the led light to come on lol
spookamiester that link just brings you back to this thread so i've placed a link to all HD files and it has all the RUU files there
http://forum.xda-developers.com/showthread.php?t=841207
just check the first two links for ruu files
and a guide here to install ruu's
http://forum.xda-developers.com/showthread.php?t=864054
spookamiester said:
CWM should come with an uninstall guide and a notice of how annoying this is, I see it's quite a widespread problem for everyone trying to calibrate the battery with no clear answer
Click to expand...
Click to collapse
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
and to answer the question, reflash with the appropriate RUU
Or just flash recovery.img from a stock rom
Is the s-off that stops the receiving of OTA's ?
Sent from my Desire HD using XDA App
ghostofcain said:
Maybe I am being simple but I see this posted everywhere as a problem, it in no way affects battery calibration, yes when the phone is turned off and plugged in it boots into recovery (it also does this with the stock ROM) so what? It's still charging and from CW you can then wipe the battery stats which is required to complete your calibration anyway.
What exactly is the problem with it booting into CW when turned off and plugged in
Click to expand...
Click to collapse
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
spookamiester said:
First of all I'd like to thank everyone for the responses, should be able to get things sorted now.
In response to the charging in CWM, I tried it for over an hour after full charge on and the LED remained amber, I turned the phone back on and the battery was at 99% which leads me to believe that it doesn't actually charge in CWM recovery, I tried this on stock and within 10 minutes after full charge on I got the green light off. I've asked in other threads if anyone can confirm the phone charge whilst in CWM but so far no confirmation, just similar results.
I'll keep my eyes pealed for answers but I don't think it works with CWM and can't find a way to charge whilst off without CWM recovery popping up.
Click to expand...
Click to collapse
I have spent quite a while in recovery and I am fairly sure it's charging I wouldnt be surprised that the green led didn't function though? I don't really see how it wouldn't charge surely it a hardware thing when the power is attached?
Update: I use QtADB to give a GUI interface to ADB, have spent the past 15 minutes monitoring the battery state whilst in Clockwork recovery and it is most defintetly charging so you needn't worry about that
I bought the phone from Hong Kong with stock ROM. Rooted, S-Off and installed CWM but never flashed any ROM. But I have same the problem, screen will boot to recovery when I want to charge. I found there are a lot of DHD guys have the same problem here in China or Hong Kong..... and no solution found in any forum here yet. Some said it's a bug on CWM.
Anyway. I found an alternative myself. Instead of using the DHD original charger, I used the I9000 charger to charge the DHD. It worked perfectly (100% charged) and no recovery screen appeared so far......
Hey guys!
I have the original Desire HD stock ROM but I have clockwork mod recovery.
Could you guys provide a step by step guide on how to remove and replace with original recovery image?
I would really appreciate all the help!
xmoo said:
Or just flash recovery.img from a stock rom
Click to expand...
Click to collapse
I have a file recovery.img. How do I flash it to the DHD?
I'd like to know this as well. I have the Clockwork bootloader installed. It's OK, but I changed my mind - I'd like to keep this phone as close as possible to factory-standard and use a different phone for hacking. Is there a step-by-step guide to reverting a DHD back to normal so I can benefit from the regular OTA updates?
Thanks!
Reflashing the ruu is the hard and long way.
Just download the stock recovery.img which west2cool was good enough to post for me. (Cheers again I didn't really feel like installing windoze just for that).
Then use fastboot - "fastboot flash recovery recovery.img"
dr.m0x said:
Then use fastboot - "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
And make sure it is FASTBOOT mode. Flashing fails otherwise (unless I did something stupid).
Sorry, I'm a newb at this.
When I boot by doing vol-down + pwr I get a mainly white screen with three Androids skateboarding at the bottom. At the top it says
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
The top option is "FASTBOOT", so I press pwr once to select that.
Next I see four options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I do not see an option to reflash a recover image.
If I go into "RECOVERY", I see the green text on a black background of ClockworkMod v2.5.1.3. There is an option to apply an update.zip, however that's clearly not the same thing as I was instructed to do.
Detailed step by step instructions would be much appreciated!
THANKS!
I'm resurrecting my laptop with ubuntu 10.10 x64 right now (so I can build gingerbread) so can't help until later. If someone doesn't beat me to it, I will up a proper set if instructions along with the links you will need once my laptop is fully functional again.
Sent from my performance enhanced Desire HD
Ok buddy, my lappy lives again
1. Download the recovery.zip posted earlier on in the thread.
2. Extract recovery.img from the recovery.zip (best to extract it somewhere easy like a new folder called c:\fastboot)
3. Download fastboot from here. http://developer.htc.com/adp.html#s2
4. Make sure fastboot.exe and recovery.img are in the same directory (e.g. c:\fastboot)
5. Reboot your phone as you did before (while holding vol down + power)
6. Select fastboot and push the power button
7. Plug your phone into your computer - it should change the message to "FASTBOOT USB"
8. Open a terminal (push start button and type in "cmd" to get one if you don't know how).
9. Type "cd c:\fastboot" and press enter.
10. Type "fastboot flash recovery recovery.img"
11. You should see a message which says something like sending ... send complete ... done.
12. To test: Push the power button on your phone once, push volume down once to highlight recovery, push power button. It should boot you to a screen with a red triangle.
13. Push vol up + power button to bring up the stock recovery menu
14. Push power button to reboot
Hopefully thats detailed enough
So I have my old phone, and wanted to use it as a media player. I chose to use UberSonic RC3, however after I've flashed this, it will sit at the bootloader if it's plugged in, until I unplug the phone and reset it and let it boot up. Hboot 2.18.0001 with S-off as well, so everything flashed right from what it seems, though if I hold Vol up and Power on it keeps vibrating but no screen. Anyone else run into this? Could it be that I've got a bad flash on the bootloader partly causing any issues?
Thanks
gdeeble said:
So I have my old phone, and wanted to use it as a media player. I chose to use UberSonic RC3, however after I've flashed this, it will sit at the bootloader if it's plugged in, until I unplug the phone and reset it and let it boot up. Hboot 2.18.0001 with S-off as well, so everything flashed right from what it seems, though if I hold Vol up and Power on it keeps vibrating but no screen. Anyone else run into this? Could it be that I've got a bad flash on the bootloader partly causing any issues?
Thanks
Click to expand...
Click to collapse
Volume up + power doesn't do anything. When powered off, volume down + power will pull up the bootloader. What recovery are you using?
Sent from my EVO using xda premium
TWRP 2.3.3.0 . Sorry I was exhausted last night and knew I would miss something of key relevance, when typing the post it. When I do it, I just get the 3 vibrates and nothing. The big problem for me is that the phone won't get past the bootloader when plugged in to a source though, however, if we can figure out both things, that would be awesome. The other thing is that my bootloader has been unlocked via HTC Dev as well as the S-off. Is that a big no no?
Edit:
I Just updated to 2.5.0.0 via GooManager. Same issues still occur so I'm pretty sure it's not recovery causing the issue, but then again I'm not an expert with it either.
gdeeble said:
TWRP 2.3.3.0 . Sorry I was exhausted last night and knew I would miss something of key relevance, when typing the post it. When I do it, I just get the 3 vibrates and nothing. The big problem for me is that the phone won't get past the bootloader when plugged in to a source though, however, if we can figure out both things, that would be awesome. The other thing is that my bootloader has been unlocked via HTC Dev as well as the S-off. Is that a big no no?
Edit:
I Just updated to 2.5.0.0 via GooManager. Same issues still occur so I'm pretty sure it's not recovery causing the issue, but then again I'm not an expert with it either.
Click to expand...
Click to collapse
Have you tried a different recovery?? mainly just to rule it out completely... i highly recommend SmelkusMod of AmonRa, http://forum.xda-developers.com/showthread.php?t=1661543.
angryITman said:
Have you tried a different recovery?? mainly just to rule it out completely... i highly recommend SmelkusMod of AmonRa, http://forum.xda-developers.com/showthread.php?t=1661543.
Click to expand...
Click to collapse
I have tried a few, including the one you mentioned. It still does the 3 buzzes with vol + and power, and will still continue to stick on the bootloader and reboot there. I think it might be the rom but hard to tell. Do keep in mind, I have S-off and did the HTCDev unlock so.
gdeeble said:
I have tried a few, including the one you mentioned. It still does the 3 buzzes with vol + and power, and will still continue to stick on the bootloader and reboot there. I think it might be the rom but hard to tell. Do keep in mind, I have S-off and did the HTCDev unlock so.
Click to expand...
Click to collapse
did you double check the MD5 after you downloaded UberSonic?? maybe its just a bad download. check it with MD5 Check Utility, or any other version. or try another rom. make sure to Wipe Data/Factory Reset & Wipe Dalvik Cache.
angryITman said:
Have you tried a different recovery?? mainly just to rule it out completely... i highly recommend SmelkusMod of AmonRa, http://forum.xda-developers.com/showthread.php?t=1661543.
Click to expand...
Click to collapse
angryITman said:
did you double check the MD5 after you downloaded UberSonic?? maybe its just a bad download. check it with MD5 Check Utility, or any other version. or try another rom. make sure to Wipe Data/Factory Reset & Wipe Dalvik Cache.
Click to expand...
Click to collapse
It seems that it works fine when it's not plugged in. It's like the bootloader is jacked up when it detects power. I'm gonna try to do a full system wipe and reflash it though to ensure 100% that it's not that.
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
I'm running CM11 on my M8 and use TWRP 2.7.1.0 as my recovery,
the problem is, when I charge my phone when turned off, it boots straight into TWRP, without me pressing volume down or something.
Then the screen flickers between TWRP and the charging screen, which is really annoying.
anytime I turn on the phone to check the battery status, it reboots into TWRP.
Is there a way to fix this?
I can't use stock recovery because I need TWRP in order to update CM11 nightlies.
I've googled about it but I haven't found ANYTHING :/
Far as I know, its a known issue for a long time, and don't know why TWRP hasn't been fixed.
Not really a solution, but why charge the phone with power off at all? I just about never turn my phone off. The only reason I noticed this at all was by mere chance. I think the phone had powered off during the root/s-off process, and that is the only time I've noticed this bug.
Have you tried CWM?
I give it a try.
Is this the correct file? http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.8-m8.img
I flashed CWM, the issue still exists!
Same issue as stated above. I wonder if Philz Recovery works better. Ill probably give that a try later.
Same Problem
jaxenroth said:
Same issue as stated above. I wonder if Philz Recovery works better. Ill probably give that a try later.
Click to expand...
Click to collapse
Anyone find a solution yet? Also seems to make the battery level jump around when you turn it on and off during charging.
What ever it may be the best recovery is TWRP for me anyways. For me I had several issues with CWM, like flashing and installing of ROMS.
Well I too have this bug but its not a great scene. Adjustable
I am in need of some serious help. My AT&T M8 won't boot past the HTC logo screen and won't allow me to go into recovery or the hboot screen. I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen. It was so bad that I just left it plugged in overnight and I don't have a clue as to how long it took to power off because I fell asleep before it did. If there's a video tutorial out there that someone has or simply a link that can show me how to install something via backdoor on this device, that would be great!
alpinesun said:
I believe I may have wiped the OS on it; this is the only thing I can think of that makes sense. !
Click to expand...
Click to collapse
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
alpinesun said:
Furthermore, when I try to power down the device by long pressing the power button, it doesn't respond at all. It just stays on the logo screen.
Click to expand...
Click to collapse
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Thanks already. I didn't realize I had to hold down the volume down button after it goes dark. It got me into twrp. I believe I should be good from here after I download a new rom to sideload. But to give you a run down, I was prepping the phone to sell it by wiping the data and installing the rom the guy said he wanted on it. When I was going thru the normal procedure to install the rom (wipe, flash, etc) that's when the phone started sticking on the logo screen. My assumption was that I downloaded a bad rom, so since then I've been trying to get back into twrp so I can load a new rom and finally was able to after you told me this. I'll report back if a new rom actually didn't help the situation. I only thought I wiped the OS because something similar happened with my Note when I was tinkering and that was the result.
alpinesun said:
I'll report back if a new rom actually didn't help the situation.
Click to expand...
Click to collapse
If you need any further help, please answer all the questions I previously asked.
Good luck.
redpoint73 said:
Recount as best you can, all the steps that got the phone to this point.
What were you trying to do when this happened?
Also, need much more info in order to help:
1) bootloader unlocked?
2) custom or stock recovery
3) custom ROM?
4) what hboot number?
5) s-on or s-off
6) did you make a nandroid with custom recovery?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons, and just hold vol down. Don't let go until the hboot screen appears.
Click to expand...
Click to collapse
So, it seems I'm still having the problem, even while trying to install cyanogen. Here are the answers to those questions...
1) bootloader unlocked?... YES
2) custom or stock recovery... TWRP
3) custom ROM?... It was a custom AOSP Rom
4) what hboot number?... 3.16.0.0000
5) s-on or s-off... S-OFF
6) did you make a nandroid with custom recovery?... It was erased
Any help you can give from this point would be awesome. Thanks again!
alpinesun said:
So, it seems I'm still having the problem, even while trying to install cyanogen.
Click to expand...
Click to collapse
Failure to flash ROMs can often be solved with fastboot erase cache, then install TWRP by fastboot again. Update TWRP version, if you are using an outdated one.
Also, if you try to flash any ROMs based on Sense software beyond version 1.x (huge majority of them are past 1.x at this point) you will likely experience extremely long boot times (10 minutes or more) and broken WiFi due to outdated firmware. But CM should be okay.
alpinesun said:
6) did you make a nandroid with custom recovery?... It was erased
Click to expand...
Click to collapse
It was erased, or you wiped it?
Okay. Do you suggest trying an older sense rom to see if it works? The last time touched the phone was when I picked up my Note 4, so I will look for something that predates that.
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
alpinesun said:
Okay. Do you suggest trying an older sense rom to see if it works?
Click to expand...
Click to collapse
Sure, it couldn't hurt. With your current firmware, you will need a ROM based on 1.x software. There aren't a heck of a lot of those left. But there are a few. GoldenEye is one I can personally vouch for, since I was running it for a while back in the day:
http://forum.xda-developers.com/showthread.php?t=2705640
But I would definitely recommend just trying fastboot erase cache and re-install TWRP first. I've lost count how many times suggesting this simple fix has helped other users here on XDA, when ROMs fail to flash.
alpinesun said:
As for the nandroid being erased, I can only assume it was my actions that caused it to be deleted, but I don't recall intentionally doing it.
Click to expand...
Click to collapse
Fair enough. Just FYI, don't do a factory reset in bootloader (in the OS settings or recovery is OK). On modded phones this may cause the internal storage to become corrupted. Nandroids have sometimes been lost this way. This may or may not be what happened to you. Just wanted to throw that out there.
Also, there has been the occasional occurrence of internal storage being corrupted, possibly by TWRP. It may not even have been something you caused.