Related
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.
Well... Seems like we've got ourselves a new bootloader, after flashing the BETA1 Gingerbread for U8800. Not cool...
I tried it and didn't like it.
Furthermore, I wanted to keep my device in that zen condition which allows me to return it to my carrier under warranty.
I've tried to revert to my carrier stock ROM, but to no avail. I can run froyo alright, but the carrier costumizations are simply ignored, courtesy of the new bits that came with Huawei's beta.
Some time ago, and antecipating something like this, I connected the mobile, while in pink screen mode, to a linux box and dd'ed the entire volume to a dump file. I can mount this dumpfile through /dev/loop and confirm it carries the same partition schema that is present in the mobile. I'm tempted to dd it back to the mobile, to restore it, but affraid of bricking it for good. If bootloader gets invalid then nothing short of a factory j-tag flash will solve it, for sure.
Has anyone done this before?
Thanks in advance.
EDIT: It worked. The whole volume was restored (bootloader included, naturally).
Greetings,
Everything else aside, claiming that the installation of a manufacturer released upgrade (yes, even one labeled Beta) automatically voids your device's warranty pretty wild. That's not to say that someone somewhere won't make that argument, but there are plenty of crazy people in the world.
That said, good luck.
bonowax said:
Well... Seems like we've got ourselves a new bootloader, after flashing the BETA1 Gingerbread for U8800. Not cool...
I tried it and didn't like it.
Furthermore, I wanted to keep my device in that zen condition which allows me to return it to my carrier under warranty.
I've tried to revert to my carrier stock ROM, but to no avail. I can run froyo alright, but the carrier costumizations are simply ignored, courtesy of the new bits that came with Huawei's beta.
Some time ago, and antecipating something like this, I connected the mobile, while in pink screen mode, to a linux box and dd'ed the entire volume to a dump file. I can mount this dumpfile through /dev/loop and confirm it carries the same partition schema that is present in the mobile. I'm tempted to dd it back to the mobile, to restore it, but affraid of bricking it for good. If bootloader gets invalid then nothing short of a factory j-tag flash will solve it, for sure.
Has anyone done this before?
Thanks in advance.
Click to expand...
Click to collapse
is the dump file around 4gb then yes it will work I did it my self through restoring raw sd image
Sent from my u8800 using xda premium
By the time I red your reply, my mobile was already back to Zen state. Thank you nevertheless.
On a side note: the battery was very low by the time I initiated the restore, but since it was connected through USB, I assumed it wouldn't be an issue.
It took around 45 minutes to restore the image and when finished, the battery was exhausted to the point that I couldn't turn the mobile on. Thought I had bricked it for good...
Charged overnight and everything was fine and dandy.
Cheers
mine took 25min
I managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal SD and it worked (Take off the external SD first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied CWM recovery in the pink screen and it works now too. Then i was able to install Miui again.
straight restore did not work for some reason, maybe needs to format everything first?
sanpsa said:
i managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal sd and it worked (take off the external sd first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied cwm recovery in the pink screen and it works now too. Then i was able to install miui again.
Straight restore did not work for some reason, maybe needs to format everything first?
Click to expand...
Click to collapse
man you are the king!!!!!!!!!!!!!
Thanks you
sanpsa said:
I managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal SD and it worked (Take off the external SD first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied CWM recovery in the pink screen and it works now too. Then i was able to install Miui again.
straight restore did not work for some reason, maybe needs to format everything first?
Click to expand...
Click to collapse
Yes, I had it running FROYO back too, but the phone's condition wasn't the same as before.
If I understood it correctly, the 2.3.5BETA rewrites de boot partition - the 2nd primary parition on the device, marked bootable. This becomes obvious when the "IDEOS" logo is replaced by the "HUAWEI" one during device boot-up.
The partition scheme is the same as before, however, as I had the chance to confirm.
Flashing a 2.2.1 ROM from Huawei did not write the old bootloader back, furthermore this might not be the only change.
I was able to revert to an overseas 2.2.1, both through CWM restore and "dload" method, but carrier customizations were always absent.
Along with the regular system, my carrier's ROM adds a batch of apps, ringtone, wallpaper, binaries and libs, under "cust_data/tmn/pt". These were all ignored. Not that I cared much for them, but as I stated in the original post, I wanted it back in the original condition, as TMN will consider warranty void if the device has been tampered with.
Since I had a raw dump of the volume I restored it back and got my mobile as it was some 3 weeks ago... To my relief...
Can you please make a tutorial to make and restore raw backups?
1. Step : Download a official 2.2.2 rom
2. Step : Put the dload folder at the root of your sd-card
3. Step : Power your device of and boot into bootloader by pressing volume +, volume - and power (before you do that, you can do a titanium backup)
4. Step : Wait till the prozess is done. When your device doesn't reboot by itself, reboot it manually. (if there are any problems with the rom, wipe cache and date with the original recovery)
5. Step : Download a CWM recovery. Boot your device like the same way above into the bootloader. Rename the CWM recovery you've downloaded before into recovery.img
(6. Step : Rename the recovery of your device in the folder (device):/image into recovery.img.orig, to do a backup of the original recovery)
7. Step : Put the new recovery.img in the folder from above. Unplug your phone from the PC and put the battery out to turn it off. Boot it into recovery by pressing volume + and power.
Congratulation, you've restored your Ideos X5 to 2.2.2.
Now you can download a custom rom and install it by the normal way.
FabioAreia said:
Can you please make a tutorial to make and restore raw backups?
Click to expand...
Click to collapse
Good sugestion... Will start a new thread for it.
IDEOS X5 - Update dead drives bootloader - help me
4. Use the English language.
We understand that with all the different nationalities not everyone speaks English well, but please try. If you're really unable to post in English use an online translator, You're free to include your original message in your own language below the English translation.
Click to expand...
Click to collapse
MOD EDIT: Please read the forum rules.
how can we restore a raw dump?
dd if=[image filename] of=/dev/[block device allocated to the U8800] bs=512
Search the forums for the complete tutorial...
Ok, as many of you know, the only thing between custom ROMs and your phone is the fact that we can not get the ROMs that we make to flash correctly in our current CWM recovery. We either get status 0, status 1, status 6, or status 7 errors when flashing. Most of these errors directly correlate with the boot.img command line(s) in the updater script.
uoY_redruM and I have spent over ten hours a piece trying to figure this out and have made progress but are still stuck.
We soon found out that the kitchens we were using to cook our ROMs did not have the latest directory for our phones partitions and their addressess (mmcblk0p1, etc.) This directed us to where we need to look to fix this.
The critical partitions we need to make ROMs flash are
1. Data
2. System
3. Boot
4. Cache
5. (optional) SDCard
It was easy enough to find 1,2, & 4, however the boot was a little bit trickier.
There are drives on our phone that had the following IDs:
1. mmcblk0p5 aboot
2. mmcblk0p7 boot
3. mmcblk0boot1 disk
4. mmcblk0boot0 disk
We believe that the real boot partition is 7, however we have yet to get a fully functional ROM up and running, despite writing the boot.img to p7.
With certain modifications to the boot.img lines in the updater script, I have been able to flash a ROM, but upon boot I lose SU permissions and the radio is borked (does not detect SIM card). Clearly this is still not functional and is caused by the boot.img (kernel) not being included in the ROM.
Attached is a scanned copy of a list of all of the partitions in our phone, along with their ID.
This is a thread where we can easily bounce ideas off of each other and hopefully get to the root of this problem ASAP.
Let's please keep this on topic. Thanks.
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Reviewers said:
Status 7 is updater-script which means ur close I'm pretty sure or the Recovery needs to be remade for our phone like I said before.
Click to expand...
Click to collapse
Yeah, we're starting to think it's recovery related.
We've (well most he) got the ROM to boot up now....but......and that's a big but.....it reads as if we have no SIM card. So, that's where we're currently stuck.
Same place boots loads kernel but no root or radio same sim card error
Wildchld said:
Same place boots loads kernel but no root or radio same sim card error
Click to expand...
Click to collapse
Are you using an insecure boot.img?
FiveOhFox said:
Are you using an insecure boot.img?
Click to expand...
Click to collapse
yep
Built in the kitchen
---------- Post added at 06:46 PM ---------- Previous post was at 06:41 PM ----------
I think it maybe the recovery too because I have lost root on restores
Wildchld said:
yep
Built in the kitchen
Click to expand...
Click to collapse
Ok. I'm trying it with secure boot.img files to see if that has any bearing on our results but so far nothing.
Ok well I'm going to shelf working on the script for a while and instead start working on my ROM and possibly learning how to make a recovery lol.
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Reviewers said:
It's the recovery then.
We need a recovery made for our phone, should have listened to my thread of what I said.
Oh well, we just need somebody to work on a Recovery.
Wish I could help but I don't know ANYTHING about compiling a recovery.
Click to expand...
Click to collapse
Why are you so adamant that it's the recovery?? You don't even own the phone!
I owned the amaze before and it didn't flash with 1 recovery but it worked on another.
I know this is Samsung but another user is agreeing with me as well.
Read the thread I made in General.
Flashing something from another phone will never work 100% as made for that phone.
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
Plus when I get the phone I'll look into it as well.
I might not be much help in this area but I'll do what I can.
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
uoY_redruM said:
Anybody have any insight?
We've about hit our ceiling. I know I have for sure, I think Five still has some tricks up his sleeves somewhere
Using his updater-script we can get a boot but no radio. My thought is the radio isn't flashing properly (maybe a corrupt img file?) or it's not mounting properly somewhere?
Also, if you look at the International Galaxy SIII ROMs, some of them have flash_image, modem.bin and recovery.bin in their update script and the updater-script points to them to be written. That leads me to believe perhaps we have to make the radio flash...I'm just spit balling here. Also, the modem.bin files in the international ROM kind of makes me think there is a file missing somewhere in ours.
I pulled the system.4ext.tar/boot.img rom our ROM and used Cygwin kitchen to build it fresh, replaced the updater-script with Five's, got a boot and no radio. If I replace the updater-script with the one from the International ROM (and change the mount points in the script) I get Status 6 error.
Anybody have an opportunity to look at this, or maybe has experience in fixing this, speak up please!!
Another ~10 hours put into this today and no farther then yesterday
Click to expand...
Click to collapse
If you use the update-binary from the EU rom the status 6 error goes away but same results but the kernel will load. Status 6 error is a syntex error not because of the script but the binary is looking for different parameters.
Also I see no Sprint roms being dev maybe they have the same problem
One last shot before work... Attached is a working script and binary
Rom boots fine and about shows baseline unknown so maybe we need to load the radio in the rom also.
Also when I restore a nandroid radio comes back but won't connect till I turn off wifi then service returns.
Here's the thing I found odd....
If you use CWM to pull a backup, the boot.img/recovery.img are both 10MB in size.
If you use the Toolkit to pull a backup, the boot.img/recovery.img are 2MB/512KB.
Why is that? That doesn't make any sense to me. They should be duplicate but they're not.
....the only thing that comes to mind is maybe the Toolkit (since it was designed for the international phone) points to different partition points and aren't pulling the correct files? Then again, why would they be named properly?
That's where I'm at for today.
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
uoY_redruM said:
OK, could have a problem.
I ran it with your updater-script and it booted up like you said with no radio. However, when I turned it off and tried to get back into recovery, I keep getting put into Odin. It appears my recovery was overwritten? I can boot the phone back up but I cannot restore my working Nandroid now *yikes*
Got to figure this one out...
Yeah, that's exactly what happened. I can't get into recovery now. Need to figure out how to flash the recovery back.
In the mean time, my phone is useless. At least it boots up but I have no radio...
EDIT-
Fixed. Re-ran Odin/CWM Install. We're good.
Now I know the recovery.img I pulled from the backup is bad! That's the recovery I had it flash and ended up with no recovery. Hmmmm...
Click to expand...
Click to collapse
You used the recovery.img from what, again? And the script posted above writes to p18 which is recovery so that's not a problem.
So it boots but is missing radio? Do you have root?
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Wildchld said:
I used the above script and binary it boots and loads the kernel and recovery fine and everything works but no root or radio. I have not tried removing the boot and recovery but don't think that will make a diff. I will try tonight. Also will pull boot and recovery from my working nandroid to see if that works.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
uoY_redruM said:
Be careful when you do that. I included the recovery.img from the Nandroid in the root of the zip and that's what caused me to not be able to access recovery (I had to re-flash recovery using Odin).
Click to expand...
Click to collapse
Lol your right but i have loaded this nandroid like 30 times i know its good
Sent from my SGH-T999 using Tapatalk 2
FiveOhFox said:
Ok. We are adding files and commands to flash the modem.bin that Rum pulled from his phone to see if that fixes radio issues.
Click to expand...
Click to collapse
Found a few more files that could be of use. Five is writing up some commands to try flashing them.
I'm starting to feel really good about today!
I live in the Houston area. Bricked my A500 will pay you to fix email me . I went from CWM v5 1.3.4 to 1.7 and now I can only go into boot loader but nothing can be applied , tried different ROMS wipe everything still nothing
[email protected]
If I lived in Houston I would try to help you, can't you get into recovery? What happens when you connect to your PC ?
twistedknickers said:
If I lived in Houston I would try to help you, can't you get into recovery? What happens when you connect to your PC ?
Click to expand...
Click to collapse
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Moscow Desire said:
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Click to expand...
Click to collapse
I have a similar problem. Bootloader V8 installed fine. But when I flashed different ROMs through CWM (install zip from SD card inside recovery), it hung at the screen "CZ's Bootloader V8, booting primary kernel" forever. Scratched my head for a couple of nights now, wondering what the glitch was. I even tried Bad Sector's V8 green. Same result. Help!!!!
Edit: I can still downgrade by flashing EUU (though not TD's V4, which installs fine but won't boot back up once I turn it off and on again???). Anyway, running HC 3.0.1 does make you feel like a Neanderthal. A clear instance of cruel and unusual punishment, I'd say. Even HC 3.2 won't stick! WTH?
Quandary unsolved
Moscow Desire said:
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Click to expand...
Click to collapse
Hello. Anyone? How about Mockba the Great? I'll do more than thank. I'll grovel at your feet (lol); or fly to your city vodka bottle in hand. Be compassionate and tell me something. Anything. Like my tablet is shot beyond salvage, so I can put it to rest. Why is it that I can flash EUU and use without problems but not any other upgrades? Is it possibly because of physical bad sectors lying in the path of data from the new roms (sizably larger than HC)? Or automatic remapping of NAND shot to hell? There's got to be some explanation.
graphdarnell said:
Hello. Anyone? How about Mockba the Great? I'll do more than thank. I'll grovel at your feet (lol); or fly to your city vodka bottle in hand. Be compassionate and tell me something. Anything. Like my tablet is shot beyond salvage, so I can put it to rest. Why is it that I can flash EUU and use without problems but not any other upgrades? Is it possibly because of physical bad sectors lying in the path of data from the new roms (sizably larger than HC)? Or automatic remapping of NAND shot to hell? There's got to be some explanation.
Click to expand...
Click to collapse
I am not sure, but, I have the same problem. If I flash the EUU (Acer stock 3.01) , I can spend a couple of hours following the upgrade path all the way to ICS 4.03, then it seems no matter the boot loader/recovery combo I flash, I either end up stuck in APX, or I get the new boot loader/recovery, and the original Rom boots fine, but when I try to flash using fast boot I end up with the android on his back with the red exclamation.
It may or not be related, but the very first time I tried flashing a new ROM, I ended up stuck in APX, & the only way I could find to get out was to use Badsector. The next Rom I flashed left me again in APX, so, the first thing I went back to was BadSector, & it would not work. (Can't remember what the error was, but it wouldn't get far before stopping.) So, I tried APXFlash & it worked perfect. (Before I ran BadSector the first time I could not get APXFlash to work at all.)
Now I can flash as often as I want, but still can't get anything to work right. (Except Stock stuff????)
Danny2 said:
I am not sure, but, I have the same problem. If I flash the EUU (Acer stock 3.01) , I can spend a couple of hours following the upgrade path all the way to ICS 4.03, then it seems no matter the boot loader/recovery combo I flash, I either end up stuck in APX, or I get the new boot loader/recovery, and the original Rom boots fine, but when I try to flash using fast boot I end up with the android on his back with the red exclamation.
It may or not be related, but the very first time I tried flashing a new ROM, I ended up stuck in APX, & the only way I could find to get out was to use Badsector. The next Rom I flashed left me again in APX, so, the first thing I went back to was BadSector, & it would not work. (Can't remember what the error was, but it wouldn't get far before stopping.) So, I tried APXFlash & it worked perfect. (Before I ran BadSector the first time I could not get APXFlash to work at all.)
Now I can flash as often as I want, but still can't get anything to work right. (Except Stock stuff????)
Click to expand...
Click to collapse
This is my guess: I was able to get someone with the right equipment to probe into the NAND and scan. The result shows random bad sectors all over the place. The scan lasted for more than a day without finishing, so eventually remapping could not be executed. If the capability of the NAND to remap is exhausted then depending on your luck, if the ROM data fits into good sectors, you get to use the unit. If the cache partition has black holes in it, you'll get errors and operational aberrations. If I'm right, then this is purely a hardware issue which will come back to haunt sooner or later. Makes sense?
Since the NAND is soldered onto the Main Board, there is little chance of replacing the NAND, if you can find one, that is. Darn it!
graphdarnell said:
I have a similar problem. Bootloader V8 installed fine. But when I flashed different ROMs through CWM (install zip from SD card inside recovery), it hung at the screen "CZ's Bootloader V8, booting primary kernel" forever. Scratched my head for a couple of nights now, wondering what the glitch was. I even tried Bad Sector's V8 green. Same result. Help!!!!
Edit: I can still downgrade by flashing EUU (though not TD's V4, which installs fine but won't boot back up once I turn it off and on again???). Anyway, running HC 3.0.1 does make you feel like a Neanderthal. A clear instance of cruel and unusual punishment, I'd say. Even HC 3.2 won't stick! WTH?
Click to expand...
Click to collapse
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Danke schoen dibb nz
dibb_nz said:
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
This gives hope. With TD V4, it stops at power on - power lights on (white LED), but screen remains dark. Thanks for sharing your experience, I will definitely try when I get back to it at the end of the month. So if I'm slow in posting the outcomes, you know why. One more favor to ask: what do you do after fixing permissions while on earlier EUU (I remember seeing that option somewhere in the recovery menu)? Should I proceed to flash V4, then move up from there? If I install V8 Bootloader while on V4's ROM, would that hinder further flashings in any way? Many thanks again. And what is going on now with your JB ROM? And Happy Thanksgiving to all the Yanks in here!
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD
Thanks MD
Moscow Desire said:
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD
Click to expand...
Click to collapse
Can't thank you enough MD, and dibb_nz too. Can't wait to get back to the tablet. Hopefully things will work out. When they do, I'll post the results for the perusal of similarly situated members.
graphdarnell said:
This gives hope. With TD V4, it stops at power on - power lights on (white LED), but screen remains dark. Thanks for sharing your experience, I will definitely try when I get back to it at the end of the month. So if I'm slow in posting the outcomes, you know why. One more favor to ask: what do you do after fixing permissions while on earlier EUU (I remember seeing that option somewhere in the recovery menu)? Should I proceed to flash V4, then move up from there? If I install V8 Bootloader while on V4's ROM, would that hinder further flashings in any way? Many thanks again. And what is going on now with your JB ROM? And Happy Thanksgiving to all the Yanks in here!
Click to expand...
Click to collapse
Well after u fix permissions u boot straight back into cwmand flash the v8 and civatos cm 10 flex, which is exactly what I did after getting it up n running again. edit: no, u need the latest tdv4 - ...I'll post the link for it shortly....
I'd definitely uninstall the Acer drivers and reinstall them. When u connect to yr PC , windows will try to install the drivers....don't let it search windows updates, u have to be quick to cancel it....then it should install the drivers from the acer folder on yr PC which u just reinstalled....is that clear as mud, lol???
One more thought, u could get round all this driver business if u know linux at all....
But will w8 till u get a chance to spend some quality 'tab time'
Sent from my A500 using Tapatalk 2
Moscow Desire said:
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
MD
Click to expand...
Click to collapse
So, this might seem kind of obvious, but I want to be sure. I found the Recovery-from-boot.p file easily enough, and I found a file called "Install-recovery.sh" in the etc folder, which seems to call another file called "system/bin/sh".
So, do I delete (or possibly just re-name??) "recovery-from-boot.p" and "Install-recovery.sh"? And do I need to do anything with the "SH" file in "system/bin"? (Like delete or re-name?)
Thanks for this much clearer (but still not 100% clear) info about these files. I had read mention of "recovery-from -boot.p" in another post, but it didn't make clear where to find it, just that you needed to deal with it. This excellent post makes it much more obvious which files & where to find!
Danny2 said:
So, this might seem kind of obvious, but I want to be sure. I found the Recovery-from-boot.p file easily enough, and I found a file called "Install-recovery.sh" in the etc folder, which seems to call another file called "system/bin/sh".
So, do I delete (or possibly just re-name??) "recovery-from-boot.p" and "Install-recovery.sh"? And do I need to do anything with the "SH" file in "system/bin"? (Like delete or re-name?)
Thanks for this much clearer (but still not 100% clear) info about these files. I had read mention of "recovery-from -boot.p" in another post, but it didn't make clear where to find it, just that you needed to deal with it. This excellent post makes it much more obvious which files & where to find!
Click to expand...
Click to collapse
Just those 2 files
This will prevent overwriting your custom recovery on boot.
MD
Moscow Desire said:
Just those 2 files
This will prevent overwriting your custom recovery on boot.
MD
Click to expand...
Click to collapse
OK, Thanks
Progress report
dibb_nz said:
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I was able to follow MD's instructions and installed Re-Flexxx Rom. As to dibb-nz's advice, I couldn't find earlier versions of TD (there was a link that led to some silly software instead - hijacked?). So I reflashed V4 which after the first reboot took me to the setup part fine. However, a second reboot resulted in a dark screen with nothing doing. I tried accessing recovery in vain. I'm not sure earlier TD versions would yield differently. If I recall correctly, V4 only differs from V3 in that TD added XP drivers. Why the tablet behaved thus is beyond me. I intended this superfluous info as a warning to such possibility, however absurd it might appear.
Anyway, thanks to those who came to the rescue, and Merry Xmas to all.
graphdarnell said:
I was able to follow MD's instructions and installed Re-Flexxx Rom. As to dibb-nz's advice, I couldn't find earlier versions of TD (there was a link that led to some silly software instead - hijacked?). So I reflashed V4 which after the first reboot took me to the setup part fine. However, a second reboot resulted in a dark screen with nothing doing. I tried accessing recovery in vain. I'm not sure earlier TD versions would yield differently. If I recall correctly, V4 only differs from V3 in that TD added XP drivers. Why the tablet behaved thus is beyond me. I intended this superfluous info as a warning to such possibility, however absurd it might appear.
Anyway, thanks to those who came to the rescue, and Merry Xmas to all.
Click to expand...
Click to collapse
can u provide a link 2 the tdv4 u used i will check it.....seems couple folks having yr issue, i wanna make sure the zip isn't corrupt...
ALSO: there are 2 ways to use the EUU -
1) as an upgrade tool - used to upgrade from one HC build to the next - just open and run with usb connected and
2) as a downgrade too - used to downgrade from the ICS back to HC - you run it by not connecting your usb cable and force apx mode
Im curoius as to why folks are getting stuck with the black screen - this happened couple months back too
and tho i have been stuck with it myself - i have never been able to replicate the issue..and believe me when i say i've done some crazy things with my tab in the process of trying... so would like to rule out a bad file...just in case its me causing all the problems, lol....feedback would be appreciated....
Sent from my GT-I9300 using Tapatalk 2
Possibly corrupt V4?
dibb_nz said:
can u provide a link 2 the tdv4 u used i will check it.....seems couple folks having yr issue, i wanna make sure the zip isn't corrupt...
ALSO: there are 2 ways to use the EUU -
1) as an upgrade tool - used to upgrade from one HC build to the next - just open and run with usb connected and
2) as a downgrade too - used to downgrade from the ICS back to HC - you run it by not connecting your usb cable and force apx mode
Im curoius as to why folks are getting stuck with the black screen - this happened couple months back too
and tho i have been stuck with it myself - i have never been able to replicate the issue..and believe me when i say i've done some crazy things with my tab in the process of trying... so would like to rule out a bad file...just in case its me causing all the problems, lol....feedback would be appreciated....
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I'm almost sure I downloaded from the link provided in this thread, though I'd appreciate your not quoting me on it (lol). I remember downloading twice but cannot tell now which is which. Either way, I "upgraded" from HC 3.1 to 3.2, which is the version included in V4. Beyond that, I'm not sure what other information would help sort things out. Oddly enough, the first automatic reboot after flashing works fine and takes me through the whole setup process glitchlessly. It only happens on the following reboot. You can get into recovery 1.5, but fixing permissions won't do.
graphdarnell said:
I'm almost sure I downloaded from the link provided in this thread, though I'd appreciate your not quoting me on it (lol). I remember downloading twice but cannot tell now which is which. Either way, I "upgraded" from HC 3.1 to 3.2, which is the version included in V4. Beyond that, I'm not sure what other information would help sort things out.
Click to expand...
Click to collapse
ok thanks for that - the v0-v2 required all sorts of jumping thru hoops to get root/cwm installed....when u finished the first flash you would end up with a LNX check sum error in red text on your tab and have to boot straight to recovery and fix checksum errors (not permissions as i said earlier)
v3/v4 now comes pre-rooted with cwm 1.5, which is what may be corrupting things if you are still have the v8 bootloader - altho in saying that, a few of us have been on HC3.01 with v8 and had no probs flashing a compatible ICS v8 rom from there...maybe it was just a fluke who knows...One thing I do know is you should really have a compatible recovery with the v8 - which is why all the flash packages come pre-loaded with a custom recovery....as MD said above you need to make doubly sure your rom/reocvery/bootloader are all compatible with each other. this applies whether they be stock or custom 'whatevers'....
Oddly enough, the first automatic reboot after flashing works fine and takes me through the whole setup process glitchlessly. It only happens on the following reboot. You can get into recovery 1.5, but fixing permissions won't do.
Click to expand...
Click to collapse
and you have completed all the wipes as MD suggested, including toggling /data/media erase in cwm?
I realise you may have done everything correctly, this is more for the benefit of those folk "trying" to follow along
this is on 3.2?? you run the EUU ok, boot to android, and run thru the setup wizard, then the next reboot goes awry??
dibb_nz said:
ok thanks for that - the v0-v2 required all sorts of jumping thru hoops to get root/cwm installed....when u finished the first flash you would end up with a LNX check sum error in red text on your tab and have to boot straight to recovery and fix checksum errors (not permissions as i said earlier)
v3/v4 now comes pre-rooted with cwm 1.5, which is what may be corrupting things if you are still have the v8 bootloader - altho in saying that, a few of us have been on HC3.01 with v8 and had no probs flashing a compatible ICS v8 rom from there...maybe it was just a fluke who knows...One thing I do know is you should really have a compatible recovery with the v8 - which is why all the flash packages come pre-loaded with a custom recovery....as MD said above you need to make doubly sure your rom/reocvery/bootloader are all compatible with each other. this applies whether they be stock or custom 'whatevers'....
and you have completed all the wipes as MD suggested, including toggling /data/media erase in cwm?
I realise you may have done everything correctly, this is more for the benefit of those folk "trying" to follow along
this is on 3.2?? you run the EUU ok, boot to android, and run thru the setup wizard, then the next reboot goes awry??
Click to expand...
Click to collapse
I was initially on 3.1 stock. I went to stock recovery which proceeded to erase whatever, then showed the android belly up with the triangle exclamation mark and so forth (The sd card contained no ROM at this point). I rebooted, then flashed V4 directly from inside 3.1 with debugging on. It "PASS" uneventfully, rebooted on its own to the setup wizard. Things function normally within that capsule (it showed HC 3.2 I believe). I turned it off after setup was done, then on again to experience the black SOD. I then went to Recovery 1.5, erase everything a few times, then rebooted. Same result. Eerily dead.
Then came the V8 Bootloader and Thor V20, and the tablet was resuscitated. Works fine now.
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.