Root HELP: Desire stuck on splash, cant flash roms

[325i]

Today, i did a full wipe and tried to flash the Leedroid 3.03 rom.

But it was stuck on the splash screen for over 20 mins so i decided to forget it and go back to Eddy's Rom. But i have tried that rom, neo's new rom and a modaco rom but all get stuck at splash screen.

Can somepne please help me?

 

[kewlbuddy]

which hboot/table are you on?

 

[325i]

S-off on stock sense hboot.

 

[325i]

I have tried to flash the modaco and teppic stock 2.2 rom and get the following error;

E: Cant chown/mod /system/xbin
(no such file or directory)
E:Failure at line 66
set_perm_recursive 0 2000 0755 0755 SYSTEM:Xbin

 

[kewlbuddy]

stock and sense hboots are different

 

[325i]

I meant the bravo stock 250mb system hboot.

 

[325i]

Update: i can still the redux rom. Other roms just freeze on the splash screen,

Seems very strange?

 

[325i]

Anyone??

Is there anyway to find out what the phone is doing when stuck on the splash screen?

thanks

 

[anoniemouse]

I am using the new rom from neophyte
AuraxTremeGinger & it does sit on the flash screen for quite a while before booting up

 

[SUroot]

I have tried to flash the modaco and teppic stock 2.2 rom and get the following error;

E: Cant chown/mod /system/xbin
(no such file or directory)
E:Failure at line 66
set_perm_recursive 0 2000 0755 0755 SYSTEM:Xbin

Thats teh sort of thing I would expect to see if there wasn't enough space on system, but if you're definitely on stock 250 that shouldnt be the case.

If you know how to use adb, you can connect to PC after flash whilst still in recovery.

Then

adb shell
mount /system
ls /system

If it returns a folder in the list of folders called "lost+found" then you haven't enough space.

Since this cannot be the case if you have 250 system, perhaps you need to do a format on /system from recovery before flashing.

 

[325i]

Thats teh sort of thing I would expect to see if there wasn't enough space on system, but if you're definitely on stock 250 that shouldnt be the case.

If you know how to use adb, you can connect to PC after flash whilst still in recovery.

Then

adb shell
mount /system
ls /system

If it returns a folder in the list of folders called "lost+found" then you haven't enough space.

Since this cannot be the case if you have 250 system, perhaps you need to do a format on /system from recovery before flashing.

Thanks, really appreciated.

Ive installed redux for the time being so my phone is working.

Tomorrow, ill try leedroid 2.4.1 (froyo) and ill run the above adb commands. Ill post the results here.

How do i format the /system? Im doing a full wipe on recovery before installing any rom.

 

[325i]

I am using the new rom from neophyte
AuraxTremeGinger & it does sit on the flash screen for quite a while before booting up

How long exactly? Ive waited over 20 mins but no luck.

I also tried Eddy's superduper rom which i have been using lately and even this did not work.

 

[SUroot]

in clockwork, go into mounts and storage menu. You can format system there.

Also, in redux download quick system info just to confirm your system partition is definitely 250

But if there are corrupt files in system, maybe the rom cant over write them, attempt to co-exist and run out of space.

 

[325i]

in clockwork, go into mounts and storage menu. You can format system there.

Also, in redux download quick system info just to confirm your system partition is definitely 250

But if there are corrupt files in system, maybe the rom cant over write them, attempt to co-exist and run out of space.

Ill check using quick system info pro.

Also im using AmonRA, can i still format using this amon?

 

[325i]

in clockwork, go into mounts and storage menu. You can format system there.

Also, in redux download quick system info just to confirm your system partition is definitely 250

But if there are corrupt files in system, maybe the rom cant over write them, attempt to co-exist and run out of space.

Right, on quick system info pro, it does say system size is 250mb.

But on cache size, it says INFORMATION NOT AVAILABLE

Also on AmonRA, under mounts, i can only mount \system, there are no options to format it.

Thanks

 

[SUroot]

On redux my cache shows the same

 

[325i]

I get the following text when i do ADB shell whilst stuck on the splash screen;

link_image[1995]: failed to link /system/bin/sh
CANNOT LINK EXECUTABLE

Any ideas?

 

[SUroot]

Sounds like the file doesnt exist. Consistent with my thoughts about lack of space. Not sure on the cause though.

Shame you have amonra. Dont know my way around it sorry.

 

[325i]

Sounds like the file doesnt exist. Consistent with my thoughts about lack of space. Not sure on the cause though.

Shame you have amonra. Dont know my way around it sorry.

Have you got a link to the CWM i need? If so, i can get the phone working by installing redux and then changing recovery using android flasher.

Thanks mate

 

[SUroot]

http://db.tt/7PNHSE8

Yes you can flash using flasher from fastboot mode. You dont need to have a bootable rom for that

 

[325i]

http://db.tt/7PNHSE8

Yes you can flash using flasher from fastboot mode. You dont need to have a bootable rom for that

Mate, you are an absolute legend. Installed CWM, formatted system and its working.

Really apprecited, PM me your paypal address and ill send you some beer tokens.

 

[SUroot]

You have managed to flash roms you couldnt previously?

Although I have paypal, i do not accept payments for help

 

[325i]

You have managed to flash roms you couldnt previously?

Although I have paypal, i do not accept payments for help

yes its working, just flashed leedroid 2.4.1.

Looks like some system files got deleted or corupt whilst i was changing roms.

The only rom i cant install now or before was the new leedroid GB sense, its always stuck on splash screen.

I get the following whilst on splash,

ls /system
usr
sd
media
lib
framework
fonts
etc
customize
build.prop
app
bin
xbin
lost+found

 

[SUroot]

yes its working, just flashed leedroid 2.4.1.

Looks like some system files got deleted or corupt whilst i was changing roms.

The only rom i cant install now or before was the new leedroid GB sense, its always stuck on splash screen.

I get the following whilst on splash,

ls /system
usr
sd
media
lib
framework
fonts
etc
customize
build.prop
app
bin
xbin
lost+found

What happens is if you install for example a 300MB rom in a 200MB partition, install will be successfully, but there is not enough space so files that there is not enough space for go into "lost+found". If you see that folder like above, that is the cause.

Not sure how big the leedroid GB unpacks too (might be worth checking with someone who has it installed)

 

[ben0058]

i really need some help

I have this same problem tried to boot and just stayed on boot screen.
then i try another rom, and does the same thing....

I have tried lots of things... nothing has worked.

can anyone help me?