A huge problem seems to have arisen on my Desire Z.
After using Andromadus 8 for a while I decided to try some other ROMS.
They were:
- Andromadus V10 and 11
- Virtuous Quattro RC3
- Ice Cream JIBwich 1.1
- BlissDroid
- Android Revolution HD 7.0
All of these ROMS flashed after using Superwipe G2 however were stuck on the initial boot screen.
I left some of these ROMS on for more than an hour on the boot screen to no avail.
The only ROMS that still seem to function are Andromadus V8 and MIUI ICS (however with no Wi-FI)
Please can anyone give an indication of what is wrong?
Some roms don't want you to wipe anything because the flashing will do it for you. Although it could've been that the roms have problems?
Sent from my CM7 G2!
i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.
Cleared dalvik and checked all the MD5. Everything seems fine except it doesn't work
Tried a ordinary factory reset/data wipe?
-Nipqer
starop013 said:
i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.
Click to expand...
Click to collapse
Superwipe does clear dalvik cache.
I am at my wits end
ONLY Andromadus 8 works for some reason
I cleared it and cleared it, and reflashed every combination of roms
BUT only 8 works and I'm tired of not having my camera anymore
I've even tried bare Sense 2 ROMS to no avail. Every ROM is stuck on bootloops
Does anyone have a solution?
Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer
Have you tried flashing from recovery directly? RM is great for convenience, but I just don't trust it to do things properly. I've had this happen to me sometimes where a ROM looks like it's flashed, but hasn't. Weird, I know. Try the following, it worked for me before:
1. Flash SuperwipeG2+ext4 (if you want the ext4 filesystem)
2. Flash your ROM
3. Check to see if it worked
4. If it didn't work, flash your ROM again without wiping
Usually that fixes it for me. In 4EXT recovery, you can check the partition sizes to see if the ROM installed properly. Not sure if CWM does that as well.
Nipqer said:
Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer
Click to expand...
Click to collapse
Nipqer
You sir are a legend
An obvious solution that makes me wonder why I didn't think of it
Thank you, thank you
flashing through recovery is just easier for some, and if your not near a computer. but for best results always fastboot -w and flash rom via fastboot, just makes life easy the first time. and im ocd a little so i also flash superwipe and manually wipe data/cache. so if you dont wont any issues, fastboot wipe, fastboot flash... your golden!
Related
Hi,
I was hoping some of the smart people here might be able to point me in the right direction for a solution to a problem I am having.
As the thread subject says; I've flashed several ROMs based on the official 2.2 release and I end up with a boot loop at the first HTC logo, it never makes it to the quietly brilliant screen, it just re-boots continuously until I pull the battery.
However, ROMs based on 2.1 boot fine, both official ones and modified ones obtained here on the forum. Also, the 2.2 based DeFrost ROM boots fine.
The actual flash process seems to go fine, with no errors being reported.
I've tried wiping/factory reset before I flash, after I flash, but the result is always the same.
I've tried with and without the latest radio installed.
I've tried booting with the SDCard and SIM removed, but no luck.
I've even tried downgrading from bootloader 0.80 to 0.75, again with no difference.
A bit of background info;
My Desire is a generic unbranded model.
Yesterday, I did try to install the OTA 2.2 update, but something messed up during the flash process and I ended up with a corrupted recovery partition and (once again) a boot loop.
Thankfully, I managed to flash an older RUU file and things are back to normal, except for the in-ability to boot any ROM based on the official 2.2 release.
If anyone can help I would be forever in your debt, as this really is driving me crazy.
I had the same problem when I installed the new 2.2 HTC ROM without wiping...
Anyway try to wipe both factory reset and all caches with both amon ra recovery port and clockwork recovery...
Same problem... but fixed I fixed it installing this: http://forum.xda-developers.com/showthread.php?p=7483900
I have same same loop like that
I dont know why? I use r5 modaco custom rom. it seems well. but when I try to use edge/3g, it starts loop booting. if turn off edge/3g, the phone works perfectly.
after that, I tried to flash another ROM, Wipe Factory reset, Wipe Cache, Wipe Dalvik, even wipe ext but it still happens
I put out SIM, the phone boot correctly( maybe just reboot one time). but put SIM in, it reboots.... sometime the phone vibrate 5 time at HTC screen .
somebody can help me?
ps: how to know wipe dalvik work perfectly? I cant see any info about it done
I had the same problem with the first rooted official rom I tried to install, then I restored to my modaco mcr-r5 (2.2) rom, updated to the new radio and then installed the rom from nickiberli via rom manager and it worked.
btw, I selected wipe data in rom manager when prompted, lost all my apps and data but the setup wizard ran when it booted up first time.
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
raz2133 said:
Thanks for the suggestions.
I have now tried wiping with both ClockworkMod and AmonRa.
I wiped the following with both, but still the boot loop persists with 2.2 based ROMs.
Wipe Data / Factory Reset
Wipe Cache Partition
Wipe Dalvik Cache
I also tried the MCR-R5 ROM, but it also fails to boot for me. It doesn't loop, but it seems to freeze on the first HTC screen.
As mentioned previously; 2.1 based ROMs boot flawlessly.
I really don't know what else to try.
Click to expand...
Click to collapse
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
ratykat said:
try http://forum.xda-developers.com/showthread.php?t=741867
Ive had a bit of a shaky day with custom roms, rooting not working etc, first rom i tried failed, but this one worked straight out, wipe cache, default, ext partitions and dalvik, I used mybackup to back everything and wiped the whole phone, works like a charm now
Click to expand...
Click to collapse
Thanks for the suggestion, but I just tried this ROM and it wont boot for me either.
bakedecake said:
Do you have an ext partition on your memory card for a2sd? If you don't and you try to install a rom with a2sd then I think it might cause this kind of problem. I had a2sd with an ext partition on the card, I booted into clockworkmod recovery and formatted the sd card and the phone wouldn't boot.
I generated a new mcr-r5 without a2sd or a2sd+ and installed and all was ok, if that works then I would try installing the new radio and then the new rom which is what I did.
Click to expand...
Click to collapse
I do have an ext partition on my SDCard and I have tried ROMs with and without A2SD. In fact, the ROM I have used for most of my tests is "Rooted Official HTC Android 2.2 (FroYo) ROM [Market issue fixed]", which I don't think has A2SD.
I have tried booting with 3 different SDCards so far, and of-course I have tried with no card.
HI... i updated my phone with cyanogen 7 rc2, but after it booted up it's stuck in the animation that says cyanogen mod 7 , and the blue android sign... in comes than goes, again it comes... about 20 min stuck... what to do???
It sounds like you need to go into recovery mode and delete all your caches. If you are using ClockworkMod recovery do the following (make sure you are backed up first):
Delete all user data and info (under wipe data/ factory reset),
Wipe cache (under wipe cache partition),
Wipe Dalvik Cache (under advanced).
Then once you've done that try installing and running the ROM again.
i done that one time... for info im using AmonRA.. i cleaned all the cache and everything also... and installed again... nothing happens... fortunately i restored my nand backup and booted my phone with the OTA again... waiting for some answer.... do u think that installing stable version can fix this?
Sounds like a bad flash. I had rc2 running for a month or so with no issues. I've had times when the rom just doesn't install properly ans reflashing fixes it.
Download the zip again, if possible check md5 to make sure it's all good, make sure you have the desire/bravo GSM version, clear everything and flash just the rom and nothing else. If it boots, then go back and flash your gapps and whatever else you want.
Sent from my HTC Desire using XDA App
thx for replying.. as i was waiting for your reply, i download the cm 6 that is a stable version and checked, it has the same problem too.. i also downloaded GingerVillain 1.6 and it had the same problem too. do u think the problem might be that my phone is "s-on"? and how should i know if my phone is s-on or s-off... when i was rooting my phone with unrevoked, i checked the option that says disable security, but i'm not sure if it's disabled.... because i can't install un-signed zip packages....
any reply?
That definitely sounds odd. Its definitely not an issue with S-ON/OFF, nothing you've done here requires S-OFF to work properly.
Lets just make sure you're following all the steps.
In amonra, you've done your nandroid backup, so no need to do it again. There's no point having a non working backup
Go to wipe and wipe data/factory reset
Wipe davlik cache
Wipe sd-ext (shouldn't need to do this one as you don't have apps2sd yet, but better to be safe)
Now you flash your update.zip, then reboot and you should be fine. The only other thing I can perhaps suggest if every rom you flash sticks at boot is to perhaps try clockwork recovery instead of amonra. Apart from that we might have to wait for folks more knowledgeable than myself cause I'm all out of ideas.
thx for reply.... in meanwhile , i s-off ed my phone and it has the same problem too... i have problem with all cm and gingervillain roms.. but i don't have any problem with leedriod... one more question that maybe the problem is that i have android 2.2 installed, but gingervillain and cm use android 2.3 ... this maybe the problem.... and that's why leedroid works right, because it uses android 2.2.... i'm going to check OxyGen roms... i will post the result here...
i also faced same problem CM7 .. i tried CM6 and it went on fine..
heyyy... right after i posted the reply , i went to recovery and wiped anything, then installed gingervillain 1.6, and everything's fine now... it booted up and now im setting it up.... im going to check the cm 7 too.
i tried cm7 rc2 ... and it was fine and now im using it... here's a how to for solving the problem...:
1.S-OFF your device with AlphaRev : http://forum.xda-developers.com/showthread.php?t=805811
2.Install the AlphaRev Recovery(S-OFF Image will do it automatically).
3.Go to recovery and install the rom...
4.Boot up and it should not go to system and it should stay in loop as the problem was..
5.Now you should reboot your device into recovery... there are two ways to do this... either take the battery off and put it on, then boot to bootloader by pressing the volume down and the power key and select recovery , or the second way connect it to your computer and start adb and run this command:
adb reboot recovery
6.In AlphaRev recovery first wipe the cache partition , wipe user data, and factory reset...
7.then install the rom (either cm7 or gingervillain)...
8. boot up , and now you have the system running...
This solved my problem... reply if it didn't yours...
hooo.. it worked for me now. just kept update.zip in a new SD card and not flashed google apps..
im very happy that i solved one's problem.. ... thread marked as solved...
*UPDATE* : now i realized that we can mark it as solved.. !!! hehe.. Admin do it for us...
This is really bothering me. I've attempted to flash into MIUI but I am stuck on the boot screen and it's just staying there. I tried two different sources of MIUI, the latest being from here: http://forum.xda-developers.com/showthread.php?t=915527 - the thread for MIUI Evo 4G.
I don't know what I'm doing wrong and I don't know how to make this work. This has been my first try at installing a custom ROM. I already have a backup readily available.
I have tried removing my battery and restarting the phone. How do I fix my problem?
Edit: I have tried clearing dalvik cache and data cache. No go.
Gad the same prob... but didnt bother to ask... i just loaded cm7.. but i would like to try miui lol
sent from my supersonic evo .:CM7:.
infallibleapex said:
Gad the same prob... but didnt bother to ask... i just loaded cm7.. but i would like to try miui lol
sent from my supersonic evo .:CM7:.
Click to expand...
Click to collapse
That isn't helpful and doesn't contribute to the thread in any way.
YouThere said:
This is really bothering me. I've attempted to flash into MIUI but I am stuck on the boot screen and it's just staying there. I tried two different sources of MIUI, the latest being from here: http://forum.xda-developers.com/showthread.php?t=915527 - the thread for MIUI Evo 4G.
I don't know what I'm doing wrong and I don't know how to make this work. This has been my first try at installing a custom ROM. I already have a backup readily available.
I have tried removing my battery and restarting the phone. How do I fix my problem?
Edit: I have tried clearing dalvik cache and data cache. No go.
Click to expand...
Click to collapse
I'll first ask the usual question: did you wipe everything (factory reset/wipe data, cache, dalvik cache, system, boot, and sd android secure) before flashing the new ROM?
And have you tried to download from this site?
http://miui.us/
Use amon RA recovery, flash a format all zip (you can find it with a quick search) and then flash miui
Deck's + SZ + SuperCharger script + ViperMod script.
Hi all, I'm pretty familiar with flashing custom ROMs as I previously had a Samsung Galaxy S Captivate.
I recently got a Telus T989D, and I'm having some frustrating problems trying to flash a custom ROM. I have ClockWorkMod Recovery installed, and have been trying to flash various Cyanogen CM9 ROMs onto the phone. They all install properly, but once it gets to the Cyanogen splash screen (with the Android man turning angry for CM9), it gets stuck here.
I thought perhaps I needed to flash my radio, since all these custom ROMs were for the T-Mobile T989 "hercules" model. So I flashed the SGH-T989_UVLE1_radio.zip hoping that would work. Same problem.
Kind of at a road block here - any suggestions would be very much appreciated. Thanks!
Rhombuss said:
Hi all, I'm pretty familiar with flashing custom ROMs as I previously had a Samsung Galaxy S Captivate.
I recently got a Telus T989D, and I'm having some frustrating problems trying to flash a custom ROM. I have ClockWorkMod Recovery installed, and have been trying to flash various Cyanogen CM9 ROMs onto the phone. They all install properly, but once it gets to the Cyanogen splash screen (with the Android man turning angry for CM9), it gets stuck here.
I thought perhaps I needed to flash my radio, since all these custom ROMs were for the T-Mobile T989 "hercules" model. So I flashed the SGH-T989_UVLE1_radio.zip hoping that would work. Same problem.
Kind of at a road block here - any suggestions would be very much appreciated. Thanks!
Click to expand...
Click to collapse
Oh, and to clarify in case anyone asks - I have been doing data/cache/Dalvik wipes in recovery before installing the ROM.
Rhombuss said:
Oh, and to clarify in case anyone asks - I have been doing data/cache/Dalvik wipes in recovery before installing the ROM.
Click to expand...
Click to collapse
If you are running CWM 5.0.2.7 non touch recovery, you have to use TDJs Superwipe script first to wipe data partition and system partition. Then you flash the ICS radio (if you haven't done so already) then the CM9 ROM, then ICS Gapps.
After this you need to flash TDJs Cache Wipe script. This will properly wipe cache, dalvik, and fix permissions. CWM 5.0.2.7 doesn't wipe and align the cache properly and gives problems. I never had any issues with CWM when running those scripts and it boots up everytime.
Alternatively, you may want to install TWRP 2.2.2 instead of CWM. It's a touch based recovery, but very simple to use and much better than CWM in my opinion. You also don't need to run the scripts since the data and system are wiped properly and cache and dalvik are also cleared properly as well.
If you go to the development section, under the TWRP thread, and search for flashable zip, there is a 2.2.2 flashable available that you can use in CWM. Then the next time you boot into recovery you will be in TWRP instead of CWM.
Chochiwpg said:
If you are running CWM 5.0.2.7 non touch recovery, you have to use TDJs Superwipe script first to wipe data partition and system partition. Then you flash the ICS radio (if you haven't done so already) then the CM9 ROM, then ICS Gapps.
After this you need to flash TDJs Cache Wipe script. This will properly wipe cache, dalvik, and fix permissions. CWM 5.0.2.7 doesn't wipe and align the cache properly and gives problems. I never had any issues with CWM when running those scripts and it boots up everytime.
Alternatively, you may want to install TWRP 2.2.2 instead of CWM. It's a touch based recovery, but very simple to use and much better than CWM in my opinion. You also don't need to run the scripts since the data and system are wiped properly and cache and dalvik are also cleared properly as well.
If you go to the development section, under the TWRP thread, and search for flashable zip, there is a 2.2.2 flashable available that you can use in CWM. Then the next time you boot into recovery you will be in TWRP instead of CWM.
Click to expand...
Click to collapse
I just installed TWRP and I'm still running into the same issue. The Cyanogen splash screen just runs indefinitely. Looks like that wasn't the problem? Does it matter if you're rooted or not, if you try to flash a ROM from recovery?
Rhombuss said:
I just installed TWRP and I'm still running into the same issue. The Cyanogen splash screen just runs indefinitely. Looks like that wasn't the problem? Does it matter if you're rooted or not, if you try to flash a ROM from recovery?
Click to expand...
Click to collapse
Use the Darkside Superwipe to recreate all your partitions correctly. Sometimes when they are not aligned properly (by TWRP) you get weird boot hangs.
Don't restore data! Instead back everything up with something like Titanium and restore user apps only after the ROM has booted and you are satisfied.
+1 for the last post. Should work 100%!
Sent from my SGH-T989 using xda premium
---------- Post added at 12:17 AM ---------- Previous post was at 12:09 AM ----------
http://forum.xda-developers.com/showthread.php?t=1477955
Sent from my SGH-T989 using xda premium
Hello!
After some fiddling around I have finally succeeded into installing the MIUI custom rom. (had a heck of a work around to perform because I forgot to put the custom ROM on my SD card first.)
Right now, I've got Clockwork Recovery 5.8.4.0 installed with the latest miui. Fastboot is also installed and working, and my phone is unlocked. The correct boot.img has also been installed.
It even boots. BUT. After it has showed the MIUI logo and goes to my home screen, it starts loading for like 4-5 seconds where everything still works, and it then stops. Crash. The screen freezes and my phone reboots. It seemed like a SIM card problem to me, but even removing the SIM card and booting my phone wont solve this issue. Does anyone have any clue what I can do?
Summary of installed software:
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
Latest MIUI for One X (downloaded this afternoon)
Latest ADB Development Kit. (Not used though)
Latest Flashboot.
Factory Reset performed (Whole phone is empty except for above mentioned programs.
Thanks in Advance!
P
Erase Cache
While in Fastboot Mode .Perform This command
Fastboot erase cache
Should do the job for u!
I would suggest flash the boot.img again and then erase cache again.Will work
Tried it, but..
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Clockwork Recovery V5.8.4.0
HBOOT 1.12.0000
^^ for ARHD 16 u need hboot 1.33 , 1.36 depending on your CID
for miui did you do full wipe?
Piedro92 said:
I'm afraid it didn't do the trick.
Even flashing another custom ROM (Android Revolution HD16) with it's corresponding boot.img didn't do the job. The crashing times have also changed now. It sometimes works for like 5-6 seconds into booting the homescreen, and sometimes it doesn't even reach it.
Click to expand...
Click to collapse
Did you wipe cache and dalvik cache? I think ARHD does that anyway, but might be worth doing the superwipe.
Oh, and if you're restoring system data or system apps with Titanium backup, stop it.
HBOOT!
I am afraid ur not on the right CID version for installing JB roms.
Please update ur Hboot
@ali3nfr3ak: Yes, I did a full wipe before MIUI. After every flash I do a Dalvik Cache Wipe, Factory Reset Wipe and Cache Wipe. Even the fastboot receive a cache wipe after every flash.
How do I update my HBOOT? The rest seemed pretty straight forward, but there are tons of versions out there, and I do not know which one I should be taking. And what is CID? I've also been having troubles porting a Super Wipe toward my mobile phone. Can a Super Wipe be performed within fastboot/recovery?
Haha and no, I'm not using Titanium Backup
Right, I've succesfully restored my phone to it's old state. Flashing MIUI again provided the same error. Could it be that my hBoot is out of date here? My One X still has the 4.0.4 android version, whilst MIUI is based on 4.1, right?
Change the rom, miui isn't good.