I am unable to flash any roms except cm6 ( I can also flash any nightlies. )
This is driving me crazy. I have tried to flash fresh 3.2 to no avail. I have also tried to install the new virus rom. I attempted to install the rooted version off the newest ota with the same results.
After each attempt the result is the same. It will just hang on the HTC evo 4g screen.
I have downloaded the roms a few times each to ensure they were completed correctly.
I have pulled the battery and waited.
I have deleted all data / dalvik / Cache several times in a row.
I have attempted to flash using a different version (earlier) of clockwork with the same results.
I even attempted to flash with RA recovery. Same results.
I am completely lost as to why I can only flash cm6 roms
Please let me know any suggestions.
Sent from my PC36100 using XDA App
From what I have read...................
You need to restore a 2.1 or a 2.2 rom you have, boot to that, then you can flash to a 2.2 rom.
You can't go from CM directly to another rom.
I am on 2.2
Sent from my PC36100 using XDA App
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Bielinsk said:
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Click to expand...
Click to collapse
Ok, so basically I am going to unroot - reroot?
I just flashed from cm6 straight to baked snack directly with no problems. Not really helpful but you shouldnt need to flash to a stock rooted rom first. Note sometimes you have to wait a good 5 minutes for the htc screen to go away. Probably took about 5 when I moved from cm6 to snack.
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Defpdp said:
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Click to expand...
Click to collapse
I unrooted- rerooted with the same results, I cannot flash ANY roms other than Cm6 it seems, this is very frustrating..
Anyone else have any ideas at all??
Thanks!
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
crimeslunk said:
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
Click to expand...
Click to collapse
Nothing worked, tried going to different recoveries/versions. Nothing.
Anybody? Any advice?
if you flashed cm6 and have it working... its my understandung that you cqn not just go and flash a different rom. there is a process that needs to be followed.
but i have never and never will use cm6 so i could easily be talking from my rear.
Sent from my PC36100 using XDA App
I flash from cm6 to rooted stock rom when I need to update prl and stuff.
After you flash wipe dalvik and cache again I had that problem when flashing snap.
Im not sure if these don't help. Maybe you can send a tweet to cyanogen himself to get it resolved. If fix pst your findings
Sent from my PC36100 using XDA App
Re root and see what happens
Sent from my PC36100 using XDA App
Also check your kernel, you shouldnt have to flash anything but the rom you want when switching from cm6
Related
so im stuck on gingerbread, and can only use my backup with is a gingerbread one, when i reload cwm 2.5.x through fastboot its doesnt work just loas the rom and never boots past the htc screen. being stuck on gingerbread aint the worst but i always like to move around. any ideas?
try flashing the recovery from rom manager, this will install the 2.5 recovery. fastboot flash will only work if you have the eng h-boot, radio s-off won't do.
yeah got the eng h-boot
and im geting into 2.5, and it says it loads but no dice.
doing the install through rom manager just force closes on gingerbread for me.
fetusbeats said:
yeah got the eng h-boot
and im geting into 2.5, and it says it loads but no dice.
doing the install through rom manager just force closes on gingerbread for me.
Click to expand...
Click to collapse
You can't flash back to CM6 via the ROM Manager. You need to flash CWR v2 via the ROM manager, boot into recovery and manually flash your CM6 backup. And be sure to do a full wipe of everything before flashing
Sent from my T-Mobile G2 using XDA App
OriginalGabriel said:
You can't flash back to CM6 via the ROM Manager. You need to flash CWR v2 via the ROM manager, boot into recovery and manually flash your CM6 backup. And be sure to do a full wipe of everything before flashing
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yeah, im flashing from recovery. i dont have a 2.2 backup just gingerbread. im not installing from rom manager. yeah so im trying to install a rom as i dont have a backup. i boot into CWM 2.x and it says all is loaded but sticks on htc screen. ive wiped everything a few times. even tried wiping in cwm 3 and then fastboot flashing 2.5 and trying to install rom there. no dice.
fetusbeats said:
Yeah, im flashing from recovery. i dont have a 2.2 backup just gingerbread. im not installing from rom manager. yeah so im trying to install a rom as i dont have a backup. i boot into CWM 2.x and it says all is loaded but sticks on htc screen. ive wiped everything a few times. even tried wiping in cwm 3 and then fastboot flashing 2.5 and trying to install rom there. no dice.
Click to expand...
Click to collapse
To clarify, you're trying to flash CM6 back and you currently have CM7?
Sent from my T-Mobile G2 using XDA App
well im actually using the gingervillian 1.4, but previously was using cm6. and alas i ****ed up and didnt do backup previously.
I had cm7 but went back to cm6.1.0 on my g1 but returning it to stock Android 1.0 and then rooting from the beginning, the phone is a little faster now after formatting the sdcard
Sent from my HTC Wildfire using XDA App
fetusbeats said:
well im actually using the gingervillian 1.4, but previously was using cm6. and alas i ****ed up and didnt do backup previously.
Click to expand...
Click to collapse
I'm not sure what you're asking then ... what are you trying to flash?
Sent from my T-Mobile G2 using XDA App
OP are you gfree? U might b able to just unroot / flash the OTW/pcimg10
Sent from my HTC Vision using XDA App
yeah didnt use gfree, got my s-ff the hard way on day one. but i have flashed the pc10img after hex editing before so i think i might try once i mull the problem some more.
fetusbeats said:
yeah didnt use gfree, got my s-ff the hard way on day one. but i have flashed the pc10img after hex editing before so i think i might try once i mull the problem some more.
Click to expand...
Click to collapse
You should still go the gfree route, they found the initial hack could be overrided; check the Wiki here for a guide to use gfree for those of us that rooted from the get go.
Sent from my T-Mobile G2 using XDA App
fetusbeats said:
well im actually using the gingervillian 1.4, but previously was using cm6. and alas i ****ed up and didnt do backup previously.
Click to expand...
Click to collapse
Okay, I think I got it. You flashed Gingervillan without backing up your stock ROM?
Here are links to the pre and post OTA stock ROMs: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#ROMs
Sent from my T-Mobile G2 using XDA App
If you want to flash a non-GB ROM, you need the CWM2 (which is what you did). It sounds like after you put this recovery back though, you tried to flash a GB backup? This won't work (since anything GB requires CWM3).
If you have the CWM2 recovery, just go download any Froyo-based ROM you want to use, place the zip on you SD card, boot into recovery, and apply the zip.
nah just tried to flash a 2.2 rom through cwm2.5 no backup will only flash gb backup through 3.0.0.5
I am using the newest amon recovery. Everytime i try to restore a nandroid i save it gives me bootloops. I normally wipe everything twice and flash caulks format all zip. Is there something im doing wrong?
Sent from my PC36100 using XDA App
i would love to have this answer also...was getting the same thing happening to me, sumtimes bootloop off a hot restart...various roms, mysn, mik, virus, miui, didnt really matter which i was coming from or going too...
have since unrooted my phone and rerooted it just to see if sumthing was off...so far so good...would still like to have answers as to why though.
amon ra 2.3
latest radios
oo3 hardware
3.70
hboot .76 eng boot
Same here i rerooted and then reooted back and i still get the same result. Wonder if i am supposed flash the rom, then restore? On my hero i never had issues.
Amon ra 2.3
004 hw
Newest everything
Myns rls5
Ziggy nwest
Sent from my PC36100 using XDA App
Is your usb plugged in while either backing up or restoring? Have you tried loading a different version of amon?
U need to flash a kernel, nandroid dont save that
Sent from my SGH-T959 using XDA App
so your are saying flash the kernal first then restore nandroid restore?
Okay I just tried what you said and I still got bootloops. And my USB is never plugged in when i do a nandroid.
Something in the backup is giving you bootloops. Try completely wiping, the flashing a new rom.
You can review the recovery log too.
Sent from my PC36100 using XDA App
DEFINITIONOFREAL said:
U need to flash a kernel, nandroid dont save that
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes it does. Likely the issue is that a wipe is not being performed before restoring the data in the nandroid.
Sent from my PC36100 using Tapatalk
Garbage in, garbage out.
If your device was unstable when you backed it up, it will continue to be so after you restore.
Try a different Sd card. If your device continues to be unholy, revert back to a stock based rom or even RUU. If your issues persist, you likely have a hardware fault.
Basic troubleshooting 101...
Nandroids dont replace the kernel, do the nand then flash the kernel
Sent from my SGH-T959 using XDA App
i really need sum help...have posted here once before on this issue...i just flashed mik4.5 last nite...made a backup this am...flashed sum mods and made another nand backup this afternoon...needed a text message off the first nand backup so i wiped everything and started the nand restore...installed just fine and started to boot up just fine untill the boot animation stopped...then it started bootlooping...wth man...i have had my evo since it came out and been using amon ra since i started this adventure we call rooting...never have i had so many things go wrong with nand restore or backups...9 out of 10 backups i have made since 1.8 has become obsolete has not worked...please help...ty
Man I'm having bootloops all the time now ever since i updated the new combo radios and flashed myn RLS5. On sense with rls5 my phone reboots a lot kinda and with AOSP roms like MIUI my phone reboots like every 24 hours and goes on a bootloop. I can't figure out what's going on. Tried messaging some devs but they don't answer me
Did u run Calkulins Format All.zip?
Sent from my PC36100 using XDA App
LuvThyMetal said:
Man I'm having bootloops all the time now ever since i updated the new combo radios and flashed myn RLS5. On sense with rls5 my phone reboots a lot kinda and with AOSP roms like MIUI my phone reboots like every 24 hours and goes on a bootloop. I can't figure out what's going on. Tried messaging some devs but they don't answer me
Click to expand...
Click to collapse
When you switched roms, did you do a format data/calkulin's format all? doing either or should fix your bootlooping problem.
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
marcusva79 said:
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Same here bro. I've tried 3 different roms this weekend thinking it was just miui causing the problem but I actually got bootloops on all of them . This is weird
Sent from my PC36100 using XDA App
"Wipe everything", is that a factory restore/reset?
Cause that's what I do (factory reset).
Then the nand restore............
marcusva79 said:
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Are you flashing kernels over that?
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Few suggestions: Are you wiping properly, do you have the latest recovery (amon ra or clockwork), are you flashing gapps, did you update to all the latest radios/wimax/prl?
Why don't you try to flash decks aosp rom!
http://forum.xda-developers.com/showthread.php?t=1078558
Sent from my PC36100
jjchdc said:
Hello forum,
I recently switched from CM7 because I was having some issue with random resets and FCing with Maps that slow down and shut off my phone. I flashed to the New Fresh ROM to try it out. That worked fine, but I missed the pull down notification bar. I tried Salvage-Zen but got stuck in a boot-loop and then I tried Salvage. I got past the boot screen but when the Android pops up even though I click I can't go any further. Does anybody know of a possible solution?
Click to expand...
Click to collapse
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Same problem on friends phone just use amon RA wipe everything twice and flash and be patient with the white evo 4 g screen it may take a while there.
Sent from my PC36100 using XDA Premium App
I'm wiping completely using both Clockwork and Amon but its still a no go and I flash falls when using aosp. I'll try that Rom and report the results.
Sent from my PC36100 using XDA App
playya said:
do you do a clean wipe before flashing roms or are you just installing one on top of the other. I would suggest looking for Caulkins format all zip and run it prior to flashing a rom
Click to expand...
Click to collapse
The format all was just what I needed. Thank you very much!
I have been trying to flash Shooter E3, MikG, and Synergy. I cannot get any of them to work!!! They flash fine but all get stuck in a boot loop. I have wiped everything, more than once and redownloaded all of them just to check. Every other Rom i have downloaded (CM6, Cm7, Fresh, Stock, Myns Warm, MIUI, etc.) all flash and work fine. Anyone have some ideas???
I think I read somewhere that u have to use RA recovery but not 100% on that. If ur on cwm then try with RA. If ur on RA then idk
Sent From My Pocket
Correct, and it has to be the latest version 2.3
Sent from my nike hating evo!
I am using 2.3, but does my sd have to be partitioned?
Sent from my PC36100 using XDA App
legasus233 said:
I am using 2.3, but does my sd have to be partitioned?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No it doesn't but it helps if you want more internal space for running a rom using A2sd
Jlallman said:
No it doesn't but it helps if you want more internal space for running a rom using A2sd
Click to expand...
Click to collapse
Ok, then any other ideas why any 3.0 rom I load results in an endless bootloop?
legasus233 said:
Ok, then any other ideas why any 3.0 rom I load results in an endless bootloop?
Click to expand...
Click to collapse
If you get a bootloop, that's because the phone wasn't wiped correctly. Be sure to do a full wipe [factory/data, cache, and dalvik cache].
{ParanoiA} said:
I think I read somewhere that u have to use RA recovery but not 100% on that. If ur on cwm then try with RA. If ur on RA then idk
Sent From My Pocket
Click to expand...
Click to collapse
RA is not required I flashed in CWM all the time, I use RA now because it wipes better just like Charmin!
---------- Post added at 11:53 AM ---------- Previous post was at 11:50 AM ----------
legasus233 said:
I have been trying to flash Shooter E3, MikG, and Synergy. I cannot get any of them to work!!! They flash fine but all get stuck in a boot loop. I have wiped everything, more than once and redownloaded all of them just to check. Every other Rom i have downloaded (CM6, Cm7, Fresh, Stock, Myns Warm, MIUI, etc.) all flash and work fine. Anyone have some ideas???
Click to expand...
Click to collapse
Oh! Btw I'm running Synergy RLS1 it was flashed in CWM just remember if you flash in CWM do it three times over or so it just seems to work better
I am using RA 2.3 and have been sure to wipe everything, every option except sd card (duh). I have wiped multiple times, tried Calkulins format all, kings format all. It seems to start looping right when the phone boots up and starts sending/receiving data. Could this be a radio problem??
Most of the 3.0 roms, shooter especially, take a very long time to load. Usually around 10 minutes on first boot...are you waiting long enough?
im having the same issue, everything worked fine till i tryed to use firerats method to install kingedrunny 0.3. now it just sits at the boot screen, 37 mins & counting now
i also noticed when i flash a new rom it takes abot 1 min which is unusually fast.
I waited upwards of 1 hour. I am thinking of throwing in the towel.
Sent from my PC36100 using XDA App
im back on a 2.xx rom till i figure this out. may just have to flash back to stock & start from scratch.
im going to try again in a few since i have to re do my nv items anyway
I fixed mine, here's what I did, hope it works for you
http://forum.xda-developers.com/showthread.php?t=1265585
I have been trying to hook a buddy of mine up with a new rom for his Evo, basically make it exactly like mine with the newest Fresh Rom. I rooted his phone with Revolutionary and it all went just fine, the phone is now rooted with Superuser successfully installed. I put the Fresh zip on his SD card, wiped everything as you are supposed to, and then flashed the zip. It flashes fine and boots up, loads to the lockscreen and setup, but then reboots and does the whole process again, basically a bootloop. I have tried various roms and kernels, wiped over and over again, redownloaded the file, etc., but nothing seems to work. Am I missing something?! I never had this issue installing this rom on my phone. Any help would be appreciated!
try using a different recovery
Something other than RA? What do you suggest? CWM is crap isn't it?
Sent from my PC36100 using XDA App
Give newer versions on CWM its work just fine for me. I never had a problem.
Sloth
I am skeptical that a different recovery will fix the problem, but I will give it a try and report back. Is there anything else anyone can come up with?
I had a really weird issue where I couldn't flash any of the Gingerbread roms a while back, and had flashed goodness knows how many since I bought my evo on launch day and rooted it day one when it was available.
Trying different recovery versions might help, but if it doesn't, I'd suggest to unroot it and start all over. Find a post in the dev section on unrooting, go back to the stock sprint rom, and start over.
I did that, and was then able to flash all gingerbread roms and get them to not bootloop.
I'm not the only one that was having the problem, but NO devs could/would help figure it out. Not even flipz. Give it a shot.
Thanks for the info, I will try to Recovery thing first and then do a full wipe out and start over from a stock rom. The weird thing about it is that this is the first time this phone has been rooted and the first attempt at flashing roms.
Just curious, how many times does it reboot?? Over and over and over, or are you pulling the battery after the first or send time?
Over and over
Sent from my PC36100 using XDA App
Try recovery and fast boot from there.
Sloth
I changed recoveries to clock work, and it did not make a difference. I continued to get the same boot loop as before with RA. I just wiped out the entire system, and went into the boot loader to unroot back to stock. I will report back my results once I am done
Sent from my PC36100 using XDA App
Either change you clockworkmod or try something else. Dam man that sucks.
Sent from my PC36100 using XDA App
SLB9884 said:
Either change you clockworkmod or try something else. Dam man that sucks.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Changing up the recovery did nothing to fix my problem. I unrooted his phone, regained s-on, flashed a stock rom and am starting over. I will report back my results.
Well damnit anyway, starting all over from scratch did nothing as well. Still get the same damn bootloop. WTF!?!? Anyone else have any other ideas?
I've read every post and I can't think of anything that would help. You think it's a software issue, like inside the phone itself might be bad?
Sent from my PC36100 using XDA App
Is this something that could be discovered on a logcat? I have never done one or know how they work, but would anyone be willing to diagnose the problem if I am able to get a logcat?
Damn that sucks. What your status. Did you fix the bootloop?
Sent from my PC36100 using XDA App
Still no fix discovered, any help on this would be greatly appreciated
Sent from my PC36100 using XDA App
What's interesting, is that this is the exact same boot loop problem I was having on my Evo when trying to flash any sense 3.0 rom.
Sent from my PC36100 using XDA App
Have you tried using / flashing any of the zips that are prepackaged " wipes " ?
Have you tried using TWRP recovery ?
I never had any problems while using RA but had numerous failed flashes with Clockwork.
TWRP has been stellar so far ... no failed flashes yet.