Related
Have some hardware problems with my phone (screen live its own life, I can control it form 1 cm away from the screen). And want to put everything back (so unroot it, and put original rom back. So I can send it in for repair.
Does anyone know who to do this?
check this http://theunlockr.com/2009/10/03/how-to-unroot-the-htc-hero/
They are also in [ROM] Official HTC Hero RUU ROM + Radio Links
Plus there are a few others there that aren't listed on the other link given.
Thnx! But when I do this, i get an error message saying:
Error [140]: BOOTLOADER VERSION ERROR
The rom update Utility cannot update you Android phone.
Please get teh correct ROM Update Utility and try again.
What should i do?
What ROM version have you got at the moment? Which ROM are you trying to install?
Are you trying to put on an older ROM than you currently have?
You should be able to put the same or a newer ROM on. That error message is usually received when ppl are trying to downgrade *I THINK*.
Use HEROIMG.ZIP
I believe the easiest solution to your problem is the following:
- Run RUU update on your computer
- After the installer starts, and before it completes, search at your local temp directories for a file named "rom.zip"
- Copy it, this is your actual rom
- Rename it to HEROIMG.zip and put it in SD root
- Restart your hero while keeping Volume Down button pressed
- The bootloader will start and should normally find the HEROIMG and flash it
Done!
Good luck!
PS: I believe this process is written elsewhere in the forums but could not trace it at the moment.
gtsek said:
I believe the easiest solution to your problem is the following:
- Run RUU update on your computer
- After the installer starts, and before it completes, search at your local temp directories for a file named "rom.zip"
- Copy it, this is your actual rom
- Rename it to HEROIMG.zip and put it in SD root
- Restart your hero while keeping Volume Down button pressed
- The bootloader will start and should normally find the HEROIMG and flash it
Done!
Good luck!
PS: I believe this process is written elsewhere in the forums but could not trace it at the moment.
Click to expand...
Click to collapse
I think that will only work on an unlocked SPL, but as they are getting,.....
thedutchie said:
Error [140]: BOOTLOADER VERSION ERROR
The rom update Utility cannot update you Android phone.
Please get teh correct ROM Update Utility and try again.
Click to expand...
Click to collapse
....I dont think it will work,... Worth a try though if trying the same ROM version .exe fails.
Indeed it does not work. I get the error saying:
Main Version is older!
Update Fail!
Atm I am using Villian 5.5.0
So if I understand correctly I have to wait till there is a 2.1 update for the Hero before I can go back to a official HTC rom?
Oh,... Your already running a custom ROM?
What network are you on? Which .exe file did you try out?
ddotpatel said:
Oh,... Your already running a custom ROM?
What network are you on? Which .exe file did you try out?
Click to expand...
Click to collapse
Yes, Villian 5.5.0 (a 2.1 rom)
Vodafone
RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_ NoDriver.exe
-edit
I just downloaded a RUU from htc.com/nl/SupportViewNews.aspx?dl_id=671&news_id=254
and it seems to be working
-edit 2
It works
Strange wasn't working the first time i tried it :S But hey so thnx guys
WAHEY!!!!!
At last.
I searched through the forums for hours and didn't find an example quite like mine (some were close)
Verizon HTC Eris. It's a hand me down.
My friend gave it to me because on normal start up it loads into the 3 Skating Androids screen and goes no further. I don't know how it ended up like that. I wanted to see if I could fix it. All the key combos work (soft boot reset, FASTBOOK start up, HBOOT start up, etc.)
Info:
PB00100 XC SHIP S-ON
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Feb 8 2010, 00:08:56
I can get the phone into stock recovery, don't know if it has the Amon_RA recovery installed.
HBOOT doesn't recognize the PB00IMG.zip (I downloaded the Eris_RootROM_v2.19.605.1_PB00IMG.zip, copied it to my sd and renamed it PB00IMG.zip) and can't get it to load.
I tried SDK but command line "adb devices" list nothing. "adb shell" doesn't work either.
I can run RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver when my phone is in FASTBOOT mode. It's says I have 2.37.605.4 ROM on my phone but will not go any further than that.
When I hook the USB up to my computer, it makes the "USB attached" noise, but I can't see it listed in the removable drives.
Is this a brick??
Again, I searched and read, and searched some more for threads on this problem. Didn't wanna violate the noob rule, because I am a noob.
No Help from anyone? I'm really trying to bring this thing back from the dead
You don't mention if the HBOOT version is 1.49.0000, but I suspect that it is. If memory serves me well, I believe this is why the root ROM PB00IMG file will not load - it will only install over 1.46.0000 or 1.47.0000.
Since you S-ON, Fastboot mode isn't going to help you with much that's useful. That requires S-OFF (which, of course, the root ROM would give you, if you could install it.)
The RUU would not install, I think, because it recognized that you have a newer version of the Eris already installed. This is probably a good sign, though.
I assume that you tried the hard reset of the Eris? http://www.technipages.com/hard-reset-htc-droid-eris.html
With the phone turned off, press and hold the Volume Down, Send (green phone) and Power buttons. The device will turn on. Keep holding down the keys unto you see a screen to clear storage.
Press the track ball.
Follow the instructions to complete the hard reset.
Click to expand...
Click to collapse
See if that works.
doogald said:
You don't mention if the HBOOT version is 1.49.0000, but I suspect that it is. If memory serves me well, I believe this is why the root ROM PB00IMG file will not load - it will only install over 1.46.0000 or 1.47.0000.
Since you S-ON, Fastboot mode isn't going to help you with much that's useful. That requires S-OFF (which, of course, the root ROM would give you, if you could install it.)
The RUU would not install, I think, because it recognized that you have a newer version of the Eris already installed. This is probably a good sign, though.
I assume that you tried the hard reset of the Eris?
See if that works.
Click to expand...
Click to collapse
Did as instructed and got the following:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Feb 8 2010, 00:08:56
CLEARSTORAGE
Delete all user data?
<Action>Yes
[I pressed trackball]
Clear.....
Restore NV Okay.
Done
Reboot after 5 seconds
black screen (2 seconds or so)
Restart back to 3 skating androids..that it
I'm not sure if this will work, but in this thread: http://forum.xda-developers.com/showthread.php?t=909921
Find the PB00IMG.zip file for "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU)" (not the RUU, but the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP. Rename it to PB00IMG.zip, copy to the SD card, start HBOOT (hold VolDn while starting up - but I think you know how to do this already) and see if that installs. Since you have a later version on the phone already, it may not.
doogald said:
I'm not sure if this will work, but in this thread:
Find the PB00IMG.zip file for "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU)" (not the RUU, but the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP. Rename it to PB00IMG.zip, copy to the SD card, start HBOOT (hold VolDn while starting up - but I think you know how to do this already) and see if that installs. Since you have a later version on the phone already, it may not.
Click to expand...
Click to collapse
Looks like this one worked...or it got me farther than I've been before. I used the file above and got the progress bar to show up on the top left side. That's never happened before.
You were correct that the version above was too old.But there's good news. The update failed. I tried three (3) fixes:
1) Renamed the 2.36.605.1 file PB00IMG (load it on my laptop using SD adapter, then just rename it), and tried to use HBOOT. It started the blue progress bar in the top left (that's never happened for me so YAY), finished. But, when it was "Checking PB00IMG.zip", it said "Update Failed" and "Version Too Old" or something like that.
2) I tried using
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
I renamed this file PB00IMG (did laptop rename process) and got the progress bar in the top left again, and the process finished. This time it went to "Checking PB00IMG" and finished no problem. The bar in the top left disappears, but it stays on the same screen with:
<SEND> FastBoot Mode
<VOL UP> Recovery
I didn't know what to do from here. So just pulled the battery and tried fix #3
3) Renamed the #13 File from Fix 2 above "update" (using laptop rename process). With phone off, held "VOL DWN" and "PWR" button to get into stock recovery mode. I navigated to "install sd update.zip", started it, and got this message:
E: can't open cache/recovery/command
--Install from sdcard...Finding update package...opening update package...verifying update package...installing update...file_getprop: failed to stat "/system/build.prop":No such file or directory
E:error in sdcard/update.zip
(Status 7)
Installation aborted
Do you think I just need a ROM file or something on the sd card too (besides just the PB00IMG file)? Or should it automatically load something after the PB00IMG status bar and check finishes?
Neither method worked, but I at least got something different. It's getting me farther than I had gotten before. So thanks for the recommendations. Ready to try your next suggestion when you get time.
Still needing help....is the tereg recovery the best shot...and how do you do that...
Cap'nO said:
Still needing help....is the tereg recovery the best shot...and how do you do that...
Click to expand...
Click to collapse
You could try getting the S-OFF bootloader installed using SoSicWiTiT's RUU+"rom.zip" swap-out trick
From there, flash a custom (Amon_RA or variant) recovery to the phone (using the fastboot utility from a PC), and try a ROM install.
BTW, using OTA update files will certainly never work renamed to PB00IMG.zip, and in general they will only work from a stock recovery as "update.zip" IF and ONLY IF the phone is in good working condition and with a precise stock OS version pre-existing on the phone. They can NEVER be used to "repair" a phone, as they are "patch kits" for a specific prior release - not a full installation.
bftb0
Yeah OTA updates are typically overlays for a previous update in order to keep the size down. I think you'll see a lot of patch files which is sort of like a .diff file and patches the differences.
The RUU when decompressed with a utility like universal extractor will have a real usable zip in it.
Don't worry about the radio at this point unless you suspect you have a damaged radio firmware which you probably shouldn't mess with unless your 110% sure.
Thanks bftb0..i thought no one would get back to me. I'm going to try your solution now. Full disclosure, I read it but will need some time to decipher it. I'm a self-admitted noob, but trying to become more proficient.
Cap'nO said:
Thanks bftb0..i thought no one would get back to me. I'm going to try your solution now. Full disclosure, I read it but will need some time to decipher it. I'm a self-admitted noob, but trying to become more proficient.
Click to expand...
Click to collapse
Scary_Alien posted a great step-by-step over at AndroidForums.com here: http://androidforums.com/eris-all-things-root/440288-eris-half-brick.html#post3423263
bftb0 said:
You could try getting the S-OFF bootloader installed using SoSicWiTiT's RUU+"rom.zip" swap-out trick
From there, flash a custom (Amon_RA or variant) recovery to the phone (using the fastboot utility from a PC), and try a ROM install.
BTW, using OTA update files will certainly never work renamed to PB00IMG.zip, and in general they will only work from a stock recovery as "update.zip" IF and ONLY IF the phone is in good working condition and with a precise stock OS version pre-existing on the phone. They can NEVER be used to "repair" a phone, as they are "patch kits" for a specific prior release - not a full installation.
bftb0
Click to expand...
Click to collapse
This may be funny, but I'm still trying to fix this thing. Trying the "swap method" you mention above. What's the exact file name (2.1) I'm using for this?
Possible solution (Troubleshooting)
Cap'nO said:
Looks like this one worked...or it got me farther than I've been before. I used the file above and got the progress bar to show up on the top left side. That's never happened before.
You were correct that the version above was too old.But there's good news. The update failed. I tried three (3) fixes:
1) Renamed the 2.36.605.1 file PB00IMG (load it on my laptop using SD adapter, then just rename it), and tried to use HBOOT. It started the blue progress bar in the top left (that's never happened for me so YAY), finished. But, when it was "Checking PB00IMG.zip", it said "Update Failed" and "Version Too Old" or something like that.
2) I tried using
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
I renamed this file PB00IMG (did laptop rename process) and got the progress bar in the top left again, and the process finished. This time it went to "Checking PB00IMG" and finished no problem. The bar in the top left disappears, but it stays on the same screen with:
<SEND> FastBoot Mode
<VOL UP> Recovery
I didn't know what to do from here. So just pulled the battery and tried fix #3
3) Renamed the #13 File from Fix 2 above "update" (using laptop rename process). With phone off, held "VOL DWN" and "PWR" button to get into stock recovery mode. I navigated to "install sd update.zip", started it, and got this message:
E: can't open cache/recovery/command
--Install from sdcard...Finding update package...opening update package...verifying update package...installing update...file_getprop: failed to stat "/system/build.prop":No such file or directory
E:error in sdcard/update.zip
(Status 7)
Installation aborted
Do you think I just need a ROM file or something on the sd card too (besides just the PB00IMG file)? Or should it automatically load something after the PB00IMG status bar and check finishes?
Neither method worked, but I at least got something different. It's getting me farther than I had gotten before. So thanks for the recommendations. Ready to try your next suggestion when you get time.
Click to expand...
Click to collapse
If you get this kinda of message that the file_getprop then the update zip is corrupt. or its not compatible with the phone you are trying to mount. It took me a bit but I was able to find a good set up. Just take a breathe. If you can install from sdcard from recovery then your recovery is fine. if you can boot it up and at least get a splash screen your boot.img is right. I stress that you dont change those two if you are able to do both of those. All you need is a Good rom that is 1 compatible with your cell and 2 works with both your boot.img and recovery.img. I am guessing you forgot to backup your original settings. MIUI roms are really good and thats what i settled on.
Thanks for the reply. I actually got the phone working. Took a while but yes, the ROM was corrupt. And yup, it wax never backed up and was stock in the loop.
Not anymore
Sent from my SGH-T959 using xda app-developers app
I was sitting a work when I noticed the OTA notice come up, I planned to hit differ so that I could check my order of operations on how to handle this. In my haste to prove I really got the OTA notice I hit a screenshot which closed the notice. I assumed it automatically hit differ when I pressed the home button. I returned to the phone after finding here I should S-Off before the update, only to find it on the "Android system recovery" screen.
I am faced with the following.
Code:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip menu
- Wipe
- Partition sdcard
- Mounts
- Other
- Format data.system.cache Ext4 | Ext3
- Developer menu
- Power off
---------------------------------------------------------------------------
Build : RA-VIGOR-v3.1.0-getitnowmarketing
Finding update package...
Opening update package...
Installing update...
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
Deleting specific files...
Removing unneeded files...
Patching system files...
Unpacking new files...
Symlinks and permissions...
I am not running a rom, I was stock rooted with HTCDev unlock and I do believe Amon-Ra recovery though I admit I haven't touched that aspect of things since February. I wanted to wait for the OTA to make any bigger changes than adding a tether app I could really use. Am I screwed? Do I tell it to reboot and hope for the best?
At the time of this post I could not find anything for someone in my situation. Sorry if it is in the wrong area. I lurk instead of posting 99% of the time.
EDIT: I told it to reboot and it spit me back to the home screen I am used to, still old software. Doing a little more reading I have established this is normal in cases with a recovery installed.
howser87 said:
I was sitting a work when I noticed the OTA notice come up, I planned to hit differ so that I could check my order of operations on how to handle this. In my haste to prove I really got the OTA notice I hit a screenshot which closed the notice. I assumed it automatically hit differ when I pressed the home button. I returned to the phone after finding here I should S-Off before the update, only to find it on the "Android system recovery" screen.
I am faced with the following.
Code:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip menu
- Wipe
- Partition sdcard
- Mounts
- Other
- Format data.system.cache Ext4 | Ext3
- Developer menu
- Power off
---------------------------------------------------------------------------
Build : RA-VIGOR-v3.1.0-getitnowmarketing
Finding update package...
Opening update package...
Installing update...
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
Deleting specific files...
Removing unneeded files...
Patching system files...
Unpacking new files...
Symlinks and permissions...
I am not running a rom, I was stock rooted with HTCDev unlock and I do believe Amon-Ra recovery though I admit I haven't touched that aspect of things since February. I wanted to wait for the OTA to make any bigger changes than adding a tether app I could really use. Am I screwed? Do I tell it to reboot and hope for the best?
At the time of this post I could not find anything for someone in my situation. Sorry if it is in the wrong area. I lurk instead of posting 99% of the time.
EDIT: I told it to reboot and it spit me back to the home screen I am used to, still old software. Doing a little more reading I have established this is normal in cases with a recovery installed.
Click to expand...
Click to collapse
I don't believe you can accept OTA with AmonRa. Stock recovery is what it installs through. Could be wrong tho.
zac41189 said:
I don't believe you can accept OTA with AmonRa. Stock recovery is what it installs through. Could be wrong tho.
Click to expand...
Click to collapse
you can get stock recovery over here http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/ down at the bottom.
topgun1953 said:
you can get stock recovery over here http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/ down at the bottom.
Click to expand...
Click to collapse
Thanks all! This was my exact situation as well.. AmonRa was the only real change I made since picking up the phone, holding out for ICS!
So let's go waaay back to the basics.. anyone have a link to how I install that stock recovery? Sorry for the n00bness.
namebrandon said:
Thanks all! This was my exact situation as well.. AmonRa was the only real change I made since picking up the phone, holding out for ICS!
So let's go waaay back to the basics.. anyone have a link to how I install that stock recovery? Sorry for the n00bness.
Click to expand...
Click to collapse
I think you would just be better off to install the full .12 RUU. Links are everywhere here but since you just ran stock rooted you can still root it I believe. If its not rootable install the full .10 RUU and root that. The differences between the two are minor and that way you will have the updated firmware and radios.
It will wipe data though.
namebrandon said:
Thanks all! This was my exact situation as well.. AmonRa was the only real change I made since picking up the phone, holding out for ICS!
So let's go waaay back to the basics.. anyone have a link to how I install that stock recovery? Sorry for the n00bness.
Click to expand...
Click to collapse
Rename the file to ph98img.zip. Reboot into bootloader and select yes to update. It will install the stock recovery.
Hello Everyone,
I badly need help on my Huawei Honor U8860 phone. I have recently updated it from 2.3.6 to 4.03 over WIFI and the update went smoothly. So now here is what my phone have:
Kernel Version: 3.0.8-perf-00059-g3a757a2 [email protected] #1
Build Number: U8860IV100R001C00B923SP01
I have not rooted the phone at this time. It was working fine until 2 days ago when I started getting messages on the screen like:
"Unfortunately, 2D Home has stopped"
"Unfortunately, Google Play has stopped"
"Unfortunately, Contacts has stopped"
"Unfortunately, Settings has stopped"
"Unfortunately, Google Play Music has stopped"
"Unfortunately, Browser has stopped"
And so on, and so forth. It seems that all apps and processes have stopped when I try to use them so I literally can't use the phone. I went through several threads here just trying to restore my phone back to a
working state. I tried to do the following in order but without success:
1.) Factory data reset / erase everything - the phone boots to the recovery menu then it formats the /Data, /Cache and /HWUserData then it reboots. After reboot, the phone is back to where it was before the factory data reset with everything in it including downloaded apps.
2.) Manually uninstalled all downloaded apps. Removed screen lock (just to see if phone behavior changes). Then rebooted the phone but after reboot, all the apps are still installed and the screen lock is back as well.
3.) I tried to Force Update with the following official ROMs: B886, B919 and B923 but I always get the message "Update failed" during the update process.
4.) I downloaded the file "recovery-u8860-en.img" so I can replace the "recovery.img" file . Rebooted the phone w/ the pink screen and connected it to my PC but there is no USB mass storage device mounted.
5.) Finally, I tried to root the phone. I enabled USB debugging. I installed the ADB drivers then I downloaded the U8860 root tools and rootexplorer.apk. When I ran the "root-me.cmd", it tried to copy some files to the phone but it failed. The error was "read-only file system".
So it seems that the problem is because of the "read-only filesystem". I does not permit/allow any changes made to the phone. Can you help me restore my phone?
Please.. Can somebody help me on this?
Thanks, clint2rose
clint2rose said:
Please.. Can somebody help me on this?
Thanks, clint2rose
Click to expand...
Click to collapse
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
clint2rose said:
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
Click to expand...
Click to collapse
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
kaefert said:
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
Click to expand...
Click to collapse
thanks for the reply. it did not work. I even formatted the internal SD. Re-run the firmware update but it failed. when i boot the phone, all the contents of the internal SD remains intact. any other suggestion?
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
kaefert said:
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
Click to expand...
Click to collapse
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
clint2rose said:
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
Click to expand...
Click to collapse
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
kaefert said:
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
Click to expand...
Click to collapse
Thank you once more for your time. Most of the thread I read regarding these patches often used the phrase" you have to flash the current version of your ROM using the patch"...
And yes I created dload folder, place the UPDATE.APP and put it on the sdcard. I turned off the phone and removed the battery. Then I pressed vol+ vol- and power on/off button. The firmware update went to about 70% installing before displaying update failed.
I guess I will have to bring my phone to a repair center. My only problem is that there is no Huawei service center at my place (I reside here in Saudi Arabia). I got the phone as a free device on a broadband package and the warranty is already expired. I'm a little worried to take the phone to the small mobile repair shops as they might screw up the phone even more. Huawei is not a popular device here unlike iPhone, HTC and Samsung Galaxy.
As I understood that your device is rooted, you should get some custom ROM and try to install it.
okty2k said:
As I understood that your device is rooted, you should get some custom ROM and try to install it.
Click to expand...
Click to collapse
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
clint2rose said:
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
Click to expand...
Click to collapse
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
kaefert said:
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
Click to expand...
Click to collapse
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
U8860 not responding
clint2rose said:
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
Click to expand...
Click to collapse
Have you find the solution yet? I have the same problem. Somehow my phone system is "locked". I can't install or uninstall app. Some google apps keep showing not responding. Everything changes i made, keep showing up after the phone rebooted.
This was happen a few days after I upgrade to ICS B932SP01 and rooted my phone (to remove original chinese apps).
Luckily i have friend in huawei indonesia. He gave my u8860 to the technical support. But the result was no good.
They try everything, even install my phone with the original GB and always failed.
The last suggestion is change the phone machine, which is as same as buy a new phone.
I really appreciate is someone can help me here...
Thanks
ASUS MeMO Pad 8 (K011) ME181C Recovery Guide
The following is a list of what we can currently do with this tablet. It assumes firmware versions with the WW prefix (WW-3.1.23.1xx).
Root Status: Obtained
Bootloader: Locked
CWM Recovery Possible: Yes (Tethered)
Custom ROMS: None
The following information is for recovering your tablet and obtaining root only. The bootloader is locked on the device at this time.
Tethered CWM recovery
This is a temporary solution to unsigned loading. The bootloader on the device is currently locked, so after rebooting, it will revert back to standard recovery. Use this to restore to a stock firmware or to install SuperSU.
Download the official firmware and extract it.
Rename UL-K011-WW-3.1.23.172-user.zip to user.zip.
Copy user.zip to the root of your SD card.
Enable USB debugging on your tablet.
Run Launcher.bat.
Type ACCEPT.
Choose option T3.
This will reboot in to the Tethered Recovery.
Choose Install Zip from external SD card.
Choose user.zip
Reboot once finished.
Bootable Image for Recovery
This file is to be used if your system will not get past the Asus or Intel logo. Boot the system using Volume Up and Power. Once the logo appears, let go of power. Once in DroidBoot, use fast boot to flash the boot and system images. This is provided in case signature verification fails on the official images.
fastboot flash system system.img
fastboot flash boot boot.img
This file also contains adb and fastboot. If your tablet is not detected, try the Asus drivers.
Reboot the system and use the CWM tethered recovery to reinstall the official firmware.
OTA Updates
If you’ve recovered from the official firmware on the Asus site, you’re probably sitting at version WW-3.1.23.172. Here are the OTA updates to bring your system up to the current version of WW-3.1.23.189. There are two different OTA updates available here, so the process will need to be completed twice. Update 172 to 183 and Update 183 to 189.
Boot in to recovery, press the volume keys several times and install from ADB.
Extract the RAR file and rename the files update.zip.
On your PC, open a command prompt and change to the directory containing the update file
Assuming ADB is installed on the system, type: adb sideload update.zip
Once the process completes, reboot your system and update apps as needed.
Repeat this process for any additional update files.
Recovery image
This is the default recovery for the tablet. If you get adventurous and try to flash another one, this may come in handy.
can you explain
RemmyLee said:
All thanks to vampirefo for his work on this.
FB Tethered Recovery Launcher
Kind of curious if this method will work with the other versions of the tablet to allow SuperSU to be installed. Anyone want to try it?
Long story short, I screwed this thing messing with the framework. For some reason, the official firmware from the Asus site was failing signature verification when trying to reinstall. Someone managed to grab a stripped system image that at least gave me a launcher and USB debugging. This beauty allowed me to get the firmware installed and everything back to normal, as well as installing SuperSU.
If you have any trouble getting the tablet to show up in Windows, the Asus distributed drivers work like a charm.
Click to expand...
Click to collapse
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.
2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).
3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)
4. Reboot.
5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.
6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.
You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
Sent from my K011 using XDA Free mobile app
Asus MeMo Pad 8 - Pro 7 Entertainment Pad
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
OTA update 172 to 183
OTA update 183 to 189
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
shadow2483 said:
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
Click to expand...
Click to collapse
If you need any more help than whats above, let me know.
fulishone said:
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
Click to expand...
Click to collapse
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
RemmyLee said:
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
Click to expand...
Click to collapse
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
fulishone said:
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
Click to expand...
Click to collapse
Yep. That'll get you updated to the current firmware. I contacted ASUS yesterday and sadly, there are no plans on bringing Lollipop to this thing, nor are they interested in giving us an unlocked bootloader.
As for the Intel Tether, where the bootloader is locked, we can use a tethering method to access CWM recovery, but once we reboot, it reverts back to the standard recovery. This prevents us from using custom roms at this time. When it reboots, it checks signatures. The official firmware was not installing using the standard methods, so I used CWM to reinstall. That's why I included it above.
BBY builds
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
et1ssgmiller said:
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
Click to expand...
Click to collapse
I'm curious to know if the tethered method would allow a temporary CWM session to install SuperSU on the BBY line. I haven't seen anyone try it yet. If USB debugging is enabled, the tethered restore should try to automagically do everything for you. If you boot in to recovery, can you do a fastboot devices?
Can´t mount external sd card anymore
After using CWM tethered recovery to backup my rom, i cant mount my external sd card anymore. Any ideas?
Updates
RemmyLee said:
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
URLS removed to post
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
tperki said:
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
Click to expand...
Click to collapse
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Success
RemmyLee said:
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Click to expand...
Click to collapse
Yeah, strange that it won't update over the air. But thanks to your assistance I am running build 189. It may just be wishful thinking, but the device does seem a bit peppier. Thank you RemmyLee!!!!
[Update] Since updating to build 189, the device is much more stable and snappier. This was definitely worth doing. I don't understand why ASUS would not be pushing this out to everyone with this device.
Just wanna say thanks to the OP. Got my tablet back from the service center and was wondering why some apps were missing. Sure enough I was on WW...179. Nice to have updates and recoveries in one place. Great work!
Thank you so much bro, I have been googling a lot trying to find a root method and just discovered that I can easily have recovery and flash supersu zip thanks to you!!
Me181c not working...
Hi guys, I was using SoftKeyZ for about 2 weeks, I wanted to set my navigation buttons to it's default, so I tried using Backup of the SoftKeyZ, but when it rebooted the tablet, I lost my navigation buttons and indeed my notification and status bar. It rebooted again automatically, and this time when it started, I got an error which says: "Unfortunately, KeyguardTestActivity haas stopped", the error prevents me from unlocking the tablet and using it, so I cannot use it at all. I don't know how to go to recovery mode on my tablet, I used the button tips but it didn't work for me. I've downloaded the official rom from asus.com . Pleeeeeeeeeeeeeeeeeeeeeease, I need your help guys, you're my last chance...
should I do a complete wipe ?
Hi,
Thanks for the help in this thread.
I followed the instructions and successfully flashed the update firmware file. I was expecting for the tablet to be reset to original factory condition but found that all my apps ect were still there. I guess the user.zip is an update rather that a full ROM or should I have wiped everything first ?
I am have problems with the tablet such as Bluetooth has stopped working and wifi will only connect to very strong signal, (as in touching the router) which is why I wanted to completely wipe the device a start fresh.
f I wipe everything will the firmware file be able to restore the system fully?
Is there a complete firmware image file that can be downloaded any where ?
Thanks in advance for any advice
update : so fed up with no Bluetooth so I took the chance and did a full factory wipe and the system restored ok with the firmware file. Bluetooth problem solved, (Wifi did not, probably Hardware issue)
Thanks again
Signature failure
Thanks to your instructions, I've successfully managed to update my device to build WW-3.1.23.172, however, when trying to install 172 to 183 update I get a signature verification failure message.
Any ideas why this is happening?!