Flashing a 1.5 Rom after doing official 2.1 RUU - Hero CDMA Q&A, Help & Troubleshooting

I was messing around last night and came across an overclocking kernel I had been playing around with for Gumbo 1.5c and was bored so I proceeded to flash it and play around for @!#$s and giggles. To my surprise to mater what 1.5 Rom I tried I got boot loops. I thought it was the baseband I was using so I flashed back to stock 1.5 radio. still no go. Reflashed recover, 1.6.2, rewiped, reformated sdcard, etc.
Has anyone else experienced this, and if so is there a solution?
PS: Will post a logcat tonight.

bump
10chars

Related

Boot Loop?

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.

Problem with Milestone, constant bootloop

I have flashed many diferent firmwares on my phone. Lately I have been primarily using TelusLiteV4. Yesterday I tried a new rom and decided I did not care for it. So for about the 30th time I reflashed TelusLite back on through G.O.T. open recovery. Well, now I get constant bootloop. I have tried to do a couple other firmwares, bootloop. I tried a new sdcard, bootloop. I have my sdcard partitioned for Ext3/Fat32/linux swap. Everything is a constant bootloop. The only case where I do not get that issue is if I use RSDlite to flash GOT 2.2.1. However I dont care for 2.2.1. Just want TelusLiteV4. Any suggestions from anyone would be awesome. Thank you
I would try a SBF image with stock 2.1, you can find the procedure in the development section and if it works then install telus lite
Sent from my Milestone using Tapatalk
Hi. Thank you for the reply. I figured it out shortly after posting my situation. I reflashed with G.O.T. Telus SBF, then did the normal stuff to install TelusLiteV4. Everythings a-ok. Thank you.

[Q] Boot Loop when installing ROM

Hey guys; i'll try to provide you with all the information but honestly i'm not 100% on all of it so try and be patient.
I'm trying to go back to SuperE from Froyo by Laszlo which was absolutely killing my battery without me even using it. However, every time i flash it (and i wipe everything) after it goes past the G1 screen it just resets again.
I'm not sure if this is maybe because of the new kernel (2708) which i'm PRETTY sure i have, but am not 100%. I do know that i have one of the new radios though.
Would the kernel be causing the problem? If so how do i downgrade?
I hope you can help me out!
Thank you!
Q: Can you mention step-by-step what did you flash? And confirm the exact setup before flashing. I believe you mentioned your radio is 2708.
Powered by Android
Thank you for replying. I'll definitely try.
I'm back on FroyoByLaszlo-int2.1 because i couldn't successfully flash either Super D or Super E.
My Radio is 2.22.28.25
Kernel version says 2.6.35.10 - froyobylaszlo
Basically i did what i always do. I wiped everything, first by flashing the "all-wipe" and then going back and wiping it all manually.
Then i flashed the appropriate gapps, followed by the ROM. Rebooted afterwards, but every time it gets passed the G1 screen it reboots.
The only thing i can think of is incompatibility with the kernel but then again, i don't know crap, so that's why i'm asking
Yep, most likely it is indeed the incompatibility of the kernel with the radio.
I'd try flashing the ezBiffTestKernel20101106-2708.zip after the ROM+GApps.
Just use Google to find the kernel.
Powered by Android
The battery drain could be becos of the new kernel. Try installing the 35.9 kernel from ezterry (the one he had for CyanogenMod 6.1 2708) It is working good for me, the battery last for a whole day.

Help installing CM7

Hello,
I am trying to install CM7, the stable (bbq) version, on my gfs n1. I downloaded the zip, did a nandroid backup just in case, applied zip and rebooted. It opened to the CM7 load screen and i thought everything was working. Waited on that blasted screen for 45 mins and nothing happened. Did a battery pull and restored from the backup and everything is working how it used to. I am trying to figure out why the CM7 install didnt work.
I think it is because of the radio. She is coming from 2.1, an old CM rom. I am not sure which one. I didnt update any radio before i flashed the rom. I didnt know which radio to flash. The newest radio is a Korean radio. Should i flash that before i do CM7 flash. Any advice would be great. Thank you.
yes, you should have the newest radio, korean radio is ok for usa use.
alright, ill flash radio, then flash rom, then reboot. Ill let you know if i blow anything up. Thank you =)
Did you wipe everything?
i would do a full wipe ...yes
Did you flash gapps file also?
Full wipe should include system partition also.
FYI radio 5.08 is what come with 2.3.x ota. Radio 5.12 should work no problems.

[Q] New Root

Hey guys i just used the RUU and then re-rooted. My question is what setup do you guys suggest. Im not just talking about which rom i should use this time (i was previously using cm 7.0.3). I mean what ROM, KERNEL, MODS, SCRPITS, PATCHES, ETC. I want my phone to be as fast as possible because i am tired of the hero's lag. I love my phone but frankly i have got to speed it up since im still like 4 months from getting a new phone (Hopefully a Nexus 3!!)
Do you install a lot of apps?
Only about 35-45
Firerats if you can get it to work, no idea what you did wrong but we all know it works.
®patience is a virtue©
I fixed it by not following the directions lol. I used mtdpartmap at 120 15 and then i did all the wiping, flashed the fr recovery, rewiped, DID NOT REBOOT RECOEVERY, flashed gingerbread deck, flashed gapps, flashed sobe kernel, flashed fr boot, rebooted and it suprisingly worked. Now im going to flash the ram optimization script.

Categories

Resources