Develop Bugs

[Q] desire z stuck on gingervillian and cant change roms!

hi there, i really need some help..not a tech genius..i installed the gingervillian 1.5 rom..everything went fine, but i forget to make a nandroid back up..when i install it was too late and my nandroid back up now is the gingervillian rom itself!..i dont really like the gingervillian because it wont work with htc sync. i have googled and tried so many ways i cant use other roms except gingervillian 1.5. all other roms just get stuck at the htc boot screen(for like 5 hours!)..factory reset dont work, full wipe dont work..i just need help on how to get back the original rom of the desirez 2.2 froyo..thx a lot..my life is counting on u genius out there!

I am assumng that you flashed CWM Recovery 3.0.0.x (orange) to install Gingervillian in the first place, right? Well in order to flash a Froyo version rom you need to flash the CWM Recovery 2.5.1.3 (green) back onto your phone prior to trying to flash a Froyo (2.2) based rom.
Update: The new CWM 3.0.0.5 recovery from ROM Manager now support both 2.2 and 2.3 roms.

joemm said:
I am assumng that you flashed CWM Recovery 3.0.0.x (orange) to install Gingervillian in the first place, right? Well in order to flash a Froyo version rom you need to flash the CWM Recovery 2.5.1.3 (green) back onto your phone prior to trying to flash a Froyo (2.2) based rom.
Click to expand...
Click to collapse
yes i did flash cwm(orange)..i also revert back to green (2.5.1.3), but where do i get the froyo rom?..i did get 1 from modaco but it wont work..i am now in the CWM Recovery 2.5.1.3 (green), but every rom i install stuck on the htc boot screen..

rottenapples said:
yes i did flash cwm(orange)..i also revert back to green (2.5.1.3), but where do i get the froyo rom?..i did get 1 from modaco but it wont work..i am now in the CWM Recovery 2.5.1.3 (green), but every rom i install stuck on the htc boot screen..
Click to expand...
Click to collapse
What particular ROM's have you tried? Are any of them still on your sd card?

i tried 'Z ROM v2.0' and 'modaco r2 rom' and yes still in my sd

Have you been clearing the data and cache partitions after flashing new roms?
Sent from my T-Mobile G2 running Cyanogenmod.

rottenapples said:
i tried 'Z ROM v2.0' and 'modaco r2 rom' and yes still in my sd
Click to expand...
Click to collapse
I'm unfamiliar with those ROMs but if they aren't built for the Desire Z and/or TMobile G2, then that is your problem. The best place to get your ROMs is in the Development thread here:
http://forum.xda-developers.com/forumdisplay.php?f=758
If the ROM you have is specifically built for your phone and is on the sd card then:
1 boot into recovery
2 wipe data/factory reset
3 (still in recovery) advanced>wipe davlik cache
4 (still in recovery) mounts and storage>format boot & format system
5 flash the zip from the sd card
6 reboot system (you may need to reboot a second time on some ROMs for everything to work correctly)

thanks man
Thanks man
edkeys said:
i'm unfamiliar with those roms but if they aren't built for the desire z and/or tmobile g2, then that is your problem. The best place to get your roms is in the development thread here:
http://forum.xda-developers.com/forumdisplay.php?f=758
if the rom you have is specifically built for your phone and is on the sd card then:
1 boot into recovery
2 wipe data/factory reset
3 (still in recovery) advanced>wipe davlik cache
4 (still in recovery) mounts and storage>format boot & format system
5 flash the zip from the sd card
6 reboot system (you may need to reboot a second time on some roms for everything to work correctly)
Click to expand...
Click to collapse

is this a known issue? i myself am stuck with GV, nice rom but i want my swype back! lol, anyways will try the green cwm and see what happens

Try finding a stock g2 rom. After that download the zip. Go into recovery mode by pressing power and vol down. Make sure you have clockwork mod recovery. Not sure which version. Mine is orange. Wipe data and cache partition or something. Then install the zip. Should work. Hope I helped.
Sent from my HTC Vision using XDA App

[Q] Clockworkmod Recovery - Problems restoring backups

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!

[HELP] Bootloop sense roms... (Stock Table)

