• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Pre-rooted Gingerbread (stock)

ManOfSteal said:
Yes, never had that with any other ROM. I've also tried a later CWM recovery in case it was an issue there, but that refused to work due to the usual script asserts issue. As mentioned, the MD5 matches, so it's not a corrupted ROM.
Are there no other similar stock-like GB rooted ROM I could try?
Click to expand...
yeah there are, its the one we recommend but there are others
check on the xda rom sticky. it should be there
 
I tried installing a few 'near-stock' Gingerbread ROMs on that XDA sticky before, but nothing that would actually boot. The only GB ROM that has so far was the popular LeeDroid, but I always got boot loops with that. Guess I'll have to wade through every ROM to find something that works for me...
 
what radio are you using?
im thinking you might have to bite the bullet and try ruu'ing the device to a newer hboot and see if things behave differently
 
indeed i remember that thread.
its odd and i think its something to do with bootloader which is part of the hboot. theres no way of changing this without s-off but you cannot get it.
i was thinking if you RUU to a froyo rom with a 0.93 bootloader then re root, you would probably have a better chance.
I can understand why you dont and we dont know what outcome this may have.
 
Well it's a way of doing it for sure, but as others have used Alpharev successfully with the same Hboot it seems doubtful that's the reason. I suspect it's down to my PC's handling of USB/hardware recognition, so I need to try on another PC to ascertain that.
 
ManOfSteal said:
Well it's a way of doing it for sure, but as others have used Alpharev successfully with the same Hboot it seems doubtful that's the reason. I suspect it's down to my PC's handling of USB/hardware recognition, so I need to try on another PC to ascertain that.
Click to expand...

aye try a different pc
just seems odd with this error too
 
SUroot said:
Good luck with that! Apalling recovery imho
Click to expand...
Isn't it just the usual CWM 2.5.1.8 with a few more options? I thought CWM prior to v3 were okay to use (by comparison)? Only glitch I found was when selecting the wipe dalvik cache option it, when it seems to fall asleep for a few seconds...
 
ManOfSteal said:
Isn't it just the usual CWM 2.5.1.8 with a few more options? I thought CWM prior to v3 were okay to use (by comparison)? Only glitch I found was when selecting the wipe dalvik cache option it, when it seems to fall asleep for a few seconds...
Click to expand...

nah, the only cwm that was ok was 2.5.0.7
all the rest were user mods made from CWM source and not by koush. nearly all of them had problems.
while that recovery is a bit bad, it generally wouldnt cause this issue.
I would imagine it was the hboot/bootloader and had some weird glitch

as for the dalvic wipe behaviour. thats common on all recoveries i think
 
ManOfSteal said:
Thanks, I guess RMD Recovery v1.0.3.4 is the best option these days, but all my existing Nandroid backups are from CWM, so I'll have to wait a while before changing.

BTW, this mod: [MOD] Trackpad press to unlock (and awake) Official HTC GB 3.14.405.1 - xda-developers doesn't appear to work with this ROM. Do you know of a trackpad press to unlock mod that does?
Click to expand...

nah dont use RMD, while it has lots of opttions SUroot found a bug that cannot be ignored and ive verified it.

the options are CWM 2.5.0.7 or amonRA 2.0.1
personally as you are already using CWM i would flash CWM 2.5.0.7
 
Thanks again, have flashed CWM 2.5.0.7 back on using Fastboot Commander. I also applied a custom splash screen, both reported as successful.

Note at the same time I then went into recovery to apply the zip for removal of the previously mentioned mod, which then resulted in a boot loop, so it's obviously a mod to avoid for this ROM :(

Grrr - just applied a Nandroid restore and still getting the boot loop, any ideas?
 
Try a factory reset and see if it boots after that?

Or reflash the ROM, which will remove any patches which were applied subsequently.
 
Have done a full wipe before Nandroid restore, the versions I can restore are not patched. I can only think there's a problem with the recovery_CWM_2.5.0.7.img I flashed, although no error appears while using it. At the moment all I can think of is to try and put the alpharev_cwm recovery back on, but I can't seem to find a download for it :(
 
What recovery did you make the nandroid with?

Try wiping after the restore and see whether it will boot. Wiping before a restore is irrelevant. If it boots after a wipe, then the ROM was OK and the problem was with the data.

If that doesn't work, just flash the ROM again. If it boots after that then at least we know the recovery works for ROM flashing and the ROM itself is OK.

You didn't change anything else after getting S-Off, such as flash a different HBOOT?
 
1. What recovery did you make the nandroid with?

CWM-Alpharev 2.5.1.8

> If that doesn't work, just flash the ROM again. If it boots after that then at least we know the recovery works for ROM flashing and the ROM itself is OK.

Have reflashed the ROM, it went into a boot loop just after entering Sense. Rather than installing the ROM afresh I'd prefer to restore the Nandroid if possible.

> You didn't change anything else after getting S-Off, such as flash a different HBOOT?[/QUOTE]

No, just changing the splash screen and reverted to CWM 2.5.0.7 recovery, as it was recommended above. I have (non-Alpharev) CWM 2.5.1.8. as a zip rather than an img, if I can't locate CWM-Alpharev 2.5.1.8.img then I guess I'll give that a go.

[Edit] Managed to restore Nandroid backup successfully with CWM 2.5.1.8.
 
ManOfSteal said:
1. What recovery did you make the nandroid with?

CWM-Alpharev 2.5.1.8

> If that doesn't work, just flash the ROM again. If it boots after that then at least we know the recovery works for ROM flashing and the ROM itself is OK.

Have reflashed the ROM, it went into a boot loop just after entering Sense. Rather than installing the ROM afresh I'd prefer to restore the Nandroid if possible.

> You didn't change anything else after getting S-Off, such as flash a different HBOOT?

No, just changing the splash screen and reverted to CWM 2.5.0.7 recovery, as it was recommended above. I have (non-Alpharev) CWM 2.5.1.8. as a zip rather than an img, if I can't locate CWM-Alpharev 2.5.1.8.img then I guess I'll give that a go.
Click to expand...

it will be in the iso of alpharev
ive extracted it for you and hopefully its the right one.
in fure BACKUP before you make any changes, remember that 2.5.0.7 is an older recovery to the 2.5.1.8.
this should take you back to 2.5.1.8 so you can restore properly
then flash 2.5.0.7 and backup the rom
 

Attachments

If your erase size is 20,000 you should go back to cwm 2.5.0.7 and make a new backup. If your erase is 40,000 you should go to amon-Ra 2.0.1 and make a backup. Essentially get away from 2.5.0.8. Imho it is the dodgiest of cwms
 
he must have erase size of 20k as he was originally on a 80 hboot
his current rom is dead however he has previous working backups created with alpharev cwm
hopefully by him flashing alpharev cwm hell get the backups resotred properly then he can flash the proper recovery and make a new backup of the working rom
 
You must log in or register to reply here.
Back
Top Bottom