[GUIDE] Rooting the OPX without unlocking the bootloader. - OnePlus X General

This method uses KINGROOT, no mingling with the bootloader.
STEP 1
Just google "kingroot" (kingroot.net) and dowload the latest apk, open the app and after the initial welcome screens click on the button in the bottom that says "TRY IT", give it some time 4-5 minutes.
Thats it, your device is rooted, just like that.
BENEFITS OF THIS METHOD.
Since you have not unlocked the bootloader once you choose to unroot the device(why would anyone ) no one will be able to tell if you actually rooted the device.
RECOMMENDED (Like seriously recommended)
Once you get the root access install the app "Partitions Backup" by the one and only "wanam" and backup the partitions highlighted in yellow(at least these three modem, modemst1 and modemst2) these are your devices efs partitions. They will be the only thing that will save a lot of trouble if you manage to corrupt your efs partitions(I've been there people, trust me not a pretty situation!:crying, copy these safely to your ext sd, computer, email yourself a compressed copy(this way The NSA will also get a copy which they off course never looked into, so now it's like completely safe).
One more optional thing is to uninstall the sister app of kingroot "PURIFY" its really an annoying little app(imo at least).
OTA
This method also disables ota updates.
So the only way to update is to dirty flash the base stock rom dump throught stock recovery(which i forgot to mention as a benefit you have not mingled with) and then go ahead and sequentially update your device and then eepeat the root process in the aforementioned manner.
If I've made any mistake please do correct me(my first thread, my first guide) , if you have anything to add please let it out.... Thanks for reading, and be kind to each other. :angel:

Will this wipe my device?

I'm going to close this thread based on the fact that there are multiple threads on this same topic, including an active thread that can be found linked below.
http://forum.xda-developers.com/oneplus-x/general/guide-root-oneplus-x-twrp-pc-t3251027

Related

Root my phone