I recently moved to CM7 and S-OFF. I used the alpha-rev method and flashed the CM7 hboot
Seeing the new Leedroid GB rom, I figured I'd give it a try. So I did a full backup, wiped everything, flashed the stock Hboot from Alpha-rev website, then flashed the Leedroid rom and... BOOTLOOP.
I then tried version 2.4, and same thing.
Following this I flashed Redux, which was nice but slow and I was able to confirm that I had 148 Mb of internal memory...
I then redownloaded Leedroid 3.0.5, thinking my file was perhaps corrupt, and still nothing...
I even tried restoring an my old CoolSenseHD 9 nandroid, which passed the splash screen, but looped at the boot screen.
Any ideas??

I had a similar problem. Go into CWM and format system, data and cache.

Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???

i think your recovery is outdated, this can cause bootloops, something to do with your recovery version not able to handle new updater-script.
so update your recovery, you dont have to remove current one, just get the fake-flash.zip of any new recovery (clockworkmod 3.0.2.7) put it on ur sdcard, then in AmonRa select to flash the fake-flash.zip file and it should boot up CWM. then wipe all and flash the ROM.
other than that make sure you have correct partiton layout on ur sd (ext needed ofc) and obviously, correct hboot table.

I tried flashing the latest CWM, then wiping everything and flashing leedroid, but no luck. Then I tried putting AmonRA recovery back, and I tried once more, but still no luck. Then I tried flashing the latest Gingerbread MIUI, and that worked like a charm....
So that rules out my recovery being outdated, and I did flash the latest Radio, so that's good too... I really can't pinpoint the issue, but regardless, I'm really liking MIUI, so that's good I guess.
And as for partitioning, my SD card had a 500MB EXT3 partition for Leedroid, as specified on his page, and my partition table was set to Stock Bravo. I reflashed that Hboot about 4 times just to make sure...

TheSobadef said:
Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???
Click to expand...
Click to collapse
As I said, I had this exact problem and solved it by formatting system in CWM. I could flash certain Roms like redux but not leedroid.
AmonRA does not have an option to format system, just wipe which is different.

But even with CWM, I couldn't do it...

I'm guessing it's because the boot.img is too big in the leedroid GB rom, and you have corrupted blocks which limit the allowable size or something. I have that problem with my Desire with certain roms.. which really sucks. Maybe it's because we have Telus branded Desire's lol....

Well I don't believe the Telus Desire is branded (no telus bloatware like other phones, no logo or anything)... I mean I never had to make a gold card, and I haven't been on stock since december...
I just find it wierd that I used to be able to run Froyo leedroid (version 2.3d), but now that I try and flash 2.4 (also froyo) or 3.0 (GB) I have no luck

Have you tried using the RUU to get stock ROM, use Unrevoked and then get the LeeDroid version you wanted?

Are you trying to load htc sense roms on cw7 hboot? Of course it won't work, there is not enough space for the rom.

^If you read my posts, you would know that I have not been using the CM7 HBoot, but the stock Hboot, which is why I was able to load a stock rooted sense rom.
The thing is, I'm afraid to use and RUU because Telus didn't modify their roms in anyway, so carrier RUUs don't exist, yet the phone is locked to Telus... I haven't created a gold-card yet because I haven't had to, yet I feel as though an RUU can jeopardize all of this.

Custom ROM fails with infinite Android logo

I rooted my Desire yesterday and it worked fine (with the Superuser app showing up and all)
I have downloaded ClockworkMod recovery and that too works fine. I backed up my current factory ROM on it.
I downloaded the devnull.zip yesterday from
Code:
http ://download.oxygen.im/devnull.zip
and installed it on the phone and it is stuck in an infinite android logo loop.
What should I do ? The recovery *.zip file in ClockworkMod does not do anything ..

I am currently downloading a new ROM by Cyanogen CM 7.0.2
Let me see if it works .. =/

Okay .. So I erased the all user data and the old ROM works fine. It doesn't have the Sense UI so I am still going to install the Cyanogen ROM

I think this has to do with one of 2 things.
1. Your version of recovery. If you have ClockworkMod 2.5.0.7 then you will be able to flash most things fine. Later versions of some ROMS require different scripting in later versions of Clockworkmod like 3.0.0.5 but they will normally tell you in the instructions.
If that isn't the problem
2. Your EXT partition on your SD card is not correct or corrupt. Many of the newer sense ROMS built on the new HTC Desire test keys sense don't support EXT4 and you need to format your SD-ext as EXT3
If you are still having an issue and you are S-OFF. You most likely have will have flashed an alternate HBOOT. If that is the case, flash the stock HBOOT, then choose the option reboot bootloader in the fastboot screen.
Should get you back on track.

