I was trying to install cyanogenmod 6.1 on my G2 but when I reboot it gets stuck at the HTC screen and doesn't load past it. I've rebooted about 20 times and can't get it to work. In Clockwork recovery i installed a stock rom, formatted the data, system, and caches but it still gets stuck at the HTC Screen. Is there any way to fix this?
do you have a back up? if so restore your back up
is there a reason you needed to post the same thing a dozen different places? you posted your issues in the CM thread, good you decided not to start a new thread and asked in there. then you made this thread in Q&A and another in General, in general you stated you fixed the problem but you have not posted anywhere what you did to fix it. please do not double post, and please share solutions when you find them.
Related
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Have you use amo-ra?
Sent from my evil evo!!
rsjc741 said:
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Click to expand...
Click to collapse
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
klquicksall said:
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
Click to expand...
Click to collapse
Thanks
I should face-palm myself. I just read the sticked post and I'm going to try some of his suggestions. He pointed out why cyanogenmod wouldn't work.
My whole consept of the framework went out of the window, and now I think of it more like a standard linux distro, in terms of kernel->ROM relationship.
I don't think I need to have a custom kernel for the Gingerbread beta-4, but i'll look it up just in case... Though I don't have a clear idea on how to flash that.
And to the person 2 above, im using Cyanclockwork. For whatever reason, I like its design verse RA recovery. I might try RA recovery just to see if it works better, as everyone has said it does.
I think i needed to clear all my caches and then load the ROM.
So I did a wipe of everything (data, darvik, cache) and trying to install the GB ROM. My boot screen is *still* looping. Do I need to get another kernel? Is it like flashing a ROM? Where are they at? I didn't see any in the software section...
Hi there XDA Developers
I have a problem with my HTC Desire, that it gets stuck on the white screen with green HTC logo.
I have been using Neophytes AuraxTSense 8.1.3 for a long time, due to this problem. I wanted to test the new "true" Gingerbread ROMs, so i flashed a new ROM and the recommended radio.
I wipe everything - Data, cache, dalvik and battery.
When i reboot it get stuck on the logo screen as before mentioned.
I made a new partition on my SD card, because i read somewhere that it might be the problem that i was having. It formatted my SD card. So i don't have my recovery's anymore.. i thought they were saved on the phone itself :/
The ROM i have recently flashed/is flashed now is Leedroid 3.3.5
I hope you can help me..
If you need further information, ask me to elaborate
Thanks
Hi there begginer ... you won't get any answer cuz you got the wrong section ... ask in Q/A
We've a Q&A section why you went posting here ? By the way use the SEARCH TOOL there're 1xxx posts with the solution to your problem.
Sorry for this hard answer but i like this forum. Alot! And i want to keep it clean.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to Q&A
1st WARNING
So, now that it has been moved to the Q&A,
can someone help me?
I have been using the search, but i did not seem to find anything that could solve my problem.
Hold down and power, wait a moment then choose 'recovery', does this take you into your recovery? If not, find the right ruu for your desire and flash back to stock. Unless you are s off, and have sdk installed that's your only option I think.
Yeah, it does take me to recovery.
But, wipes doesnt work.
Nor does Clear Storage
Did u restore ur system in recovery?
Ur phone seems to turn into semibrick.
There are some ways to fix it,use google.
There are no recoverey, due to the format on the SD card.
I made a log, and mounted the USB storage from recovery
http://www.myupload.dk/showfile/9753233c52a.log
BUMP
I'd really like my phone to work
FredMaHead said:
BUMP
I'd really like my phone to work
Click to expand...
Click to collapse
^This
Please help guys
Bump guys..
Anyone who can help ?
Bumping yet again
hey mate.. i had the same problem with my desire also. but i solved it: here is the solution:
http://forum.xda-developers.com/showpost.php?p=12399238&postcount=10
hey mate.. i had the same problem with my desire also. but i solved it: here is the solution:
http://forum.xda-developers.com/showpost.php?p=12399238&postcount=10
I can't.
That guide needs the phone to be fully booted :/
EDIT: Reason
... No one !?
I would like a working phone soon
You have a few choices:
1 - Restore your phone from a Nandroid backup using the recovery console.
2 - Restore your phone from a Nandroid backup using Fastboot (if recovery doesn't work)
3 - Download and Transfer a new ROM image to your phone through recovery mode / by putting your SD card into your computer. Re-flash the new ROM and see if you get any further.
The issues you are describing are all too common, which is why you have received very little help. Do some searching with google and sort as much of it out for yourself, you'll learn much more that way.
So I decided to try out a sense rom. Flashed Synergy, tried it for an hour, didn't like it. I then went into recovery (TWRP), wiped, started my nandroid restore. When booting back up after that, it just hangs on the white EVO 4G screen. I left it sit for 20 min at that screen, no change.
WTF do I do now?
These issues have been well documented on xda. I suggest skimming through all of them and seeing which solution works best for you... Or hopefully by now you have already fixed the problem... either way good luck..
Edit: One suggestion try changing recoveries and reloading rom
Uh...thanks for the help??
I ended up flashing recovery back to AmonRA and starting over from scratch with the latest CM7 nightly.
Oh, btw, I did search before posting, but nothing I found was close to what I was experiencing.
Usually if u restore a recovery n it acts up just flash the rom over top of it
Sent From My Pocket
So I've done some searching, and have yet to find a solution to the issue I'm having. GF's phone is the HTC Incredible as you can probably already guess by what subforum this is posted in. It's been running the CyanogenMod 7.1.0 Rom for quite some time alright. From everything I've seen, most people that have had issues with bootloops is because they have been flashing to a new rom/radio and skipped something/pulled the battery/or something along those lines. This phone has been running fine, and then out of nowhere I guess, started to restart itself continuously yesterday. I can get into HBOOT no problem, but that's about it. When I try to select Recovery, it just kicks right back into the bootloop. Anyone have any suggestions??? Phone isn't under warranty anymore, and her contract ends in a month and a half, so we don't want to have to buy a new phone before then if at all possible.
try reflashing recovery.
first start with a freshly formatted FAT32 sd card, download this file and place it on it
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
this should be the only file on your SD card. now turn off your phone and put the sd card in. now boot into hboot (vol down+power) and it should prompt you to update by pressing vol up. do this and when it boots back into hboot, remove the sd card and delete the file. then try booting into recovery
Tried it and still no change
there was a similar situation (stangely similar ) here
http://forum.xda-developers.com/showthread.php?t=1628585
both cases happened to be running cm 7 too...and randomly started boot looping and stuck with no recovery.
i would read through that thread and see if any of the steps will help you
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
downwardzspiral said:
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
Click to expand...
Click to collapse
you can try doing the steps in that thread. you may have better luck. Perhaps someone else on this board knows of another method that may help
Just because it didnt work for that guy, dosent mean it wont work for you. Are you s-off? Have you tried reflashing recovery yet?
it's S-Off and I've tried to reflash recovery
How about an ruu?
tried that. tried through the pc and the computer wouldn't recognize it. tried by updating it in HBOOT, and after the update, it would still just bootloop
Sounds like another possible hardware failure. My only other sugestion would be to try the fastboot flash of the misc img, but it probably wont work either. Its very strange, i have seen this 4 or 5 times now in the past couple months, all on cm7, and all unfixable. I dont want to start a war, but mabey something with cm7 or cm7 and a certain program or combination of programs, is causing this. Or mabey its just cause these phones are getting up there in age.
i too find it odd each one is cm7..
Well thanks for all the help anyways. A new phone it is I guess
the basic problem is CM 7 (for the Dinc). it is extremely common. i have seen it happen to so many people now. it drives me insane when i see people suggesting CM 7 "stable" to others (for the Dinc). i have tried to communicate this here and other places too... i have given up hope of people ever accepting this obvious situation. the "stable" version of CM 7 is simply not stable.
however...
a reflash of clockwork recovery has always gotten people out of the CM 7 bootloop. then they are able to get a working rom installed.
i don't understand why you can't get a recovery re-flashed.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
hi
ive done a search and read the thread in the developer section, but it wont allow me to post on that as i havent contributed enough posts yet.
im trying to fix my wifes phone, and have asked on the androidforums about this and been pointed here. basically, theres a glitch on some One Xs where the picture is green when the flash is used. this is the thread ive been reading
HTML:
http://forum.xda-developers.com/showthread.php?t=2082782&page=5
for several hours last night i muddled my way through unlocking the bootloader and then rooting the phone, and installed viper rom and rebooted fine. i then installed the 'green tint fix' zip from sd card in recovery. once id done that tho, it prompts for reboot, but gets hung up with a system fault and wont finish booting. i then have to do a clean wipe and restore my backup (so no green tint fix is ever capable of being tried out)
could anyone help me get round this please?
thanks a lot
ive just found out my mate has an HTC One X too, but no camera problem. is there anything i can check or 'copy and paste' into my wifes phone from my mates? im thinking overwriting a file or something?
thanks