I keep making matters worse and I need some help. Please.
I had a perfectly running stock U8800-51 / froyo
I changed the recovery.img per instructions in /cust_backup/image/recovery.img which, presumably, has provide CWM 5.5.0.4
1st; I made a bad backup to linux on my pc
Then; I installed a ROM (MIUI) that was probably destined for U8800 (not 51). Who knew there was such a thing
Then; I tried oxygen which doesn't work
Figuring that I would have more flexibility if I installed Gingerbread, I tried the following which fail to install:
U8800V100R001C00B526G001 (Normal Gingerbread).zip and;
U8800V100R001C00B528G001 (Universal)(Gingerbread).zip
I can boot into recovery.
I can boot to purple and mount the filesystems
I can an adb shell from recovery (it seems to be partial)
But that's ALL I can do!
Come on guys. I have helped so many people with Fedora over the years. Someone must be sufficiently proficient to help me out herez!
Related
I used CM7 for a while, but recently the device stopped booting it only shoes the honeybee icon and resarts.
I the following without success
1. wipe cache
2. factory reset data
3. used CM7 rom and MUIU rom to for update.zip but the update stopss with cache:recovery/log can't mount
Another trial was RSDLITE but the boot loader was shown once and later its shows Failed to initialize ....... failed to flash
the only way I feel would work is to use ADB method to replace the partitions, but need help to know how to do it (sdk and adb tools already installed), what files are required can the CM7 rom has all the img files
Please help in a simple step by step way.
oh that sounds like an interesting problem, such as mine
i never heard of a bootproblem even after wipe ... that's the problem of my defy as well ... look at my post here: http://forum.xda-developers.com/showthread.php?t=1522842
mabe, we have the same problem? would be nice to know, so we can move on together ...
nice greetz
EDIT: i even have a full dump of the unlocked chinese defy ... so if any partition is failed, we could overwrite it with the one of that defy ...
DJ_Synergy said:
oh that sounds like an interesting problem, such as mine
i never heard of a bootproblem even after wipe ... that's the problem of my defy as well ... look at my post here: http://forum.xda-developers.com/showthread.php?t=1522842
mabe, we have the same problem? would be nice to know, so we can move on together ...
nice greetz
EDIT: i even have a full dump of the unlocked chinese defy ... so if any partition is failed, we could overwrite it with the one of that defy ...
Click to expand...
Click to collapse
Thanks DJ_ sunergy
However, I unable to flash the SBF also as it fails in rsdlite. may I have the custom rom with mount recovery issue. How do you use adb to push the recovery img to the phone. I am not able to do that , i dont have these files either. help in reflashin the individual partitions. maybe this will help
i'm not able to do anything on my defy but flashing full-sbf ... cause i don't have any cwm at the defy at the moment, so i have no ability to get ADB-conection ...
so .. please ... leve it at this and do not flash any full-sbf, because it will overwrite cwm and you don't have any adb such as me
with adb ability we should be able to flash your / our defy with a working rom ... that just needs trial and error
EDIT:
ehhm .. let's talk over IRC:
irc.freenode.net
#motodefy
DJ_Synergy said:
i'm not able to do anything on my defy but flashing full-sbf ... cause i don't have any cwm at the defy at the moment, so i have no ability to get ADB-conection ...
so .. please ... leve it at this and do not flash any full-sbf, because it will overwrite cwm and you don't have any adb such as me
with adb ability we should be able to flash your / our defy with a working rom ... that just needs trial and error
EDIT:
ehhm .. let's talk over IRC:
irc.freenode.net
#motodefy
Click to expand...
Click to collapse
Thnks you gave me hope, i d have the CWM working which gives error on mount recovery. But It seems I am not aware on what you suggested as
"with adb ability we should be able to flash your / our defy with a working rom"
could you help me how to use adb and where can i get the necessary image files which mentioned in almost all solutions. confused ho to flash thse boot.img, recovery.img flash partitions etc
hope is allready there, because the defy is nearly unbrickable ... totally bricking the phone is quiet impossible (if you aren't Epsylon3 ) ...
I got the clue now, the recovery running on my defy is 3e and the CWM recovery has gone missing, thats is why is not allowing unsigned roms to even try to mount. If somehow I can get CWm or some other recovery manager to run. I might survice. did you DJ_synergy try this thourgh some tools. do let me know your experience too.
Somebody please help on this issue. How do i get the ADB , recovery image work on this device.
wtf? you didn't have CWM running n your Defy?
Thankfully RSD worked
The RSDlite took me back to stock by using JORDN sbf.
Now trying CWM wiki to get custom recovery installed and will try MUIU on this.
I have been upgrading a friend's Blade but I've run into trouble. I rooted the froyo firmware and flashed CWM. Now if I try to boot into recovery via "adb reboot recovery" it somewhat works but if I try to get into the recovery via Vol - + Power it doesn't. It just gets stuck at splash screen and won't bulge. But if I have flashed a stock recovery I can boot into FMT. This is not the end of it though.
I went on to flash CM9 KonstaKANG release but wanted to do a reflash after doing TPT conversion, the TPT part went fine but now I later realised that I can't get into CWM. So...I got stuck. I flashed a Gen 2 stock via Windows and flashed a TPT image.bin I found that contained a stock 2.3.5 firmware. Brilliant, life saved...no? Turns out I can't root it, so I can't flash a custom recovery to it and boot into it in order to flash CM9. So....I did a bunch of other stuff and at this point the blade has a CWM recovery which I can't boot into, empty system partition and pretty much a boned status. I thought I'll flash a stock 2.2 TPT which I found at: http://amphoras.co.uk/downloads/blade-tpts but the one with a ROM are in some other format than TPT and I can't figure out how to flash them. Can anyone help me here?
Install rom manager (available in google play as a freeware) then flash clockwork mod recovery.
Now u can enter recovery with just 1 tap ie "reboot into recovery"
NOTE USB debugging should be enabled at all times
Add on:
You can root ur phone using an app named z4root.
To permanently root it search google and click the android modaco link
Sent from my Blade using xda app-developers app
Dragooon123 said:
I have been upgrading a friend's Blade but I've run into trouble. I rooted the froyo firmware and flashed CWM. Now if I try to boot into recovery via "adb reboot recovery" it somewhat works but if I try to get into the recovery via Vol - + Power it doesn't. It just gets stuck at splash screen and won't bulge. But if I have flashed a stock recovery I can boot into FMT. This is not the end of it though.
I went on to flash CM9 KonstaKANG release but wanted to do a reflash after doing TPT conversion, the TPT part went fine but now I later realised that I can't get into CWM. So...I got stuck. I flashed a Gen 2 stock via Windows and flashed a TPT image.bin I found that contained a stock 2.3.5 firmware. Brilliant, life saved...no? Turns out I can't root it, so I can't flash a custom recovery to it and boot into it in order to flash CM9. So....I did a bunch of other stuff and at this point the blade has a CWM recovery which I can't boot into, empty system partition and pretty much a boned status. I thought I'll flash a stock 2.2 TPT which I found at: http://amphoras.co.uk/downloads/blade-tpts but the one with a ROM are in some other format than TPT and I can't figure out how to flash them. Can anyone help me here?
Click to expand...
Click to collapse
Heh, not only have you screwed up CWM, you also converted your phone into a GEN3 phone in the process (by flashing that 2.3.5 TPT).
Easiest way to fix it:
1, download: http://bit.ly/yUi4Nu (stock partition layout, if you want a 160MB system layout use: http://bit.ly/wEO8Im )
2. unpack it to your sdcard (/image/image.bin)
3. flash it like you would any TPT
You should have CWM installed at this point (just press and hold vol- during bootup) and now you can flash whatever ROM you want to.
I have just installed quarx' experimental 3.0 nightly on a defy+, which is working, but I can't access recovery any more. Entering recovery from the red screen by using the menu button causes the phone to restart. Resetting using stock recovery doesn't help.
Is there a way to replace the recovery from either adb, the terminal, or by using some app? Is it a matter of dd'ing an image from either update_recovery.zip or the rom over /dev/block/mmcblk1boot1 (or some other device)? If so which file - ramdisk-recovery from update_recovery looks promising.
Is there a better way to recover from a failed recovery? I did install update_recovery.zip, and reboot to it before flashing - I could have done something wrong there.
Of course, if this isn't possible, then there is always .sdf-ing it back to a stock and trying again.
Just replace the bootmenu folder in system with the one from the zip. Don't dd any images, because our custom kernel runs via kexec, not by regular booting
Sent from my Nexus 5 using Tapatalk
Thanks for that. I tried that, and found something interesting - the files at /system/bootmenu/2ndboot don't seem to be used - the firmware does not have a bootmenu folder - everything is in /system/bootstrap. I installed on this phone by flashing the sbf, rooting and installing 2ndInit, installing cm10, then update-recovery, then cm11, if it helps.
I am certainly loading the files in /system/bootstrap. I put '$BB_STATIC echo 64 > /sys/class/leds/[red,green,blue]/brightness' commands into bootstrap/scripts/recovery.sh, and the light cam on and changed color as it should, until it reached the line "./hbootuser ./hboot_recovery.cfg". It did not get past that.
Any assistance would be a help. As you can see, I like digging into things like this.
Edit: Fixed! I downloaded one of the other, older files, extracted the zImage and ramdisk-recovery, and put them into /system/bootstrap/2nd-boot as zImage-recovery and ramdisk-recovery. Then I edited hboot_recovery.cfg to make sure it was pointing at these files, and recovery now works.
Mind you, i might have just messed it up with flashing gapps......
Hi all technical gurus and experts
I have the standard u8800 X5 and have managed to recover it after two weeks after bricking it quite properly. The question I have is that I am unable to get the official GB update to install correctly over the stock Froyo Rom.
I had the phone running on the official GB for a number of years unmodified without problems until I rooted the phone for the first time.
In an attempt to fix it I managed to remove the OS completely (I know I know). I have finally managed to recover the phone by flashing the stock 2.2.2 B138 rom. Next I attempted to upgrade to to the official 2.3.5 B526 I downloaded from the huawei site. Every time after it installed it boot looped. Pull the battery out and put back then I do a factory reset from the recovery and the phone would work. At next restart it would have multiple error messages about processes unable to start and would reboot back into the boot loop.
Back to square one and re flash the froyo.
Eventually I flashed oxygen 2.3.7 over the froyo, which is stable.
I have root access and CWM 5.0.2.6 installed.
Please help as I would like to install a newer Rom like Aurora ICS or CM10, what do I need to do to get it right?
Thanks in advance.
Bump for @Blefish
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Thanks for answering. You are the foremost expert on the u8800 that I know of.
Blefish said:
Its difficult to understand why this is happening. However, if you installed 2.3, your baseband is updated and theoretically you should be able to switch the ROM, even though the stock ROM is crashing. Huawei ROM is loading some of the items from the "cust" partition, it might happen this does not have the necessary items but I doubt it.
Click to expand...
Click to collapse
If you mean amms.mbn it is not the thing which controls switching between roms.
OP should check partitions, I think all the problems are from them (and from appsboot.mbn too ).
Last time I bricked my phone, it refuses to install any roms (I was on B919 and was not able to install B919 :silly: ) except B939.
I have checked logs, located in /sdcard/dload, and found some "partition error", or "installing new partitions", etc.)
PS: Solved.
Cust partition is not a problem, I remember I cleaned it from my U8860 and everything was ok.
OP, try to install different mods and if nothing helps, ask someone to send you a dump.
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
missioner said:
What you said about the updated baseband gives me an idea. If I can install CWM 6 with es file manager, after updating to the GB. I can use your partioning tool and then install Aurora or CM10. Do you think that could work?
Click to expand...
Click to collapse
I am quite sure it could work. But I would suggest installing B518 or at least install pink screen unlock before you do repartitioning.
Thanks I will keep that in mind.
I will install ES explorer tomorrow and see about an updating the recovery
I checked the size of the internal sd card as Jeka suggested and total size is 1.4Gb. I remember that the internal SD card should be 2Gb if the partition is stock. I did run the Blefish recovery repartitioning zip before I so wonderfully bricked the phone, it is most likely the partition size that is causing the error.
I have the 3 partition zips downloaded including the stock partition one, so I will give it a go this weekend if my son agrees. It is his phone and he appears to be enjoying the oxygen rom currently installed. Ultimately I want an ICS rom installed though.
After much time I have solved the problem.
The phone has been running for some time on oxygen 2.3.7 GB, but sadly started having problems again. This time due to the dodgy games my son had installed on to the phone.
I flashed the official GB to update the baseband and then realised I had made a small mistake as I had also unrooted the phone and replaced the cwm recovery with a stock one.
Some hasty searching later and installing ES FILE MANAGER I managed to find and install a rooted recovery. I did this as my other root methods were unsuccessful.
This allowed for me to install the Team Win U8800 recovery. As per the previous post the phones partitions had not been restored to stock, so I installed the Aurora ICS Lite Rom.
Very happy with the results and I have to say that the TWRP recovery is top notch.
Hello.
Long time lurker, have been meaning to get rid of my 2.2 Android for years, and finally took the plunge yesterday(read as about 8 hours ago).
I read http://forum.xda-developers.com/ideos-x5/development/rom-unofficial-cyanogenmod-12-0-t2989575 (hey if you're going to install another version it might as well be the newest) and worked my way backwards.
I realized that i needed to
1)Install the official 2.3.5 version from Huawei to get 404020 baseband
2)Use SuperOneClick to root it.
3)Install Clockwork Mod recovery
4)Reclaim my Pink Screen by flashing B-518 bootloader
5)Replace CWM with TWRP Recovery which is LVM compatible
6)replace that with BlePart LVM
7)Install CyanogenMod 5
I managed to locate the 2.3.5 update after some searching and install it. I had some trouble getting SuperOneClick to root my phone, because of incorrectly installed drivers, but got through that.
Installed CWM and B518 bootloader and finally replaced CWM with TWRP. Took a backup on the SD of 2.3.5
I then tried to install BlePart and ever since the phone is stuck on the Huawei logo. I can reboot and get access to TWRP, and the Pink screen, giving me access to a 300MB filesystem which contains the cust_data folder.
Since I had access to TWRP i tried flashing CM but to no avail. I also tried to restore my 2.3.5 backup but also nothing. It seems to be going fine but then it will again freeze on the logo.
Please help me. I have spent over 8 hours on and off at this, and it's 5 am now!
Thank you.
EDIT:Thought I'd give it another try, so I uninstalled BlePart LVM and restored my 2.3.5 backup. It went smoothly except for the fact that it couldn't mount the eMMC partition. I'm now in 2.3.5 but I have no internal SD card space.
So I still need help getting up to 5 or 4.4 and mounting the internal SD partition.
hunk_gr said:
Hello.
Long time lurker, have been meaning to get rid of my 2.2 Android for years, and finally took the plunge yesterday(read as about 8 hours ago).
I read http://forum.xda-developers.com/ideos-x5/development/rom-unofficial-cyanogenmod-12-0-t2989575 (hey if you're going to install another version it might as well be the newest) and worked my way backwards.
I realized that i needed to
1)Install the official 2.3.5 version from Huawei to get 404020 baseband
2)Use SuperOneClick to root it.
3)Install Clockwork Mod recovery
4)Reclaim my Pink Screen by flashing B-518 bootloader
5)Replace CWM with TWRP Recovery which is LVM compatible
6)replace that with BlePart LVM
7)Install CyanogenMod 5
I managed to locate the 2.3.5 update after some searching and install it. I had some trouble getting SuperOneClick to root my phone, because of incorrectly installed drivers, but got through that.
Installed CWM and B518 bootloader and finally replaced CWM with TWRP. Took a backup on the SD of 2.3.5
I then tried to install BlePart and ever since the phone is stuck on the Huawei logo. I can reboot and get access to TWRP, and the Pink screen, giving me access to a 300MB filesystem which contains the cust_data folder.
Since I had access to TWRP i tried flashing CM but to no avail. I also tried to restore my 2.3.5 backup but also nothing. It seems to be going fine but then it will again freeze on the logo.
Please help me. I have spent over 8 hours on and off at this, and it's 5 am now!
Thank you.
EDIT:Thought I'd give it another try, so I uninstalled BlePart LVM and restored my 2.3.5 backup. It went smoothly except for the fact that it couldn't mount the eMMC partition. I'm now in 2.3.5 but I have no internal SD card space.
So I still need help getting up to 5 or 4.4 and mounting the internal SD partition.
Click to expand...
Click to collapse
Take a look at this post http://forum.xda-developers.com/showpost.php?p=57883272&postcount=59 that might be helpful.