ok guys, I have successfully been able to root every device I have ever had thanks to the great work and directions of people on this site. Trust me when I say I have searched and searched for the answer to this and I can not find it.
I have a Note 10.1 2014 P605 international version. All I am trying to do is root this device. I would also like Kit Kat 4.2.2 however not required.
At this point, I am able to flash TWRP and can go back and forth from JB and KK, however I for the life of me can't flash any other thing on this device. I have tried multiple downloads of the CF Auto Root, but I get the same thing every time. I go into Odin, process starts, screen flashes, and than goes into boot loop, and stays there until i rerun Odin, and flash stock back on. I have tried to flash a custom reom on this device also but same thing.
I don't care about tripping the KNOX counter, i just want the device rooted, plane and simple. I am starting to think its not the file, but there is a block on the device somewhere and i have missed it. It seems to let me run any stock rom, just nothing else.
I have gotten Supersu but it stops when it gets to the last part and says that i just updated and need to bascly come here for help!
I'm kind of at a loss here. Not sure what to do next. Any ideas? or links that I have missed??
Afarrens said:
ok guys, I have successfully been able to root every device I have ever had thanks to the great work and directions of people on this site. Trust me when I say I have searched and searched for the answer to this and I can not find it.
I have a Note 10.1 2014 P605 international version. All I am trying to do is root this device. I would also like Kit Kat 4.2.2 however not required.
At this point, I am able to flash TWRP and can go back and forth from JB and KK, however I for the life of me can't flash any other thing on this device. I have tried multiple downloads of the CF Auto Root, but I get the same thing every time. I go into Odin, process starts, screen flashes, and than goes into boot loop, and stays there until i rerun Odin, and flash stock back on. I have tried to flash a custom reom on this device also but same thing.
I don't care about tripping the KNOX counter, i just want the device rooted, plane and simple. I am starting to think its not the file, but there is a block on the device somewhere and i have missed it. It seems to let me run any stock rom, just nothing else.
I have gotten Supersu but it stops when it gets to the last part and says that i just updated and need to bascly come here for help!
I'm kind of at a loss here. Not sure what to do next. Any ideas? or links that I have missed??
Click to expand...
Click to collapse
If you only want root, have you tried Towelroot? I was able to root my P605V when no other method worked. The only issue I have (since I have a locked bootloader) is that I can't update my SU binaries in the ROM or via recovery (since it's stock). You likely won't have that issue since you have custom recovery and can just flash.
ok- so after another night of sleep, i was able to get this done - here's what I did -
Reflashed stock rom via ODIN
Flashed TWRP via ODIN
installed SuperSU onto simcard, installed via TWRP
SuperSU opens and tries to shut down KNOX, stalls
I reboot, rerun SuperSU, and again tries to shut down KNOX, but this time it works
I reflash Kit Kat 4.2 and repeat the process and whoop there it is...root access with stock Kit Kat.
Finally!
Hope this helps someone!
adam
Related
So for anybody that needs help this will!! So I have the T mobile version M919. I did the OTA update not knowing myself it would lock the kernel. Which makes Mottochopper method not work. Soooo I spent a long time reading and found that this method does work with the ODIN flashing of TWRP.
Follow this."http://galaxys4root.com/galaxy-s4-root/how-to-root-galaxy-s4-using-twrp-method/" the only thing that this process doesn't tell you to do is to disable the auto reboot in ODIN on your computer. You need to do this cause if the phone just reboots after flashing TWRP it will over write the recovery.
You will need to do this "http://galaxys4root.com/galaxy-s4-root/t-mobile-uvuamdl-firmware-update-root-fix/"
Follow the tutorial to Step 9. Then do the following.
Turn the Auto Reboot option Off in ODIN, then Flash the TWRP recovery(Which is step 9 in the above method), then unplug the device, then take the battery out, put in back in, then Press Up + Home button + Power button till you see the Samsung logo with some blue script in the top left corner then let go. It should boot into the TWRP recovery. Then just locate the zip folder SetUIDRestrictRemovedKernel and install it. Once you do that then locate and flash the CWM-SuperSU-v0.99 . Once you do all that just reboot the phone. there you go.
Hit thanks if this helped in any manner
Yeah the battery-pull step with auto-reboot disabled was a key step for rooting the S3 as well. Maybe it became an "understood" step so people stopped emphasizing it. Who knows.
Chainfire's CF AutoRoot is a great alternative to this. Ridiculously easy, he uses Odin to inject a temporary custom recovery, flash root, and then rewrite the original recovery. In about 6 seconds.
Despite keeping the stock recovery, it will break OTA updates, since the device is recognized as modified.
Dr. Fed said:
Yeah the battery-pull step with auto-reboot disabled was a key step for rooting the S3 as well. Maybe it became an "understood" step so people stopped emphasizing it. Who knows.
Chainfire's CF AutoRoot is a great alternative to this. Ridiculously easy, he uses Odin to inject a temporary custom recovery, flash root, and then rewrite the original recovery. In about 6 seconds.
Despite keeping the stock recovery, it will break OTA updates, since the device is recognized as modified.
Click to expand...
Click to collapse
Okay Great. I just couldn't find a distinct method so I thought it best to post what i found to work.
As for the S3 i didn't have one. Thanks though I am sure your post will help as well
I was able to root my T-Mobile SGH-M919 phone with restricted kernel using TWRP without having to remove my battery or prevent Auto-Reboot. I used the website mentioned in the original post of this thread and at first I had trouble with the phone overwriting the custom recovery with stock recovery. I then read on another site that if you IMMEDIATELY start holding the Up Volume as soon as ODIN says the flash was successful and don't let go of the volume button until TWRP comes up then it will work. That worked for me.
Rooted OTA update
Dr. Fed said:
Yeah the battery-pull step with auto-reboot disabled was a key step for rooting the S3 as well. Maybe it became an "understood" step so people stopped emphasizing it. Who knows.
Chainfire's CF AutoRoot is a great alternative to this. Ridiculously easy, he uses Odin to inject a temporary custom recovery, flash root, and then rewrite the original recovery. In about 6 seconds.
Despite keeping the stock recovery, it will break OTA updates, since the device is recognized as modified.
Click to expand...
Click to collapse
Mine says the same thing that will not update due to Root, will our rooted phones update to 4.4 still come November 18, the official T-Mobile launch OTA update?
kapparosko said:
Mine says the same thing that will not update due to Root, will our rooted phones update to 4.4 still come November 18, the official T-Mobile launch OTA update?
Click to expand...
Click to collapse
4.3*
And, the answer is no.
The update will fail unless you're on stock firmware.
Hello there,
I've previously used Odin to install several versions on several phones, so at leas I know some very basics, like, using Odin and what not.
Here's my problem. I rooted my 4.3, it gave me some trouble, and the main reason I wanted it rooted was to get backups for my apps. Turns out I can back up my data with carbon "rooted-unrooted" so I decided to ditch the root since it was giving me some hassle with the security update thing and titanium was not working properly. "had to do some other stuff and I was kind of tired.
Turns out I tried to install my other official firmware I had "4.1". Sadly, upon using Odin with it, it now says that I'm trying to install an unsupported version and won't proceed... I'm stuck in here because I cannot restart by pressing up+power because it gives me an error and says I need to restart in download mode.
I was wondering if installing a fresh copy of 4.3 would fix this. Yet I've been unable to find any actual official files... yeah... I know this sounds pathetic, but... I've been herer for an hour + and have not found either a solution or the original 4.3 file or whichever file I would need for this.
Decided to turn unto this community which has helped me a lot in the past to solve all my previous issues.
So... How do I install a fresh 4.3 or how do I get out of this mess? My cell phone doesn't turn on, it just tells me the following:
Firmware Upgrade Encountered an issue. Please select recovery mode in Kies & try again.
I had 4.3 installed with all the security crap on it, so when I go to download mode and install 4.1, it says that the verison is unsopported...
Thank you all in advance.
Download Mr Robinson's 4.3 rooted ROM from here.
Flash it via ODIN and you should be good to go.
Your phone is already on 4.3 bootloader and it is not letting you downgrade to any version below it.
[Q] Problems w/ Root & Custom Recovery on LG LS980...and I only have Ubuntu access...
First off I'm running Ubuntu 14.04 and I'm probably not as tech savvy as I should be for someone running Ubuntu. I do not have access to a Windows computer. My gf has a Macbook Air but I know she's tired of me running my phone experiments on it. Here's the problem that I'm in. I have spent hours upon hours of research and made numerous attempts at this and I just can't figure it out. I have an LG LS980 and I'm running the ZVE update (phone already had ZVE on it when I bought it). I do not have root or CWM or TWRP. I have been trying to root, install CWM or TWRP and then switch to CM 11. I originally rooted my phone, then, because of an incessant error issue (it would pop up repeatedly every second making the phone unusable) I had to factory reset. Since that factory reset I have not been able to achieve root. I have tried everything (IOROOT, STUMP, TOWELROOT) nothing. Stump says that I'm rooted but SUPERSU says I have no binary. I figured I'd just go straight to a custom recovery and then flash a rom that is already rooted. However it appears that there is no TWRP or CWM for LG LS980 without root. I just can't figure out how to get root status back and how to install a custom recovery. I'm stuck and I need help. I've read about going back to a stock ZVC and starting all over again but I don't know how to do that. I appreciate any future help from you all.
Using LG Flash Tool, you can tot back to stock, and retry rooting. There are a couple of guides floating around here, I'd look for one of them and just follow it exactly to get root and TWRP set up, then you can try your hand at a custom ROM.
Edit- Not sure if LG Flash Tool works on Ubuntu. If it doesn't or you just want to play it safe, I'd borrow a friend's laptop to run it. It's pretty quick, like 5-10 mins if I remember correctly.
Yes I have read that but does anyone know how to do that on Ubuntu?
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
lsiravi said:
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Click to expand...
Click to collapse
lsiravi said:
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Click to expand...
Click to collapse
Nope! No go!!
Triangle away reset the counter.
The stock recovery works well. I was able to boot to recovery and wipe the data and all that.
Odin says "SW Revcheck Fail" when trying to download the stock rom.
I rebooted into Lollipop, downloaded Triangle away again and reset the counter. Still Odin fails with the same message.
I tried flashing ROM first then the recovery as it was suggested in that link. Nope. Again "SW Revcheck fail". For the record, my SWREV appears to be 3. It is supposed to be 0. Triangle Away does NOT reset this. It did reset another counter (as reported by Triangle away itself - was 5, got reset to 0).
I remember *this* was the problem previously as well, hence the original Q:
How *do* you get back to stock from Lollipop on the Galaxy S3/ATT?
Meanwhile, although Keis failed to recognize the device, I tried to run a firmware recovery manually. It took a long time and in the end failed. It also messed up the recovery, so I had to flash CW again to make it bootable. I'm still back up with Lollipop at this point, but I don't want Lollipop.
Anyone anything else I can do? Any other guide out there to downgrade?
Thanks again
L
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
audit13 said:
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
Click to expand...
Click to collapse
Right. I finally figured it out.
First the 4.1.1 FWs weren't flashing (in other words SW REV CHK FAIL) was basically indicating that my Bootloader was far ahead of the 4.1.1. I dropped 4.1 after I figured that part out.
Next, I tried to flash a 4.4 (UCUFNE-rooted-odex is available as a zip-flash) through CWR, which didn't work (no boot, stuck at splash).
Next I got hold of a 4.3 (UCUEMJB-2024954-REV04-user-low-ship), which successfully flashed through Odin (repartition checked), but there was no sound, IMEI indicated null. Service Mode yielded a blank screen.
I flashed TWRP through Odin (was working on CWR since the beginning) and then flashed the UCUFNE-rooted-odex above on top of 4.3 through TWRP, which was successful, still no sound/IMEI/service mode.
Finally I got hold of the UCUFNE-Modembaseband zip (a small one - 20MB) and flashed that through TWRP. Both sound and IMEI came back.
I'm at 4.4.2 now, but an OTA update from ATT failed (probably because it went through TWRP)
Now I'm back to stock, albeit rooted ROM (because of the Rooted-Odex 4.4 flash), but I am a happy camper.
Thanks to XDA for various bits of info here and there. But essentially *this* is how you go back to stock from Lollipop.
L