Hello all,
I have a Thunderbolt, had a friend perform the root (here) a few months ago.
Worked great, until the VZ OTA came out.
Now, the OTA is downloading, even when rejected, sometimes at random times, and attempts to load it.
Just moments ago, it attempted to load, shutdown the phone, attempted to load and gets locked up in the attempt.
If I could stop OTA from attempting, I would be happy. But it seems to try several times a day. Often, my phone is offline and locked in the update area and I don't notice.
I then use ClockworkMod Recovery to wipe cache and reboot. Good to go after, for a few minutes/hours or a day or so, until I repeat the entire process.
So.... my question!!!
How do I revert back to stock, maybe run the update for OTA and then, use the new way to gain root?
I'm new to Rooting, but my buddy who helped is not around now, and I am in a rush to just have a working phone, root not needed until I learn to perform it myself.
Help!
Well, was able to figure it out on my own, with some help from the guys in the chat room.
For those with the same issues, easy fix!
Download the new MR2 Files HERE Section D. Downloaded both the ROM and Radio.
Updated the ROM first and then the Radio. So far... SO GOOD!!!
No more OTA updates in 24+ hours, hoping for a much longer wait for the next one too!!!
Related
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
Long-time lurker, this is my first serious post here, so... be gentle
The Hardware: Verizon Galaxy S3 16GB SCH-i535 (Pebble Blue, if you must know )
Where I was: Rooted Stock ICS 4.0.4 (Root66) VRALF2 with OTA blocker to keep it there.
What I did first:
Unblocked OTA updates.
First update 40MB VRALF2 to VRALG7. Updated succeeded but broke root. Restored Root using Voodoo OTA Rootkeeper
Second Update: 62MB VRALG7 to VRALHE. Updated succeeded but broke root again. Got a Custom Padlock screen on bootup that wouldn't go away even if the phone was not rooted before the upgrade. Restored Root using Voodoo OTA Rootkeeper.
Third Update: 400MB VRALHE to VRBLK3. Update FAILED. Repeatedly. Each time, the update would download and reboot into recovery mode to install. It would get about 40% of the way through and the widdle gween andwoid would fall over with a yellow twiangle above him. Then it would reboot back into VRALHE.
Hmmm...
What I did next:
ODIN flashed back to VRALF2 Root66
Took OTA updates.
First succeeded as before, so did the second. To my surprise the third ran to completion. Restored Root using Voodoo OTA Rootkeeper. Still has a custom padlock on boot, but when I unlocked the bootloader it disappeared - either that or the boot screen didn't stay on long enough for it to appear - not sure which.
Anyway, I am now on JB. The last to the party. as usual. Project butter must have worked - the interface feels smoother.
Battery life is a mixed bag. I use Battery Widget Reborn Pro to measure the average time to use 1% of battery life. Under ICS it was 6-9 minutes. On initially installing Jelly Bean, this initially dropped to about 3 minutes. I assumed that this was because of post-upgrade housekeeping, as the CPU was continuously busy (according to Usage Timelines Pro). After leaving it running and on the charger all night long, it settled down. It is now at 10-15 minutes per 1% of battery life - almost double what I was getting before.
OTA blocker supports VRALF2 and VRALG7, but it does NOT support VRALHE or VRBLK3. This is not surprising; the last version is three months old. With no OTA Blocker, I am at the mercy of whatever method Verizon comes up with to bugger up my phone. The OTA blocker folks need to get their fingers out and update the app.
On the other hand, the folks who built Voodoo OTA Rootkeeper (which I originally bought for my Droid X2) are on the ball and they have saved my bacon thus far.
Hope this helps anyone out there in a similar predicament. The usual caveat applies: Before trying anything drastic, BACK UP YOUR DATA!
Finally I would like to recognize two apps that have been very useful to me during this process: I have no interest in either developer or program, just a satisfied customer.
Usage Timelines -- A neat program that tells you how busy your CPU is (Free, full version is $2.49)
EZ Recovery -- on-the-fly recovery flash of CWM, CWM Touch, TWRP, Stock or... just about anything else. (Free, but I sent the dev a few dollars)
If you want to block OTA, and own Titanium Backup you can freeze the process that triggers them. The OTA Blocker that your talking about is not needed.
Hmmmm...
Elite49 said:
If you want to block OTA, and own Titanium Backup you can freeze the process that triggers them. The OTA Blocker that your talking about is not needed.
Click to expand...
Click to collapse
Funny... I had tried blocking processes before using the OTA blocker, and it hadn't worked. Did I miss something? Which processes do I need to freeze?
SDM 1.0
lol smh
I'll be gentle.
Curious. Why would you go through all of that? You know you could have just unlocked the BL, flashed Vzw JB stock zip and then the radios? And be at the same spot? 8 days sooner? Lol
I never understood the allure of wanting to take an OTA. I like the fastest way possible. We all end up with the same product . Never got it
Oh, and sorry about your X2. I had one of those. Horrid device....
Sent from my SCH-I535 using Tapatalk 2
1ManWolfePack said:
I'll be gentle.
Curious. Why would you go through all of that? You know you could have just unlocked the BL, flashed Vzw JB stock zip and then the radios? And be at the same spot? 8 days sooner? Lol
I never understood the allure of wanting to take an OTA. I like the fastest way possible. We all end up with the same product . Never got it
Oh, and sorry about your X2. I had one of those. Horrid device....
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. I decided to go OTA because... it was there. I wanted to know what the fuss was about. Since I had alreay Odin-flashed a ROM I knew I could, but I had never taken an OTA, and wanted to see how far down that rabbit-hole went.
Had that not taken me where I wanted to go, flashing a JB ROM would have been my next move. The eight-day delay was not an issue - when it comes to updates, I tend to wait until others have taken the arrows in the back.
More than a week later, the phone is rock-solid. Under ICS, I used to have to reboot the phone once or twice a day. This phone has been running for over a week without being rebooted (see screenshot), and is still going like a champ. There are just two problems: The GPS pop-up and the Bluetooth Pop-up... but that is another subject for another thread.
As for the X2, it was a lovely little phone, and I was happy with it. The biggest problem with the phone was the lack of support from Verizon (just like the S3 ) I had to upgrade to keep my unlimited and get to 4G, and that is why I took the S3.
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
NevetsDrassel said:
Got a notification this morning that there was a new update available for KitKat. I do not know what the update is as I postponed it. I am currently running KitKat 4.4.2 Kernel version 3.4.0. The build is D80020c. I am rooted. I have no other information except that it shows that an update is pending but it will not tell me what the update is and I do not know where to find out what it is.
Anyone have any ideas as to what this is? I am concerned because the last time an update rolled out, it soft bricked my rooted phone.
I spoke with tech support at AT&T and they claim that they do not know what it is and suggested that I call LG for an answer.....
Click to expand...
Click to collapse
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Jank4AU said:
Don't install it, it jacked up my phone. I was running the rooted mixed partition D80020c and I can't boot or get into download mode now. All I get it a constant reboot back to recovery. Cannot install another ROM, cannot restore a backup. My daughter was playing with my phone and pushed to continue with the install and now I'm trying to unscrew it.
Click to expand...
Click to collapse
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
NevetsDrassel said:
Is there any way to force a not install or deny it? The only option I have is to postpone the install and after 4 hours, it will run again and continue to run every 4 hours unless I find a way to break the cycle. How do I force a no install option?
That is what happened to me last time with the "q" update. I postponed the install (no option to not take it) and it installed itself after 4 hours when I left my phone on one night. I woke up to a bricked phone.....
Click to expand...
Click to collapse
I don't know how to permanently disable the update, but I'm sure there's a way. As info, I was able to easily fix my phone with the help of this thread posted by @thecubed: http://forum.xda-developers.com/showthread.php?t=2451696. I didn't read it all, but this might be what disables the update.
I'm not rooted. I took the latest update and all is fine. It's google+ fixes and Google wallet support. It actually let me set up tap & pay! I'll have to go somewhere to try it out.
Sent from my LG-D800 using Tapatalk
I got the notification too but figured that it would probably screw things up since I'm rooted and running TWRP so I did a little searching and came across this, http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3 . It's been a few hours since I changed the setting and haven't seen the update notification again although AT&T pushed the update into CACHE/FOTA sometime this morning.
Well scratch that, the notification just came back. I'll try freezing it now.
Well if rooted just use TB to freeze software update. I am also running a mixed partition D80020c. I am on Straight Talk AT&T. Before rooting I tried taking the official OTA of KitKat but for some reason you can't enter an APN type so I couldn't get or send MMS. So I flashed back to the D firmware,rooted,added custom recovery,entered the APN type and then flashed the modified C firmware. You could also use Root Freezer instead of Titanium Backup to freeze
Hi,
This might take a while, and maybe a fellow whiner might understand. Not for the faint of heart or busy people. Disclaimer ends. Kinda.
Naman here. I've a xt1033 Asian variant with stock 4.4.4+root. So, as obvious, bootloader is unlocked.
I'm not a patient fellow, so when someone posted lollipop soak test 5.0.2 zip, I "cleansed" my phone and flashed it.
Some partition problem happened and suddenly I can't on my device's storage, let it be by Bluetooth file transfer or via USB.
So I thought maybe I have to flash it as an update over KitKat.
Again, cleansed and flashed 4.4.4 and then dirty flash 5.0.2 soak.
This time Wi-Fi got fcuk'd up. It kept showing "WiFi turning on...", and the little flick switch was disabled, as in cannot-interact-with disabled.
"Check it tomorrow."
Next day, Official update came. Unbelievable. Resisting temptation of all sorts of plausible lollipops out there for 2 months and the day I flash soak test, official update comes 24 hours later.
So I flash stock 4.4.4 again and as a civilized user, I let Motorola update services take care, I let my phone go through all sorts of rituals.
After some time, I pick up my phone and see a dead green bot with a red caution sign hovering over its cut-open chest.
Apparently, update has failed.
I had philz recovery. So I tried opening my phone long enough to transfer the stock recovery zip. But my curse wasn't done playing around, it kept restarting my phone.
Now after 4th restart, just a wild guess, it says update failed and my phone kept still. So I hurried and put the zip and flashed it.
Finally again I wait through the update rituals. It does update again. Finally, I have it...
The Off-fcukng-cial Lollipop on my G. Guess what? "WiFi turning on...".
Thanks for your precious time, no pun intended.
Sincerely,
Fellow ”installed-kitkat-again" xdian.
P.S. I've already tried stock kernel modules, stock radio, stock kernel, stock recovery for 5.0.2 present in one of the post in development section. Also, I know its super lame to use P.S. in the internet age, but at this point in the, I don't the courage necessary to scroll up and this there.
Peace.
Try this: http://forum.xda-developers.com/showpost.php?p=49656627&postcount=3
I unrooted with su in order to try get updates didn't work I used the. e LG one click method from source Forge that's somewhere up here. when I tried to reroot su got hung up and now it says I have to manually root. I do this stuff on the low on my . dad's pc for like a couple hours a week 2x a week sometime more. sometime less so what do I have to do to fix this I have a d850 with 5.01. so I tried running it through but it just give same results with that method. Help please
Updates via OTA are not possible by just unrooting with su. You have to revert back to KK and then proceed forward. You will end up downloading a few OTAs to get the most up to date version. Be prepared to spend a few hours. Then you will have to root again.
Sent from my awesome phone!
Thanks I guess it really isn't giant of a issue to me if its rooted and I started with lollipop I did it cause I'm a musican and needed an sd card fix now its done so is there any issues ill have to deal with leaving be
I'm also still on stock rom