What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
What's the best way to root my so I can use setcpu? I only want to do that and keep everything I currently have the same. Is this possible and if so how?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
If I do a full root does it delete everything that I have? I have never tried it an I now looking Ratbags site that has a full outline on how to do it. All I want to do is use setcpu without deleting my stuff
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Most of the root methods involve unlocking the bootloader with the "fastboot oem unlock" command as the first step.
That's the command that erases your phone.
Any method that has you do that command will erase your phone.
If the method above works as expected, it will root you without erasing your phone. Shrivelfig did it without harm to his phone, but he had already been rooted the old-fashioned way.
I would certainly backup my data that I could before doing any root method, but this one seems like it's 99% safe.
Use at own risk, of course, but that's true of all the methods.
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
B3arfruit said:
OK last question what is the easiest way to backup your phone? How?
Believers b3ar fruit with their Nexus S.....
Click to expand...
Click to collapse
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
distortedloop said:
Without root, your options are limited and incomplete.
The only stuff you'll be able to backup are items that are stored on the sdcard. Some apps put their data there, some don't, some mix it up.
To backup the sdcard is as easy as usb mounting the phone and dragging/dropping the stuff you want to save.
Click to expand...
Click to collapse
Your the man thanks bro I'll let you know if it works. Hope my phone doesn't crash on me
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
B3arfruit said:
Man I suck I followed a lot of different direction and still can get my computer to recognize my phone when trying to root....
Click to expand...
Click to collapse
You're putting the phone in fastboot mode? It's got the white screen?
You're using the proper commands fastboot? What message does your computer show? Are you Win, Mac, or Linux?
distortedloop said:
CAUTION: experimental/theoretical until someone tries it on a virgin phone, but...
Shrivelfig's found a method that might let you root without unlocking your bootloader and erasing the phone.
Download these two files:
clockwork recovery
su-2.3.6.1-ef-signed.zip
Place the su zip one in your sdcard.
Place the other on your computer.
Put your phone in fastboot mode (power off, then hold volume up and power key at the same time until the phone boots to a white screen).
Use fastboot to boot the phone into the clockwork recovery:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
If you're not sure how to get fastboot working on your computer, follow the instructions that Allgamer gives in this thread, but don't do the oem unlock command!
Once in clockwork, flash the su file to the phone by following these steps from this thread:
select install ZIP from sdcard (power button to apply)
select choose zip from sdcard (power button to apply)
select su-version#-signed.zip file you downloaded earlier, and apply it
select yes - install su-version#-signed.zip
confirm it says "Install from sdcard complete"
select go back
select reboot
Reboot.
If it works, you should be rooted, with a locked bootloader, and none of your data erased.
That said, never hurts to have a backup of your precious data on the sdcard that you can copy over to the computer.
Please let me know if that works; I've not seen anyone who wasn't already rooted report back on the success or failure of this method.
Click to expand...
Click to collapse
Just tried it on a new Nexus S, worked perfectly
I rooted using this method last night. From start to finish, 10 minutes. I have full root capabilities.
Sent from my Nexus S using XDA App
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
zorak950 said:
I've been somewhat discouraged from rooting my Nexus S because of the apparent hurdles to rooting. When I rooted my Vibrant it never erased any data or stopped me from getting a firmware upgrade. Sure I lost root after upgrading, but all I had to do was run it again.
With the NS, when I hear people talk about root methods erasing their phones and preventing them from upgrading, it worries me. Sure I can back up all the data I really care about, but why should the NS have these difficulties when the Vibrant didn't?
Click to expand...
Click to collapse
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
kenvan19 said:
Actually, you haven't been keeping up with the rooting methods. A few weeks back someone figured out how to push a recovery and install Superuser without unlocking the bootloader which is the part that wipes your phone.
The reason it is so easy to root most phones is that they use an exploit in the Android system to grant Superuser priveleges while on the Nexus S we do it the legitimate way. I've not heard of root preventing people from updating nor does it really bother me. I run custom roms and therefore wait for the updates to be integrated in my custom ROM. I'm sort of confused why someone would buy a Nexus S, a phone Google has said was designed to be hacked to pieces, and leave it stock.
Click to expand...
Click to collapse
Because it's the fastest, cleanest, most up-to-date Android device of its class on the market. Custom ROMS are all well and good, but they're hardly the only reason to get the phone. Indeed, there are a ton of phones out there with arguably equal or better third-party ROM options at present. Anyway, to say Google designed the NS to be hacked to pieces is perhaps a bit of an overstatement; to my knowledge all they said is that they deliberately left open a way to root the phone, and even at that, it wasn't exactly a consumer marketing point.
Not that I'm badmouthing rooting, installing custom ROMS, or whatever else people do to their phones. On the contrary, I think it's fantastic. But ultimately, I object to the idea that there's a "wrong" choice when it comes to making those modifications. Different people have different priorities, concerns, and levels of comfort with various procedures, and the NS is a great phone no matter what you choose to run on it. I'm probably on the low end of the spectrum with respect to my interest and comfort in modding as far as people who post with any regularity on these forums go, but bear in mind I'm also probably a great deal more engaged with it than the majority of users, many of which may not even make full use of their phone's basic features, let alone think to try making their phone do anything that the top-layer UI doesn't facilitate.
Clockwork link not working
suhas_sm said:
Clockwork link not working
Click to expand...
Click to collapse
Try this one: http://mirror1.kanged.net/recoveries/recovery-clockwork-3.0.0.5-crespo.img
or go straight to koush's blog: http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
worked for me as well, on 2.3.2 without erasing anything.
thanks!
I concurr, the nowipe method works here (UK SNS fro Carphone Warehouse on 2.3.2).
All we need now is google to fix the issues (rebooting in particular).
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Paparasee said:
Hey, thanks ... if this works without unlocking the bootloader, I'm trying it
Click to expand...
Click to collapse
It works. Try it. Full thread on it that I'll update as things change here.
Paparasee said:
Two things before that though:
a) Please let us know if you can update to 2.3.3 after this or if you have to wait for a new image.
Click to expand...
Click to collapse
We won't know for sure until the 2.3.3 update comes out and we can examine its contents and what it does. There's no reason to expect that Google will do much differently in terms of the bootloader or recovery than they have in the last two updates, especially since they've said in the Google blog that the NS was designed to be easily unlocked and rooted.
In the prior two OTA updates, you could update with no issues other than your root being broken, but it was as easy as just rebooting into clockwork and reinstalling the su update zip.
The only people who had issues updating prior OTAs after this kind of root were folks who had messed around with applications in the /system folder (such as replacing the Market or Gmail apps with some modded one). That can be worked around easily and is discussed numerous times in a couple of threads.
Paparasee said:
b) Can I rewind and get my phone back to the unrooted version as it was when I bought it? If yes, can someone write the steps for that too?
Thanks
Click to expand...
Click to collapse
All rooting with this method does is add the su binary to /system/bin, the superuser.apk file to /data/app and change permissions on /system/bin. If you install busybox (which you really need to do for root to be most effective) it will add it's own files and some symlinks.
Several easy ways to reverse the process:
Restore/flash a nandroid or stock rom image that's not rooted. (Try making one after getting into Clockwork and before flashing su-update.zip.)
Use terminal/adb, the Settings/Applications app or the Market to rm and/or uninstall the su binary, the busybox install, and the superuser.apk as well as any root-enabled apps you installed.
There's more details if you need them in another thread here or Q&A section. You should be able to find them with a search on the terms "rm /system/bin/ root".

