Related
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
2.3.3 was all the rage about a month or so ago.
Sent from my LG-P999 using xda premium
Well, sure, but all news says that T-mobile stopped doing OTAs some time ago (started late July, stopped August 10). So why on earth is my phone just getting it now? I even do a manual check every so often and never got it. I didn't do anything special today that I can recall.
you should update it. you dont have nothing to lose. ifd your still rooted it will unroot but then you can flash nvflash recovery and go back to any rooted roms you want
epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
No idea why you're just getting it now, but its the same one thats been out for a while now.
hmichaelkim said:
No idea why you're just getting it now, but its the same one thats been out for a while now.
Click to expand...
Click to collapse
T-Mobile removed the 2.3.3 update from their servers long ago. If you are getting something else it is new most likely. You can do an OTA if you are rooted as long as you have not modified any system files other than adding su and superuser.apk to get root..
epithumia said:
I've a rooted G2X that's still running 2.2. Just over an hour ago I got a "T-Mobile Update Service." notification. Surprisingly there's no talk of a fresh OTA here so I'm not really sure what's going on. Not that an OTA would work for me since I'm rooted, but I guess it's going to keep bugging me until I do something about it.
Click to expand...
Click to collapse
So what was the update?
Sent from my HTC Desire using XDA App
What happens?
Sent from my LG-P999 using XDA Premium App
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
I'm on froyo to and rooted but no clockwork mod recovery. I tried to check for an update and it said some kind of error i dont remember.
epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Check in the /cache directory for the zip file for tthe update. If you can, before you install it can you save a copy of the zip to a separate area on your sdcard and thn upload it to a file sharing site so others can download it? Once you install it, it gets deleted from the /cache directory but if you save it elsewhere those copies will be saved.
epithumia said:
Well, I let it update but of course it just booted into CWM instead of doing anything. I'm guessing I'd have to flash back to stock in order to apply any OTA. If someone tells me what to search for I can run logcat and see what it downloaded, but I didn't see anything obvious when I looked (and there's a lot of stuff in there).
Click to expand...
Click to collapse
Yes, you need to be on stock recovery and your phone's system partition must be stock. LG stores some OTAs very differently than other vendors.
Do a backup of your phone first to preserve the OTA image. It might be in the cache but it might be elsewhere. If you wouldn't mind giving me a link to the system and cache images I can try to find the OTA and see what it is for.
I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.
Lenin809 said:
I just got the 2.3.3 ota update about 2 weeks ago which i thought was real late also. I used to check for the update and i would always get an error too. i was rooted in stock froyo for tmobiles g2x (LG P999DW). I didnt have to re-root the phone and last night i just flashed clockworkmod recovery and flashed the 1.55ghz overclocking kernel on to the 2.3.3 that i got from the ota update.
Click to expand...
Click to collapse
Did you flash roms and then restore an old backup? That backup could have had the OTA on it and you did not notice it before. T-Mobile pulled the OTA months ago (was available less than two weeks). Doesn't seem likely it was pushed to you recently.
Hi all,
I'm a bit noobish at all of this so please bear with me.
I have a t-mobile us HTC sensation and I followed the guide to S-off, installed CWM, and then rooted the phone. I never flashed a new ROM.
This morning the OTA update popped up and having a "blond moment", I clicked update.
Now my phone is showing a little green droid holding an exclamation mark in a triangle and I don't know what to do!
Any help is really appreciated. I am really freaking out right now... it's been like this for 20 mins.
Thanks,
Lys.
try flashing a new rom.. maybe u should try flashing android revolution hd rom... working good for me till now... read the instruction carefully when flashing new rom.... gd luck...
Thanks for the fast reply.
How do I get off this screen that I'm hung on?
-Lys
Take battery out
Then turn on the phone holdin volume down.
See if you can get in to bootloader screen, then select recovery.
If you can get this far, your far from bricked.
Just install a new rom. Do a data wipe, and flash away.
Yay!
I got to recovery.
Thank you for you help. You're awesome!
-Lys
All that happened is that you were denied the OTA since you are rooted. It happened to everyone back when 2.3.4 came out. If you want the OTA instead of a custom ROM then you can run the RUU for your phone and then accept the OTA.
Matt
mrg02d said:
If you want the OTA instead of a custom ROM then you can run the RUU for your phone and then accept the OTA.
Click to expand...
Click to collapse
What does RUU mean and where can I get it?
-Lys
Lysiana said:
What does RUU mean and where can I get it?
-Lys
Click to expand...
Click to collapse
http://www.filefactory.com/f/c87a2330449af512/
Search for instal HTC RUU. It's really quite simple!
Okay first off, i know this is the wrong section. I can not post in development because I am new here, but I am in need of help desperately. Okay so I am rooted on 1.85 and the bootloader is NOT unlocked. Well i decided today to take the update to 4.0.4 before I did research. (Stupid me eh?) Well I start the OTA and then do some research. I learn that the update to 4.0.4 might be harmful to rooted users. So I disconnect from WiFi knowing it will pause the download. Well now I have a download that is just paused in the notification bar, and any time i connect to wifi it will continue the download. While the download is paused, can i unroot and take the update safely? I have seriously been searching for hours on end to find someone with a situation that I am in and i can not.
If you do a factory reset the update will go away. But that would also make you loose root. You should unlock the bootloader, then flash the rooted 2.20 update from the dev section.
Sent from my HTC One XL using xda app-developers app
Yep, get that bootloader unlocked immediately and flash a rooted stock ROM or a custom ROM. Make sure you backup all your stuff with Titanium because the bootloader unlock will wipe your phone.
Also, just so you know, this thread most definitely did NOT belong in development, which is reserved for ROMs and kernels and root guides and the like ONLY. Threads like this belong in Q+A but nobody is gonna kill you for posting it in General.
After the download, you should get a prompt to either Install, Postpone, or you can press the "back" capacitive button to cancel. Cancel should stop the update notifications. At least this is how its worked on past HTC OTAs. I personally can't verify, as I haven't gotten the notification yet. But others seem to verify this: http://forum.xda-developers.com/showthread.php?t=1817429
But if you want to be safe, you should SuperCID and unlock bootloader first, as others have suggested. Pressing the wrong button for the method I suggested above will be catastrophic otherwise (lose the ability to root and unlock BL).
Thanks for your help guys!
I just did a factory data reset on my phone. Honestly, I've gotten myself into trouble with rooting. I really need to read up before i continue with things of this sort. So since i did a factory data reset, am i 100% unrooted? Will i be safe to take the OTA now? Thanks for your help guys!
If you were stock 1.85, and rooted using the one-click or "manual" method (which you must be, if you you are still BL locked), then you are now unrooted. You are either rooted or not, there is no "percentage" of rooted.
What kind of trouble have you gotten into rooting, and what do you typically use root for?
I've been debating on whether or not to just go ahead and install the OTA to 2.2. The only thing I've used for root was for WiFi-Tether and I don't even use that anymore so I think I don't even necessarily NEED root anymore. I'm just tired of the updater telling me there's a new update to install - frankly very annoying. I've been just using the back capacitive button to cancel it. BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
extol1337 said:
BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
Click to expand...
Click to collapse
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
redpoint73 said:
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
Click to expand...
Click to collapse
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
extol1337 said:
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
Click to expand...
Click to collapse
Is the update actually downloaded to your phone? You may need to locate and delete it.
It may be trying to install the OTA from recovery, which makes sense. Don't actually know what happens when an OTA installs.
I've never installed an OTA! I'm always rooted, always will be!!!!
Just to be sure.
I did a factory data reset the night of the problem, been good ever since! I have not done anything to the phone except install a few apps. Should i be okay to take the OTA now? Sorry i just really want to be sure. This is my 3rd phone is 3 months so... no second chances.
SOLVED
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Did everyone got an update ?
I still do not see update notification
From beast called HTC One X
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
wantabe said:
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
Click to expand...
Click to collapse
Excellent info!
ssteven232 said:
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Click to expand...
Click to collapse
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
borets.boris said:
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced). One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone! My quadrant went up 800 points and battery life is still ridiculously good! I also have to agree with "I can't own an android without root access" especially on AT&T. Personally I'm good to go until the Jelly Bean update! Decisions, decisions! :laugh:
wantabe said:
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced).
Click to expand...
Click to collapse
I've never installed an OTA, so I wouldn't know either. Honestly, I don't know why one would do that, when the awesome devs here post ROMs with the latest OTAs and root prebaked into them. There are "modded" ROMs and "stock" (or close to stock) ROMs available to everyone's taste.
wantabe said:
One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone!
Click to expand...
Click to collapse
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
wantabe said:
My quadrant went up 800 points and battery life is still ridiculously good!
Click to expand...
Click to collapse
Where was your improvement? Did the increase happen in the aspect/area that directly affects your daily use, or in some esoteric algorithm that the phone all of a sudden processes faster? I used to go crazy on quadrant scores, but now I don't really understand their value/accuracy. As long as the phone feels buttery smooth while lasting 5+ hours of screen time, I'm happy!
Since you're interested in the scores, I installed quadrant and ran it, so you can compare.
Sent from my HTC One X using xda app-developers app
in admiration, totally confused!
borets.boris said:
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
Click to expand...
Click to collapse
Hi, do you think you could point me in the right direction for this? I found the general thread on radios, but am at a total loss about what it means or what to do with it!
You knew this was the wrong section but posted here anyway? Not a good way to start your membership on XDA. First rule of thumb is to search before creating a thread. Google is a great source for information. For future reference, all questions belong in the Q&A section, where coincidentally, this is being moved to.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.
I have a rooted, unlocked SG3 running stock ROM and as of a couple weeks ago, continue to get prompted to install the OTA update (VRAGL7 I believe). Unsurprisingly the install fails when I try to apply it.
My question is, do I have to restore in order to apply this update? And if so, is it possible to instead defer the update indefinitely (since I dont want to restore and there doesnt appear to be anything useful in this update according to their site).
Im also sure someone else must have asked this before, but after browsing the last few pages and searching, I couldnt find anything. Feel free to direct me to a previous response if I missed it.
Thanks in advance!
This has been covered numerous times, but, here you go. If you want to take the update, lock your bootloader, Odin back to stock, take the OTA update, reroot, unlock, etc.
If you don't want to do that, freeze SDM 1.0 with Titanium and the message will stop. One thing though, you will not be able to update OTA until you restore SDM. Which, you shouldn't be updating a rooted phone to begin with unless you want a world of problems.
Good luck!
Sent from my SCH-I535 using xda premium
So to be clear, absolutely no way to apply the update without going back to stock first, correct?
Sorry for posting up whats probably been asked 100 times, but really couldnt track it down with a search and browse of the last few pages.
Thanks again.
timofcourse said:
So to be clear, absolutely no way to apply the update without going back to stock first, correct?
Sorry for posting up whats probably been asked 100 times, but really couldnt track it down with a search and browse of the last few pages.
Thanks again.
Click to expand...
Click to collapse
I did not have to do all that...
I used Mobile Odin Pro to Pre-Inject Root into the OTA Update before flashing it, then I flashed the latest modem immediately after flashing the OTA update.
I didn't lose Root or Unlocked Bootloader status..
Best part of it was... I didn't need my PC to do any of it...
The following thread is the one you should read in detail..
http://forum.xda-developers.com/showthread.php?t=1887741
Perfect. Exactly what I was looking for.
Thanks again.
timofcourse said:
Perfect. Exactly what I was looking for.
Thanks again.
Click to expand...
Click to collapse
Glad to help..
tekrhino said:
I did not have to do all that...
I used Mobile Odin Pro to Pre-Inject Root into the OTA Update before flashing it, then I flashed the latest modem immediately after flashing the OTA update.
I didn't lose Root or Unlocked Bootloader status..
Best part of it was... I didn't need my PC to do any of it...
The following thread is the one you should read in detail..
http://forum.xda-developers.com/showthread.php?t=1887741
Click to expand...
Click to collapse
Make sure that you read it and pay attention very carefully. I tried to do the same exact thing and had problems. Had to Odin back to stock. I think my problem was that I was running a custom kernel. Anyway I got the unauthorized software message and could only get into stock recovery and download mode.
Guess I will read the thread myself and see where I screwed up at.
Sent from my SCH-I535 using xda premium
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
vax1170 said:
I am just curious ... why would you want to update to the OTA 4.3 and forever lock down the bootloader? Once the verizon 4.3 update takes hold, you might be able to root, but (so far) will not be able to load custom roms without bricking the device.
Click to expand...
Click to collapse
Well your almost right. First off you for sure can root. Second you can install custom roms with safestrap. Its limited to tw roms atm. There have been a hand full of people who upgraded just to use safestrap. I wouldnt recomend it right now because its alittle buggy.
RedBullet said:
So, my phone is running 4.1.2 rooted, and it got an OTA recently. The OTA failed because the bootloader was unlocked.
I thought easy-peasy, just odin flash the locked boot loader and download/apply OTA again, right?
Flashed fine, locked and clean for initial boot. But when it went to install the OTA, same problem happened, the bootloader was miraculously unlocked again, and the OTA failed.
Any ideas on how I can get past this? I really don't mind loosing root, just trying to avoid a complete odin reflash and loosing everything...
Click to expand...
Click to collapse
Wife's phone. She doesn't want to mess with it.
I think I figured it out, looks like I had a custom recovery installed. Flashed that to stock and locked bootloader and all is fine now. Running latest and greatest. Just what the missus is looking for...
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
ThePagel - Thanks. One one of my phones was cursed with an accidental OTA 4.3 upgrade. Nice to know something is in the works, I'll dig up that thread and watch it.
vax1170 said:
RedBullet - Ah, I fully understand now I'm having a similar conversation with my misses.
Click to expand...
Click to collapse
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
RedBullet said:
I assume if one wants to go the custom ROM route they would simply need to odin flash one of the older stock images and go from there. Doesn't seem like a big problem. Of course > 50% chance I have no idea what I'm talking about...
Click to expand...
Click to collapse
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
landshark68 said:
If you take the 4.3 OTA, you cannot odin flash an older stock image. Will brick your device.
Click to expand...
Click to collapse
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
It sure is sad but true. Im thankful google blessed us with the nexus 5
RedBullet said:
Really? That is pretty tragic. I may only buy unlocked devices from here on out; they seem to be getting better and better at making their devices less and less useful...
Click to expand...
Click to collapse