Was using the latest version of Oxygen up until yesterday, with a custom partition (by Geno.Kolar), and decided I wanted to update to Aurora.
Followed the instructions linked in the first post of the thread, but didn't revert my partition to original before doing so.
I managed to install the original stock 2.2.1 rom, and then proceeded to install 2.3.4, however it would make it to the boot animation and just cycle through the animation endlessly (though very jerky).
I put my partition table back to originals and tried again, this time the update was failing right at the end.
Decided that I really needed a working phone, so I tried to restore a nandroid backup I had made right before, after restoring the partition table, but it's failing at the data partition.
Seems I'm unable to mount or format the data partition, so I can't install anything.
Any suggestions?
Tried these instructions without luck:
Download mediafire.com/?1hbk6n46hgamyt6
Unzip it, and find UPDATE.APP
Put UPDATE.APP in a dload folder and upload to empty sdcard.
Put sdcard in phone, and hold vol+/- and power and flash it.
After phone has restarted pull battery.
Download http://www.mediafire.com/?6hrfz36b8e2vw87
Unzip and copy the dload folder to empty sdcard.
Hold vol+/- and power and flash it.
After it fails near the end or if it restarts then pull battery.
Download a rooted boot.img and a clockworkmod recovery.img (got both mine from links at modaco)
Attach phone to PC in pink screen mode and delete the boot.img and recover.img files.
Upload the downloaded root.img and recovery.img to image folder in phone.
Download any custom rom from XDA, I used http://forum.xda-developers.com/show....php?t=1475687 and upload it to sdcard
Pull battery.
Hold vol+ and power and go into clockworkmod, wipe everything and flash the custom rom!!
UPDATE:
I can get to recovery (using CWM 5.5.0.4), however if I attempt to format the data partition, it gives me the following E:format_volume: make:extf3fs failed on /dev/block/mmcblk0p13
How would I get around this?
Thanks!
Heh, looks like I haven't.
Managed to get it working again by using Geno's original partition, and then flashing Oxygen again.
Thanks!
Related
I hope someone can help. Originally, when I downloaded Hero beta4 it came with a recovery file. Since I didnt know where it went, I did not adb it over. Now, everytime I wipe (i am now running rosie), it locks up at the Android screen and endless boots. I am sure it is because I am missing my recovery image. I presume I can use any update.zip and rename it recovery.something. My questions are
1. what is this recovery file named?
2. Where does it go? I have app_s installed to my ext2 partition for rosie.
If you boot up without holding down the home key (a normal boot in other words) the system doesn't touch your recovery partition. So having a damaged recovery is likely not the cause of your looping. If you want to install a recovery.img you can just grab it out of a full updater or as a separate file.
Thanks, but you said something interesting. You said recovery partition. Where is that? And would I use ADB to push the recovery file over to where ever?
it only boot-loops when i wipe. If I update, things go smoothly. Until I wipe again. Seems like i am missing the recovery image (since it came with the download but I never moved it).
Thanks jashsu for your prompt response.
pine
I don't think it's the recovery partition. I get kinda the same with tehseano's Hero theme 1.1. When I wipe before applying the update, I get problems with home app. And after, I get a bootloop..
So the night before yesterday before going to bed i connect my ideos to pc and left it charging and went for sleep.
When i woke up i realized that the phone is dead.
Going into recovery tryed to flash my rom again,the process finished really quick
reboot stacked at ideos screen.Cannot format /data.
So reboot ,bootloader purple screen trying to copy my original image,seems ok.
Reboot,nope clockwork again.Boot loader once again same files not my original.
Shift delete recovery image ok,copy original image ok unmount remove usb reboot.
Clockwork again.
Trying to format image drive from windows "Drive is busy"
Connecting to Linux system at bootloader giving a lot of drives.Unmount Image format ok,copy original image ok.Reboot ... clockwork once more.
So one idea that i have is that i have a partition around 600mb which is ext ,and i wonder if the /data is that partition and maybe needs format it fat32.
Any help and ideas would be appreciated.
Using latest cm7 from geno with stock kernel with no problems.
Greek Ideos.
Cheers
Tryed to flash stock firmwares like Overseas b136 and another two all failed to update at the second part.Also i tryed with Genos repartioning tools failed,to be honest didnt try the one wich needs three flashes to restore stock partitions i ll try it later today.
h ttp://imageshack.us/photo/my-images/267/screenshotflb.png
I tried to install officical 2.3 to huawei u8800 and it say i need more space and yes i did it with my micro sd (2gb)
when i deleted images folder and i got blue screen?
can someone help me please!
katu2006 said:
I don't think your phone is bricked.
During the installation of the Stock Roms the recovery.img and boot.img files get replaced/modified and that's why your phone gets stuck at the Huawei logo.
Try the following:
Boot the phone in Bootloader (pink screen) by holding Vol+, Vol- and Power, format the partition with FAT32, create a folder called "image" and copy the following files on there.
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
Once the files are copied, just disconnect the USB cable and remove the battery. Then boot into Recovery by pressing the Vol+ and Power. If you manage to get into CWM Recovery, then it's all good, you can install a custom Rom like Oxygen (
https://sourceforge.net/projects/u8800oxygen/files/ ) by selecting "install zip from SD Card" option.
You'll probably have to use the MOUNT functions within the Recovery to transfer the Oxygen.zip file to your root folder of the SD Card.
Click to expand...
Click to collapse
When you will have custom ROM installed you can try installing offcial 2.3 again (follow the guide that comes with the update and make sure it is for your phone (U8800/U8800pro))
yannn007 said:
When you will have custom ROM installed you can try installing offcial 2.3 again (follow the guide that comes with the update and make sure it is for your phone (U8800/U8800pro))
Click to expand...
Click to collapse
thx dude saved my life but how can i install official 2.3? can you show me some step or should i do the official 2.3 folder into zip? sorry for my bad english
Download the official 2.3.5 from here: http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDM2NDk=
Then format SD and create dload folder on the root of SD card. Then unzip the downloaded update and copy update.app in dload folder. Everything is also described in the pdf that is in the zip of the official ROM
If you find a mirror for the official beta2 version then you can also flash this (beta2 has unlocked bootloader while final has locked bootloader(pink screen))
OK, so I flashed one of the new leaked ICS stock ROMs and it appears that everything is ok. I'm digging all of the features including the panoramic camera. I decide that I want to put on Taboonay for a little flavor. I try to boot into recovery and this is what I get:
Erasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
Yes, I tried to flash a recovery image through the ACER recovery install and the ROM Manager. Both of them flashed an image with no problem, until I actually tried to flash an image.
My question is this: How do I flash a recovery image if my bootloader is busted?
I do have ADB access , so it there a way I can copy a recovery image file directly onto the A500?
I appreciate the help!
xodus1914 said:
OK, so I flashed one of the new leaked ICS stock ROMs and it appears that everything is ok. I'm digging all of the features including the panoramic camera. I decide that I want to put on Taboonay for a little flavor. I try to boot into recovery and this is what I get:
Erasing cache before SD update
SD update cmd: recovery
--update_Package=SDCARD:update.zip
Booting recovery kernel image
(IN RED) Recovery verified failed
Yes, I tried to flash a recovery image through the ACER recovery install and the ROM Manager. Both of them flashed an image with no problem, until I actually tried to flash an image.
My question is this: How do I flash a recovery image if my bootloader is busted?
I do have ADB access , so it there a way I can copy a recovery image file directly onto the A500?
I appreciate the help!
Click to expand...
Click to collapse
Well, not sure if I can get you up and running. This is going to depend on if you followed traditional installation instructions that are posted on every thread that contains a Rom.
But first, let's cover where you went wrong. And that would probably be when you went back to Recovery. It seems, you didn't hit Vol - and PWR, but instead selected Vol + and PWR. And as such, it tried to run an update.zip file, which is a no-no. This resulted in a corrupted image.
Secondly, Rom Manager is a phone app. This will in most cases, bork your tab.
First, I would try Acer Installer (newest version) and try to install RA Recovery. If you were using CWM before, you probably can't flash it again.
If that doesn't work, then you will have to roll back from ICS, and you will need your original UID number. Hopefully you wrote this down somewhere. If you were using RA Recovery, you will find the UID number in the UID.txt on your SD Card in the Recovery folder (if you made a system backup before flashing ICS roms). If you were using CWM, well, it might be buried in one of the .img files in the clockwork folder (again, if you made a backup before flashing ICS). You will have to de-compile the image files to find it (hopefully).
If your ADB seems to be working, you may want to push the RA Recovery;
http://forum.xda-developers.com/showthread.php?t=1459821
If you have your original UID number, then you may want to try this;
http://forum.xda-developers.com/showthread.php?t=1522384
or this;
http://forum.xda-developers.com/showthread.php?t=1516012
Hope you get it going. From what I have seen, mostly when the people lose their recovery, they were using CWM. Haven't heard of any losing it when using RA Recovery. But anyhow, use Acer Recovery first, and try the RA Recovery.
I know, I should have dumped the stock system partition, but I only found about this crypto key thing after the deed was done. Starting from here, what's the quickest way to go back to a functioning phone? After a factory reset all I'm left with is Meticulus TWRP, but being unable to wipe the crypto key I can't flash anything so my phone is crippled. I suppose flashing a stock image from dload would help, right?
vnvman said:
I know, I should have dumped the stock system partition, but I only found about this crypto key thing after the deed was done. Starting from here, what's the quickest way to go back to a functioning phone? After a factory reset all I'm left with is Meticulus TWRP, but being unable to wipe the crypto key I can't flash anything so my phone is crippled. I suppose flashing a stock image from dload would help, right?
Click to expand...
Click to collapse
You need to download official firmware and flash it via dload method. ( The firmware must be the same as the one in your oeminfo file./
Hi, i solved this problem one mouth ago,
1. fotmat adta to ext4
2. install cyanogen mod 13
3. with adb Flash system and recovery
4. put stock firmware in dload folder in sd card
5- vol up +vol - power
6. install stock
7. reboot ok
silviuss82 said:
Hi, i solved this problem one mouth ago,
1. fotmat adta to ext4
2. install cyanogen mod 13
3. with adb Flash system and recovery
4. put stock firmware in dload folder in sd card
5- vol up +vol - power
6. install stock
7. reboot ok
Click to expand...
Click to collapse
In the end I solved the problem with a mix of both the suggested solutions: in other words by:
1) formatting the SD card with gparted on my Arch machine.
2) putting my stuff back on it, plus a stock ROM and CM13
3) flashed stock
4) flashed Meticulus TWRP with adb
5) flashed CM
6) stuck with CM because it's actually pretty good right now, plus it manages multiple storage options better than stock...
Thank you guys for the support.
vnvman said:
I know, I should have dumped the stock system partition, but I only found about this crypto key thing after the deed was done. Starting from here, what's the quickest way to go back to a functioning phone? After a factory reset all I'm left with is Meticulus TWRP, but being unable to wipe the crypto key I can't flash anything so my phone is crippled. I suppose flashing a stock image from dload would help, right?
Click to expand...
Click to collapse
I am a noob have done this many times lol. I just get the newest update and flash it through twrp it still boot loops until turn phone off hold power and up till the logo appears let go of power button factory reset and reboot