Related
Hi
I'm going to update my a500 to 3.1
I have unrootedmy device but how to remove CWM completly????
Please help
Why don't just update via CWM:
http://forum.xda-developers.com/showthread.php?t=1154492
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Do you know where can I find stock recovery for my version?
I have Acer_A500_1.139.05_COM_GEN1
thank you!
simonsgray said:
1) re root your device
2) go into acer recovery installer and reflash to the backed up recovery (or do the stock recovery for your version)
3) de root.
I had to do this to get my update to work.
Click to expand...
Click to collapse
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Thanks! I used stock one in ARI, woks good.
simonsgray said:
When i installed ARI, it backed up my current recovery. When i went back into ARI, my old recovery was the first option. Sorry, explanation sucks, i don't have screenshots for you. I know there are threads with most of the software/firmware elements of most of the different versions, maybe do some digging? This would be the best place to start: http://forum.xda-developers.com/showthread.php?t=1126364
Click to expand...
Click to collapse
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Hi Euclid, are you able to post a copy of that install-recovery.sh file? I don't seem to have it in my system/bin anymore
...That is assuming the file is not unique to each device??
I'm thinking the reason my OTA update wouldnt install is because i dont have the stock recovery menu.
Thanks!
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Floatingfatman, that is exactly what I did, and it worked perfectly. Good advise!
FloatingFatMan said:
I really don't get why everyone is spazzing over this... If you've already taken the steps to root and install CWM in the first place, why not just install the stock 3.1 image that's been provided in the dev section? It's 100% stock, no need to wait for Acer to stop twiddling their dangly bits...
Click to expand...
Click to collapse
Yeah thats what i ended up doing to update it to 3.1.
Reason i want it back to stock is that i couldnt update via OTA at all (downloads fine but install fails at ~20% with the ! in a red triangle).
I was hoping by restoring it to stock the OTA would work, and so any future updates could also be done via OTA as opposed to finding a workaround each time.
Other than that, it's working just fine for now.
Euclid's Brother said:
Look in system/etc for a filed called install-recovery.sh. if its there change its permission from 444 to 544. Then reboot normally. It'll overwrite cwm with your stock recovery.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
I don't understand 'change permission from 444 to 544'. Root Manager lets me choose between, 'Read, Write or Execute'. Could you please elaborate?
Thanks
Never mind. Problem solved.
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
dccxviii said:
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
Click to expand...
Click to collapse
You cannot get root back without a custom recovery. OTA will not relock the bootloader, you'll just lose root and custom recovery.
You need to flash custom recovery using fastboot, then flash superuser to get root back. There are plenty of guides in the stickies describing the process.
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
The superuser app checks to see if you have the latest superuser binary and will download and instalk it. Or download superuser from within rom manager.
Sent from my Nexus S 4G using xda premium
Ok..the binary update fails (because i don't have root) so it's chicken and egg as far as I can tell.
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
dccxviii said:
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
Click to expand...
Click to collapse
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
albundy2010 said:
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
Click to expand...
Click to collapse
You've misunderstood what i'm after. Thanks for trying to help tho
irishrally said:
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
Click to expand...
Click to collapse
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
dccxviii said:
You've misunderstood what i'm after. Thanks for trying to help tho
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
Click to expand...
Click to collapse
Turn off signature verification in CWM and try again.
irishrally said:
Turn off signature verification in CWM and try again.
Click to expand...
Click to collapse
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
dccxviii said:
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
Click to expand...
Click to collapse
You're welcome.
If you stick with a stock ROM then recovery will reflash every time you reboot. To prevent this you can go to system>etc, and change the file install-recovery.init to something else like install-recovery.init.bak.
I know I'm not the only one who can't Odin flash CWM and actually get it to stay after reboot
So, anybody working on an easier, more reliable method?
Migital Warfare said:
I know I'm not the only one who can't Odin flash CWM and actually get it to stay after reboot
So, anybody working on an easier, more reliable method?
Click to expand...
Click to collapse
I was able to get it to stick just now by using this kernel... http://forum.xda-developers.com/showthread.php?t=1307980
Flash mkasik's key fix kernel mentioned above *before* you flash clockwork. Then it will stick. I posted this over in the purple clockwork recovery thread but I don't think its gotten a lot of attention. If you use heimdal you could pull the zimage and recovery.bin from the tar files and flash them at once as well. That should work too.
chrisott9628 said:
I was able to get it to stick just now by using this kernel... http://forum.xda-developers.com/showthread.php?t=1307980
Click to expand...
Click to collapse
Did you Odin the keyboard fix kernel before CWM, or at the same time? If you did it at the same time, does the kernel go in the Phone slot?
Thanks Stilesja
Migital Warfare said:
Did you Odin the keyboard fix kernel before CWM, or at the same time? If you did it at the same time, does the kernel go in the Phone slot?
Click to expand...
Click to collapse
I flashed the kernel first, rebooted and then flashed recovery. I used the PDA slot each time.
Migital Warfare said:
Did you Odin the keyboard fix kernel before CWM, or at the same time? If you did it at the same time, does the kernel go in the Phone slot?
Thanks Stilesja
Click to expand...
Click to collapse
Glad to help, what made me think of that is I remembered back when purple clockwork came out you would still go into orange clockwork if you did a reboot recovery from the Clockwork App, and it was because there is actually a copy of recovery built into the kernel, then everyone updated their kernels with the new recovery and it was always purple. So when this happened I thought that sprint must have done something to send the three finger boot into the kernel recovery, turns out that must have been the case because a custom kernel fixes it.
The problem is that after (any) OTA update, the phone will reflash the recovery kernel with the stock boot kernel image on every boot, unless the recovery image is already "up to date". Here's the longer explanation.
Anyways, there's two fixes:
1. Flash a custom kernel, then a custom recovery. (As other have noted.)
2. Once rooted, use root explorer or something to delete the files: "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p". That will let you run the stock EI22 kernel with a custom recovery.
XDA ROX
Thank you folks, you have the questions asked & answered (typically) before I can even ask. Just need to look!!!
mkasick said:
The problem is that after (any) OTA update, the phone will reflash the recovery kernel with the stock boot kernel image on every boot, unless the recovery image is already "up to date". Here's the longer explanation.
Anyways, there's two fixes:
1. Flash a custom kernel, then a custom recovery. (As other have noted.)
2. Once rooted, use root explorer or something to delete the files: "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p". That will let you run the stock EI22 kernel with a custom recovery.
Click to expand...
Click to collapse
Very interesting read (I actually read your "long" explanation a couple of days ago, then re-read it just now), thanks for the excellent, informative explanation! <Thanked>
[TIPS AND DISCUSS] ICS update DOES NOT *ALWAYS* BREAK ROOT (& other tips and reviews)
This is not intended to be a bug-sharing thread, report them if you wish, but I'm sure there will be entire threads devoted to this, so keep this in mind when posting.
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried. Dlpkgfile available HERE NOW!
luna_c666 said:
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried. Dlpkgfile available HERE NOW!
Click to expand...
Click to collapse
Cheers luna ... just need a WW version
Noob question though ..... I am on a custom ROM. I have CWM recovery.
I thought I couldnt update OTA if my TF was rooted ? or is it that I have the custom recovery that prevents this ?
I can flash back to stock easily - its removing CWM and unrooting that looked to be the more techie issue.
With what you are saying is there an easy way, once I have reverted to stock ROM, to revert to stock recovery without losing root ? Or do i even need to revert to stock ROM ??
Can update if rooted, but need to be on a stock ROM and stock Recovery image in order to successfully install. Download the 8.2.3.5 US recovery file located here :http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/, flash it through CWM and you have now overwritten your CWM and gone back to stock. Ready to update from there. Cheers!
so what is the procedure to update? Rename it, put it in microsd root and reboot into recovery?
another question, i cannot root with nachoroot, so is it possible to root with 1-click root?
asder00 said:
so what is the procedure to update? Rename it, put it in microsd root and reboot into recovery?
Click to expand...
Click to collapse
That might work, I don't know exactly because I got the FOTA pushed to my device and updated through the 'official' update process. I honestly have no idea how the dlpkgfile is even packaged, if it is CWM flashable or requires stock recovery etc., honestly my first time fooling with capturing the OTA files.
Ok I'm trying and I will tell u....
I don't care about root right now...
luna_c666 said:
Can update if rooted, but need to be on a stock ROM and stock Recovery image in order to successfully install. Download the 8.2.3.5 US recovery file located here :http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/, flash it through CWM and you have now overwritten your CWM and gone back to stock. Ready to update from there. Cheers!
Click to expand...
Click to collapse
Do I understand correctly that I only have to do Step 7 of the tutorial? and then install ICS (regular update process)?
I am rooted and I have CWM (no custom ROM)
So first impressions luna? Might as well start a discussion to keep the post on top and visible.
Did you run Spark? If so how does it compare?
Positives negatvies
Yes I do realise that you have had it for like 12 seconds but first impressions are nice.
Sent from my Sparkified TF101
Dreamboxuser said:
So first impressions luna? Might as well start a discussion to keep the post on top and visible.
Did you run Spark? If so how does it compare?
Positives negatvies
Yes I do realise that you have had it for like 12 seconds but first impressions are nice.
Sent from my Sparkified TF101
Click to expand...
Click to collapse
Unfortunately I never did get around to trying the latest Spark, I saw the complaints about touchscreen issues and decided it might be best to wait for Paul to work it out, but Asus finally got the upper hand on him!
Seems a treat, but I expected as you can see I've been running CM9 on my epic for about 3 weeks now. Much snappier, generic comments that have already been posted- but not explored completely yet, too busy helping others get their own ICS since the update came in to be selfish and sign off yet
Steven, I'm not sure which step 7 you are referring to but you will need a stock recovery in order to flash the file. CWM will flash files that have been repacked for CWM usually, and OTA updates install from the cache partition so CWM will not be able to install the OTA. CWM can flash it manually, I THINK (not sure if it needs to be repackaged for that to occur or not), but CWM will not install the OTA through the normal OTA process.
luna_c666 said:
Steven, I'm not sure which step 7 you are referring to but you will need a stock recovery in order to flash the file. CWM will flash files that have been repacked for CWM usually, and OTA updates install from the cache partition so CWM will not be able to install the OTA. CWM can flash it manually, I THINK (not sure if it needs to be repackaged for that to occur or not), but CWM will not install the OTA through the normal OTA process.
Click to expand...
Click to collapse
I was refering to step 7 on the Unlocker page you pointed to:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
So in short only replace the recovery as explained in pojnt 7 (and 8) of that page and then do a regular system update to ICS.
No need to unroot??
Will this keep my apps and settings? I do have Titanium so I can do a backup and restore that way.
Thanks a lot for helping!!
Steven_nl said:
I was refering to step 7 on the Unlocker page you pointed to:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
So in short only replace the recovery as explained in pojnt 7 (and 8) of that page and then do a regular system update to ICS.
No need to unroot??
Will this keep my apps and settings? I do have Titanium so I can do a backup and restore that way.
Thanks a lot for helping!!
Click to expand...
Click to collapse
Yes, your apps and data should remain intact, and that is correct, you only need to flash the recovery back to stock if you are already on a stock ROM. As of right now, only US and TW firmware versions are getting the OTA pushed to their device, but if you are not one of these you can manually flash to these stock ROMs via CWM if need be. But yes, if you are stock + root + CWM, you only need to flash over CWM back to stock. Root is fine to keep and all data will be saved (it is an official update, people would be irate if it wiped their data you know!)
Great stuff thanks again. I'n in Europe so I might need to wait for a bit but that is fine.
No problem. Ok guys, I've done a bunch of talking and answered quite a few PMs, and posted all my methods/experience with ICS so far, now, I'm going to go play for a while (it's 7am, and I've not been to bed, and I have to work at 4pm and my son will likely be up in an hour, so no sleep for me today, should have a well-rounded review by the time you see me again)
If you guys want to keep this thread alive, have at it! Turn it into a discussion.. See you guys in a while, can't wait to see what I miss while I'm gone
Well I did the update with root disabled with rootkeeper but now rootkeeper will not restore Root.
I guess I should of read thi before updating
Anyone in the same state?
dmazyn said:
Well I did the update with root disabled with rootkeeper but now rootkeeper will not restore Root.
I guess I should of read thi before updating
Anyone in the same state?
Click to expand...
Click to collapse
If you are SBK1 device you can flash CWM via NVFlash, use CWM to flash SU binary from ChainsDD (located HERE ) and then flash the stock recovery if you so choose to return to stock recovery (in case any patches or incremental updates come out you may need this if you want to stay stock ICS).
ONE MORE THING BEFORE I GO GUYS;
I just noticed that ICS brings a new recovery as well, so the update will overwrite your recovery, I assume it will do this if you figure out how to flash via CWM so be prepared for that. Any devs will want to work on removing the recovery blob from the patch file before releasing as a CWM flashable zip. My 2 cents. See you guys in a few hours/days, depending on how addicted I get to ICS.
Your dlpkgfile didn't work.. i need the WW version
Anyway I've rooted with nachoroot with stock asus recovery, waiting for ics update via FOTA
asder00 said:
Your dlpkgfile didn't work.. i need the WW version
Anyway I've rooted with nachoroot with stock asus recovery, waiting for ics update via FOTA
Click to expand...
Click to collapse
You need to reflash with a US version not WW.
Sent from my Sparkified TF101
Confirmed working! thanks. too bad i have to go straight to work
Dreamboxuser said:
You need to reflash with a US version not WW.
Sent from my Sparkified TF101
Click to expand...
Click to collapse
Ur right but i prefer to wait for ww
luna_c666 said:
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried.
Click to expand...
Click to collapse
After I updated to ICS, OTA Rootkeeper gave me the option to Restore root. Under the status section, Device rooted and Root permission granted were both unchecked until I used the Restore root option.
Hi, All -- I rooted my Google Play Edition Galaxy S4 using Chainfire's method, and it's now generating an error when it tries to install the OTA update to Android 4.3. I've unrooted the phone using SuperSU and have wiped it, but it still won't install the OTA.
Can anyone help?
Thanks, Alan
carrot34 said:
Hi, All -- I rooted my Google Play Edition Galaxy S4 using Chainfire's method, and it's now generating an error when it tries to install the OTA update to Android 4.3. I've unrooted the phone using SuperSU and have wiped it, but it still won't install the OTA.
Can anyone help?
Thanks, Alan
Click to expand...
Click to collapse
Have you re-locked the bootloader?
gee2012 said:
Have you re-locked the bootloader?
Click to expand...
Click to collapse
Ah. No, I haven't. I didn't realize that was necessary, and I'm searching now and not finding instructions on how to do that. Can you point me in the right direction?
Thank you!
Alan
carrot34 said:
Ah. No, I haven't. I didn't realize that was necessary, and I'm searching now and not finding instructions on how to do that. Can you point me in the right direction?
Thank you!
Alan
Click to expand...
Click to collapse
Look here for how to http://forum.xda-developers.com/showthread.php?t=2363025. For locking the BL type: fastboot oem lock.
carrot34 said:
Hi, All -- I rooted my Google Play Edition Galaxy S4 using Chainfire's method, and it's now generating an error when it tries to install the OTA update to Android 4.3. I've unrooted the phone using SuperSU and have wiped it, but it still won't install the OTA.
Can anyone help?
Thanks, Alan
Click to expand...
Click to collapse
If you rooted using CF-AutoRoot then it's likely your recovery was replaced. You need to flash the stock 4.2.2 recovery in all likelihood.
To be sure, what error does the screen show when you try to install the OTA. That will help us diagnose what isn't passing the OTA pre-check.
I have same issue here trying to update OTA update. Device rooted and bootloader unlocked.
When trying to install 4.3 OTA update, it rebooted into TWRP and start flashing but twrp mentioned some files not found and aborted, didn't even get a chance to look at the errors. After boot back up, it still show 4.2.2 and checking system update doesn't say new update found anymore.
tublah said:
If you rooted using CF-AutoRoot then it's likely your recovery was replaced. You need to flash the stock 4.2.2 recovery in all likelihood.
To be sure, what error does the screen show when you try to install the OTA. That will help us diagnose what isn't passing the OTA pre-check.
Click to expand...
Click to collapse
Thanks so much for helping with this. The screen just says "error." Is there any way I can get more information? And if flashing stock 4.2.2 recovery is what I need to do, how would I do it?
Thank you!
Alan
carrot34 said:
Thanks so much for helping with this. The screen just says "error." Is there any way I can get more information? And if flashing stock 4.2.2 recovery is what I need to do, how would I do it?
Thank you!
Alan
Click to expand...
Click to collapse
No problem. Go to this thread http://forum.xda-developers.com/showthread.php?p=43500355 and follow the steps, but try at first only doing the step that flashes recovery. Can you take a photo of your screen? What recovery are you using to flash the OTA?
tublah said:
No problem. Go to this thread and follow the steps, but try at first only doing the step that flashes recovery. Can you take a photo of your screen? What recovery are you using to flash the OTA?
Click to expand...
Click to collapse
Thanks, but there isn't any thread listed there. Could you try posting it again?
I can get a screen shot of the error message, but it will take a little while. All it says is "Error!"
Thanks, Alan
carrot34 said:
Thanks, but there isn't any thread listed there. Could you try posting it again?
I can get a screen shot of the error message, but it will take a little while. All it says is "Error!"
Thanks, Alan
Click to expand...
Click to collapse
I updated my previous post. If you really want fool-proof working 4.3, you can follow the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2388504 and just ODIN the full stock 4.2.2 and then try to apply the upgrade.
tublah said:
If you rooted using CF-AutoRoot then it's likely your recovery was replaced. You need to flash the stock 4.2.2 recovery in all likelihood.
Click to expand...
Click to collapse
This. I was stuck on this for a while. You first need to make sure you have stock recovery. I also had to reflash a new system IMG but the recovery was a big problem.
OK, I followed the instructions to re-lock my bootloader, which seems to have been done successfully, but I'm still facing the same error (as seen in the attached photo). So I guess I need to flash the stock recovery. I'm game to try the Heimdall approach or the ODIN approach that have already been suggested, but I wonder if there's a simpler way to do this. Based on what I read here, it sounds like I could just download stock recovery from here, and then just type these commands to flash it:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Does that approach make sense? And sound safe? Or would I be better off going down the ODIN or Heimdall roads?
Thank you all for your help in navigating this!
Alan
carrot34 said:
OK, I followed the instructions to re-lock my bootloader, which seems to have been done successfully, but I'm still facing the same error (as seen in the attached photo). So I guess I need to flash the stock recovery. I'm game to try the Heimdall approach or the ODIN approach that have already been suggested, but I wonder if there's a simpler way to do this. Based on what I read here, it sounds like I could just download stock recovery from here, and then just type these commands to flash it:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Does that approach make sense? And sound safe? Or would I be better off going down the ODIN or Heimdall roads?
Thank you all for your help in navigating this!
Alan
Click to expand...
Click to collapse
Its worth a try. Not sure but you might have to he unlocked to flash stuff.
Sent from my Nexus 10 using XDA Premium HD app
tublah said:
Its worth a try. Not sure but you might have to he unlocked to flash stuff.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
OK, that didn't work. I get a "Secure check failed" message.
tublah said:
No problem. Go to this thread http://forum.xda-developers.com/showthread.php?p=43500355 and follow the steps, but try at first only doing the step that flashes recovery. Can you take a photo of your screen? What recovery are you using to flash the OTA?
Click to expand...
Click to collapse
OK! Thank you all for the help. This Heimdall method fixed me up and let me install the 4.3 OTA without a problem. (The ADB commands I mentioned in the previous post not only didn't work, but left me with a phone that wouldn't boot!) Next step is to figure out how to re-root...
Alan
carrot34 said:
OK! Thank you all for the help. This Heimdall method fixed me up and let me install the 4.3 OTA without a problem. (The ADB commands I mentioned in the previous post not only didn't work, but left me with a phone that wouldn't boot!) Next step is to figure out how to re-root...
Alan
Click to expand...
Click to collapse
This is basically what I followed to re-root after 4.3. Worked fine. You're just booting to CWM recovery temporarily to install the SuperSU update. Then it will revert back to stock recovery.
ack154 said:
This is basically what I followed to re-root after 4.3. Worked fine. You're just booting to CWM recovery temporarily to install the SuperSU update. Then it will revert back to stock recovery.
Click to expand...
Click to collapse
Thanks! Can you share the instructions you followed to do that?
Alan
carrot34 said:
Thanks! Can you share the instructions you followed to do that?
Alan
Click to expand...
Click to collapse
Crap, forgot the link. Sorry. Here you go:
http://forum.xda-developers.com/showthread.php?t=2365555
ack154 said:
Crap, forgot the link. Sorry. Here you go:
http://forum.xda-developers.com/showthread.php?t=2365555
Click to expand...
Click to collapse
Awesome!!! That worked great and very easily. Thank you so much!