Hi,
I got my Huawei U8150 two days ago and I rooted it with z4root . Then I wanted to backup the original ROM before removing some stock apps.
So I installed ROM Mgr 2.5.1.2 and flashed the ClockworkMod recovery 2.5.0.1. When I tried to backup my current ROM, I rebooted to a black screen .
Eventually I found the 1.8.1.4 recovery image should be used in another forum .
Question => How to reflash 2.5.0.1 with 1.8.1.4? I tried in ROM Mgr but got an error.
Many thanks in advance.
Same Problem
Did you find any solution. I also flashed clockworkmod version 2.5.0.7 using Huawei pulse mini option. ROM Manager v3.0.0.7
Now when I go to recovery mode my phone has black screen. No recovery screen.
Please respond how to get my stock recovery back
Flash a stock Ideos Rom. Its recovery will replace yours
Sent from my DJDroid Ideos v0.4 using XDA App
Dear eidolon88.
Thanks for your prompt response. You people are really great. I have found stock ROM on xdadevelopers wiki website.
http://forum.xda-developers.com/wiki/index.php?title=Huawei_U8150_IDEOS#Official_ROMs
Is this right?
And can you recommend the guide for flashing ROM. Because I don't have access to Recovery menu.
OK. I'm stuck too. I just installed RomManager v3.0.0.9 with ClockWorkMod v2.5.0.7 for Pulse Mini. Now I cannot boot into recovery. Recovery boot just shows a T-Mobile Logo. Actually, I was making a mistake here and booting into the bootloader. When I booted correctly into recovery I got a black screen. I receive an error when I try to install anything under All CWM Recoveries. So far the phone still boots normally.
If I could locate a working CWM version then I could use the following hack to force install it.
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
Anyone know of a working ClockWorkMod version for the U8150?
Update:
I found a fix by installing the modified Koush's Clockwork Recovery 1.8.1.4 for Pulse Mini via Linux Terminal and ADB here:
http://android.modaco.com/content/t...lling-a-custom-recovery-image-on-your-device/
Now I can boot from RomManager v3.0.0.9 into ClockWorkMod v1.8.1.4 or boot into recovery via 'vol up + green send + power' even though RomManager says CWM is v2.5.0.7.
Update:
Using the setup in the previous update I was able to successfully backup the current ROM with apps and data to SD using RomManager v3.0.0.9 and ClockWorkMod 1.8.1.4.
Related
hey i rooted my nexus s and installed clockworkmod 3.0.0.0
i have installed rommanager 3.0.0.2
when i open the rommanager it says that there is a update to version 3.0.0.5
i tap on install after a wile it says that is installed correct
BUT
when i boot into recovery ... it dont work ... i boot the nexus s again an step back to clockwork 3.0.0.0 an i can boot to the recovery ...
so what is wrong?????
thx
footballpics.info said:
hey i rooted my nexus s and installed clockworkmod 3.0.0.0
i have installed rommanager 3.0.0.2
when i open the rommanager it says that there is a update to version 3.0.0.5
i tap on install after a wile it says that is installed correct
BUT
when i boot into recovery ... it dont work ... i boot the nexus s again an step back to clockwork 3.0.0.0 an i can boot to the recovery ...
so what is wrong?????
thx
Click to expand...
Click to collapse
you may just have to install CWM manually like you first did
ok ok ... i will do that ... thx for the hint
BUT
what for is the updatefunction in the rommanager then if it is not working???
slowz3r said:
you may just have to install CWM manually like you first did
Click to expand...
Click to collapse
You could probably flash it from fastboot, but the OP is correct, the 3.0.0.5 update "breaks" ROM Mgr and CWM.
With 3.0.0.0 you can open ROM Mgr, then select Reboot To Recovery, and the phone will quickly reboot into CWM recovery.
Upgrade to 3.0.0.5 and when you select Reboot To Recovery, the phone gets stuck on the white Google on black background screen. A battery pull is required.
Downgrade to 3.0.0.0 and the expected behavior returns.
Seems to be a bug to me with 3.0.0.5. Need to let koush know.
To the original poster, you're aware that if you're on Android 2.3.1 that any fresh normal boot of the phone restores the stock recovery to the device unless you remove/rename the appropriate script in the /etc folder, right?
i have Android 2.3.1
which file i have to remove/reneame in dhe "/etc" folder?
is this different to the way to update the clockwork as on the HTC Desire?
thx
footballpics.info said:
i have Android 2.3.1
which file i have to remove/reneame in dhe "/etc" folder?
is this different to the way to update the clockwork as on the HTC Desire?
thx
Click to expand...
Click to collapse
/etc/install-recovery.sh
Be aware there are some who think it's risky. I'd advise reading this thread before proceeding, at least the last few pages of it.
I'd also be leary of messing with the recovery until you're sure you're able to get into at least CWM to make fixes if needed (e.g., have CWM 3.0.0.0 working).
Also, I just went to the Market, found Rom Manager (Premium) and scrolled down to the email the author link and sent a bug report. I'm not encouraging spamming him with complaints, but those anxious for a fix might want to report the bug as well if they have it.
i installed Clockwork again from: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (Nexus S 3.0.0.5)
an installed it manualy with: fastboot flash recovery recovery.img
after taht i loaded the recovery and it told me that i have 3.0.0.5
rommanager told me i have 3.0.0.0 and there is a update for me *g*
but when i tryed to reboot an go to the recovery again its not possible ... i got an error and had to hardboot - its possible to load android ...
so now ... whats the problem ... i downloaded the right CW and installed it like i did 1st. time ...
i read the link you gave me - found that:
Originally Posted by Luxferro
well in order to prevent your recovery from returning to stock, you need to use root explorer, or another method to rename the following file:
/etc/install-recovery.sh
rename it to something like install-recovery.sh.old
now when you phone boots, it won't be able to run that script to replace your recovery.
That's all there is to it. It's that simple. Root explorer is a file explorer with root access. When you browse to the file, click the button to enable read-write access in root explorer, and then long press on the filename and rename it.
...............................................
when i have 3.0.0.0 as recovery and i reboot and then reboot to recovery anything is working i kan go to the recovery menue - i have root rights and i can install what i want .. so what is set back with this "bootscript"?
for me everything sounds a little bit wierd ... i am sorry ...
thx
flo
My 3.0.0.5 recovery wasn't there as well. I reflashed it in Rom Manager, and then it worked.
Rom Manager had a problem on Droid 1, where you had to flash the recovery a couple times. I'm hoping that bug doesn't apply to Nexus S as well.
so now its not possible to boot into the recovery ... its 3.0.0.0 or 3.0.0.5 ...
ok i renamed this /etc/install-recovery.sh to /etc/install-recovery.sh.sav now the update seems to work ...
If I try to update Clockwork Recovery on my Nexus S to anything newer than 3.0.0 (using Rom Manager), the phone will not boot into recovery and stays in fastboot mode instead. However, if I reboot and flash back to 3.0.0 then recovery mode works fine. Not a big deal, just curious what the problem is that's preventing me from using the newer versions of Clockwork.
Thanks.
i had a similiar problem with rom manager, i reinstalled clockwork with fastboot on your computure, worked for me.then reinstalled rom manager. I am currently using clockworkmod 3.0.2.4.
Im trying to flash the Clockwork Recovery mod to my sidekick but every time I boot in recovery I keep getting the stock recovery screen. First of all I rooted my phone using the latest version of SuperOneclick Root. Once the phone was rooted I installed both root explorer and rom manager.
I downloaded the modified binary recovery file and replaced it in system/bin using Root Explorer. I used Rom manager to flash the CWM and it supposedly intalled it (it says version 4.0.0.2). I tried to reboot on recovery but it doesnt boot the CWM recovery screen. I the tried donwloading the CWM and placing the update.zip file in the root of my SD card. I then rebooted into recovery and selecte reintall packages and i get the following:
E: signature verification failed.. installation aborted?
Im guessing its the binary recovery file that's causing the problem but I've tried replacing the file again and it wont work. Anyway, does anyone have any idea whats going on and how I can successfully install the clockwork recovery mod??
Yes that would say that it isn't using the correct modded recovery binary. use my modded oneclickroot script to push the correct recovery and update, and it should work.
http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Currently that's normal. I've got the same thing on mine.
sly_fox said:
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Click to expand...
Click to collapse
Yes that CWM is a fake flash and doesn't actually replace your stock recovery so you would have to reinstall packages everytime, unless you flash bali kernel which has the red CWM that replaces the stock recovery when you boot into recovery mode
Sent from my SGH-T839 using XDA App
EDIT: sniped by ayoteddy.
That is normal, as that script uses the "fake flash" instead of having CWM built into the kernel.
A fake flash technique uses a modded recovery binary that doesn't check for signature verification, allowing us to boot into CWM from a stock looking recovery, even on a stock kernel.
In order to have recovery boot straight to CWM, you need to have it built into the kernel, which currently only exists on the Bali kernel (as there's no need to build it for another kernel).
I was installing revolver 4 rom and my restore wasn't working I was using titanium back up pro it was saying something bout su and to reboot and I did like a few times so I reinstall the rom and now I can't get out of recovery when I reboot it takes me right back I tried installing a new recovery and it still on this recovery the recovery am using is clockwork mod v5.5.0.4 I need help can some one help me
the thing about titanium backup does not matter you can just skip past it or hit cancle it works either way. the official CWM 5.xxx by Kouch is bugged and does not work. use team rouge's recovery it is also based on 5.xxx but it works.
baconspaceman said:
I was installing revolver 4 rom and my restore wasn't working I was using titanium back up pro it was saying something bout su and to reboot and I did like a few times so I reinstall the rom and now I can't get out of recovery when I reboot it takes me right back I tried installing a new recovery and it still on this recovery the recovery am using is clockwork mod v5.5.0.4 I need help can some one help me
Click to expand...
Click to collapse
You need to go here to solve your recovery boot loop problem.
http://forum.xda-developers.com/showthread.php?p=23256536
All,
I'm rooted and unlocked. The weirdest thing I'm experiencing is that in both the EZ Recovery and Rom Manager, when I select to reboot into recovery, I'm not booting into ClockworkMod. I'm booting into stock recovery I think. The only time it would boot into ClockwordMod is when I flash touch clockwork mod then it would boot into the correct recovery.
Do I need to flash the Touch ClockworkMod every time I want to boot into recovery? Thats annoying.
Please help.
Thanks!
If you boot into stock recovery by selecting reboot recovery then CWM is simply not installed. Are you selecting the correct option in ez recovery to install the recovery?
I'm good now. I was on stock, but was rooted and unlocked. Like I said, it would work if I flash the recovery, but if I reboot into recovery again without flashing it would go back to stock recovery.
Anyways, I've flashed to CleanRom 4.0 and tested rebooting into recovery and sure enough it went to the ClockworkMod Recovery. So looks like I"m good.
It will do that on stock rom unless a couple of files are modified I believe. Doesn't do it on custom roms.