Just thought id point it out if no one has posted yet, but in the link provided, chainfire has included root for nexus player (fugu) as well.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
obviously its a work in progress, but apparently doesnt require a custom kernel?
Finally got home and attempted to root, over and over again. Keep getting boot loop the moment I try to install supersu via twrp. Ugh.
Anyone else have any luck?
unvaluablespace said:
Finally got home and attempted to root, over and over again. Keep getting boot loop the moment I try to install supersu via twrp. Ugh.
Anyone else have any luck?
Click to expand...
Click to collapse
Same over here.
Boot loop here as well.
well then im sorry to have jumped the gun fellas. i was at work when i found chainfires root. Can anyone contact him to let him know root on nexus player doesnt seem to be working?
has anyone had success yet?
Chainfie Is The Best On The Planet
unvaluablespace said:
well then im sorry to have jumped the gun fellas. i was at work when i found chainfires root. Can anyone contact him to let him know root on nexus player doesnt seem to be working?
has anyone had success yet?
Click to expand...
Click to collapse
I experienced the very same thing as you guys. Chainfire is the best on the planet when it comes to rooting all Android devices. He will have this issue fixed fast.
I'm just going to wait on the Chainfire Nexus TV Player M6 root version, maybe Ethernet will work with his root.
Sorry guys, it seems I broke x86-32 support on KitKat+ in v2.50.
New v2.51 BETA posted here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
New Fugu boot.img posted here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Chainfire said:
Sorry guys, it seems I broke x86-32 support on KitKat+ in v2.50.
New v2.51 BETA posted here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
New Fugu boot.img posted here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
Thanks Chainfire for your fast response fixing the boot.img and giving us a new SuperUser v251 Beta.
Works Like A Charm With Ethernet Pass Through
The above new rooting files by Chainfire works like a charm with Ethernet pass through. Chainfire you are the man!
Ok guys, it's safe to go back into the water again! Again thanks a million Chainfire.
Chainfire said:
Sorry guys, it seems I broke x86-32 support on KitKat+ in v2.50.
New v2.51 BETA posted here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
New Fugu boot.img posted here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I will follow your suggestion and i will build a selinux enforced boot image for my next firmware full android 6 for Nexus Player.
I want know, if possible, apart security stuff, why you suggest to maintain the enforced mode.
Is just question of security, or you suggest the enforced mode also for others future problems that can happen to the firmware and apps.
In others words, in Android 6, Selinux in permissive mode can create problems to the normal execution of the android framework and Google stuff ?
p.s.
The new init of Android 6 don't permit Selinux Permissive for release firmwares ( not problem for user-debug and eng builds ) so to have a fast root i swapped the original init with TWRP init and repacked the boot.img
Just to have a simple root method, before your instruction on the selinux stuff and before a complete custom firmware.
Just a way to have root in the same moment that Google published the stock firmware. Nothing special.
For those that don't have an otg to connect a mouse or keyboard, I was able to flash the modified kernel via fastboot and the cm recovery used for cm 12.1. I saved SuperSU to my device and flashed the zip with cm recovery and gained root.
Sent from my Nexus 6 using Tapatalk
Worked perfectly for me. Thanks!
Sent from my XT1096 using Tapatalk
followed Chainfire's instruction. on his thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Flashed fugu-mra58k factory> load up and put beta-supersu-2.51.zip > bootloader > flash fugu-mra58k-boot.zip from CF> flash twrp > recovery > installed beta-supersu-2.51.zip > profit.
Much thanks to CF for his work.
No Binaries in SuperSu
I can't get the Binaries in SuperSU to install. Can someone point me in the right direction?
very helpful
payazo915 said:
For those that don't have an otg to connect a mouse or keyboard, I was able to flash the modified kernel via fastboot and the cm recovery used for cm 12.1. I saved SuperSU to my device and flashed the zip with cm recovery and gained root.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
thanks, after doing my research i found your post and now i have my new NP rooted and running Android M , Thanks as well to Chainfire for his Boot wich allow us to do this.
A lot of us got the 6.0 update forced on us and aren't happy with it. With root and custom recovery, we should be able to revert back to 5.1.1 and a lot of our issues would be resolved. I would love to implement this root method on my Nexus player, but the instructions are not put in a way that I can understand. Can anyone put this in easier terms and comment on a possible downgrade? I was wondering why a thread like this wasn't on the first page or sticky'd. Please help! Marshmallow on Nexus player is a pain without root and the Marshmallow update came only a few days after I got my Nexus player so I really want to get this thing back to the version it came from the store with it(when it worked perfectly and I could root it easier).
I'm having some trouble with gaining root for marshmallow ... I flashed the newest image for NP the MRA58N build and tried following chainfire method: flashed the modified boot, twrp recovery and finally latest su zip 2.56
No dice ... I then tried to flash MRA58K and follow same steps but again ... not able to get root
Any suggestion?
Sent from my 1+1 using Tapatalk
Related
Universal Android Root Guide 4.4.0+
No PC Required!
by Kwongger
BY PROCEEDING PAST THIS POINT YOU ACKNOWLEDGE THAT ALEX BECK (KWONGGER) IS NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY THE USER. USING ANY METHOD DESCRIBED IN THIS GUIDE IS AT YOUR OWN RISK. NO WARRANTY IS IMPLIED OR PROMISED.
ONLY FOR KITKAT - NO ANDROID L/5.0 SUPPORT
It is VERY unlikely that these tools could do anything harmful.
Confirmed Devices:
ATT/VZW GS5, GS4 Active, Nexus 5, ATT/VZW Note 3, Sprint HTC One Max, MadCatz Mojo*, NVIDIA SHIELD*, and NVIDIA SHIELD Tablet*
* Requires alternate app version (the guide will let you know)!
Requirements:
A FULLY-FUNCTIONAL Android device with Internet access.
Step 1:
1a.
Enable Unknown Source APK installs on your phone.
Click Settings, then Security, then “Unknown Sources”
1b.
Download TowelRoot, a kickass hack by GeoHot.
https://towelroot.com/
Click the big-ass Lambda to download the app.
Use THIS version for NVIDIA SHIELD/ SHIELD Tablet and MadCatz Mojo
1c.
Install TowelRoot.
Just tap on the finished download in your notifications bar, and install.
Step 2:
l337 HAXX0R SK1LLZ
Tap “make it ra1n”
If you device DOESN’T reboot, your fine. If it reboots, try THIS version of towelroot.
Step 3:
Root it up.
All that towelroot does is allow you to install/inject a Superuser application.
I’ll always use and recommend SuperSU. Install it now (from google play).
After it installs, open it and let the magic happen. Reboot when it tells you to.
Step 4:
This step is entirely optional. You don’t need to do this if you just want root.
Continue if you want to make full nandroid backups, or install custom
software to your device.
4a.
Download Flashify.
This is great stuff, it allows you to flash boot.img’s and recovery.img’s
without an unlocked bootloader!
4b.
Find and download a custom recovery for your device.
Custom recoveries such as, TWRP, CWM, and PhilZ, all need to be
built for a specific device. This means that you can’t just find one and
install it on just anything. You need to find one specifically for your device.
For this you need to head to google, so search in this format:
<device> <recovery> xda
I recommend that you use TWRP, it’s my personal preference, they are
all about the same though.
The “xda” is there so that you’ll be directed to the xda-developers forums. They
are THE SOURCE for anything regarding android mods.
4c.
Install that recovery!
Once you have downloaded the recovery file, open Flashify.
Tap on Recovery Image, tap on “Choose a File,” navigate to “Downloads” then tap the recovery that you downloaded.
4d. You’re set!
Enjoy your rooted device, complete with custom recovery.
Sorry If I am misinterperiting this, but I thought flashify didnt work to flash recoveries with locked bootloaders like the S5?
joshuabg said:
Sorry If I am misinterperiting this, but I thought flashify didnt work to flash recoveries with locked bootloaders like the S5?
Click to expand...
Click to collapse
This is also confusing.
Download TowelRoot, a kickass hack by GeoHot.
https://towelroot.com/
Click the big-ass Lambda to download the app.
Use THIS version for NVIDIA SHIELD/ SHIELD Tablet and MadCatz Mojo
Why even post the link to towelroot and say download, then say download again below it with a different link. If it's for credit issue, format the grammar differently
I'm trying to root the "normal" way. I unlocked my bootloader, but there are no custom recovery or boot images available yet. Should i just do towelroot for now?
T-Keith said:
I'm trying to root the "normal" way. I unlocked my bootloader, but there are no custom recovery or boot images available yet. Should i just do towelroot for now?
Click to expand...
Click to collapse
That's what I did. There's no reason to unlock you boot loader if you use towelroot and then flashify when a build of cwm is released. So, either way, this method is best. You can use flashify to flash a recovery or boot image ☺
Well we don't know if towelroot and flashify will still work after the next android release. I know on the motox with 4.4.4 it no longer works. I like my bootloader unlocked and to have twrp myself. Hopefully a custom recovery will be available soon. Xda needs to add a shield tablet forum.
Sent from my Nexus 7 using Tapatalk
Is there a device tree for the shield tablet. http://forum.xda-developers.com/showthread.php?t=1943625
Sent from my OtterX running AICP using Tapatalk
Can I flash a factory image now without unlocking the bootloader?
Does anyone have a link to a factory image without the patch ?
Not sure if anyone wants to try but I was looking for custom recovery, and just thought I'd try it. Used WWJOSHDU' s video on youtube about installing recovery on shield portable. IT WORKS but with a draw back. I have CWM on my tablet but its upside down, but buttons work in the upside down orientation. Only problem I ran into (if it's considered a problem) is when I did a nandroid back up it saves to the internal memory even if you choose to backup to the sdcard. But as far as I know, all seems to be working quite well.
Had to unlock the bootloader though. Took a minute to get the drivers to work on my laptop but after about an hour of just playing around it finally worked. Not really sure I did anything differently but my laptop eventually recognized my device in fastboot mode. Will report back if anything changes
I really hope we get some new kernels and roms for this awesome device (esp. updated sound drivers!!!) The future is bright for this great gaming tablet.!
derking1 said:
I really hope we get some new kernels and roms for this awesome device (esp. updated sound drivers!!!) The future is bright for this great gaming tablet.!
Click to expand...
Click to collapse
Once the device tree is modified enough to get a build of cm fully compiled, expect some roms from me if I have enough time.
joshuabg said:
Once the device tree is modified enough to get a build of cm fully compiled, expect some roms from me if I have enough time.
Click to expand...
Click to collapse
That sounds great m8 look forward to them
Why unlock bootloader.
Thanks to Kwongger my Shield is now rooted , got CWM and backed it up.
Is it cause of towelroot we dont need to unlock bootloader anymore?
Are my bootloader now unlocked when i rooted it and installed CWM?
Thanks
Knievel
This doesn't appear to work with the newly released OTA.
EDIT, yes it does but it takes way past forever to work.
Hi Everyone,
is it safe to use this method to root the Shield 4G/LTE ???? I don't need recovery or rom, just rooted so I can use my rooted apps....
Thanks,
jce
jce2005 said:
Hi Everyone,
is it safe to use this method to root the Shield 4G/LTE ???? I don't need recovery or rom, just rooted so I can use my rooted apps....
Thanks,
jce
Click to expand...
Click to collapse
Hi all,
well, I took the risk and trie to install TowelRoot, but even by selecting under SECURITY " Unknown sources", TowelRoot does not install....
Any ideas ?
Thanks,
jce
UPDATE :
I am not able to install ANY version of TowelRoot...... tried both versio, from TR web site and alternate version for the Shield tablet and after going through the install process, it just comes up with a message : app not installed.....
Anyone has an idea what could be wrong ? Am I doing something wrong ?
Any help would be greatly appreciated.
Thank you all......
jce
Enter YouTube and search for root nvidia shield tablet and the first video in the description have the link to the direct site of towellrot download the apk and mayket rain then install SuperSU from the play store when you open the first time it will tell you to update the binaries chose the normal way then it will tell you its fail but restart the tablet and buala you have root access
Sent from my SHIELD Tablet using XDA Free mobile app
rene130313 said:
Enter YouTube and search for root nvidia shield tablet and the first video in the description have the link to the direct site of towellrot download the apk and mayket rain then install SuperSU from the play store when you open the first time it will tell you to update the binaries chose the normal way then it will tell you its fail but restart the tablet and buala you have root access
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Hi, thanks for replying.
I already downloaded towellroot a few times, the regular version, as well as the alternate version for the Shield Tablet, but neither version of towellrot will install. Under settings/security, I allowed installs from unknown sources , but the tr.apk or tr-1.apk will NOT install.....
Any other suggestions?
Thx,
jce
Hi again.........
Seems strange that no one knows why the TowelRoot ( tr.apk ) and the tr-1.apk ( for the Shield Tablet ) does not install. As I mentioned, I allowed under Security "installs from unknown sources", and the installation starts, but ends with "App not installed" message.
Am I doing something wrong or do I overlook something here ???
Any help would be appreciated, thx,
jce
Q&A for [Nexus 5] CF-Auto-Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Nexus 5] CF-Auto-Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
nexus 5 autoroot: downloading root.img failed
Hi Chainfire, thanks a lot for the program!
I actually just paypal'd you a symbolic euro for all the effort.
But after all, de root did not work completely yet,
after the selection menu 'unlock bootloader YES/NO' (I choose NO btw, will stay with the stockrom for a while),
i get the error message
' downloading boot.img FAILED (command write failed (No such file or Directory) ) '
I don't see anyone else reporting this problem on the thread, so my question: what could cause it? What can I do?
Extra inf:
I am on a windows system (7) and had the trouble with usb-driver that was not installed first, dont know if that influenced it?
flekkie said:
Hi Chainfire, thanks a lot for the program!
I actually just paypal'd you a symbolic euro for all the effort.
But after all, de root did not work completely yet,
after the selection menu 'unlock bootloader YES/NO' (I choose NO btw, will stay with the stockrom for a while),
i get the error message
' downloading boot.img FAILED (command write failed (No such file or Directory) ) '
I don't see anyone else reporting this problem on the thread, so my question: what could cause it? What can I do?
Extra inf:
I am on a windows system (7) and had the trouble with usb-driver that was not installed first, dont know if that influenced it?
Click to expand...
Click to collapse
dont use root toolkits, as you will learn nothing, then think your phone is bricked when it needs some simple upkeep. its a nexus, its easy to root, no toolkits needed, unless you just dont want to learn anything/the basics.
Hi Simms22,
You're absolutely right, thanks for your remark.
Just for the sake of explaining why I tried the toolkit:
I literally just bought the phone (<24h), and I only wanted a quick access to the SU-privileges. I didn't want the unlock the bootloader and go for custom ROMs (yet).
I did this with my previous phone (sony xperia), and all the trouble I had with the process took me 1,5 full days to get the thing running again.
Just to say, I dont want to go all deep into it right now. If I could root my nexus with the tool, that'd be great, but if it isn't possible, I will first explore my new phone as a ordinary user I guess. Going trought all the flashing-nexus-infothreads if for later on.
Thanks for the advice!
flekkie said:
Hi Simms22,
You're absolutely right, thanks for your remark.
Just for the sake of explaining why I tried the toolkit:
I literally just bought the phone (<24h), and I only wanted a quick access to the SU-privileges. I didn't want the unlock the bootloader and go for custom ROMs (yet).
I did this with my previous phone (sony xperia), and all the trouble I had with the process took me 1,5 full days to get the thing running again.
Just to say, I dont want to go all deep into it right now. If I could root my nexus with the tool, that'd be great, but if it isn't possible, I will first explore my new phone as a ordinary user I guess. Going trought all the flashing-nexus-infothreads if for later on.
Thanks for the advice!
Click to expand...
Click to collapse
Unlocking bootloader and using custom ROMs etc on a Nexus is no where near as complicated as it is on a Sony device (or any other) - in regards to if anything goes wrong, it usually takes 5mins or so to start from scratch on a Nexus again compared to Sony/Samsung etc.
Also remember, there is no warranty issues on a Nexus device either. So you can unlock/lock your BL as and when you see fit.
radicalisto said:
Unlocking bootloader and using custom ROMs etc on a Nexus is no where near as complicated as it is on a Sony device (or any other) - in regards to if anything goes wrong, it usually takes 5mins or so to start from scratch on a Nexus again compared to Sony/Samsung etc.
Also remember, there is no warranty issues on a Nexus device either. So you can unlock/lock your BL as and when you see fit.
Click to expand...
Click to collapse
Ok, thanks a lot for your reply. It gave me confidence to try the 'unlock bootloder'-option, which worked like a charm
I am enjoying now the perks of a good titanium-datatranfer; I like!
See you around in a few months when I try custom ROMs!
Device already unlocked?
Hello,
I am also new to gaining root access on android devices, and I could use some help.
I have a Google Nexus 5, and followed the steps using CF Auto Root, but it only says <waiting for device> when started and wont proceed with anything. I have the device in bootloader and it tells me the Lock State is already unlocked. I haven't left CF Auto Root on <waiting for device> for more than 5 minutes, assuming it shouldn't take that long.
So I went ahead and installed SuperSU via Google Play to see what I could do, but SuperSU tells me that there is no SU binary installed, and that if I just upgraded to android 4.3, I will need to manually re-root. However, I have android 4.4.2.
I have used two different root checking applications, but they both told me that my device does not have proper root access.
Superuser also doesn't seem to work. It wont inform me when I try to use an app to perform root access actions.
Any help on what I could do next would be appreciated.
Thanks ~
Valdtun
Valdtun said:
Hello,
I am also new to gaining root access on android devices, and I could use some help.
I have a Google Nexus 5, and followed the steps using CF Auto Root, but it only says <waiting for device> when started and wont proceed with anything. I have the device in bootloader and it tells me the Lock State is already unlocked. I haven't left CF Auto Root on <waiting for device> for more than 5 minutes, assuming it shouldn't take that long.
So I went ahead and installed SuperSU via Google Play to see what I could do, but SuperSU tells me that there is no SU binary installed, and that if I just upgraded to android 4.3, I will need to manually re-root. However, I have android 4.4.2.
I have used two different root checking applications, but they both told me that my device does not have proper root access.
Superuser also doesn't seem to work. It wont inform me when I try to use an app to perform root access actions.
Any help on what I could do next would be appreciated.
Thanks ~
Valdtun
Click to expand...
Click to collapse
Your best bet is to learn to do it manually.
Your next steps are
1) install recovery
2) flash superSU zip from recovery
Recovery is installed by fastboot.
In my signature, is a link to guides and info threads. Click it and then read the thread "adb and fastboot. What is it?"
This will tell you what you need.
Then you can download TWRP recovery image to flash.
Solved
It seems that my driver wasn't very compatible, and now my phone has been successfully unlocked. Thank you for the help.
rootSU said:
Your best bet is to learn to do it manually.
Your next steps are
1) install recovery
2) flash superSU zip from recovery
Recovery is installed by fastboot.
In my signature, is a link to guides and info threads. Click it and then read the thread "adb and fastboot. What is it?"
This will tell you what you need.
Then you can download TWRP recovery image to flash.
Click to expand...
Click to collapse
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Same here, none of the root explorers I tried seem to work.
Will the latest CF Auto Root wipe the storage on encrypted Nexus 5?
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Try flashing pie patch. http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page2 (post #13).
If problem still exists, try to install SELinuxModeChanger from the play store and change SELinux mode to permissive.
root
This is not a full root... at least in my nexus 5..
There are thing that I am not aloowed to do like disable startup apps and give some apps# permission
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Some root apps aren't working on lollipop right now. Root explorer on es file manager is one of these
ravi84m said:
Same here, none of the root explorers I tried seem to work.
Click to expand...
Click to collapse
Search "amaze file manager" on the play store, it works flawlessly
Thanks, pie patch did the trick for me.
I had to use SELinux Mode Changer for viper though.
CF-Auto Root
Relocking the bootloader will not reset your warranty, for that you would have to run CWMbootunlocker script in twrp or cwm or philz. Oh and here is the link to a good thread to explain all that..
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That is because of new SELinux polices which developers will need to workaround it ..
WARNING WARNING WARNING
You could use SELinux mode changer or run setenforce via term emulator and set it to permissive However!! this allows more malware to have access to your phone basiclly
Want to ROOT my N5, just root it, already unlocked bootloader.
Hi,
I just want to root my nexus 5. I am on Android 5.0, updated during the official rollout, and not using any custom flash/ROM.
Boot-loader is already unlocked, I had rooted it when on 4.4.4 Kitkat, but after I updated to Lollipop, all root priviledges were lost.
I do not want to flash any custom ROM or anything, just want to root it.
I found may threads and guides showing how to root is, but all of them included unlocking bootloader or flashing a custom ROM.
I dont even know what a custom ROM is and what is its use?!?! (noob)
Please just help me root my phone.
Thanks
vvk619 said:
Hi,
I just want to root my nexus 5. I am on Android 5.0, updated during the official rollout, and not using any custom flash/ROM.
Boot-loader is already unlocked, I had rooted it when on 4.4.4 Kitkat, but after I updated to Lollipop, all root priviledges were lost.
I do not want to flash any custom ROM or anything, just want to root it.
I found may threads and guides showing how to root is, but all of them included unlocking bootloader or flashing a custom ROM.
I dont even know what a custom ROM is and what is its use?!?! (noob)
Please just help me root my phone.
Thanks
Click to expand...
Click to collapse
A couple of options:
1. Flash CF-Auto-Root
2. Boot to TWRP recovery and flash SuperSU.zip
Everything is well explained in the main CFAR thread or in the General sticky threads.
Apply update to version 2.37?
Hi all,
I rooted my Nexus 5 running Lollipop some time before with CF-Auto-Root. I think Chainfire still used a patched kernel in this approach and installed SuperSU v2.20.
Afaik Chainfire managed to get root without the need for a patched kernel now. Therefore I would like to update to v2.37. Can I? How? Would the kernel stay patched after using the latest CF-Auto-Root? Do I need to go back to the stock kernel before applying the latest CF-Auto-Root? And how to go back to the stock kernel?
Thanks for your help!
Maik
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
I only picked up my NP last week and after a couple of days it updated to 8.0 / Oreo, So all my research and prep for a root & flash has been thrown up in the air.
Are there any major changes anyone knows of that might make rooting, custom bootloader & rom flash problematic?
i did really like the old leanback launcher UI and the update is way too fussy for my liking, and i'm not even going to comment on the lack of catch-up content for UK users. If ever a device needed hacking, this is the one.
cheers in advance
Honestly im pretty sure you could just flash magisk through twrp with the 8.0 zip. Im pretty sure it would work
thanks for the reply, i'm dithering as i'd hate to lose the chromecast feature and have yet to find a rom which has it mastered and working.
gascomm said:
thanks for the reply, i'm dithering as i'd hate to lose the chromecast feature and have yet to find a rom which has it mastered and working.
Click to expand...
Click to collapse
Magisk root and TWRP work just fine. You won't lose any functionality, but that's with the stock images.
Is there a way to get back without a computer? I lost root after the forced update. Think I'm still unlocked boot loader got the icon at boot up but have no twrp recovery anymore or root sadly I miss 7.1.2 after the update it crapped the nexus player
Sent from my Nexus 7 using Tapatalk
I don't believe so. You'll need a computer to run adb to downgrade.
An easier method is to use the Nexus Root Toolkit which will input all the commands for you. You just point and click.
I ported twrp for the Asus Zenfone max plus m1.However I don't have experience on how to test it or if I did flash it,how to restores stock recovery so I haven't tested it yet.I would like some people to test it for me.After or if it is successful and I get confidence in porting these things I might try to port a rom or too for our device.or try to port a kernel.as our current kernel is kind of old.
Hi, i would love to test it.
But still can't root it after Oreo update, even with the tool provided by Asus .
Tried kingroot also didn't support.
I could test it. Although, I really need a method of root first.
Anyone knows a method in which you could root it without a custom recovery? And yes, I've heard of Magisk, but I'd rather avoid that until it's the last option. Thanks!
Carpeso said:
I could test it. Although, I really need a method of root first.
Anyone knows a method in which you could root it without a custom recovery? And yes, I've heard of Magisk, but I'd rather avoid that until it's the last option. Thanks!
Click to expand...
Click to collapse
Wait why do you need root to install a custom recovery in the first place? I haven't tested the twrp file I made and also I lost it, so I might have to recreate it. Sorry for not being active for awhile, I was busy with school
Carpeso said:
I could test it. Although, I really need a method of root first.
Anyone knows a method in which you could root it without a custom recovery? And yes, I've heard of Magisk, but I'd rather avoid that until it's the last option. Thanks!
Click to expand...
Click to collapse
follow this tread and site
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
https://twrpbuilder.github.io/downloads/twrp/#tab=completed#724
and here
https://github.com/TwrpBuilderTests...s/tag/TWRP-3.2.3-TwrpBuilder-2019-03-21_15-58
Sorry for the long period of inactivity
I've been away from xda for awhile sorry y'all. I had to focus on studies and I didn't check xda for a bit. I can't seem to find the twrp file that I ported with a online method. I never tested it, and it's likely it wouldn't have worked as the previous post shows. Someone has built twrp for our device. Bless them. As for the root question. It's possible to unlock bootloader on our Asus Zenfone max plus m1 and then use the patch boot image method by extracting the boot IMG from the firmware and then patching it with the magisk apk/ app and flashing it with fastboot flash boot patched_boot.im.