Root CWM Recovery Boot Loop

[Ani01]

I rooted my desire s with s-on hboot 2.00.0002 after unlocking by htc dev installing cwm recovery v5.0.2.0.after that i installed a custom rom b4 dat i did a nandroid backup of my system.now when i try to restore that nandroid back up the restore is done but my ds boots only in recovery i.e sort of recovery boot loop.now i am unable to get back to my custom rom.things have become complicated for me...
the funny thing is that i also made a nandroid backup of the custom rom and when i restore this backup my phone boots normaly without any problem.
tell me how can i get back to my stock rom....

 

[FoX777]

Can't much help, but I think your backup may be corrupted.

I assume you want to restore the ROM so you'll still have all your app's right? if that's the case then maybe someone else help you.

on second thought, did you flash the boot.img of the ROM you flashed? if you did you may have to flash the boot.img of the stock ROM.

 

[Ani01]

@FoX777 yes i flashed boot.img of the custom rom.
i also tried flasing the boot.img from the nandroid backup after the restore but no luck.
tell me 1 thing i downloaded the ruu file(RUU_Saga_hTC_Asia_India_1.47.720.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199605_signed)
and got the zip file from temp folder so should i flash this zip file in recovery or something bad will happen if i flash??

 

[notebook]

Worth a try. Rename the 'ROM.zip' (that was extracted from the RUU.exe) to PB88IMG.zip, then flash it from the SD card via HBoot. If successful, you'll wipe whatever's on the phone with the new image.

 

[FoX777]

If what notebook said doesn't work try flash just the boot.img of the RUU after you restore your back up.

If that fails then try the following;

Make a full wipe (system, data, cache, dalvik cache, boot) from recovery. Then run your backup. then boot into fastboot run the command to flash the boot.img

 

[FoX777]

Okay after some reading..... There was the same case over at XDA (see here), basically the (assumption) problem is do to with the new lib (library) partition of hboot 2.00.0002.

Old hboot has the table;

/dev/block/mmcblk0p25 /system
/dev/block/mmcblk0p26 /data
/dev/block/mmcblk0p27 /cache
/dev/block/mmcblk0p28 /devlog

and the new one is;

/dev/block/mmcblk0p25 /system
/dev/block/mmcblk0p26 /data
/dev/block/mmcblk0p27 /cache
/dev/block/mmcblk0p28 /system/lib
/dev/block/mmcblk0p30 /devlog

The new lib partition is required for sense 3.0, thus the reason why your backup didn't work (the lib is not backed up currently, though the 4ext developer is working on it).

It was suggested to try flash the PG88IMG.zip from this thread (it has a leaked lib img) but it wasn't attempted so I don't know if it will work.

If you do attempted it do it this way; restore your backup, then place the PG88IMG.zip on your SDCARD and try flash it in your hboot.

The only other alternative is to restore your phone with a RUU.

 

[InfernalByte]

Worth a try. Rename the 'ROM.zip' (that was extracted from the RUU.exe) to PB99IMG.zip, then flash it from the SD card via HBoot. If successful, you'll wipe whatever's on the phone with the new image.

YOU DO NOT FLASH A PB99IMG!!!!!!!

Put the PB99IMG in the root directory of your Sd card and boot into hBoot, when asked if you want to install the update select yes.

 

[FoX777]

YOU DO NOT FLASH A PB99IMG!!!!!!!

Put the PB99IMG in the root directory of your Sd card and boot into hBoot, when asked if you want to install the update select yes.

I think that's that notebook means the bootloader, cause if say's via hboot.

Also.... but the PB99IMG is for the desire and PB88IMG is for the desire s.

Not sure if it will make a difference though.

 

[InfernalByte]

Yes.

Yes PB99 and PB88 will make a difference, I used to have a rooted Desire and old habits die hard I'm afraid.

 

[notebook]

I've changed the file name. (Typo!) Thanks for the heads up!