What is the problem with cm? The download speeds i am getting for the rom are inane. 83 MB is going to take forever @8kbps ..
Sent from my HTC Desire using XDA App

CWM recovery update

Hi.
I have an issue with my Desire bravo. I can't install Evervolv's KK 4.4.
A year ago I used unrevoked3 to root my phone. It installed CWM 2.5.0.7. I had tried many 4.2.2 ROMs and than decided to stick with MildWild.
Now I want to try KK4.4 but I simply can't install it. CWM always writes: Status 0. Installation arborted.
I tried to update CWM through ROM manager but it won't update it. It writes that current version is 5.0.2.0, however when I boot into Recovery I can see that I have the same CWM.
Can somebody help me please?
Thanks.

lakotamm said:
Hi.
I have an issue with my Desire bravo. I can't install Evervolv's KK 4.4.
A year ago I used unrevoked3 to root my phone. It installed CWM 2.5.0.7. I had tried many 4.2.2 ROMs and than decided to stick with MildWild.
Now I want to try KK4.4 but I simply can't install it. CWM always writes: Status 0. Installation arborted.
I tried to update CWM through ROM manager but it won't update it. It writes that current version is 5.0.2.0, however when I boot into Recovery I can see that I have the same CWM.
Can somebody help me please?
Thanks.
Click to expand...
Click to collapse
flash latest 4ext recovery, latest update changes were made to be compatible with kitkat.

jmcclue said:
flash latest 4ext recovery, latest update changes were made to be compatible with kitkat.
Click to expand...
Click to collapse
I tried to flash it without success. Than I went to Hboot and it wrote that I had S-ON (that's strange). So I used Revolutionary to S-OFF my phone. It flashed CWM 4.0.1.4 and waw - everything works!

lakotamm said:
I tried to flash it without success. Than I went to Hboot and it wrote that I have S-ON (that's strange). So I used Revolutionary to S-OFF my phone. It flashed CWM 4.0.1.4 and waw - everything works!
Click to expand...
Click to collapse
Lastly, uninstall ROM manager, it's bad for Desire. You don't need it.
As long as you only use CWM to install / wipe you'll be ok, do not use it to partition your sd card.
4EXT is generally a better recovery, and is also recommended for partitioning, you can install it using the 4EXT app or flash it through fastboot commands.
Now that you're S-OFF it's much more powerful (e.g. you can change hboot). You were wasting a lot of memory while S-ON with stock hboot and mildwild.

eddiehk6 said:
Lastly, uninstall ROM manager, it's bad for Desire. You don't need it.
As long as you only use CWM to install / wipe you'll be ok, do not use it to partition your sd card.
4EXT is generally a better recovery, and is also recommended for partitioning, you can install it using the 4EXT app or flash it through fastboot commands.
Now that you're S-OFF it's much more powerful (e.g. you can change hboot). You were wasting a lot of memory while S-ON with stock hboot and mildwild.
Click to expand...
Click to collapse
I have already flashed 4EXT.
What's the advantage of using custom hboots? I think that Evervolv's roms can be flashed only on stock hboot.
I have flashed Evervolv's nightly KK4.4. It seems to work OK (but I liked Jelly Bean's interface more).
Thank you guys.

lakotamm said:
I have already flashed 4EXT.
What's the advantage of using custom hboots? I think that Evervolv's roms can be flashed only on stock hboot.
I have flashed Evervolv's nightly KK4.4. It seems to work OK (but I liked Jelly Bean's interface more).
Thank you guys.
Click to expand...
Click to collapse
custom hboots simply allow for more space, one of the primary reasons for gaining s-off and rooting in the first place
a custom hboot generally has a smaller /system and /cache and therefore more /data (internal memory)
depending on which mildwild rom, you only filled 100 to 130MB of the 250MB /system partition on stock hboot, which wastes max ~150MB. You could have used cm7r2 hboot or similar to nearly double the /data partition and hence more space for apps.
You're right though, now beside the point for ROMs like Evervolv which require stock hboot....