I rooted yesterday after being on stock for a while. I started goofing around with different ROMs. I flashed a few just to compare them, and now I seem to have lost root? SuperSU says outdated binary, but I cannot update it because it cannot find root. Simple root checker says I am rooted, but root checker days not. Help/advice?
Edit: restoring my stock rooted ROM seemed to fix this. Anybody have any idea what may have caused it?
GAPO said:
I rooted yesterday after being on stock for a while. I started goofing around with different ROMs. I flashed a few just to compare them, and now I seem to have lost root? SuperSU says outdated binary, but I cannot update it because it cannot find root. Simple root checker says I am rooted, but root checker days not. Help/advice?
Edit: restoring my stock rooted ROM seemed to fix this. Anybody have any idea what may have caused it?
Click to expand...
Click to collapse
Super user just had a significant update that has ya download a new clutch of binaries. You probably flashed a rom with outdated su binaries, didn't update the app, then flashed another, and now are unable to get root.
Try updating the app from the Play Store, let it update the binaries, reboot immediately, then see if that sets you back to normal.
Report back please.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Super user just had a significant update that has ya download a new clutch of binaries. You probably flashed a rom with outdated su binaries, didn't update the app, then flashed another, and now are unable to get root.
Try updating the app from the Play Store, let it update the binaries, reboot immediately, then see if that sets you back to normal.
Report back please.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
It seems to only be a problem with one of the ROMs. JellyBomb Domination. I have been switching between it, Toxic Swamp, Minimus, and my backup of stock rooted. The only one it has been a problem with is JellyBomb. I love JellyBomb, I just think maybe my download was corrupted somehow? I will delete the .zip and try it again to see what haopens. But with any of the other ROMS I have been bouncing between all day, it's the only one tthat seems to be affected. As soon as I flash one of the others, I download a couple of root checkers, and they're fine.
GAPO said:
It seems to only be a problem with one of the ROMs. JellyBomb Domination. I have been switching between it, Toxic Swamp, Minimus, and my backup of stock rooted. The only one it has been a problem with is JellyBomb. I love JellyBomb, I just think maybe my download was corrupted somehow? I will delete the .zip and try it again to see what haopens. But with any of the other ROMS I have been bouncing between all day, it's the only one tthat seems to be affected. As soon as I flash one of the others, I download a couple of root checkers, and they're fine.
Click to expand...
Click to collapse
OK, now that is a bit strange, but I would suggest that something else in the sequence of things is going on, and not the rom. The update for 3.2 has been out long enough (since January 20th), and many use the rom, so at least one user would've reported what you're noticing, and I haven't read any similar accounts of same. If I'm wrong, please correct me. I'd also suggest posting this on the JellyBomb Q&A thread.
Ask that you try what I suggested first on a clean install of JellyBomb 3.2, and then report back (fresh flash, straight to the Play Store, update binaries, reboot, finish the setup of JellyBomb).
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
OK, now that is a bit strange, but I would suggest that something else in the sequence of things is going on, and not the rom. The update for 3.2 has been out long enough (since January 20th), and many use the rom, so at least one user would've reported what you're noticing, and I haven't read any similar accounts of same. If I'm wrong, please correct me. I'd also suggest posting this on the JellyBomb Q&A thread.
Ask that you try what I suggested first on a clean install of JellyBomb 3.2, and then report back (fresh flash, straight to the Play Store, update binaries, reboot, finish the setup of JellyBomb).
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Tried it, no good. I am re downloading now and will try again.
Edit: deleted and re-downloaded all three .zips, flashed them and everything is peachy.
Related
Apologies up front... I'm sure this has been discussed ad nauseum, but my searches can't turn up the answer I'm looking for.
I'm not ready to grab the new update, kernel, or radios. I'm running perfectly the way I want with Nils GingerSense 1.5 (GB).
The first OTA nag, I was able to reject. This morning, the OTA downloaded (found the OTAPkg.zip in /cache/fumo), but I was only able to defer several days, no reject option.
Question: Is there anything I can do to prevent future Verizon OTA attempts and forget about this until I'M ready to move forward?
I used to have fotakill.apk in my cm7 rom for the incredible . Maybe you can download any cm7 rom and extract that file. Might work?
I believe you can just delete otacerts.zip from /system/security and it shouldn't prompt you. I think that's what some people did on the Inc to block it before. Some also modified their build.prop, but I'm not sure what the line was, or what to change it to now.
I'm not to be held liable if anything goes wrong after modifying any of these things. Make a backup first!
Sent from my ADR6425LVW using XDA Premium.
SteveG12543 said:
I believe you can just delete otacerts.zip from /system/security and it shouldn't prompt you. I think that's what some people did on the Inc to block it before. Some also modified their build.prop, but I'm not sure what the line was, or what to change it to now.
I'm not to be held liable if anything goes wrong after modifying any of these things. Make a backup first!
Sent from my ADR6425LVW using XDA Premium.
Click to expand...
Click to collapse
I see a otacerts.zip in /etc/security , so I'll try renaming that, thanks.
Well, about an hour after I renamed /etc/security/otacerts.zip to otacerts.zip.bak, another OTA download has begone, so that's not going to do the trick. I've restored the file, and the download is continuing. I'm deferring again, not sure what to try next.
Resigned
DIncLover said:
Well, about an hour after I renamed /etc/security/otacerts.zip to otacerts.zip.bak, another OTA download has begone, so that's not going to do the trick. I've restored the file, and the download is continuing. I'm deferring again, not sure what to try next.
Click to expand...
Click to collapse
You will have to stare at this thing to be ready ... it snuck the OTA at me when I wasn't looking, and I only realized it when the phone vibrated as it leaped into recovery and started flashing the OTA. Never asked my permission, and I never gave it.
I simply deleted every apk in the /system/app folder that said either Verizon or VZW.... I have not gotten any prompts about the OTA and it definitely has not installed or attempted to.
htcdm showed up as "hogging data" in one of my data trackign apps when i got my update message, hope that helps.
Would be nice to reject this OTA.
It don't even ask before trying to apply it!
I'm suprised that people on custom roms are getting the update attempt. Usually on a custom ROM, that kills the OTA updates. This is usually only a problem on those that are on a stock rooted type rom.
Very weird
I'm at a loss. I don't know whether to accept the update or not. I think with the Mainver fix, I can always go back...right?
My thinking is the update might patch a leak that might help us get S-Off. If I'm way off base, please let me know, because ignorance is bliss.
jdmba said:
You will have to stare at this thing to be ready ... it snuck the OTA at me when I wasn't looking, and I only realized it when the phone vibrated as it leaped into recovery and started flashing the OTA. Never asked my permission, and I never gave it.
Click to expand...
Click to collapse
I'm just stock ICS rooted, only did it for removing bloat and using tethering. Now my phone tries to do this update automatically too and it just reboots into twrp and sits there... One of these days it will do it overnight and i'll miss my alarm!! Pisses me off. ha
brettokok said:
I'm just stock ICS rooted, only did it for removing bloat and using tethering. Now my phone tries to do this update automatically too and it just reboots into twrp and sits there... One of these days it will do it overnight and i'll miss my alarm!! Pisses me off. ha
Click to expand...
Click to collapse
I registered just to reply to this. I took did a stock ICS root to get rid of bloat. Last night, it attempted to do an install at 2 AM est, got to recovery and hung. I rebooted it and went to sleep. 7:30 AM, my back-up alarm goes off, I look over at my phone, and it's stuck in recovery again, they tried to push another update while I was sleeping, and I missed my early alarm.
This is unacceptable. I need to find out how to permanently reject this blasted thing.
solo_xda said:
I registered just to reply to this. I took did a stock ICS root to get rid of bloat. Last night, it attempted to do an install at 2 AM est, got to recovery and hung. I rebooted it and went to sleep. 7:30 AM, my back-up alarm goes off, I look over at my phone, and it's stuck in recovery again, they tried to push another update while I was sleeping, and I missed my early alarm.
This is unacceptable. I need to find out how to permanently reject this blasted thing.
Click to expand...
Click to collapse
Yeah, happens to me once or twice a day, and if you don't notice it as it happens, it ends up just rebooted sitting in twrp. So I don't get calls or texts or alarms.
Anyone out there have any idea how to block the OTA's? Or can anyone answer if the following is possible.... I have never used titanium backup for actually doing any backups. I have just used it for removing stupid verizon apps. Could I do a backup of setting/apps and then flash the newest stock ICS ruu or whatever, re-use the root tool, and then restore my stuff from my backup?
Googled it and it was the first result...
http://www.chargeforums.com/forum/d...s-ota-update-very-easy-but-requires-root.html
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Googled it and it was the first result...
http://www.chargeforums.com/forum/d...s-ota-update-very-easy-but-requires-root.html
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
About 8 posts back someone said that didn't work for their rezound. I tried it regardless. Had tried renaming that file with astro file explorer and i didn't have permission so I bought root explorer and it let me do it. We'll see if it keeps doing it to me like it did to the above poster...
brettokok said:
About 8 posts back someone said that didn't work for their rezound. I tried it regardless. Had tried renaming that file with astro file explorer and i didn't have permission so I bought root explorer and it let me do it. We'll see if it keeps doing it to me like it did to the above poster...
Click to expand...
Click to collapse
I used titanium backup pro and froze the updater.apk so far so good. all day and no popups. I am Stock and Root.
ckupsco said:
I used titanium backup pro and froze the updater.apk so far so good. all day and no popups. I am Stock and Root.
Click to expand...
Click to collapse
I'm stock and rooted.
Last night, I froze the updater app in Titanium Backup. I rebooted for good measure. This morning I woke up to my phone booted in recovery.
I rejected the update and booted back up. So this is still an issue...
Just chiming in that I'm also affected, but havne'tthat on Sunday this push broke my GB image, so bad that I had to RUU it to ICS. Now I've been finding my phone at TWRP every morning with an OTA.zip failing to flash.
Additionally, I got a message that offered me to defer my update and I chose 3/10 at 7pm. But it still tried overnight.
Use tibu to freeze the ota updater package.
Or flash a custom recovery like amon ra for rezound. Or even a custom rom, say simplistic if you want to stay on an ics/sense based rom
To get the ota, one must have: a relatively unmodified stock rom (key system apps can't be frozen or missing) and the stock recovery tool. If you change either of those, you won't get prompted to do the OTA.
Sent from my Infected Rezound using Tapatalk 2
---------- Post added at 01:55 AM ---------- Previous post was at 01:49 AM ----------
AndroidGraphix said:
I'm at a loss. I don't know whether to accept the update or not. I think with the Mainver fix, I can always go back...right?
My thinking is the update might patch a leak that might help us get S-Off. If I'm way off base, please let me know, because ignorance is bliss.
Click to expand...
Click to collapse
If you're s-on, you can't rewind the firmware on your phone. The mainver fix is just to get certain roms installed.
While it's possible they could patch the current s-off method, I doubt they care much at this point. Verizon has depleted their stock of replacement rezounds and HTC has moved onto new devices.
Sent from my Infected Rezound using Tapatalk 2
Greetings,
I know the easy answer to this is going to be to flash a new rom, but if I wanted to do that I would have already. I'd rather find and repair the source of the issue and learn from it.
That being said, shortly after getting my tbolt (when they were first released) I used the revolutionary root and added in VPN software for work. Being unaware that OTA updates hadn't been blocked during the rooting, the phone took an update and went into a death-boot-loop. I found a clean updated OTA rom, flashed and unrooted the phone as the VPN software didn't work well for what I intended anyway.
Great, now the phone is all back to stock (or so I thought).. After a while, another OTA update came down, it asked to update, I allowed, and it said update failed.. Repeat ad nauseum for the next several weeks. Since I was happy with the way the phone was operating, I didn't care if it got the updates or not.
So last week, I decided that since the phone is out of warranty anyway, I might as well root and get rid of some of the bloat, and while I'm at it, get rid of the damn nag screen every tine I hook it to a computer. Searched around, found thunderbolt tool 1.0.1, downed it and tried it out, and it proceeded to say unable to lock my phone.
After a little screwing around, the "update status" on the phone itself reports ROM Version: 2.11.605.9, while the tool was getting a response of 2.11.605.5, so it was using the wrong method to get into the phone. So I edited the batch file to use the .9 method no matter what it reported back, and it proceeded to root, add the recovery, and superuser.
Ahhh, life is good, the phone is rooted again, time to start doing my own customization.
Except that after a couple reboots, everything loses the root rights.
Running titanium backup says "asking for root rights" and then "titanium has been granted superuser permissions" but it just hangs there at the "asking for root rights" screen.
Wireless tether similar story... Start the app and it says "press to start tethering" and touching the screen gets "wireless tethering has been granted superuser permissions", then hangs at "please wait while starting".
Won't do anything that requires root, unless I run the tool again and select "S-off but no root", and it will go through a procedure and root will work again for a while.
Also, as I'm typing this, I discovered that it doesn't necessarily require rebooting to lose root. I had root working last night, but when I picked up the phone to get the proper messages to type, it is not showing root again, and it hasn't been rebooted since root was working.
Thoughts on how to repair this without flashing a rom?
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like OTA RootKeeper to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Milimbar said:
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like -edit- to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
Click to expand...
Click to collapse
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
I'll check out the rootkeeper.
disconnecktie said:
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Never took the .19 update, and both the tool and phone report as .05 now. (if I remember correctly the .09 reverts back to .05 to get in)
damm315er said:
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
Click to expand...
Click to collapse
What recovery are you using?
I only use 4ext and would recommend that.
The fix permissions will take up to 5 min and may not help your particular issue, but shouldn't hurt to try.
If 4ext - Boot into recovery, select tools then select fix permissions.
If CWM I think its in the advanced menu.
and If TWRP I think it is in the advanced menu again.
Good luck and listen to the others here, they go out of their way to help people a lot
Ok earlier I misread your post. I thought it said 605.19. Still though something you're doing is causing you to only get temp root. Reread the op of the allinone tool and make sure you meet the requirements before you start it. That away when you run it this time you are in the best possible situation for it to work. Trter is very helpful and if you post your issue in his thread he will probably assist you with anything you need.
Sent from my ADR6400L using Tapatalk 2
I remember having a similar problem about 6-7 months ago.
I would randomly loose root, though not as often as he is describing.
In my case it was a combination of an outdated root method and a flawed ROM.
If everything he is using is current, including the ROM, he shouldn't have an issue.
If it were me I would flash Santod's stock deodexed ROM and be done with it.
It is the stock ROM with nothing changed except it is prerooted.
I understand that you would like to "fix" this issue without flashing a ROM, however the ROM itself could be the problem. this solution is the simplest I can think of.
Using everything from the thunderbolt toolkit, so yes, 4ext.
Found and ran the fix permissions, ran for 15 minutes before it finished so we'll see how it goes.
I get what you're saying about the rom being screwed up, and am starting to think my only choice is to reflash it, so I'll start looking into a new rom.. That being said I'm still pursuing fixing this until I find a rom that serves my purpose.
Is there a good stable ICS for thunderbolt, pre-loaded with root and good battery life?
Yea the one in the post above yours. If you want something a that is faster and has better battery than it then head over to infectedrom.com and check out all the different options santod has made.
Sent from my ADR6400L using Tapatalk 2
Hello,
As a first time poster I would like to first thank the community here for all of the hard work done! It's an extremely informative website.
I successfully rooted my Verizon S4 using the simple exploit for VRUAME7. However, I then decided to permanently remove the bloatware on my phone. After realizing this was a bad idea I decided to flash the phone back to the original VRUAME7 build using the steps in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
The phone works great but I noticed that some of the apps are still missing. I think what may be contributing to this is another stupid decision I made: I tried to download the bloatware with the Play store before I flashed the phone. They obviously aren't too important but what I'm worried about is what may happen when I download the next OTA update. I don't think I will be rooting my phone again so I would like to leave it as is and receive future OTA updates. However, I'm concerned that it may break the OS if some of the apps are missing. Again, the phone works fine now and it doesn't show "Custom" on boot but I'm worried what may happen later down the road with future updates.
Am I safe or should I use a complete factory restore flash and wipe the entire phone?
Thanks!
The rom you odined is a no wipe rom. That is why it did not install all of apps. If you want it to be totally stock use this one.
http://forum.xda-developers.com/showthread.php?p=43420116
Whether or not you do it now is entirely up to you. It might be quite some time before there is another update. If everything you want is working fine now, it wouldn't hurt anything to wait until there is an update.
Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
Thanks! So that pretty much confirms that downloading the OTA update will screw up my current OS. I'll flash the device using the rom you linked. Thanks again for the confirmation!
EDIT: I flashed the phone using the rom you linked and everything works great! It works just like I did when I first purchased it. Thanks again!!
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Under the settings in the Superuser app is an option to "Full Unroot" Will this really work for unrooting the device, or do i need to do the odin thing i keep reading about? Why would odin even be necessary if this is an option. It seems to easy.
You will need to return your phone to stock, root will prevent the OTA. You can try to unfreeze SDM and take the update, it won't brick your phone, it will just fail to install because root will cause it to fail.
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Paramemetic said:
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Click to expand...
Click to collapse
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
Click to expand...
Click to collapse
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
jmgib said:
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bummer, I was wondering about that after i started looking at different image names. I started seeing the common theme, and no I am not on MDK, I am on MK2. Bummer because that file took along time to download here at work.
kude87 said:
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Rageboardr said:
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Click to expand...
Click to collapse
If it is your daily and you aren't in any hurry, I strongly suggest waiting it out. Read some forums and get a better feel about rooting and romming.
A tar file is flashed through Odin, and depending which one you download, could lock your bootloader (I forget which firmware you're on). I'd personally wait for/if NC5 is rooted and proceed then.
"Romming" is a broad term used to define flashing custom roms. Predominantly, this means you have an unlocked bootloader and are flashing zip files through a custom recovery.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Click to expand...
Click to collapse
Hi I had the same issue. mk2, rooted, wanted to take the ota update and didn't mind losing root.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
I have been searching all over to find any information on this new kitkat update for the Note 2. I haven't found much. I think the main thing I found was Knox 2.0 or whatever. Is it possible, or is anyone working on a way to at least get root back on here? I didn't do the update yet, but it's bugging me. I would like kitkat and I like this phone, but samsung/verizon locking this thing down is driving me nuts. To the point that I want to sell this phone. So yeah, is anyone aware of any information on the 4.4.2 update and the possibilities to root it at least. I don't even care to install ROMS.
S5 rooted
mkobella said:
I have been searching all over to find any information on this new kitkat update for the Note 2. I haven't found much. I think the main thing I found was Knox 2.0 or whatever. Is it possible, or is anyone working on a way to at least get root back on here? I didn't do the update yet, but it's bugging me. I would like kitkat and I like this phone, but samsung/verizon locking this thing down is driving me nuts. To the point that I want to sell this phone. So yeah, is anyone aware of any information on the 4.4.2 update and the possibilities to root it at least. I don't even care to install ROMS.
Click to expand...
Click to collapse
Galaxy S5 just rooted maybe this will work for Note2 after 4.4.2 update
http://forum.xda-developers.com/showpost.php?p=53406788&postcount=1
I think it's worth trying for everyone without root. Seems to be successful on several different phones.
Sent from my SCH-I605 using Tapatalk
Yeah I'm just not sure I want to let this update go through just to find out it fails and I'm stuck locked down. Is anyone willing to try? Or has tried? I guess I may have to be the first.
Mkobella I'm in the same boat as you... I've been lurking waiting to see if towel root will work for the 4.4.2 update... I'm on 4.3 and not going to lose my root... If you check it out please report back... It would be awesome if someone who took the kit Kat update could try it out
dpeck411 said:
Mkobella I'm in the same boat as you... I've been lurking waiting to see if towel root will work for the 4.4.2 update... I'm on 4.3 and not going to lose my root... If you check it out please report back... It would be awesome if someone who took the kit Kat update could try it out
Click to expand...
Click to collapse
Looks like it doesn't work currently maybe something will be available in the upcoming days
http://forum.xda-developers.com/showpost.php?p=53423728&postcount=548
Thats unfortunate, has anyone else given it a try?
Yeah this is unfortunate. I would try it if I could flash back to 4.3. Has anyone attempted that? I would gladly chip in and help with this, but I'm new and don't know much about rooting and what not. If there are people working on it I would like to find them.
So... I can confirm that this root does not work for the VZW Galaxy note II running the latest update 4.4.2 (ND7). I tried it several times. Not sure if I am doing anything wrong, but from what I gathered, its pretty straight forward. Just run the app. Also, I can tell you that once you download the OTA you WILL NOT be able to go back to a previous version. I tried to Odin back to MJ9 4.3 and that failed. So, essentially, once you do the kitkat update, you're screwed, and stuck. I can't root, can't go back now. Hopefully someone else can figure this out. Or chime in?
Please try these steps: http://forum.xda-developers.com/showthread.php?t=2784138
Rooted wife's S4. Ran towelroot. Tried the play store supersu but it couldn't install su binaries so I thought it wasn't rooted until I tried an app that needed root. It got root via supersu even tho it kept complaining about binaries. I then followed the steps in that post and the phone is now rooted with safestrap.
Also try app called root checker from play store.
Towel root does not work. The phone just reboots almost immediately after pressing make it ra1n. Once it boots back up I have checked with root checker. I am not root. Tried it several times. It appears that the exploit gets past the enforce SELinux but for some reason it doesn't on this phone. Or maybe it's Knox that is knocking it down and rebooting the phone.
Sent from my SCH-I605 using Tapatalk
mkobella said:
Towel root does not work. The phone just reboots almost immediately after pressing make it ra1n. Once it boots back up I have checked with root checker. I am not root. Tried it several times. It appears that the exploit gets past the enforce SELinux but for some reason it doesn't on this phone. Or maybe it's Knox that is knocking it down and rebooting the phone.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
doesn't work with mine either
after reading the thread on towel with the drastic high usage is disappointing. Im seeing now where someone suggested puttting SuperSU on before the the towel exploit .. however it questionable. RIght now most talk seems to steam from shutting off knox which seems to be the issue.
Unfortunately putting supersu on before you use the towel exploit does nothing. Supersu needs root in order to run or do anything. And even so. I ran the exploit several times. First time with with supersu. Second time with out. Then I reinstalled the latest and ran it again. Still nothing. Phone just reboots and is unrooted. Also, you can't disable Knox with out root. Whether that be from supersu disabling it or freezing and/or uninstalling Knox files. You need root in order to do these things. I ended up emailing geohot a few days ago about it, but he never got back to me. Like I said I am willing to try things and help on a project. But, I am no programmer.
Sent from my SCH-I605 using Tapatalk
No root eiter
mkobella said:
Unfortunately putting supersu on before you use the towel exploit does nothing. Supersu needs root in order to run or do anything. And even so. I ran the exploit several times. First time with with supersu. Second time with out. Then I reinstalled the latest and ran it again. Still nothing. Phone just reboots and is unrooted. Also, you can't disable Knox with out root. Whether that be from supersu disabling it or freezing and/or uninstalling Knox files. You need root in order to do these things. I ended up emailing geohot a few days ago about it, but he never got back to me. Like I said I am willing to try things and help on a project. But, I am no programmer.
N2 VZW
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I too am in this boat! have tried EVERY possible way too get towel too work on my N2 VZW but nada!. I also emaled him and G+ him but NO response?, So i think we are left out!!
I guess we are left out. I'm sick of Verizon and Samsung locking us down! Well I'm not giving up. I keep looking and trying. Hopefully someone else comes on here and helps out.
Sent from my SCH-I605 using Tapatalk
Hey everyone. I am in the same boat. I just want to root because I can't save anything to my SD card anymore. If anyone has a fix please let us know!!
Thanks!!
Sent from my SCH-I605 using XDA Free mobile app
Me too!
It has nothing to do with Verizon. It's all samsung
Sent from my LG-VS980 using XDA Free mobile app
Well, I managed to get a log of this Towelroot running via ADB. I emailed Geohot again, and pasted a portion of my log in the email. I'm hoping he responds this time. I will post a snippit of my log on here for anyone to see if they can make sense of it. Hoping Geohot or someone can respond and shed some light on this, as to why this doesn't work for us, and if it can. After the last line the phone just reboots, no root.
http://pastebin.com/P05AuknT