[Q] Looping Boot Image - EVO 4G Q&A, Help & Troubleshooting

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...

Related

Did I brick my Dinc SLCD??? Help please!

Ok, so I did unrevoked and have an unrooted phone. Started to get bored with the stock 2.2 and wanted better battery life.
My Dinc has an SLCD screen. So, when I go into the standard clockwork recovery, it goes to a black screen with white bars on the side. I had to do a custom flash recovery for my phone through unrevoked/flash. I then did a nand backup.
Tonight, I downloaded MIUI and attempted to install through the recovery flash. I ended up getting errors. So, I then thought that I needed to go through the ROM Manager app.... when I tried to flash the ROM, it automatically switched my recovery back to the Clockworks recovery..... then tried to go into the recovery portion of the ROM flash. Needless to say, I had to do a battery pull. Now when I try to do a normal boot, the phone freezes at the white screen that reads "HTC Incredible". If I boot into recovery... I can get to the hboot screen with the three droids at the bottom, but a script comes up on the screen and I think that it says something about no image... from there I can navigate around the recovery menue, but nothing works for me getting past this. If I go to recovery, it just keeps going to the black screen with the two white bars.
Is there anything that I can do. I am wondering if it is trying to flash the ROM everytime it comes on.... but this recovery method is not working on my phone.
Any help would be greatly appreaciated!
I believe you need a special clockwork recovery for SCLD screens. Not exactly sure where to find it on here, but it should be hanging around somewhere. I hope I helped ya out a bit, good luck.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
OK, so I was working a 24 hour shift yesterday when I posted this... unable to download any zip or exe file (damn firewalls)... This morning I was able to remove the miui zip from the root of the sd card via card reader. I then copied the PPB31IMG.zip to the root of my sd card. Then booted into recovery. I asked if I wanted to flash this file, I said yes and then it gave me the correct recovery menue. from there I was able to choose the recovery image that I had created yesterday. It seemed as though it was going to work, booted up to a stock rom that required manual setup (like on a new phone). Then I started to get FC's all over the place. I was able to find on my sd card two other nandroids that were saved in a different place than the only one that recovery allowed me to choose from. I moved the newly found recovery folders to the same location as the first and now I had those recovery options listed. I chose one from last week and thankfully my phone is restored and working.
I am not sure if this information will help anyone with an SLCD Dinc. There seems to be a huge difference in how these phones react to roms and tweaks. I am very hesitant to attempt any other ROMs at this time. On my eris, I flashed about 30 different ROMs and about 5 differnet radios. I am not new to this, but this SLCD Dinc has been a headache.
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Well I'm glad you got it back up and running. I've heard about them not working well with some roms, I didn't know it was with all asop roms.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
doug piston said:
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Click to expand...
Click to collapse
Thanks for the info on the AOSP roms. I did not know either. I wonder if there is a way to make the AOSP roms to support it by providing the new kernal in the flash or at least making a note on the AOSP ROM forum page that states the issues with SLCD Dinc's and what needs to be done to avoid problems. I would venture to say that anyone new to this stuff and was feeling brave would not be able to figure out how to restore there phone when it was acting the way mine was. Just my 2 cents.
Thanks again for the info.

[Q] Misc. Questions, Flashing to Ginger help

Thanks for taking your time and helping me, I saw you guys(and girls) have done some pretty amazing things here at XDA. I just need some help with getting this Gingerbread ROM to work.
I'm using Supersonic 2.2.1 first off, and using the alter. recovery rom from Rom Manager.
Ok, so I rooted my phone using rEVOked and chose a ROM called Bc-Gingerbread-beta4. I'm not sure of the eact title used, but if anyones faimilar with Gingerbread ROMS, they should know what that is... It was on the EVO ROM page.
So at first, I was using ClockWorkMod Recovery (2.6.*) to try and install the ROM. I eneded up with status 7 ever time, so I tried to upgrade to 3.0.* (newest one) and recieved a error about not being able to flash. No details were given.
I tried flashing to the alternate recovery, and it worked. From their, i (un?)successfully installed the ROM according to the recovery application.
The status bar didn't move past the halfway mark, but i figured it was just how it worked..
Then, I tried to boot into the new ROM. I was on the HTC screen for about 3~5 minutes, then it showed me the android load screen instead of the usual Sprint/4G screen. From their, it was in a constant loop because every 3 to 4 seconds, it would take off the android logo, then place it back. I waited approx. 10 minutes... Nothing. Unfortunetly, the alternate screen doesn't have the option to browse for your nandroid back ups (mine aren't in /android) So i'm left with a relativly bricked phone until I can find a working ROM.
I have a microsd card reader.. so I'm not too terribly screwed, I just need help on what I did wrong, how can I fix it (if im able to), and what Gingerbread ROM I should use. It needs to be relativly stable. I don't care about 4G support, even though its almost everywhere in Atlanta. I'd like to have video rec. if possible. and 8MP support.
If it fits those standards, please, I'd like to hear what the community thinks is a great Ginger ROM.
Also, I'm using Windows. I have the adb shell installed, and im familair with basic-medium level terminal commands.
Edit: I'm going to flash again, using cm_supersonic_18.zip. It says installing update, but it says flash zip from sdcard in the main menu...
Edit #2: apparently it's a Cyanogen mod (#7)
Just keeps looping the android on the skateboard screen... I'm going to figure out how to get back to the clockwork recovery console and -hopefully- get this thing working.

