G5 Plus Help unroot help! - Moto G5 Plus Questions & Answers

Ok so I am just going to say I am a idiot and need some help. Please don't hate on me. I am not good with phone technology, but I followed directions to root my phone with TWRP & Magisk 12.0 and everything is working ok for the most part. The problem is I need a specific app to work for my job, but it fails to start due to the failed Safety Net. I would probably be able to figure out how to unroot it & relock the bootloader, but in my haste to root my phone, I did not backup the stock ROM image 1st. If anyone can help me figure out the next step to go back to a factory phone, I would forever be indebted to you. My specific model is an XT-1681 dual sim which I believe is from Brazil. I am in the US and not sure if I can use a different stock rom because I have tried searching to no avail. Please help if you can.
Thanks for your time.

There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.

Karlinski said:
There's a flash file for magisk which allows it to pass safety net. I saw it in the Lineage thread a few days back, but I don't know the exact origin.
Secondly, you can't relock the bootloader anyways. I don't know for sure if that in itself would cause safety net issues.
Click to expand...
Click to collapse
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.

ronefx said:
I appreciate the response, but I was able to finally locate the stock rom from a site linked on here & flashed and relocked the bootloader using ADB. Basically my phone is stock again & working like I need it to. I tried hiding the app in Magisk, but was unsuccessful. So I guess this post can be locked.
Click to expand...
Click to collapse
Which phone version you have retin?
Sent from my Moto G (5) Plus using Tapatalk

Related

LG-STYLO H634 CRICKET Supersu/xposed framework installation guide

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?

Download Unsuccessful MSG - KK to N910VVRU1BOAF

I'm trying to root, then unlock my Retail phone. I heard it can be done on BOAF 5.0.1. I downgraded my phone to KK ANJ5 (details on what steps I took, here)
I actually did a Factory Data Wipe twice before beginning, although the instructions said I only needed to do it once (doing it twice shouldn't hurt).
When I tap the System Updates button, it appears to start downloading, then after a few minutes, I'll get an error message saying "Download Unsuccessful". I've done this several times. Why is this happening now? I've cleared everything. Could Verizon have pulled the update? Can I install the two files manually? If so, please point me to the right direction. Thanks.
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I took the latest safe upgrade, I think it's BP1 or something like that., to 5.1.1. THAT worked.
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
rrjskj said:
So basically we have to be on 5.1.1 ??
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
JOSHSKORN said:
I'm just saying that's what for sure worked for me. KK didn't work at all. I don't know if you "have to" be on it or not.
Click to expand...
Click to collapse
I might give it a whirl if fix doesn't come soon. In the meantime could u point me in the right direction for the safe upgrade files and what Odin version ?? Thanks in advance.
Sent from my SM-N910V using XDA Premium HD app
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
Already did it I appreciated.
Sent from my SM-N910V using XDA Premium HD app
I've had it work on boaf, bpa, bog5. kk wouldn't work for me. using king root 4.0,.all unlocks (n4.n4.bin. n4.fix) worked for me. bpa (5.1.1)required the emotion kernel to boot. also returned my original Cid to use kies to restore all apps & data, then odined back again, unlocked, rooted ect. be patient
Rom-Addict said:
http://forum.xda-developers.com/not...nt/firmware-safe-upgrade-to-lollipop-t3313224
read everything!
Click to expand...
Click to collapse
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Sizzlechest said:
What confused me and a few other people in that thread is that you NEED to flash that kernel before the SuperSU linked there if you want to root 5.1.1 firmware. I thought it was just if you had taken the OTA 5.1.1.
Click to expand...
Click to collapse
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
went ahead and did the safe upgrade via Odin
Swapped out my MicroSD card for a different one I had laying around
Unlocked my phone
Powered Down (If I could, or remove the battery)
Removed the MicroSD card (otherwise it would boot loop)
Connected to My Computer
Boot to Download Mode (DOWN ARROW+HOME+POWER BUTTON)
Flashed TWRP using Odin
Reinserted the original MicroSD Card (Different SD card than what was used during the unlock process, the same one I was using prior to unlocking)
Booted into TWRP (UP ARROW+HOME+POWER BUTTON)
It prompted me to install SuperUser, so I did, it caused a bootloop, so I pulled my battery.
Removed MicroSD Card, plugged it into my computer and put SuperSU.zip and a kernel (See this post) zip file on it, re-inserted the MicroSD into my phone
Booted to TWRP (UP ARROW+HOME+POWER BUTTON)
Flashed the two files I'd just put on my MicroSD (Not sure if a reboot is required or if they could be done at the same time, I rebooted each time)
I did not clear cache/dalvik. Not sure if that was necessary.
This is all what got me to where I'm at, now.
JOSHSKORN said:
This is what I did (I think). Kinda hard to remember everything. For more information, read through the HOWTO thread. I think I started posting at about page 9.
...
This is all what got me to where I'm at, now.
Click to expand...
Click to collapse
For 5.0.1, you don't need to flash a new kernel, so that's why it works. If you want to upgrade to N910VVRU2BPA1:
Download N910VVRU2BPA1_StockRestore.tar.md5.7z and uncompress with 7-zip.
Flash with Odin.
Reboot phone back into Download Mode and flash TWRP with Odin.
Copy MultiSystem-Kernel_LP-5.1.1.zip and BETA-SuperSU-v2.67-20160203160253-TruncatedBoot-Fix.zip to the phone's internal memory. (Include xposed-v75-sdk21-arm-arter97-snapdragon.zip if you want XPosed.)
Reboot to recovery and flash all three in the above order.
Wipe cache and Davlik cache. Reboot to system.
Sizzlechest said:
Flash N910VVRU2BOG5_StockRestore.tar.md5 using Odin. It will upgrade you and you will be able to convert your phone to developer mode using the steps in the thread.
Click to expand...
Click to collapse
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Sizzlechest said:
There seems to be a bug in the detection routine on the program that changes the bootloader to developer when run on 4.4.4. If you want to follow the original directions, upgrade (first) to a 5.0.1 firmware since that is known to work with the unlocker and no new kernel needs to be flashed. If you get it to work for 5.0.1, then you can always upgrade to 5.1.1 or flash another rom.
If you want to try to go straight to 5.1.1 by flashing through Odin, you can try it. I'm almost positive you could downgrade to 5.0.1 if that doesn't work. (If you take the software upgrade through Verizon, you will have problems downgrading AFAIK.)
Click to expand...
Click to collapse
Thanks I just upgraded through Verizon to 5.0.1 and I'll give that a try and see if it works if not I'll safe upgrade to 5.1.1 thanks
Jimmy8 said:
I'm on 4.4.4 is this what I need to do a lot of other people are having the problem of getting the commands to work on 4.4.4 and are asking the question of do we need to upgrade some aren't getting answered and some are being told different things I'm sorry for asking but I need to know so I can unlock my bootloader thank you
Click to expand...
Click to collapse
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
JOSHSKORN said:
If that doesn't work, I recommend you rollback to 4.4.4 (you should be able to if you're on BOAF), then take the safe upgrade to BP1. Once you do that, you should be good to go. That is, I wasn't able to convert to developer mode on KK, but after taking the safe upgrade, I was. Maybe it had to do with the BOAF bootloader, and if that's the case, "maybe' you're ok doing it as is. Good luck. I'm sure you'll be back if it doesn't work, but if it DOES work, can you report back? In fact, I also have a thread in Q&A titled Root Survey. Please post there as well ONLY if you were able to successfully convert. I wanted to compile a list of users that were able to convert, where they were before they started, what worked, what didn't, and so far, all what I'm seeing is, is that starting from KK doesn't work, although we were told all along to keep KK. I also heard one user said that he had taken all OTAs to 5..1.1., still made the conversion process work, BUT, his phone was a developer phone to begin with but he accidentally locked it with a Retail ROM. I'm kind of a noob, myself, but from what I do know, I don't recommend taking any OTAs anyway past BOAF, otherwise the conversion "might not" happen, but there are a lot of people who have taken all OTAs so we'll see what happens with them.
Click to expand...
Click to collapse
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Jimmy8 said:
I can't even get king root to root it constantly reboots my phone during rooting process I've tried different versions and it doesn't matter do you have any suggestions or point me in the direction to roll back to 4.4.4 I've been out of the game for a while so I've forgotten a lot of stuff on how to do this thank for all your help so far
Click to expand...
Click to collapse
Believe me, I'm with you right there, as well, been out of the game for so long. Thanks Verizon Retail locking. Anyway....
Where are you right now? Your Android version/Build Number.
joshskorn said:
believe me, i'm with you right there, as well, been out of the game for so long. Thanks verizon retail locking. Anyway....
Where are you right now? Your android version/build number.
Click to expand...
Click to collapse
5.0.1 / n910vvru1boaf

