Related
I am putting together a quick guide on how to update your Stock ROM, Rooted, custom recovery T-Mo GSIII without having to wipe your phone.
You will need:
- Kies (If your phone has not prompted you to install the OTA yet, Kies will download and attempt to install it for you) (http://org.downloadcenter.samsung.c.../20120809103126135/Kies_2.3.2.12074_13_13.exe)
- ODIN 3.7 (http://forum.xda-developers.com/attachment.php?attachmentid=1270006&stc=1&d=1345396888)
- STOCK T-Mo GSIII recovery.img (I extracted this from the stock ODIN image for T-Mo) (http://forum.xda-developers.com/attachment.php?attachmentid=1269983&stc=1&d=1345396186)
- TWRP or CWM ODIN Flash-able recovery (CWM - http://forum.xda-developers.com/attachment.php?attachmentid=1269979&stc=1&d=1345396186 , TWRP - http://forum.xda-developers.com/attachment.php?attachmentid=1269980&stc=1&d=1345396186)
- Recovery flashable SuperSU root package (http://forum.xda-developers.com/attachment.php?attachmentid=1269984&stc=1&d=1345396186)
SO, place your phone in download mode (Vol Down + Home + Power), and via ODIN, flash the "Stock-Recovery-Image(Working T-Mobile T999).tar" image. ( This is putting the stock recovery back on your phone so the update can install).
When it reboots, either select yes to allow the OTA update to install (if your phone is already aware there is an update) on your phone, OR plug you phone into your PC and allow Kies to prompt you to update your firmware. Select yes and allow the OTA to install.
Once completed, your phone is updated without having to wipe, but you have lost root and customer recovery, so.....
Again, in Download mode, Flash either of the provided ODIN flash-able custom recoveries (TWRP, or CWM) I prefer TWRP
Once that is complete, you can reboot your phone into the new recovery (Vol UP + Home + Power)
Once in recovery, flash the SuperSU.zip package and Voila, all done, Triangle away and you in cool runnings.
Let me know if I need to clarify anything here. It makes sense to me, but then again, I fumbled through it to figure it out and extract the right recoveries and set permissions etc.....
Please hit the thanks button if this helped you in any way
Hans
Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:
Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Wildchld already released it.
http://forum.xda-developers.com/showthread.php?t=1838101
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
But with Wildchild's it's a complete ROM (650-700MB), correct? Are you not wiping when you flash his?
Actually I'm not 100% that you need to do a full wipe, but I'm guessing you probably should. Depends on what's different. You can always nabdroid and give it a shot. I will later if I have time.
Anyway, I was more responding to the post above mine about stock with root than to the op. Sorry if shoulda been a little more clear on that.
Sent from my SGH-T999 using xda app-developers app
i might wait. finally got google now and google wallet working and i dont want to mess it up lol
RotaryXperiment7 said:
i might wait. finally got google now and google wallet working and i dont want to mess it up lol
Click to expand...
Click to collapse
What did you have to modify to get them working? Like I said before, I made this little method so you did not have to wipe your phone to get the OTA installed.
The only thing I could see that would cause the OTA to break wallet, or Google now would be that if you have to modify pieces in the /system/ directory that would be overwritten. The only thing I had to do after updating was re-flash my little installer for international boot image, re-remove Carrier IQ as it was added back, and revert the googlesearch.apk to the earlier backed up version (functioning unified search) with titanium. Outside of that I run a pretty tight ship as far as system modifications go outside of root and root privileged programs.
had to edit build pro for wallet
Thanks op, this worked great for me! Updated and rooted again...
Sent from my rooted T-Mo SGS3
I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?
pappuhathi said:
I tried several times but couldent unroot my phone. I even tried through the root kit by mskip. I think the problem may be that I got my phone unlocked, not using an unlock code but some other method (all I know about this method is that my phone says"restricted access" for a few seconds upon restarting.)
Any suggestions on how to unroot? Also, if I unroot, will I loose the unlock?
Click to expand...
Click to collapse
I think the best method to unroot your phone will be to ODIN it back to the stock T-Mobile image. (Overwrites EVERYTHING, probably your unlock as well).
http://forum.xda-developers.com/showthread.php?t=1737855
Above is the link to the stock image.
Apologies, in general, but I feel you may have the wrong thread if your looking to unroot your phone. That is off topic on what is being discussed here.
has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.
arts711 said:
has anyone tried this and kept google wallet and google now working? Any troubles?
I'm wanting to update but I'm rooted withthose two apps finally up and running.
Click to expand...
Click to collapse
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?
cybrnook said:
I would assume the build.prop file will be overwritten. So its possible you would need to modify after updating. May not be any way around it.
If you want to test for others, make nandroid backup , upgrade and test. If it works, update us. If not, update us
Click to expand...
Click to collapse
You are correct about build.prop being overwritten.
Sent from my rooted T-Mo SGS3.
If I've helped you, be sure to use the thanks button!
arts711 said:
So (in case this all doesn't work out) to restore via nandroid, just root and apply right?
Click to expand...
Click to collapse
Well if it doesn't work (Which I think it won't), you don't need to worry about restoring root. You just need to flash a custom recovery to revert your nandroid backup. Your root and customization will come back with that.
But with some of the added features that come with the update, I would say don't look back. Upgrade to the latest, then reapply your customization to get wallet and all working again.
IF you have to revert your nandroid back, make sure to do a factory wipe before you revert to your backup.
thanks! i'll give it a shot this weekend once i get more time.
I've used two different versions of Odin and two different T-Mobile stock recoveries (other one is here), and I can't get stock recovery to replace CWM on my GS3. Odin reports that the flash is successful, but when it reboots, ROM Manager still shows me as having latest CWM Touch, and the T-Mo update fails. I'm attempting the update via Kies right now, but I anticipate failure due to CWM still being installed as recovery.
-- I have Cerberus anti-theft installed, but I don't see anything about protecting recovery.
-- I have Busybox installed, but that shouldn't affect recovery.
Any ideas?
EDIT: Interestingly enough, where the OTA update failed, the Kies update went smooth as silk. Now to re-root and remove bloatware!
RaymondPJR said:
Nice instructions, but I'm going to wait a few days. I'm want to see if the dev that did the flash and root without tripping the flash counter will do the same for the new firmware. I'm still not too keen on custom recoveries yet even though I backed up my IMEI, so I just want to be rooted. If not, I'll use your guide.:good:
Click to expand...
Click to collapse
Are you referring to MrRobinson's rooting method? I'm waiting for it too.
Sent from my SGH-T999 using XDA Premium App
Im unable to update. I used Odin to flash the stock recovery, then downloaded the update via settings-> about device-> software update. Installing reboots the phone but then fails and reverts to current state. I can't update through kies also bc it just says "connecting", no errors. I tried uninstalling/reinstalling drivers but kies never completes connecting. Any help?
Sent from my SGH-T999 using xda app-developers app
EDIT: I uninstalled all my samsung drivers and Kies from "Programs and Features" in win7, deleted Samsung folders from HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER. Reinstalled Kies and connected my phone to install the drivers. Kies was stuck in the connecting loop still, so I unmounted my sd card, turned on USB debugging and Kies finally connected and asked to upgrade. Upgrading at this moment.
Hello all,
Sorry if this question has an obvious answer. But I am trying to make sure that I don't lose S-Off before applying the 4.3 update for the HTC One. Since I know as of this post that rumrunner does not work on 4.3 builds yet and so I would really rather not be in that kind of situation.
I want to apply the OTA to make sure I get all the stock radio/binary/fimrware updates installed before I flash a custom 4.4.2 ROM. Since last time I tried that, I was unable to get any kind of data connection and was only able to use Wi-Fi. I want to make sure I have all the needed radios before I apply KitKat again.
So the question being, does applying any OTA break S-off? I am in a strange state with my HTC one right now where I am having a difficult time getting to the bootloader. I will try again when I get home by using adb but right now it's not working.
Thanks ahead of time.
It should not break S-off. To the best of my knowledge only relocking it yourself is about the only way to reset a phone to S-on.
Sent from my HTC6500LVW using xda app-developers app
merlin66676 said:
It should not break S-off. To the best of my knowledge only relocking it yourself is about the only way to reset a phone to S-on.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
So I would just need to apply the update, then re-unlock the bootloader since it's already s-off. After that, flash custom recovery and flash KitKat and be on my way?
You could just get the firmware from here http://forum.xda-developers.com/showthread.php?t=2485319 in post #2. Then you would not have to worry about losing anything.
mercer24 said:
You could just get the firmware from here http://forum.xda-developers.com/showthread.php?t=2485319 in post #2. Then you would not have to worry about losing anything.
Click to expand...
Click to collapse
I tried that and I was still not getting data on just the radio. So I tried the other zip and I just ended up in a bad state. I think I might have grabbed the wrong version potentially. I'll try again later at home.
ppd0526 said:
Hello all,
Sorry if this question has an obvious answer. But I am trying to make sure that I don't lose S-Off before applying the 4.3 update for the HTC One. Since I know as of this post that rumrunner does not work on 4.3 builds yet and so I would really rather not be in that kind of situation.
I want to apply the OTA to make sure I get all the stock radio/binary/fimrware updates installed before I flash a custom 4.4.2 ROM. Since last time I tried that, I was unable to get any kind of data connection and was only able to use Wi-Fi. I want to make sure I have all the needed radios before I apply KitKat again.
So the question being, does applying any OTA break S-off? I am in a strange state with my HTC one right now where I am having a difficult time getting to the bootloader. I will try again when I get home by using adb but right now it's not working.
Thanks ahead of time.
Click to expand...
Click to collapse
If you are already s-off with an unlocked bootloader you can take the OTA and not lose either. You'll just have to flash TWRP or CWM in fastboot and then the su binary in recovery to get root again.
ppd0526 said:
I tried that and I was still not getting data on just the radio. So I tried the other zip and I just ended up in a bad state. I think I might have grabbed the wrong version potentially. I'll try again later at home.
Click to expand...
Click to collapse
The hosed data thing is fixed with a factory reset from the stock recovery.
Sent from my Nexus 7 using Tapatalk 4
I was able to resolve this issue.
For anyone looking at this in the future or having the same issue:
I was able to get bootloader to properly load after holding the power button + vol down for a while. My lights started blinking (home and back) but I just kept holding the buttons. Eventually it finally loaded the bootloader.
Went into fastboot from bootloader and then flashed twrp recovery. Grabbed the firmware zip from the post where all the stock files are available and flashed that properly using the steps in the post (http://forum.xda-developers.com/showthread.php?t=2485319).
Once I flashed that, I went back into recovery, did a clean wipe on everything but sd-card/internal data.
Flashed my new rom after that (twrp requires a reboot after a wipe to properly flash for KitKat at this time).
Everything was smooth sailing after that and I have 4G data now thanks to the new radios/firmware.
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
You need a custom recovery (TWRP or CWM).
bkeaver said:
is there away to install SuperSU when you have stock recovery? I'm thinking that we have to have either CWM/TWRP to install the zip. or am I having a brain fart on this.....
Thanks for whomever can clear my cobwebs..
Click to expand...
Click to collapse
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
uronfire said:
You can install it if you have the bootloader unlocked.
Use boot command instead of flash to boot into custom recovery and install su.
e.g
Fastboot boot twrp.img
Click to expand...
Click to collapse
Thanks this worked :good:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
bkeaver said:
so when I go into recovery now I get a image of a htc one with a red triangle and exclamation mark inside of it?? since I have never went into recovery on this phone before isn't it supposed to look like any other stock recovery??? and if this isn't right I have tried flashing the recovery already and still get the same result... can someone expand on this for me pls
Click to expand...
Click to collapse
You have stock recovery.
BenPope said:
You have stock recovery.
Click to expand...
Click to collapse
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
bkeaver said:
so it doesn't give you flash update and wipe and all that anymore.. sorry like I said I have never went into recovery on this phone.. just making sure...
Click to expand...
Click to collapse
I think you have to hold volume up and hit power or something.
ok I am good.. thank you... I'm putting everything back to stock because someone bought my phone and I just want to make sure everything is correct on it now.. thanks!!
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
and btw thanks everyone for the help. I hit my thanks button but on my browser it it isn't showing it just to let you know....
bkeaver said:
i sold the phone and this is what they requested. I know the OTA wont work and I never keep stock recoveries on my phones but.... I guess they will find out for themselves
Click to expand...
Click to collapse
Sounds like somebody that is a bit ill-informed. They want root, but they probably also want OTA (the 2 don't go together, IMO) and heard that you need stock recovery for OTA. I suppose they can change everything back that they modified with root, and unroot or hide root to install the OTA. But it just seems they are making life more complicated than it needs to be.
Also sounds like its a person that wants root, but not willing to do it themselves. But I suppose that's not really your problem!
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Mr Hofs said:
Option to root and have ota is very easy :
Stock rom (unmodified but rooted)
Stock recovery
And you can ota. The ota will probably delete superuser but that's about it. The ota will not fail because its rooted as long as the stock rom/apps are unmodified
Click to expand...
Click to collapse
yeah this is what I did for them so who knows.. I've never tried it that way but i guess it would work like that
redpoint73 said:
Yes, this.
However, why bother keeping stock recovery at all? Stock recovery is effectively neutered once rooted, as you can no longer install an OTA.
Click to expand...
Click to collapse
Rooting doesn't affect ota's, at least not in my experience.
ashyx said:
Rooting doesn't affect ota's, at least not in my experience.
Click to expand...
Click to collapse
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
redpoint73 said:
Only if absolutely nothing was changed with the stock ROM.
Its more my point there is little point to installing OTAs on a rooted device.
Click to expand...
Click to collapse
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
ashyx said:
I don't understand that statement. I still run stock sense, but with a few additions that don't affect ota's. So I still get updates while having things configured the way I want. I can also run things that require root such as titanium backup and a few others.
Click to expand...
Click to collapse
Because once you accept an OTA, you will be unrooted. You will have to root again, either by installing custom recovery (than back to stock recovery so you can OTA) or the trick of booting custom recovery via adb to flash SU (as described here). Its just a lot of jumping through hoops with little added value.
On the other hand, if you have custom recovery installed, you can flash any of the array of stock rooted or awesome custom ROMs posted here. This includes stock rooted ROMs taken from OTA updates from lots of versions (often posted within days of the OTA starting to roll out), not just your carrier, so you can possibly get an update much faster than waiting for the OTA to roll out from your carrier (although that depends on what carrier version you have). You also don't have to constantly be worried "well, if I change this I won't get OTAs". You can do whatever the heck you want, and isn't that really the whole point of root?
Its just my opinion. And a lot of this may stem from the fact that I'm on AT&T, who are not only agonizingly slow about rolling out OTAs (sometimes 3-4 months or even later than other carriers on my past HTC device) and have even went to the effort to close exploits and prevent unlocking of bootloaders when rolling out new OTAs (on the One X EVITA). In fact there was even a bug (I assume it was a bug - others may accuse that it was intentional) where installing the Jellybean OTA with SuperCID and S-on bricked the phone.
As I said, its just an opinion. But there are many others on XDA that will agree that OTAs have no place on rooted Android devices.
And to be fair, I did cover myself and stated "there is little point" instead of "there is no point"
The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?
Lanthanide said:
The OTA 4.4.3 update is now available for my phone, but I've rooted it, and I've read the horror stories so I'm not going to blunder blindly into this
My rooting experience went a little poorly - I thought I was doing the right thing by backing everything up on the phone first, using Helium. Unfortunately Helium simply did the backup onto the internal storage itself, so it all got wiped during the process anyway.
Anyway, I got over that, but now I want to install the OTA 4.4.3 update. So here's the things I've done which I think are relevant:
1. Installed TWRP recovery, as required for rooting
2. Have flashed the SuperSU program for root
3. AFAIK I'm still on "stock" - I haven't gone out to find any special roms etc
4. Had to reinstall the calc and flashlight apps as they were missing after the whole exercise (so many I'm not on stock, or they would be there?)
5. I have installed Xposed Framework and the Sense 6 tweaks and GravityBox apps.
6. I tried to uninstall some system apps (Facebook, Twitter, things I don't use) with a root uninstaller program, but every time the phone reboots they re-appear, so I think I need s-off to do that properly?
7. I've 'Disabled' the weibo app through the standard app info button
I understand I have to go back to the "stock recovery" in order to do the OTA update, but is there anything else in the above list that I need to do anything about?
Will going back to the stock recovery mean I lose all of the content on my device again, and have to restore it from a backup? If I use the HTC backup app to back up all my phone data on the rooted 4.4.2 I'm running, can this then be restored onto the 4.4.3 version?
Also is the problem I mention in #6 solved by going s-off?
Click to expand...
Click to collapse
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).
bruce7373 said:
I thought it didn't matter if you were s/off or not, so long as recovery and OS were stock and CID matched (or were SuperCID).
Click to expand...
Click to collapse
It doesn't matter in general. But it matters in case that you used S-Off to uninstall system APPs Thus an OTA wouldn't succeed.
That's what I wanted to say in my post above
Sent from my HTC One_M8 using XDA Free mobile app
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.
Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
Click to expand...
Click to collapse
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.
HTCNerdYoda said:
I would revert to stock recovery and get me this OTA. And you need a 2.22.xxx FW for some of the custom ROMs currently available.
It's the fastest way to update your firmware anyway
Alternatively you could try to perform an S-Off using SunShine and paying 25$ for it, as I did to flash the newest FW.
Click to expand...
Click to collapse
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
is the s-off really worth it?
Yuskow said:
Got my cid as bm 001
so i got the nandroid backup here http://forum.xda-developers.com/showthread.php?t=2701376
now i just do a restore under twrp?
Click to expand...
Click to collapse
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Yuskow said:
is the s-off really worth it?
Click to expand...
Click to collapse
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).
Yuskow said:
Wow found my answer already. Just to confirm. I'm in the same situation. Rooted. Installed twrp and su. Went to s-off with firewater but got the whelp message.
Got the OTA update in this morning. Tried installing it, went to my recovery so I tried to install it. It failed of course. Phone is still ok.
I'm just making sure I'll do this ok. Gotta go back to original recovery then install it or am I just better off going to a custom rom?
On my vivid, I used paranoid when it was available, used pacman for a bit. Also used the CyanogenMod. I know recommendation shouldn't be made but i know on my vivid there were lots of issues since there wasn't a specific team rolling out the roms but someone porting them from the specific team. Is there a team dedicated to this phone? If so are their roms leaps ahead of the ones ported over? Just looking at the downloads you can tell which one is the most popular, that doesn't always mean they are the best.
Thanks for any advice.
Click to expand...
Click to collapse
I had the Vivid as well and ended up with a 4.4.2 ROM which seemed to be the most current that was available at the time, but can't remember the name or the dev.
As for the M8, I've been on ARHD almost exclusively and think it's one of the best ROMs out there. I've tried Viper, MaximusHD, Renovate also, but always come back to ARHD.
http://forum.xda-developers.com/showthread.php?t=2694917
---------- Post added at 07:40 AM ---------- Previous post was at 07:33 AM ----------
HTCNerdYoda said:
As long as the ROM you are using is stock and you only routetd, you just need to flash stock recovery for the OTA to succeed.
Well from my point of view: yes it is. Needed S-Off to debrand my One M8 and change CID to a WWE one. Well and additionally you can do a lot more if the security flag is on off (never without propper reading before doing it of course).
Click to expand...
Click to collapse
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?
bruce7373 said:
I have the WWE edition and am currently with ATT. I'm considering their new update mainly to see if the new firmware/radio will give me better LTE speeds. The fw is 2.23 based. Will that be a problem if or when I return to ARHD which is on 2.22?
Click to expand...
Click to collapse
That's a really good question. Regarding ViperOne I could tell that running 1.8.0 (which was on 1.54.xx base) with 2.22.xxx FW worked flawlessly. So I would guess this should work just fine.
At least it's worth a try. Maybe better ask in the ROM thread.
Used arhd on my vivid for a bit. Must say it was an ok rom but lots of issues in general with all new roms on the vivid. Hardware too outdated. Maybe I'll give it a shot. Really leaning to a de-senced one.
HTCNerdYoda said:
Flashing back stock recovery you won't loose anything. This just happens during the unlock process if done with HTCDev.
Good that you are not S-Off and FB, Twitter and so on are still installed, as otherwise you wouldn't be abled to perform the OTA. An OTA is only going to run if the whole system is unchanged.
Only thing that's quite likely going to happen, is that you root is lost after the OTA. Tthus you would have to flash TWRP and the SuperSu again, after the OTA.
Click to expand...
Click to collapse
Ok, that's encouraging.
My CID is HTC__621 although I don't think I need that for just flashing back to stock recovery. My version is 1.54.709.12, so I downloaded the matching recovery from here http://forum.xda-developers.com/showthread.php?t=2701376 and flashed it. I confirmed that the stock recovery was installed by booting to it and getting the red triangle etc.
Then I downloaded the OTA upgrade and told it to install. I didn't watch the installation progress, but eventually it went to the red triangle screen and finally rebooted. But I'm still on 1.54.709.12, so I take that to mean the OTA failed. When I go to system update, it checks and finds one available and offers to download it again, which I haven't done.
I'm wondering if 'disabling' the weibo program could have caused the update to fail? Or possibly I *did* actually uninstall a stock program or two that I mentioned at #6 and that's what's preventing the update?
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?
Lanthanide said:
Ok, that's encouraging.
Anyway, I made a complete nandroid backup on the external SD card before I flashed the recovery. It seems like the easiest approach now would be to flash a stock ROM for HTC__621 then do the OTA upgrade. After that, I could restore my HTC sync (the app) backup from the cloud, but if I wasn't happy with that I could recover the data portion of my nandroid backup?
Click to expand...
Click to collapse
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.
HTCNerdYoda said:
In fact you are right. The OTA fails as something on the system has been changed that's critical to the OTA.
So I would back up the data on the phone I need, download a stock nandroid backup for your CID, install with twrp, re-flash stock recovery and perform the OTA again.
Click to expand...
Click to collapse
Ok, so I put on a stock nadroid backup for HTC__621, changed to stock recovery, but the OTA update is still failing at around the 30% mark.
Actually I've just noticed that the stock ROM I put on doesn't have the calc or flashlight apps, but when I originally bought the phone they were on there. I had subsequently installed them using the apps on this thread here: http://forum.xda-developers.com/showthread.php?t=2699906
But maybe that is what is preventing me from doing the OTA now?
Edit: Right, so doing some more reading, it seems that HTC included these 'stock' apps in the /data directory instead of /system, so when doing the HTCDev install, they get wiped. But there was a note in that thread saying that for the One M7, they would actually do a hash of those apps too and if they weren't there the update would fail.
Someone linked to this thread http://forum.xda-developers.com/showthread.php?t=2703759 which says the APKs in the first one were from the M7, and these are from M8, and it also included another one called Seven Digital (yet another bloatware app I don't care about, hence why I didn't notice it was gone). Anyway I installed those 3 apps, but the OTA update still fails at around the 30% mark. I notice that the thread says preload APKs for 1.54.401.5, but my phone is running 1.54.709.12, so if they really are doing hashing for all of these apps, the update might be expectly a slightly different version and therefore fail the hash check?
Resolved!
Right, posting as new post because I solved it!
I searched through the collection thread and luckily found someone else who has HTC__621 who wanted to do the 4.4.3 upgrade as well. ckpv5 stepped in to lend a hand with this post: http://forum.xda-developers.com/showpost.php?p=54598052&postcount=1514
The TWRP stock ROM he posted there includes the flashlight and calculator app, as well as another one that looks like it was missing - WeChat. So now the OTA update has applied as expected. :highfive
I'll suggest Mr Hofs remove the existing nandroid backup for HTC__621 that he has there because it isn't complete.
Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Edit: More findings. In installing Xposed Framework on my phone, it can't do the 'classical' install because of S-on, instead it flashes it through recovery. So I suspect this could have been preventing the OTA update as well.
Lanthanide said:
Weirdly after all that was done, now that I have 4.4.3, the calc and flashlight apps are again missing; no sign of WeChat either. So I'll probably have to go through this whole performance again next time I want to OTA update?
Click to expand...
Click to collapse
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.
ckpv5 said:
Because you relocked bootloader when you did the OTA update. So those files were deleted when you re-unlocked bootloader after OTA done.
There's a TWRP backup for the latest here : http://forum.xda-developers.com/showpost.php?p=55097943&postcount=1744
Just a note : there is no need to relock bootloader to do OTA update.
Click to expand...
Click to collapse
Ok, at least there's an explanation for what happened, but I didn't at any point explicitly lock the bootloader. All I did was:
1. Flash TWRP recovery
2. Flash the ROM you provided
3. Boot the phone, going through the setup stuff to configure wifi etc
4. Booted to fastboot and flashed to stock recovery
5. Rebooted phone, downloaded and installed OTA update
6. Booted to fastboot and re-flashed TWRP, ran nandroid backup and then installed superSU when offered
At what point would the locking of the bootloader have occurred?
Lanthanide said:
At what point would the locking of the bootloader have occurred?
Click to expand...
Click to collapse
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA
ckpv5 said:
Re-unlocking bootloader is one scenario that may happen that remove the preload folder.
Restoring an old backup which doesn't have the preload folder is another scenario.
Anyway that is easily can be fix by pushing the preload folder from OTA zip to /data
then make a new backup for future OTA
Click to expand...
Click to collapse
Ok, well like I said, I didn't explicitly choose the lock the bootloader at any point, and the nandroid backup that you created *did* have the extra apps in there (I confirmed their presence at step 3 in my sequence).
Note that I'm not trying to be argumentative, just explaining my experience in case this might help others in the future.
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G
I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512
OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..