[Q] Please Help! Looping

Ok... here's the deal. I just decided to switch roms finally to see what is new out there. I had been running an old version of Uber Kingdom. Here is the problem I am having. It is boot looping. Relatively simple problem to fix usually. But wait, there's more! It is boot looping in every single rom I install. Sometimes it won't boot to clockwork properly either and I have to pull the battery. Is there someway I can fix this? Or is this a hardware problem (which I kind of doubt)? I just don't understand what the heck is going on. I have been flashing different roms left and right for the past few hours trying to get this thing to stabilize. Sometimes it will boot up into the rom, I will get mostly through the google accounts setup, and then it will restart, and then loop. Other times it won't even get past the white incredible screen, and then sometimes it will make it into the rom splash screen. I have attempted to install CM7 nightly, Uber kingdom, and Synergy so far. I can flash the new rom, I can mount the SD card in clockwork, but then it begins to loop again as soon as I leave clockwork.
Let me know if you need any other information.
Is there a way to just completely redo EVERYTHING, clockwork, rom, everything, just to make sure I have a nice clean slate?
Thanks a ton for reading through this novel. I am extremely frustrated.
~Will
PS, I may not get back to this thread until morning. I have to get to sleep for work. Sorry if I don't respond right away to information requests. Thanks again!
If you can mount the SD card, download the stock RUU from www.dougpiston.com, put it on the root of the SD card named exactly PB31IMG.zip, and boot into hboot to install it. Your phone should be restored to stock, a clean slate.
Tried a different SD?
Sent from my ADR6300 using XDA Premium App
How are you downloading and flashing the ROM? I had this problem when trying to do everything through Rom Manager. Even trying to flash in recovery with a ROM downloaded through ROM Manager would loop.
Update
Well, I was just getting ready to flash the original RUU when I tried one last time to restore my old Uber rom setup and it worked (whereas the last 3 times of doing exactly the same process didn't). It stopped looping at least, even though I am still running the same rom I was before. I think tonight I am still going to attempt to flash the RUU anyway and start over anew.
To answer the questions before, No, I did not try a different SD. I didn't know it could make that much difference. Still on the original one that came with the phone.
As the downloading and flashing process goes, I was downloading direct from the XDA forums on my laptop, then transferring the files via USB. I have never really liked using the Rom Manager. It cuts me out of the XDA loop and I don't get to see all the bleeding edge discussions, etc...
So I will try to flash everything new tonight, and then post my results for anyone who is curious. Thanks for the help guys!

Revolutionary on new wildfire problem (or extreme muppetry)

Hello everyone.
I enjoyed the noob video and also look forward to being pasted no doubt.
I have a wildfire running 2.2 android which I understand means I am running the latest firmware, which I also understand is going to make it difficult for me to root easily.
Never the less not being one to be beaten I have tried with EVO3, which no matter what I tried would not work, constantly asking if my firmware was too new. I even wiped it but no luck.
So I struck upon revolutionary, which yes I understand is beta.
This is perhaps where my lack of understanding comes in. Would I be right in thinking that custom roms require a specificly rooted device?
The thing is I have apparently been successfull with revolutionary. I can boot into it and I was able to instaly cryongena rom which worked OK until I installed google apps where by it constantaly showed the spinning blue arrow, round and round, rebooting and rebooting.
Thing is all other roms I have tried, everyone, has failed, with either script being old 'error 6' etc etc.
I found I needed a different kind of rom, which a few were offering however these also failed with error 6 which apparent was something to do with not being pure unix or something.
Sorry I am not up on the language, but I think I have tried all the popular ones, puzzle etc and none will install.
When I start up with the volume button pressed it shows the screen then says something about failing to load image, but goes away to quick to read pc4diag.img or something.
Is it possible I have not loaded revolutionary correctly, and have I gained 'root'
Thanks for reading, and please feel free to tear me a new one.
- Yes, I am sure you have Revolutionary installed correctly. You got a bootloop while installing GApps, in which case I would recommend performing a full wipe in Clockworkmod and try to install again. (Install the CM ROM first, then the GAPps Zip. Also, I hope you are using a filename called gapps-gb-2011xxxx.zip)
- If you want to install other ROMs, Sense and Android 2.2.1 ROMs require Clockworkmod 2.x. Attempting to flash them in Clockworkmod 3.x/4.x will give you the "Scripting not supported" error. The workaround to this is to download this attachment:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
Flash this in your new Clockworkmod Version, which will give you temporary 2.5, then proceed as normal.
- When you boot into the HBoot Mode, it will automatically perform a search for the files PC49IMG.diag and .nbh. It's normal, and theres nothing to worry about. After the search is over, and, it has not found the files, you can navigate properly again.
Oh, and I think you are being too paranoid about the video and everyone here trying to tear you a new one.
Good Luck
Thanks very much for your answer.
Honestly I spent 2 hours on google last night trying to get my head around it.
To be honest all I want is a quick phone, and I am not getting that with stock software on my wildfire, I get very frustrated when trying to scroll but it reads it as me tapping an app icon, and there are loads of them I don't want in here, footsteps and tweets and the likes, I am simply not interested and neither am I allowed to remove them. The cynogenmod looked amazing, but I can see even more processor intensive than the stock software.
I will have a look at what you have suggested and thanks for your help!
In that case, I think you might want to stick with the Stock ROM, and, get an app like 'Root Uninstaller' or 'Titanium Backup' which allows you to uninstall (Or, to be more correct - 'freeze') any apps you wish - Including System Apps.
Not trying to advertise Cyanogenmod here, since I understand ROM preference is a personal thing, but, I would recommend giving it one more try, after a full wipe. Also, go with the latest nightlies rather than the Stables. I have been using it since it was released back in January, and, honestly, I am never going back to Stock / Sense based ROMs.
Don't get me wrong it looks awesome. But the boot up time was just shy of 4 minutes (although I now understand it may have been because of first boot) and two attempts at install failed.
I shall look at how to fully wipe, but to be honest, being very new to hacking my phone I am quite happy having the back up there to revert too.
Well I tried to install anything but nothing works so I shall revert to my original back up and see about these tools for removing unwanted apps.
Thanks for the help, but something is not right. All roms either get as far as the twinkly noise on the HTC screen then do it again and again, and cynogen gets to the rotating arrow, then eventually an android zips across the screen and back to the arrow
Well I don't think I have root on this device. I tried to install busybox and titanium and both tell me my phone is not rooted.
Sigh.
If you are on the Stock ROM, you will have to flash this additionally:
http://bit.ly/su2361ef
This will install Superuser, which is what will give you "root". If you are on Custom ROMs, flashing this additional file is not required, since, they include the Superuser Binary already,. So, flash that, and then try installing Busybox / Ti Backup. (make sure you get a "superuser" icon in your app drawer after flashing that zip)
EDIT:
- Are you on Clockworkmod 3.0.0.6 incidentally? That version has caused bootloops for many users when installing ROM's.
- First boot time is extremely long (Upto 7-8 mins), and its normal.
Hello thanks for the info.
I am not confident I know what mod I am on, I just went to the revolutionary website and downloaded the latest beta.
When you say it can take 7-8mins to load up would this include the boot loops though? Thats all I get on all of them
I shall install the super user bit see if that helps.
No, not including bootloops. BTW, I am referring to the Clockworkmod Version, not Revolutionary,
When you enter the Recovery to flash something, at the bottom, you will "Clockworkmod Version x.x.x.x". It is that version I was asking.
Sadly I am not getting anywhere here, every single rom just goes round in circles in one way or another.
The version say revolutionary CWM v4.0.1.4
I was unable to get the standard revoked installed as I am runnning the latest android firmware and it just kept failing.
Something I am getting rather used to!
I cannot see a clockwork mod number anywhere, although it must be there as I have clockwork folder on the SD card.
Sorry, I am being a muppet here.

[Q] I stuffed up. What do I do?

Hi, first time posting here.
I have a bit of a unique problem or so I've heard. So I was an idiot and decided to flash a Virtuous ROM over the WiFi via ROM Manager on my Desire Z. Previous to this it was rooted and was running CM 7.1 RC1 and was all fine. When I flashed the Virtuous Sense Rom (Not unity, the one before it in ROM Manager), it flashed, what I thought was fine. However, when I actually got into the phone, it said everything was crashing and would go into a boot cycle. Then for some stupid reason I just reflashed the 1.3.4 or whatever ROM back onto (The one you're meant to downgrade to). At this moment in time, I can't do anything. When I'm in the bootloader of the phone itself, I can't scroll up or down to the recovery option, so I can't flash through that. I've tried re-rooting the phone (Or that process), hoping that it would work. At this point in time, it keeps popping up errors at /data/local/tmp/psneuter
Note: I was following the CM7 rooting guide thing.
Anyway, I hope someone'll be able to help me out of this stupid stupid thing that I've done.
THanks!
EDIT: Okay, well, going through the CM7 rooting guide a fourth time seems to have fixed it. It's all fine now. On another note, how do you change the Virtuous Unity lock screen to something else? I'm not really a fan of the Sense 3.0 lockscreen.
You should not need to re-root after flashing any custom ROMs.
Also, I would not do any more ROM flashing if clockworkmod is not properly installed, or you don't know how to use it.
Did you bother to wipe data and cache? You didn't mention it. If you didn't that's your problem
Sent from my HTC Vision using XDA Premium App

Categories

Resources