Hating Sammy atm. I'm getting the notice to update once an hour now. I don't want to update because I'm still testing the phone and want to root KK. Still in my return period but don't want to. Just want the update issue resolved.
Questions/info, etc.
1. Solved.
2. I want to root, but prefer rooting KK, not LP because I like the idea of being able to downgrade later if I really hate LP, and I'm hearing a lot of bad stuff about LP.
3. Not rooting until I'm sure I'm keeping this baby - i.e. no other issues, etc. Samsung can bite me!
4. What would you do?
5. I have previously rooted five devices, but am a beginner at best. This is only my third Samsung and it's very different to root, etc..
6. If anything goes wrong with root I am really screwed because I don't want a Note 5 or a downgrade if I have to use my insurance.
7. I trust the long-term, knowledgeable xda guys so that's who I'm really asking.
8. I don't want a rom, only root and twerp or cwm at some point, but not yet.
9. I would tend to use CF auto-root since it worked for me on the Note 3.
10. I can do a factory reset, but just got it all set up yesterday.
11. Which root and why?
12. Will I be able to downgrade if I update to LP or would I be better off waiting and dealing with the update notice?
I'm on KitKat 4.4.4 and everything is smooth with zero issues.
Pertinent info:
Sprint Carrier
Software version - KTU84P.N910PVPU1ANK2
Hardware version - N910P.05
Thanks in advance. You guys rock and you know it!
Yes you can use CFAutoRoot and even root NK2 stock. I don't recommend it on OG5 root due to the kernel exploit required; hence, boot loops.
If you value Sprint Wi-Fi calling, you may want to consider Lollipop OB7.
If you do update to lollipop, only OB7 will allow downgrade back to KitKat.
Xposed works on stock Odex in KitKat but Lollipop 5.0.1 requires arter97 art framework along with the rovo89 Xposed installer and only works with deodexed ROM.
Warranty void is something you'll have to weigh yourself. I waited a couple of weeks before rooting myself to make sure my phone and firmware was error free. I've mostly used rooted stock myself.
That should help with your no pressure decision.
Sent from my SM-N910P using Tapatalk
samep said:
Yes you can use CFAutoRoot and even root NK2 stock. I don't recommend it on OG5 root due to the kernel exploit required; hence, boot loops.
Click to expand...
Click to collapse
But OG5 is not me, right? Or did I not give enough info? AFAICS I'm not OG5, but don't want to make any mistakes here.
samep said:
If you value Sprint Wi-Fi calling, you may want to consider Lollipop OB7.
If you do update to lollipop, only OB7 will allow downgrade back to KitKat.
Click to expand...
Click to collapse
I do value Sprint Wi-Fi calling. How can I make sure that the download I have waiting is LP OB7
samep said:
Warranty void is something you'll have to weigh yourself. I waited a couple of weeks before rooting myself to make sure my phone and firmware was error free. I've mostly used rooted stock myself.
Click to expand...
Click to collapse
The hardware on these devices seems really stable. I've only had my Note 3 (my first Note) since 10/2013 and rooted since 10/2014, but everything has been very stable with only app issues that are easily resolved. So I'm less worried about using my Sammy warranty as long as everything stays golden during this 14-day testing phase. I have insurance with Sprint, but as previously mentioned, do not want to end up with a downgrade device (at worst) or a Note 5 (at best).
samep said:
Xposed works on stock Odex in KitKat but Lollipop 5.0.1 requires arter97 art framework along with the rovo89 Xposed installer and only works with deodexed ROM.
Click to expand...
Click to collapse
As mentioned, I don't use roms, but do use the CWM for backups. I use Titanium BU and several other root apps for configuring and convenience, but everything else is stock (sort of ).
Don't really understand anything about Xposed. Looked at it and understood even less. If you take time to explain how it is used and installed (via recovery, assuming) please talk to me like I'm a 2-year old, because with roms I am.
Thank you for taking the time to help! I really appreciate it.
toenail_flicker said:
But OG5 is not me, right? Or did I not give enough info? AFAICS I'm not OG5, but don't want to make any mistakes here.
Click to expand...
Click to collapse
Don't think so but Galaxy Tools will tell you for sure. If you're running NK2 with no issues, you're most likely correct.
toenail_flicker said:
I do value Sprint Wi-Fi calling. How can I make sure that the download I have waiting is LP OB7
Click to expand...
Click to collapse
OTA updates are incremental but I'd recommend Odin OB7 if that's your choice.
toenail_flicker said:
The hardware on these devices seems really stable. I've only had my Note 3 (my first Note) since 10/2013 and rooted since 10/2014, but everything has been very stable with only app issues that are easily resolved. So I'm less worried about using my Sammy warranty as long as everything stays golden during this 14-day testing phase. I have insurance with Sprint, but as previously mentioned, do not want to end up with a downgrade device (at worst) or a Note 5 (at best).
As mentioned, I don't use roms, but do use the CWM for backups. I use Titanium BU and several other root apps for configuring and convenience, but everything else is stock (sort of ).
Don't really understand anything about Xposed. Looked at it and understood even less. If you take time to explain how it is used and installed (via recovery, assuming) please talk to me like I'm a 2-year old, because with roms I am.
Thank you for taking the time to help! I really appreciate it.
Click to expand...
Click to collapse
Xposed is really for those don't like stock or are bugged by things that don't work as expected. If you use Nuance Swype but hate Dragon Dictation, there's a module for that. Want to change functions or theme or volume change audible change bugs you? You can fix that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Xposed installer installs via apk sideload. OB7 would require deodexed ROM plus another flashable zip that installs the art framework.
http://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
Sent from my SM-N910P using Tapatalk
samep said:
Don't think so but Galaxy Tools will tell you for sure. If you're running NK2 with no issues, you're most likely correct.
Click to expand...
Click to collapse
I have GalaxyTools. Thought it required root to use so haven't installed it on my N4.
samep said:
OTA updates are incremental but I'd recommend Odin OB7 if that's your choice.
Click to expand...
Click to collapse
I have something waiting now and it just wants to install. If I go to recovery will I be able to see what it is? Is there some other way I can find out which it is?
Thanks again!
toenail_flicker said:
I have GalaxyTools. Thought it required root to use so haven't installed it on my N4.
Click to expand...
Click to collapse
Correct
toenail_flicker said:
I have something waiting now and it just wants to install. If I go to recovery will I be able to see what it is? Is there some other way I can find out which it is?
Thanks again!
Click to expand...
Click to collapse
If you respond to the prompt in pull-down, it should give a change log with update number? Maybe reboot or go into Settings/System Update?
Once you get rooted and running the ROM you prefer, you can delete the folder below that pertains to your Android version to avoid those update notifications and downloads.
Lollipop= /cache/fota*
KitKat= /data/fota*
*= delete whole folder to stop notifications and update.zip downloads.
Sent from my SM-N910P using Tapatalk
samep said:
Don't think so but Galaxy Tools will tell you for sure. If you're running NK2 with no issues, you're most likely correct.
Click to expand...
Click to collapse
I opened GalaxyTools and looked but don't see anything that shows OG5. Specifially, where would I look?
toenail_flicker said:
I opened GalaxyTools and looked but don't see anything that shows OG5. Specifially, where would I look?
Click to expand...
Click to collapse
Main screen: bootloader version confirms the last full update.
Sent from my SM-N910P using Tapatalk
samep said:
If you respond to the prompt in pull-down, it should give a change log with update number? Maybe reboot or go into Settings/System Update?
Click to expand...
Click to collapse
I see it now. It is Lollipop 5.0. What number is the bad one? Doesn't give letter like OB7
samep said:
Once you get rooted and running the ROM you prefer, you can delete the folder below that pertains to your Android version to avoid those update notifications and downloads.
Lollipop= /cache/fota*
KitKat= /data/fota*
*= delete whole folder to stop notifications and update.zip downloads.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks!
samep said:
Main screen: bootloader version confirms the last full update.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
:victory: This is my bootloader N910PVPU1ANK2
toenail_flicker said:
:victory: This is my bootloader N910PVPU1ANK2
Click to expand...
Click to collapse
Thank god, i ran out of popcorn at just the right time.
xxSTARBUCKSxx said:
Thank god, i ran out of popcorn at just the right time.
Click to expand...
Click to collapse
Now you're just being mean...
Thanked you earlier and ran out again.
Now were back at Square 1. *taps foot*
toenail_flicker said:
Now you're just being mean...
Thanked you earlier and ran out again.
Click to expand...
Click to collapse
!! Lol, Glad you took it in the right context.
xxSTARBUCKSxx said:
Thank god, i ran out of popcorn at just the right time.
Click to expand...
Click to collapse
xxSTARBUCKSxx said:
Now were back at Square 1. *taps foot*
!! Lol, Glad you took it in the right context.
Click to expand...
Click to collapse
Of course. :laugh: I was following you around earlier looking for a good post to thank. Saw you "beat up" the guy who was asking too many questions about idone and thanked you. Idone is alright.
Thanks for the thanks! :good:
Turns out that this waiting update, according to Sprint is the OB7. I'll wait a couple of weeks and then root and move to LPOB7.
Would someone please tell me where to access the activation lock on KitKat4.4.4? I'm going blind from searching and looking at menus. :silly: Not finding it. Admittedly, it's probably me. Getting everything ready for root. TIA!
toenail_flicker said:
Would someone please tell me where to access the activation lock on KitKat4.4.4? I'm going blind from searching and looking at menus. :silly: Not finding it. Admittedly, it's probably me. Getting everything ready for root. TIA!
Click to expand...
Click to collapse
Reactivation lock started with bootloader OE1 which you wouldn't have with KitKat or OB7. It's found in Settings/Security.
If you have the recent Odin 3.10.x series, in the option tab, there's a OEM unlock that is recommended for those those bootloaders.
For recovery and initial modem flash, the auto reboot shouldn't be checked. Requires a battery pull and 30 seconds wait. For recovery, boot back into recovery. For modem, flash the second time and let it boot on second flash.
The older bootloaders may not require the battery pull for recovery but for the sake of confusion, it's recommended.
Sent from my SM-N910P using Tapatalk
samep said:
Reactivation lock started with bootloader OE1 which you wouldn't have with KitKat or OB7. It's found in Settings/Security.
If you have the recent Odin 3.10.x series, in the option tab, there's a OEM unlock that is recommended for those those bootloaders.
For recovery and initial modem flash, the auto reboot shouldn't be checked. Requires a battery pull and 30 seconds wait. For recovery, boot back into recovery. For modem, flash the second time and let it boot on second flash.
The older bootloaders may not require the battery pull for recovery but for the sake of confusion, it's recommended.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks! I may have more questions about the other things you mentioned here later. Thought I was just too tired to find the activation lock.
TWRP
Need help again, please. I have no idea how to install twrp or which one to install for kitkat 4.4.4. I have somehow gotten some app that has put ads on my lock screen and I want to root after factory resetting, but I want to install twrp first. All help appreciated.
Many humble thanks!
toenail_flicker said:
Need help again, please. I have no idea how to install twrp or which one to install for kitkat 4.4.4. I have somehow gotten some app that has put ads on my lock screen and I want to root after factory resetting, but I want to install twrp first. All help appreciated.
Many humble thanks!
Click to expand...
Click to collapse
Odin CF Auto Root first and then Odin TWRP.
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
An easier method to get TWRP would be to let the CF Auto Root flash auto reboot and install Flashify in Google Play to use to download and flash TWRP.
Sent from my SM-N910P using Tapatalk
Related
I have a rooted Galaxy S3 with stock rom.
I keep getting a pop up for a system update, but cant update.
Please tell me how to manually update, and (where) I can find the latest stock updated software
Thanks
Voodoo8648 said:
I have a rooted Galaxy S3 with stock rom.
I keep getting a pop up for a system update, but cant update.
Please tell me how to manually update, and (where) I can find the latest stock updated software
Thanks
Click to expand...
Click to collapse
Take a look in the android dev sections to this forum. If you ever update once rooted, you should be flashing a new ROM (clean or dirty flashing) to receive the next update. Running stock ROM in between a Sammy update and while having the older ROM without the newest update will yield that result.
Xontic said:
Take a look in the android dev sections to this forum. If you ever update once rooted, you should be flashing a new ROM (clean or dirty flashing) to receive the next update. Running stock ROM in between a Sammy update and while having the older ROM without the newest update will yield that result.
Click to expand...
Click to collapse
I dont know what any of that means.. I just want to update my phone. This cant be brain surgery.
Voodoo8648 said:
I dont know what any of that means.. I just want to update my phone. This cant be brain surgery.
Click to expand...
Click to collapse
This might be a foolish question, but why root your phone to leave it as is?
Xontic said:
This might be a foolish question, but why root your phone to leave it as is?
Click to expand...
Click to collapse
Wonderful question. I would LOVE to unroot my phone :good:
lol, well if you want to read up on installing a custom ROM, then that is your ticket to experiencing the world of rooted phone glory. If not, I recommend looking up the unroot method...
Xontic said:
This might be a foolish question, but why root your phone to leave it as is?
Click to expand...
Click to collapse
There are plenty of reasons for rooting but remaining stock (such as: tethering, Droid wall, Titanium Backup to allow me to backup and restore app data, removing bloat, etc).
I have flashed custom rooms in the past on my Evo but right now I am happy with my S3 at stock.
Sent from my SPH-L710 using xda app-developers app
Xontic said:
lol, well if you want to read up on installing a custom ROM, then that is your ticket to experiencing the world of rooted phone glory. If not, I recommend looking up the unroot method...
Click to expand...
Click to collapse
Oh, okay, Thanks for the help!
Voodoo8648 said:
I have a rooted Galaxy S3 with stock rom.
I keep getting a pop up for a system update, but cant update.
Please tell me how to manually update, and (where) I can find the latest stock updated software
Thanks
Click to expand...
Click to collapse
I was in the same boat at you. I put it off for a while but finally decided to update tonight. I followed the steps posted here.
You can update your baseband by flashing a properly packaged official baseband zip, or flash from recovery tool (my preference), like the one here: http://forum.xda-developers.com/showthread.php?p=29820376. There are also unofficial, or leaked basebands, available to flash from all-in-one zips, such as the one here: http://goo.im/devs/freeza/Galaxy-S-fre3-LIGFirmwareModemAIO.zip.
As far as the build version goes, that does not have to match your baseband (modem). Most of the ICS ROMs are LG8, although there are some LI3 ICS ROMs to choose from. There's also a leaked build of Jellybean, builds LIF & LIG, with a third leak LIH reportedly coming out tomorrow. Once rooted, you can update your build version by flashing the ROM of your choice, based upon the build of your choice.
One of the top developers, and probably the greatest asset to this community, is freeza. He explained the difference very well here: http://forum.xda-developers.com/showthread.php?p=32095775
That's a long-winded response, but I hope it answered your original question, and helps you out.
Have fun!
Edit: Once you're rooted, you'll still receive OTA update notifications, which will continually annoy you until you choose to update and reboot. Once you reboot, the update will fail because of your custom recovery (you will NOT lose root) and the notification will go away....until the next OTA...
Sent from my SPH-L710 using xda premium
m20120 said:
I was in the same boat at you. I put it off for a while but finally decided to update tonight. I followed the steps posted here.
Click to expand...
Click to collapse
Excuse me for my stupidity but I'm new to android. I'm also using the sprint variant of the s3 and have it rooted with stock rom. However my build number is IMM76D.L710VPALF9. I'm assuming the last 3 are the update versions. What is the current version and how do I update to it?
Also, I'm rooted with Clockwork mod 5.5.0.4. How do I upgrade this to version 6.0.1.2? Will I have to unroot then root again?
Thanks for clearing anything you can up. Don't mean to pirate the OP but I figured I'd post in this thread rather than make a new one. Thanks again.
johnnygabe89 said:
Excuse me for my stupidity but I'm new to android. I'm also using the sprint variant of the s3 and have it rooted with stock rom. However my build number is IMM76D.L710VPALF9. I'm assuming the last 3 are the update versions. What is the current version and how do I update to it?
Also, I'm rooted with Clockwork mod 5.5.0.4. How do I upgrade this to version 6.0.1.2? Will I have to unroot then root again?
Thanks for clearing anything you can up. Don't mean to pirate the OP but I figured I'd post in this thread rather than make a new one. Thanks again.
Click to expand...
Click to collapse
You can flash a new recovery using ODIN, or Mobile ODIN. I use Mobile ODIN. There's a thread on recoveries here: http://forum.xda-developers.com/showthread.php?p=31894089
As far as the versions, see my previous post on this thread.
Sent from my SPH-L710 using xda premium
Can anyone tell me how to just UNROOT?
Maybe step by step instructions and where to get the software?
Thanks
Voodoo8648 said:
Can anyone tell me how to just UNROOT?
Maybe step by step instructions and where to get the software?
Thanks
Click to expand...
Click to collapse
There is a link to a video of the unroot process in this post.
I just discovered a reason NOT to unroot...
I just found out that I can tether free wifi hotspot!
Zoing!:victory:
Voodoo8648 said:
I just discovered a reason NOT to unroot...
I just found out that I can tether free wifi hotspot!
Zoing!:victory:
Click to expand...
Click to collapse
That is one of the reasons that I am rooted... so I can use WiFi Tether. I do not it much. Hardly any data at all. But when I am in a spot and need a wireless connection and I only have my phone it comes in handy.
Some other reasons:
- DroidWall: Lets me block individual apps from accessing the internet.
- AddFree: Block ads in some apps.
why would you do that?
Xontic said:
This might be a foolish question, but why root your phone to leave it as is?
Click to expand...
Click to collapse
so you don't have to pay Sprint 12 dollars a month to teather.
Don't want the OTA right now?
Tired of deferring the update?
How can you stop it or get rid of it before or after it downloads to the device?
Answer:
M7vzw OTA Killer - Flash in Recovery
Enjoy! :good:
santod040 said:
Don't want the OTA right now?
Tired of deferring the update?
How can you stop it or get rid of it before or after it downloads to the device?
Answer:
M7vzw OTA Killer - Flash in Recovery
Enjoy! :good:
Click to expand...
Click to collapse
Awesome thanks! Is there a way to get OTAs back after flashing this? Just curious.
Cares said:
Awesome thanks! Is there a way to get OTAs back after flashing this? Just curious.
Click to expand...
Click to collapse
Flash my full odex stock rom...they won't apply to much else anyhow.
santod040 said:
Flash my full odex stock rom...they won't apply to much else anyhow.
Click to expand...
Click to collapse
I am going to flash this with Bonestock. Shouldn't be a problem right?
Cares said:
I am going to flash this with Bonestock. Shouldn't be a problem right?
Click to expand...
Click to collapse
You can flash this on any rom.
santod040 said:
Flash my full odex stock rom...they won't apply to much else anyhow.
Click to expand...
Click to collapse
which rom of yours is full odex stock?? i;d love to try it
sant0d, you are da best. Not that I need this, but you've done a lot to ontribute to this model phone. So thank you.
This work with your KitKat ROMs too?
I just went through and flashed your Odex Debloated KitKat ROM, and downloaded this to block the OTA from happening. However, I just noticed the last update of this is from December. Is it still OK to flash this on top of the KitKat ROM, or is that going to muck up things? (Or did you already "bake" it in by getting rid of some of the stuff in the debloat process?).
Thanks again!
Robert
Robertjm said:
I just went through and flashed your Odex Debloated KitKat ROM, and downloaded this to block the OTA from happening. However, I just noticed the last update of this is from December. Is it still OK to flash this on top of the KitKat ROM, or is that going to muck up things? (Or did you already "bake" it in by getting rid of some of the stuff in the debloat process?).
Thanks again!
Robert
Click to expand...
Click to collapse
It should still work fine on KK.
But the debloated rom already has the OTA stuff removed.
Look in Settings > see anywhere to even check for a software update? No you won't...
It's already been removed.
santod040 said:
It should still work fine on KK.
But the debloated rom already has the OTA stuff removed.
Look in Settings > see anywhere to even check for a software update? No you won't...
It's already been removed.
Click to expand...
Click to collapse
Thank you so much!!!!! Finally something that actually works to get rid of the OTA Thank you so much Santod045 you are the best!
Oh yeah. Will this still work with sense 6.0?
Sent from my HTC ONE.
onthehole said:
Oh yeah. Will this still work with sense 6.0?
Sent from my HTC ONE.
Click to expand...
Click to collapse
Yes, it should work just fine.
santod040 said:
Yes, it should work just fine.
Click to expand...
Click to collapse
It does indeed!
Thank you very Much :good:
Stock Un-Rooted HTC One..?
My husbands phone (which he refused to let me root when we had the chance, has been giving him a lot of grief with this latest OTA. It keeps downloading, attempting to install, and there errors 410 update failed, and exits software update. When I checked his phone after the latest attempt by the phone to install 4.4.3 to see if the download was still ON his device, it had disappeared with the failure of the update.
My question is, he's just sick of getting the prompt, error, and reboot - as a temp fix, can I push this OTA Killer onto his phone even though it isn't rooted and have it work, or do I need to find a signed RUU of the 4.4.3 and flash in bootloader (as I was originally planning on doing, but came across this...)
Thanks in advance!!!
xenacick said:
My husbands phone (which he refused to let me root when we had the chance, has been giving him a lot of grief with this latest OTA. It keeps downloading, attempting to install, and there errors 410 update failed, and exits software update. When I checked his phone after the latest attempt by the phone to install 4.4.3 to see if the download was still ON his device, it had disappeared with the failure of the update.
My question is, he's just sick of getting the prompt, error, and reboot - as a temp fix, can I push this OTA Killer onto his phone even though it isn't rooted and have it work, or do I need to find a signed RUU of the 4.4.3 and flash in bootloader (as I was originally planning on doing, but came across this...)
Thanks in advance!!!
Click to expand...
Click to collapse
If he has a custom recovery installed, then it will work. Have you tried downloading the OTAzip to his SD card and running the ota directly from stock recovery?
Get into recovery, select install update from SD, select OTAzip.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
If he has a custom recovery installed, then it will work. Have you tried downloading the OTAzip to his SD card and running the ota directly from stock recovery?
Get into recovery, select install update from SD, select OTAzip.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
NO, no custom recovery installed, everything is 100% stock. He spent a good part of 3 hours with tech support with Verizon and HTC and they were both dumbfounded....go figure!
Problem is because it's a virtual SD, I have no way of verifying (without root) that it's even downloaded to the virtual one on the M7. Would it hurt anything to take a shot at it from stock recovery.....?
Or is there a link someone could suggest to a download to the OTApkg file?
xenacick said:
NO, no custom recovery installed, everything is 100% stock. He spent a good part of 3 hours with tech support with Verizon and HTC and they were both dumbfounded....go figure!
Problem is because it's a virtual SD, I have no way of verifying (without root) that it's even downloaded to the virtual one on the M7. Would it hurt anything to take a shot at it from stock recovery.....?
Or is there a link someone could suggest to a download to the OTApkg file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55244412
@dottat uploaded it to his android file host account.
Sent from my HTC6500LVWBLU using XDA Free mobile app
would this help my problem??
I recently read a post, I don't know where now, but it had to do with a hidden Trojan/malware. That was started in 2013... After reading, thinking back to when this really started affecting me Feb,26, 2015. I noticed some strange things mentioned in my service log from around that date. The post mentioned how it places a high tracker in some obscure app. Unfortunately I got the bug, BAD!!! So not knowing about this until I made it worse by plugging my phone into my computer... I'm sure you can figure out the rest. My everything is screwed now. My HTC one m7, is the only device I can use period, now. I tried to root, and couldn't. Then downloaded another root checker, and it said my device was already rooted. Is there anything I can do(on my knees begging). This has to be the worst inter-web experience ever. Any and all ideas, advice, similar problems, links, and time are greatly appreciated. Thank you
Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0
thadeus_d3 said:
Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0
Click to expand...
Click to collapse
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I'll give this a shot tonight!
I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?
Coop1979 said:
I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?
Click to expand...
Click to collapse
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk
secret.animal said:
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for that suggestion. I was able to use Download Mode to fix my G2 and then OTA the KitKat update. Your post saved my phone.
Sent from my Nexus 7 using Tapatalk
I must have gotten lucky...wasn't thinking and took the OTA a while ago. Lost root but phone is fine.
Now...I'm off to find it again so I can get tether working
thadeus_d3 said:
Thank you for the reply. I'll give this a shot tonight!
Click to expand...
Click to collapse
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed
esoh said:
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed
Click to expand...
Click to collapse
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.
thadeus_d3 said:
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.
Click to expand...
Click to collapse
I'm the same way, but I figured that I should just go ahead.
So I'll throw that out, anyone pick one of these methods have a preference? I'm on TWRP, rooted, stock ZVA. Some mods including tether and camera. Thanks.
I am sure you will soon begin seeing some Custom ROM's based on today's GPE 5.0 release. In the meantime here is a method to start enjoying 100% Stock GPE 5.0 now!
Instructions:
1. I recommend that you use the latest TWRP v2.8.4.0.
2. Perform and Advanced Wipe and wipe "Dalvick Cache", "System", "Data", and "Cache."
3. Flash the I9505GUEUDNL3_100%_Stock_Rooted_ROM.zip
4. Last, press "Home" then press "Reboot," reboot into "Download Mode" and flash the M919_NK2_Stock_Modem+Bootloader.tar.md5 in Odin's PDA slot(AP in Odin v.3.09+). Done!
Tip: For blazing fast speed turn off animations from developer options and reboot.
Notes:
1. 5.0 seems to require the 4.4.4 modem/non-hlos otherwise security settings will force close. Therefore as of 12/14 the above process will also update your modem/non-hlos + bootloader to NK2(4.4.4) in order to ensure a consistent user experience.
2. The NK2 modem may not stick on your first attempt when flashing the modem + bootloader file in Odin. Should that happen re-flash the file until it sticks.
Alternative Odin Method:
1. Extract the I9505G_UDNL3_GPE_5.0_for_M919.tar and flash in Odin's PDA slot(AP in Odin v3.09+).
2. Power down and boot into stock recovery and perform a factory data reset. Done!
Notes:
1. This is a pre-rooted "All-in-One" Odin package which will update your System and Kernel to 100% stock GPE 5.0 and your Modem, Non-hlos, Recovery, and Bootloader to NK2.
2. The NK2 modem may not stick on the first attempt causing security settings to force close. If that happens flash the M919_NK2_Stock_Modem+Bootloader.tar.md5 until it sticks.
XDA:DevDB Information
[How-To] Update to Official GPE Android 5.0 UDNL3 (12-12-2014), ROM for the T-Mobile Samsung Galaxy S 4
Contributors
muniz_ri
ROM OS Version: GPE 5.0
Version Information
Status: Stable
Created 2014-12-12
Last Updated 2014-12-29
reserved
reserved
does this have the knox and all that nonsense with the voided warranty stuff?
just wondering.
buntobo said:
does this have the knox and all that nonsense with the voided warranty stuff?
just wondering.
Click to expand...
Click to collapse
Are you referring to data drops without a knox bootloader? I'm assuming that will likely be an issue with this ROM but I'm on a knox BL and have not experienced any issues. As for warranty my warranty was void a long time ago so don't know. Others will have to chime in on that.
buntobo said:
does this have the knox and all that nonsense with the voided warranty stuff?
just wondering.
Click to expand...
Click to collapse
Knox is dependent on which Android version of TouchWiz you're running. It is on 4.3 and 4.4.2. If you are on TouchWiz 4.2.2, you can flash this rom without dealing with any of the Knox warranty crap at all.
EDIT: So far it works, but I get a FC on Settings everytime I access Security. If I remember correctly, it can be fixed if keystore.msm8960.so is deleted in /system/lib/hw
Vigz said:
Knox is dependent on which Android version of TouchWiz you're running. It is on 4.3 and 4.4.2. If you are on TouchWiz 4.2.2, you can flash this rom without dealing with any of the Knox warranty crap at all.
EDIT: So far it works, but I get a FC on Settings everytime I access Security. If I remember correctly, it can be fixed if keystore.msm8960.so is deleted in /system/lib/hw
Click to expand...
Click to collapse
Yes, deleting the keystore file solves that issue. I will upload a new version of the ROM without that file. Thanks for the heads-up!
Baseband?
I9505GUEUCNE3... does this have a baseband/modem update as well?
zavien3 said:
I9505GUEUCNE3... does this have a baseband/modem update as well?
Click to expand...
Click to collapse
No, the ROM only flashes system and kernel. I have not tested the NE3 modem on our device but the NB4 modem and non-hlos work just fine with this ROM.
This is a great Rom. I've been using it for a 2 days now and have 0 problems. why not move it to S4 Android Development?
youngwake said:
This is a great Rom. I've been using it for a 2 days now and have 0 problems. why not move it to S4 Android Development?
Click to expand...
Click to collapse
Thanks, glad to hear it's working well.
And since I kept it completely stock I'm not sure it meets the criteria to be in the development section. Anyway I put it together for my own use and just put it out there in case anyone wanted to try it out. Enjoy
muniz_ri said:
Thanks, glad to hear it's working well.
And since I kept it completely stock I'm not sure it meets the criteria to be in the development section. Anyway I put it together for my own use and just put it out there in case anyone wanted to try it out. Enjoy
Click to expand...
Click to collapse
Works great. I personally think people would enjoy this awesome rom. But hey I totally understand what you mean. I am glad I found it...3 days running..zero issues :good:
Great ROM, no problems, thanks for posting!
Sent from my 919 using XDA Free mobile app
I enjoy this ROM. everything running smoothly, I'm using art, too. No glitches at all. Thanks for posting.
Sent from my GT-I9505G using Tapatalk
Is there a way to add the navigation bar to this ROM?
Sent from my T 919 using XDA Free mobile app
CompConfig said:
Is there a way to add the navigation bar to this ROM?
Sent from my T 919 using XDA Free mobile app
Click to expand...
Click to collapse
You can do it with xposed module "Gravity box"
Sent from my GT-I9505G using XDA Free mobile app
Can Viper be used on this ROM?
Sent from my GT-I9505G using Tapatalk
dawgdoc96 said:
Can Viper be used on this ROM?
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Yes it does work...
muniz_ri said:
Thanks, glad to hear it's working well.
And since I kept it completely stock I'm not sure it meets the criteria to be in the development section. Anyway I put it together for my own use and just put it out there in case anyone wanted to try it out. Enjoy
Click to expand...
Click to collapse
are you going to do a 4.4.4? I've been checking to see if you updated. anyways, just wondering
youngwake said:
are you going to do a 4.4.4? I've been checking to see if you updated. anyways, just wondering
Click to expand...
Click to collapse
Lol, good timing......uploading now.
ok, i am running Lollipop 5.0.1 on SM-N910P, my question is if i go and get the current rooted .img and flash it using ODIN, would it trip my knox? sence it would be a stock Kernel. i have Tried KingoRoot, Pingpong root, Towelroot, Activeroot, SuperRoot, king-root. i am having such a hard time with this, only had the phone sence February and i dont want to trip knox.
or would it be possible to install a modified signature .ZIP of superuser and install it on normal recovery? thanks
Knox II will trip with any root method; none known that won't trip Knox for Note 4.
CF Auto Root will work in Odin for your OE1 build but you're limited to CM12 or Noterized Stable for custom ROMs; the others won't boot and full Odin stock tars won't work and there's no OE1 tar either. This is not a standard Sprint OTA; I don't think a OE1 tar will be released; it's long overdue.
If you're still interested, there's a request for stock OE1 recovery; it needs to be backed up and shared in order to help some other rooted OE1 users to take the next OTA to 5.1.1 whenever that releases. Without it, you would be waiting on a tar as well; stuck. To get the recovery backed up, root in Odin (root only), download Flashify in Google Play and backup the stock recovery before you upgrade to TWRP. Share that gem with others that need it. Here: http://forum.xda-developers.com/showthread.php?p=61456449
Still with me? Next you would need TWRP to backup your stock rooted OE1 for a backup if some flash or mod goes awry.
Finally, you could modify the stock Rom or flash Noterized and back it up as well. Keep all these recommended backups in a safe place like on your sdcard and duplicates on PC hard drive.
Read, be careful and ask the questions when you don't understand and you'll avoid the problems others have unexpectedly ran into or got stuck with. OE1 is basically a broken update that shouldn't have got pushed.
Sent from my SM-N910P using Tapatalk
eankk said:
ok, i am running Lollipop 5.0.1 on SM-N910P, my question is if i go and get the current rooted .img and flash it using ODIN, would it trip my knox? sence it would be a stock Kernel. i have Tried KingoRoot, Pingpong root, Towelroot, Activeroot, SuperRoot, king-root. i am having such a hard time with this, only had the phone sence February and i dont want to trip knox.
or would it be possible to install a modified signature .ZIP of superuser and install it on normal recovery? thanks
Click to expand...
Click to collapse
I don't think so without root access
Sent from my SM-N910P using XDA Premium HD app
---------- Post added at 05:57 AM ---------- Previous post was at 05:56 AM ----------
There is no oel stock recovery no one has it
Sent from my SM-N910P using XDA Premium HD app
Yeah I only want root for the WiFi tether for root and sound boost, o well I will just stick with PDAnet. I was hoping there was something out there. But I am familiar with rooting very well, this is the 1st time that I am stumped and getting frustrated with it. But at least I asked though
eankk said:
Yeah I only want root for the WiFi tether for root and sound boost, o well I will just stick with PDAnet. I was hoping there was something out there. But I am familiar with rooting very well, this is the 1st time that I am stumped and getting frustrated with it. But at least I asked though
Click to expand...
Click to collapse
It's still just as simple; just fewer choices with OE1. Some have said Bluetooth is broken in some applications of its purpose, IDK for sure.
I made the request for the stock recovery which would add an extra step if you chose to help.
If Knox trip is a concern, sorry to be the bearer of bad news. Just to clarify...
I could post some links if that helps? Want them posted?
Sent from my SM-N910P using Tapatalk
samep said:
It's still just as simple; just fewer choices with OE1. Some have said Bluetooth is broken in some applications of its purpose, IDK for sure.
I made the request for the stock recovery which would add an extra step if you chose to help.
If Knox trip is a concern, sorry to be the bearer of bad news. Just to clarify...
I could post some links if that helps? Want them posted?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I will help, but I don't know coding or any development things, yeah knox trip is a big concern, (when I had my s4 I rooted and tripped knox, the SIM card error poped up and sprint said sorry we can't do anything Warrinty is void, only had it 9 months).... yes Pease
eankk said:
I will help, but I don't know coding or any development things, yeah knox trip is a big concern, (when I had my s4 I rooted and tripped knox, the SIM card error poped up and sprint said sorry we can't do anything Warrinty is void, only had it 9 months).... yes Pease
Click to expand...
Click to collapse
Did it still have custom recovery or root or mods installed when warranty was denied? Backing up these may help, if needed. Can't guarantee that but I'd try another service facility if turned down initially. Just tell them we never had this conversation. Lately, I'm hearing Sprint is cracking down on root. I've had conversations with tech and admitted I root as a right. It's not illegal but warranty is becoming another subject.
I'll post the links here shortly if someone doesn't beat me to it.
Sent from my SM-N910P using Tapatalk
samep said:
Did it still have custom recovery or root or mods installed when warranty was denied? Backing up these may help, if needed. Can't guarantee that but I'd try another service facility if turned down initially. Just tell them we never had this conversation. Lately, I'm hearing Sprint is cracking down on root. I've had conversations with tech and admitted I root as a right. It's not illegal but warranty is becoming another subject.
I'll post the links here shortly if someone doesn't beat me to it.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Nope everytime I took it to a sprint store I flashed it back to complete stock and made sure that the newest version of Android was on it. He is like your knox sensor is tripped. Then I said. "I messed up my phone bad and had to flash stock firmware back on it (when I got the note 4, the chick who sold it to me used to work for Samsung and we where talking about rooting, and then I asked about the sensor if it can be reversed she said, once it is tripped not even samsung can fix it) and damn I did not know sprint was cracking down on root. That's crappy
Links and steps to root OE1, backing up stock recovery
CF Auto root Download SM-N910P; follow OP for instructions. (Use Odin)
Flashify use to backup stock recovery. (Share using link in post 2 above; thanks in advance.)
Use Flashify app to get TWRP recovery (select latest tar, not zip; Odin tar is optional and TWRP Manager is optional: ) You'll need to make a stock nandroid backup once you have custom recovery.
Noterized stable 2 follow OP for install instructions; it will flash over OE1. (If so inclined to stay with TouchWiz custom ROM) TWRP/nandroid backup again; label these backups and keep safe.
samep said:
CF Auto root Download SM-N910P; follow OP for instructions. (Use Odin)
Flashify use to backup stock recovery. (Share using link in post 2 above; thanks in advance.)
Use Flashify app to get TWRP recovery (select latest tar, not zip; Odin tar is optional and TWRP Manager is optional: ) You'll need to make a stock nandroid backup once you have custom recovery.
Noterized stable 2 follow OP for install instructions; it will flash over OE1. (If so inclined to stay with TouchWiz custom ROM) TWRP/nandroid backup again; label these backups and keep safe.
Click to expand...
Click to collapse
^^ Sticky this beautiful answer to the ever lasting-never ending redundant OE1 question. Eventually we'll need some thread pruning.
So I understand.
Samsung is the one who would release the tar right and you are saying they have not released it because it is buggy?
Mship said:
So I understand.
Samsung is the one who would release the tar right and you are saying they have not released it because it is buggy?
Click to expand...
Click to collapse
Consider the facts as we know them. Sprint shouldn't have released it; it's the ugly duckling of a long string of unlocked bootloaders for dancing phones on Sprint. There's a new OS lock intended to protect the owner of a lost phone from easily being written over to bypass a screen lock with a battery pull and Odin tar. But there should also be a user switch to momentary bypass this so Odin wouldn't have been totally broken to rightful owner. Maybe Samsung didn't intend for that to happen and Sprint didn't know better? But since as some have reported that Bluetooth is not fully functional; Sprint should have caught that. I'd say they both collectively hold the blame since it wasn't immediately addressed. I'd blame Sprint more for not halting the update, infecting more users. Hopefully, they're trying to fix that. Maybe they were but decided to work on 5.1.1 update instead?
If it walks like a duck, quacks like a duck...; it must be a duck. It sounds odd to many here, from what I've read. But this is an ugly one. They both should own it, admit it, fix with an immediate update and move on. Until then, make the most of it; apparently, you can't expect a fix by taking it back to Sprint and some warranty replacements had the update pre-installed or quickly updated. Just plain wrong; a definition of insanity.
Maybe mostly opinionated but specifically, are there exceptions to the above for those that got OE1? I think there were some that said the only drawback is not being able to downgrade or recover a soft bricked phone. I could be wrong but just impressed by those OE1 users that have commented.
Edit: short answer is yes because users could update in KIES and that would make Samsung directly to blame for those users. Silence seems to indicate the bugs exist. And may signal a user need to wait for tars to be released which indicates Samsung deems the release as stable.
Sent from my SM-N910P using Tapatalk
Update
So I just got a new update, does anyone know anything about it?