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.
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.
Whenever I flash TWRP with the AIO Toolkit from Hasoon2000, TWRP recovery will load, but the internal SD (/data/media) is blank. The files are there when it boots to the system, but they're not showing up in TWRP. CWM won't boot at all when flashed (it just goes to back to fastboot). I tried flashing the generic TWRP in the AIO Toolkit and the Sprint version, both seem to behave the same. Also if I try to flash a ROM, it always fails (CM fails immediately, Viper installs then says failed, InsertCoin says it succeeded, but then it never boots). I tried flashing TWRP 2.7.1.0 as downloaded from the TWRP website and it won't flash ("BootMagic failed" error). And GooManager doesn't find the right file to flash for my M8. Does anyone know how to fix this? I like the stock ROM alright, but I want to try some others. Oh, also when I try to do a backup it fails, saying it can't mount /data/media.
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
EDIT (FIXED)
WHAT WENT WRONG...
1. Was using CWM (When i was last active in android flashing, twrp was just another custom recovery, cwm was needed for cm)
2. When i did use TWRP, it was an older version, and did not work (did not even boot to recover, in fact)
3. When i did get twrp working, i used a bad cm.zip file (corrupted)
nishant_713 said:
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
Click to expand...
Click to collapse
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
bloodhound42 said:
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
Click to expand...
Click to collapse
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
nishant_713 said:
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
Click to expand...
Click to collapse
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
bloodhound42 said:
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
Click to expand...
Click to collapse
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Update -- Ok flashed 2.8.6.0 and now boots to revovery (even after a restart) but still can't flash cm. Something pops on screen for a fraction of screen and then recovery reboots. It says "no md5 file found". Any chance of zip being corrupt ?
Update 2 -- Now my internal memory has stopped working :/ can't even take a screenshot, nor a photo. says memory full. Doesn't even copy file to memory when connected to pc. Although in recovery mode (twrp) , with usb mounted, it does copy.
nishant_713 said:
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Click to expand...
Click to collapse
weird did u flash normal recovery or gpe recovery ? U have to flash normal recovery and one more thing are u sure that its going into cwm recovery ?
May be the ROM is corrupted buddy download again and flash or try other Roms
Haha. After a hell lot of effort, i did get TWRP installed, and after breaking my head on why cm nightly won't install, i downloaded another one, and it installed fine. Now rocking CM 12.1 (4th device which I'm using on CM, and yet never had so much trouble getting it running..)
Droid Turbo (quark) is the device in question...
So over the weekend I attempted to boot into TWRP recovery and TWRP ended up in a bootloop. Never had this happen before (version 3.1.1-0 is installed). Attempted to reinstall version using Flashify, however Flashify hung up and stalled when I'd click on "search for file to flash" or whatever it's called. So I (successfully) flashed TWRP version 3.2.1-0 using the TWRP app, rebooted to recovery, and TWRP still bootlooped (showed that version 3.2.1-0 was installed). Using TWRP app I (successfully) reflashed the 3.1.1-0 version .img file I had saved from the first time I flashed TWRP months ago, rebooted to recovery, and TWRP still bootlooped (showed that version was again 3.1.1-0).
I'm fairly certain that some rogue apps I installed caused the issue. It's the only thing I can think of as to why TWRP is messed up. I've uninstalled the rogue apps with Titanium Backup, TWRP still bootloops.
Any ideas on what I've botched, and how to unbotch it? Phone otherwise works as it should booting up normally, running normally, etc. I'm just at a loss for any future tinkering I want to do since I can't get into TWRP to make or restore backups.