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

Root Desire Gingerbread 3.14..405.1 | A2SD Base official HTC RUU |Android 2.3.3

M

mcp1999

Newbie
Has anybody tried this ROM?

[rom]Desire Gingerbread 3.14..405.1 | A2SD Base official HTC RUU |Android 2.3.3 - Page 3 - xda-developers

Despite following the instructions I can't get it to work.

I've tried 3 times and every time it installs fine and android 2.3 loads up and seems to work as it should. But when I reboot for the first time it gets stuck at splash screen. Clearing the cache and dalvik allows it to start once again but again a reboot and it sticks at start up.

Does anyone know why this might be?

Many thanks in advance.
 
SUroot said:
What sort of wipes did you do before installing?
Click to expand...

1) Wipe and factory reset
2) Wipe cache
3) Wipe dalvik cache

Is there any more?

I don't know if this affects anything but my phone was originally branded to Three but I successfully installed the generic stock ROM "RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32 U_4.08.00.09_release_137222_signed.exe" using a goldcard (which is still in the phone), which I then rooted using Unrevoked3.

Many thanks.
 
SUroot said:
No thats more than enough. Are you doing some kind of restore afterwards?
Click to expand...

Nope. I literally install the ROM, boot it up, skip through the set up stuff have a quick look to see it is working (open browser, camera etc. ) then restart it and it doesn't come back after the restart. Sometimes it keeps restarting at the first white HTC scree, other times it just hangs at the same screen.
 
The goldcard's purpose is to let you run an RUU other than your network's version. That's all. So while I'd never say never, I can't think why it should be, since a custom ROM doesn't care about the cid (the thing the goldcard hides).

Bad SD cards can cause problems, though I've not heard of this one. And it couldn't be the fat partition of the card, since the phone hasn't read that at the point it's hanging. Are you using an ext partition, and if so, do you know whether your dalvik cache has been moved to it?

You say that clearing cache and dalvik lets you boot. Have you tried clearing just cache, or just dalvik? Does it require both to be cleared, or if not, which one is important?
 
Hadron said:
The goldcard's purpose is to let you run an RUU other than your network's version. That's all. So while I'd never say never, I can't think why it should be, since a custom ROM doesn't care about the cid (the thing the goldcard hides).

Bad SD cards can cause problems, though I've not heard of this one. And it couldn't be the fat partition of the card, since the phone hasn't read that at the point it's hanging. Are you using an ext partition, and if so, do you know whether your dalvik cache has been moved to it?

You say that clearing cache and dalvik lets you boot. Have you tried clearing just cache, or just dalvik? Does it require both to be cleared, or if not, which one is important?
Click to expand...

Ah. Removing the SD card seems to resolve the problem. I havn't set up any ext partition or moved the dalvik cache so unless unRevoked does any of this I guess not.

Should I try formatting the SD card? Is there a way that might fix it without formatting the card?
 
Well, I'm surprised! Because if you've not created a partition, then the dalvik cache can't have been moved, in which case I'm not sure how clearing cache and dalvik would make a difference if it's a card problem, since neither was on the card. Guess it's a little more subtle than that.

If the card is the suspect, then formatting is safest option. Just copy everything you can onto your computer, including "hidden" files (whose names start with ".", such as ".android_secure"). If you get any errors when copying that might be a sign in itself.

If you have a disc repair utility you could try running that on the card and seeing whether it helps. But if not, a format is the next thing to try.

One final, silly idea: have you tried just cleaning contacts and replacing the card? I don't think it will help in this case, but then I didn't really think it was the card (or rather, not in this way).
 
Hadron said:
Well, I'm surprised! Because if you've not created a partition, then the dalvik cache can't have been moved, in which case I'm not sure how clearing cache and dalvik would make a difference if it's a card problem, since neither was on the card. Guess it's a little more subtle than that.

If the card is the suspect, then formatting is safest option. Just copy everything you can onto your computer, including "hidden" files (whose names start with ".", such as ".android_secure"). If you get any errors when copying that might be a sign in itself.

If you have a disc repair utility you could try running that on the card and seeing whether it helps. But if not, a format is the next thing to try.

One final, silly idea: have you tried just cleaning contacts and replacing the card? I don't think it will help in this case, but then I didn't really think it was the card (or rather, not in this way).
Click to expand...

I'm confused.

Firstly it was clearing the dalvik that was needed on each restart. It would not start after clearing the cache alone.

Secondly, formatting the memory card has not fixed it. I still need to clear the dalvik on every reboot if the SD card is in it.

Is this something to do with the ROM looking for a partition that is not there? A2SD? I do not need A2SD but think it is included in the ROM in some way.

Many thanks for your time.
 
Have a look in the Rom zip file for the a2sd script and remove it. Then reflash. Open it with.winrar (not extract) and navigate to /system/etc:init.d. this is where all boot scripts are kept. It should be obviously named. Delete it, flash and test-drive

The other thing to check is that sdcard/.android_secure is definitely empty. This has the apps that are moved to sd and could affect dalvik.
 
SUroot said:
Have a look in the Rom zip file for the a2sd script and remove it. Then reflash. Open it with.winrar (not extract) and navigate to /system/etc:init.d. this is where all boot scripts are kept. It should be obviously named. Delete it, flash and test-drive

The other thing to check is that sdcard/.android_secure is definitely empty. This has the apps that are moved to sd and could affect dalvik.
Click to expand...

I'm off for a few days and won't have time to try this yet. I'll report back after I've tried.

