I've been poking around the forums trying to figure out an answer to this, but nothing so far has worked. My question is a simple one:
How do I root a stock ROM of Android 5.0?
First, the tech stuff:
Device: SM-N900A / AT&T
Android: build LRX21V.n900AUCUEOC1
I had Android 4.4.3 (rooted with Towelroot), which I was finally able to force to upgrade to 4.4.4 by using ODIN to flash a firmware update. In the process, root access disappeared, but my overriding concern was to get Android 5. I found a stock ROM of it here, which I downloaded and which did install perfectly.
Now, I've tried a bunch of different things to get it rooted--including trying to flash the pre-rooted Android that Walter.White posted in another thread (my phone kicks back an "invalid signature" error when I try, the install always fails and what I get is a device that's like it's fresh out of the box)--I also tried the CF-Auto-Root route, with ODIN says fails and which causes my phone to freeze. Towelroot doesn't work, and I can't get Safestrap to work either (it complains that there is no root access and there's no Safestrap option in the restart dialogue box).
I know that I'm missing something, and I know that it's probably something absurdly simple. I've got no doubt someone else has cracked this, any chance someone out there could help me figure out what I'm getting wrong?
You must go back to android 4.4.3 and root like you once did, then flash the pre-rooted version android 5.0 and you're all set. Sounds like you have everything you need, just need to do it in the right order.
I rooted my wife's N9008V which was running Android 5.0 with Kingoroot and afterwards removed Kingoroot with Super-Sume. After that I installed SuperSu.
I know that I'm missing something, and I know that it's probably something absurdly simple.
very simple .
Op you are in the wrong forum this is NOT Note 3 AT&T forum .
I rooted my note 3 by flashing TWRP through odin then flashing the SuperSU.Zip package through TWRP
The n900a can't be flashed with twrp if it has a locked bootloader.
Related
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
chokem said:
Hi guys. Not new to rooting but new to my AT&T S4. I rooted it tonight with Motochopper and installed CWM recovery. Downloaded and tried to flash a ROM, and it simply didn't work. Then I tried Beanstalk 4.2.2, and it downloads, but then when I rebooted it, it gave me the yellow triangle unauthorized software message. So I pulled the battery and finally got it to boot into recovery, then installed the back up I had from the stock OS. My question is two fold-what's causing this and if I download a ROM with the Loki patch, will that bypass the error message I'm getting. I searched the forums but am not understanding what was written. I'm pretty confused, any help would be greatly appreciated.
Click to expand...
Click to collapse
So, to sum up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Furies said:
So, to some up development in this forum for the last 3 months: The ATT version of the S4 has a locked bootloader, which is a fancy way of saying ATT and Samsung don't want custom software on their phone partitions. To keep people from installing custom ROMs, their bootloader requires a verified signature present in the ROM to actually allow the device to boot.
An individual found a way to trick this verification process, and created a patch for it called LOKI.
When a ROM is "Loki'd" it contains this workaround for the verification process in the bootloader, allowing custom software to be installed.
To answer your question, when you root your phone and install the recovery (TWRP or OUDHS): a ROM must be lokied to work. OUDHS recovery has a feature which automatically installs the workaround in every ROM you flash using the utility. I recommend this version of Clockwork Recovery.
The link is here:
http://forum.xda-developers.com/showthread.php?t=2291956
I personally use the nightly CyanogenMod 10.1 builds for the ATT S4 (called jlteatt). They're quick and stable except for a few quirks with the camera, call-audio via headsets, and bluetooth audio.
The link to download is here:
http://get.cm/?device=jflteatt
*This version of CM 10.1 is already Loki'd
Have fun flashing, and if all else fails and you accidentally run into a scenario where you can't boot your phone, use this utility to restore the factory OS that comes with the phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Click to expand...
Click to collapse
OK, thanks very much. So I was indeed on the right track. I'll try your ROM recommendation as well as the modified CWM recovery.
Just got my T-Mobile G2 a few days ago and have been looking around at the different ways of rooting it. I know the T-Mobile variant is harder to root and run a custom ROM on because IORoot doesn't work on the KitKat OTA, so I haven't updated it yet. Right now the phone is running the D80110C firmware.
What I'm asking for is a way of being able to get the phone to the point where I can flash any 4.4.2 ROM compatible with it (even if it needs patches). Looking at both dr87's guide and utesred's guide, I'm thinking I need to take the following steps:
1. Root the 4.2.2 D80110C firmware (currently on the phone) with IORoot.
2. Install latest version of TWRP. Need suggestions on how to do this.
3. Reboot into TWRP, wipe everything (minus internal storage), flash SmiLey497's 4.4.2 ROM and the SU file. I gotta do this all in one go or it will complicate things.
4. Reinstall TWRP using AutoRec.
5. Go on to flash something like CM11 or Mahdi-ROM.
Any help is greatly appreciated!
EDIT: Alright, I got it! Just followed my guide and the recovery install method suggested by XxZombiePikachu and everything worked great.
Can anyone assure me that this will work? Or even share a quick run down of what they did? Thanks!
NicoC72 said:
Just got my T-Mobile G2 a few days ago and have been looking around at the different ways of rooting it. I know the T-Mobile variant is harder to root and run a custom ROM on because IORoot doesn't work on the KitKat OTA, so I haven't updated it yet. Right now the phone is running the D80110C firmware.
What I'm asking for is a way of being able to get the phone to the point where I can flash any 4.4.2 ROM compatible with it (even if it needs patches). Looking at both dr87's guide and utesred's guide, I'm thinking I need to take the following steps:
1. Root the 4.2.2 D80110C firmware (currently on the phone) with IORoot.
2. Install latest version of TWRP. Need suggestions on how to do this.
3. Reboot into TWRP, wipe everything (minus internal storage), flash SmiLey497's 4.4.2 ROM and the SU file. I gotta do this all in one go or it will complicate things.
4. Reinstall TWRP using AutoRec.
5. Go on to flash something like CM11 or Mahdi-ROM.
Any help is greatly appreciated!
Click to expand...
Click to collapse
that is all correct also install recovery guide
Ok, everything's rooted and running just fine! Installed CM11 and the KitKat modem with rotation fix.
For anyone who finds this thread in the future, here's the zip of stuff you need to flash TWRP the first time, just make sure to pick up IORoot25 as well, since that's what I used to for the adb. Second time around (once you have the rooted KitKat LG ROM installed), use AutoRec. Here's a link to the KitKat modem you might need if you flash a ROM and auto rotate doesn't work.
I'm not responsible if you screw up your device. This all worked for me, so I'm just sharing the steps for prosperity. Make sure you ready all the threads and guides I linked or mentioned, use OEM cables, use a USB 2.0 port that is actually connected to the motherboard in your PC (not a hub, pass-through, or front case port), as well as being focused at the task at hand. Disabling your anti-virus might help too, used to have to do this when rooting older phones, so it might still be necessary.
If this does work, have fun with your newly rooted LG G2 D801! :good:
Hi everyone,
I have a Note 4 Exynos version and recently i decided to make the root procedure. My steps was first update to 5.1.1 then, root by flashing the su zip file, flashing TWRP recovery and then i did a full backup to make sure i can keep my files intact just in case. I tried installing CM 12.1 but i had the " Execute updating binary failed etc..." and after a lot of tries i decided to restore my backup. The problem is that after restoring my phone keeps rebooting in randomly.. Can i unroot without flashing stock firmware, so i can keep my backup as it is?
Any thoughts appreciated.
5.1.1 can't be root just yet.
Flash stock rom & setup your phone to fix it.
You can flash another rom after that
So that is the reason for the random rebooting? To be honest i followed the procedure from a known website that was talking about rooting this particular phone with version 5.1.1 ...
Thanks for the response
I'm expecting my 910c to arrive soon and I'm currently reading for root procedures.
So, if my phone arrives with 5.1.1, I won't be able to root? and if I root can I later flash 5.1.1 without problems?
Also, please direct me to a threat that is safe to follow in order to root.
Of course you can root 5.1.1
Just read the development section and follow the instructions there
sent from somewhere
Antreassy i have followed the procedure from a website i do not wish to quote since it might be against the forum rules. But the result was not the best since my phone keep rebooting. So the only thing that saved it is by flashing the stock 5.1.1 firmware using odin and everything came back to normal.
From my own research i believe that at the moment the most valuable custom firmware is CM 12.1 and that is the reason i tried to flash it at first but without any success.
I picked up a used GS4 JFLTECAN and the battery life on the stock rom is brutal, so I would really like to try something else. I have flashed recoveries kernals and roms before on other devices but have never had to deal with these "locked" boot loaders.
I have the I337mvlufnc1 bootloader and the most recent Android 5.0.1 OTA update from Rogers. My ROM and modem are I337MVLUGOH1
Can I ODIN TWRP at this point? Or will I brick my device?
Here's how I wound up at this point.
I have managed to root by odining SuperUserSU.zip by following these instructions; http://www.google.ca/url?sa=t&rct=j...4gA4TauS3dXnXcIOA&sig2=MHLMfY4z5M21bgTArDKniQ
I installed wakelock detector and a root uninstaller for bloatware as well as greenify to take advantage of root and try to fix battery drain issues. However I did something wrong and now whenever I boot "Package Access Helper" and "System UI" both unfortunately stop. I am also being prompted to select a homescreen every time I boot (touchwiz variants)
Rather than factory resetting to the stock firmware I would prefer to get on something different. any help is appreciated.
Paging @raptor170 ?
arasarn said:
I picked up a used GS4 JFLTECAN and the battery life on the stock rom is brutal, so I would really like to try something else. I have flashed recoveries kernals and roms before on other devices but have never had to deal with these "locked" boot loaders.
I have the I337mvlufnc1 bootloader and the most recent Android 5.0.1 OTA update from Rogers. My ROM and modem are I337MVLUGOH1
Can I ODIN TWRP at this point? Or will I brick my device?
Here's how I wound up at this point.
I have managed to root by odining SuperUserSU.zip by following these instructions; http://www.google.ca/url?sa=t&rct=j...4gA4TauS3dXnXcIOA&sig2=MHLMfY4z5M21bgTArDKniQ
I installed wakelock detector and a root uninstaller for bloatware as well as greenify to take advantage of root and try to fix battery drain issues. However I did something wrong and now whenever I boot "Package Access Helper" and "System UI" both unfortunately stop. I am also being prompted to select a homescreen every time I boot (touchwiz variants)
Rather than factory resetting to the stock firmware I would prefer to get on something different. any help is appreciated.
Paging @raptor170 ?
Click to expand...
Click to collapse
From my understanding with that bootloader is that it will prevent you from downgrading to say 4.3 etc etc. To be extra Safe, have stock firmware files from sammobile handy, but you should be good..... Don't quote me on it tho lol
He was successful on twrp flash, anyone watching this lol, all i337m unlocked
So If anyone else gets a used galaxy s4 here is the procedure to root and install custom recovery with the most recent OTA updates installed. There is no need to worry about any locked bootloader or anything.
Step 1: get root with Odin
http://www.google.ca/url?sa=t&rct=j&...5M21bgTArDKniQ
go to twrp.me
Step 2: flash twrp 2.8.4.0 with Odin
Step 3: flash twrp 2.8.7.0 (or a newer version if one is available) via twrp itself. After 2.8.4.0 TWRP only has .img files released which are to be flashed directly from twrp.
Step 4: Flash a rom.
arasarn said:
So If anyone else gets a used galaxy s4 here is the procedure to root and install custom recovery with the most recent OTA updates installed. There is no need to worry about any locked bootloader or anything.
Step 1: get root with Odin
http://www.google.ca/url?sa=t&rct=j&...5M21bgTArDKniQ
go to twrp.me
Step 2: flash twrp 2.8.4.0 with Odin
Step 3: flash twrp 2.8.7.0 (or a newer version if one is available) via twrp itself. After 2.8.4.0 TWRP only has .img files released which are to be flashed directly from twrp.
Step 4: Flash a rom.
Click to expand...
Click to collapse
Easiest waytp flash the ol s4 great writeup for anyone starting off on the s4. Let me add a step 3a: backup efs in twrp for if the rare case you loose imei, chance of getting it back
raptor170 said:
Easiest waytp flash the ol s4 great writeup for anyone starting off on the s4. Let me add a step 3a: backup efs in twrp for if the rare case you loose imei, chance of getting it back
Click to expand...
Click to collapse
Add this to the first post of the Canadian galaxy s4 mega thread.
I have a Tab E 8 (SM-T377P) and I cannot get any version of TWRP new than 2.8.7.0 to flash, Magisk will not flash, and no custom roms will install.
I've tried both lineage 15.1 and 16, both the standard and GO versions.
It's on stock firmware, 5.1
I rooted with cfautoroot with Odin 3.10.7.
Hopefully someone has an idea on what I need to do.
:edit:
I was able to get magisk installed by rerooting with cfautoroot and then doing a full unroot and restoring bootimage with supersu. Still can't install any roms though
So I was able to update to Nougat using the rom posted in this thread. It was the ONLY place I was able to find the stock firmware. I was hoping that installing 7.1.1 would put me on a new bootloader/kernel that might allow me to install an Oreo rom.
Still, the only TWRP that I can get to boot is the one posted in this thread, which is 2.8.7. The dev posted links to 3.0.2-1 that do not work, but I've tried multiple different versions of TWRP, and they all boot loop and I have to reinstall 2.8.7 via Odin.
All roms say that they are intended for SM-T377P and cancel, although my device is exactly that.
So, after doing a total wipe and flash back to stock 7.1.1 using Odin, I was able to boot back into Download mode and install the latest version of the TWRP posted in this thread - https://forum.xda-developers.com/ga...official-lineageos-16-0-galaxy-tab-e-t3847488
Still won't let me install a custom rom though...
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Krunk_Kracker said:
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Click to expand...
Click to collapse
Thank you for documenting your progress.
I am in a similar situation.
I am the original owner of my t377p.
I'm going to try your steps to see if it will work for me.
UPDATE:
Flashing back to Stock and starting the process all over again, as you described above--fixed the problem. I am now running LineageOS16.
Thank you!
I'm glad it worked for you!
That's exactly why I updated the thread, I knew I wouldn't be the last one have this odd issue.
Do you have a copy of twrp the servers are down and I've been trying for week to download it