Database Users

Noob needs help - Totally overloaded with info!

Greetings all.
Firstly, thanks for such a great repository of info. I have successfully managed to root my phone using Chainfire's method. I'm supremely happy to have even accomplished that.
I'm not a tech noob, but I'm quite new to Androids.
The feeling of frustration at trying to learn new terms and make sense out of all this information is HUGE. I have seen various "noob" entitled threads, as well as threads (Like ChainFire's) that make it somewhat easier. However, there seems to be so many threads to look through, and different info/terms that at this point trying to add a battery percentage mod to the status bar (which I'm sure is an easy easy thing to some of you) has become quite the gargantuan task for me.
---to that topic i'm having trouble understanding what it means when people say "flash using CWM". I understand "flash" (i think) and i know what CWM is, but have no idea what steps to take to "flash the necessary apk" files.
Do i use CWM? I've seen mention of using a root explorer or just adding the files overtop.
Then I've read "backup first". Yes, i know i want to do that. I have Titanium Backup on my device. And I've backed it up> but then i read that i should be using Nandroid. Where the hell do i get that? lolz. I mean I've searched for it and found threads, but from HTC section. Is it even compatible? No D/L links...
arrrrgggggg!!!
I did find some resources from Villain rom. So at least I found some term definitions.
Speaking of Roms...
If I have KF3 on my phone, and i wanted to put Villain Rom v.2 on it, would i need to install KF2? Or is it recommended to put on KG1? Am I flashing that like I flashed the kernels when rooting (via odin)?
------------------------------------
Well if you made it through that - thanks. My head feels like it's going to explode. Too much info, too fast. I feel like I've had a ton of info my brain really doesn't comprehend. What was that movie...Johnny Mnemonic?
I wish we had a Rooting Rom'ing Guide for Noobs. One that explained what terms meant along with the instructions. Maybe a screenshot or two.

benivolent said:
Greetings all.
Firstly, thanks for such a great repository of info. I have successfully managed to root my phone using Chainfire's method. I'm supremely happy to have even accomplished that.
I'm not a tech noob, but I'm quite new to Androids.
The feeling of frustration at trying to learn new terms and make sense out of all this information is HUGE. I have seen various "noob" entitled threads, as well as threads (Like ChainFire's) that make it somewhat easier. However, there seems to be so many threads to look through, and different info/terms that at this point trying to add a battery percentage mod to the status bar (which I'm sure is an easy easy thing to some of you) has become quite the gargantuan task for me.
---to that topic i'm having trouble understanding what it means when people say "flash using CWM". I understand "flash" (i think) and i know what CWM is, but have no idea what steps to take to "flash the necessary apk" files.
Do i use CWM? I've seen mention of using a root explorer or just adding the files overtop. CWM comes with Chain Fires Rooted Kernel. If you have rooted your phone using Chaninfiire Kernel you should have an app called CWM. you need to put the apk in your internal storage using PC, then open CWM, theer is an option to install apk. select that and browse to the file.. all done
Then I've read "backup first". Yes, i know i want to do that. I have Titanium Backup on my device. And I've backed it up> but then i read that i should be using Nandroid. Where the hell do i get that? lolz. I mean I've searched for it and found threads, but from HTC section. Is it even compatible? No D/L links...
it means backing up ur phone using CWM.. open CWM and theer is a backup option select that or just boot to recovery power off then Power+home key+ volume Up) and select backup from there
arrrrgggggg!!!
I did find some resources from Villain rom. So at least I found some term definitions.
Speaking of Roms...
If I have KF3 on my phone, and i wanted to put Villain Rom v.2 on it, would i need to install KF2? Or is it recommended to put on KG1? Am I flashing that like I flashed the kernels when rooting (via odin)?
no ur not required to put KF2 first. flash the villain rom using CWM (install zip from sd card)
------------------------------------
Well if you made it through that - thanks. My head feels like it's going to explode. Too much info, too fast. I feel like I've had a ton of info my brain really doesn't comprehend. What was that movie...Johnny Mnemonic?
I wish we had a Rooting Rom'ing Guide for Noobs. One that explained what terms meant along with the instructions. Maybe a screenshot or two.
Click to expand...
Click to collapse
hope that helps

