Hello all,
A friend just purchased a used G2. I was able to take it from stock 2.3.x ROM, downgrade it, and then root it and load a CM7 KANG on it just fine. I then updated CWMR to the latest version for this phone (5.0.2.7) through ROM Manager.
I noticed that if I have the battery in and the phone off, when I plug in a USB cable, the phone boots directly to CWMR (no HTC screen) after about 7 seconds. Searching on the forums it looks like this was a CWMR issue that was fixed earlier in 2011. Is this a regression in CWMR or is something else up?
Stranger still: if I leave CWMR up, the CWMR text on the screen disappears after 20 seconds and the whole screen is blank. The phone seems to stay on though as I can now boot it by pushing the black button at the bottom center of the phone (OK/Confirm in CWMR) or the Power button. Normally when the phone is unplugged it only boots via the push of the Power button.
Any tips would be appreciated. Thank you XDA!
Clockword 5.x.x.x has issues on the G2 - I would recommend going to Rom Manager, go to "All ClockworkMod Recoveries," and choose 3.0.2.4, or flash that manually.
That fixed it! Thanks!
Sent from my Nexus S using xda premium
Related
I installed the latest build of Cyanogen Mod 7 on MyTouch 4G, and everything went smoothly, but now my phone won't turn on at all. Nothing happens when I hit the power button. Not even a splash screen which I thought was weird. I have a recovery file, but if I can't access the bootloader/recovery screen, can't really recover it.
Any suggestions? I luckily have a backup Windows phone 7 near me (HD2), but I'm just wondering if the MyTouch 4G can be recovered.
Thanks!
Edit: Also note, that I can't do anything, including hboot, fboot, get anywhere. It will not power on, and looks like it won't recharge as well.
Edit #2: Uh..looks like taking out the Sim Card worked.
Have you try pressing volume key down and power at the same time to get into Hboot then scroll down into recovery and wipe
Sent from my HTC Glacier using XDA App
For the longest time, I couldn't power it up until I took out the sim card. Which I finally figured out. I'm doing the wipe right now, thankfully. I'm trying to figure out now what I did wrong...
Thats gotta be scary im running cm7 now had no problems flashing any of the builds knock on wood lol
Sent from my HTC Glacier using XDA App
this happened to me earlier when i pushed/flashed/installed (whats the correct term here?) CM 6.1.2 on to my phone. i thought i did it right then i went to reboot and it just shut off. wouldnt turn on or anything. thought i ****ed up and bricked it. after taking battery/sd card/sim card out it worked though.
it was SO relieving.
Is CM7 not stable?
Battery Pull
All you have to do is a batt pull (no sim or ext. sd) and go into H Boot ( Hold bottom volume buttton and then power on button & hold until you see letters and release both buttons and you will be in H Boot) then hit recovery. If that doesnt work and your flash screen is stuck, go back to H Boot, hit recovery...wait for green letters up top, go down to backup and restore then hit restore.
I have the same problem
I tried to Flash the cyanogen mod, i followed the prompts i click the button where its supposed to go into recovery, then completely blank screen. I left it for 15 minutes then took the battery in then out but now it won't power on and shows no sign of life. PLEASE HELP ME. the sim card thing doesn't seem to work for me.
HELPMEPLEASE!!! said:
I tried to Flash the cyanogen mod, i followed the prompts i click the button where its supposed to go into recovery, then completely blank screen. I left it for 15 minutes then took the battery in then out but now it won't power on and shows no sign of life. PLEASE HELP ME. the sim card thing doesn't seem to work for me.
Click to expand...
Click to collapse
Does the LED show when you connect the phone to a power source? Can adb see your phone?
Sent from the HTC Glacier Sense 3.0 using XDA premium app
saranhai said:
Does the LED show when you connect the phone to a power source? Can adb see your phone?
Sent from the HTC Glacier Sense 3.0 using XDA premium app
Click to expand...
Click to collapse
No, it doesn't power on or show the LED screen at all.
And also doesn't show up on ADB.
wrong recovery image
If you are flashing cyanogen 6, use clockworkmod 2..x. If you are flashing cyanogen 7, use clockworkmod 3..x
Not sure why some roms don't work on clockwork mod 2..x.... Maybe a limitation in a past clockworkmod which was fixed in a later version.
xmc wildchild22 said:
If you are flashing cyanogen 6, use clockworkmod 2..x. If you are flashing cyanogen 7, use clockworkmod 3..x
Not sure why some roms don't work on clockwork mod 2..x.... Maybe a limitation in a past clockworkmod which was fixed in a later version.
Click to expand...
Click to collapse
it's because clockworkmod recovery 2.x only flashes up to ext3 filesystems. the new clockworkmod recoveries, anything above v3.x has support for both ext3 and 4 filesystems. since cyanogenmod 7 has an ext 4 filesystem, the ROM will not flash correctly on clockworkmod 2.x.
Yes, I searched, but nothing I found seemed similar to my situation.
Here is the timeline of events:
Rooted my nook with autonooter a long time ago.
Decided last weekend that I wanted to install CM7.
Installed Rom Manager, CWM, etc. Then installed CM7.
Decided that I wanted to bring my nook back to stock so I could check out the 1.2 update.
Restored it back to stock using Option #1 in this thread: http://forum.xda-developers.com/showthread.php?t=914690&highlight=reset+stock
It worked fine the past few days.
Then last night I decided I would try this: http://forum.xda-developers.com/showthread.php?t=1045018
I burned the image to the SDcard, expanded the partition in order to be able to use the SDcard for storage. Placed the sdcard in my nook.
It wouldnt boot at all. The screen refused to turn on.
I tried it many different ways, holding the 'n' button while turning it on, holding the volume buttons, etc.
Then i took the sdcard out of the nook and tried booting it.
It still wouldnt turn on. The screen simply would not turn on. Finally after a few tries, it did turn on. So I shut it off for the night and thought I'd try again today.
I tried to turn it on again today (without the sdcard in the nook) and it will not turn on. I've tried it about 25 times. Holding the power button for many different time intervals.
And yes, its charged. It was fully charged last night.
Any idea what I can do here??
Connect it with power cable (no matter if its charged) and try to turn it on by Power button.
Then restore it to original rom.
RASTAVIPER said:
Connect it with power cable (no matter if its charged) and try to turn it on by Power button.
Then restore it to original rom.
Click to expand...
Click to collapse
Unfortunately, I'm at work and dont have my power cable with me.
I have a compatible USB cable that I can plug into the computer, but I already tried that and it didnt work.
Also, the nook should be on the stock rom already. It was on stock 1.2 before I tried the dualboot sd card last night.
OK, so I just tried turning it on for the 50th time today, and for some reason it worked.
It was not plugged into anything, I didnt do anything differently.
Just held the power button.
Anyone have any idea what could be causing this?
My nook is stock 1.2.
I had a similar problem, and I thought mine was bricked. I used WinImage to create a ClockworkMod boot microSD card. Holding the power button for ten seconds performs a manual power down, release, then hold it for another three to five seconds. It will boot to ClockworkMod Recovery.
Now, I had installed HC update RC3 from a week ago, and it worked just fine. The dev releases a hybrid with the Asus Eee Pad Transformer this week, and I tried updating to it. It caused my Nook screen to not turn on just like yours.
Once in ClockworkMod, I can reinstall the zip files, but it still won't turn the screen on unless in Recovery. When I try to restore my backup of CM7, it says there is an "MD5 error." Not sure what that is or how to fix. Maybe you can help me?
jlscarpa said:
I had a similar problem, and I thought mine was bricked. I used WinImage to create a ClockworkMod boot microSD card. Holding the power button for ten seconds performs a manual power down, release, then hold it for another three to five seconds. It will boot to ClockworkMod Recovery.
Now, I had installed HC update RC3 from a week ago, and it worked just fine. The dev releases a hybrid with the Asus Eee Pad Transformer this week, and I tried updating to it. It caused my Nook screen to not turn on just like yours.
Once in ClockworkMod, I can reinstall the zip files, but it still won't turn the screen on unless in Recovery. When I try to restore my backup of CM7, it says there is an "MD5 error." Not sure what that is or how to fix. Maybe you can help me?
Click to expand...
Click to collapse
Well it sounds like our problems are very different. However, I have some experience with your problem with my thunderbolt.
When I got an MD5 error, it meant that there was something wrong with the name of my backup. Does your backup have spaces in the name? Or did you change the name of it after creating it?
Unfortunately, I was never able to recover the backup with the MD5 error.
If you can get into recovery, it sounds like you should be able to restore your nook to stock via this thread: http://forum.xda-developers.com/showthread.php?t=914690&highlight=reset+stock
If I were you, I would return my nook to stock and start over.
Hi guys,
I struggle from few days with my U8800 pro.
After installing genokolar cyanogen 7 ROM, the device reboot when the screen fade out. If i press the power button 1-2 seconds after fading out evrything is o.k, but a second later the phone reboots. I've tried МIUI rom, and nothing changed. The funny thing is that if the phone is connected to USB it's O.K. and if the screen is on there is no problem either.
I've tried factory reset, whipe cashe, whipe baterry stats but nothing worked.
Any help will be appreciated.
Best Regards,
Yasen
Change CWM Recovery...
if you are using the 32 kernel.
Install Cwm version 4.0.0.5 or 5.0.2.7
Re:
I currently use CWM v. 5.0.2.7, but after updating throug ROM manager, should i flash the ROM with CWM v. 5.0.2.7?
I've tried to flash new ROM with CWM 5.0.2.7 but it's the same. I'm near to compete madness and i need your support guys!!! The baterry have charge, but if i let the screen black for more than 3-4 seconds, when i press the power button it reboots.
What can cause this???
Any suggestions or i am the only one with problem like tais?
Best Rgards,
Hi guys everything f...cked up now. Trying to restore original 2.2 folowing this tutorial: http://forum.xda-developers.com/showthread.php?t=1493403&page=3 my phone is completly damaged. After "update is successful", i have black screen, when i push power button it vibrates ones.. then nothing. I prsume that my phone is for garbage now is it?
Same Isssue
yasenmlad said:
I've tried to flash new ROM with CWM 5.0.2.7 but it's the same. I'm near to compete madness and i need your support guys!!! The baterry have charge, but if i let the screen black for more than 3-4 seconds, when i press the power button it reboots.
What can cause this???
Any suggestions or i am the only one with problem like tais?
Best Rgards,
Click to expand...
Click to collapse
I'm also having the same issue with this rom. If the charger is plugged in it is fine but if not it reboots after 3-5 seconds. Please help!
Thanks in advance
I have read its because you didnt flash official gingerbread before installing cm7..
Ok so I just got my Nexus 7 unlocked and rooted no problem, I have done this on a few Galaxy Nexus phone without issue.
Now here is the strange part, if I adb into bootloader then select boot into recovery it works (CWM Touch) however if I manually go into the bootloader, hold volume keys and select reboot into recover it will just hang at the google screen.
I can get out of that bu holding power until the deivce reboots back to the OS.
I can do this as much as I want, from using adb into bootloader and get into recovery, but not manually. What can i try?
I have already tried flashing stock recovery, and other CWM non touch and all act the same way, what am I missing?
I had the same issue completely stock. No idea what causes it, and I've still not fixed it either.
Good to know I am not alone.
same here! even with 6.0.1.0
Sent from my Nexus 7 using xda premium
I rooted a week ago and this problem drove me nuts. I was paranoid enuff not to wanna flash anything. Within the last few days it was found that you can do the 3 button thing, get into the bootloader and select recovery ONLY if the N7 is plugged into something with a powered usb port. It seems any computer will work, and I read where one guy tried assorted ports like tvs, direct tv box, xbox, etc. These also allowed the buttons to activate bootloader & select recovery. There must be something within the port which requires power in order to get past that Google screen? It doesn't matter whether your on cwm 6.0+ or TWRP. It seems to be a hardware issue as far as I know at this point.
I read where a guy said that during a bootloop, hold power + volume down and wait, sometimes as long as 50 seconds. Eventually it has always worked for him. I've had one bootloop and didn't try that method. I just connected usb cable to the laptop, held the buttons and was in. That is a summary of what I know as of now.
Sent from my Galaxy Nexus using Tapatalk 2
I can confirm that it only works if you have USB plugged in.
Anyone able to get past the red triangle? It seems to just hang there for me
Its a bug with the early CWM Official Port i think, try TWRP Recovery
The only way I was able to get into CWM was to use ROM Toolbox or ROM Manager to boot into recovery. :\ Hangs for me while holding down volume and power.
Guys,
I installed CM10 (official) onto my Nexus 7. The ROM was running perfectly, no problems whatsoever. I then decided to flash the Elite kernel. I made a back up via Clockwordmod before hand, just in case anything went wrong.
I then installed the kernel and now all I get is the CM10 spinning green boot screen. That's it! I've installed Wug's tool, to try try and boot into recovery, but I can't even get the drivers to install to even use the tool... which is massively annoying.
Spent an hour last night searching for a solution and trying to get this thing to boot into recovery.
I've tried the obvious by holding down the volume rockers and then holding power, I get to the screen (I can't remember it's name) where you can toggle through different selections via the volume rockers, I select Recovery but it doesn't work.
Any ideas?
Make sure your Nexus is plugged into your PC, then you'll be able to get into recovery from the bootloader. This is the well known workaround for the problem with the original bootloaders.
Also, upgrade your bootloader to 4.13 as that version fixed the problem of getting into recovery.
Sent from my Nexus 7
Thanks.
Daft question, I'm not 100% on upgrading the boot loader. Can this be done on the device itself? If so, how?
Yes. There's a flashable zip file that you can install using recovery. Search the Development section.
Sent from my HTC Desire S