Related
but none of them seem to work quite right...
-i tried one from the thread that was titled something like "Everything You Need To Know About the SCL22"...
---... but when i finished my root-checker app told me that i did not have root, and busybox/terminal weren't installed correctly.
-i then tried one from different thread that required manual terminal input "using su, etc."...
---... but when i got to the point of inputting the terminal code, it told me that it could find root, and rather than having a #-symbol, i got the $-symbol...
i also tried the first two methods again , two more times, each; to make sure i wasn't fowling up someplace. meticulously followed each of the steps, with same result.
-and then, finally, i tried CF-autoroot but could not find my model number, and was getting impatient, so i tried just the standard N900 one and got a soft-brick, which i am currently trying to restore...
-i only wish to remove bloat, install a custom rom (don't care about NFC, don't care about Knox, etc.), and install custom apk's. but meh :/
does anyone actually have a real, working root that i can follow clearly? lollipop or otherwise? in my reading of these forums, it seems the SCL22/SM-N900J (au Model) has been neglected.
i read through every thread i could find on the matter, so i feel like i really tried to root it myself and fix it myself, before asking for assistance :/ any help?
DK
Old post... but I have been looking for some SCL22 solutions myself, so I thought I'd help here.
I have root on my SCL22. Busybox works. I may have done more, but as I remember it, all it needed was:
Install:
twrp-3.3.1-0-hltekdi.img.tar (Installed via Odin3 v3.12)
Booted into recovery mode with TWRP. Installed (via zip, not image)
SR3-SuperSU-v2.79-SR3-20170114223742
That SuperSU copy, I've had for a while. Dunno if it can be found again, so I'll leave a copy here.
Yeah... that's it! There may be better software than SuperSU, but this works 90% for me. I wish SuperSU had the option for me to select software to give root permissions to; instead the app has to request root access, and then SuperSu will pop-op a notification to grant/deny root permissions. Sounds fine until the software you want to give root, doesn't ask for root (so then it never gets it )
But yeah... root. Enjoy.
ok, so there are some things i've found out by doing some research and combining what i found on here with the issues that some people were having with the Cricket version of the LG Stylo, and would like to share with you guys. while i was rooting my phone with kingroot, i noticed a threat that discussed that using supersu me and supersu wasn't an option without soft bricking your phone with a boot loop, after some research and trial i figured out how to get around the problem. The issue was the uninstallation of kinguser app form the phone, this is because using supersu me uninstalls kingroot and replaced it with the superuser binaries, but it leaves some core files of kinguser behind which causes errors, an if you keep your phone on, you'll notice that you'll start getting error messages for an about kingroot permission and all types of errors until your phone starts to freeze and act up. there is an easy fix for it all that worked for me, and would like to share this information and help people having this issue.....
I'm posting this as a hint for those who needed the help with installing xposed on cricket model LG STYLO only running 5.1.1
so to begin, download system repair 2016 and apps2sd from play store, kinguser directly from their site so it will be the latest version,,,root your phone,,,,,don't delete the kinguser apk you downloaded you'll need it for later,,,,now install supersu me from the play store and open and run it, it'll uninstall kinguser and replace the binaries for superuser, this is where its gonna become tricky,,,,,,download supersu and run which will ask for update of binaries also let it finish updating and uninstall the supersu me control,,,,,now open apps2sd and clear the davik cache and other caches without restarting,,,,then run system repair 2016, it'll show that you had a few errors because kinguser hates the fact that supersu me uninstalled it and left messed up configurations on your phone, then clear the davik cache again, now you have to use the same kinguser apk you get at the start of the process and reinstall it to your phone, or else you will be getting a boot loop issue......for some reason even though all the caches are cleared and the system has been checked for errors, the kinguser app installs itself as a system app, a dependency if you will, like a basic LG/Cricket app that if you uninstall will cause errors, so but reinstalling it we stop that problem, you can run it but don't need to activate the root option of kinguser......this will cause the kinguser permission errors to stop also from this point only you can restart your phone,,,,,now you're able to install flashfire and xposed frameworks, and even restart your phone without worry of boot looping since there isn't much support for the LG-H634 stylo model.........:angel::angel:
hope this was helpful for you guys that was in need of replacing kinguser, and installing xposed framework, i've not tried anything further with the twrp install but keep a look out for the names "vegito6" "vegito69" ....and wish me luck on twrp
#humbleprogrammer
seems i've got to post at least 10 times in order to post outside pics
So I rooted my same phone via kingroot and it has the purify apo along with it. Also having problems with errors and stuff. I'm gonna follow your method see what happens. This being #2 stylo after bricked the first one and couldn't find kdz. Anyway I'll get back to ya let me know if you have anymore info thanks for the help man.
orphan tear maker
Help Please
Drumdestroyed said:
So I rooted my same phone via kingroot and it has the purify apo along with it. Also having problems with errors and stuff. I'm gonna follow your method see what happens. This being #2 stylo after bricked the first one and couldn't find kdz. Anyway I'll get back to ya let me know if you have anymore info thanks for the help man.
orphan tear maker
Click to expand...
Click to collapse
got bricked today, anyone any luck with something??
markos638 said:
got bricked today, anyone any luck with something??
Click to expand...
Click to collapse
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
vegito69 said:
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
Click to expand...
Click to collapse
I got bricked, trying to change from kingroot to SU, I´ll really appreciate when you find solution give us instructions on how you did it!!
Have you guys any luck with a recovery method? And think you for helping I'll do my best with what I have. Also idk if I mentioned it earlier but when I reboot lg symbol appears but (authentication failed #9) appears below it. It was roted via king root and didn't o anything but remove some bloatware. Idk God be with you man cuz this is a bummer
vegito69 said:
ok i'm not sure how you guys got bricked, but i just got bricked using flahfire to create backup, so don't use that app as of yet, but anyways working on the replacement now, gonna be trying to create a restore img or flashable zip for the cricket stylo.
Click to expand...
Click to collapse
I'm pretty sure that you ended up with brick because you didn't unlock your bootloader before backing up. My girlfriend did the same thing. As of right now I'm trying to figure out If there's a way past the bootloader or at least a way to do everything the bootloader can do without unlocking it.
Original Firmware
Can we not flash the original firmware via download mode ? I had this phone (bought from a friend, cricket sim unlocked, phone bricked while i was playing around. )
I'm not super familiar with LG phones, but i keep hearing about a KDZ , is that some kind of official image format ?
If we can flash it for stock via download mode, can someone direct me as to where I might find instructions for our variant of the device, please ?
I was able to replace Kingroot with SuperSu using a guide I found on a website called w0lfdroid, I think. I just Google 'replace Kingroot with SuperSu and it was the second one down (I'm a new user so I can't post the link). I think it worked pretty well, but I'm still not able to flash TWRP or start the process to get xposed. If I can't get it, I might unroot and try the process again with this method.
as anyone with brick try this http://lg-firmware-rom.com/downloads/lg-g-stylo-h634-stock-tot-firmware-v10g/ , they offer files for unbricking, $40 bucks
what do you guys think
markos638 said:
as anyone with brick try this http://lg-firmware-rom.com/downloads/lg-g-stylo-h634-stock-tot-firmware-v10g/ , they offer files for unbricking, $40 bucks
what do you guys think
Click to expand...
Click to collapse
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
vegito6 said:
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
Click to expand...
Click to collapse
works just fine!!!! lg stylo is back!!! thanks vegito ,....
vegito6 said:
works great, after flashing with LG Flash tools tot method just take out battery and wait 5sec, and put it back in and turn on, android logo will show and then it will boot normally, now i'm back to working on the supersu install methods to help people from bricking, wish me luck . also backing up boot img and then trying to use super sume to switch to still will cause boot looping to my knowledge. got 2 phones working on it, thanks to our annonomous LG guys for the unbricking
https://mega.nz/#!95ZSCARR!dWAG0bd5zi3DQUal3gfB4nMH-zmIR0H0kdCXBdWGLQk
password = wang276634161
Click to expand...
Click to collapse
Great job man. It is people like you who keep the community going.
Su binary installation failed!
Mooose-Nuckle said:
I'm pretty sure that you ended up with brick because you didn't unlock your bootloader before backing up. My girlfriend did the same thing. As of right now I'm trying to figure out If there's a way past the bootloader or at least a way to do everything the bootloader can do without unlocking it.
Click to expand...
Click to collapse
well not really, because if you go into the developer options there is the oem bootloader unlock you can select, not sure but i've got a cricket and boost version i've been working on it for a while, for some reason the phone doesn't like the way SU gets injected into the phone, and writes things to the wrong areas, i've been playing with some scripts for superuser installers from zip, hopefully i get a hit.
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
jxs714 said:
Great job man. It is people like you who keep the community going.
Click to expand...
Click to collapse
thats the life of us programmers and developers thats trying to get better lol, we just share the knowledge passed down lol
vegito6 said:
well not really, because if you go into the developer options there is the oem bootloader unlock you can select, not sure but i've got a cricket and boost version i've been working on it for a while, for some reason the phone doesn't like the way SU gets injected into the phone, and writes things to the wrong areas, i've been playing with some scripts for superuser installers from zip, hopefully i get a hit.
---------- Post added at 09:48 AM ---------- Previous post was at 09:47 AM ----------
thats the life of us programmers and developers thats trying to get better lol, we just share the knowledge passed down lol
Click to expand...
Click to collapse
I noticed there is no solution posted. I recently bricked my phone and fixed it, thanks to you. I was simply wondering of there has been progress with getting the framework installed. Your help is much appreciated.
So I'm sort of confused... I cannot install xposed, and can't seem to find a work around. I am rooted but not with kingroot. I used a one click root tool on pc, and works great... Using su that is suggested using in this guide, so no trace of king root. Idk, could someone give me a quick run down on how to install xposed?
So no luck with installing xposed yet
So far I am rooted with Super SU and have exposed installer I'm just having a hard time getting the framework installed. I do not have custom recovery installed. Is there any way to flash the framework zip file with like flashify or another app like that?
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
What version are you running? B20/B27/B29
If you are not tech savvy, do not attempt the root method. It's for advance user and too many people have bricked their phone already. Just read the threads and you will know what I mean.
S8ntsHaz3 said:
What version are you running? B20/B27/B29
Click to expand...
Click to collapse
I'm running B29.
And yes I can probably guess the amount of people who bricked their phones. But what if everything were to be laid out simple and I follow the directions in every respect? I'm not going to start rooting until I know what I'm doing. So don't worry. I'm stupid but I'm not THAT stupid.
No your fine lmao I started with this phone so we're pretty much same level. As to my understanding it is possible but I would wait just a bit for the b29 stuff to come out.
Don't worry, you're not the only one. I've been reading these tutorials and it's all gibberish, lol.... Every phone I have has been rooted within the first day, this phone I've had over 2 months, and I still can't get it. So you're not alone, lol...
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Bolandk said:
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Click to expand...
Click to collapse
I'm looking closely at this phone now myself...
I've seen the bootloader thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I'm only interest in this if I can successfully unlock the bootloader and stock root is possible...from what I've read, BOTH can be done. According to the root thread, the model I need (A2017G) is listed as unlockable, correct? What's the difference between a2017g B02 and B03??
RoOSTA
totalFX said:
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
Click to expand...
Click to collapse
OK I have read far too many of these questions here about root on B29 - so here goes.
1. Go to the ZTE website, download the stock B20, and install it.
2. http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 use this to get TWRP installed on your phone - don't worry about root.
3. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 UNLOCK the bootloader
4. http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 flash boot file, system file, and SuperSU 2.65
Now please relax - anyone here with any dev skills whatsoever are neck deep in other projects (like CM13). B29 hasn't been out long and the only stock image we have from ZTE is B20, which doesn't give us a ton to work with
I also very new to android smartphone and I also feel so so out of place too.
I wish someone make a video how to root this axon 7 phone.
search around youtube jailbrake iPhone is so easy root samsung phone is so easy.... but root axon 7 nothing
I love axon 7 so much now but if I know it's so hard to root i'm just gonna buy samsung phone .
so F..... tired of this youtube ads
ads block is the only reason why I want to root
and that is the only reason why I jailbrake all my ideviese
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
tasar said:
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
Click to expand...
Click to collapse
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Click to expand...
Click to collapse
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
rczrider said:
[*] *Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
Click to expand...
Click to collapse
Thanks, reboot disemmcwp fixed my write access to /system
rczrider said:
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
Click to expand...
Click to collapse
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I think ZTE will eventually put out a bootloader unlock without killing the warranty. But, yeah, either way it's easy enough to do it on your own now.
rczrider said:
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
Click to expand...
Click to collapse
Thank you; thank you, THANK YOU!!!!! I tried for an hour or two, using both ADB and Terminal Emulator to apply this "reboot disemmcwp" fix, and I just couldn't get it to work (I'm on B29). Then, I saw your instructions to use TWRP and followed them, and it worked first time, like a charm!
Thanks again - I'm a very happy camper. You da' man, LOL!
Dennis
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
Wasn't it much easier if you install TWRP first, then root it using magisk?
Thank you for thatsuggestion. I didnt know that I can install TWRP before rooting the phone first
I had trouble rooting with CF auto root on my SM-N910F, not exactly the same problem as you.
Then I did some reading into other root alternatives and basically found out that SuperSU, which CF autoroot uses, was sold to a Chinese company called Coding Code Mobile Technlogy sometime around 2015. As it's closed source and Chinese firms particularly have been known not to respect user privacy, I would go with Magisk instead as it's open source, plus I have had zero problems with it so far.
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
hgroth said:
Thank you so much for your help. I am not an expert with the rooting, but done a Note 4 Verizon before and it wasnt easy.
Now I got the 910F and I want to make sure I dont brick it. Can you tell me where I can find exact instructions? I already
downloaded twrp-3.3.1-0-trlte.img is that the correct version for my 910F ?
Click to expand...
Click to collapse
I'm no expert myself, in fact I'm new to it! but I'll share with you what I know.
I basically flashed TWRP to the phone using Samsung Odin (Loads of videos Youtube showing the process) Then I used Android Debug Bridge to push the Magisk flashable .zip file over to the phone (I think I could have actually just copied it into /sdcard - Androids name for internal storage bizarrely - through windows just like any other external device) before booting into TWRP on the phone, and simply selecting "install", selecting the Magisk .zip and flashing it from there. Then I just booted into Android and I seem to remember either the Magisk manager app will now be in your app draw, or alternatively there is an app placeholder there which allows you to download the full manager app, I can't remember which it is but small difference. Here is a link to the official Magisk thread on XDA which you can use find the download links you need. Take note that right at the top it states...
"Magisk does NOT have a website. Do NOT download Magisk from unofficial sites"
When I did it I downloaded Magisk from one of the top websites that appears when you search "Magisk" in Duckduckgo (they look very official) however after I read the notice above in the official thread I wiped the phone and did the process over again just to be safe! I hope that is helpful. :good:
hgroth said:
I am trying to root my SM-N910F using CF Auto Root but when the phone reboots, I noticed that
it says boot image not found, aborting........ and the phone will not root. Is there anything I am doing
wrong or that I missed to cause this issue?
Click to expand...
Click to collapse
did you remove battery after the flash?
Thanks for your help. Yes I tried that after the 2nd attempt when I set Odin not to auto reboot, I removed the battery
and then booted the phone after inserting the battery with the same result, not root. I am wondering why it says
boot image not found, aborting....... since I loaded the CF Auto Root which should be the correct boot image