Thanks again for your help.
 
i have 2 problems with this ROM:
-my windows doesn't recognize my phone-when i connect the usb cable absolutely nothing happens , after a few minutes the red light appears like its charging and nothing more.
I tried to copy the files from program files\htc drivers to windows\system32 like someone told me with no change.
uninstalled htc sync and installed again
-bluetooth doesn't work
i am very new to this so if anyone can help me will be perfect
thank you
 
csbid said:
i have 2 problems with this ROM:
-my windows doesn't recognize my phone-when i connect the usb cable absolutely nothing happens , after a few minutes the red light appears like its charging and nothing more.
I tried to copy the files from program files\htc drivers to windows\system32 like someone told me with no change.
uninstalled htc sync and installed again
-bluetooth doesn't work
i am very new to this so if anyone can help me will be perfect
thank you
Click to expand...

is the phone able to access sdcard via a file explorer like es file explorer
 
Rastaman-FB said:
is the phone able to access sdcard via a file explorer like es file explorer
Click to expand...

yes , it can access the sdcard via a file explorer and i also have access to the sdcard when i put it in a card reader.
i tried to connect the phone to my pc with another usb cable , still no luck
the same with another computer
 
csbid said:
yes , it can access the sdcard via a file explorer and i also have access to the sdcard when i put it in a card reader.
i tried to connect the phone to my pc with another usb cable , still no luck
the same with another computer
Click to expand...

the reason i asked this is because you could have a usb brick
if it is not recognising that its connected even when you connect as mass storage then something is wrong as mass storage drivers are built into windows
if you boot to recovery and mount usb storage does windows see it?
 
Rastaman-FB said:
the reason i asked this is because you could have a usb brick
if it is not recognising that its connected even when you connect as mass storage then something is wrong as mass storage drivers are built into windows
if you boot to recovery and mount usb storage does windows see it?
Click to expand...

hi,
seems like i'm now having another problem , i tried to boot to recovery and i got a black screen with a red triangle
it says:
E:Can't open /cache/recovery/command

thank you Rastaman for your replyes
sorry for my bad english , i'm from spain
 
csbid said:
hi,
seems like i'm now having another problem , i tried to boot to recovery and i got a black screen with a red triangle
it says:
E:Can't open /cache/recovery/command

thank you Rastaman for your replyes
sorry for my bad english , i'm from spain
Click to expand...
you are not rooted with unrevoked
did you flasdh the new GingerBread WWE RUU?
this is not the RUU this is a custom rooted rom based on the RUU
 
Rastaman-FB said:
you are not rooted with unrevoked
did you flasdh the new GingerBread WWE RUU?
this is not the RUU this is a custom rooted rom based on the RUU
Click to expand...

i was rooted with unrevoked but now i lost root when flashing this rom
the rom i extracted from the RUU_HTC DESIRE ANDROID 2.3 UPGRADE that i downloaded from HTC Developer Center.
i extracted the rom because running the .exe file didn't work
i put the rom in the sdcard , booted the phone in HBOOT and let it do its thing
this is what i get under software information:
android version -2.3.3
baseband version - 32.56.00.32U_5.17.05.23
kernel version - 2.6.35.10-g3f43272
htc-kernel@and18-2 #1
tue jun 14 21:11:23 cst 2011
build number - 3.14.405.1 CL96875 release-keys
software number- 3.14.405.1
browser version webkit/533.1
thinking of an usb brick i found this
Fix USB Brick No Root - xda-developers - what do you think of this , will this work ?
 
Were you s-off? You have unrooted your phone with the official ROM. Again, this thread is about a custom rootred rom. In what way did your .exe not work?
 
SUroot said:
Were you s-off? You have unrooted your phone with the official ROM. Again, this thread is about a custom rootred rom. In what way did your .exe not work?
Click to expand...

hi ,
sorry if i posted in wrong place , i am new to android forums
about s-off i don't think i was and wheen i run that exe file nothing happnes(i waited a very long time)
again , sorry if my posts are in a wrong place and i hope you guys will help me solve this
thanks
 
csbid said:
hi ,
sorry if i posted in wrong place , i am new to android forums
about s-off i don't think i was and wheen i run that exe file nothing happnes(i waited a very long time)
again , sorry if my posts are in a wrong place and i hope you guys will help me solve this
thanks
Click to expand...
your problem isnt related to this rom as this is a rooted rom

what you did is get the GB WWE RUU and pull the rom.zip from it and flashed it as PB99img.zip

what you have effectively done is completely removed root so now you have stock htc recovery, you have the 1.02 bootloader and no way to currently root your device.

if you also have usb connectivity issues where it doesnt give an option for mass storage then try wiping the device and if that still doesnt work you will have to return it to htc for warranty as you have flashed official firmware
 
Rastaman-FB said:
your problem isnt related to this rom as this is a rooted rom

what you did is get the GB WWE RUU and pull the rom.zip from it and flashed it as PB99img.zip

what you have effectively done is completely removed root so now you have stock htc recovery, you have the 1.02 bootloader and no way to currently root your device.

if you also have usb connectivity issues where it doesnt give an option for mass storage then try wiping the device and if that still doesnt work you will have to return it to htc for warranty as you have flashed official firmware
Click to expand...

thanks for your help Rastaman , i did not manage to solve this at this time , tried to wipe the device and no luck
i'll get back to you when i find a solution for this
 
You must log in or register to reply here.
Back
Top Bottom