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.
Related
I wanna upgrade to official gingerbread so i can flach ICS but every time i try it and with any official GB it gives me an update failed.Is there any other way to get ICS to work???maybe flashing .35 kernel and then ICS on the same time???
As far as I know, there's no other way than through the stock ROM. Please try with a freshly formatted SD card that you know works otherwise, and make sure the downloaded/extracted file itself itsn't corrupt.
Did you change any of the partitions sizes?
If so reverting to the original may fix your problem upgrading.
I have run into the same problem and managed to brick my phone.
Been spending hours trying to fix it now. Unfortunately I get the same error with 2.2.
Try this: Put the battery out and connect it to USB charger. I had this problem also.
no luck
Schrauff said:
Try this: Put the battery out and connect it to USB charger. I had this problem also.
Click to expand...
Click to collapse
Already tried it could it be because i am trying to upgrade from 2.2.1 and not from 2.2.2 ?
Skace13 said:
Already tried it could it be because i am trying to upgrade from 2.2.1 and not from 2.2.2 ?
Click to expand...
Click to collapse
I updated from 2.2.1. My only issue was that i had to manually delete DATA every time i booted.
if not i got a bootloop. i only updated to get the Aurora rom so i was cool with it tho
I am getting the same issue with my handset. Attempting to flash stock 2.3 ROM using CWM 4. I am attempting to update my CWM version, but it is not allowing me to replace the recovery.img.
Any help appreciated
adamkerrnz said:
I am getting the same issue with my handset. Attempting to flash stock 2.3 ROM using CWM 4. I am attempting to update my CWM version, but it is not allowing me to replace the recovery.img.
Any help appreciated
Click to expand...
Click to collapse
You can't flash stock ROMs through CWM. You have to put the "dload" folder from the update in the root of your memory card, then hold volume +, volume -, and the power button down together with the phone turned off. This will start the "official" update process. To save yourself the trouble of rooting your phone after upgrading to stock, flash the B518 update. You'll have to reflash a newer CWM after this; either 5.0.2.7 or 5.5.2.4.
Triflot said:
You can't flash stock ROMs through CWM. You have to put the "dload" folder from the update in the root of your memory card, then hold volume +, volume -, and the power button down together with the phone turned off. This will start the "official" update process. To save yourself the trouble of rooting your phone after upgrading to stock, flash the B518 update. You'll have to reflash a newer CWM after this; either 5.0.2.7 or 5.5.2.4.
Click to expand...
Click to collapse
Correct, Sir...and if I may add something.
Try updating the ROM from the internal SD card (remove the external card).....That is if the update still fails with the other instructions given before...
There is always the chance to have a corrupted update.app.
Try to download again the file and use a fresh FAT32 formatted sd card.
Hope that helps
I got it to work.. sorta.
Reformat internal SD card to vanilla partitions -> install 2.2 -> 2.35 -> MIUI v4 elite SX.
2.35 failed to boot so I had to install a custom ROM, which did boot. Now it's running fine with latest MIUI rom.
Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.
lowsum said:
Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.
Click to expand...
Click to collapse
Sounds like you have data leftover (either not a good enough wipe, or corrupted data)
Try this. Note that this will reformat your entire internal memory, but will ensure all remaining data is cleaned up and removed.
Before installing your rom;
1. Wipe User Data
2. Wipe Cache
3. Wipe DalviK
4. Wipe Battery Stats
go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This WILL format your entire internal memory, so if you have something important, you need to copy it out. Note that this should not effect things on the Ext SD Card.
Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!
lowsum said:
Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!
Click to expand...
Click to collapse
Well, more than likely it is indeed a bootloader issue. But you must understand, all these "leaked" ICS roms are what they are... BETA. And with each new leak, there's a different bootloader. So you have to pay attention to the instructions for the specific leak. Usually involves flashing a newer or older bootloader to match the rom.
Until Acer releases an "official" ICS Rom and source code for the 500/501, these issues are going to be around for awhile.
My choice, would be to run a 3.2.1 rom. Very few issues with some of the mildly modded ones. Then wait awhile, till the official ICS updates come out.
One good thing out of this, you learned some tricks on how to recovery from some "semi-bricks"
I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!
lowsum said:
I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!
Click to expand...
Click to collapse
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.
Moscow Desire said:
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.
Click to expand...
Click to collapse
It is possible to rebuild your partition structure from scratch (using SBK + bootloader + nvflash create command + bct + flash.cfg + system image + recovery image + boot image + probably some other things) but I'm not sure of anyone that has done this and I can't say I have myself. Using timmydean's method (with a, what looks like, leaked Acer A500 Flash Tool) should, in theory, wipe it clean and start again.
I created a flash bundle to reset back to version EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 (it's on the forum I use which I got tempbanned for mentioning publicly ) but it's untested. I see no reason it shouldn't work, however.
I tried another way to restore my tab, this time flashing a leak based rom with RA recovery instead. This time i had a little different behavior, during flash process, formating flexrom froze for a while outputing this error: Random Offset : 0x188 ...the rest flashed normally. At first boot it froze after 2sec during bootanimation, before it froze at the black & white lines.
I think I may have a corrupted flexrom partition, so Im wondering, does the recovery*doing a quick format erasing only the first sectors? If so, is there any way to do a deep format?
Got ICS, OTA (download) installed that no problem, downloaded the acer usb drivers and used ICS Root (blackthund3r). Now i want to install LightSpeed 4.4 (i know theres a newer version) I renamed it update.zip and did the power button + V- button but it says invalid image.
Now im a bit confused cause all this android stuff is new to me, I have the acer recovery installed but im not sure what to do with it. Tried renaming it to recovery.img it says it is flashing but nothing happens.
Kinda lost at what to do or how to get this rom working.... if someone could point me in the right direction it would be sweet
Fox
foxorroxors said:
I renamed it update.zip and did the power button + V- button but it says invalid image.
Fox
Click to expand...
Click to collapse
Yep. That was pretty n00b of ya (that little trick only works on signed official roms, and even then, only ify-ify)
Check this thread. It has the tools you need.
http://forum.xda-developers.com/showthread.php?t=1622425
You can skip the part about installing an ICS rom and rooting. You already did that. You need to do steps 1, 2, (partial 4) 5 or 6 basically.
Note after you rooted. Look at step 4 and delete the required file like it says, before going to steps 5 or 6. You have an option on which package to use. Personally, I like the exe package. But your choice.
This installs patched b-loader and CWM recovery so you can flash ICS only Roms.
Easy
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.
urbie47 said:
As you've Acer Recovery why the difficult way ? Just choose "Download / Install Roms, tick Lightspeed 4.4 in the left column, hit download and then install.
(i've version 2.74)
Fast, easy and no problems. I flashed Flexreaper 14 (now replaced by Flexreaper ICS RF1) and i can recommend it, the Rom and the way of flashing it.
Click to expand...
Click to collapse
Acer recovery is fine if it'll install the patched Bootloader.
However, it doesn't make a user get his UID number, which is essential in case something happens in the future. Without your UID, you're basically toasted Or you're in for the long haul in figuring out how to unbrick a tab.
help
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
ores992 said:
I need help for boot loader.I tried to put ICS boot loader v3, I didn't success and now I can't put another rom(I have ICS for A500 but I use A501 and it doesn't work 3G modem).How I can put other rom?
Erasing cache before SD update...
SD update cmd recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed...
Click to expand...
Click to collapse
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).
Moscow Desire said:
You can't run that update.zip like you did. You got the error message.
Can you still boot into the 500 Rom? If so, you need to install a CWM Recovery before you can flash custom Roms. Look at the link below for instructions for CWM installation.
If you can't boot into your System, then you will need to do everything again.
You should still have your UID number when you tried to NVFlash the ver3 bootloader (I hope you wrote that number down)
You need to probably re-install the ver3 bootloader again as your attempt to install an update.zip messed things up. You just can't do it that way. So go here;
http://forum.xda-developers.com/show....php?t=1622425
Only this time, follow the instructions. You need to install CWM recovery. This is how to flash Roms, not putting update.zips on the SD card. And BTW, you should delete that update.zip from Your EXT SD Card. It will cause problems.
Also note, in those instructions, if you installed the FULL 500 ROM, you must delete a certain boot-p file before you install CWM Recovery. Or else it will delete it when you reboot the tab. Again, read the instructions.
The above steps install a 500 rom. The 500 DOES NOT have 3g like a 501. This is why you had no 3g. You have to install a 501 ICS Rom after, through CWM Recovery, and, currently, I have the only ICS Rom for the 501. And... it's a Beta release from Acer. But it works ok mostly.
Read the instructions, and understand exactly what you are doing. Also remember, with ver3 ICS Bootloader, YOU CANNOT INSTALL HC BASED ROMS without going back to an HC based bootloader. ICS Roms only. (unless you want to go back to stock).
Click to expand...
Click to collapse
Thanks, but that link is dead
ores992 said:
Thanks, but that link is dead
Click to expand...
Click to collapse
Yeah, XDA did some cleaning up overnight. Try it now;
http://forum.xda-developers.com/showthread.php?t=1622425
MD
Right basically if you've followed my last thread, http://forum.xda-developers.com/showthread.php?p=27975788#post27975788 it turns out I haven't got anywhere really. Today I managed to flash both froyo and GB but after trying to root both and install a custom ROM it would fail and I'd end up in a bootloop. Normally I'd just reinstall the dload files from the SD card and start again. Now however, when I go to boot the dload files, I get pink a screen (with usb plugged in I have the image folder with various files). When I try and boot recovery, nothing happens, I've tried replacing the recovery image, but no success. So now I'm left with a phone that does pretty much nothing other than bootloop or turn pink on command. Any suggestions on what I can do to install froyo or GB?
Sorry and thanks again.
Before root the rom(s) run ok?
And how you root the device? Also are you sure that the root have success? How you check it?
The root was fine, followed the instructions from the thread in dev section, ran the one click root everything was fine, swapped the recovery to get v5 used remount and astro explorer. went to CWM, made sure i had a rom that ran with the kernel, installed it everything said it was fine reboot into a loop. my options now are boot loop or pink screen, it wont even pick up the dload from the sd card.
So the bootloop happen with the custom rom you flashed from recovery mode?
Which rom you flashed? Did you wipe data/cache/dalvic_cache before the reboot?
Indeed I did. Something corrupted in the image folder. So I found a custom Image folder by the guy who's developed the v5.5 of CWM. In his signature theres a load of zip files one of them had a custom Image folder which Ive swapped in to which the phone has read the dload files now finally. Im hoping this will work.
If the device boots fine with the official roms, and bootloops with the custom, there is nothing wrong with the image file. The problem is with the rom that you try to flash and maybe with the recovery version.
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Dave759 said:
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Click to expand...
Click to collapse
The only cases I can think a custom ROM won't work are
- installing a .32 ROM over a ROM based on .35 and vice versa
- installing a custom ROM without wiping data and caches of the previous ROM, especially if they are not related, like not different builds of the same ROM
- installing a .32 ROM using cwm other than 5.0.2.6 and below
- installing a .35 or ics ROM using a cwm other than 5.5.0.4 or 5.0.2.7
Are you sure you did none of that?
Sent from my U8800
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.