Related
Hi all
I have a HTC Desire which I initially rooted using the UnRevoked method. Using Clockworkmod Recovery, I began installing ROMs to my hearts content. Everything was perfect, and I was changing ROMs every few days, testing them out, trying to find the perfect ROM for me, restoring back to the one which was currently my favourite
Later, being a newbie, I discovered that when I try to use ADB to push apps to the phone, I realized my NAND was read only, and my phone was S-ON. I then used AlphaRev HBOOT to S-OFF my phone, and this is where things have taken a turn...
It seems that since I have done the S-OFF, I can install ROMs fine, I can back them up and restore them too, all with no problems or errors during the process. But now it seems that whenever I restore to any backup, when the phone boots up, it gets to the point where the screenlock is visible, and then once I unlock the screen, I seem to get loads of force closes for various apps popping up on the screen and not letting me do anything! I can no longer rely on my Clockworkmod backups anymore
Extra information:
HTC Desire S-OFF via AlphaRev 1.8 HBOOT, CWM-AlphaRev Recovery 2.5.1.8Problem seems to occur with 2 ROMs I tested after S-OFF. Currently running InsertCoin1.8h DHD ROM port, and my last backup of this ROM when restored gave same problem as above. Previously running Oxygen 2.0 RC7, last backup also gave force closes when restored. With the Oxygen ROM, I managed to solve the problem by re-flashing the original ROM zip without wipe, but all my customizations and themes are lost. When I flash any ROM, I always wipe using the "Wipe user data and cache" option, then wipe the Dalvik cache, and then flash. I do the same thing when restoring to any backed up ROM too. My phone is rooted, I have SU permissions, I can push files to /system/app via ADB without any errors, so it is S-OFF. I do not get any problems using the ROMs, they are fast and very fluid, I can install themes and zips cooked in UOT kitchen, other kernels, patches, etc. I have formatted my SD card 3 times, and re-partitioned it each time using ROM manager initially, and later Clockworkmod Recovery 3.0.0.5 (temporarily installed this recovery to create 1GB EXT partition, presumably on EXT4?)
Sorry for the huge dump of information, its just to provide as much information as I can, so to not frustrate anyone kind enough to help me (assuming you are not already frustrated because I asked a complete newbie question with a simple answer!)
Any ideas what the problem can be? I thank anyone in advance and really appreciate any responses
Did you wipe data and cache?
Sent from my HTC Desire
I (and some other users) had the same problem with the 2.5.1.8 alhpa rev recovery..I solved using the 2.5.0.7 recovery
Did you wipe data and cache?
Sent from my HTC Desire
Click to expand...
Click to collapse
Yes, I always do, it is something I am weird about
I (and some other users) had the same problem with the 2.5.1.8 alhpa rev recovery..I solved using the 2.5.0.7 recovery
Click to expand...
Click to collapse
Initially I did not install the AlphaRev recovery, and was running 2.5.0.7. I think I still had the same problem, thats why I installed the AlphaRev. But honestly speaking, I cant remember properly, so I cant be sure. I will try other recoveries and post back.
Thanks for the suggestion!
Hello all
I just updated to 3.0.0.5 and now when I reboot into revocery via Rom Manager I get to the HBOOT screen with the only options for:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I don't get the usual black background with green letters? From what I've read it should go to the black background but now with Orange letters?
Please advise at what I'm doing wrong. Which option should I use to get to clockworkmod 3.0.0.5
Thanks in advance
-g
A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.
patsfan1130 said:
A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.
Click to expand...
Click to collapse
The oldest version available is the current one I am on 3.0.0.5. There are newer version .6 .7 and .8? Do you know if those versions will produce the same issue?
After much reading this cwm3 is causing lots of problems. I've searched the forums for a write up on how to flash back to 2x but haven't found one. Does anyone have a quick write up to get this done either through fastboot or adb?
Thanks
-g
I have a thread in the dev forum updated today that explains exactly what you want.
I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?
tdiman said:
I have a thread in the dev forum updated today that explains exactly what you want.
Click to expand...
Click to collapse
Awesome tdiman! Thanks for the write up, it worked. I just needed to enable wipe!
sitrucz said:
I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?
Click to expand...
Click to collapse
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either
tdiman said:
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either
Click to expand...
Click to collapse
First, thank you for your response. I'm not going to spend too much time on this since 3.x is the new standard. I use Cyanogenmod 7 dailys as my daily driver and rEVOlution 2.2 as my sense rom backup. So, if after a restore and rebooting and then wiping cache and davlik and possibly reflashing a froyo kernel, incredikernel 12/20, doesn't solve it I'll just restore from 2.x recovery, upgrade recovery, and then get a new backup. I'll do the same for Cyanogen and call it a day and start using cwm 3.x.
After testing I was unable to restore my rEVOlution rom using 3.0.0.8 from 2.5.1.2. I wiped cache and davlik and flashed a froyo kernel and still no dice. It was strange even though I could only see the boot logo the rom was fully booted as I had voicemails and I heard the voicemail notifications but the home screen never came up. I rebooted and still the same thing. So I reflashed 2.5.1.2 restored rEVOlution upgraded recovery then got a backup. I did the same for my Cyanogen nightly and I'm on 3.0.0.8 now for good. I wanted to pass this on to others. If I want to restore an older backup I'll just restore recovery to 2.5.1.2 and do a restore.
I have looked across this forum and two other forums and have not found an answer which will satisfy me.
I have successfully rooted and flashed different ROMs many times, so the whole process is not anything I don't understand.
I can successfully flash any of the Cyanogens, Incredibly Re-engineered, Redemption, and SkyRaider ROMs.
I CAN NOT flash but ONE ROM with 'Z' in the title and that is Incredibly Re-engineered Z. Every other ROM such as Super Z, Warm Z 2.2, IncDoes, Uber Z
My DInc will just sit at the HTC Incredible white screen when I reboot after a successful load via clockworkmod.
I have left it sitting for 30 minutes plus while sitting at work. Nothing. Only choice I have is to restore from backup to a working ROM.
Any suggestions?
The ROM's you quoted are mostly using ClockWorkMod Recovery version 3 for the install. If you are on CWM version 2 the result you are getting is kind of expected. The v3 scripts are not compatible with v2 but v2 does not know any better so tries to install it.
Go into ROM Manager and see what recovery you are on and use RM to install CWM v 3.0.0.7
I would then try installing the ROM with RM selecting the wipe option
SIDE NOTE: If you are on CWM v3 and you try to install a v2 based ROM CWM will tell you that it is outdated
That is what I saw on other sites, but I have the latest version of clockworkmod v3.0.0.8 and have flashed the ROMs successfully with it, but they just wont go past the HTC Incredible white screen. The ones that gave me script errors, I have flashed down to clockworkmod v2.5.1.7 or whichever i seen in the OP of that ROM
I just do not understand it. =( ... I dont wanna be limited
Sounds like it could be related to you not having a Samsung Fascinate. I'd try to get a Samsung Fascinate and then you might have better luck.
Get back to work.
JWhetstone02 said:
That is what I saw on other sites, but I have the latest version of clockworkmod v3.0.0.8 and have flashed the ROMs successfully with it, but they just wont go past the HTC Incredible white screen. The ones that gave me script errors, I have flashed down to clockworkmod v2.5.1.7 or whichever i seen in the OP of that ROM
I just do not understand it. =( ... I dont wanna be limited
Click to expand...
Click to collapse
You probably did not catch my recommendation to use 3.0.0.7. 3.0.0.8 has known problems with not clearing everything.
In ROM Manager at the bottom install CWM 3.0.0.7 and try flashing the ROM from the SD Card with ROM Manager and select the wipe option.
NilsP said:
You probably did not catch my recommendation to use 3.0.0.7. 3.0.0.8 has known problems with not clearing everything.
In ROM Manager at the bottom install CWM 3.0.0.7 and try flashing the ROM from the SD Card with ROM Manager and select the wipe option.
Click to expand...
Click to collapse
I might have to try this too as I'm having troubles installing roms and sticking in boot loop ..
If I change to CWM 3.0.0.7 from my current 3.0.0.8, will my previous backups on 3.0.0.8 still be useable through 3.0.0.7?
Thanks!
KB3MMX said:
I might have to try this too as I'm having troubles installing roms and sticking in boot loop ..
If I change to CWM 3.0.0.7 from my current 3.0.0.8, will my previous backups on 3.0.0.8 still be useable through 3.0.0.7?
Thanks!
Click to expand...
Click to collapse
Yes your backups will work
I will give that a try. I currently have only two flashable files for clockworkmod ... v3.0.0.8 and v2.5.1.2
I'll try and find the previous versions of clockworkmod, nandroid backup my working ROM, wipe data/factory reset, cache and dalvik and try this one more again.
JWhetstone02 said:
I will give that a try. I currently have only two flashable files for clockworkmod ... v3.0.0.8 and v2.5.1.2
I'll try and find the previous versions of clockworkmod, nandroid backup my working ROM, wipe data/factory reset, cache and dalvik and try this one more again.
Click to expand...
Click to collapse
Flash this zip before you flash the Rom this is for CWM 3.X.X.X it will wipe everything I have one for older clockworks to just let me know
http://db.tt/s1VTbac
Sent from my Incredible using XDA App
Keyboards said:
Yes your backups will work
Click to expand...
Click to collapse
Excellent, I'll change to CWM 3.0.0.7 with ROM manager then
newtoroot said:
Flash this zip before you flash the Rom this is for CWM 3.X.X.X it will wipe everything I have one for older clockworks to just let me know
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Thanks. I am up and running now. WarmZ twoPOINTtwo nightlies 03/31 =D
Very smoooth
Hi
I'm trying to flash a gingerbread rom to my desire but I always end up being stuck on the HTC logo. I tried several ROMS( opendesire, modaco with sense and without, some more too but can't remember the names,... ) The only gingerbread ROM that installs is CM7, but i have market problems that annoy the hell out of me ( can't find certain apps, need to hack to install bigger apps ). A shame because i really like CM, but i want to compare with others
Any idea why gingerbread won't flash correctly. I have tried several froyo ROMS without any issues before, by the way
I have
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
RADIO-5.14.05.17
thx
ntdst
Did you remember to wipe your data between each different install?
That's the most common problem when you get stuck at boot.
i use rom-manager and always create a back-up and wipe.
I also tried with an empty SD-Card and repartioned it ( with rom-manager ). The results are always the same, every gingerbread rom gets stuck. I thought there was something wrong with the partitions or maybe i need s-off for gingerbread... ?
What version of CWM do you have? Did you update manually to the new radio for the GB Roms?
- Recommended RADIO
http://insertcoin.dataninja.net/Addons/Radio/
If you flash the 32.56.00.32U_5.17.05.23. Radio a good idea will be to flash
the ril-firmare-drivers updates for it too
Click to expand...
Click to collapse
I'm using Rom Manager v4.2.0.2
It is possible that i flashed that radio with a previous modaco sense/froyo ROM.
should i first flash that one you mention and then try again?
Okay, Rom Manager Is not a recovery What's your recovery exactly?
And what ROMs do you try to flash?
AFAIK, you need to flash that first in order to get booted.
sorry clockworkmod 2.5.0.7 is current recovery
I really tried several ROMS
Modaco sense gingerbread
Modaco without sense
opendesire
oxygen
etc...
all and always stuck on HTC Logo except for CM7, that one works fine except for the market issues
- Clockworkmod Recovery 3.x.x.x (Recommended to be used! 2.x recoveries MAY have some problems with the updater-script => boot loop)
Click to expand...
Click to collapse
I found this in one of the ROM threads.
So my suggestion:
First try to update the radio to the newest (alredy posted the link).
If that does not help, then try to update your recovery.
updating radio and flashing updates did not help
i'm still stuck when trying to install oxygen
I could use some help in updating my recovery. I f i do this with rom manager 2.5.0.7 is the most recent.
I seems there's a 2.5.1.2 out and 3.x.x.x is not advised. Is there an update zip somewhere to use?
People report that Insertcoin S v22 can be installed with 2.5.0.7
Make sure you do a full wipe in THE RECOVERY, not ROM Manager or any program.
Too boot into recovery hold down Power+Vol Down while phone is off.
There:
1. Wipe data/factory reset
2. Wipe cahce
3. Under advanced menu > Wipe dalvik-cache
Also make sure your SD card is partitioned right.
And for the update - you can only update your recovery if you are S-OFF or you use Unrevoked3 with a custom recovery image.
Grab a copy of Ubuntu and check that the apps2sd partition on your card is formatted correctly. I tried all ways of formatting and partitioning (via clockwork/rom manager) and it never formatted correctly and always caused HTC boot sticking.
If I completely reformatted SD and reflashed an older rom (like Leedroid 2.3) would then boot fine. I then used Rom Manager to repartition & format SD, boot ubuntu (live CD is enough - no install required) then reformatted partition to EXT4, flashed and worked fine.
Also, is 2.5.0.7 your TRUE recovery version? Turn your phone on with vol-down held then select recovery - does the version change to an older one? If this is the case you may need to re-root is (Unrevoked) to update your recovery version permanantly.
Hope that helps.
If you are S-off you can flash newest recovery using fastboot, this flash would be permanent!
fastboot flash recovery recovery-clockwork-3.0.2.8-bravo.img
i agree with TMSsecret,
the gingerbread ROMs i have used seem to need a more recent version of HBOOT. First time I tried to flash LeeDroid 3.0.2, it didnt work. Applied S-OFF (which updates your HBOOT during the process) and tried again, worked no worries. Also, if you're keen to install the latest ROMs, upgrade to clockworkmod recovery 3.x... It took me a few tries to get FASTBOOT working properly (possibly because my version of windows XP has had too long to decompose), but if you persevere, it will work.
The best way to make sure your ROM will work is a thorough research session. Not slagging you at all, just pointing out the obvious. Look up everything to do with your intended ROM and read the threads.
Hey all-
So I've flashed to CM7 3 times now and each time I get everything setup correctly, my apps restored etc. But as soon as I go to reboot I get stuck on the CM7 loading screen forever. The image is animated, but it will not finish.. it will go all night if I let it.
I have a feeling the issue is in the method im using to install. I'm coming from Fresh 3.5 using Amon Ra recovery. I cleared all user data, dalvik cache and then flashed the rom. I then flashed gapps and it boots into CM7 fine. The reboot is the problem. Am I missing a step? Should I be clearing/formating/deleting more before flashing the new ROM?
Thanks guys. This forum has been a huge resource for me in the last couple weeks. <3
Coreyfuncrusher said:
Hey all-
So I've flashed to CM7 3 times now and each time I get everything setup correctly, my apps restored etc. But as soon as I go to reboot I get stuck on the CM7 loading screen forever. The image is animated, but it will not finish.. it will go all night if I let it.
I have a feeling the issue is in the method im using to install. I'm coming from Fresh 3.5 using Amon Ra recovery. I cleared all user data, dalvik cache and then flashed the rom. I then flashed gapps and it boots into CM7 fine. The reboot is the problem. Am I missing a step? Should I be clearing/formating/deleting more before flashing the new ROM?
Thanks guys. This forum has been a huge resource for me in the last couple weeks. <3
Click to expand...
Click to collapse
I think i know what ur doing wrong first flash the rom then reboot then go back to amon ra wipe cache and then flash gapps and if it still doesnt work then do the exact same things but with clockwordmod (which u can both flash from rom manager).
Sent from my PC36100 using XDA Premium App
Followup Question:
Can I restore a Clockwork Backup using Amon RA? Amon wants to check the nandroid folder for backups..and I don't have any nandroid backups (not sure how I didnt do one). can I move a existing clockwork backup from the clockwork folder to the nandroid folder on my SD's root and use that?
Or does anyone have any suggestions on how to flash to clockwork? Now when flashing to CM7 or Fresh I'm getting stuck on the loading screen.. Thanks
So, it looks like the issue is with gapps. When I flash CM7 it works great..once I reboot into recovery, flash gapps, I get the freezing error. I am using version:
gapps-hdpi-20101113-signed.zip
Is this what I should be using?
No there's a newer version you can use let me see if I can find it and get you a link...
Edit: I found the one on my SD card its not the newest but it should work
http://db.tt/YuaCnd9
Sent from my nightly EVO