Related
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.
I notices a few users have mentioned that they're dealing with trying to restore or unbrick their Continuum after flashing incompatible kernels and other problems.
I made this backup immediately after I got root, before I did anything else, to make absolutely sure I wouldn't be SOL if anything went awry. I've made absolutely certain this works, by unzipping and flashing on my own Continuum prior to uploading. It contains the system, recovery, and kernel partitions.
This file is also helpful if you need to get back to stock for warranty purposes, in which case you can manually un-root by using your favorite file explorer (I happen to prefer ES File Explorer), grant root permissions, mount system as rw, then manually delete SuperUser from /system/apps, su from /system/bin, and busybox from /systen/xbin. I hope this helps some of you who have been stuck.
You don't need to be rooted to flash this. Simply unzip, flash the .tar.md5, and you're golden. If you end up in restore mode after flashing, you probably need to do a hard reset, but this is unlikely as I tested it by flashing this a few times after installing various programs from the Market and never had to do a hard reset.
Don't forget to put your phone in Download mode by removing the battery, then holding the vol down button while inserting the usb cable. Good luck!
http://www.mediafire.com/?a897dbakz4j7k4f
Thanks for this. I had been messing around with the phone. I was able to get it back to stock.
Kay I try to flash this and it's telling me it's an invalid image type
Never mind, I got it. Thanks
Not a problem, glad I could help!
My phone was soft-bricked. This worked like a charm. Thank you so much!
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
kingtuk1 said:
I ran this and everything passed then when i boot up the phone with animations and sound after the animated verizonwireless logo is up for a while; everything goes black.
any suggestions? never mind I had to do a wipe then it worked
Click to expand...
Click to collapse
Yup, gotta wipe! At first it's so easy to forget this step. When you get to customizing your installation, you'll get to used to having to wipe it'll become second nature!
I'm so glad to hear this is coming in handy for you all! Now that you got this done, get yourself froyo, courtesy of imnuts: http://forum.xda-developers.com/showthread.php?t=1197415
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Native89 said:
Ok after having installed EC03 Froyo via imnuts's thread. Everything was going fine except for some bugs here and there. Fast forward a couple weeks later and I try to fix those bugs by installing a stock odin rom via torque's thread (seems so foolish now that I look back on it). Which brings me to today and my bricked Continuum.
Well to explain further I tried to install the odin Rom only to receive a FAIL in the end (Selected the md5 file through the PDA option and proceeded to flash). Disconnected afterwards only to find out I can't even get the Samsung logo to show up or the phone to charge, but the phone will still go into download mode.
And this leads me to this thread with the same outcome. I've tried flashing this eclair? image only to end up with the fail message again. After the recovery.bin stage it just says "Complete(write) operation failed." Any help with this matter would be appreciated.
Edit: After some searching, gonna try it with imnuts' DL17 image. Will post results.
Edit2: No luck with that either. Guess I'll just wait until the Bionic gets released, but for now I'll have to dig up my dumbphone.
Click to expand...
Click to collapse
Read the OP from pastorbennett here: http://forum.xda-developers.com/showthread.php?t=1203597 and try the unbrick process. You can do a search for pastorbennett and trailblazer. Both have posted "recovery processes", or at least links to others that have posted recovery processes. They've saved my butt a couple of times... Except on my first phone that wouldn't go into DL or Recovery Mode. It would just flash the Samsung logo, over, and over, and over again... That happened before pastorbennett posted the unbrick info. Oh well, Verizon replaced it under the hardware warranty. Thankfully.
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Native89 said:
Looks like I didn't search hard enough.
Thanks for the link Moon. I will be trying this ASAP.
Hit a little bit of a snag trying to get it to work. It told me to install drivers for my device, however my Phone does not show up in the dropbox and the only related thing I can find is "Gadget Serial".
I've tried uninstalling the drivers, but Win7 is being a fool and automatically installing drivers for me.
Click to expand...
Click to collapse
Okay, if you can, grab a different computer (either Windows XP or Windows 7) and install the samsung drivers from this post: http://forum.xda-developers.com/show....php?t=1203597. The hint here with ANY Windows computer is to install the device drivers FIRST! (I've been a system administrator for about 20 years.) Then plug in the hardware. It usually makes the installations go MUCH smoother.
If you have to use your computer, try installing the Samsung drivers first, then plug the phone in.
zzir said:
Does anyone know why i get a 'FAILED' after trying to flash this with Odin? My phone is soft-bricked btw.
Click to expand...
Click to collapse
The key to odin seems to be this:
1. Start odin.
2. Click the PDA button and select the odin TAR or MD5 file. (You can only do one. Not both.)
3. Make sure the phone is not plugged into the computer.
4. Make doubly sure the phone is not plugged into the computer.
5. Put your phone into download mode. (With the phone off, hold the Volume Down button and turn the phone on.)
6. Then plug the phone into the computer.
7. Start the odin flash and you should be good to go. Also, before unplugging the phone, make sure it says either success or failed. If it doesn't say anything, or says loading (or something like that), WALK AWAY! Go get yourself a cup of coffee, a soda, a nice cup of tea... Something. I recommend waiting at least 10 minutes. If the progress bar has not moved, in that time, okay, then pull the cable and the battery and start again.
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Tarheel487 said:
I tried to do this, but when it boots into recovery mode, it says update.zip is gone. Any ideas why this might be happening? Also if it's like this, will Verizon take it back within the 14 day return policy without charging me anything?
Click to expand...
Click to collapse
Did you flash the CWM Recovery in Odin? (cwm_recovery_test4_adryn.tar) Can be found here if not http://forum.xda-developers.com/showthread.php?t=1230072
is it possible to flash this with heimdall or only odin?
ntien said:
is it possible to flash this with heimdall or only odin?
Click to expand...
Click to collapse
I don't know, however, pastorbennett posted this http://forum.xda-developers.com/showpost.php?p=16600453&postcount=29. It might help? I use Linux at home to build most of this stuff, then use my wife's Windoze machine to flash. It just seemed easier.
Yes, you can use heimdall, you just need to extract this .tar and put the extracted files in the corresponding location in heimdall xD
Sent from my SCH-I400 using xda premium
yeah i saw that but in heimdall 1.3 the UI is different. i don't know where to put any of the stuff. i have the .tar but i dont know where to put the other stuff. here's a screenshot
I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
If you have the paid version of the TiBu then you can freeze it with that.
1.ATRIX-in-PT said:
I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Click to expand...
Click to collapse
What's wrong with 4.5.141? I installed it and just rerooted/unlocked/flashed
Hi live4nyy !
Thanks. The file is /system/app/Upgrader.apk ?
Hi ericc191 !
Probably you are right and nothing is "wrong" with 4.5.141 and "no risk, no fun". But it seems, that it includes just some little improvements.
It's not a real system update, so I am not very much in the mood for all this struggle to get my Atrix back to normal after the update (rooted, unblocked and not bricked).
Yeah, upgrader or updater. One of those
1.ATRIX-in-PT said:
Hi live4nyy !
. The file is /system/app/Upgrader.apk ?
Click to expand...
Click to collapse
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
If you're in Titanium Backup, then it's called Updater 2.3.4.
If you've already downloaded the update, then you might also need to boot into recovery and wipe the cache partition to erase the update file.
live4nyy said:
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
Click to expand...
Click to collapse
this didnt work for me
das8nt said:
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
Click to expand...
Click to collapse
this did the trick
Yesss! No more annoying notifys!
hi all,
since the update was popping up from time to time and never really researched how to turn it off today, I friggin accidentally pressed on "install update" and automatically tried to reboot the phone, when I realized the mistake, I quickly pulled the battery out and waited for a few minutes then switched it back on.
it booted up fine but once it completes its bootup sequence, it would again prompt for an auto restart and try to install the update. Seems like the update is on the auto startup items (if there's such a thing).
I tried booting into safemode but can't get to do it maybe because I'm using an Alien build rom.
Any ideas on how to solve the problem? Please note that the phone boots but it tries to restart as soon as I can use it.
I have booted up now to recovery and will try to delete the updater apk and see if that will work. thanks in advance!.
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
*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?