Related
Hello, first of all, I'm sorry for the noob question. I tried to search for the answer but I got more confused than when I started. I have rooted my SGS3 just to be able to use the Wifi hotspot, I'm not into other modifications or anything, I just wanted the hotspot. Now the phone wants me to update through OTA, but of course it's not working. My questions are:
-Should I go back to stock (following the videos from qbking77) and then apply the OTA? Is it safe?
-Should I go back to stock and MANUALLY update the phone?
-Is LF9 the latest OFFICIAL update?
-Is there anything else I should consider?
I don't care about custom roms or any other modifications, I like the phone vanilla BUT with the hotspot enabled. I was looking through a lot of videos and threads but I could't find a good answer.
Thanks in advance!
The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.
m20120 said:
The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.
Click to expand...
Click to collapse
Thanks for the help! Yes I think I have CWM on. I followed a video from qbking77 (I think) and installed it. Or at least it was something like custom recovery or something the like. Do you think I can apply the update directly from CWM? Or it would be easier (and cleaner) to go back to stock recovery and do it "officially". Also, are all stock recovery the same? I ask because there are some different files in qbking77's website. I don't know if the version of stock recovery matters at all. Also, thanks for the tip on the modified app.
You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.
m20120 said:
You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.
Click to expand...
Click to collapse
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?
nahuelarg86 said:
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?
Click to expand...
Click to collapse
It is probably there if it is prompting you to update.
One step that I almost forgot about. When you do the update you will reinstall the script that detects a custom recovery and it will install the stock recovery.
There is a good procedure here that gives you the step by step process, including flashing the Team Epic file to prevent the updated ROM from restoring the stock recovery. If you do not flash the Team Epic file the update will still be successful and you will still have root, you will just end up with the stock recovery.
The process is really easy and it is the one that I used to update from LI3 to LJ7.
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Monoclypsus said:
I recently took the ota update to 4.1.2 mb1 and lost root. My question is can I use odin to flash [ROM|Stock Rooted] 3/3/13 Sprint Touchwiz Jelly Bean 4.1.2 (L710VPBMB1) Odex/DeOdex? And If so do I use the full ROM odex? And Do I have to flash anything besides the ROM? Or can I keep everything else stock?
Click to expand...
Click to collapse
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
ok
topherk said:
Hey there buddy, welcome to XDA (I see this is your second post).
Anyways, do you still have a custom recovery? I'm assuming you don't, since it sounds like you went all the way back to stock unrooted in order o get the update (in the future, Freeza typically has the update for Root users a week or so after the OTA release, so no need to go back to stock unrooted).
Anyways, back to your current situation. Since you most-likely have the stock recovery, you'll have to go back to being rooted with either CWM or TWRP (I prefer TWRP, but they're both good). I personally use mskip's toolkit, it's fairly straightforward. You could also follow qbking77's rooting method. He does a good job explaining how to root. Samsung hasn't locked their bootloader and don't try to in their updates, so these rooting methods stand the test of time (and updates).
Once you have a custom recovery installed (or if you already have one installed), FIRST THING to do is perform a nandroid backup. THIS IS KEY. Once you have one done, go ahead and flash Freeza's Stock Rooted ROM. I'd recommend doing a clean flash, as it's the best way to minimize the chances of errors and bugs. Just wipe system and cache and dalvik cache, and then flash the downloaded ROM. And speaking of downloading, be sure to check the md5 sum of the download before you flash. Most problems with the stable ROMs here on XDA stem from bad downloads.
You can also check out other ROMs. I won't go too crazy on advertising here, but scroll through these two sub-forums, Android Development and Original Android Development. I've enjoyed most ROMs I've tried.
Hope this helps!
Click to expand...
Click to collapse
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Monoclypsus said:
Ok, just out of curiousity... Before I took the OTA i was rooted 4.1.1 stock with stock recovery. Is there any way to do it the same? The method I used before was this [HOWTO] [ROOT] No Tripping Flash Counter [SPR L710VPBLJ7] JB 4.1.1. It was super quick and easy.
Click to expand...
Click to collapse
Yeah, that same method should work. I personally like the custom recoveries, but understand your desires to leave it at stock recovery (not triggering the flash counter).
Like I mentioned before, Samsung hasn't (and most likely won't) locked their bootloaders, so any rooting method that has worked in the past should work in the future. Just make sure to read the last 3-4 pages of the thread for whatever method you're trying to use to see if there are any issues. I know an earlier version of mskip's toolkit was having issues with JB for a little bit (it's updated now).
Well I'm gonna give it a shot. Ill let you know how it turns out.
Sent from my SPH-L710 using xda app-developers app
Just went with cf autoroot. Worked fine.
Sent from my SPH-L710 using xda app-developers app
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
jkj said:
I've got a problem I installed the OTA and now I cant boot into android. Its stuck on starting apps. I have the stock recovery. How can I fix this?. What do I do? I can get to ODIN download mode. *edit** can get into safemode too. And I now have a custom recovery installed.
I still dont know what to do from here. How do I flash the downloaded rom because the new file I downloaded seems to be a zip and can only be flashed with CWM not ODIN. I cant place it in the right directory of my phone to do that.
Click to expand...
Click to collapse
I replied to your thread. I hope it works for what you need.
I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is it possible to flash or adb stock recovery back?
Yes, the stock recovery and files are posted here. I have reflashed the stock recovery and ota'd myself. As easy as flashing a custom recovery. You might want to read all the other ota threads here...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
flyinfool2 said:
Is it possible to flash or adb stock recovery back?
Click to expand...
Click to collapse
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Great info, Thanks!
flyinfool2 said:
I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
Click to expand...
Click to collapse
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
andybones said:
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Click to expand...
Click to collapse
Well damn andy. Dropped the knowledge bomb on him
Yeah it's not worth OTA'ng, especially given the experience vzw S4 owners had with getting their root exploits and such closed...
Flashable OTA update question
So my One is unlocked and S-off. I manually updated to firmware version .15, however, my ROM is still version .10. (I could not download the version .15 ROM version as it was taking way too long) I keep getting the constant nag about the software update. I want to stay current, but dont want to lose ROOT or worse.
First, how do you use a flashable rom file to update your current rom? I dont what to have to backup and flash a new rom and restore all my settings everytime if I can avoid it. Is there a way to just update like what the OTA does?
Here was my thought. I would make a backup and clean install the current version (.15) of a custom, stock ROM. This would prevent future OTA's correct? Then, I would just update with flash-able files as they are released to keep my ROM up to date and ROOT privileges, etc safe?
Or would it be possible to update my current .10 ROM to .15, disable all OTA's and then flash updates as they are released?
BreakingVZW said:
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
Click to expand...
Click to collapse
This is my wifes phone, so she is not concerned with having any custom operating ROM. For me however, I have always been a hacker at heart, and I love to run different ROMS on my own phone. For her phone, I just want the ability to run the most recent stock software, with root, so that I can make backups and freeze unnecessary apps to my liking. If a rooted stock zip is just around the corner, then I see no need to take the OTA update as you stated. Thanks for the insight. I just didn't realize that I could get the same result (an updated stock, rooted update) without taking the OTA. I appreciate the help! :good:
What can I do in the meantime to prevent my wife from accidentally accepting the OTA (it just began pushing on her phone)? I know the update wont take without stock recovery installed, but is there an easy way to prevent the repeated download and prompt for install?
EDIT: I found another thread with a flashable file to stop OTA...thanks all
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
wpsantennas said:
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
Click to expand...
Click to collapse
I have that. Haven't figured it out yet either. I did the stock recovery too. s-off and unlocked.
Had the same exact problem as WPSantennas and paganhobbit. Endded up using this thread http://forum.xda-developers.com/showthread.php?t=2475216 to return to S-On, Locked Bootloader at 1.10.605.8 (For mine to work right on this tutorial I had to skip the 2nd 'fastboot oem rebootRUU' after failing for it work.) I think the latest OTA doesn't really like if you have modified or deleted their stock bloat apps for some reason. IMO, The update is not impressive at all and I'd advise to stay at 4.2.2 but this is may be good to do if you want to bump to KitKat in the future. Hope this helps!
EDIT: Here's the link to the RUU I used since the link on the original was dead: http://www.android-edge.com/Login/uploads/PN017IMG_M7_1.10.605.8.zip
I ended up RUU-ing as well, going back to .10. Then it updated to .15 and the 4.3 update without a problem. I didn't re-lock or go S-On to do this. I had tried three different "official stock recovery" files I found, but 4.3 wouldn't update successfully with any of them.
A new problem is it doesn't seem to want to remember my WiFi connections for some reason now. If I go out of range and come back, I have to re-enter the WPA2 key all over again. I suspect it's Verizon's ploy to make me use more data
I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
KingKobra813 said:
I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
Click to expand...
Click to collapse
Yes wipe your storage n youll. Be good to go
pbedard said:
Yes wipe your storage n youll. Be good to go
Click to expand...
Click to collapse
I wiped my internal storage and I'm still getting stuck in at the same part. Do I need to wipe my external storage as well?
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
Thank you. I will try that.
KingKobra813 said:
Thank you. I will try that.
Click to expand...
Click to collapse
Forgot to mention that Flashify has become a trusted source, to me and maybe others here. You can find it on Google Play and it will download TWRP, I recommend the non-zip latest one. Flashify will also automatically prompt you to install it from where it just downloaded it and checks its integrity. Since TWRP updates frequently, could be a manual step saver.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
So I used a totally different computer and new cable and I'm still getting stuck at the exact same place. Everything on ODIN said it worked but my phone just bootloops.
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
samep said:
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
Click to expand...
Click to collapse
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
KingKobra813 said:
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
Click to expand...
Click to collapse
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
samep said:
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
Click to expand...
Click to collapse
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
KingKobra813 said:
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
Click to expand...
Click to collapse
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
samep said:
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
Click to expand...
Click to collapse
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
KingKobra813 said:
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
Click to expand...
Click to collapse
Correct.
Refer to post 8 for the links to alternate rooting method files if you don't already have them.
Best wishes for success. No luck to it.
These files will restore stock recovery and cache for those who have rooted with CF Auto Root, so that you can return those partitions to factory status for an OTA. Remember that any changes to /system in Lollipop nullifies OTA capability so you also need to undo any changes you've made, restore any bloat, unroot from within SuperSU, etc. For those who used CF and have done minimal mods or changes, this is merely a faster (both in terms of download time and flash time) way of restoring recovery and cache (which are modified when you flash CF Auto Root) than flashing the full stock tar. If you've deleted a whole bunch of bloat, installed Xposed, flashed mods in recovery, etc. then you probably just wanna use the full tar
Flash via Odin PDA/AP slot.
OC9:
OCF:
https://www.androidfilehost.com/?fid=24052804347756900
OE2:
https://www.androidfilehost.com/?fid=24052804347756938
Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!
JoeFCaputo113 said:
Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!
Click to expand...
Click to collapse
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today
iBowToAndroid said:
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today
Click to expand...
Click to collapse
AHHHH!! You are a God! Thanks so much :good:
I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.
Johnrob011045 said:
I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.
Click to expand...
Click to collapse
If you install a non-stock recovery (like TWRP) you cannot take OTA updates. Any version, doesn't matter.
Follow the guide posted at http://forum.xda-developers.com/sprint-galaxy-s6/general/how-to-to-100-stock-root-t3075448 and you will have the latest version with custom recovery and root.
Or, if OTA updates are crucial to you, Odin the TAR file and stop there.
Mine wasn't working after I flashed the stock rom from Sammobile before I flashed twrp, since it wouldn't update I figured I needed twrp to stay up to date from now on but I'm not trying to post bad information to anyone, it wasn't working for me but maybe these caches can bring back OTA. I wish there was a way to get Samsung pay working.