First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Sharjeel.Khan said:
First of all, don't get your hopes high, i rooted as traditional method like many others. I'm flashaholic and i started new thread for those who upgraded intentionally or accidentally and now think download would brick their sets. it won't. things are pretty obvious here but i repeat I'm sharing this to people who've upgraded for any reasons and have no clue how to downgrade or achieve root.
So i bought a cell (sm g920V) with preinstalled PI2 (MM6.0.1) . found out pingpong root is avail only for 5.02 . i was afraid to downgrade so i searched more. found out nogat 7.0 DQD1 has root. and can be rooted via cf autoroot. i upgraded and i tried. but it didn't worked. on nougat i did everything. tried every root app (both pc and apk ver) but failed. i decided to go back.
here i found This thread by @toutanje which said even i upgraded to nougat, i can safely downgrade to PK2 (6.0.1) , PH1 (6.0.1) and BOG7 (5.1.1) . i flashed BOG7 (5.1.1) directly because during search i've foundout that there is temporary root available for BOK7, and they both are 5.1.1. i did this because BOG7 is earlier version than BOK7, for this i won't have to downgrade but to upgrade that i did. i flashed BOK7 and headed Here, a thread by @klip1 . there wasn't any clear instructions not links no attachments. but thanks to @MrMike2182 who shared main file Here. BEWARE that you'll lose root each time you reboot, but you can gain it back easily by running root apk simply from your mobile. this is better then not having one.
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrage to BOK7), then flash BOK7, odin Sboot file (attached). you'll see some yellow codes above when restart. i was stuck there with bootloop on VZ logo. all you need to do is to factory reset. (by pressing and hold vol + & vol down + power button until you see black screen with options. press vol down and highlight second option factory data and reset. now press home button. )
phone will start normally, goto devloper options, enable usb debug, allow unknown sources and than root it with kingroot apk. done.
Those who prefer SuperSu can get lead from Here thanks to @EvilRubberDuck. but i am not sure about point 3. there is nothing attached at first post. tough little search may lead you to success.
Thanks to whoever took even little interst to make this beast rooted. please try to get permanent root for this device too. if anyone know how to get it, or any more info regarding rooting this device. please share. let me aware. i'll really appreciate that.
NOTE : i take no responsibility of what you do to your mobile. you're doing it with your own consent. if you're unsure what you're doing, don't do it. I, developers/members mentioned and xda are not responsible for ANYTHING or what you do to your phone.
Click to expand...
Click to collapse
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
MrMike2182 said:
If you use the SuperSU instead of KingRoot then you can use my installroot script and then the rootatboot if you need to reboot for some reason however if you are not near a PC at the time and you really need to reboot then use terminal emulator from the play store and open it and type su then enter and on the next line type pkill zygote and voila reboots without PC.
Click to expand...
Click to collapse
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Sharjeel.Khan said:
yes i've read this post of yours, i should've added this. Glad you came here and i really appreciate your efforts for s6 users. you've done great job for us.
it'll be great if you attach your script and write or quote your method here too. so users don't have to go through earlier threads and finding things. like me who bought this phone pretty late.
right now i'm using quickreboot apk to get hot reboot which keeps the root. but sometimes when you really need to restart. i see your solution as best.
Click to expand...
Click to collapse
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.. I've included in the file the eng kernel and eng sboot but there's different versions so this one in my file called boot.tar is from the eng kernel to the S6 G925V so if you're using G920V you need to get the eng kernel for that one.. Now first you put the phone into download mode and flash the eng kernel using odin and after the phone boots then using Windows command prompt navigate using the cd command to where the file is you downloaded called S6rootbyMrMike2182 once you're in there type installroot and the script should run and flash everything needed including busybox and then the phone will reboot (it will also boot just this one time without using the rootatboot because the same codes in this file too) now when you click on the SuperSU app it's going to say it needs to update su ignore it and go right to the play store and install/update the SuperSU from there and then the phone should be rooted and ready to go.. If you ever need to reboot for some reason connect the phone to your PC and open a command prompt in the same folder again and run rootatboot and it will set the phone as permissive again so it boots.. You can unplug it after you see the Verizon logo.. If for some reason you aren't near a computer and you really need to reboot then use terminal emulator from the play store and open it and type su and grant root access and then on the next line type pkill zygote and voila reboots without a computer
If you have KingRoot on your phone and you want to get rid of it to use SuperSU thanks to @Chainfire then use this script that I'm listing below.. Also keep terminal emulator open while you are doing this because you might(not all devices just some) get a continuous annoying popup that prevents you from doing anything (thanks to KingRoots junk) so you'll have to use terminal emulator to kill/end that process in order to continue and after you kill/end that process then go delete it immediately! Links to root with SuperSU and KingRoot removal are below!
S6EdgeRootByMrMike2182
KingRoot removal script
G920V ENG Sboot
By the way I nor XDA-DEVELOPERS is responsible for anything you choose to do to your phone! If something goes wrong, just reflash your original firmware but don't go blaming me nor XDA because I don't have to put this up so please do your research before messing with your phone and as always, make a backup of everything you wish to keep! And no this will not delete or wipe your phone unless you choose to! Links are above. You can change it or whatever just give props where it's due!!
SERIOUSLY MAKE A BACKUP OF ALL YOUR PICTURES ETC ETC BEFORE DOWNGRADING AND I'M NOT KIDDING!!!
MrMike2182 said:
OK so my phone is on 5.1.1, it was originally on 7.0 so you can downgrade back to the 5.1.1 firmware.....
Click to expand...
Click to collapse
great. you completed the thread :highfive:
Didn't know about script removing kr.. wil give it a try for sure. :good:
ok i'm getting confuse here. can you please provide exact files that needed to flash on g920V please ? i mean eng kernel and sboot ? and the file with odin says "G920A_Kernel_Root_5.1.1_S****.tar", A ? isn't A refers to at & t ?
i'm afraid if i may flash wrong file. can you please help me here with exact files needed for us (G920v) ?
and when i'm running installroot via cmd, it execute it goes like it created by you until daemon started successfully for like for five to 8 sec and then disappear. phone doesn't reboot. nothing happens. ,
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Sharjeel.Khan said:
so if you desperately want root. wherever you're on nougat DQD1 or MM. Downgrade to BOK7.
simply follow instructions there and all you have to do is to flash BOG7 from thread mentioned above (for safety as i did did step and i'm not sure if you may directly downgrade to BOK7), then flash BOK7.
Click to expand...
Click to collapse
Muhammad Aliyan said:
can anyone confirm if i can directly downgrade to BOK7 ? im currently on DQD1 also can anyone guide me how to actually flash my phone like step wise im new here.. I upgraded to 7.0 but I desperately want root now I've odin installed i just need some1 to teach me how to do it like where to select sboot file and other files
Thanks
Click to expand...
Click to collapse
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Sharjeel.Khan said:
welcome here. first things first, i don't mean to discourage you but if you don't know about where to "put sboot and other files", you really shouldn't be doing this. additionally downgrading is a risky process where things get messy due to single mistake .
To answer your question directly, NO. i've read a post somewhere here that we can only downgrade to mentioned (in 1st post) firmware. OP there tried to downgrade to other fw but failed.
and that is exactly why i did long and safe procedure and downgraded to BOG7 and then BOK7. . both are 5.1.
2nd question : you need to put sboot file in "AP" section of odin. (be careful with using it)
i assume you have G920V, which have locked bootloader, my suggestion would be... its not worth it. trust me. even if you downgrade, and rooted too, you'll loose root if you restart your device. and you cannot install recovery and so on. there is no permanent root for this device.
Exchange your device for international version or so, either wait for it and enjoy being on nougat. devs are working on it may be. some claim to root nougat too. better don't downgrade and much better if you stop right there when you don't have basic knowledge about this. you'll end up having paper weight instead of device.
Click to expand...
Click to collapse
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Muhammad Aliyan said:
But on 5.1.1 my battery life was so good now it just keeps draining even on power saving just drain and drain I previously also upgraded using Odin from 5.1.1 to 7.0 (biggest mistake) and i'm regretting it although its much better it terms of improvements and performance i just cant live with this battery life also i need root for WifiKill and to hack in-app purchases .. and i don't reboot my device often..
so if im downgrading to both of these BOK7 or BOG7 i need to use the sboot file u provided right ?
Click to expand...
Click to collapse
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
LuisElListo said:
Quick question if i can root my device with this method it possible to install xposed framework via Flashfire?, just a question.
If not possible install xposed not a problem, better root than nothing, and i am not reboot so much, to say nothing.
And like say Muhammad Aliyan, the battery in 7.0 is much more less than 5.1.1
(Sorry for my bad english.)
Click to expand...
Click to collapse
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Sharjeel.Khan said:
i have tried it earlier and failed but now when i saw youre asking this, i gave it another try and i'm stuck on bootloop. lol.
better don't do it.
i've read it that xposed is not compatible to our devices (64bit) yet ( just read it not confirming it) + in xposed official thread, it has been warned that bootloops occur in samsung stock roms. soi'd say do not try this.
Click to expand...
Click to collapse
So close, well better wait to safe method in stock room, or unlock bootloader. Thanks anyway.
Sharjeel.Khan said:
alright. nothing to worry about. just downgrade like i mentioned on OP (for safe side as no one here to confirm)
okay so like i said you just need to put the provided file (all credits to original dev/coder) in AP section and flash after you install BOK7. .
i can only tell you about BOK7 as i've done and using this. not G7.
so after to downgrade to bok7, let it boot properly. factory reset your phone, go to download mode and flash attached file using odin. (uncheck all options but f reset time and auto reboot)
phone will restart, and you'll see some green numbers and something when booting. let it boot. go to dev options enable usb debugging. uncheck "verify apps usgin adb" and... root either from kingroot (comes with 100 of ads even on lock screen) or look at this post by MrMike2182 who gave us superSU :victory:
and most important part here : make a backup of everything. and i take no responsibility of what you do to your mobile. you're doing it with your own will. if you're unsure what you're doing, don't do it. I, developers/members mentioned here and xda are not responsible for ANYTHING in any way.
good luck :good:
Click to expand...
Click to collapse
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Muhammad Aliyan said:
everything was good I downgraded to BOG 7 first with odin all good then OK7 and again all good successfully booted up everything is fine fingerprint sensor etc right after i flash the sboot file my fingerprint sensor stopped working it says an error occurred can you please help me .. phone is rooted though but cmon fingerprint sensor i can't live without it..
Edit: tried factory reset and restarting, none worked.
edit2: reflashed OK7 again and its fingerprint is working but can't root. flashed sboot to root but fingerprint stopped working.
edit3: again flashed OK7 then sboot again green text in the corner again root succeed but again fingerprint not working guess something wrong with the sboot..
Click to expand...
Click to collapse
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Sharjeel.Khan said:
thats strange because i had FP working while rooted from same sboot file that i attached.
try downloading from another source like in second post where mrmike2182 shared it. and try removing Samsung account (if its there, don't forget to turn off reactivation lock before that.)
see if it helps.
Click to expand...
Click to collapse
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
LuisElListo said:
Same issue with this flash OK7 FP work ok, but install Sboot and FP not working.
edit1: cant root the device i open cmd with adm permission, installroot, daemon is stop, is starting, after close cmd and the phone not reboot.
Click to expand...
Click to collapse
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Sharjeel.Khan said:
hmm. i believe FP didn't came friendly with this sboot. any experienced dev might help us out here
make sure you have proper drivers installed and have working adb. read instructions, search fourm. by the way, for same kind of issues, i had to go with kingroot.
Click to expand...
Click to collapse
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
LuisElListo said:
Well better than nothing, uninstall all bloatware for my phone (finally), FP sensor yes it to cool but, meee y si better pin or patron.
Just have to try install Xposed and all done.
Do you try to install official xposed? Or the unofficial for Samsung Stock https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Sharjeel.Khan said:
i'd love to try right now but i can't because i'm currently working on something else.
but for your assistance, Here is what you're looking for. its a success.
Click to expand...
Click to collapse
I try a shoot.
Its working, its ****ing working, I sacrifices FP, and Supersu but I dont mind i have xposed and a root.
imgur(dot)com/a/zLvrD
Edit1: bad news activated module xposed requeried reboot, soo the root is lost and requiered to root again with kingroot the problem is my percent is not advance 01%. Also every time I rooted the phone is slowing arriving a point where it restarted alone and is only 01%.
If i a factoy reset i lost xposed and root or better reflash the Rom OK7?
Related
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!
Need a link to the files you mentioned.
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin
I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!
sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...
Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.
Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:
Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:
Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you
Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?
VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.
Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk
THIS WILL VOID YOUR WARRENTY AND I AM NOT AT FAULT IF YOU BRICK YOUR PHONE.
I AM NO LONGER ACTIVELY WORKING ON THIS PROJECT AS I AM WORKING ON A PROJECT FOR THE S7
I have achieved root on my Amp Prime. SM-J320AZ for cricket. It has been tested on other versions of the J3 and has worked. If it you do decide to test it, please report back on your device model and carrier.
ON THE SM-J320AZ It does NOT trip knox to do this. If you try to flash any TWRP you will trip Knox and get the samsung BSOD and will have to use Smart Switch do an emergency recovery,
DISCLAIMER: THIS COULD BRICK YOUR PHONE. I AM NOT RESPONSIBLE IF ANYTHING GOES WRONG. IF YOU NEED HELP PM ME
First Enable Dev options and select OEM Unlock And USB debuging
Than flashed this modded boot file using odin to exploit SElinux and enables ADB:
drive.google.com/open?id=0B1rwlbcYZ8i6NldnV0ppVHJ3Z1U
place the file in AP and make sure Re-partition is NOT check.
Then I ran Wondershare TuneGO I was able to achieve perm root. It looks like it fails after it reboots a few times and then gets stuck on a black screen, when this happens, do a battery pull then restart and run SU, it will have you update the binary's then you are rooted. Enjoy
Note: Sometimes you get a failed to install binaries, if you get this you might have to restart 2 or 3 additional times after battery pull to install SU binaries.
Thanks and let me know how it goes.
I will post a better guide later, just spent 9 hours working on this now im tired
Xposed for Samsung is untested, please use at your own risk. If you get stuck on booting after installing, use smart switch to do an emergency recovery. http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
UPDATE: XPOSED does work if you flash it with FlashFire, make sure the latest version of BusyBox is installed
You might get security notifications saying unauthorized files and such. If you do, set SElinux to Enforcing. Use ADB shell or terminal as SU and type setenforce 1. To check SElinux mode, type getenforce
NOTE: NO CUSTOM RECOVERY YET and WiFi becomes unstable, you will have to turn it off and on a few times to make it work. I am working on this.
To Fix the WiFi issue edit your build.prop using your favorite build.prop editor and change ro.secure.storage.support to false and reboot. You will have to forget your network and re-add it but it should save it and auto connect now.
To fix the warnings, freeze/disable knox, use the search function, their are lots of great tuts on how to do this already.
Known Bugs:
Built in flashlight app does not work, can freeze.
Wifi becomes unstable (See above for temp fix)
Knoxs gives unauthorized errors until disabled.
Disabling androids built in security leaves your device vulnerable. I suggest using PMP once exposed is installed.
I am working on a rooted version of the stock rom with fixes in place to upload, when complete
Look man, you have no idea how long I've been trying to get my j3 rooted. You are the man. I can confirm this works. So obviously we don't have any Roms for this phone, but could I install team win recovery? Not sure what good it would do but do you have any advice on that? I really appreciate you man.
GarrettVW67 said:
Look man, you have no idea how long I've been trying to get my j3 rooted. You are the man. I can confirm this works. So obviously we don't have any Roms for this phone, but could I install team win recovery? Not sure what good it would do but do you have any advice on that? I really appreciate you man.
Click to expand...
Click to collapse
Thanks! Glad this helped. Right now no costume recoveries work. Also if you have stability issues after flash, edit the build prop and find ro.secure.storage.support and set it to false. This will fix errors with the wifi, im working on another fix for this issue right now and getting a CWM/TWRP to work right now
GidgetTheGnome said:
Thanks! Glad this helped. Right now no costume recoveries work. Also if you have stability issues after flash, edit the build prop and find ro.secure.storage.support and set it to false. This will fix errors with the wifi, im working on another fix for this issue right now and getting a CWM/TWRP to work right now
Click to expand...
Click to collapse
Alrighty. I appreciate all your hard work bro. I've not had any stability issues so far believe it or not. Keep up the good work! Any work you put towards a rom or recovery id be happy to make a donation.
EDIT- Also, which xposed did you flash?
Use the link on the OP and download SDK23 / Arm Build and flash using FlashFire.
I recomend backing everything up before you do, make it the Odin flashable for easiest use
twrp is providing to be more difficult due to the locked bootloader and other security in MM. please stay tuned. Tonights build i flashed worked for the first boot, and then on the second boot locked the phone and soft bricked it.
Man thank you so much, i have been seaching a method for root my device. I can confirm it works on Samsung Galaxy Sol (SM-J321AZ). I updated the SU but now the problem is the Wi-Fi, i don't know how to delete the SS DATA File for fix that. Can you help me please? I don't know what is that file. I'm newbie with this and i want fix this problem, thank you again for your really hard work, i know this is hard!!!
EDIT 1:
Another problem when the USB is connected to PC.
I'm getting this message every time i have connected my device to my PC (Windows) and sometimes the device reboots automatically without reason.
The last thing. I was trying to set SElinux to Enforcing on Terminal Emulator but it says:
"setenforce: Couldn't set enforcing status to '1': Permission denied"
I had to disable the service SecurityLogAgent for remove the security notifications saying "unauthorized files".
EDIT 2:
The problem with the Wi-Fi is when the device reboots it removes automatically all the networks and you have to enter the password again.
I received many errors on the menu saying "The system do not respond" and "Unfortunately calendar has stopped" i was unable to take a picture of this or take a Screenshot because it was blocked.
The flashlight icon doesn't work anymore after root the device. (I had to use a 3rd party app for turn on the Flashlight) It works good on the Camera.
I had to use Smart Switch in Emergency Mode for get back my device.
legnison said:
Man thank you so much, i have been seaching a method for root my device. I can confirm it works on Samsung Galaxy Sol (SM-J321AZ). I updated the SU but now the problem is the Wi-Fi, i don't know how to delete the SS DATA File for fix that. Can you help me please? I don't know what is that file. I'm newbie with this and i want fix this problem, thank you again for your really hard work, i know this is hard!!!
EDIT 1:
Another problem when the USB is connected to PC.
I'm getting this message every time i have connected my device to my PC (Windows) and sometimes the device reboots automatically without reason.
The last thing. I was trying to set SElinux to Enforcing on Terminal Emulator but it says:
"setenforce: Couldn't set enforcing status to '1': Permission denied"
I had to disable the service SecurityLogAgent for remove the security notifications saying "unauthorized files".
EDIT 2:
The problem with the Wi-Fi is when the device reboots it removes automatically all the networks and you have to enter the password again.
I received many errors on the menu saying "The system do not respond" and "Unfortunately calendar has stopped" i was unable to take a picture of this or take a Screenshot because it was blocked.
The flashlight icon doesn't work anymore after root the device. (I had to use a 3rd party app for turn on the Flashlight) It works good on the Camera.
I had to use Smart Switch in Emergency Mode for get back my device.
Click to expand...
Click to collapse
Please follow the directions above with the build prop editor to fix the wifi issue. As for the flashlight and the warnings they are still a work in progress, but doing the build prop edit has fixed some of the issues for me and I no longer get the error messages.
To set SELinux to enforce you have to do it through terminal emulator or ADB shell.
type:
SU
setenforce 1
getenforce
this should also help with the errors.
The Final method i used to get rid of the errors was, I froze all the knox processes.
The usb error i still get also but has had no effect on performance or on sync
Galaxy sol
Thank you for getting a root. I have a question/problem.
when I go to run wondershare it says it can not transfer data please reconnect and try again. it also says something about smart transfer.
do I need to use the paid version or will the free version work?
I have usb debugging enabled, I was able to flash the tar file via odin
Any help is greatly appreciated
This might not work for your phone as it is for the Galexy Amp Prime from cricket. The free version is all i used.
Thank you for the reply, I did see one poster above was able to get it to work on the sol. I'll pm him and ask if he had the same problems.
ok, so I have another question. I re-read above and looked at the attached picture and I was great getting the security log error when I tried to use wondershare. I downloaded package disabler and I ran it again and it didn't show that error but still said unable to root. Do you know if disableing the security log like that would make a difference? my model number is SM-J321AZ
Will this work on sm-j320az cricket?
Quick question, if I were to factory reset or actually more so wipe my system and third party apps through flashfire, would anything incredibly drastic happen and also would I lose root?
Edit- to the guy above, yes this is for our j320az for cricket
I have a j320r4, for US Cellular. Tried a variety of root methods for my phone and all have failed so far. Would flashing this to my phone brick it? Would I be able to reflash stock if it did?
I might ask, what method does this use to obtain root. The guy I was working with on this phone seems to think my bootloader is locked.
cutederf said:
Will this work on sm-j320az cricket?
Click to expand...
Click to collapse
Yes this is specifically for the cricket phone
LeviathaninWaves said:
I have a j320r4, for US Cellular. Tried a variety of root methods for my phone and all have failed so far. Would flashing this to my phone brick it? Would I be able to reflash stock if it did?
I might ask, what method does this use to obtain root. The guy I was working with on this phone seems to think my bootloader is locked.
Click to expand...
Click to collapse
I am not sure, I am not familiar with that phone sorry
GarrettVW67 said:
Quick question, if I were to factory reset or actually more so wipe my system and third party apps through flashfire, would anything incredibly drastic happen and also would I lose root?
Edit- to the guy above, yes this is for our j320az for cricket
Click to expand...
Click to collapse
If you do a factory reset after root you MAY lose it. I played around with it and did a system wipe from the bootloader and was able to install SU and reroot with out having to do anything else as when you do a factory reset it wipes the /data and /cache but leaves /system intact. My xposed framework also stayed intact after a factory reset. I do recommend installing Xposed and FlashFDS kit to fix security warnings from TIMA and KNOX
angrybear000 said:
ok, so I have another question. I re-read above and looked at the attached picture and I was great getting the security log error when I tried to use wondershare. I downloaded package disabler and I ran it again and it didn't show that error but still said unable to root. Do you know if disableing the security log like that would make a difference? my model number is SM-J321AZ
Click to expand...
Click to collapse
As this is not for your model, I am not sure. Sorry.
thanks works for the gophone.
I will wait for your final fix solution, i hope you get it soon. Thanks for this hard work, i'm really happy with this )
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section to root, or "Do the prep" section to fix a bad root.
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting update UPDATE-SuperSU-v2.82-20170528234214.zip (version 2.82) is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
Do the prep:
Note that the hidden Do the prep section is ONLY for repairing a bad flash, SuperSU has been updated and as of version 2.79 the hidden section should no longer be needed for general purpose root on a working device, you just flash SuperSU. If you flashed an older version and are bootlooped, perform this section and continue.
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, when you have your backups and are ready to root, first go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press ENTER (there is no confirmation returned). You can verify this worked correctly by entering 'cat /data/.supersu' in the terminal and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again. Now press exit/back and press the HOME key.
After you have successfully entered the command in the TWRP Terminal you may continue
How to do it:
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
Again, this is somewhat dated information and only applies to fixing a bootlooping device when improperly rooted.
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.
Alternate Method #1
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 98% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
Reserved - FAQ (oops, guess I already did that)
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Jorinde123 said:
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Click to expand...
Click to collapse
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
acejavelin said:
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
Click to expand...
Click to collapse
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Jorinde123 said:
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Click to expand...
Click to collapse
Because you are not on 49-18, if you were on the latest OTA for 6.0 you were on 49-18-4. Pre-flash validation failure confirms your using the wrong version. Look in my sig for the return to stock thread, there are links to current roms and discussion of the 'preflash validation error'.
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Got the Moto X Pure a few days ago. It came with 6.0. This procedure works. Thank you!
ban.codrut said:
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Click to expand...
Click to collapse
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
SouthernEvo said:
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
Click to expand...
Click to collapse
It is not a known issue... Where are you storing the backup, internal storage or SD card?
acejavelin said:
It is not a known issue... Where are you storing the backup, internal storage or SD card?
Click to expand...
Click to collapse
Was backing up to the SD Card . Been messing with it and now its working for some weird reason . I appreciate your quick response though
I used windroid to unlock the bootloader and install twrp( don't reboot system but rather boot into recovery to make twrp stick) , from there I just flashed supersu and I was good to go. Many methods out there but this worked for me.
Thank you so much for this guide. I have to say, as a new Motorola user coming from Samsung phones exclusively, this whole process made me feel like a real noob again.
I made the switch from iOS to Android back when the Galaxy S2 came out because I grew tired of the jailbreak cat and mouse games on the iPhones and iPads. Learning to root and flash ROMs on all my subsequent Samsung devices was fairly simple and very enjoyable. This Moto X Pure though was a real tasker for me. I honestly never knew about the extra steps you had to take to unlock, twrp and root this phone. I really wish manufactures would help us make this much easier.
Anyway, thank you again for your help. I'll be seeing y'all around the forums as a new MXPE user!
acejavelin said:
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Click to expand...
Click to collapse
Thank you for clarifying a misconception I had on systemless root
(I intentioned to reply to you earlier, but the mad busy week made me forget about my intent )
I'm going to try right now the latest stable with systemless method (rather than flashing the older version) on a full wiped clean stock to see if it works. (Even tho I see lots of feedbacks here inspiring me to believe it would)
In what order?
acejavelin said:
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting SR4-SuperSU-v2.78-SR4-20161115184928.zip is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. You can verify this worked correctly by entering 'cat /data/.supersu' and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again.
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Click to expand...
Click to collapse
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Iglooian said:
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Click to expand...
Click to collapse
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
acejavelin said:
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
Click to expand...
Click to collapse
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Iglooian said:
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Click to expand...
Click to collapse
Fair enough... I will edit the "How to do it" section to make it more clear.
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I mean its with SuperSU and of course doesn't survive a reboot and still can't figure out anyway to write to /system..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How did you manage this? Was it with just installing SuperSU?
https://github.com/gfunkmonk/N920V_7_TMPROOT
Hey man @gfunkmonk, thank you so much for continuing development on this phone because I lost all hope recently. I saw your link to github.com and downloaded the files. Flashed the first folder using Odin but couldn't figure out what to do with the second folder. I would love if you could assist me in getting it done. I know it's tempting root but at least I could remove bloatware and run certain software. Looking forward to a reply and hopefully full root could actually be a possibility. I'll also volunteer to test anything you come up with if you continue development.
Oh yeah, the second folder is a linux script.. i'll add something for windows. Unfortunately you aren't going to be able to do that anyways. If you try to remount /system read/write the phone will lock up and reboot. I believe this is due to dm-verity which would require patching the kernel. Not possible since the bootloader is locked.
gfunkmonk said:
Oh yeah, the second folder is a linux script.. i'll add something for windows. Unfortunately you aren't going to be able to do that anyways. If you try to remount /system read/write the phone will lock up and reboot. I believe this is due to dm-verity which would require patching the kernel. Not possible since the bootloader is locked.
Click to expand...
Click to collapse
I saw different options on different threads, Would something like this be possible on marshmallow 6.0.1? Or maybe flashing a different firmware such as one for the N920T beacause they use the same processor after flashing a combination file? Full root is possible on 5.1.1 for the N920V but because we cant downgrade if you didn't have an old device without updates it's impossible. So I think the best bet is working with marshmallow for now. I've seen people say they get temp root without crashing using mobilego so maybe applying what you have here would have better luck on MM. Maybe dm-verity could be bypassed and maybe we can use safestrap to flash files that could help.
You most certainly can downgrade to 5.1.1. I did it a couple days ago myself. But yes you do have to flash a combination firmware and use safestrap, Now, I'm not much of a dev but I did make some pretty cool roms for my Moto Droid and later my Droid 3... Now, I remeber we had a safestrap on it, I almost swear it had some nifty was to boot other kernels... but that was just 2012 and I can't remeber.
As far as MM if you had a engboot kernel that gives root in adb, it would work exactly the same. Sorry I don't know much about the N920V, I have a N920T.. I got the Verizon one as a cheap whim on ebay. Plus it was gold lol.
I've got a way to get perm root but its so complicated and still can't touch /system or it reboots so not even worth it,
Either way, I found MM firmware that should flash, I might mess with it later.
Oh, and I certainly wouldn't flash another models anything. Like with Note8s they literally are all the same... I *think* I read something about the N920P being close enough it could boot our kernel or the other way around... something like that. But I think any of that stuff would just end badly.
gfunkmonk said:
You most certainly can downgrade to 5.1.1. I did it a couple days ago myself. But yes you do have to flash a combination firmware and use safestrap, Now, I'm not much of a dev but I did make some pretty cool roms for my Moto Droid and later my Droid 3... Now, I remeber we had a safestrap on it, I almost swear it had some nifty was to boot other kernels... but that was just 2012 and I can't remeber.
As far as MM if you had a engboot kernel that gives root in adb, it would work exactly the same. Sorry I don't know much about the N920V, I have a N920T.. I got the Verizon one as a cheap whim on ebay. Plus it was gold lol.
I've got a way to get perm root but its so complicated and still can't touch /system or it reboots so not even worth it,
Either way, I found MM firmware that should flash, I might mess with it later.
Oh, and I certainly wouldn't flash another models anything. Like with Note8s they literally are all the same... I *think* I read something about the N920P being close enough it could boot our kernel or the other way around... something like that. But I think any of that stuff would just end badly.
Click to expand...
Click to collapse
Hey man could you maybe give me a link to the combination file and safestrap as well as instructions on how to downgrade? There's permanent root on 5.1.1 and I'd rather have a rooted phone on lollipop than a stock one on nougat.
Hopefully you can mess around the MM firmware and figure something out. I think we're about the only two persons still interested in root on the version note 5 so we gotta stick together lol.
I'm definitely no dev or anything but I can contribute with info as I've searched every thread on XDA and other sides and I will help you test etc. Thanks again for everything you're doing man, you've stopped me from giving up on this device XD .
Yeah, so this is the combonation file I used: https://drive.google.com/file/d/1FEU3Msz3MQTCv5DnMe6zc8PlZERa2y6x/edit
So flash it in Odin and let it boot up all the way and whatnot.
use wondershare/mobilego to root from your computer or kingoroot or Kingroot 5.3.7, but you'll want to switch their junk for SuperSU. There's a script for that. Search "replace kingroot with supersu" the file is usually called mrw.zip
Go to the play store and install 'flashfire' If you have trouble with it crashing when you start it manually change the date on the phone to 2012, it'll work then, just believe me.
get safestrap 4.08 here https://forum.xda-developers.com/verizon-galaxy-note5/recovery-locked-safestrap-recovery-v4-t3915714
in flashfire click install zip, select the safestrap and when it asks hit mount system rw. Then hit flash, screen will go dark stuff will scroll by it'll reboot. when it does you'll have an option to enter recovery.
NOBLEROM is pre-rooted 5.1.1 it's here https://forum.xda-developers.com/verizon-galaxy-note5/rom-noble-rom-aoj3-v1-0-t3940543
flash that into recovery and then reflash safestrap before you leave, cause it'll be overwritten by that rom
and uhhh that's it. when you reboot you should be greeted with rooted 5.1.1
gfunkmonk said:
Yeah, so this is the combonation file I used: https://drive.google.com/file/d/1FEU3Msz3MQTCv5DnMe6zc8PlZERa2y6x/edit
So flash it in Odin and let it boot up all the way and whatnot.
use wondershare/mobilego to root from your computer or kingoroot or Kingroot 5.3.7, but you'll want to switch their junk for SuperSU. There's a script for that. Search "replace kingroot with supersu" the file is usually called mrw.zip
Go to the play store and install 'flashfire' If you have trouble with it crashing when you start it manually change the date on the phone to 2012, it'll work then, just believe me.
get safestrap 4.08 here https://forum.xda-developers.com/verizon-galaxy-note5/recovery-locked-safestrap-recovery-v4-t3915714
in flashfire click install zip, select the safestrap and when it asks hit mount system rw. Then hit flash, screen will go dark stuff will scroll by it'll reboot. when it does you'll have an option to enter recovery.
NOBLEROM is pre-rooted 5.1.1 it's here https://forum.xda-developers.com/verizon-galaxy-note5/rom-noble-rom-aoj3-v1-0-t3940543
flash that into recovery and then reflash safestrap before you leave, cause it'll be overwritten by that rom
and uhhh that's it. when you reboot you should be greeted with rooted 5.1.1
Click to expand...
Click to collapse
Hey man I got it to work and i just want to say thank you so much! My error before was that flashify wasn't flashing the zip properly. Flashfire did the trick and the ROM works now and everything. However I'm noticing a few bugs such as the WiFi password is forgotten after a reboot and the fingerprint sensor option no longer works. I know you weren't on development of Noble ROM but any idea on how to fix this?
Also I saw this customn rom - : Samsung OneUI Running Full Android 9.0 For the Exynos7420 Family! . Here's the link if you have time to have a look [ https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804 ] Do you think I would be able to flash it now that I have safestrap installed?
Also if there are any updates regarding getting permanent root on Marshmallow or ultimately Nougat think we could be kept in the loop on this thread? I'll probably just check in every few days. Once again thanks for everything you've helped me with.
Jherane said:
Hey man I got it to work and i just want to say thank you so much! My error before was that flashify wasn't flashing the zip properly. Flashfire did the trick and the ROM works now and everything. However I'm noticing a few bugs such as the WiFi password is forgotten after a reboot and the fingerprint sensor option no longer works. I know you weren't on development of Noble ROM but any idea on how to fix this?
Also I saw this customn rom - : Samsung OneUI Running Full Android 9.0 For the Exynos7420 Family! . Here's the link if you have time to have a look [ https://forum.xda-developers.com/note5/development/rom-floyd-n7fe-port-v1-0-t3882804 ] Do you think I would be able to flash it now that I have safestrap installed?
Also if there are any updates regarding getting permanent root on Marshmallow or ultimately Nougat think we could be kept in the loop on this thread? I'll probably just check in every few days. Once again thanks for everything you've helped me with.
Click to expand...
Click to collapse
Again the only kernels we can use are flashed through odin and have to pass secure boot check, So stock or engboot. Now I used to run that rom on my t-mobile version, till it bugged me so much that the camera is broken in the S8/N8 ports past Nougat. As for the wifi pass and biometrics, never checked it. Now, same thing happens when you root a Note8 (which is a similar process) and I believed it's fixed by flashing a Nougat bootloader. Unfortunatley, we don't have one, so basically both will be forever broken.
As for MM, you gotta remember I'm one guy and I'm simply doing this for fun. I don't always know what I'm doing exactly 100%, some of its straight trial and error. I'll probably try flashing stock MM and playing around a bit tomorrow maybe, but I wouldn't have high hopes for anything there either tbh.
I got a little excited because I found an engboot kernel for MM, but unfortunately, it's exactly like nougat. root is temp and trying to modify or remount /system leaves phone unresponsive and eventually reboots. However, I haven't noticed any random reboots like nougat.
gfunkmonk said:
I got a little excited because I found an engboot kernel for MM, but unfortunately, it's exactly like nougat. root is temp and trying to modify or remount /system leaves phone unresponsive and eventually reboots. However, I haven't noticed any random reboots like nougat.
Click to expand...
Click to collapse
Haha the journey continues, I figured it would be a huge task since most people said it was impossible XD. It's a little more stable than Nougat I guess because it's closer to 5.1.1 I think the issue is always gonna lie with getting system to mount r/w without freezing. Whatever code they inserted as soon as the system is altered the kernel panics unfortunately.
Btw Completely get you regarding the development. I didn't mean any disrespect, just meant in the event you had a breakthrough, wasn't so much out of expectation ?
I see you mentioned a S8/N8 port, I'm not the most advanced in the custom rom section so are you saying that the the noble rom you mentioned to me earlier today is an s8 or n8 port or is that another rom? If I can ask you to clarify?
Lastly about the Wi-Fi and Fingerprint, it sucks but I can live with that with everything that root offers. I'm gonna do a complete wipe and repeat the process to see if it goes away or search the noble rom thread to see if anyone had the same error.
Jherane said:
Haha the journey continues, I figured it would be a huge task since most people said it was impossible XD. It's a little more stable than Nougat I guess because it's closer to 5.1.1 I think the issue is always gonna lie with getting system to mount r/w without freezing. Whatever code they inserted as soon as the system is altered the kernel panics unfortunately.
Btw Completely get you regarding the development. I didn't mean any disrespect, just meant in the event you had a breakthrough, wasn't so much out of expectation
I see you mentioned a S8/N8 port, I'm not the most advanced in the custom rom section so are you saying that the the noble rom you mentioned to me earlier today is an s8 or n8 port or is that another rom? If I can ask you to clarify?
Lastly about the Wi-Fi and Fingerprint, it sucks but I can live with that with everything that root offers. I'm gonna do a complete wipe and repeat the process to see if it goes away or search the noble rom thread to see if anyone had the same error.
Click to expand...
Click to collapse
No, the Floyd rom you linked me is an N8 port. The Note8 came up because they way you root it is similar. Flash combination, flashfire, all that.
Now interestingly, 6.0.1 let me make a backup of /system without rebooting, 7.0 would not. So I got one idea here that could work, but it's going to take me a minute to test it.
gfunkmonk said:
No, the Floyd rom you linked me is an N8 port. The Note8 came up because they way you root it is similar. Flash combination, flashfire, all that.
Now interestingly, 6.0.1 let me make a backup of /system without rebooting, 7.0 would not. So I got one idea here that could work, but it's going to take me a minute to test it.
Click to expand...
Click to collapse
Well that actually sounds like progress. There was another thread on here about rooting the N920V, Idk if you've seen it for maybe situations where you get stuck. All the best.
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
gfunkmonk said:
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
Click to expand...
Click to collapse
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the binary would be bootloader would be unlocked. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
gfunkmonk said:
Can you send me/post a link? I have learned a couple things today, its progress but I don't know how much.
Click to expand...
Click to collapse
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the bootloader would be changed. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
Jherane said:
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the binary would be bootloader would be unlocked. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
Long story short: can we flash normal system.img over ENG bootloaders? I got "SYSTEM REV. CHECK FAIL DEVICE:1, BINARY:0" after reboot, so instead we can flash it as flashable zip. yes this work but we end up with bootloop. so what to do to pass this situation.
digging in ENG boot.img ramdisk I can see "export LD_PRELOAD libsigchain.so:liblptcp.so" and system/lib/liblptcp.so nor system/lib64/liblptcp.so is not there in stock 5.1.1, So take them from ENG firmware you will get fully working system over combo bootloader.
Attached Files
File Type: zip LD_PRELOAD-NOBLELTEVZW-SS-FF-flashable.zip
@gfunkmonk I'm trying to post the links here but it won't allow me. I'm gonna private message them to you. Also what do you get from this? I'm seeing on another thread where a DEV said this could fix the Wi-Fi and fingerprint issue because it would be a stock system image but the bootloader would be changed. Any help please. I know this maybe not your area of expertise but I asked on the thread and it seems to be dead. Thanks in advance.
Click to expand...
Click to collapse
Ahhh, I get it but no. That's what we did. used the ENG bootloader and kernel (combination files) then re-wrote the system image. Which speaking of, I've got to test out the new nougat image I made earlier.
Okay so what I'm asking is, the issue with the Wi-Fi and biometrics seems to be with the Kernel that's included in noble rom. I read somewhere where you can flash a system image from an earlier 5.1.1 firmware. Say AOJ3 and it should still work since it's close enough to stock and that should fix the Wi-Fi issue. My problem is I have the system image extracted but I don't know how to create a flashible Zip from the system.img so I can use flashify or safetrap to flash it. I saw the kitchen stuff but it's a little complicated for me.
The Dev for noble rom also created a script that would remove the parts of the system that wouldn't allow the normal system image to boot over the ENG bootloader so I'm wondering if this would work. I'm really just desperately searching for a fix to the wifi password being forgotten after reboot so if you have any ideas or workaround it would be greatly appreciated. I can live without the fingerprint scanner.
I saw something about maybe using Tasker to move the file containing the saved password to somewhere safe at shutdown and restoring it on reboot but I'm not sure of proof of concept so I thought I'd ask here first if it sounds feasible.
either flashfire or the safestrap twrp lets you flash an 'img' file... But remeber if it doesn't work you have to redo the entire process and flash & root the combo again