Right, I have been on froyo for about a week and have been missing certain cyan features so decided to flash back. Flashed the old radio through fastboot and then flashed the new test5. Phone shows the first nexus logo and thats it. I know it sometimes takes longer with first boot, but it has been sitting there for half hour.
Thought I might try flashing froyo again?
Any suggestions.?
Wipe and re-flash
Have tried that already, but doing it again now. Got some weird write error when trying to flash Pauls froyo again. :/ Went with test 5 again.
Edit: How long does it take on first boot. Mine is still sitting there.
Have tried a nandroid restore as i couldn't think of anything else. And it seems to work, getting past first screen as i type.
If is cyanogen 5.0.8, then I believe it needs froyo radio
Rellikzephyr
-------------------------------------
Sent via the XDA Tapatalk App
That would be the solution, cheers matee.
Related
I was rooted running on damagecontroll 2.08.1 for the longest time with no problems, then i moved onto the evo 4g and without service on my hero everything went wrong. sense wouldnt boot and would keep force closing. i eventually was able to get into the phone loading up vanilla home. i attempted to restore a nand backup, but none could be found somehow. i created one and replaced the files created with the old one and it found but still stuck in bootloop. i also tried to flash flipz rom, but still stuck in bootloop. is there anything i can do to get this thing to be able to be ready to reactivate? i am really lost here, tried all i could think of.
nvm i was able to HBoot with a stock rom, still 1.5, so i can still root correct?
Can someone help me clear up some issues with cm7 on my hero.
Sent from my HTC Hero CDMA using XDA App
For example. Battery bar. Force close on some apps
Sent from my HTC Hero CDMA using XDA App
This is too vague to even know where to begin. What about the battery bar? What apps force close? What recovery are you running? Have you read the GB wiki or search through the thread?
Ok. I am with cell south and when I got cm7 it says sprint. My battery bar is not right. It says I have more battery than I have. Beautiful. Widgets. Force close when trying to get new skins
Sent from my HTC Hero CDMA using XDA App
And 2.5.0.7 on recovery from rom mgr
Sent from my HTC Hero CDMA using XDA App
stuck on boot loop with CM7 - HTC Hero CDMA
I need help getting passed the boot loop (cyanogenMod7 screen with the android guy on a skateboard). I've tried the following:
1st time flashing AOSP CM7 (got it from this page: romrepo.info/wiki/index.php?title=Main_Page) I just flashed it over my CM6 which was working fine.
2nd time I followed instructions that we're supposed to follow if we run into boot loop problem (also from romrepo.info/wiki/index.php?title=Main_Page), which is to flash the kernal mentioned on that page
3rd time I wiped everything, and tried re-flash the AOSP CM7 rom.
everytime I get stuck at the cynogenmod7 screen, and it just keeps looping.
any ideas?? (Yes, I'm new here, but I've successfully flashed many other ROM's and know what I'm doing. Just can't figure out how to get passed this boot loop!)
sixstrum said:
I need help getting passed the boot loop (cyanogenMod7 screen with the android guy on a skateboard). I've tried the following:
1st time flashing AOSP CM7 (got it from this page: romrepo.info/wiki/index.php?title=Main_Page) I just flashed it over my CM6 which was working fine.
2nd time I followed instructions that we're supposed to follow if we run into boot loop problem (also from romrepo.info/wiki/index.php?title=Main_Page), which is to flash the kernal mentioned on that page
3rd time I wiped everything, and tried re-flash the AOSP CM7 rom.
everytime I get stuck at the cynogenmod7 screen, and it just keeps looping.
any ideas?? (Yes, I'm new here, but I've successfully flashed many other ROM's and know what I'm doing. Just can't figure out how to get passed this boot loop!)
Click to expand...
Click to collapse
try clockwork 3.0.0.5, wipe both options in recovery main menu, then format everything but sd in mounts and storage menu, flash rom, then gapps, reboot, if that doesn't work try one of the kernels linked on the wiki, if that doesnt work, go to the live help irc chat linked in the OP for aospCmod.
that worked. My fault, i missed the wipes in the "mount" section. figured it out a few days later. This CM7 is my fav ROM so far!
oh, and thx for the reply il Duce!
First time posting so i need some guidance. @When running cm61.1 stable my phoned paireed with my car bluetooth and I was able to dial by name, "Call Joe Cell", after flashing with CM7 RC4 the phone will still pair but then if I try to make a bluetooth call by name, it will act like it is calling (active call on bluetooth display)and then it stops. Funny thing is if I say call and then speak the nmber instead of the name it will complete the call through the bluetooth in my car. This struck me as strange. any help would be appreciated
I seem to be having the same problem. I wiped both options in the recovery main menu, formatted everything in the mounts and storage menu except for sd card, installed cm7, installed gapps, and rebooted.
Still stuck on the boot screen (android guy on skateboard with spinning arrow). Any ideas what could be causing this?
(HTC Hero CDMA)
Never mind, just got it to work!
Thanks, il Duce, your tip worked great!
I recently received a Nexus One from a friend. The bootloader is unlocked and I believe it is rooted. When I got it it kept generating some sort of process error and the phone randomly rebooted. I tried reinstalling a ROM and then the phone just sat with the "X" boot screen. 3 days later and I managed to find a ROM that makes the phone usable (22607-ERD79-update-nexusone-stock-signed). The phone ran fine with that but it is now 2 generations old and I want to update to Gingerbread. Every attempt I have made has ended with the phone just sitting there with the "X" screen after 20 mins. Clearly the updates aren't working. I'm completely confused by all of this.
I'm coming from an iPhone that I was able to jailbreak and hack with no problems. I also have experience with WinMo phones. Never had these issues.
Most of the updates seemed to install correctly. The log screen completes all the steps and ends with "Install from sdcard complete."
Running RA-nexus-v1.5.3
Please help me with this. I want Gingerbread!
First, what versions of Radio and HBoot you use?
How would I tell? Where would I find this info?
Sounds like you are not wiping data.
Whenever you change to a different rom (other than upgrading the same rom) you need to wipe the data partition, otherwise you could get bootloops, stuck at X, unstable systems, etc.
Sometimes not wiping works out okay, but in this case it sounds like it didn't.
I have tried the wiping. As I understand it, I should wipe before flashing the new ROM?
THe baseband is 32.41.00.32U_5.08.00.04
Found them!
HBOOT = 0.35.0017
radio = 5.08.00.04
so I've now upgrade to recovery-RA-supersonic-v2.3.img
supersonic is the wrong phone.....
OK. What is the correct one?
So apparently I was provided the wrong recovery. I did a little research and believe I have the correct one now. recovery-RA-passion-v2.2.1.img
Now should it work...
Still not working. I have no idea what I'm doing wrong. This is really getting under my skin.
Can anyone offer any more info on this? Maybe walk me through it. I have to believe that I am doing something wrong as the phone seems to work otherwise.
Return to a completely stock image. Follow the unroot/restore method from the wiki, using passimg and the FRG33 image...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
OP I had a similar issue. Wiped, installed, wiped, installed. No ROM was stable. It constantly rebooted.
Luckily it was under warranty and HTC replaced it. The new device is rock solid but has burn-in (Pandora buttons always visible and I don't even have Pandora installed).
They are replacing this one as well.
Hope it's under warranty. If so, HTC is great, even with an unlocked bootloader.
Sprint Hero
8gb new SD card
Was rooted to a cyanogen mod 6 (???)
The other day my sd card needed to be replaced. This card had my backup info on it, but became corrupted. I tried using various utilities in Win7 to try to fix the card, but had no success. Somewhere during the process of everything, I must have erased/corrupted the info on the phone itself, as it will no longer boot.It just freezes at the HTC screen.
I am trying to flash a new rom to the phone via the sd card using the hboot method. I have tried various roms, and had one actually start to install itself, but at the end it said the system info is older (not sure of the exact words) and would not proceed. So now I am stuck in what to do.
I want to get my phone working. I don't care if it is the basic stock OS, or something better at this point, as I can mod it once get it up and running. I am able to get to the clockword recovery prompts (if this helps any).
Any help in resolving my problem would be appreciated! Specific steps would even be better
I can't stand being without a phone... and this is driving me crazy!
U still have a recovery on ur phone?
Sent from my HTC Hero CDMA using XDA App
i have clockwork, if that is what you are referring to???
Run the RUU from bootloader and restore to factory. Re-root and you'll be good to go.
If you still have Clockwork recovery you can flash a new ROM from there and the problem should be fixed as well.
Is this a new ROM you are working on?
Thank you.. I think I have it working again.. I downloaded a rom from this link... http://forum.xda-developers.com/showthread.php?t=581521 and it booted back up....
so, if I want to go to a different rom, say CM 7, or even a different one all together... I can do it from here using rom manager, right ??????? Thanks for your help!!!!!
Did you make sure you were fully charged. My phone sometimes refuses to get past the white HTC screen. If I make sure it's charged and sometimes I pull the battery and just let it sit. I always boots. It never did this on any rom previous to gingerbread. I would do this before spending an hour or two rru'ing or reflashing. My phone didn't seem to like the cwr 3.0.0.5 either, lots of booting issues. I had to downgrade back to 2.5.whatever. Looks like you got it fixed though.
Sent from my HTC Hero CDMA using XDA App
Moved to Q&A...
how can i fix this and its frustrating phone was working fine and when i update it does nothing but reboot...when i am in safestrap, the "install" tab is not lit to be able to select, so i can not even install a different rom on there....is there a way to fix this
If you are stuck in a bootloop, probably going to have to flash the .246 fxz to get you to stock OTA untouched and then roll from there. I went through this back in ancient days of yore with the DroidX and Froyo, had to fxz(sbf) the phone.
scottyd035ntknow said:
If you are stuck in a bootloop, probably going to have to flash the .246 fxz to get you to stock OTA untouched and then roll from there. I went through this back in ancient days of yore with the DroidX and Froyo, had to fxz(sbf) the phone.
Click to expand...
Click to collapse
It would boot up to the normally then a minute later it will automatically reboot I had flashed .246fxz and still the same issue...I did noticed that the baseband build was "unknown"......so makes me think that something was not flashed or updated right...the reception bar has a red circle with a line thru the center....so I hope somebody understands this and can help me out...
vk4559 said:
It would boot up to the normally then a minute later it will automatically reboot I had flashed .246fxz and still the same issue...I did noticed that the baseband build was "unknown"......so makes me think that something was not flashed or updated right...the reception bar has a red circle with a line thru the center....so I hope somebody understands this and can help me out...
Click to expand...
Click to collapse
Redownload the file from another source and flash it. You also might want to boot into the stock recovery and do a complete factory reset if you haven't already. I also have had to do this on previous phones I've owned when updating.