Moto X Style (XT1572) Rooting issues - No Wifi

Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
stumbows said:
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
Click to expand...
Click to collapse
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
acejavelin said:
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
Click to expand...
Click to collapse
I didn't take a backup as TWRP broke during the process but the root worked. I am only on 6.0 so is that ok to resolve? I can't see the baseband details at the moment as I am boot looping due to trying to follow another guide on resolving my issues. Trying to load a stock rom on to my device through TWRP now. Will report back soon.
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
stumbows said:
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
Click to expand...
Click to collapse
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
acejavelin said:
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
Click to expand...
Click to collapse
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
stumbows said:
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
Click to expand...
Click to collapse
Nope... Not a clue, sorry.

NO OEM unlocking with S off

I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
anderson96007 said:
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
Click to expand...
Click to collapse
If its S-off already there is no need for the bootloader to be unlocked.
Thanks
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
anderson96007 said:
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
Click to expand...
Click to collapse
The 10 is a little different.
Locked and unlocked work basically the same, and it's my understanding it's suggested to be S-OFF locked from Sunshine crew.
I've been S-OFF locked since release of vzw S-OFF and everything works perfectly.
Hope this helps a little.
Just doesn't work
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
anderson96007 said:
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
Click to expand...
Click to collapse
I would leave the phone locked.
If you plan on flashing Venom, and you have already flashed twrp, there really is no need to root the current rom. Just make a backup of it in twrp (just in case) and flash Venom. Just make sure you select the correct firmware that matches the phones firmware in the aroma installer.
OK will give that a shot tomorrow thanks
If you're S-OFF. You shouldn't have any issues flashing the latest N firmware for your device, latest TWRP, and then latest N ViperROM. And since Viper comes pre-rooted, you will only need flash ViperROM.
Get a hold if you need some help, I'll do my best to assist.
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
anderson96007 said:
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
Click to expand...
Click to collapse
My HTC 10 is S-OFF Locked bootloader, this is what Sunshine crew suggests, and works the same (on the 10, previous devices are different) as unlocked bootloader.
It seems you are in a simple bootloop. Would need recovery log to see more, and Viper devs would be able to understand their stuff better than myself.
I do have suggestion as to what I would do.
You are on 6.0.1, you should update to the latest Nougat 2.41.605.18. Either by flashing the firmware, or flashing the RUU. Read up on encryption with Nougat.
Everything you said you did sounds correct to me. And as are as selecting the correct firmware in Aroma, that is for the fingerprint to work, and can easily be fixed if you accidentally select N instead of MM.
I hope this helps in some way.

Shortcut to being rooted on N910VVRU2CQI2

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.

Categories

Resources