Sorry for posting this, I hate starting new threads but I have come to a point where I have had no luck. I havnt rooted for a few years, last time I did was my S2 (Epic 4g Touch 2). My terminology might be off a bit I apologize in advance.
So a couple days ago I decided to root my S5. I was at NK4 stock and never rooted. So I attempted to flash to the NE5 so I could do the towelroot. That worked where I was able to get root and I got all those weird fail messages but I got root access. Then when I tried to go back to Nk4, I kept getting stuck on the boot screen when flashing back to NK4. My phone I would consider to be in a soft brick status but I was able to flash back to NE5 and atleast get to the previous step. Now I am unable to NE5. I try my phone on and it gets stuck on the yellow "Sprint Spark" screen. Somehow I did trip the knox counter, which I am not too concerned with if I am able to get my phone functional again.
Could someone guide in the right direction? Ask me some more questions and I will try to clarify. I am a little rusty when it comes to this stuff again but I have certainly studied everything before I tried attempting this. I used Odin3.09 to do everything.
EDIT: What can I do to start over?
Flash the full nk4 tarball in Odin
Since you did trip Knox you can use cf auto root to gain root
Or even better you can Odin the leaked 5.0 garwynn posted in Android Development. Which also can be rooted with cf auto root
elwood said:
Flash the full nk4 tarball
Click to expand...
Click to collapse
So the only thing I could get to work was flashing this:
http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-sm-g900p-ni3-modem-kernel-t2886483
This seems to have gotten my phone functional again. So currently I am unrooted at 4.4.2 NCB. What steps would you advise doing from here forward? I have already tripped knox.
I do appreciate all the work everyone puts in here and the support. Its great honestly.
Edit: --5.0 seems enticing
St Louie said:
So the only thing I could get to work was flashing this:
http://forum.xda-developers.com/sprint-galaxy-s5/development/rom-sm-g900p-ni3-modem-kernel-t2886483
This seems to have gotten my phone functional again. So currently I am unrooted at 4.4.2 NCB. What steps would you advise doing from here forward? I have already tripped knox.
I do appreciate all the work everyone puts in here and the support. Its great honestly.
Edit: --5.0 seems enticing
Click to expand...
Click to collapse
Since you did trip Knox you can use cf auto root to gain root
Or even better you can Odin the leaked 5.0 garwynn posted in Android Development. Which also can be rooted with cf auto root
Related
I have a brand new stock verizon S3 and am wondering if I can use the MrRobinson root method to root for the very first time. I swear someone in one of the forums said they did but it sounds like most people are using those images to just update. I originally tried this 4.1.1/4.1.2 method and it bricked my phone on flashing the VRALEC bootchain step, everything looked good in odin, the phone looked like it tried to restart, then went black and never came back. I got a new phone and am wary of trying the same method again. If that is the method I have to use any thoughts on what could have went wrong?
I appreciate any input.
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Ryno77 said:
There should be no problem using the Mr. Robinson file in Odin. I have flashed the bootchain that soft bricked your phone and had no issue. Your following the Odin instructions exactly, right....just checking. Everything needs to be installed using the PDA slot unless it specifically says to put the file somewhere else....I have not run into that yet. You had problems with Odin before so that makes me a little apprehensive advising you to use it again.
The Mr. Robinson 4.1.2 file is not the ota. Use the 4.1.1 ota file so you can grab the 4.1.2 ota. Before installing 4.1.2 ota install ota voodoo rootkeeper....temp unroot, take ota then reroot. Pretty sure that's the only way other than flashing the bootchain that will get you on stock rooted 4.1.2
Click to expand...
Click to collapse
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
idk why that happened. My best guess is if the battery was low prior to you using Odin then it may have needed charging. But that VRALEC/Odin method is proven working countless times and those files linked in the OP have been used countless times.
Just know that with mrRobinson's pre-rooted images, you'll still need to unlock your bootloader with say EZ Unlock v1.2 (available on Rootzwiki so google it) before you decide to flash custom roms/kernels.
Ryno77 said:
I would be scared to use Odin if I had your experience too. I've used Odin several times without any issue but I have not used it since the 4.1.2 update....although I'm sure many have without any problems. Yes, you can flash any OTA via Odin even if your going backwards . I can't say you won't have any issues because I don't think you should have had an issue the first time.......maybe wait to see what others think?
Click to expand...
Click to collapse
Like I said above, may have been the luck of the draw or it could have needed charging.
Clyde Tacoma said:
I actually had the video demo they have linked open and was watching that then pausing and following the directions and making sure everything I was doing was identical. I really have no idea what happened, I've read over the directions a few times watched the video again and I can't see anything I may have missed. But it hard bricked my phone, I couldn't turn it on or get back into download mode or anything.
If I can just use the MrRobinson method on a brand new unrooted phone I will do that. I think the phone was already on 4.1.2 when I got it, so that won't matter using the 4.1.1 ota file? I've been flashing roms and toying around with my Incredible 2 since the day I got it basically and have never had any problems. Now that I had this issue with the S3 i'm scared to try anything . It seems the S3 has a good community though which is the main reason I went with it over my other options.
Click to expand...
Click to collapse
If you want to have a 4.1.2 rooted stock version, you need to download MrRobinson, K3 full wipe image with root (http://www.androidfilehost.com/?fid=9390214368362234355), unzip it first, then use Odin to flash this, then install Voodoo OTA root keeper from the market to preserve root, then let OTA update back to 4.1.2, finally use OTA root keeper to restore root. Done, simple and risk free.
You guys rock thank you!
As a followup for anyone that may stumble upon this thread in the future, I used the method provided by buhohitor and it worked like a champ. I flashed the mrRobinson image used ez unlocker to unlock the bootloader then used ez recovery to flash the latest version of TWRP. I'm now running this Paranoid Android 4.2.2 Rom and it is fantastic!
I sold my p905 a while back, going to get a p900 however, the biggest factor is able to delete files on the sd card. I know I have to root it, however, from what I read there's issues and you can no longer root it?.
rirawin said:
I sold my p905 a while back, going to get a p900 however, the biggest factor is able to delete files on the sd card. I know I have to root it, however, from what I read there's issues and you can no longer root it?.
Click to expand...
Click to collapse
Use Odin to Flash TWRP then use TWRP to Flash Super SU.
nrage23 said:
Use Odin to Flash TWRP then use TWRP to Flash Super SU.
Click to expand...
Click to collapse
Thanks, so no issues with rooting with latest firmware?.
http://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
This guide?, been ages since I rooted.
rirawin said:
http://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
This guide?, been ages since I rooted.
Click to expand...
Click to collapse
I love how that guide says all variants and then makes no mention of the P907. I would love to be able to use a custom recovery. Unless the P907 falls under the LTE moniker even though the model number is different?
Yes, TWRP works with P900
I went through this a week ago (with some help) and once I figured out how to get TWRP 2.8 to flash using Odin the process of rooting and installing a custom rom was easy. There is a thread a little lower on this forum that goes through the process.
Keith
do you have the link please.
What happens if I wish to unroot?
rirawin said:
do you have the link please.
What happens if I wish to unroot?
Click to expand...
Click to collapse
I can't post a link but the thread is in this forum. I have not unrooted but there are several threads that mention going back to stock.
Please can someone link me to an up to date method to root?
I understand towelroot only works for p905 and p900/
okay
rirawin said:
Please can someone link me to an up to date method to root?
I understand towelroot only works for p905 and p900/
Click to expand...
Click to collapse
I do not have enough posts to link an email. About three weeks ago I had the same question. The thread is in this forum on page 3, 5 or so messages down. I am the op, stedmakr. Gastrom answered the thread, provided a link and helped me root the p900 and install his rom (its excellent). Sorry I can't post links. Page 3 of this forum.
Keith
http://forum.xda-developers.com/gal...reliable-root-method-p900-build-bnk1-t2986600
I still don't quite understand, I just like to root to get sd card fix
Since there's this thread... How about KNOX? Is there a way to root P900 without tripping KNOX flag? I don't care about KNOX software itself, but since here in Poland warranty problems are left to the decision of the service, it is quite important for me not to give them opportunity to refuse a repair (if something happens, which - I hope - never will).
Wytaptalkowane na notatniku
Peri Noid said:
Since there's this thread... How about KNOX? Is there a way to root P900 without tripping KNOX flag? I don't care about KNOX software itself, but since here in Poland warranty problems are left to the decision of the service, it is quite important for me not to give them opportunity to refuse a repair (if something happens, which - I hope - never will).
Wytaptalkowane na notatniku
Click to expand...
Click to collapse
Nope, no way to avoid Knox trip.
Sent from my SM-P900 using Tapatalk
can anyone confirm please, is this the method to root:
https://androidxda.net/root-samsung-galaxy-note-pro-12-2-all-variants-on-android-4-4-2-kitkat/
So after I done that, I update su user and then I install sdfix is that right?.
anyone please?
Are you having problems or just too afraid to try it?
Not sure if you realize this but one of the reasons people aren't answering you is because those of us who have rooted do so and never look back. I wish I could tell you for sure that it will work with the current version of the firmware but I cant . . I rooted 8 months ago and haven't looked back. I cant speak for others but I'm not about to flash stock and go through the whole thing again just to update an old thread so I suspect that this is part of the reason that there's no updated guide. For devices that get a ton of development things are different but this niche device doesn't have a flurry of development activity surrounding it so . . .
One thing I can say is that it is my experience that if CF Autoroot fails the worst thing you're left with is a tripped knox and the stock rom without root. I say this because I was one of the unlucky ones who had to struggle through multiple attempts to get CF Autoroot to work. Eventually it did but during that time I had multiple shots at it and each time I was able to at least recover to the point of getting stock OS and recovery working again.
I see no reason why you can't achieve root on a SM-P900. If you can't do it with CF Autoroot then just download one of Gatsrom's images of stock rooted, flash TWRP using Odin (with auto reboot option disabled), boot into TWRP and do a full wipe and flash Gatsrom's image. You'll lose your setup and apps but you'll get root.
muzzy996 said:
Are you having problems or just too afraid to try it?
Not sure if you realize this but one of the reasons people aren't answering you is because those of us who have rooted do so and never look back. I wish I could tell you for sure that it will work with the current version of the firmware but I cant . . I rooted 8 months ago and haven't looked back. I cant speak for others but I'm not about to flash stock and go through the whole thing again just to update an old thread so I suspect that this is part of the reason that there's no updated guide. For devices that get a ton of development things are different but this niche device doesn't have a flurry of development activity surrounding it so . . .
One thing I can say is that it is my experience that if CF Autoroot fails the worst thing you're left with is a tripped knox and the stock rom without root. I say this because I was one of the unlucky ones who had to struggle through multiple attempts to get CF Autoroot to work. Eventually it did but during that time I had multiple shots at it and each time I was able to at least recover to the point of getting stock OS and recovery working again.
I see no reason why you can't achieve root on a SM-P900. If you can't do it with CF Autoroot then just download one of Gatsrom's images of stock rooted, flash TWRP using Odin (with auto reboot option disabled), boot into TWRP and do a full wipe and flash Gatsrom's image. You'll lose your setup and apps but you'll get root.
Click to expand...
Click to collapse
Well said mate! Well said.
If someone's gonna root their tablet, especially one of this caliber & price point. Then they should know how to recover it back to stock on their own. Concerning the tripping of Knox, who cares! Samsung won't turn down a hardware issue covered under warranty just because you decided to load another ROM. That topic has been discussed to death in another thread. If your going to root this thing, then root it and live on! LoL ?
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Android.Ninja said:
Samsung won't turn down a hardware issue covered under warranty just because you decided to load another ROM.
Click to expand...
Click to collapse
Not here in Poland...
Hi,
About a year ago I got fed up with Verizon constantly messing with my rooted phone, which I was completely happy with as it was, with their OTA updates. I used some of the guides on here to stop the OTA's and after some trial and error finally got them to stop bugging me. The phone is running Kitkat 4.4.2.
Now a year later I bought a new car and in order for the phone to work with the car it needs to be running at least Lollipop 5.0 but I cannot get the phone to update. I know I used Titanium, the full version, to freeze some of the OTA entries and I tried unfreezing them to no effect. I know I used another program to freeze some of the OTa options but I do not remember what it was. I have also tried doing multiple factory resets and I have tried to update it using Kies. Nothing works. I also used Odin and flashed the stock 4.4.2. Had no effect.
Appreciate any help. I am not that tech savvy but I can usually follow instructions well if anyone can help me out.
Thank you.
If you used Odin to flash an image, whatever you did to freeze the OTA function was completely undone. That's clearly not your problem.
Just follow the instructions in this thread to flash the latest Lollipop image provided, and then root it. http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
painiac said:
If you used Odin to flash an image, whatever you did to freeze the OTA function was completely undone. That's clearly not your problem.
Just follow the instructions in this thread to flash the latest Lollipop image provided, and then root it. http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
Thanks for the reply.
First, I'd like to say that while I'm not new to this, I AM quite rusty. So before you call me retarded for doing what I did, I already know. Now...
I have been just daily driving along on 4.4.2 for a good few years on my phone but I just got a Tab4 and rooted it and noticed that the TWRP version I wound up with was newer than on my phone, and had a few more options. Sooo, I tried to Odin the TWRP to my phone and caused all kinds of problems. Wouldn't boot. So I downloaded everything I could get my hands on to try to Odin onto the G900V to get it up and running again. The ONLY this I could flash was this...
PD1_Full_Factory_Restore_No_Aboot.tar
So now the phone is on the 6.0.1 which I figured was great but quickly noticed that not everything was working. No WiFi, no Camera, no Back and Recent keys, and no extsdcard recognition, so obviously unacceptable. Is this too new to be undone? I spent all night last night and today reading through the various forums, and I haven't seen it directly addressed.
Here are my questions...
1. Can I root this and fix the issues from there? If so, with what tool?
2. If I cannot yet root this, how do I downgrade from this kernel/firmware to something that is at least stable for this device?
Point me in the right direction, I'm not a total newb. I've rooted many devices, many times, but I really haven't been keeping up on anything for some time. Any help would be awesome, I'll pour some beer out for you, Thx in advance.
~Chris
I tried all of these, none will flash via Odin but the one that got me to where I am (PD1)
mods, please delete this post #2.
I edited it all into #1
Odin back to stock
I did something similar, which is what I get for just reading the instructions instead of the warnings at the top of a post.
I tried a number of things, but ended up using odin to do a complete wipe and go back to stock.
Thanks for the reply.
AFAIK this IS a stock ROM, but as I said this was the only thing I could get to flash after I tried to flash a new TWRP. Nothing else will go.
Being a bit rusty myself, it caught my ear when you mentioned the full wipe, I never performed a wipe of any sort during my efforts.
Could that be the problem?
Also, someone please refresh my memory, what piece is it that actually determines whether a device is rootable?
Is it the kernel? Is this one rootable? What is the modern method for acquiring root? I was using towelroot back in the 4.4.2/4.4.4 days.
Thanks
UPDATE : It also will not make a phone call. Hitting the CALL button or trying to answer when it rings will cause the phone to reboot, lol
Someone please get me back to a custom recovery, I've got some great TWRP backups and a ****load of titaniumBU
Just downgrade to PB1 using the stock TAR and unlock your bl from there...
Thank you for the PB1 advice.
Should I be able to accomplish this via Odin?
Is a full wipe/reset required?
Thank you for the PB1 tip
Got that handled, all is up and running, but not rooted
Gunna have to wait till after work for that stuff
Thanks again
OK so now I'm fully stock PB1, where do I want to go from here to acquire root?
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
I ask because above I was advised to "downgrade to PB1 using the stock TAR and unlock your bl from there..."
My question arises from the fact that I had this phone rooted for YEARS before I messed it up, and the thread proclaiming that "S5 bootloader unlock is here!" seems to be only 3 months old. Leading me to wonder, do I need an unlocked bootloader, or merely to acquire root? Seems like a valid question to me. I just want to make sure in advance before proceeding.
SO in summary, this is the question...
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Also, what file system do I want for my SDcard?
Thank You
cjschriver3 said:
OK so now I'm fully stock PB1, where do I want to go from here to acquire root?
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
I ask because above I was advised to "downgrade to PB1 using the stock TAR and unlock your bl from there..."
My question arises from the fact that I had this phone rooted for YEARS before I messed it up, and the thread proclaiming that "S5 bootloader unlock is here!" seems to be only 3 months old. Leading me to wonder, do I need an unlocked bootloader, or merely to acquire root? Seems like a valid question to me. I just want to make sure in advance before proceeding.
SO in summary, this is the question...
Which of these 2 threads shall I follow?
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM], OR...
Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1] [3-3-16]
Also, what file system do I want for my SDcard?
Thank You
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=WS86FHqY6rE with appropriate files worked! Tremendous help for me.
Miilliiee said:
https://www.youtube.com/watch?v=WS86FHqY6rE with appropriate files worked! Tremendous help for me.
Click to expand...
Click to collapse
Thx for that. Being able to see the video helped a lot, not because I can't read, but just because I was able to see what was SUPPOSED to happen at each step.
All fixed up now. Thx again.
Can I still root the latest build number NRD90M.N920TUVU4EQG3 for the T-Mobile Note 5?
My overall goal in rooting is to revert back to MM. Honestly I hate Nougat and the battery life has dropped significantly so I'd like to flash a MM ROM. I'm sorry if this is in the wrong section or has been asked before. Just looking for some help. The research I did only showed how to root Nougat but didn't specify the particular build number. I forgot to ask also if Odin is the ONLY method I have to root? I've run into issues before with Odin. Just curious if there's another method for rooting.
tech15 said:
Can I still root the latest build number NRD90M.N920TUVU4EQG3 for the T-Mobile Note 5?
My overall goal in rooting is to revert back to MM. Honestly I hate Nougat and the battery life has dropped significantly so I'd like to flash a MM ROM. I'm sorry if this is in the wrong section or has been asked before. Just looking for some help. The research I did only showed how to root Nougat but didn't specify the particular build number. I forgot to ask also if Odin is the ONLY method I have to root? I've run into issues before with Odin. Just curious if there's another method for rooting.
Click to expand...
Click to collapse
You don't have to root to revert. What I did was put the phone into download mode and flashed the MM Rom from QC2, I believe, or whatever the version was from samfirm which is deprecated now. Just remember to have the OEM unlock enabled and USB debugging enabled in developer. You should be able to then use Odin to revert. If it doesn't work then you can try and root the phone using the root QE1 method from the posts in the T-Mobile note 5 thread and follow the guide. I can't say for certain if you can downgrade straight from an unrooted 7.0 rom to an earlier 6.0.1 MM rom in Odin. But what I do know is this. I came from the Khongloi v11 rom and decide to do something stupid.
"After unwittingly turning off OEM unlock and USB debugging and rebooting phone. I lost all my data. Stupid me. I got so used to quick rebooting and all of sudden decided to do a hard reboot, *sigh. Oh well, you live you learn. Just remember if you do root. Leave those options on. Never, ever, ever, ever disable OEM unlock. EVER."
Anyways, try downgrading in Odin 3.10.7 or if you have trouble with any newer Odin versions. If you have trouble with the newer versions, use an older version. If you can't downgrade directly from that rom, might have to try another way.
Thanks for the reply and advice! But just making sure though for general root purposes: I'm able to root the latest build number?
Try and see. I'm actually on the same firmware and haven't tried yet. I'm still considering if I should root again. I miss using game guardian, especially for LDoE: Survival.
I'd do it but I'm nervous I'm gonna mess up my phone. I was hoping someone will chime in and let me know it's good to go lol
No worries. You can't, because Odin will give you an error message if the firmware doesn't allow it. Kinda how it was in previous revisions. I've tried on purpose to brick my device. The only real way to brick a device is to do something super, super stupid. Try, the only thing that can result is you get an error in Odin and it fails.
The reason I say this is because I tried to use Odin to flash Nougat onto my Verizon S7 and I honestly don't know what the hell I did but it continually bootlooped to the point where I couldn't get it in recovery or anything. It was messed up. Had to send it in for another S7 which I sold and got a Note 5 lol. Needless to say I'm a bit nervous to use Odin.
tech15 said:
The reason I say this is because I tried to use Odin to flash Nougat onto my Verizon S7 and I honestly don't know what the hell I did but it continually bootlooped to the point where I couldn't get it in recovery or anything. It was messed up. Had to send it in for another S7 which I sold and got a Note 5 lol. Needless to say I'm a bit nervous to use Odin.
Click to expand...
Click to collapse
Honestly, bootloops can be fixed. Either thru the recovery or by download mode. It must have been something else you flashed. But if you decide to try and root and Odin doesn't take, then you haven't done anything to jeopardize your phone.