[Q] Best first steps with a new tablet

Ultra Noob here
So I had my first android-TF700 for about 10 days. Played around with it, read around this site and realized it was a tablet for someone with experience.
So I now have an N10. Charged, not even turned on yet. What should be my next steps? I see a couple toolkits,an auto root, and ASOP-
What would you suggest a noob start with?
I know, I know, turn it on
Thanks!
Depends on what you want to accomplish with the device. If you want to try or at least gain some understanding as to the different features you might be interested in, read the first post of the different ROMs available and see if anything sounds enticing.
I personally use me for taking media with me on the go, be it news or videos, so I don't have to carry a laptop around. I'm on CM10.1 right now but cycle through every rom to see how everything works. Good luck!
Sent from my Nexus 10 using XDA Premium HD app
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
rauschkugl said:
First step is unlocking the bootloader and installing root and a custom recovery. Even if you don't need it at the moment there will come the time you want to try it. When you unlock the bootloader you will lose all your data so it's the best if you do it at first when you get your tablet.
Click to expand...
Click to collapse
And how do you unlock the bootloader and install root?
What do you mean a custom recovery?
Are there other ways to root the device with out wiping it? Seems like most android smartphone you can load up an exe or something to shift the su app around or something.
Thanks.. (still waiting for my N10 to arrive.. meanwhile.. still playing with my ICS Bionic)
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
rauschkugl said:
There are tons of threads here about unlocking the bootloader, rooting and installing a recovery like teamwin or clockworkmod.
Click to expand...
Click to collapse
Found the threads. Look easy enough to follow. Something I'm not understanding . What does it mean to install a recovery? whats the purpose of that. I've search and (at least not yet) found a good description of what/why that it. I'm sensing that devices are different (duh!) and I didnt need to install a "recovery" on my Droid Bionic when I rooted it, but this N10 must be different.
With the custom recovery you're able to install zip files, make a backup of your Rom,... You can't do that with the recovery that comes with the nexus 10.
Recovery is like a separate system that you can boot to, if you want to mess with the main Android OS. Like rauschkugl said, you can boot to a custom recovery to flash different ROMs that are distributed in flashable ZIP files. You can also make (or if anything goes wrong, revert to) a complete backup of the device's internal memory.
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
Great questions. You are one step ahead of me on my new N10. I've not turned it on yet, really wanting to, but I dont want to do much to it, until after I unlock/root/ and learn how to make backups. Though since i've got a TBpro license, I'll probably use that. I dont want to tweak the OS. so I think I need root just to be able to run TBpro. I just want to be sure I'll still get OFA updates, and I want to learn more about if and how backup work for a multi-user N10.
EraVulgaris said:
Ok I am rooted and unlocked with mskip's awesome toolkit and DroidModderX video which really helped.
I picked all in one click option and choose TWRP. I fell asleep when I got to TWRP, so I guess I will have to reboot to the recovery page to pull it up.
After that I have no idea what to do I really haven't played with the N10 much. I was planning to leave it stock for awhile (as suggested by rauschkugl).
Do I need to do any backup or anything with TWRP if it's a new tablet? if so what and how ? Please point me to a tutorial for noob types.
Other question is I have a system update and 6 new updates waiting for me to install, can I go ahead and do that rooted and unlocked with stock ROM and no TWRP backup yet?
Thanks!
Click to expand...
Click to collapse
I would suggest straight away that you perform a backup with TWRP, so that if you decide to delve deeper into ROMs and playing with your system files, you'll have a completely stock backup to rely on. Simply boot into recovery and select 'Backup', then you can rename the backup file if you want, then swipe the slider across and wait, then you're done!
When it comes to system updates, you'll most likely have to use your root toolkit to unroot the device, else the update will fail. You can however continue to update all your apps as you normally would. Hope this helped
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
EraVulgaris said:
OK
So I kinda started from the beginning of Droid ModderX's video, picked yes to update the toolkit i had donated- (got an update) accessed TWRP (pain to get to- could I download goomanager now after I have TWRP?) and backed up my stock set up just as you said Huggogguh :good:.
Then I went ahead and touched "install system update" that was hanging around in the upper left corner of my tablet (I'm being really specific for other noobs) and it updated my system to 4.2.1 and my apps. Build number changed to JOP4OD
Looked at root checker app. I am now not rooted, so I will go back through toolkit and choose 4 once I am in fastboot mode to reroot I hope:fingers-crossed:.
Thanks!
Click to expand...
Click to collapse
Sounds like a great success then so are you saying that you performed the system update while you were rooted and you retained the root access?
Nope. Got the OTA system update and it knocked me off root. But I got it back easily with the toolkit.

[Q] Second-hand N4, some questions?

Hey!
I recently bought a second hand Nexus in decent shape.
Im really a newbie when it comes to roms, rooting, bootloader etc and Im not really interested in it either!
So what I did when I got the handset was to google around for how to restore it to factory edition. (The other guy seamed to have used other Roms and such)
I found a tool by Wugfresh called Nexus root toolkit and used it to lock bootloader, restore factory image (I downloaded myself from google) and unroot the phone.
Now I have some questions! Is the tool safe? Since Im a complete noob I have no way of telling if the rom etc is legit, could there be spyware or such on my phone now?
Since Kitkat is comming OTA soon, would that be a good way to check if the phone is "original"? I mean, if i get OTA 4.4 from google, will that make sure my handset is completly as it was out of the box, and nothing hidden can be there?
This is a screenshot from my "About phone" maybe you can verify that this is correct?
https://www.dropbox.com/s/17b4i9wi1wypsgl/Screenshot_2013-11-14-13-04-53.png
Very thankful for your help!
I found a tool by Wugfresh called Nexus root toolkit
Now I have some questions! Is the tool safe?!
Click to expand...
Click to collapse
Why don't you ask him personally?
Toolkit being safe or not depends on who you ask. It could cause problems and sometimes it's better to learn to flash the device manually. For some its better to use toolkit since they can potentially cause more problems doing something wrong manually. If you want to flash the factory firmware manually, the instructions are in these steps: http://forum.xda-developers.com/showthread.php?t=2010312
Since Im a complete noob I have no way of telling if the rom etc is legit, could there be spyware or such on my phone now?
Click to expand...
Click to collapse
If you install the factory image from here https://developers.google.com/android/nexus/images, then its the official Google firmware. However, these OTA packages are original as well: http://forum.xda-developers.com/showthread.php?t=2145848. To tell if other third party custom roms are safe, I don't program myself, but reliable ones are open source and have the sources available to the public that you can use to compile yourself. You can use hash checking to make sure if a file is original, Google gives you the hash values for their downloads.
This is a screenshot from my "About phone" maybe you can verify that this is correct?
https://www.dropbox.com/s/17b4i9wi1wypsgl/Screenshot_2013-11-14-13-04-53.png
Click to expand...
Click to collapse
The screenshot shows you are running stock Android 4.3 with stock kernel. However a device need to run an "odexed version of the stock rom" and stock recovery too to receive updates. If the toolkit installed the factory firmware for you, then you have everythig stock and is good to go to receive the updates.
Since Kitkat is comming OTA soon, would that be a good way to check if the phone is "original"? I mean, if i get OTA 4.4 from google, will that make sure my handset is completly as it was out of the box, and nothing hidden can be there?
Click to expand...
Click to collapse
No, a better way would be to flash the factory firmware of 4.4 when it become available, which would wipe everything in the process. It's always possible for phones to have spywares if you know how to exploit it, no software are impenetrable. For example, the seller could have installed a virus that stay in your system that lives through factory resets and use it to tell your exact location, phone information, record audio or take pictures of you. I use this myself, see: Cerberus (Nothing as drastic compared to what Google or Apple does however.) However, if you have flashed the factory image then it would wipe out programs like Cerberus.
But before being too worried about malwares, I suggest reading this article on Android malware: http://www.androidpolice.com/2013/1...at-001-of-apps-evade-defenses-and-harm-users/. To stay safe, just make sure to download apps from the PlayStore. Android have the ability to sideload app, don't utilize it if you are concerned. Even if you do sideload, if the phone have Google services installed, the "Verify apps" feature will ask to scan it before installing.
For many technical reasons and depending on usages and scenarios I believe its much safer to root than being unroot, but this will lead to other discussions. (Root may be required to catch and prevent exploits or close security holes that affect unrooted devices. It's down to how you use it. Aside from the UAC checking, most people who use Windows computer runs it fully rooted without knowing.)
eksasol said:
Why don't you ask him personally?
Toolkit being safe or not depends on who you ask. It could cause problems and sometimes it's better to learn to flash the device manually. For some its better to use toolkit since they can potentially cause more problems doing something wrong manually. If you want to flash the factory firmware manually, the instructions are in these steps: http://forum.xda-developers.com/showthread.php?t=2010312
If you install the factory image from here https://developers.google.com/android/nexus/images, then its the official Google firmware. However, these OTA packages are original as well: http://forum.xda-developers.com/showthread.php?t=2145848. To tell if other third party custom roms are safe, I don't program myself, but reliable ones are open source and have the sources available to the public that you can use to compile yourself. You can use hash checking to make sure if a file is original, Google gives you the hash values for their downloads.
The screenshot shows you are running stock Android 4.3 with stock kernel. However a device need to run an "odexed version of the stock rom" and stock recovery too to receive updates. If the toolkit installed the factory firmware for you, then you have everythig stock and is good to go to receive the updates.
No, a better way would be to flash the factory firmware of 4.4 when it become available, which would wipe everything in the process. It's always possible for phones to have spywares if you know how to exploit it, no software are impenetrable. For example, the seller could have installed a virus that stay in your system that lives through factory resets and use it to tell your exact location, phone information, record audio or take pictures of you. I use this myself, see: Cerberus (Nothing as drastic compared to what Google or Apple does however.) However, if you have flashed the factory image then it would wipe out programs like Cerberus.
But before being too worried about malwares, I suggest reading this article on Android malware: http://www.androidpolice.com/2013/1...at-001-of-apps-evade-defenses-and-harm-users/. To stay safe, just make sure to download apps from the PlayStore. Android have the ability to sideload app, don't utilize it if you are concerned. Even if you do sideload, if the phone have Google services installed, the "Verify apps" feature will ask to scan it before installing.
For many technical reasons and depending on usages and scenarios I believe its much safer to root than being unroot, but this will lead to other discussions. (Root may be required to catch and prevent exploits or close security holes that affect unrooted devices. It's down to how you use it. Aside from the UAC checking, most people who use Windows computer runs it fulled rooted without knowing.)
Click to expand...
Click to collapse
Very much thanks for your post! Appriciated that you are taking time to reply.
When it comes to why I don't "ask him personally", well, if I myself developed a malicious software I would obviously not tell people it is?
When I write safe, by safe I mean free from harmful or hidden software, not safe as in bricking. I've already used the toolkit and flashed the factoryimage I downloaded myself from google, my concern was if the toolkit in some way could add harmful code when the firmware was flashed.
An "odexed version of the stock rom" is not enough to be sure the phone is fine if I interpret you correctly? Since you are saying that recieving OTA 4.4 is no guarantee that the rom, bootloader, recovery, etc is completly googlish? Guess I will consider to flash 4.4 manually then when it's out, ill be reading the thread. Thanks alot!
How do I tell if Im running stock recovery?
I've never installed anything from outside google play, and pretty much every app are from trusted sources with millions of downloads. Atleast if facebook and instagram are to be trusted
You need to understand this is XDA Developers, a community that share open source ideas, not a warez site, you've been a member for a while to know this. The community and moderators do their best to check uploads for harm, in the end of the day still your choice to use the toolkit or install something, and to do research on it (reading through the thread).
Since you are able to use the toolkit to install factory firmware, KitKat firmware image is already available, so I suggest you flash it instead of waiting for the OTA. Generally a clean install have less issues than OTA updates.

So confused about the current ability to root an A2017U on B29

It seems like everywhere there's circular logic in the steps to get from stock to root and at some point a tool which gets flagged as a trojan by 20 or so antivirus products is a part of the process.
step 1 - download and use tenfar's axon7backup.exe to make a backup
step 2 - download and use tenfar's axon7root.exe trojan. I guess you have to turn off any antivirus on your computer for it to work which makes no sense because I've never had to root an Android device with a utility flagged as Windows malware - which is even more suspect considering half of VirusTotal's scan engines detect malware. False positive? Really?
step 3 - flash tenfar's boot.img (I don't know which to use since only B27 is provided), maybe DrakenFX's StockSystem and BootStack but his notes say it requires TWRP recovery
step 4 - flash tenfar's unofficial TWRP recovery
step 5 - wipe everything 5 times.
step 6 - install SuperSu or PHH superuser
and then there are several other suggestions sprinkled in to install other files to unlock w/o an unlocked bootloader or something yet say you need TWRP... which requires an unlocked bootloader. It sounds like every suggestion ends up depending on this axon7root.exe file
I don't get it.
There's no way I'm using literally closed-source malware to root my phone. I also don't feel the response that tenfar's method is not malicious when he's not the one making that claim... it's just random users. It makes no sense.
The way to do it is just follow the guide but I'll do my best to answer what I can.
The trojan is because the tool is pretty much a rootkit for your phone. It is hacking the system and if you're not doing it yourself, well that's not good. I personally just went to defender and restored the file and told it to ignore it.
Back when you could officially unlock the phone, you had options. Since that isn't possible at the moment (I think?), you'll have to go through this sequence to get root or unlock. I recommend rooting without unlocking if you don't really care (no real reason to unlock at the moment other than Magisk or something).
You're not flashing the bootimg with twrp you flash it with the tool on your pc. Once you do have twrp it makes everything easier imo.
When you go through the steps in tenfar's root program you should end up with backups, twrp and root, however this is NOT POSSIBLE on B29, so you'll have to do it on B20 or B27.
Hope I helped, but you should really go and look over those threads again, they'll be a lot better than I am.
I understand why you're confused. When a phone is new, threads and guides are made as progress is made. Some are updated, some aren't, some methods become obsolete with updates, some don't. Right now, this is the most painless process for rooting your phone and it includes unlocking the bootloader (otherwise, you're going to be stuck with an encrypted data partition in TWRP and it will be inaccessible in recovery).
1.) Copy everything off your internal storage that you don't want to lose.
2.) Get all of the files you need from the steps below and put them on your microSD card.
3.) Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
4.) Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
5.) Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
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.
Now, you say: "There's no way I'm using literally closed-source malware to root my phone. I also don't feel the response that tenfar's method is not malicious when he's not the one making that claim... it's just random users. It makes no sense."
If that's the case, this phone isn't for you. In fact, many phones with dev support on XDA aren't for you. In many cases, it requires a "malicious" tool to "break into" a phone that's locked down. I'm surprised you made it this far without realizing it.
thank you both
@rczrider perhaps I am suspicious because I have gotten this far without using methods which employ this behavior. If it was detected with an Android/Arm/Qualcomm signature that is a little more understanding but the heuristics point to a Win32 trojan.
I guess I've just rooted Nexus, LG, and Samsung devices and this is my first least unfriendly method I've come across :/
https://virustotal.com/en/file/070b...8ba19b57c66a9cc27b286d50/analysis/1478566368/
https://virustotal.com/en/file/4c47...70ee78db8fd3ebda2f54de31/analysis/1478567966/
Regardless, I'll go ahead and mark as answered even though it's not really answered. Plus, I don't know what is being exploited and if it is making a permanent lower-level vulnerability open for attack by doing it. That's the part that concerns me. I mean, I use Virtualbox to do this stuff just to keep my machine safe. But if it's a lower-level permanent backdoor that is what concerns me because it isn't explained in his thread.
I am so confused
Sent from my ZTE A2017U using Tapatalk

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