Related
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
Your Nandroid backup was on that SDcard...I don't suppose you saved it before formatting it?
lorsoblu said:
Hello everyone,
(Note, I did do a nandroid backup before I did ANYTHING, right after rooting)
I was having some issues with Modaco 1.0 when it was first put out, and like everyone else, got trapped in a reboot loop. Once I saw that the fix was repartitioning to FAT32, I did so, re-flashed the ROM, and I was back in. All was good.
But when 1.1 came out, I really wanted to restore to my backup to start fresh with the new ROM, but it did not work out. When I tried to do so in the recovery console, I got this error - Error: "nandroid-mobile.sh restore" from console! -
What am I supposed to do with that? I went ahead and went through with 1.1, but I am worried I accidentally closed my backdoor at some point. I noticed I lost some things from the basic ROM (such as the default wallpapers, and I had issues with Google Maps), and I am just generally worried something is fishy in there.
Any suggestions?
Click to expand...
Click to collapse
nah. The happens sometimes. Could be your nandroid backup got corrupted or you are low on battery power. Two most common causes. I would make sure the nandroid backup is on the sd card. if so, simply try plugging it in to a power supply. Let us know if you get it working.
All right... I did not want to admit it but I believe what you said is probably true, and I either corrupted or simply deleted the nandroid backup during all the flashing and repartitioning. I am not seeing it at all when I mount the SD card. It crossed my mind a little too late that I should have pulled it off the card.
What are my options here? On the one hand, it is working fine for now. I had just got the Hero earlier that day (did an exchange due to dead pixels and network issues), so it was not like I lost anything important. Is there an easy way for me to go all the way back, such as flashing the original ROM to the phone, and essentially starting over, like I just opened the box and turned the phone on? That way I can do it right from the very beginning. I just worry that in all my partitioning things got scrambled, and I am not seeing the repercussions from it yet, other than Google Maps.
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
if at first you try and fail.... try try agian
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
lorsoblu said:
Thanks for the link.
Is there some process to this? I mean, I understand the whole update.zip concept of flashing the ROM, but would I also need to do a complete wipe of the SD card to achieve the fresh start I am looking for? Should I partition it at only FAT32, or go ahead and setup the ext2 partition before flashing the original ROM?
Click to expand...
Click to collapse
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
johnsongrantr said:
convert sd card to "SDPART:fat32 only" from custom recovery
et the official RUU wipe your phone
enable USB debugging in settings>applications
reroot your phone using asroot exploit
make any partition changes you want
do a nandroid backup
do a nandroid restore to verify it works
backup on your workstation /sdcard/nandroid
DO NOT TOUCH YOUR SD PARTITION TYPE AT THIS POINT
get to modding in confidence
Click to expand...
Click to collapse
All right, I am having issues already, from the very beginning.
The RUU ROM .exe will not recognize the HTC Hero. It throws an error 170 at the step where it is trying to pull information from the phone. I think this has something to do with ADB, and the fact the computer did not have the SDK on it. (I originally set up the root with my Mac.)
So, where do I go? I have a Boot Camp partition and another computer both running Windows 7, but my attempts to put the SDK on those computers and then have the phone drivers properly recognized failed on both, and the .exe still cannot complete. Is there something I am missing here, or can I somehow do this on the Mac side? I'll take anything!
Edit: Just cause I can see someone asking, yes, I tried to do this on both of my Windows 7 computers, not the Mac. I recognized that the .exe would not run on OSX pretty quickly.
can you put your phone into fastboot (power+vol down) and get to the point where windows basically sees your phone
what you are looking for is when you type adb devices it shows your hero
fastboot might not work because it's a seperate program but try custom recovery main menu.... enable usb.... or something to that extent
I appologize I don't have my main computer in front of me so I can't tell you EXACTLY where to go
once I do, I'll find which one to hit.... it does work though because I had to do the same thing with my godly preaching of backups :blush:
it's one of the recovery areas though i promise
fastboot will see the hero as the same device as adb will in fastboot
adb will see the hero as recovery device in custom recovery
attempt both of these I'm certain one of these work
if absolutely all else fails.... after you "install" sprint ruu search your computer for rom.zip it should be in your START>RUN>%TEMP% in here somewhere
rename rom.zip it to HERCIMG.ZIP and put it at root of your sd card and boot into hboot and it should automatically find it and press action to flash it
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
lorsoblu said:
I'll give some of that a shot. I can confirm that adb devices was not showing the hero connected cause I tested that, so I have a feeling correcting that is my primary concern. What happened when I connected the Hero the first time was that it applied the drivers, but it could not find the ADB one, even after I added the SDK. So if anyone knows what that means (Windows 7 doesn't really give you an easy way to point and say, "Hey, I know what you are looking for, it's right here!" apparently, at least I haven't found it) it would be appreciated.
Click to expand...
Click to collapse
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
johnsongrantr said:
go to htc's website and get htc sync under support>sprint hero it has the drivers built in.... should fix driver issue
Click to expand...
Click to collapse
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
lorsoblu said:
Hey, that did the trick! Currently flashing with the official ROM right now. Thanks for all the help! FINALLY, I will get to do this right!
Click to expand...
Click to collapse
glad to be of assistance
johnsongrantr said:
glad to be of assistance
Click to expand...
Click to collapse
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
you'd think so.... but from my own experience if you do a backup on a partititon then convert it... it screws with the backup and you can't recover from it.... just in case... do 2 backups.... store the normal fat32 nandroid backup on your workstation (the entire nanddroid folder) and copy it back to sd after you convert it to fat32+ext2 .... you'll see what I'm talking about....
I don't quite understand why it does that... but for me I was only successful in recovering from a partition that I made a backup to not copied to (if that makes any sence)
also if you don't want to experiement yet... just leave it fat32... you can always change it later after you see it working (sorta confidence builder before tinkering)
lorsoblu said:
Actually, I do have one more question.
Following your instructions back on page 1, wouldn't I want to make the nandroid backup BEFORE repartition to fat32+ext2, so I could recover it all the way back to the standard ROM without partition alterations? Or is it necessary for me to repartition before creating a backup?
Click to expand...
Click to collapse
Think about it this way, you do a nandroid backup...it places it on the sdcard.
Then you go and change the format of the sd card (potentially blowing away or corrupting any data on it, including the nandroid backup you just made).
Thus why it's better to do it afterwards (besides, nandroid doesn't back up your sd card, just your phone's OS and such)
solved for me
i had that problem its cuz the back up is brocken get anthoer copy of it if u hav 1 then restore it again it worked for me
I had rooted my evo with of course the unrevoked and my brother was playing around with my phone and did a format on the sdcard now i lost my backup and all data dose anyone know how to get back to stock or know of a stock rom any help i will take thanks...
You might give "Testdisc" or "Recuva" a try. I have used both to recover deleted and over-written files. Both are open source and surprisingly effective. I prefer Testdisc and always have it at the ready of my computers.
If you really want to get back to stock, find the post in the dev section called shipped roms. Download the 3.70.xxx .zip and make sure it is named PC36IMG.zip and not PC36IMG.zip.zip and put it on the root of your sdcard. Boot your phone into bootloader by holding down volume down and power buttons and it will scan the card and find the PC36IMG and ask if you want to update. Select yes and let it do it's thing until it asks you to reboot your phone. Reboot and you will be back to stock. Make sure your battery is charged before starting.
My EVO doesn't charge anymore. Guess my port got broken. My phone is rooted, and I dont have PC syncing capabilities. Is there a way to restore my phone back to the stock sprint rom so i can take it in for service or get a new phone? Does a hard reset restore the stock sprint rom? Im running the MIUI rom As u can tell im sort of a newb
Find a PC36IMG file of a stock, unrooted ROM and flash it through the bootloader.
Get a cheap standalone battery charger on ebay. While you're at it, get a microSD card adapter that you can load into a SD card reader. Charge your battery that way since the micro-usb doesn't work. Pull out your microSD card from the phone and load into adapter. Put an RUU file onto the microsd through your comp then put the microsd back into phone with the charged battery and you should be back to stock.
Another option, just bring to Sprint store and have them fix the micro-usb port. Their policy has changed and they should repair your phone even if it's rooted.
Make sure you have a fully charged battery before going back to stock. Download the unrevoked s-on tool from the unrevoked website, along with the most recent RUU in PC36IMG.zip form. Make sure that the RUU is named correctly - all caps, only one zip at the end. You will not need to add .zip to the end in the process of renaming.
Boot the phone into recovery & flash the s-on zip. Power the phone down and boot into the bootloader via volume down + power buttons. Make sure it says "Ship S-on" at the top. The phone will scan and find the RUU (as long as it's on the root of the card and named correctly), then ask you to update. Choose yes, then wait for it to flash. When it's done, choose yes when it asks you to reboot and you'll be good to go.
While Sprint will fix rooted phones with hardware problems, a broken port is not fixable. You also don't want them flagging your account. You will have to get a new phone, so you can toss any nandroid backups - do not attempt to restore them on your new phone. While it may be possible, you don't want to risk messing up your wimax... along with other things. You can restore user apps with Titanium Backup, but restoring system settings is probably a bad idea. Good luck!
plainjane said:
Make sure you have a fully charged battery before going back to stock. Download the unrevoked s-on tool from the unrevoked website, along with the most recent RUU in PC36IMG.zip form. Make sure that the RUU is named correctly - all caps, only one zip at the end. You will not need to add .zip to the end in the process of renaming.
Boot the phone into recovery & flash the s-on zip. Power the phone down and boot into the bootloader via volume down + power buttons. Make sure it says "Ship S-on" at the top. The phone will scan and find the RUU (as long as it's on the root of the card and named correctly), then ask you to update. Choose yes, then wait for it to flash. When it's done, choose yes when it asks you to reboot and you'll be good to go.
While Sprint will fix rooted phones with hardware problems, a broken port is not fixable. You also don't want them flagging your account. You will have to get a new phone, so you can toss any nandroid backups - do not attempt to restore them on your new phone. While it may be possible, you don't want to risk messing up your wimax... along with other things. You can restore user apps with Titanium Backup, but restoring system settings is probably a bad idea. Good luck!
Click to expand...
Click to collapse
I had the same problem you had. This method worked best for me.
where do i get the most recent RUU in PC36IMG.zip form? I have the stock sprint radio file but its exe.
"RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe"
Do i rename this to PC36IMG.zip or do i need to download something else.
edit:
Or i download this file and rename to PC36IMG.zip?
PC36IMG_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15.00.07.28_NV_1.40_release_140444-signed.zip
Use the one I'm going to link you to. Rename it to PC36IMG.zip, leave the .zip intact - don't add it again. Then follow the directions I posted earlier.
http://goo-inside.me/evo/stock/ruu/...0.09.01_NV_1.77_003_release_154209-signed.zip
Sent from my PC36100 using Tapatalk
ok thanks!
Another thing for future refrence . I personally keep a folder on my SD card named "Emergency restore" Just in case . It contains the PC36IMG.zip and the Unrevoked S-on tool . Granted in the event the screen was broken or something to that extent and I still had some control over the phone I can still restore back to stock if I am away from my computer at home . Just an idea
ok i turned on the s-on via the "unrevoked-forever-son" tool. I put the image into the sdcard root and it checked the zip file but it didnt ask me to update
loading...PC36D1AG.zip.....no image
loading...PC36D1AG.nbh .....no image or wrong image
then it loads the PC36IMG.zip and checks it, but no update.
Whats wrong?
@SouthernEvo, thats a good idea, thanks
Try downloading again, then booting into the bootloader and letting it scan. You can always try letting the bootloader scan your current one again as well. It doesn't say "no image or wrong image", correct?
I almost recommended running an RUU from your computer, but you can't connect... duh. If it still won't work after redownloading, try a different one.
Sent from my Evo using Tapatalk
im thinking its not updating because im not flashing the latest radio maybe? my version says:
Radio-2.15.00.11.19 do i need to get one after this version in order for it to update?
im downloading another RUU file. Hopefully it may work. As it looks, my phone is already running the latest. Idk...i actually dont know wth im talking about anymore lol
EDIT: Figured out it was my SD card causing the problems. Switched to the stock 8gb card and now it works. Flashed back to Stock. New phone comes Friday
Hi guys, i'm new here and a bit of a noob to the whole Android world.
I got my a500 about a month ago and loving it, Rooted it and got rid of all the bloat ware and is running like a dream.... love it....
A couple of days ago, i got an update: System Update 1.139,05, downloaded it and went to install, rebooted but nothing, Update failed!
I already have Android version 3.0.1 and Kernel version 2.6.36.3.
Is it me doing some thing wrong? Is it because its rooted? Do i need the update, please help, just want it to be up to date. Love the forum, thanks
chickin2000 said:
Hi guys, i'm new here and a bit of a noob to the whole Android world.
I got my a500 about a month ago and loving it, Rooted it and got rid of all the bloat ware and is running like a dream.... love it....
A couple of days ago, i got an update: System Update 1.139,05, downloaded it and went to install, rebooted but nothing, Update failed!
I already have Android version 3.0.1 and Kernel version 2.6.36.3.
Is it me doing some thing wrong? Is it because its rooted? Do i need the update, please help, just want it to be up to date. Love the forum, thanks
Click to expand...
Click to collapse
I've seen that some other users have had issues with the update if they removed the bloatware. Have you put it back before you attempted the update? If not, you'll have to put everything you've removed back and if you've edited any of the system files like build.prop, etc..you'll have to put it back to original also.
Thanks for the reply JackMetal! ERRRRRMMMM Q: is this a big update and if so then how would i put everything back, would it be factury settings? and if i do need to put everything back on why did i root it? lol sorry for being suck a noob! )
chickin2000 said:
Thanks for the reply JackMetal! ERRRRRMMMM Q: is this a big update and if so then how would i put everything back, would it be factury settings? and if i do need to put everything back on why did i root it? lol sorry for being suck a noob! )
Click to expand...
Click to collapse
LOL - yeah, I know..it's kind of a sucky move on Acer's part to force that. ;-) How did you remove them? Did you just delete them or freeze them within Titanium Backup? If deleted, did you happen to make a backup of them first so you could restore them now.
You can look at /cache/recovery/last_log and see exactly what it's complaining about. If you don't have the files you deleted, you can ask in the forum to see if another user can send them to you. I'd be glad to send mine, but I would imagine mine probably wouldn't help you since they are from 'after' the update and the checksum would still fail since they're changed. We could give it a shot though, and if it doesn't work you can see if someone that hasn't updated or happens to have the previous versions backed up, could send you the files.
---edit
Actually, I've got a few Titanium Backups from before the update, so I may just have the files you need!
Sweet dude, right will have to give it a look as i deleted them, noob thing to do i know lol still learning, thanks again for the super quick reply!
Same thing happened to me and this was after I restored my A500 to factory stock. I re-started the update download from the settings/info menu and this time it went without a hitch. I now have the updated A500, rooted it and am ready to go.
Advice for those people rooting their tablets. Don't just delete any .apks you don't want; move them to a folder on the internal sd card instead so whenever you need to restore them it's a simple matter of just moving them back).
Right, just an update.......
don't laugh, but i did try to put back all of the bloat ware!!!!! However, i replace some things and got rid of others, NOT GOOD! " HOME NOT WORKING ", yes thats what it said or words to that effect! Restarted as i thought that would help! OMG BOOT LOOP! Phone acer and sent it back for repair, UPS picked it up and acer received it this morning, and 30 mins again i got a text message with it done you douche bag, well they didn't say douche bag, but hay they should have done! Yes i'm a noob at all this, but i have learnt my lesson. Must say thanks for the help anyway from the forum!
P.S UPS SUCK BALLS, they are rude and v unprofessional! (had problems with them picking up the tablet).
P.P.S Back up everything and the back it up again! And DONT get rid of any system file or anything, to quote someone from the forum, " you have plenty of room! ", I have the 32Gb so yes i have the room lol!
O and just one more thing............ BACK THING UP NOOBS !!!!!!! )
Or Rename!
iCurmudgeon said:
Same thing happened to me and this was after I restored my A500 to factory stock. I re-started the update download from the settings/info menu and this time it went without a hitch. I now have the updated A500, rooted it and am ready to go.
Advice for those people rooting their tablets. Don't just delete any .apks you don't want; move them to a folder on the internal sd card instead so whenever you need to restore them it's a simple matter of just moving them back).
Click to expand...
Click to collapse
Also to make easy, just rename the .apk's to .bak or freeze them in Titanium backup!
Not to sound like a smartass but you know you could have done it yourself? Flash the device i mean.
What you do is you look for the boot.img and system.img and update.zip files in this forum or somewhere.
First the chinese one that you can just place in your External SD card and press Power+Vol- when device is turned of.
Then proceed to look for the American version, or whatever you wish if it's available.
Then you do this: place the boot.img and system.img in the root internal memory called Sdcard and place the update.zip in your EXTERNAL MicroSDcard.
Install Terminal emulator and push the boot and system img's 1st boot, 2ndSystem. Have superuser installed to.
After that when the images are pushed (usually the tablet would freeze after the system.img)
Then you force stop and power up the unit by holding Power button + Vol-
and that's it! No need to send to repair and pay money perhaps.
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...