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!
Related
Please forgive me if my questions have been answered many times but I really don't know what to look for in the search menu to address my questions.
1. I have rooted my phone and installed Liquid smooth but I went back to stock (still on 4.1.2 TW) and would like to update to at least 4.3 or higher. One issue I'm having is that when the OTA comes through and I go to update it gives me an error. But even before that as I am rooted it boots into TeamWin and wants me to install from there. It has been a while since I've done anything with the boot loader and I'm afraid to install from there and/or if that is wise. (frankly I've forgotten how)
Honestly I just want a quick way to install the update to 4.3 or 4.4 or whatever the next OTA is so that I can move on. I really don't even want to mess with it much right now as my life is way to busy.
2. My search so far has shown me that others are having similar issues but they are saying that the ota update is messing up certain things with their rooted phones (haven't found the answers I'm searching for either). Should I wait on updating? If so, how do I get the ota to stop wanting me to update my phone?
Thank you for any help you can provide.
wouldn't you know, that as soon as I submit this post I find another thread dealing with the same thing... Sorry for the clutter.
Here is the thread I found http://forum.xda-developers.com/showthread.php?p=49249510
Sithlyone said:
Please forgive me if my questions have been answered many times but I really don't know what to look for in the search menu to address my questions.
1. I have rooted my phone and installed Liquid smooth but I went back to stock (still on 4.1.2 TW) and would like to update to at least 4.3 or higher. One issue I'm having is that when the OTA comes through and I go to update it gives me an error. But even before that as I am rooted it boots into TeamWin and wants me to install from there. It has been a while since I've done anything with the boot loader and I'm afraid to install from there and/or if that is wise. (frankly I've forgotten how)
Honestly I just want a quick way to install the update to 4.3 or 4.4 or whatever the next OTA is so that I can move on. I really don't even want to mess with it much right now as my life is way to busy.
2. My search so far has shown me that others are having similar issues but they are saying that the ota update is messing up certain things with their rooted phones (haven't found the answers I'm searching for either). Should I wait on updating? If so, how do I get the ota to stop wanting me to update my phone?
Thank you for any help you can provide.
Click to expand...
Click to collapse
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.
buhohitr said:
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.
Click to expand...
Click to collapse
Thanks so much, but now that I've put a little more research into this update I'm seeing that others are having issues with tethering and that would be a serious issue for me.
Also I used twrp to root my phone and did not use odin so I don't know how to flash with odin (or even have the files on my computer) is there a way to us twrp?
It looks like I will need to put a little more time into this than I wanted. Anyway, thanks for the help.
Sithlyone said:
Thanks so much, but now that I've put a little more research into this update I'm seeing that others are having issues with tethering and that would be a serious issue for me.
Also I used twrp to root my phone and did not use odin so I don't know how to flash with odin (or even have the files on my computer) is there a way to us twrp?
It looks like I will need to put a little more time into this than I wanted. Anyway, thanks for the help.
Click to expand...
Click to collapse
No issue with tethering for me, just root then install wifi tether router.
Hi all...
OK, so I've rooted and ROMed a few phones in the past, and I generally know what I'm doing. However, I think I may have gotten a little bit overconfident this time and not done enough research...
I had a friend give me one of these phones and I decided that before making it my daily driver, I was going to install CM11. The phone was given to me unrooted with the stock 4.3 ROM. So, I found a guide to root the 4.3 version of the phone w/o triggering the warranty killbit, and that all went well. Once rooted, I decided to use Clockwork ROM Manager to throw CM11 on it. I installed CM and, without giving it a second thought, told it to flash the latest CM recovery (apparently my root method had come with TWRP). When I rebooted, I expected to see the nice recovery screen I was used to, but instead I was informed that I needed to take my phone to the nearest Verizon store and have them restore it (no thanks). I can, however, still get in to the Odin downloader, but this is uncharted territory for me. Assuming everything is OK with my firmware, what is the best/fastest way to recover from this point? I think I understand how Odin works, but I don't know much about it. Can I use Odin to flash the latest TWRP and fix it that way? Would it be better to try and flash completely back to stock and start over? If I'm forced to use Odin anyway, can I just flash CM11 from there? I have no idea what to do...
I would greatly appreciate any guidance anyone of you ROM wizards is willing to part with...
Fix with this:
http://forum.xda-developers.com/showthread.php?t=2586319
Then read all of this, no AOSP on 4.3:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my HTC6525LVW using Tapatalk
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.
Guys, my son messed up and followed instructions off the Max "HighOnAndroid" at www.galaxynote5root.com
He flashed twrp 3.0.2-1
He followed step by step. After flashing twrp, he booted back into recovery and flashed
No-verify-opt-encrypt
And
Update-SuperSU-v2.46
When he booted it back up, its stuck on the sprint splash screen. It is specifically in the screen that says LTE Plus More spectrum better network.
After I got off from work, I came home to him crying.
Ok, I have started to download the factory ROM from Sammobile but I am wondering if maybe there isnt an easier fix. I am not to familiar with changing kernels. Ive never needed to worry about them. Could I maybe just need to flash a new kernel?
From looking on here, really all he needed to do was flash twrp then SuperSU... Does anyone know a way to fix this faster than waiting 6 hours for the Sammobile stock rom?
Please help
Edit....
Ok guys...
I got the file downloaded from sammobile. I installed it and got it installed and working. Then I tried to do the root myself. I followed the guide on this site. However I still couldn't get it working. It was still bootlooping. But not the same bootloop. This time around, it didn't get past the very 1st screen. I again flashed back the stock ROM and again everything works fine.
The files I tried to install are:
Twrp-3.0.2-1nobleltespr.tar.md5
Then I did the twrp install boot deal, booted into twrp and installed:
BeastMode-Stock-N920P-1.3-O16.tar.md5
BETA-Flashable_SuperSU-2.52
I now take it that the issue is my twrp says noble while I read not to use the noble kernel to use BeastMode. But I could be way off...
Man alive, I didn't know just how much I appreciated CF Auto Root until just now...
You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions
tdunham said:
You probably already figured this out by now but follow the instructions and links in my thread. You should only reboot directly to twrp from download mode after flashing twrp btw in case you haven't figured it out by now.
The method you are using is from a very old thread. Follow the instructions in the thread below.
[How-to] Root your SM-N920P Device - all versions
Click to expand...
Click to collapse
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk
auburn2eugene said:
Thank you for responding. I was able to get the factory ROM installed and working fine.
I have downloaded the MOAR for the device and plan on giving it a go.
I still haven't been able to root the phone. EVERYTHING I tried resulted in bootloop. So I just decided to stick to stock on his phone until I can actually get it figured out...
As far as the SuperSu being old, I got it directly from the website of the maker. https://download.chainfire.eu/696/supersu/
I REALLY want to get this phone rooted for him, as I am certain he is going to keep trying following random YouTube videos regardless of my instruction.
Like I said in my last post, I have never missed cf auto root so badly...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.
tdunham said:
Root on stock is relatively simple.
TWRP + SuperSU only.
But as you saw, it's still easy to get it wrong.
Click to expand...
Click to collapse
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.
auburn2eugene said:
Ok, so since I have flashed TWRP and SuperSU, and all it ever does it bootloop, would I be able to install TWRP, then flash MOAR on top of it? Then I would have a rooted MOAR if I understand correctly. My issue is that ive always had root accomplished before installing a custom ROM.
If all I have to do is flash twrp then SuperSU, I dont understand what I could be doing wrong.
But I'm going to take a look at your link you provided and see if I can't get root 1st.
Click to expand...
Click to collapse
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.
tdunham said:
Old habits are hard to break. A properly deodexed rom that is pre-rooted only requires twrp and a proper wipe before installing.
For rooting stock, it really is fairly simple. The instructions I provided are probably a little overly detailed but I had to cover as much as possible for those that have never done it before so it 'looks' complex but once you've done it a few times you will see that its really not that hard to do.
Click to expand...
Click to collapse
Thank you for pointing me to your thread. I was able to get root on my sons phone. Hard to believe the SuperSU was the problem... But it was... I was using the one from chainfires site, but yours worked when his created bootloops.
Thanks again!
Is there a root method for pk1
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.