Related
I'm a noob. I think I need help. I can't install the 2.3.6 update, because my phone's rooted. Or something. Something's wrong. Are there any other rooted users who aren't having trouble with this? I would normally post this in the root only thread but I really need help. I've looked at all the other guides and I still don't understand...please...haha
I really want to UNroot my phone and I've seen the fxz method it's just I understand nothing of it. I tried installing the ADW and all that stuff but it just doesn't seem to work. If anyone can walk me through this, step by step that would be greatly appreciated.
Another little question, is the factory reset delete the root or does it just bury it a little? I factory reset it from inside the phone, not the boot menu, does that make a difference?
Thanks!
Chrisruns said:
I'm a noob. I think I need help. I can't install the 2.3.6 update, because my phone's rooted. Or something. Something's wrong. Are there any other rooted users who aren't having trouble with this? I would normally post this in the root only thread but I really need help. I've looked at all the other guides and I still don't understand...please...haha
I really want to UNroot my phone and I've seen the fxz method it's just I understand nothing of it. I tried installing the ADW and all that stuff but it just doesn't seem to work. If anyone can walk me through this, step by step that would be greatly appreciated.
Another little question, is the factory reset delete the root or does it just bury it a little? I factory reset it from inside the phone, not the boot menu, does that make a difference?
Thanks!
Click to expand...
Click to collapse
What problems have you had installing the OTA. The easiest way to install 2.3.6 would be to install Bootstrap. Then install 2.3.6 as a restore
Curious about this as well. Does doing a factory restore get rid of root?
red12355 said:
Curious about this as well. Does doing a factory restore get rid of root?
Click to expand...
Click to collapse
Doing a restore does NOT get rid of root
Sent from my Atrix 2 using XDA App
I suspected as much. Thanks.
I keep getting a failed update install. it will download properly. It will then proceed to reboot. When loading the update with the little android in the center of the screen it will load about...1/3 of the way, then flash a triangle with an exclamation point and proceed to boot normally. Once booted it tells me, "Update Failed."
What is this "bootstrap"?
Chrisruns said:
I keep getting a failed update install. it will download properly. It will then proceed to reboot. When loading the update with the little android in the center of the screen it will load about...1/3 of the way, then flash a triangle with an exclamation point and proceed to boot normally. Once booted it tells me, "Update Failed."
What is this "bootstrap"?
Click to expand...
Click to collapse
Boot strap allows you to boot into CWM.
Patience is a virtue. Learn and live it.
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
pedrohell said:
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
Click to expand...
Click to collapse
Welcome to the club. Take a look at all the sections for the tablet and make sure you read the stickies too.
Method #2 and youl be good to go.
http://forum.xda-developers.com/showthread.php?t=1831152
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
Let me ask you this, why no flashing? As far as I know it's either Odin or flash. You need to get a custom recovery on it in order to root.
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Also with the s2 the recovery and kernel are in one. This is not.
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
No problem, but it don't get any easier than odin or recovery.
pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
There was an Exynos exploit method but Samsung patched the security hole a few updates ago.
The method in the link that was posted does alter your flash count and that can be correct but you are the owner of the device and if you are not comfortable flashing you tablet I wouldn't.
I have flashed mine and tried a few rom's but I always ended up resetting my flash counter and going back to stock.
Folder mount works great and that was the reason I rooted in the first place but you can store your files on the ext drive and transfer them back and forth manually but I found with my fast wifi I'm better off re-downloading the data along with "Helium - App Sync and Backup" to backup and restore my data and you do not need root, only draw back is that you have to have a computer connection for backup and restore to work.
.
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
I don't think you read that right. You're not flashing a ROM, just a custom recovery through ODIN, then a root app. It's actually very simple. (Any simpler and I would be concerned about rogue app exploits)
Fyi: I'm also new to Samsung devices and bought my tablet this week. Rooted it this morning by following the stickies, but sticking with the stock ROM for now. I'm more than happy with the tablet so far.
Sent from my GT-N8013 using xda app-developers app
pedrohell said:
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
Click to expand...
Click to collapse
There is no flashing a rom with method 2. You Odin the custom recovery then you have to flash the superuser into the system. You need superuser to get root and Odin is the easiest way.
Trust me we have all been in your shoes about being nervous, I've been doing this a long time and this method is really easy.
You can also use this method - http://forum.xda-developers.com/showthread.php?t=1957002
It does require ODIN but as has been stated this is the norm. You are not replacing any kernels or flashing another rom, you are just adding the root components. Using this method also leaves stock recovery intact...
If you woory about flash counter then run triangleaway after to reset the flash counter and recoveries....
I found doing this, doing a factory reset from settings then reflashing the Stock rom using Mobile ODIN pro gave me a stock standard, but rooted, rom with all statuses "Official" and 0 flash count....
A lot of work I know but then worthwhile things generally require it...
Ok, I followed the Method 2 made everything like on video, after pressing Power+Volume Up, I entered on STOCK Recovery, not the CWM,even so, I apply the .zip and I get:
MANUAL MODE
--Appling Multi-CSC....
Applied the CSC-code:LUX
Successfully applied multi-CSC.
--Install /sdcard....
Finding update package....
Opening update package....
Verifying update package.....
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:signature verification failed
I also retryed and turned off auto-reboot in Odin before starting the process but I get the same thing, now what should I do?
Its not rootable?
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
I see that I'm probably too late now to answer the OP.
But maybe others can be interested.
I find that the easiest way to root (without odin and without installing a custom recovery) is Framaroot.
It uses some Exynos exploits, and has been also recently updated by the developer to counteract Samsung's patches.
It may work or it may not work on some devices and with some of the more recent firmware.
In any case giving it a try doesn't cost anything. It's just an app.
If it works the app can also be used to temporarily remove the root.
For me it worked with Firmware N8000XXCLL3 and I know that it works with some more recent fw too.
Furthermore it doesn't change the counter and even the Devices Status remains "Official". Well, actually the devices status may change to "Custom" after few days with the tablet on, but it returns Official after a simple reboot.
pedrohell said:
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
Click to expand...
Click to collapse
Awesome to hear! I ran into the same thing you did, forgot to go straight to recovery from odin.
Enjoy!
Stuck
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
What were your options on the page right before that? What option did you select to initiate that?
Maybe try using the files from here instead:
http://droidviews.com/2013/root-and...ung-galaxy-note-10-1-n8000-n8010-n8013-n8020/
bigtoysrock said:
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
Click to expand...
Click to collapse
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
brix696 said:
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
Click to expand...
Click to collapse
I would use the touch cwm, and what rom are you trying to install?
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
beelow319 said:
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
Click to expand...
Click to collapse
Can you offer up the steps to do that? I know how to do a factory reset, but that will wipe the data. Thanks.
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
newtoncd said:
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Click to expand...
Click to collapse
Are you, or have you been rooted in the past?
rmjones2006 said:
Are you, or have you been rooted in the past?
Click to expand...
Click to collapse
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
beelow319 said:
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
Click to expand...
Click to collapse
May I just say, thank you very much.
That worked ... I am now running v4.4.4 .... and you are right, that was very easy.
Too bad I had already wiped my phone twice ... ugh ... again, thank you!
newtoncd said:
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
Click to expand...
Click to collapse
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
distortedloop said:
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
Click to expand...
Click to collapse
I had replaced the radios with stock before trying to update to v4.4.4 .... when that didn't work, I thought the reset to factory specs would take care of that; no joy.
In the end, I love the HouseofMoto program .... that was really easy.
I did not want to update my nexus 7 at the time I obtained it due to kitkat being new and not having a 1 click root. So I disabled the notifications. Recently I found a 1click app for kitkat and decided I would just restore to factory and then update. I was told to just clear google framework data but that did nothing and only restarted the download..... Problem is even after the restore I am getting verification errors via the manual update via system updates. I am currently sitting here with a full 25Xmb download of the update and am trying to in the nexus recovery mode to load the abt from sideload in cmd but at first i got error 7 and used winrar to repair the zip which got rid of the error 7
Now I am getting
failed to verify whole file signature
signature verification failue (which is what manual update would say when it finished downloading on the system updates screen)
AndroidObsession said:
I did not want to update my nexus 7 at the time I obtained it due to kitkat being new and not having a 1 click root. So I disabled the notifications. Recently I found a 1click app for kitkat and decided I would just restore to factory and then update. I was told to just clear google framework data but that did nothing and only restarted the download..... Problem is even after the restore I am getting verification errors via the manual update via system updates. I am currently sitting here with a full 25Xmb download of the update and am trying to in the nexus recovery mode to load the abt from sideload in cmd but at first i got error 7 and used winrar to repair the zip which got rid of the error 7
Now I am getting
failed to verify whole file signature
signature verification failue (which is what manual update would say when it finished downloading on the system updates screen)
Click to expand...
Click to collapse
i dont know what genius told you that clearing framework data would do what you want, but thats not even close to the right answer.
use this tool to installl the latest factory firmware.
also, this is a nexus device. you dont need to wait for one click root methods. after you unlock and put on a custom recovery, all you need to do is flash the su zip file and install a su managing app then you will be rooted on any version of firmware.
its been a while since i used that tool (i have a 2012 n7) but im thinking it will help you with the recovery and root too if you need it.
wug makes some good scripts.
bweN diorD said:
i dont know what genius told you that clearing framework data would do what you want, but thats not even close to the right answer.
use this tool to installl the latest factory firmware.
also, this is a nexus device. you dont need to wait for one click root methods. after you unlock and put on a custom recovery, all you need to do is flash the su zip file and install a su managing app then you will be rooted on any version of firmware.
its been a while since i used that tool (i have a 2012 n7) but im thinking it will help you with the recovery and root too if you need it.
wug makes some good scripts.
Click to expand...
Click to collapse
updated:
AndroidObsession said:
can't thank you enough for the help in the right direction... Spent all last night frustrated cause no matter how many times i tried to sideload it either was error 7 or error in whole file verify. i will give this a try and get back to you with an update if all goes well... one question though... if there a way to switch the built in 4.3 restore with the 4.4.2 once its installed fresh? that way if i wipe again ill at least be back at fresh 4.4.2 instead of going thru 4.3 issues again
Click to expand...
Click to collapse
Last time I used it there was no default file, you could choose whatever one you wanted, I'm assuming up to current unless he hasn't made those files available.
I don't know if you can insert your own file if he doesn't have it current.
I know it used to download the file you choose, so you may not be able to add alternatives.
Sent from my G2 running SlimKat
bweN diorD said:
Last time I used it there was no default file, you could choose whatever one you wanted, I'm assuming up to current unless he hasn't made those files available.
I don't know if you can insert your own file if he doesn't have it current.
I know it used to download the file you choose, so you may not be able to add alternatives.
Sent from my G2 running SlimKat
Click to expand...
Click to collapse
@bweN diorD
so far i have
flashed stock and unrooted then unlocked 4.3. not sure where to go from there atm... keep getting that error.... Thanks again for the assistance
I also tried doing adb sideload via toolkit but the zip i have keeps giving error 7 verification failed/aborted when trying to update the os from jwr66n to JSS15R so i could manual update to 4.4.2
or even if i try skipping jss15r it will give whole file verification failed when just trying to go straight to 4.4.2
AndroidObsession said:
@bweN diorD
so far i have
flashed stock and unrooted then unlocked 4.3. not sure where to go from there atm... keep getting that error.... Thanks again for the assistance
I also tried doing adb sideload via toolkit but the zip i have keeps giving error 7 verification failed/aborted when trying to update the os from jwr66n to JSS15R so i could manual update to 4.4.2
or even if i try skipping jss15r it will give whole file verification failed when just trying to go straight to 4.4.2
Click to expand...
Click to collapse
im not sure what else to tell you, maybe try and do the update normally ota.
bweN diorD said:
im not sure what else to tell you, maybe try and do the update normally ota.
Click to expand...
Click to collapse
edit: OH.... i think i figured it out now.... i found the firmware selection now
The toolkit had a bad hash apparently for 4.4.2 but i did manual and went to the google page to grab the factory and manually flashed.
tablets now 4.4.2 unlocked and as far as i know rooted. ty for guiding me.
issue is now resolved.
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.
The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.
Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.
Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!
I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.
Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.
I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.
Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol