I have an Acer 500a I just bought off carigslist. Initially I thought it would be fine but then I realized I was inheriting someone elses problems. I hope someone may be able to help.
Within the first few hours I was noticing google Play crashed a number of times and struggled to update from Market. Somehow the update went through but now there is a system update that won't go through. I'm able to down load it and when i restart the computer to complete installation the screen goes black and says: booting recovery kernel in the corner. I then see a picture of an android and a load bar which after 2-4 seconds the android is on his back and an exclaimation mark is coming out of his belly.
My android version is 3.2
Kernel version
2.6.36.3+
Build number
Acer_a500_7.006.01_COM_GEN2
I'm pretty sure its rooted and i think that might be why its not playing nice with google market and system updates. I called the old owner and explained the problem and he just said he had it rooted and he thought he unrooted it. There is an ap called superuser in aps. (although if it were rooted would'nt I be able to uninstal some of thecrap software it comes with like GOLF HD? -- it won't let me).
The system update is for Acer_a500_7.014.01_COM_GEN2 8.88mb
My problem is all of the force closes I'm getting and the inability to update the system. Any thoughts? I don't have a usb cord to connect it to a desktop either =(
I am a bit out of practice, but...
Should be pretty simple to fix. From what I am seeing, you are running a stock rom. Just because the superuser.apk is installed on the system does not mean it is rooted, but it probably is.
Hit the market, grab "Root Checker" - simple tiny program to let you know for sure if your tab is rooted or not.
https://play.google.com/store/apps/details?id=burrows.apps.rootchecker&hl=en
From what I understand - automatic system updates will fail when trying to apply them to a rooted or modded system. Probably why you cannot auto-update.
My advice at this point would be to:
1) Since you just bought it, just do a factory wipe on it. That will remove all the stuff the prior owner had running on it and will result in a unrooted tab that should be able to get auto updates without a problem.
2) Un-Root it. Once the tablet is unrooted, the system should update without any issue.
As for your Play Store issues - I have never heard of or personally seen any issues caused with installing apps from the store on a rooted device. I have seen a few apps that will refuse to run on a rooted device - but that does not sound like your problem.
I would go with option 1 - just factory wipe the thing. Prior owner may have made tons of changes to the OS that we will never know about, and may have handed you a unstable system. Start fresh. Wipe it out.
Hope this helps you out! Let me know if I can answer any questions.
k thank you so much for the quick reply! I downloaded the root checker and it Is rooted. I did a factory wipe as found in the settings privacy tab when I bought it. That factory reset did not unroot and only cleaned out some of the aps on the device. Is there a better or more surefire way to unroot it? If I reset with the volume down key will it hard reset it?
Thank you for you help!
Draight
Okay.
I am about a year out of practice with my a500 - but from what I am think, if a factory reset still results in a rooted device - the prior user installed a stock ROM that comes pre-rooted.
I highly doubt being rooted is causing the issues you are running into.
At this point if you just want to get back to stock you can probably just install the Acer Recovery Manager from the market and use it to reflash a stock unrooted ROM. Or I see a few guides about how to manually restore back to stock over in the dev section for the a500.
Others will correct me if I am wrong, but I think Acer Recovery Manager should take care of your problem.
Hope this helps!
(Edit: Or you can just download the official stock 4.x rom (ICS) from the dev section and flash that. 3.2 is pretty slow and wonky in my experience, you should be able to just download a 4.x ROM and flash, since you are rooted. Again, I am way out of practice. Don't do anything before reading up!)
(Edit again: I think I was making this harder then needs be. Just flash any stock 3.2 unrooted ROM, done. After you do that the automatic on the air update should kick in for you and update you to ICS)
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
draight said:
Thanks for taking the time to work with me on this. I downloaded the program you suggested and tried to use a stock rom. When i went to reboot I had a picture of an android looking up at an exclaimation mark. It was froze like that until I restarted it. Now its back to the way it was, rooted and unupdatable.
I'm probably going to try to just wipe it all over but do i need to plug it into my computer somehow? I dont have a usb connector for the tablet, just the wall charger plugin. can i just download a rom and use the utility to try install it? when I reboot it am I supposed to be pressing the volume button?
I've read a few other forums but usually they sound pretty intense...
Click to expand...
Click to collapse
Hmmm..
Try the thread I linked two in my second edit of my last post. You just need to grab the stock and unrooted 3.2 - put it on a MicroSD card as update.zip - then reboot with vol rocker and power switch to get the system to flash the update.
That *should* work just fine.
(Edit: Forgot the link! http://forum.xda-developers.com/showthread.php?t=1839313 - there you go)
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
draight said:
Thankw, I am going to try it after readingna bit more. Do I need to have clockworkmod installed for all of this?
Click to expand...
Click to collapse
Nope. Just snag the stock unrooted 3.2 ROM - place it in the root of the MicroSD card as update.zip
Power down.
Power up with VOL + and POWER key held at the same time (you can let the vol rocker go when you see text appear in the upper left corner)
Should be all you need to do. Worst case; it does not work and returns you back to where you are now. Worth a shot.
If that does not work, let me know so I can do a few mins of homework and help you further. Been a long time since I have changed ROMS or had any issues with my a500.
I have bricked it twice by not following directions all the way or just making simple mistakes, but from what I have found there is always a way to recover.
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
draight said:
Just tried it. I copied the boot zip to sd card and renamed update.zip and reset..It looked like it was going to download after showing some text in the corner and then an exclamation mark appeared above the androids head... I left it and after a few.min it rebooted back
Click to expand...
Click to collapse
Hmmm. Odd.
Like I said, I am rather out of practice.
Someone more experienced them me: please help me point Draight in the right direction here?
Thanks for trying to help. =(
I wish that my tablet wasn't having such issues. I;m going to try to scramble around the forums and see if I can find some advice...If anyone has a suggestion please let me know.
Thanks again entropy,
Draight
Update:
So I've been tinkering around with it a bit more and I found a usb cord that plugs it into my computer. I keep finding boken links on this site so Im struggling to find an update I can use to flash to. I downloaded a different super user program which allowed me to temporarily unroot my device. I then restarted it and no root checker says its no rooted and I cannot find the superuser program. I think I have somewhat unrooted it -- but I think the real issue now is the recovery tool. I keep reseting it - hard reset, or factory reset and it wipes everything away but when i try to update it gets about 1/3 of the way up the bar then it stops with an '!' Mark above the droid. Im kind of annoyed at this point and hoping for some new links or some ideas on how to repair the recovery piece.
Draight
Go to the Dev section, and grad a couple of the ICS Update roms. You will see them listed for the a500. Make sure they are the FULL update roms. Should be about 3-400mb. These contain a FULL ICS Update Rom, and not a patch file.
http://forum.xda-developers.com/showthread.php?t=1816560
Then, go to the Themes and apps forum. You'll see a sticky that has the Acer Update Decrypter.
http://forum.xda-developers.com/showthread.php?t=1869505
Now, unpack the decrypter, and select one of the ICS Updates. Then hit Start. Take a couple minutes, but you will have a duplicate file with the word "decrypted" added to it.
Wait, you are not done yet.
Using a program like 7zip, or even Winzip, open the decrypted file. DO NOT EXTRACT, just open it and pull the update.zip to your PC's desktop.
Copy that update.zip file to your Ext SD Card of the tablet. Don't be putting it in any folder, just copy it to the root of the card.
Now, you still ain't done.
With the tablet off. Press and hold Vol+ and then PWR. Hold them both untill you start to see text about installing blah blah blah, then release the buttons.
If it completes, and you can reboot into ICS, then you are good to go.
If something fails during installation, then decrypt the other update Rom file you downloaded, and do the same procedure. Usually one of the 2 or three should work for you.
Note these are for the a500, and not the a501.
One more thing. It's advisable you get your UID number before doing these things. You probably won't need it, but it's nice to have written down in case you need it in the future. Inf to get it is at;
http://forum.xda-developers.com/showthread.php?t=1624645
MD
Thanks! I am downloading a few of the FULL ICS roms:
*Acer_A500_1.031.00_WW_GEN1 : http://d-h.st/uAy
Acer_A500_1.031.00_PA_CUS1: http://d-h.st/idO
Acer_A500_1.041.00_WW_CUS1: http://d-h.st/Yt5
*Acer_AV041_1.054.00_WW_GEN1: http://www.theandroidcollective.org/...00_WW_GEN1.zip
*Acer_A500_7.014.16_041.206.01_COM_GEN1: https://docs.google.com/file/d/0B_bk...hVc1RVcHc/edit
The I downloaded the ones ending with Gen1. Once they are downloaded I will continue with the instructions. Thank you so much for your help! I will post how it goes later tonight.
Draight
I just decrypted both:
*Acer_AV041_1.054.00_WW_GEN1:
*Acer_A500_1.031.00_WW_GEN1
Both get get to the third bullet quickly and the bottom says DONE! It takes like 4 seconds. I don't think the Decryption key of $12 is working
[*] Opening file: Acer_A500_1.031.00_WW_GEN1.zip
[*] Decrypting using key $12
[*] Writing decrypted file: Acer_A500_1.031.00_WW_GEN1_decrypted.zip
I try to extract something from the decrypted file and it says the file was not downloaded properly and I should try redownload it...it says its not a proper archive
wahoo!
So that worked! I down loaded the file Acer_AV041_A500_1.033.00_PA_CUS1 and extracted the update. I palced the update on the sd card and booted with the power and sound volume pressed down. it went through the installation procedure and restarted twice before saying it was upgrading my aps and BOOM its got ICS and everything looks great. Thank you so much for your help and I hope that this paper trail is able to help someone in the future
My problem is that I'm on ICS and I'm rooted, but I just can't download a custom recovery. I've tried, and I haven't gotten anywhere
Sent from my SPH-L710 using Tapatalk 2
Related
I have successfully flashed my Sprint THC hero with no problems.
My issue though is flashing the phone to 2.1d. i can't for the life of me follow these directions and I am really stumped on the process of doing a nandroid and flashing the ROM.
I downloaded the nandroid from this site but not sure where I put the directory with the files at. Can anyone break this process down into "ejpyle terminology"?
My problems are:
- where to copy the nandroid directory
- where to put the 2.1d ROM
- do i need this busybox that everyone is talking about?
Successfully flashed what? And what method.
If you mean you successfully ROOTED your Phone then huzzah, that's step one complete.
Part of the rooting process should include putting a recovery image on the phone. If you did that correctly then do this, power off the phone.hold down the home button and power it back up. In a few seconds you should boot into a recovery menu with options to do a nandroid backup/restore turn on the usb connection to move files to the phone from your pc, and flashing a zip. If you don't have this recovery menu then you need to install it.
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
gunnyman said:
Successfully flashed what? And what method.
If you mean you successfully ROOTED your Phone then huzzah, that's step one complete.
Part of the rooting process should include putting a recovery image on the phone. If you did that correctly then do this, power off the phone.hold down the home button and power it back up. In a few seconds you should boot into a recovery menu with options to do a nandroid backup/restore turn on the usb connection to move files to the phone from your pc, and flashing a zip. If you don't have this recovery menu then you need to install it.
Click to expand...
Click to collapse
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
ejpyle said:
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
Click to expand...
Click to collapse
Not to be rude, because you seem like a decent enough person, but please read http://forum.xda-developers.com/showthread.php?t=668905 before asking anything else. Most of your answers are there, and 'search' will find the rest.
Kcarpenter said:
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
Click to expand...
Click to collapse
You rock....You just taught a death and blind monkey how to do it. Thanks man!!!!! I will be sure to have my wife hold the phone for the vibrate thing. LMFAO
ejpyle said:
thank you thank thank you... you have me going in the right directions.
Quesion..what is the best (most reliable without as many bugs) ROM to load that is 2.0-1?
Click to expand...
Click to collapse
There is no best one. The 2.1 ROMS are all very stable. Just avoid the ones that say {DEV} in the thread title because they are under development and likely have lots of stuff broken in them.
Decide what you want for yourself, beauty, speed, both? A good hint is to look for the ROM threads that have the most pages attached to them these are the ROMS that have the most discussion and help within them.
ejpyle said:
You rock....You just taught a death and blind monkey how to do it. Thanks man!!!!! I will be sure to have my wife hold the phone for the vibrate thing. LMFAO
Click to expand...
Click to collapse
DO NOT FLASH THE 2.1 Signed RUU Test ROM
OR I WILL FIND AND KILL YOU!
gunnyman said:
There is no best one. The 2.1 ROMS are all very stable. Just avoid the ones that say {DEV} in the thread title because they are under development and likely have lots of stuff broken in them.
Decide what you want for yourself, beauty, speed, both? A good hint is to look for the ROM threads that have the most pages attached to them these are the ROMS that have the most discussion and help within them.
Click to expand...
Click to collapse
thanks man, if I win the power ball lottery I will be sending you all a private message.
one more quickie though, If Sprint releases the 2.1 before I become eligible for AARP will I have to flash back to the 1.5 version before updating my device with it?
Kcarpenter said:
I don't think you have downloaded a Nandroid, I think you have downloaded an "update.zip" as we so affectionitly call them around here. This is a term used from the first set of recovery tools we had, where we had to rename update files update.zip to be loaded. Thankfully the recovery software has been updated to let us store and use multiple files.
So you probable have fresh-cdma-hero-2.0d.zip downloaded.
Plug your phone into USB and set it to Mount SD Card or what ever it says in 1.5
Copy this file to the root of the sdcard. don't put it in to any folders just F:\ or whatever the drive letter is.
THEN
Unmount the sdcard or turn off the disk drive mode (Cant remember what 1.5 calls it)
THEN
Power off the phone.
Power the phone back on whilst holding the home key. When you feel the vibration (let your girl hold it if she wants ROFL) let go and it will boot into recovery.
THEN
Go to Wipe...do Factory Reset
THEN
Wipe dalvik
THEN
Go back to Flash Update from SDcard
Select the update file above and hit the home key to flash it.
The phone SHOULD install and go back to the main screen of recovery.
THEN select
Reboot
THEN
Wait a hell of a long time 10+ minutes is NOT uncommon (it has to rebuild dalvik and other stuff)
THEN
When the phone boots hit Always Allow for the memory settings app.
THEN
Setup all your google info again.....
THEN
You should be good to go
AND DEN????????
HAHAHAHAHAHAHA
EDIT:
I am SURE that I left a step out above, just go with the flow and wipe everything under the wipe menu. It's laid out so a monkey can do this stuff...hence the reason I am able to.
Click to expand...
Click to collapse
I hope the possible step left out above does not give me "another" bricked phone.
ejpyle said:
I hope the possible step left out above does not give me "another" bricked phone.
Click to expand...
Click to collapse
I think I may have left out a step if you have apps on your sd card...
NOT WAIT I LEFT OUT THE DO A NANDROID BACK UP FIRST!!!!!!!!!!! DO THAT FIRST!!!! HOLY CRAP I HOPE YOU HAVEN'T DONE ANYTHING YET!!! DO A NANDROID!!!!!!!
Nope no chance at all of that as far as I can tell.
The only bricks we have seen are from people downloading GSM software or dropping a brick on their phone...that sounded funnier in my head.
smw6180 said:
Not to be rude, because you seem like a decent enough person, but please read http://forum.xda-developers.com/showthread.php?t=668905 before asking anything else. Most of your answers are there, and 'search' will find the rest.
Click to expand...
Click to collapse
Because you too seem like a decent person I will share this with you....
I followed a thread on here at the beginning of march to install a ROM and the directions (which I followed exact) bricked my phone. I spent hours reading up on this website to find out after the fact that the RUU might have a bug and some users will have issues. With that said, I decided to ask questions. This site has a lot of cleanup going on (no disrespect to anyone here as you are all VERY intelligent) and I do not think that someone as myself would be comfortable just "searching" for the answer without asking questions first with respect to the experience we have had in the past.
Kcarpenter said:
I think I may have left out a step if you have apps on your sd card...
NOT WAIT I LEFT OUT THE DO A NANDROID BACK UP FIRST!!!!!!!!!!! DO THAT FIRST!!!! HOLY CRAP I HOPE YOU HAVEN'T DONE ANYTHING YET!!! DO A NANDROID!!!!!!!
Nope no chance at all of that as far as I can tell.
The only bricks we have seen are from people downloading GSM software or dropping a brick on their phone...that sounded funnier in my head.
Click to expand...
Click to collapse
LOL I have not done it yet. I am about to copy this nandroid - file name "nandroid-2.0.zip" to my SDCARD. then i will do it.
ejpyle said:
LOL I have not done it yet. I am about to copy this nandroid - file name "nandroid-2.0.zip" to my SDCARD. then i will do it.
Click to expand...
Click to collapse
So you have gotten me curious now, where did you pick up that file at?
My only guess is that someone has posted a nandroid of their device and zipped it. Most of the Rom downloads are ROMNAME.zip....
You can always try to load it, it won't load if its not setup properly inside for a rom.
And about your going back to 1.5 to update to sprints 2.1:
IF YOU UPDATE TO SPRINTS OTA 2.1 UPDATE YOU WILL NOT BE ABLE TO ROOT AGAIN UNTIL SOMEONE FINDS ANOTHER EXPLOIT!!! WHICH COULD BE NEVER!!
Kcarpenter said:
So you have gotten me curious now, where did you pick up that file at?
My only guess is that someone has posted a nandroid of their device and zipped it. Most of the Rom downloads are ROMNAME.zip....
You can always try to load it, it won't load if its not setup properly inside for a rom.
And about your going back to 1.5 to update to sprints 2.1:
IF YOU UPDATE TO SPRINTS OTA 2.1 UPDATE YOU WILL NOT BE ABLE TO ROOT AGAIN UNTIL SOMEONE FINDS ANOTHER EXPLOIT!!! WHICH COULD BE NEVER!!
Click to expand...
Click to collapse
I got it from here....
http://dx.infernix.net/nandroid-2.0.zip
when you boot into recovery, what do you see?
If you rooted correctly and put a recovery image on there there isn't anything else you have to do to enable Nandroid.
ejpyle said:
I got it from here....
http://dx.infernix.net/nandroid-2.0.zip
Click to expand...
Click to collapse
Ok, so this leads me to another question. Where is the thread that links to this download?
The reason I am worried about this file now that I see it:
It's only 942kb - WAY to small for a rom or nandroid.
gunnyman said:
when you boot into recovery, what do you see?
If you rooted correctly and put a recovery image on there there isn't anything else you have to do to enable Nandroid.
Click to expand...
Click to collapse
I had a triangle with an exclamation point.
I am copying the recovery to my SDCARD now... recovery-RA-heroc-v1.5.2
ejpyle said:
I had a triangle with an exclamation point.
I am copying the recovery to my SDCARD now... recovery-RA-heroc-v1.5.2
Click to expand...
Click to collapse
1.6.2 is the latest. Not a whole lot different from 1.5.2 but some bugs where fixed and you can get the nifty Green Nexus Carebear back ground.
Kcarpenter said:
1.6.2 is the latest. Not a whole lot different from 1.5.2 but some bugs where fixed and you can get the nifty Green Nexus Carebear back ground.
Click to expand...
Click to collapse
I copied everything you indicated to my card. When I press HOME and PWR together I get a triangle with an exclamation point. Did this monkey not do something right?
if your have issues with the update not finishing 100% this will work
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
download the zip using heimdall flash like normal
factoryfs-factoryfs.rfs
zimage-zimage
param.lfs-param.lfs
cache-cache.rfs
recovery-zimage
ignore the rest of the files
then before first boot wipe data and cache reboot
manually use update.zip or just let it download itself
install update and your done
you can verify by going to "about device" build number will be SCH-I800.EC02
use superoneclick for root z4mod not working keep getting f/c's
it seems like anybody who used z4mod to root or flashed recovery "back to stock" is having problems a 100% fix is just download the files from my post and flash like normal then use superoneclick for root
***for it to work you must download the recovery files from my post***
the files in my post are created using a temp. root so the files are a pure clone of unrooted rom 100% stock that is why you have to use superoneclick to root I tried everything and have done this to 6 tabs with no errors
EC02 stock ota update.zip download
http://www.4shared.com/file/qIHEta11/update.html
Thanks, I noticed you posted this on the other thread too. I have never used Heimdall so I was REALLY trying to avoid this but I guess I will have to take the plunge and figure it out.......
this works
I have tried every which way and this way has worked every time for me
Finally worked
works 100% just followed the steps and no problems finally updated!!!!!
It works, 100% Thank you so much for this
This does work, 100%, but please note that it DOES NOT WIPE THE DEVICE. It will boot up with all your stuff. This is not neccessarily practical, but it will probably be fine. If you have any root dependent mods, such as set cpu or lcd density, they wont work and it may operate funny/slow until you reroot and set them back up.
stock restore files download
http://dl.dropbox.com/u/21215221/Verizon-GTab-Stock.zip
or
http://www.4shared.com/file/3skyGV3V/Verizon-GTab-Stock.html
Download Mode (Volume down and power)
Download Heimdall from Here:
http://www.glassechidna.com.au/products/heimdall/
Also just below version 1.1.0 is Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses.
Launch download mode on your tab that is already connected to your PC.
unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device or might say it other ways
Click start and let heimdall download the drivers. Once its finished, close zadig and launch heimdall front end leaving Tab plugged in and in download mode
Unzip the stock files.
the zImage goes in both the Kernel AND Recovery slot.
The factoryfs.rfs goes in Factoryfs
The Param.lfs goes in Param.lfs make sure you use param.ifs not param.rfs
and the cache.rfs goes in the cache slot.
ignore the rest of the files in the zip and just use these
After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
After this runs you will more then likely have to Power down, wait a few seconds and hold power and up volume to boot into recovery. (NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
then let update download install it and you can use superoneclick if you want root back
This worked!
Thank you lexriley! That seemed to work. I forgot to wipe data/cache before i applied the update.zip, it still worked anyway. I should probably have wiped the data/cache.
Thank you !!!!!! Great Work!
Thanks so much. I rooted using Z4 and the update failed. I used your instructions and got up and running again! You saved my Tab!
I'm happy its working for everyone like it worked for me
100% fully working!!!!!!!
thank you lexriley your guide is easy to follow and do your the man!!!!!!
This should be a sticky!!!!
Sent from my ADR6300 using Tapatalk
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
oldmacnut said:
Anyway to turn off the nagging update notification?. I have my tab where I want it, while your walk through is detailed and obviously a good solution, seems like an awful alot of time just for a minimal upgrade in software?.
Click to expand...
Click to collapse
Well let me tell you what I have noitced with the upgrade
1) Stock browser speed is faster, but I dont use the stock so that wasnt much help
2)There is now a item in the top of settings for you to activate your device through verizon (like you would using *228 or whatever it is from your phone)
3)The wifi searching thing. I often forget to turn wifi off so when I drive it drains battery searching, the drain is significantly less now.
4) BLUETOOTH HID SUPPORT! Sorry for the caps but I have been wanting this one for quite some time now. First thing I did was try my MX5500 at home and it paired up and worked perfectly.
5)Hyperlinks in emails issue. Constantly many hyperlinks were cut off and I wasnt able to click them, this has now been resolved.
If none of these things are appealing to you then by all means you have no need to upgrade. But I found that most of this was a welcomed change. The tab seems faster, but I believe that is just due to the fact that I do not have LCD density changing the density, which I find slows down many things on the tab.
lexriley said:
I'm happy its working for everyone like it worked for me
Click to expand...
Click to collapse
At first it didn't work for me. I got "failed to access device. Error: -12". But that was my fault. I had forgotten to load the zagdig drivers for Heimdall. So I did that following the instructions in this thread and tried again. First try, I simply got a "fail", second try worked like a charm. When finished the Tab rebooted on its own.
As soon as it rebooted, I got the message that an update was waiting to be installed (EC02). Since I had already wiped the cashe (twice) on earlier attempts, I just went ahead and let the update install. Worked like a charm and now I've got EC02 update.
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Now to begin the task of re-rooting, installing ADW, and putting my Tab back into shape the way I had it.
BIG THANKS goes out to lexriley!! (And by all means, make this thread a sticky.)
Robin
Excellent work! This worked perfectly.
Got it, installed the newest Keis for drivers.
i hate to be that guy but is it possible to get odin files too? i can never get heimdall to work but odin works just fine
Robin M said:
As a help to other noobs, I will add this.... The reason the update would not install in the first place is that I had deleted the VZW Vcast bloatware. Lexriley's fix here reinstalled all that VZW junk, which is what ultimately solved the problem. LESSON LEARNED: If you want future updates NEVER delete pre-installed apps. Either rename them and back them up to the SD, or better yet, "freeze" them with Titanium Backup.
Click to expand...
Click to collapse
So if I just restore the vcast stuff then I should be able to update without doing all the recovery stuff? I just renamed them all with a .bak at the end instead of deleting just incase I needed them again so I still have them all.
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
shiltz said:
Edit: apparently yes, removed the .bak I added to the files names, un-rooted, clicked update and it worked fine
Click to expand...
Click to collapse
You're welcome. ...Isn't it great when you answer your own questions? I find myself doing that more frequently now, as I learn more about Android and my Tab - mostly from this forum.
PS... Now that you've successfully updated, take a look at the recovery.log file in your /cashe/log folder. I was amazed at the number and the variety of files this upgrade patched.
Okay, i know that all the files and answers are in here somewhere, but they're strewn across dozens of posts and I can't figure out the exact process i'm supposed to use. here's the scoop:
i have an a500 (obviously) running:
android 3.0.1
kernel 2.6.36.3-00001-gf991e5d
build number Acer_A500_1.016.05_COM_GEN1
Flex version 05_COM_GEN1
device info version 1.0
if its important, the laptop it connects to run win7 home premium 64.
I rooted my device and nuked a bunch of crapware. now when i try to update it fails. the cache log says its failing because acersynchelper.apk is not there, but there will be several files missing.
I think what i need is either 1) the stock build for my version or 2) the stock updated build, and instructions on how to make the whole thing work. i have terminal emulator and i installed a bunch of Android SDK and Java SDK on my laptop while i was trying to follow the instructions on this site, but i couldn't figure out what the straight line to fixed is. any help would be great. and its my first post, so maybe keep the calling me an idiot thing to a minimum...
some is okay, of course. thanks in advance!
Plug in a USB keyboard, then boot up the tab by holding the power button and volume down (the side closest to the power button) at the same time until text starts appearing in the upper left corner of the screen. Hit the home button on the keyboard, and boom! You are in a recovery screen. Use the keyboard to select factory reset, and your tab is back to the original state.
well, that returned me to stock in that it wiped everything i've installed, but i still have root and i'm still missing the necessary .apks to pass the pre-update check. its still erroring on acersynchelper.apk
Hmmmm when I did it, it returned me to stock, and I checked it and had no root, had to re-root. Anyone else want to chime in?
A good idea might be to post a .zip with all the apps from various versions so people like me who deleted instead of renaming can fix their issues. Rest assured, i won't be making that mistake again.
I gave up looking. I dont know what happen because i rooted my tab and somehow i cant go back. I did factory reset but no luck. I just wanna go to back to 3.1 so i could update my gtab to 3.2. I know its here in this thread but i cant find it (i tried) . If you could just help me out so i could update to 3.2 that would be a help. THANKS SO MUCH!!!!
JESSICA
Hiya, I haven't done this, but will try to help anyway.
Can I ask first, why do you want to go back to the "factory" state? Do you need to return it?
Edit: coz just having root access does not stop you updating to 3.2...
factoy reseting your device will NOT WIPE SYSTEM and thats were superuser is. You need to Odin flash the firmware of you choiche. thats the best and easiest way, its done in 5 minutes. And i think its wise to not update while rooted as some have reported errors during update and some have not. good luck
Why not just flash Galaxy Task 10 Rom? It's 3.2 and much better than the stock 3.2. All you need is Clockwork Mod installed and you can do that with Odin.
I flashed it with Pershoots kernel and it runs VERY stable. You can also flash it with the stock kernel if you don't want overclocking, etc.
I bricked my galaxy tab. I want to go back to 3.1 so i could update it to 3.2. I dont know much aout hacking so I guess i messed up. Im trying to go back to 3.1 so i could update my tab to 3.2 then root it. However, i couldnt find any thread to fix.
thanks for your all reply. If I used 3.2 rom? will it stay 3.2 if I use other roms? thanks in advance
jessica
Well, a custom rom like Galaxy Task 10 is "3.2" and so yes, it will stay 3.2.
I'd recommend Task's rom, it's much better than the stock 3.2.
And no doubt he will update to Android 4 (IceCream Sandwich) so you'll be able to keep up to date.
Your comments about bricking your device are now confusing the situation.
Can you please write what steps you did (or thought you did), and what your device does or does not do right now?
Also, please be vey specific about what device you have, whether it is 3g+wifi or just wifi. Give us the model number from the box if you do not know.
We'll help, we just need details.
Cheers..
i have the 16gb wifi us version. I used odin and
everything went perfect but still cant update to 3.2 using kies. Kies say your tablet doesnt support firmware upgrade. What I did next is i tried to root my tablet
somehow it wont let me root and giving me this "your storage not prepared yet please use ui menu for format and reboot actions"
I downloaded termulator and root checker to see if im rooted however it says im not. So I cant download any roms or upgraded to rom 3.2.
Ive been searching online to how to fix it for almost 6 hours and cant find a solution. pls help!!! THANKS FOR YOUR HELP GUYS AND I REALLY APPRECIATED!
Jessica
I've put numbers (eg [*1]) in to your message quoted below;
killua_bryan said:
i have the 16gb wifi us version. I used odin and
everything went perfect [*1] but still cant update to 3.2 using kies. Kies say your tablet doesnt support firmware upgrade [*2]. What I did next is i tried to root my tablet [*3]
somehow it wont let me root and giving me this "your storage not prepared yet please use ui menu for format and reboot actions"
I downloaded termulator and root checker to see if im rooted [*4] however it says im not. So I cant download any roms [*5] or upgraded to rom 3.2.
Click to expand...
Click to collapse
1. Used ODIN to do what? Put in a recovery image? or replace a whole ROM?
2. Is a firmware upgrade available? There isn't for mine, I'm also on a 16g wifi version but no 3.2 FW has been released for my specific model yet...
3. How? By flashing a zip in recovery? Can you post the link to the information you used to do this?
4. These may give false negatives. Check in your apps list to see if you have "SuperUser". If so, run it, it will show you apps that have tried to ask for root access. They may have been asking but you didn't receive the prompt, and have therefore been denied root access. If so, grant them root and try to run them again.
5. Just FYI, you don't need root access to download/install a ROM, you need a "recovery".
Honestly, I think the best thing for you to do (besides answer these questions ) is to download the ROM Galaxy Task 10, boot into recovery, and flash it. That is assuming you do have a recovery image in place, which depends on the answer to #1 above.
i tried everything. it wont let me root the device. Tab keep saying your storage not prepared yet please use ui menu for format and reboot actions. So i cant use any or replace rom. I upgraded my tab to 3.2 before but kies keep saying its not upgradeable. Any suggestions? thanks!
jessica
Sorry, I need specific information to those questions from my previous post. As stated, replacing a rom doesn't need root, it needs a recovery image.
Maybe some screenshots of your tab and/or computer would help? Or photos, if you can't take screenshots?
Sorry, if you won't answer my questions I'm not going to be able to help.
ill try to post some pics. sorry!
killua_bryan said:
ill try to post some pics. sorry!
Click to expand...
Click to collapse
Start with answering the questions, please?
Pics can tell about "now" but I need the history too.
Back to Stock,
Here's what I did to get back to stock.
You must choose the files under the GTAB GT7510 /retail/google edition
First you have to install Clock Work Recovery using this link:
http://forum.xda-developers.com/showthread.php?t=1171089
Download the files under FilesForDummies 2 mirrors are listed. These files will help you flash Clockworkrecovery and also the retail recovery is included.
This step needs to be flashed through Odin. You also need to root your device after the flash if your not already rooted. You need the Clock Work Recovery to enter recovery mode so you can flash the Stock Files that I'll point you later.
Once you've flashed the Clockwork recovery you should reboot normally. At this point try to root your device if its not already rooted. Look for OneClickRoot I'll point to that later if you don't already have it.
Not too sure if you need to be rooted as I've always rooted my device before installing roms anyways, but you can try the next steps if your not rooted. If the next steps don't work then reboot and root the device.
Start with your tablet off.
1. Push Powerbutton as soon as you see it startup put your finger on the volume down button and press until you see the android. One side is a box saying recovery the other download. Choose download mode by pushing volume down to choose and up to enter you will be prompted at this time just take if from there. Make sure Odin is up and running, choose the PDA file as Clockwork cm4.04 its that file in the zip you just downloaded and extracted.
2. Flash Clockwork file Clockwork CM4.04 etc... using ODIN should be included in the zipped file you've downloaded. Make sure these files are unzipped in the same folder. Now after flashing the tablet should reboot and it would look normally like it did before except you have clockworkrecovery instead of the stock one.
3. Go back to the link I sent you above and scrool down until you see flashing roms and kernals heading. Click on Stock US Retail Rom, this will download the Stock US Retail 3.1 file for Clockwork. choose : hc-3.1_ota-full_sam file, and then also click on the recovery hc3.1 file.
Put these files in the same folder or somewhere where you can find them. Not sure if these are already in the file you downloaded above, if they are then don't have to download these.
4. Unzip the files and make sure you remember where they are.
5. With your tablet on and plug into your usb port transfer the hc-3.1 ota file you've just downloaded and put it into the root directory of your tablet. It should not be in any folders just in the /SD folder.
5. Now turn off the tablet, once off push power button again and enter recovery this time choosing the left android with the box. Push left button to choose and right volume button to enter. Now you should be in clockwork recover orange writing. Now look for update from Sd card, use volume button left to choose and right to enter. Click then you should see the file you've copied on your sd card of your tablet. Click down and then use left volume button to choose.
6. Once there it should start flashing the Stock Rom, once done it will return you to where you started, at this point you can choose to wipe data/ cache etc. You can do that to make sure you've clear everything in your tablet before you actually reboot. Once done choose reboot and your tablet should be back to stock but not just yet.
7. You could leave Clockwork on there or you can go directly back to stock by doing the same steps from 1 and 2 and flash the STock Recovery instead. This will bring the tablet right back to HC3.1 and Retail Stock. From this point on you can flash up to 3.2 etc.
Hope this helps but I can't go into it in any length as I'm hoping you know most of the terminolgy.
There is also videos on this link to help you.
nice
I suspect that if we see screenshots, that the wrong recovery has been flashed right from the start.
*Now Working for 4.3 Update* Will require an up-to-date install of 4.1.x first and then after re-boot, it will update to 4.3 (read post on next page).
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here https://www.dropbox.com/s/9wbux6a4kn0ndz9/StockRecovery-signed.zip
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
trickinit said:
I appreciate you writing this up. It seems like I've never been able to find a good solution to installing the OTA updates post-root. That being said, do you have any idea what happened in Step 7 that made it finally work? I just don't understand how doing the same thing over and over finally just worked. I want to try installing an update, but I'm a little nervous to do it. And I don't know how else to make the pesky update notification go away without installing it.
Click to expand...
Click to collapse
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Thank you for the info! Does sound like an awful lot of work though
jay_ntwr said:
I really have no idea why Step 7 got so strange. The only thing that gave me a warm fuzzy whatsoever was that others were reporting that it was hanging and they just rebooted the phone over and over until it got all the way through the process. It could have something to do with the stock recovery for all I know--a bug perhaps. Again, it made me nervous and I won't do it again. I only did the write up so folks could see what happens and make a call whether or not they wanted to try it themselves and see the steps all on one page instead of getting stuck like I did and then finding the rest of the steps. That part sucked. At least you'll know what you're getting into though. Good luck one way or the other. Please post up if you do go through with it and what your results are.
Click to expand...
Click to collapse
I'm thinking I'll give it a go. I'll do a nandroid backup and store it on my pc. Worst case scenario, I'll just start over from scratch, re-root, and restore my backup. I'll make sure to report my results.
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery? It's just one step more to flash the custom ROM and at least you will get constant updates with the developer who created the custom ROM. To me it seems like you either stay stock if you want OTA updates or go the whole hog and use custom ROMs. Just my 2 cents.
shadowboy23 said:
I just makes me wonder why bother using the OTA update if you already went through rooting and flashing custom recovery?
Click to expand...
Click to collapse
Well, in my case, I purchased the Dev edition straight from HTC so I automatically have a de-bloated OS from HTC instead of the ATT ROM that I would have gotten had I purchased the phone from the ATT Store. In that case, I'd no question have a custom ROM from the forum. I just didn't see the need this time around. I would have left the stock recovery, but I do like to make backups so ClockworkMod is something I can't live without. I suppose there are others in that same boat but they are probably few and far between. Really, I just hate to update my ROM since the phone is working how I want at the moment. It's hard to justify just blowing away a functioning OS, setting up everything again, etc. but I may do it again if the OTAs come frequently and/or the process is as strange as it was this past go around.
jay_ntwr said:
Warning:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Background:
I'm certainly not a developer but can wiggle my way around XDA and figure out what to do and how to do it from time to time without having to ask too many questions. This morning I got the notification that an OTA (over the air) Update was available for my HTC One Dev Edition (running the stock ROM) and I simply downloaded it and tried to flash the zip in Clockwork like I've done with countless other updated nightlies on various phones. It didn't work.
Solution:
I figured out after researching that the custom recovery wouldn't allow the OTA to be flashed and that the stock recovery would be needed to flash the OTA update. I also realized that it took a bunch of different threads to figure out how to make it all work and there didn't seem to be one thread on the HTC One forum that discussed how to do it so I figured I may as well write up what I did to help someone else--after all, so many folks have helped me on this forum and I've rarely had much to contribute of any real depth anyway--just repeating what others already had taught me.
How to:
You need to re-flash the original recovery to your phone so that CWM or TWRP are no longer your recovery. Obviously, now is the time to do a backup and I'd put it somewhere other than on the phone in case you really mess this up.
1. Get the stock recovery bits here http://www.androidrevolution.nl/downloader/download.php?file=Flash_recovery_2.17.401.1.rar
2. You'll need to un-pack the rar and there is a text file that has the instructions.
3. Of course, I didn't follow the instructions, I just plugged my phone into USB with debugging on and fired up cmd, changed into the directory where I extracted the files, cd'd into fastboot and typed "adb reboot bootloader" and waited until the phone rebooted into bootloader
4. I typed "fastboot devices" and hit enter to make sure I was connected to the phone still
5. Cd.. to get back to where the .bat files are and type install-recovery-windows.bat and the stock recovery is flashed to your HTC One.
6. Now unplug the thing and reboot and you'll get the notification again that the OTA update is ready to install and it will start to install.
7. Mine locked up. That's right, the damn OTA update stopped at about 1/4 of the way through. I figured I bricked the phone. I always figure I bricked it if something doesn't go exactly how I thought it would but I've never actually done it to any of my 6 or so devices. Then I found this thread: http://forum.xda-developers.com/showthread.php?t=2306996&page=2 and I turned off the phone by holding down the power and restarting it. It got all the way through and hung again so I reset the phone again. Then, it rebooted a few times and looked like it was going to never work right again, but I just let it keep rebooting and left it be and after a few minutes, less than 10, probably more than 5, I was back up and running and saw the android applications updating as expected after an update.
8. Now you'll want to re-flash your custom rom (TWRP, CWM) and I did that with Hasoon's All-in-one tool.
9. Re-get Root. You can do that with Hasoon's tool I suppose or however you prefer to root.
AGAIN:
Because of of how weird step 7 was, I'd recommend NOT INSTALLING THE OTA and just waiting for a ROM to have the changes incorporated. This is the last time I'll install an OTA I think as the whole thing was sketchy at best. However, if you just insist doing the OTA, that's how I did it. It may not work for you. You'll probably brick your phone as I may have just gotten lucky.
Hopefully someone will come up with a better way to do this and start a new thread and we can delete this one forever.
Click to expand...
Click to collapse
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Does sound like an awful lot of work though
greengoose_at said:
hi,
one question. this recovery.img i also can use for my htc one 802w? i use the original rom (4.1.2) on my htc one. i make s-off over htcdev.com install cwm802w.img . i become the info the system update to 4.2.2 is available but the phone cant install the update.
any people like help me?
best regards,
ps: sorry for my bad english
Click to expand...
Click to collapse
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
How to get s_off , supercid 11111111
and return to s_on with supercid ?please tell me quickly
Thanks for all friends
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
trickinit said:
I haven't been able to get this to work. I flashed back to the stock recovery, but when I attempt to install the update it gets about half way through before rebooting. It goes back into recovery, starts installing again, but then stops and just shows a red triangle with an exclamation mark. I can get the phone to reboot by holding the power button for 10 seconds, which boots it up normally. When it gets up and running, it's like nothing ever happened, but then the update notification reappears.
Click to expand...
Click to collapse
I'm experiencing the same thing, can't seem to find anything about it...
With the new 4.3 rolling out on the Dev editions, I decided it was time to try this again. What I found was I had to update to a something prior to the new 4.3. In other words, it was still one of the 1.29 streams that updated first and did just like the last time I did this. The thing stopped, locked up, had to hold the power button down, locked up again, reset again, then it was fine. As soon as the phone booted, the 4.3 update was available and I installed that without any issues. So, the method above still works and even with the weirdness I felt a little better this go around.
Good luck.
sunnyyen said:
Just find a stock recovery for 802w, flash it to your phone and you should be fine to to OTA. The original post didn't mention if he's using 802w. If he's not, then the recovery.img can't be used for 802w.
Click to expand...
Click to collapse
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Totally ran just fine
I had to as stated roll back to the attached recovery, did that with fastboot and no problems, then restarted the phone, then had it start the OTA update, then read around debating if I want CWM or TeamWin, but before I notice, the progress bar got up past half way. Looked away for what must've been less than 5 minutes until it vibrated and was restarting itself. It restarted again, and then it loaded and updated all the apps... Seemed like the smoothest rooted update I've ever done, no forced restarting or anything!
I just bought my HTC One last friday, and I think I screwed up things a little bit, because the first thing I did after I charged it, was updating everything to 4.3, before unlocking the bootloader, getting s-off and before rooting the phone. So I ended up with the latest 4.3 on my phone, but it was a pain in the ass to root it properly. I was able to unlock the bootloader, but something must be different with the way 4.3 treats the internal storage distribution, because I was only able to get root, using TWRP and the latest version of SuperSu, but I wasn´t able to install Busybox.
It's a little bit weird, because although I was able to use Titaniumbackup to install some apps, apps like OTA Rootkeeper don't work properly. I also lost the stock calculator, flashlight and voice recorder, but I was able to install older versions again.
I think the only thing I regret is not getting s-off first, but I think this will only mean that I will have to wait for a revone update, or I will have to flash the boot.img after flashing a custom rom as I always did with my One X.
jay_ntwr said:
I haven't really checked this thread in weeks. I'm not sure what an 802w is. If you can clarify, I'll check and post.
Click to expand...
Click to collapse
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
deepforest said:
802w is Chinese dual sim version with different radio frequency
Sent from my HTC One dual sim using xda app-developers app
Click to expand...
Click to collapse
That is not the one I have then.
I have a rooted HTC one with stock rom. I relock the bootloader and I also have stock recovery.
I am on 4.19.401.5 version.
So, will it be possible for me to have new OTA update including Sense 6?
Should I install the missing applications also, like calculator and flashlight?