Thanks indeed!
I did have a problem with the CWM, I did pretty much exactly as you mentioned - prior to me making this thread - and I used cwm to browse to the location with the apk on my sd card. installed... nothing happened.
re: cwm and back up - again, did as you had mentioned, but when i go into cwm and press "backup" it give me option to name the file, and then resets into recovery mode (i think - as i've used the buttons method to get to the same screen) but there is no "back up" option listed. also there is some csc error message. see picture.
re: villain rom. so to confirm, I do not have to change from kf3 to another kernel to install VR2.0?

Have to agree, especially for people coming form the world of Ilockedinsideaboxfullofnothingtochangeordophone
What are the benefits of flashing a custom rom?

PM sent.
Sent from my GT-I9100 using XDA Premium App

benivolent said:
Thanks indeed!
I did have a problem with the CWM, I did pretty much exactly as you mentioned - prior to me making this thread - and I used cwm to browse to the location with the apk on my sd card. installed... nothing happened.
re: cwm and back up - again, did as you had mentioned, but when i go into cwm and press "backup" it give me option to name the file, and then resets into recovery mode (i think - as i've used the buttons method to get to the same screen) but there is no "back up" option listed. also there is some csc error message. see picture.
re: villain rom. so to confirm, I do not have to change from kf3 to another kernel to install VR2.0?
Click to expand...
Click to collapse
according to that pic..u dont have cwm installed properly.. that recovery screen is from the default recovery which comes from the phone..ur not flashing your rooted kernel properly.. ur recovery screen should be orange in colour and it will be stated there clockwork mod recovery
and you can safely ignore that csc error..

THUDUK said:
Have to agree, especially for people coming form the world of Ilockedinsideaboxfullofnothingtochangeordophone
What are the benefits of flashing a custom rom?
Click to expand...
Click to collapse
You mean like my Blackberry? heh. for sure.
I'm hoping with the Custom Rom it's got less bloatware, better battery life.

xinfinityoO said:
according to that pic..u dont have cwm installed properly.. that recovery screen is from the default recovery which comes from the phone..ur not flashing your rooted kernel properly.. ur recovery screen should be orange in colour and it will be stated there clockwork mod recovery
and you can safely ignore that csc error..
Click to expand...
Click to collapse
I never installed cwm as a separate action. Only used the "cwm" that came with chainfire's stuff. I've seen the orange colour you speak of in an faq I've found, but I'm not sure how to remedy this....
I am using the system as described for flashing kernels in Chainfire's thread.
1. debug mode on phone
2. phone into download mode (three buttons)
3. start Odin
4. plug phone into usb
5. browse to zip/tar file of unsecured
6. phone reboots
7. root phone
8. install secured kernel to sd card
9. use cwm to flash that kernel. (which did so successfully i believe)
Is there another step I should have done to install CWM? will reflashing the kernel via odin fix this?
thanks!

benivolent said:
I never installed cwm as a separate action. Only used the "cwm" that came with chainfire's stuff. I've seen the orange colour you speak of in an faq I've found, but I'm not sure how to remedy this....
I am using the system as described for flashing kernels in Chainfire's thread.
1. debug mode on phone
2. phone into download mode (three buttons)
3. start Odin
4. plug phone into usb
5. browse to zip/tar file of unsecured
6. phone reboots
7. root phone
8. install secured kernel to sd card
9. use cwm to flash that kernel. (which did so successfully i believe)
Is there another step I should have done to install CWM? will reflashing the kernel via odin fix this?
thanks!
Click to expand...
Click to collapse
ur puting the kernel in the PDA section ?? and it is the chainfire kernel ur flashing using ODIN??
boot to download mode
CF kernel >> PDA (Odin)
Flash
Reboot
You get yellow triangle
to remove triangle use a usb jig..its the best option ..u can get it from ebay for less then 10 bux
or
transfer zimage file from the CF kernel.tar file (extract) to internal storage
boot to download mode
stock kernel >> PDA (ODIN)
flash
reboot
open up CWM application(should be in your apps)
choose flash kernel
browse to the zimage file from earlier (from cf kernel)
all done
your step 8 looks wrong.. secured kernel would mean stock..u will not flash the stock kernel (secured)

benivolent said:
You mean like my Blackberry? heh. for sure.
I'm hoping with the Custom Rom it's got less bloatware, better battery life.
Click to expand...
Click to collapse
Not unless bloatware has been removed . Read the rom posts in dev section .
Villain lite rom would be one with less bloatware or use the remove bloatware script same section .
Battery life is more than just the rom much is down to user apps installed .
Villian full rom thread has some useful battery info over the last ten or so pages .
jje

xinfinityoO said:
ur puting the kernel in the PDA section ?? and it is the chainfire kernel ur flashing using ODIN??
Yes, browsing to the CF kernel in pda section of odin
boot to download mode
CF kernel >> PDA (Odin)yup
Flashyup
Rebootyup
You get yellow triangleyup
to remove triangle use a usb jig..its the best option ..u can get it from ebay for less then 10 bux don't have a jig... yet
or
transfer zimage file from the CF kernel.tar file (extract) to internal storage
boot to download modemight do this then
stock kernel >> PDA (ODIN)
flash
reboot
open up CWM application(should be in your apps)
choose flash kernel
browse to the zimage file from earlier (from cf kernel)
all done
your step 8 looks wrong.. secured kernel would mean stock..u will not flash the stock kernel (secured)I did flash the secured version of the kernel back onto it after rooting it. That might have been the issue. I just reflashed CF kernel and had the CWM work differently for the back up. still not orange, but at least it actually backed it up!!! yaaaahooooo!
Click to expand...
Click to collapse
initially i had rooted with the one click method, and then still didn't have root so changed and did the chainfire method. but still put a stock kernel on after flashing and getting root with super one click. I think I didn't realize that the CF kernel means I get root without having to use superone click. and still put a stock kernel back on afterwards.

JJEgan said:
Not unless bloatware has been removed . Read the rom posts in dev section .
Villain lite rom would be one with less bloatware or use the remove bloatware script same section .
Battery life is more than just the rom much is down to user apps installed .
Villian full rom thread has some useful battery info over the last ten or so pages .
jje
Click to expand...
Click to collapse
Ok, fantastic. Thanks I'll have a look at that. I may not have gotten to the end yet with all 700+ pages hehe

And thanks to all who've responded to my issues. Much appreciated.
Here's the reflashed CF kernel CWM doing the back up... this about right?

benivolent said:
And thanks to all who've responded to my issues. Much appreciated.
Here's the reflashed CF kernel CWM doing the back up... this about right?
Click to expand...
Click to collapse
yes
get a jig ..will save u a lot of work.. since i think u made an error while trying to remove the triangle

xinfinityoO said:
yes
get a jig ..will save u a lot of work.. since i think u made an error while trying to remove the triangle
Click to expand...
Click to collapse
I purchased one from somewhere in the UK (off ebay), just waiting for it to arrive.
So now I've gotten my CWM working and i've backed up my phone with titanium and cwm (no need for nand i guess?) Can i safely try to add the mods for the battery %?

benivolent said:
I purchased one from somewhere in the UK (off ebay), just waiting for it to arrive.
So now I've gotten my CWM working and i've backed up my phone with titanium and cwm (no need for nand i guess?) Can i safely try to add the mods for the battery %?
Click to expand...
Click to collapse
as far as i think..backup using cwm is nand backup..unless i am wrong
once you have cwm backup u can play around with mods

thanks again for your help.

Ok got a problem, it won't boot up

So tonight I decided I wanted Netflix so I decided to root.
I followed the steps in this thread here
http://forum.xda-developers.com/showthread.php?t=1125714
I have Windows 7 and everything was running perfectly fine until step
4b. (OPTIONAL) if you want clockwork mod recovery, then go ahead and double click cwm.bat [Follow STEP 6 to update CWM]
I double clicked cwm.bat and proceeded to step 6.
I downloaded 84411.zip and placed it on my micro sd and put it in the transformer.
Then I turned off the transformer pressed vol down and power until the writing writing came up. So then I pressed vol up and it stated
Booting recovery kernel image and will not change from this. Vol buttons don't do anything. If I turn it off and on again it just stays at the Eee PAD ASUS screen and never changes.
What do I do? This thing won't boot and I don't know how to fix it.
Any help is appreciated.
Thanks
Martin

go to the sticky thread about nv_flash unbricking. The same thing happened to me, and that unbricking method restored it back to 3.1

Make sure you have the boot.img and recovery.img in place before you start anything.
Start over with these files in place and you're golden.
You don't have to unbrick it. Just start over with the files in place.
sassafras

Or even better, use the prime 1.6 rom with nv_flash and you'll have the thing rooted at the same time. nv_flash allows you to overwrite the rom/kernel at one time with one button.

AustinMartin said:
Or even better, use the prime 1.6 rom with nv_flash and you'll have the thing rooted at the same time. nv_flash allows you to overwrite the rom/kernel at one time with one button.
Click to expand...
Click to collapse
This will work. But correct me if I'm wrong, but I believe the Prime contains a data.img which will overwrite your settings. If you want to keep them, just don't include the data.img in the working folder.
sassafras

I ran the NV flash from the sticky. The Dos window showed it was updating and then closed.
Now it won't turn on. No matter how long I hold the power button. I just tried plugging it into the wall for juice but nada. It won't turn on.

i had it too the tf is running but screen is off get prime 1.5 nvflash version put it in nvdir flash it and ghen update to 1.6 using recovery

proplayer44 said:
I ran the NV flash from the sticky. The Dos window showed it was updating and then closed.
Now it won't turn on. No matter how long I hold the power button. I just tried plugging it into the wall for juice but nada. It won't turn on.
Click to expand...
Click to collapse
You can't brick this thing, just start over and make sure all of the files are in place. 9/10 times it's because you forgot to put the boot.img or the system.img in the same folder as the .bat file.
sassafras

sassafras_ said:
You can't brick this thing, just start over and make sure all of the files are in place. 9/10 times it's because you forgot to put the boot.img or the system.img in the same folder as the .bat file.
sassafras
Click to expand...
Click to collapse
Just a couple thoughts, questions.
Where should I start over? Its already rooted right? So I just need to install Prime?
The instructions for installing say to leave the zip in tact. So I assume that means put the zip on the micro sd card right? Both the bootimg and system.img files are on the microsd. I'm not sure there is a .bat file in there though.
I'm confused.

sassafras_ said:
You can't brick this thing, just start over and make sure all of the files are in place. 9/10 times it's because you forgot to put the boot.img or the system.img in the same folder as the .bat file.
sassafras
Click to expand...
Click to collapse
Also I'm just not sure what you mean, just start over. It won't turn on. My only option is the nvflash and I did it again but the device is still stuck in black screen.
I'm quite lost here. I'm in IT industry so I understand instructions fine but some of your terms I don't understand exactly. I've never really grasped flashing a the rom and upidating the kernal or updating the cwm. I don't understand what each really is.
Regardless if someone can give me step by step instructions. I'm told to use NVflash to install Prime 1.5. But all the Prime instructions I see say to use CWM.
Can you provide Something similar to this
Step one, go to ______ this thread and download _______
Take the ____ file and the _____ file from _____ and place them in the _____
Now do this or that.
Keep in mind if your first instructions are to put files on the sd card and then hit volume up and power that won't help because it won't turn on.
At this point I'm completely stuck and really appreciate the help you can provide.

proplayer44 said:
Also I'm just not sure what you mean, just start over. It won't turn on. My only option is the nvflash and I did it again but the device is still stuck in black screen.
I'm quite lost here. I'm in IT industry so I understand instructions fine but some of your terms I don't understand exactly. I've never really grasped flashing a the rom and upidating the kernal or updating the cwm. I don't understand what each really is.
Regardless if someone can give me step by step instructions. I'm told to use NVflash to install Prime 1.5. But all the Prime instructions I see say to use CWM.
Can you provide Something similar to this
Step one, go to ______ this thread and download _______
Take the ____ file and the _____ file from _____ and place them in the _____
Now do this or that.
Keep in mind if your first instructions are to put files on the sd card and then hit volume up and power that won't help because it won't turn on.
At this point I'm completely stuck and really appreciate the help you can provide.
Click to expand...
Click to collapse
Do you need your settings at all? This means all your data.
If you don't then I'll write up a quick guide.
- Download NVFlash & .tar.bz2 of a ROM you want (not all ROMs have .tar.bz2s). If you can't pick download PRIME 1.4 .tar.bz2 in NVFlash OP thread
- Set the tablet in APX mode
- Set up the drivers if you haven't already while tablet is in APX.
- Extract .tar.bz2
- Cut the files extracted by the .tar.bz2 (boot.img,recovery.img,system.img) into /nvflash/
So you should see... the 3 files (boot.img,recovery.img,system.img) next to bootloader.bin,download.bat,download,sh.. etc etc
- Double click download.sh if you're using linux.
download.bat if you're using windows
- Watch magic happen in a black box.
- Grats. You have PRIME 1.4.
- Download a ROM you want and place it in /Removable/microSD/ (Your SD CARD.. you must have one)
- Flash it in Clockwork Recovery. Note, ROM manager is incompatible with the Transformer so don't use it.
- Flash it like any other ROM as you would on any other Android device.
- You're done.
Hit the thanks. Hope this helps.
And getting into Clockwork should be VOL DOWN + POWER then hit Volume up (or whatever it says on the screen).

My first problem
I cannot find a thread with this
Download NVFlash & .tar.bz2 of a ROM you want (not all ROMs have .tar.bz2s). If you can't pick download PRIME 1.4 .tar.bz2 in NVFlash OP thread
I've searched and cannot find a link to 1.4 anywhere. I searched the form for terms prime and nvflash.
The 1.6 thread has no link to 1.4 but it does to 1.5.

Ok. I see your problem now. nv_flash is dangerous because it is a raw flash utility that will essentially wipe out anything on the flash unit of your device. The upside is that it's baked into the CPU so you can never lose the ability to NV_flash even if you completely bork the ROM.
First, download this: http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
This is the actual ROM image you will need.
Next, download this: http://www.filefactory.com/file/ccda97c/n/nvflash.zip
This is the nvflash utility for windows that will do the heavy lifting. It should also contain the apx drivers for your device.
Now:
Unzip the second zip somewhere that is easy to find.
Unzip the contents of the first zip into the same folder as the download.bat file from the second zip. There should be a boot.img and a system.img (and maybe more, I can't recall)
If your device is powered on, turn it off.
Plug your device in and simultaneously hold Power and Volume UP (this is sort of tricky, I know)
When the device shows up in windows, go to your device manager and manually install the drivers from the nvflash folder for the 'APX device that appeared' they will be in the usbpcdriver directory in that second zip.
With the APX drivers installed, run download.bat and wait. Your device should indicate that it is writing the partitions. When done it will turn off and reset.
Voila. You should be all better now.
sassafras

Awesome thanks.
Now when I use winrar to unzip the 1.4 it only has one file. System.img is that right?
Also I completed your steps already if that is correct, by reading the other responses. But now I'm stuck loading hc to it. I did do a wipe and now it is just continually rebooting. I put a clockwork zip file on the microsdcard as well as a Ultimate edition revenge as Iassumed thats what I need.
I need to boot to cwm and load hc to it right. What are those steps? Man I feel like a total noob. I think I'll make instructions for all this and request it be a sticky.
Edit, doing some research.
I don't know how important these instructions are with the advent of new technology, and ways to root but do I first need to complete Step 2 in this thread first?
http://forum.xda-developers.com/showthread.php?t=1106587

proplayer44 said:
Awesome thanks.
Now when I use winrar to unzip the 1.4 it only has one file. System.img is that right?
Also I completed your steps already if that is correct, by reading the other responses. But now I'm stuck loading hc to it. I did do a wipe and now it is just continually rebooting. I put a clockwork zip file on the microsdcard as well as a Ultimate edition revenge as Iassumed thats what I need.
I need to boot to cwm and load hc to it right. What are those steps? Man I feel like a total noob. I think I'll make instructions for all this and request it be a sticky.
Edit, doing some research.
I don't know how important these instructions are with the advent of new technology, and ways to root but do I first need to complete Step 2 in this thread first?
http://forum.xda-developers.com/showthread.php?t=1106587
Click to expand...
Click to collapse
No. The NV_Flash tool is so dangerous because it completely ignores the Android OS. You can literally flash anything you want with NV_Flash and no root or preparation in Android is possible or required.
The .zip that contains the system.img should also contain these two files:
http://dl.dropbox.com/u/10724980/nvflash/recovery.img
http://dl.dropbox.com/u/10724980/nvflash/boot.img
Put those along with system.img in the same folder as the nvflash file.
Also, make sure these two files are in that folder as well:
http://dl.dropbox.com/u/10724980/nvflash/flash.cfg
http://dl.dropbox.com/u/10724980/nvflash/transformer.bct
With all six of the files (the four I linked plus system.img and nvflash) run the download.bat file again with the transformer in apx mode.
sassafras

Awesome awesome awesome. That worked and was successful.
So then I put prime 1.6 on the card and successfully booted into CWM. YAAAAA!!!
I installed prime 1.6 successfully and choose to reboot. It then loaded on the eeepad screen with a blue bar going across. But now it just stays at the eee pad screen again. But I know I'm close because "powered by Nvidia Tegra" is back at the bottom.
So I must need to load something else here right to actually load hc?

proplayer44 said:
Awesome awesome awesome. That worked and was successful.
So then I put prime 1.6 on the card and successfully booted into CWM. YAAAAA!!!
I installed prime 1.6 successfully and choose to reboot. It then loaded on the eeepad screen with a blue bar going across. But now it just stays at the eee pad screen again. But I know I'm close because "powered by Nvidia Tegra" is back at the bottom.
So I must need to load something else here right to actually load hc?
Click to expand...
Click to collapse
haha. You fixed it then broke it again what a hopeless wreck.
Re-download 1.6 and check the MD5 against what is in the first post to make sure it's not corrupt then flash it again in recovery. Make sure you also wipe your dalvik-cache and cache before you try to boot.
sassafras

sassafras_ said:
haha. You fixed it then broke it again what a hopeless wreck.
Re-download 1.6 and check the MD5 against what is in the first post to make sure it's not corrupt then flash it again in recovery. Make sure you also wipe your dalvik-cache and cache before you try to boot.
sassafras
Click to expand...
Click to collapse
Ok I downloaded some MD5 check software and ran it and it compared the newest downloaded prime 1.6zip with the number in the prime 1.6 thread and they were the same. After reflashing 1.6 again I cleared both caches and rebooted but I'm still at the same spot. No boot.
When you first said I fixed it and rebroke it I thought, huh, because I tried to boot up after running the download.bat but it also stayed at the asus screen. I then installed the 1.6.
Now in the beginning, I'm talking about last night I went into the other linux option by not choosing volume up in the first 5 seconds and I accidentally choose the wipe option because my finger slipped on the volume toggle. Could that have something to do with it?

Maybe, but honestly, the point of the nvflash file is to wipe it fresh, even if you wiped it out entirely.
Maybe start again from APX mode with the 1.4 set of files (ensure that system.img is good. That's the real important one. Download it again just for good measure). Get it to boot in 1.4 first before you go trying any funny business.
sassafras

Working now, Thanks again.

[Recovery] Official CWM Recovery 5.0.2.6

I take no responsibility for any harm that comes to your phone as a result of applying this mod.
Official Clockwork Mod Recovery 5.0.2.6
Note that ROM manager support isn't currently complete. ROM downloads etc should all be working fine, but it needs to be updated to properly flash the recovery. At the moment it uses a method called fakeflash which will load the latest recovery from within whatever recovery you have installed. All other aspects are working fine though.
Download:
5.0.2.6: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.6-u8800.img
Installation Instructions (upgrading - root explorer method):
Using any file explorer which is able to remount as writeable (such as root explorer), browse to the /cust_backup directory and remount it as writeable
Navigate to the image directory and backup up the current recovery by renaming it to something like recovery.bak, or _recovery.img
Rename the downloaded recovery to recovery.img and copy to the image directory.
Installation Instructions (new install):
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see recovery.img etc.
(optional) Rename recovery.img to recovery_backup.img
copy the new recovery.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Hold volume + and power to boot to recovery.
Install any custom rom
Install rom manager and update to latest recovery
Source:
https://github.com/stockwell/android_device_huawei_u8800

That's cool! Is it still possible to boot it with stock kernel, or you did modifications to recovery_kernel?

You can't flash the boot images with cwm i thibk. Download and add this recovery img in /cust_backup/image folder its done.
And thanks stockwell. Haptic now work in recovery mode. Blue text version is much better than yellow
- U8800

blue text i like it.
thanks stockwell

stockwell said:
[*] Instead of using /cust_backup it now uses /boot. This doesn't affect rom installations but it WILL affect backups as it won't restore the cust image. If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made.
Click to expand...
Click to collapse
Stockwell, this is for old backups and for the ones made already with the new recovery? We still have to make these alterations everytime we want to restore?

Thanks a lot . Good job.
Sent from my u8800 using XDA App

Druida69 said:
Stockwell, this is for old backups and for the ones made already with the new recovery? We still have to make these alterations everytime we want to restore?
Click to expand...
Click to collapse
Sorry I meant to reword that since its a little unclear. This is only for backups made with an old version of recovery. All new backups will name it boot instead of cust.

stockwell said:
Sorry I meant to reword that since its a little unclear. This is only for backups made with an old version of recovery. All new backups will name it boot instead of cust.
Click to expand...
Click to collapse
You probably need to change your anyKernel script as well to use /boot instead of /cust for the boot.img, if I did not misunderstood.

Ok thank you stockwell, was just to have 200% sure

NForce25 said:
That's cool! Is it still possible to boot it with stock kernel, or you did modifications to recovery_kernel?
Click to expand...
Click to collapse
The recovery kernel is the kernel I use for Miui, but with the framebuffer set to 16-bit colour.
There's nothing specifically added to the kernel to make it work with the recovery other than that, but if you do manage to get it to boot on your pro then the display will be weird since its trying to output 16-bit colour to a 32-bit colour framebuffer.
It requires only a small modification to get the recovery working in 32-bit colour though, so if you do get it to boot then I can help you get it fixed up.
franciscofranco said:
You probably need to change your anyKernel script as well to use /boot instead of /cust for the boot.img, if I did not misunderstood.
Click to expand...
Click to collapse
Ah thanks yeah I will need to change it. I'll try and get it done now, the new version of AnyKernel should be compatible both with the new and old versions of recovery.
Edit: Modified version of AnyKernel is on my github. I haven't tried it out but it should work fine on new and old recoveries.

This recovery is already rock’in rolling in my machine.
Why when we use most of the option we have endless line of “NO” and then the option to execute in the middle of them.
Example:
No
No
NO
No
Wipe davilk
No
No
No
By the way, tried to flash new Ffranco kernel several times and in recovery it’s done successfully but when I enter the systems and go to settings it still showing the previous kernel...

Druida69 said:
This recovery is already rock’in rolling in my machine.
Why when we use most of the option we have endless line of “NO” and then the option to execute in the middle of them.
Example:
No
No
NO
No
Wipe davilk
No
No
No
By the way, tried to flash new Ffranco kernel several times and in recovery it’s done successfully but when I enter the systems and go to settings it still showing the previous kernel...
Click to expand...
Click to collapse
its there to avoid mistakes i think
and to lead user to actually read whats written there

will not comment that....
Stockwell, been making tests and apparently is not just the last Francisco's kernel that isn't working with this new recovery. All previous ones don’t work either.
I have reverted to previous recovery until this is fixed or until I know if I'm doing something wrong

stockwell said:
The recovery kernel is the kernel I use for Miui, but with the framebuffer set to 16-bit colour.
There's nothing specifically added to the kernel to make it work with the recovery other than that, but if you do manage to get it to boot on your pro then the display will be weird since its trying to output 16-bit colour to a 32-bit colour framebuffer.
It requires only a small modification to get the recovery working in 32-bit colour though, so if you do get it to boot then I can help you get it fixed up.
Ah thanks yeah I will need to change it. I'll try and get it done now, the new version of AnyKernel should be compatible both with the new and old versions of recovery.
Edit: Modified version of AnyKernel is on my github. I haven't tried it out but it should work fine on new and old recoveries.
Click to expand...
Click to collapse
Thanks stockwell, will try later.

I was able to brick my phone after i've restored from backup.
So please be aware with this version of CWM.
Brgds,
S.

mesnati said:
I was able to brick my phone after i've restored from backup.
So please be aware with this version of CWM.
Brgds,
S.
Click to expand...
Click to collapse
What ?

stockwell said:
I take no responsibility for any harm that comes to your phone as a result of applying this mod.
So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself.
Basically the main hurdles preventing this previously were that we were reliant on using the init from the Huawei recovery, and also the offmode charge code was a direct modification to the recovery source. I spent quite a bit of time yesterday and today and have overcome these problems, and the result should hopefully be rom manager support in the near future.
What's different?
Instead of using /cust_backup it now uses /boot. This doesn't affect rom installations but it WILL affect backups made from an older recovery as it won't restore the cust image (its looking for boot now). If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made.
Haptic feedback is enabled on touch keys, and the keypad backlight is turned on
When in offmode charging you need to pull the USB cable out and let it turn off before booting, you can't just press the power button to turn it on.
Backups are compressed
It's blue.
Download:
5.0.2.3: http://code.google.com/p/u8800-miui/downloads/detail?name=CWM Recovery 5.0.2.3-new_install.zip
Installation Instructions:
Unplug any usb connection and turn the phone completely off
Whilst holding both the volume + and volume - keys hold the power button to turn the device on. Let go when you see a pink/purple screen.
Attach the usb cable to your computer and wait until a few usb mass storage devices are detected and mounted. Look for one that has just one directory called 'image' in it. Navigate into this directory and you'll see recovery.img etc.
(optional) Rename recovery.img to recovery_backup.img
copy the new recovery.img to image, unmount the mass storage device (safely remove in windows) and then pull the battery out to turn the phone off.
Hold volume + and power to boot to recovery.
Source:
https://github.com/stockwell/android_device_huawei_u8800
(Note that the device config isn't properly setup for anything other than the recovery, so don't expect to be able to use it for a fully working CM7 build)
Click to expand...
Click to collapse
Why mount /cust on /boot?
It has no functional purpose and just ****s it up.
"So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself. "
The lack of a ROM Manager release is due to me trying to avoid using the huawei init where I can, because it's full of stupid hacks.
Maybe after months of users complaining at me to do something I don't have to do, I might just get fed up and decide not to do it anymore.
I've said it before and I'll say it again, this is why I hate xda.

Current recovery works perfectly for what I use it, any reason to change? Does this enable anything special? Reading the "what's different" I don't see any reason why but i could be missing something.
Edit, Have no idea who this guy Jacob is but from a few posts I've seen from him, all he does is whine. Dude buy a stuffed animal or something.

POST 1 today
"If you want to go back to one of these backups from the new recovery you can go to the backup location, rename cust.img to boot.img, and also edit nandroid.md5 so that it says boot.img instead of cust.img. The backup will then restore but just be aware that it will also revert to the recovery you had when the backup was made."
For me is not pratical to change to 5.0.2.3. I have 12 Backups various. When I make a Restore I return to 4.0.1.5 and the renamed Recovery_backup.img on internal data storage are deleted. I continue whit 4.0.1.5.
Thanks.
........................................
EDIT: I made this and work (GENO method), no pink screen :
To install (you need root):
1. Backup /cust_backup/image/recovery.img
2. Download, extract and place the recovery.img into /cust_backup/image/
3. Done.
To go to recovery:
1. Power off
2. Hold Vol+ and Power buttons to power on (hold both buttons UNTIL you see the recovery)

HCDR.Jacob said:
Why mount /cust on /boot?
It has no functional purpose and just ****s it up.
"So after months of expecting Jacob to get us ROM manager support I got fed up and decided to do it myself. "
The lack of a ROM Manager release is due to me trying to avoid using the huawei init where I can, because it's full of stupid hacks.
Maybe after months of users complaining at me to do something I don't have to do, I might just get fed up and decide not to do it anymore.
I've said it before and I'll say it again, this is why I hate xda.
Click to expand...
Click to collapse
I changed it to /boot because first off I hate calling it /cust (it should be /cust_backup anyway), and second off because (unless I'm missing something, which I may well be) nandroid won't back it up without modification unless it's called boot. It doesn't **** anything up except for anykernel(which I fixed) because all of our rom install scripts explicitly mount mmcblk0p1 to /cust rather than just trying to mount cust and letting the fstab do the rest.
As for the rest of it, have a look at my github and my post. I'm not using the Huawei init and I'm not doing any modifications to the recovery source to achieve offmode charging. This port is fully functional and should be completely compatible with rom manager.
You're not obligated to do anything, I'm merely stating that ages ago you took money from people on this forum to buy a phone, and announced that you would be porting CM7 and getting official CWM recovery, so I expected rom manager support to come. Months later we have nothing, so I did it myself.
swayjd said:
Current recovery works perfectly for what I use it, any reason to change? Does this enable anything special? Reading the "what's different" I don't see any reason why but i could be missing something.
Edit, Have no idea who this guy Jacob is but from a few posts I've seen from him, all he does is whine. Dude buy a stuffed animal or something.
Click to expand...
Click to collapse
There's no reason to change to this really, it's more of a 'pre-release' to make sure it works without any problems. If/when koush merges it into rom manager though this will be the version that's incorporated so I needed to make sure it didn't have any huge problems I missed.
Druida69 said:
will not comment that....
Stockwell, been making tests and apparently is not just the last Francisco's kernel that isn't working with this new recovery. All previous ones don’t work either.
I have reverted to previous recovery until this is fixed or until I know if I'm doing something wrong
Click to expand...
Click to collapse
His new version should work now, AnyKernel (the method used to flash the kernel to the phone) needed a small modification to make it compatible with new and old version of recovery.

Need Urgent Fascinate Help

I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help

want a droid said:
I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
Click to expand...
Click to collapse
Odin the proper clockwork,reboot straight to it, wipe data and then flash CM7 from the SD card.

Please give me step by step instructions with links. I'm an HTC Thunderbolt guy myself so I am having a hard time finding all the right links and stuff. I really appreciate your help!

First sticky in this forum has all the links and steps.
Sent from my SCH-I500 using Tapatalk

I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.

want a droid said:
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
Click to expand...
Click to collapse
Really? did you look at the sticky?
Code:
HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. All of the files, I cant guarantee links to other OP's, will still be available, I wont take them down. Your recovery methods have not changed, nor have the PIT files, so this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
Everything you need can be found here: http://forum.xda-developers.com/showthread.php?t=1026746

odin...
atlas_v2.2.pit
CI500_VZW_ED05_FROYO_REL.tar.md5
check repartition
then follow the CM wiki

I don't understand why I'm getting this: http://imgur.com/WkDsK
Sorry for rotated picture.
I'm in the process of flashing the verizon firmware but it's taking forever to download. I thought I could just odin the CWM?

You better do some research before u brick ur ****...there are guides all over the place on how to get back to stock/flash roms. And last but not least all questions should be posted in the q&a section...that's what its there for...seriously use it!

Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
When I try to connect it to my mac it says it can't read what I'm trying to connect. When I connected it to windows laptop it says its a CD drive that is write protected.
I can't move any files in or out. Also when I try to flash a rom zip in recovery it doesn't work.
I'm in the process of trying to restore her MIUI backup. Here's to hoping that works.
EDIT: Supposedly the restore worked, but here is part of the error that showed when trying to flash a zip (top text): http://imgur.com/X1RQL
Oh and I'm stuck on the Samsung screen now...what do I do?

want a droid said:
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
Click to expand...
Click to collapse
fail.
if you did CM Wiki, you have CWM 4.X, not 2 or 3
you need to flash back to stock like i said

I did flash back to stock. Anyways in the broken clockwork recovery I decided to try and install MIUI again and when I clicked it it took me to an orange recovery.
Then I flashed her backup and it loaded up fine. Hopefully everything is back to the way it was. I'm not sure what ever went wrong in the first place.Thanks for your help.

Dude...sounds like you just made it hard. Its actually quite simple.
Pull battery, put in download mode.
Odin the Verizon firmware with atlas.pit and repartition checked.
let it boot, then shut it back down and go back into download mode and Odin the fixed recovery for CM7. Then flash MIUI and profit.
It shouldn't take but about 15 minutes out so for the whole process
Swyped via Tapatalk

Well I wish you had been here last night. I was told to do the heimdall thing and then after all that the phone wouldn't be recognized in odin.
It was a frustrating 3 hour long process (granted ~1h was waiting for the 441MB file to download).

so I found this thread searching through the fascinate forums and i gotta say, it saved my ass. I used heimdall 1.3.1 and it wasn't working right for the flash. IDK why but when I tried 1.1.1 it worked first try to flash back to stock after brick. I used the eh03_full_odin.zip file in heimdall and it quick and easy to get back to stock =] this forum rox!!

[SOLVED][WALKTHROUGH] Unbricking bluescreen and pinkscreen to fully functioning phone

Hi, this is just a recompilation so that people don't have to get confused and scared.
Before your read this, please understand that this happened because of my own stupidity at somehow managing to delete the /boot from recovery 5.5.0.4, and caused a BLUESCREEN. When I tried to go to recovery, it went back to a pink screen. There were also other issues, such as a corrupted internal sd partitioning (warning, please be careful about doing partition, i highly recommend a proper partitioning zip which i'll link later in the post). In the end I was able to revive from the soft brick, and continued on to reinstall CM10.1 (it was version 7 at the time of the crash)
OKAY, let me repeat. Probably at this point you have a phone that has bricked. But if you can access PINK SCREEN, you're in luck (EVEN IF YOU DO NOT HAVE USB connection, its fine, as long as your EXTERNAL SD CARD is still accessible, physically.)
I'll put the stages in below:
WARNING I am not responsible for any loss, damage, or earthquakes or whatever crap that happens. Do this at your risk. Before you proceed, PLEASE OPEN THE BATTERY AND LOOK INTO THE BACK OF THE PHONE AND MAKE SURE IT SAYS MODEL: U8800 NOT U8800H, NOT U8800PRO. THIS IS FOR U8800 (okay, I admit i'm using U8800H but this is just an exception, probably)
PREPARATION:
STAGE 1: Getting the PINK SCREEN and booting into 2.2 Froyo / 2.3 Gingerbread
STAGE 2: Getting the TOUCH RECOVERY / CLOCKWORK RECOVERY, ROOT and SUPERUSER into the phone.
STAGE 3: Flashing the recovery, the partition, and the firmware
STAGE 4: Miscellaneous
PREPARATION
Click to expand...
Click to collapse
There are a few things that you need to prepare before hand.
1. A working computer (in this case i use windows)
2. Huawei USB drivers for windows. http://www.mediafire.com/?5z6i5cv8l6br292
3. Huawei Gingerbread base 528 ROM (this is BOOTLOCKED but don't worry, we can fix it just read up)
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyNTU=
4. BLEFISH's "get back your pinkscreen" zip file (to be used with item 3, listen!) http://forum.xda-developers.com/showthread.php?t=1457490
5. Super One Click http://www.multiupload.com/9AJDSU1Q11
6. Blefish's recovery.img for the CLOCKWORKMOD recovery
7. Forumber's PARTITION.ZIP (the better option thus far) http://forum.xda-developers.com/showthread.php?t=2145187&page=124
8.. A ROM OF YOUR CHOICE (http://forum.xda-developers.com/showthread.php?t=2166353) as for me i'll just wait for Blefish to release his version of JB / CM re-write.
Now we're done, let's proceed
BEFORE YOU BEGIN:
*credits to forumber2*
Forumber2 wrote in one of the responses (not in this thread) that caught my attention. Apparently, if you're using a B158 bootloader, you can still access the STORAGE if you remove the battery and plug in USB for 1 minute.
forumber2 said:
In Blue screen,connect your phone to PC and wait 1 minute. A storage will show if you was in B518 bootloader. If the storage shows,please report here
Click to expand...
Click to collapse
I am not sure what steps to take this (it is a new information for me) but I presume you can immediately restore the TCRW from there. Have to ask forumber2 though.
STAGE 1: Getting the PINK SCREEN and booting into 2.2 Froyo / 2.3 Gingerbread
Here are the steps.
1. Install the HUAWEI drivers for the phone, and also SUPER ONE CLICK for windows.
2. Take out the U8800's EXTERNAL SD CARD, and plug it into computer. (use a card reader if you don't have)
3. open (UNZIP) the downloaded OFFICIAL GINGERBREAD ROM. Inside it should be a manualand a folder called "STEP 1", and inside folder "STEP 1", another folder called "DLOAD".
3a) COPY the "DLOAD" folder (and its content) and place it into the ROOT of your EXTERNAL SD CARD. that means from your computer it should read like this: (when you navigate)
X:/EXTERNAL SD CARD/DLOAD/UPDATE.APP
(X is the name of the drive)
4. Unmount the EXTERNAL SD CARD, and then slot it back into the U8800 phone.
5. Pull out battery.
6. Stick USB into the port, and into computer. (WITHOUT THE BATTERY)
7. PRESS VOL+,VOL- and POWER together (Reboot into pink screen)
FIRMWARE UPDATE PROGRESS. it should be 1/2 then 2/2.
"Do Not turn off the device".
AFTER finishing step 4 (it takes some time)
there will be a "TICK" and it will say "RESTARTING".
QUESTION What if I can't? It doesn't work?
ANSWER There's another trick. Pull out the battery, plug the USB wire in (YES, just plug in without battery) and then boot into recovery. This should work. Assuming it does not, get another USB cable with data capabilities, and USB 2.0 ready port on the computer. This should provide MORE POWER to the phone (the phone has a weird failsafe system where it would not proceed with upgrade if the power is too low)
REASON: HUAWEI wanted the customers to have a simple update process, so they created the entire thing to just be unzip, plug in, and wait. Yeah. I know, you'll feel weird especially when other phones seem to be super sophisticated at this part and Huawei made it so easy. Even the remove the battery part. Yes.
QUESTION: But what if i'm stuck at 1/2? goddamnit?
ANSWER This did not happen to me with the file. Like I said, again, it depends on the firmware. What I've read and understood is that there is a possibility of 1) bad firmware (need to download another firmware) or 2) EXTERNAL SD CARD is badly formatted (please use an Android phone / tablet to format just to be sure) There's a thread with specific discussion about this but it was lost on my notes, but that's the gist about it. What I'll suggest you to do is download the 2.2 Froyo then upgrade back to 2.3 Gingerbread. Some people have made it through this stage by doing everything from 2.2 Froyo itself.
Reason: I'm not so sure what is wrong, but this is one of the irregularities that posters have asked when unbricking the phone.
NOTE:
After the installation part, it should restart itself a few times. Basically, after the big "TICK" and "RESTARTING", it will continue to restart again, and again, and again, and again. Then finally it should boot up properly, and then the HUAWEI logo, then the flying dust animation, then the Huawei lotus flower glowing animation, and then boot up into 2.2 Froyo or 2.3 Gingerbread (depending on your firmware)
QUESTION: Okay, I see the boot looping. However, it just boot loops, and does nothing. At times i see the animation stop. Something must be WRONG!
ANSWER This happened exactly to me. The answer was that for some reason the pinkscreen update DID not format cache and data, as well as dalvik, etc. This is a recovery issue. The way i solved this was, that I re-did the update (making sure that it really did update properly into the official stock rom), then wait for the boot animation loop, (which happened) Then, the next step was like this:
1. TURN off the phone.
2. Plug in battery (or remove it)
3. Plug in USB (yes, again!)
4. Hold POWER button and VOLUME UP button.
If you can somehow boot into a blue colored Android system recovery *3E* screen. This one is the recovery with menu, but it is HUAWEI's recovery.
5. FORMAT CACHE, FORMAT DATA
6. REINSTALL THE official ROM, (YES wait again for the "TICK" and "RESTARTING", then it should restart a few times, then boot up. Have patience and faith!
*note: apparently as noted by aashi02 when the said user was unbricking the u8800, the 3E recovery has a factory data reset which somehow clears up the entire phone and enables the phone to properly work with the stock factory-default firmware (instead of crashing again and again and again in 2nd boot onwards). So I would presume that after first boot, one would have to again boot into recovery and do a factory reset (or do it while in the settings in first boot). Not sure if there are any users to encounter "2nd boot force close syndrome" after this. (if there are, please tell me)
The phone should have booted. If it doesn't, please tell me. I can't help much but I'll try to record as many possible errors and steps to overcome it, if i see responses from others and proven to work.
STAGE 2: Getting the TOUCH RECOVERY / CLOCKWORK RECOVERY, ROOT and SUPERUSER into the phone.
Once you've got into the GINGERBREAD / FROYO, follow this thread
http://forum.xda-developers.com/showthread.php?t=1420728
Or I'll record the instructions here
Thatguy said:
Rooting the U8800 with SuperOneClick v2.3.3
1) Dial: *#*#2846579#*#*
2) Go to projectmenu > background settings > log settings > log switch > set Log on
3) Reboot Phone
4) Switch USB Debugging ON
5) Download SuperOneClick v2.3.3
6) Plug your U8800 into your computer but DO NOT mount SD Card.
7) Run SuperOneClick and press the ROOT Button, and let it do its thing (say yes to install drivers if asked).
8) Your phone should now be Rooted.
9) You can now go back and turn logging off if you want.
Click to expand...
Click to collapse
The next step immediately after this is NOT TO RESTART the phone, but to install the CWM
Thatguy said:
Installing ClockworkMod 5.5.0.4 on your U8800
1) On your U8800 go to Settings > Applications > Untick Fast Boot (if ticked)
2) Download Blefish's ClockworkMod from HERE (ClockworkMod v5.5.0.4)
3) Copy the recovery.img from computer to your SD Card.
4) Using Remount mount the .cust_backup/image folder as RW.
5) Using ES File Explorer or File Expert copy the recovery.img from the SD Card to .cust_backup/image (replacing existing)
6) ClockworkMod v5.5.0.4 will now be Installed on your U8800
7) Turn on your U8800 while holding [VOL+] to load ClockworkMod Recovery (keep holding [Power] + [VOL+] until ClockworkMod Loads)
Note: if you have a Synaptics screen you have to use the [VOL] buttons to navigate and [Power] button to select an option.
Click to expand...
Click to collapse
QUESTION: Okay, somehow somewhere when i boot the phone for the first time, its okay. Second time, everything goes to hell (Force Closure, errors, etc, i can't press anything!) Something must be wrong again! You suck!
ANSWER Well, yes, this happened to me. Again, please read the guide. I said, no reset. Just do everything in one GO. That's how i fixed the problem.
NOTE: by now you should be able to boot into CLOCKWORKMOD recovery.
STAGE 3: Flashing the recovery, the partition, and the firmware
This is where we want to go to, and this is where you want to fix all the problems. I should not need to elaborate here, but if you're reading this part, you can now close this thread and go to the ROM of your choice and install as per THEIR INSTRUCTIONS:
QUESTION: Wait a minute. Something's fishy. THAT EASY? You screwin' with me, noob?
ANSWER Technically it should. There should not be any other problems UNLESS you somehow again delete the /boot. NEVER EVER DELETE /BOOT. If you have installed any firmware higher than 518 (B522 and above) firmware, then you need to do the next step:
NOTE: HOW TO INDENTIFY your firmware base
This is from my own Android "about" screen:
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Click to expand...
Click to collapse
Notice the 526 in there? it means i installed base 526
QUESTION: Wait a minute. You asked me to download that frickin' partition.zip and what do you expect me to do?
ANSWER Read the answer to the next question.
QUESTION: Help! I haz problemz! i cannot install ROM! it haz fail / not enough space on my internal SD! helpz!
ANSWER IF, and I repeat IF, you're reading this, then you're probably installing something way bigger than the original partition's system partition. To help you imagine, think of it as a 10-car train. The basic idea is instead of 1 engine, you now put 2 engine, and sacrifice 1 compartment car (that means from "1engine-9car train" into a "2engine-8car train". This is where you'll find the partition.zip helpful.
BUT BEFORE YOU DEAL WITH PARTITION.ZIP, do install "GET YOUR PINKSCREEN" by Blefish, read it here:
http://forum.xda-developers.com/showthread.php?t=1457490
I quote Blefish:
Blefish said:
In the newer official ROMs, Huawei included a "feature" to lock the bootloader and therefore, get less bricks. But happened the opposite - if your cust partition gets corrupted/deleted, you'll have a high change of bricking your device.
The new bootloader is not actually locked, it's changed to use QPST (Qualcomm Product & Support Tools). As it needs a code, we can't use it.
This method flashes the B518 bootloader straight to your phone, so you will get back USB.
Apply only if you have upgraded your phone to B522 or newer. You may have a custom ROM on top, but the base has to be B522 or newer.
Tested by myself on B522, B526 & B528.
The steps required to get back pink/blue screen USB:
Automatic flashable zip is pretty much fail proof, but I have warned you.
Automatic method (recommended):
Download update-B518-bootloader.zip from MediaFire.
Save it to the root of your SD Card.
Start the phone in recovery mode (recommended recovery is 5.5.0.4)
Select "install zip from sdcard"
Select "chooze zip from sdcard"
Select the zip you downloaded before.
Select yes.
Reboot and enjoy!
Click to expand...
Click to collapse
Now that you've fixed the locked bootloader on 522/526/528, now its time to do the partition. zip
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2145187&page=124
I quote NERDO
Nerdo said:
RePartition
Note:After this operation;Phone's /data partition will be 1.4 GB,/system will be 360 MB /HWUserData (2GB Internal Memory) will be 1.02 GB and formatted
1.Download partition.zip in the attachments and copy to sdcard
2.Goto recovery
3.advanced > reboot recovery
4.Wipe data factory set
5.mounts and stroage > format system
6.advanced > reboot recovery
7."install from sdcard" and select partition.zip
*Phone will reboot to recovery after install partition.zip
7."install from sdcard" and select partition.zip again
*Phone will reboot to recovery after install partition.zip again
Click to expand...
Click to collapse
The KEY IDEA here is that you need to flash the partition 2 times.
B]QUESTION:[/B] Now what?
ANSWER Install your custom ROM as per your custom ROM's instruction.
B]QUESTION:[/B] No, really. Now what? I want to double make sure, because i don't trust you, noob.
ANSWER Okay, you need to format and clear, not everything. Follow these steps.
ROM Installation:
Use only Forumember partition.zip.
1. Copy package to SD card
2. Boot to recovery
3. Full wipe (data, cache, dalvik,) <--- This one is in main menu
4. Format /system, /data, /cache <--- This one is in ADVANCED MENU. NO NEED TO MOUNT and DISMOUNT, and DO NOT FORMAT BOOT
5. Reboot recovery
6. Install the custom ROM (and gapps if needed.)
7. Reboot. Take a deep breath.
The phone should now boot into your new custom ROM.
As per writing, i booted into CM10.1 v7 by ilyaa299. Still waiting for a better JellyBean ROM though.
Congratulations, enjoy your unbricked phone!
STAGE 4: Miscellaneous
Not all ROMs are created equal. And none stand peer to peer. No matter how many seasons have come and go, please remember the ROM is only alive as long as its developer remains commited to its releases and updates. Please thank them. They will appreciate it.
For most usage, I have no issues, except the piss poor memory of 300++MB. I have not found a way to solve this. There are APPS that claim to create a virtual RAM, but if you don't have class 6, or class 10 External SD card, don't bother, and from what I read it'll shorten your EXTERNAL SD CARD's life A LOT. use it at your own risk.
To help alleviate the situation, i installed "auto memory manager" and also "greenify". This has helped me a lot. Auto memory manager deals with current usage, but "greenify" deals with the apps that are inactive, but greedily and stealthily use RAM and hog it (as if they're some royalty of some sort)
One of the greatest points of this phone is that it has a SUPERIOR camera (even if its only 5.0mp) and it has superior HD viewing (watch movies, youtube, etc, in FULL HD, where other phones, even the MORE expensive ones cannot do)
Try to avoid apps that uses 'download as a process" like mangawatcher, because i somehow managed to fry my EXTERNAL SD card (total death) because i left it overnight to download some manga, and then it froze. Then again it probaby may be a ROM issue (its a custom ROM) but just be careful! I lost a 16GB class 4 SD card.
CREDITS:
Thanks to all that have posted to help me, big thanks to (by alphabetical order)
bdgraue
forumber2
kilroystyx
rqmok
reserved thanks to people named in the process written, especially forumber2 for his help in his post and his partition.zip. Without his post, he would not have triggered my thought process in thinking out of the box to unbrick my phone.
and a big thank you to YOU for reading, and (IF) responding to this thread to help make this thread better.

i made the same mistake, i would guess you formatted the /boot too.
you now have to take an original huawei rom, 2.3.5 will be suitable, and follow some instructions you should find in this forum already.
than u have to root your device again and install the rom you need.

Yes, you need to install the official 2.3.5 firmware again. Download it from Huawei's official website.

http://forum.xda-developers.com/showthread.php?t=1420728
in this thread you find almost every information about rooting the device.
and http://forum.xda-developers.com/showthread.php?p=22682229#post22682229 there are the instructions about installing the original rom
gl&hf

still does not work (pink screen)
Hello everyone, I did my homework by searching, but alas I could not revive my phone. (U8800)
How did it bricked: Installed CM10.1 v7, (ran fine, had to re-flash because i read that one must do /format system, /format cache, somehow probably i deleted something i wasn't supposed to, and now its bricked)
Symptoms:
1. Press power button: Blue Screen. This includes Power button and volume + together. Blue Screen. (NOTE: Huawei logo flashes briefly for less than 1 sec before screen goes blue)
2. Press power button and volume + & - together: Pink Screen.
3. (new#)Cannot access from Windows 8 (I have drivers installed, will not detect. Every time i plug the phone into win8 the phone boots up blue) but can't see internal SD.
What I know:
1. This is a U8800
2. CWM 5.5.0.4 was installed (it was bricked after i clear and format, and cannot re-enter the CWM anymore, it goes into pink screen instead)
3. Internal SD is not read-able. (this was documented when i wrote my issue, another forumer by the name of rqmok says its fine because i updated the partitioned.zip, therefore even if it cannot be read, but if it can be accessed from the android file browsers, it is okay. I believe him)
4. I can boot up the huawei + bluescreen, but no
What I did:
1. Because i was at CM10.1 v7, i renamed the entire thing as update.zip and place into external sd root folder . RESULT = nothing. just pink screen
2. grabbed an update (Gingerbread) from XDAFORUM u8800 wikipedia page (the international version), place as update.zip in external sd root folder. RESULT = nothing. just pink screen.
3# (new) I unplugged battery and the external SD, plugged the phone via USB to computer. Boot up (few seconds of Huawei logo) then bluescreen.
Yes, I understand that others have asked about this and somehow revived. What I've read, and understood was:
1. Blue screen = something about ./boot was deleted, and needs to be reinstalled.
2. Pink screen = still safe, has a chance to revive the phone.
What i do not understand:
1. Put ROM files as update.zip, but pink screen does not flash into any form of recovery.
2. Somebody from somewhere said use something called ubuntu / bt5 to "dive" into the phone's internal SD. (I don't know how to do this, and from what i understand it is risky because it involves partioning the internal SD again.
3. Any other way to rescue my phone?
What I would like to ask is some form of step by step help.
I would be very grateful if anyone can lend me some assistance. This is my first android phone (yes i'm a poor fellow) and its not even a week old. I do have an AcerA500 tablet and i have been able to update that tablet to any custom variations (ever since i owned it roughly 2 years ago), so i'm pretty confident that i am good in following instructions)
EDIT:
Okay, i'm able to update the firmware by doing the following:
1. PUT "DLOAD" folder into EXTERNAL SD, root.
2. Pull out battery.
3. Stick USB into the port, and into computer.
4. PRESS VOL+,VOL- and POWER together (Reboot into pink screen)
FIRMWARE UPDATE PROGRESS. it should be 1/2 then 2/2.
"Do Not turn off the device".
AFTER finishing step 4 (it takes some time)
there will be a "TICK" and it will say "RESTARTING".
And then the HUAWEI FLOWER (no animation).
And it repeats itself....
What do I mean by repeat itself?
1. BLANK
2. HUAWEI WITH FLOWER (NO ANIMATION)
After this, there is a green android picture and says "FORMAT /CACHE" and something like that.
Then it goes blank and huawei flowr (no animation) again, and again, and again.
*NEWv2*
I can enter the the blue colored Android system recovery *3E* screen.
formatted / data reset
it has formatted all (at first cannot format cache, causes many problems, now finally fixed). So somehow I managed to format data and clear cache.
It finally reboots. It starts up. And I thought problem over. It was not.
First time boot up was okay. It asks me to set up android, etc. Second time boot up, it will get stuck in a boot loop. Help!
I'm stuck here. Any help?

Can you access to phone from PC while pink screen?

forumber2 said:
Can you access to phone from PC while pink screen?
Click to expand...
Click to collapse
no, unfortunately no.
When I press the volume + up buttons, i can access the blue native recovery.
I updated my post as above.
Can you help me?
NEW:
again, it boots! But 2nd boot will cause issues like process.android.acore and process.google something something has stopped.
can you guys help me on this last one? (i've recorded what i've done and what happened and how i fixed it in previous post. will edit all posts later to do a proper walkthrough.

badiyee said:
no, unfortunately no.
When I press the volume + up buttons, i can access the blue native recovery.
I updated my post as above.
Can you help me?
Click to expand...
Click to collapse
Can the recovery detect sdcard?

forumber2 said:
Can the recovery detect sdcard?
Click to expand...
Click to collapse
yes, the recovery can detect the EXTERNAL SD.
But Internal SD, no. but when i click wipe data, and wipe cache (i think it does it on internal sd) it has no issues.
Again, first time boot =OKAY!
2nd time boot = F.C, all apps.
list of errors said:
The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly. Please try again)
The process android.process.acore has stopped unexpectedly. Please try again
Click to expand...
Click to collapse
I suspect the errors happen because of the fact that i installed JELLY BEAN CM10.1 v7 before, and flashed the gapps too.
Do i need to reflash gapps to GB version after formating the system? What should I do?

badiyee said:
I suspect the errors happen because of the fact that i installed JELLY BEAN CM10.1 v7 before, and flashed the gapps too.
Do i need to reflash gapps to GB version after formating the system? What should I do?
Click to expand...
Click to collapse
did you flash the original huawei rom first? or do you try to flash some custom rom immediately.
which version of original rom do you flash, when u do so?

bdgraue said:
did you flash the original huawei rom first? or do you try to flash some custom rom immediately.
which version of original rom do you flash, when u do so?
Click to expand...
Click to collapse
I flashed the original Huawei Rom first. I know i cannot flash custom rom because the recovery is *3E* recovery, not the CWM/TCW recovery.
any ideas?
I've recorded the errors.
Should I try to reinstall the original HUAWEI ROM again?
okay tried flashing Gingerbread GAPPS (FAIL SIGNATURE!)
formating data and cache again...
*ADD MORE INFO*
Huawei ROM via phone status says this
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Did I do any mistakes?

badiyee said:
Should I try to reinstall the original HUAWEI ROM again?
Click to expand...
Click to collapse
thats what i would do. first flash the huawei rom. start it, look that it works properly. after that i would root the phone, start again and look that all work as expected. then install rom manager and flash the cwm recovery, start again. boot into recovery, start again, always look if the phone is still working as it should. than take a good rom(aurora or cm10.1 v7) and flash it.
as often as you try it out and test if it all works as expected as early you can find out where errors come from.
only flash gapps if the rest works fine.
(which version of gapps do you try to flash? gapps-jb-20130301-signed.zip worked best for me over here)
Edit: http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDEyNTU=
this ist official 528 which worked very well for me. maybe 526 isnt the best suitable.

bdgraue said:
thats what i would do. first flash the huawei rom. start it, look that it works properly. after that i would root the phone, start again and look that all work as expected. then install rom manager and flash the cwm recovery, start again. boot into recovery, start again, always look if the phone is still working as it should. than take a good rom(aurora or cm10.1 v7) and flash it.
as often as you try it out and test if it all works as expected as early you can find out where errors come from.
only flash gapps if the rest works fine.
(which version of gapps do you try to flash? gapps-jb-20130301-signed.zip worked best for me over here)
Click to expand...
Click to collapse
This is the SAME ERROR i'm facing.
http://forum.xda-developers.com/showthread.php?t=2146478
I tried flashing gapps-20110828 it gave error. I also have the gapps jb20130301 file as well. But when i flash the GB gapps it says failed signature verification
QUESTION: could the partition be a problem because i used custom partition!

THANK YOU!
Thanks to everyone!
I have fixed the problem.
I will now re-write the ENTIRE post to help others that have similar issues as mine so that they would not need to be lost like I was.
Thanks again everyone!

badiyee said:
Thanks to everyone!
I have fixed the problem.
I will now re-write the ENTIRE post to help others that have similar issues as mine so that they would not need to be lost like I was.
Thanks again everyone!
Click to expand...
Click to collapse
I'll suggest you to install the patch from blefish if you are using B522, B526 or B528 as rom base.
You don't know when will be helpful to have a bootloader unlocked.
Find here: http://forum.xda-developers.com/showthread.php?t=1457490

kilroystyx said:
I'll suggest you to install the patch from blefish if you are using B522, B526 or B528 as rom base.
You don't know when will be helpful to have a bootloader unlocked.
Find here: http://forum.xda-developers.com/showthread.php?t=1457490
Click to expand...
Click to collapse
Question, how would I know my base ROM? I have read the thing, but there isn't a way in my status to know that its a B522, B526 or a B528 based ROM.
Answer: Look at the code of the installer:
E.G:
U8800V100R001C00526G001 means I have base 526 installed (LOCKED BOOTLOADER)

badiyee said:
Question, how would I know my base ROM?
Click to expand...
Click to collapse
badiyee said:
Huawei ROM via phone status says this
Android version
2.3.5
Baseband version
404020
Kernel version
2.6.35.7-perf
[email protected] #1
Build number
U8800V100R001C00526G001
Click to expand...
Click to collapse
at least after installing you will find the information in the area yoou mentioned yourselve.
if you use the original rom, the version should be in the filename. (U8800_Android 2.3 V100R001C00B528G001%28通用版%29.zip for me)

Wait, is your current recovery CWM recovery? If yes, try installing Aurora ICS. If no, first try rooting your phone and installing CWM recovery.

badiyee said:
Question, how would I know my base ROM? I have read the thing, but there isn't a way in my status to know that its a B522, B526 or a B528 based ROM.
Answer: Look at the code of the installer:
E.G:
U8800V100R001C00526G001 means I have base 526 installed (LOCKED BOOTLOADER)
Click to expand...
Click to collapse
Official Huawei GB roms have 3 different bootloaders, B517, B518 and B522, the first two are unlocked this mean you easily can reach to eMMC via pink screen. For B522 bootloader that comes into rom B522, B526 and B528 Huawei changed the way how to communicate, so we can’t reach eMMC via pink screen mode. To check if it is unlocked in pink screen mode connect to PC, if you can see the folder “image” your bootloader is unlocked.
Blefish explained in his topic that you have more chances to recover your device from soft-brick if you have a unlock bootloader because you are able to restore your device with a previous full backup done with “dd” command or with a similar program used in windows platform.
Change partition size have a high risk to corrupt them and get a soft-brick.
To have more chances to recover my device I usually follow some steps before start play with roms, see my checklist:
- Install B528
- Root the device
- Imei backup (if I haven’t done previously)
- Install CWM
- Flash Blefish’s patch, alternative I use my patch because I need my phone with SIM unlocked
- Full backup (if I haven’t done previously)
- Ready to play

rqmok said:
Wait, is your current recovery CWM recovery? If yes, try installing Aurora ICS. If no, first try rooting your phone and installing CWM recovery.
Click to expand...
Click to collapse
I think at the time of writing AURORA ICS is the most stable, usage-ready, and most complete ROM as of writing. In the future hopefully the newer ROMs like Jelly Bean, Key Lime Pie and others will be able to fit in, and be a PROPER, USABLE ROM just like how AURORA ICS and the MIUI ICS was for this phone.
kilroystyx said:
Official Huawei GB roms have 3 different bootloaders, B517, B518 and B522, the first two are unlocked this mean you easily can reach to eMMC via pink screen. For B522 bootloader that comes into rom B522, B526 and B528 Huawei changed the way how to communicate, so we can’t reach eMMC via pink screen mode. To check if it is unlocked in pink screen mode connect to PC, if you can see the folder “image” your bootloader is unlocked.
Blefish explained in his topic that you have more chances to recover your device from soft-brick if you have a unlock bootloader because you are able to restore your device with a previous full backup done with “dd” command or with a similar program used in windows platform.
Change partition size have a high risk to corrupt them and get a soft-brick.
To have more chances to recover my device I usually follow some steps before start play with roms, see my checklist:
- Install B528
- Root the device
- Imei backup (if I haven’t done previously)
- Install CWM
- Flash Blefish’s patch, alternative I use my patch because I need my phone with SIM unlocked
- Full backup (if I haven’t done previously)
- Ready to play
Click to expand...
Click to collapse
Ah, i forgot about the IMEI backup. But since mine wasn't an issue (just missing serial number, but can be found at the sticker behind phone (inside) anyways haha.