Develop Bugs

[N10] CF-Auto-Root

CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 9.5 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.

Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download: CF-Auto-Root-manta-mantaray-nexus10.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98

Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)

case-sensitive said:
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
Click to expand...
Click to collapse
From the OP... i marked in bold the important part.
What's installed
- SuperSU binary and APK
- Nothing else, that's it.

case-sensitive said:
Thanks!
Newbie question: Does CF-Auto-root unlock the bootloader as well? (probably not, as I understand from your post and that's what I want, but I want to be sure...)
Click to expand...
Click to collapse
No, this does not unlock the bootloader it only gives you root acess and installs the SuperSu app. To unlock the bootloader you must use fastboot and type the command:
fastboot oem unlock
I would suggest taking a look at mskip and wugfreshs toolkits located in the original development and development section of the nexus 10 forums respectively for a simple way to unlock your bootloader.
Sent from my SCH-I535 using xda premium

Good to see nexus 10 getting all this support from Android gurus here on xda ...but again it's a nexus device ...me glad I bought it ...extremely happy with my purchase thanks chainfire for this easy root method as usual it works

So if this doesn't unlock your device, why does the OP state:
Note that if your device had not been unlocked before, this procedure will wipe all your data !?
Does rooting/installing SU wipe this device?

His previous version didn't wipe the device, so I'm guessing this one doesn't either
Didn't need to unlock boot loader to root

shimp208 said:
No, this does not unlock the bootloader it only gives you root acess and installs the SuperSu app. To unlock the bootloader you must use fastboot and type the command:
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Are you sure? The script in the ZIP in OP has the following command:
Code:
tools\fastboot-windows.exe oem unlock
Does that not issue a unlock? Is it necessary to run this command?

hi there, not sure how to get this to work
its giving error because it can't find adbwinapi.dll
I installed the sdk for 4.2 already, not sure what i am missing
Thanks for help

d0nald01 said:
hi there, not sure how to get this to work
its giving error because it can't find adbwinapi.dll
I installed the sdk for 4.2 already, not sure what i am missing
Thanks for help
Click to expand...
Click to collapse
Please re-download, I've included the missing file in the new package.

now its stuck at waiting for device
when i plug in my n10 on bootloader screen, i hear the bad connection to usb sound, the 3 note sound, not the usual 2 note sound when i the connection is good.
but i am still able to see my n10 when i boot it up normally and can transfer files etc
am i missing something?

Thanks for this tool, works perfectly.

I'm also stuck on "waiting for device" also. any way around this?
Edit: Downloading and installing full drivers fixed it.

Big thanks, I was stuck in a bootloop, but this got me out of it!

Worked perfect (Debian)

Happy new year guys
Does CF Auto Root support JB 4.2.1 on the Nexus 10 yet?
Thanks

idefix_sin said:
Happy new year guys
Does CF Auto Root support JB 4.2.1 on the Nexus 10 yet?
Thanks
Click to expand...
Click to collapse
Sure, I used it again to root the device after taking the 4.2.1 update.

Hi, I've just bought n10. I want be sure if this procedure will wipe my data? I read that unlocking cause wipe everything. But I don't need it, root is enough Thanks for help.

From the first post:
Chainfire said:
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Click to expand...
Click to collapse
mieszk3 said:
Hi, I've just bought n10. I want be sure if this procedure will wipe my data? I read that unlocking cause wipe everything. But I don't need it, root is enough Thanks for help.
Click to expand...
Click to collapse
Seems pretty obvious to me. I didn't put it in bold red letters because it's irrelevant.

Very weird root issue

When I first bought my ZL, I rooted the phone using binary4 V27 on superuser mode and that was very fast and simple. I could modify system files and do everything.
One day using my ultimate stupidness, I updated the firmware to 10.1.1.....253 then I did factory reset without doing a backup for my root.
Right now, when I go to settings -----> about ----> I get Kernal version 3.4.0 with android version 4.1.2 but unfortunately It seems like I don't have a rooted phone + I am unable to do any function of a rooted phone like modifying system files or ....etc .
I've tried million ways such as:
1- rooting the phone using the same method --------> the result is stucking at the wight screen and nothing happened.
2- Using motochopper method --------> doesn't work
3- Using the method of installing Android SDK and using the command prompt window to push (Su-busybox-superuser.apk) files to data/local/tmp/ --------> when reach sysrw step (sysrw not found)
tried to type SU (su not found)
tried to use one of the alternative commands like cd /system/usr/we-need-root or ./su-backup -----> file not found
or mount -o remount,rw '' /systemmount ---------> Operation not permitted
I will be following your instructions directly and give u the feed back
I am not gonna move anywhere until solving this issue BC I am getting crazy
I would highly appreciate your help guys , ... Thank you so much in advance

mahmoud.kunbaz said:
When I first bought my ZL, I rooted the phone using binary4 V27 on superuser mode and that was very fast and simple. I could modify system files and do everything.
One day using my ultimate stupidness, I did factory reset without doing a backup for my root.
Right now, when I go to settings -----> about ----> I get Kernal version 3.4.0 with android version 4.1.2 but unfortunately It seems like I don't have a rooted phone + I am unable to do any function of a rooted phone like modifying system files or ....etc .
I've tried million ways such as:
1- rooting the phone using the same method --------> the result is stucking at the wight screen and nothing happened.
2- Using motochopper method --------> doesn't work
3- Using the method of installing Android SDK and using the command prompt window to push (Su-busybox-superuser.apk) files to data/local/tmp/ --------> when reach sysrw step (sysrw not found)
tried to type SU (su not found)
tried to use one of the alternative commands like cd /system/usr/we-need-root or ./su-backup -----> file not found
or mount -o remount,rw '' /systemmount ---------> Operation not permitted
I will be following your instructions directly and give u the feed back
I am not gonna move anywhere until solving this issue BC I am getting crazy
I would highly appreciate your help guys , ... Thank you so much in advance
Click to expand...
Click to collapse
u already posted in Q & A the same thing

demonicjas said:
u already posted in Q & A the same thing
Click to expand...
Click to collapse
Yeah, I am so sorry for that but as you know some people only go for a certain section so I might be missing someone who has the
solution of my issue :crying:
I am sorry again

mahmoud.kunbaz said:
Yeah, I am so sorry for that but as you know some people only go for a certain section so I might be missing someone who has the
solution of my issue :crying:
I am sorry again
Click to expand...
Click to collapse
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2

butatx said:
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2
Click to expand...
Click to collapse
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Thanks again

mahmoud.kunbaz said:
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Click to expand...
Click to collapse
Some aspects of modifying this phone can leave you a seriously broken phone, notably the TA partition. You would benefit greatly from doing a lot (like hours and hours) of reading in the "Z" section. All the activity is there, not in the ZL section. 99.9% of all the information there applies to the ZL (but practically NONE of the download files, so do not use software there unless clearly labeled for the ZL). The sections on backing up TA (look for DRM and TA), on using flashtool.
Note that all the information on root that does not specifically mention 253 is obsolete.

Linwood.Ferguson said:
Some aspects of modifying this phone can leave you a seriously broken phone, notably the TA partition. You would benefit greatly from doing a lot (like hours and hours) of reading in the "Z" section. All the activity is there, not in the ZL section. 99.9% of all the information there applies to the ZL (but practically NONE of the download files, so do not use software there unless clearly labeled for the ZL). The sections on backing up TA (look for DRM and TA), on using flashtool.
Note that all the information on root that does not specifically mention 253 is obsolete.
Click to expand...
Click to collapse
Thanks alot for your reply but I really don't understand why this device (ZL) is being ignored like that
I have opened a thread here about that http://forum.xda-developers.com/showthread.php?t=2293512
so many ZL users are complaining and unfortunately things are not going well

mahmoud.kunbaz said:
So thankful for ur reply
Unfortunately this is too much for a beginner like me so actually I have to search alot to get any of your solutions done.
by the way I did only root by binary4 so I think I still have a locked bootloader.
Thanks again
Click to expand...
Click to collapse
Yup, please read a lot and read the feedback. It will help you to gain ur confident.
Sent from my BlackBerry 9900 using Tapatalk

butatx said:
Ur bootloader is lock or unlock? If lock, you have to be patient for new root exploit method to appear.
Another way is to degrade ur Rom to. 434 and root. Then flash doomkernel v7 (this only apply to bootloader unlock) and flash .253 xcluding kernel. When finish once u want to reboot, there will be request to root appear.
Another another way, download rootkeeper, then temp un root and run OTA but some people in Z forum reported that it still fail to update, some successfully update.
Sent from my C6502 using Tapatalk 2
Click to expand...
Click to collapse
tried rootkeeper - doesn't work. (currently on 434 with locked BL)

Thread closed, use the post linked by the op three posts above

[Tutorial] Xperia Z2 Tablet Bootloader Unlocking/Relocking

Quick tutorial for unlocking & relocking the bootloader of the Xperia Z2 Tablet
this is the official way to unlock bootloader
WARNING!
MAKE TA BACKUP BEFORE UNLOCKING BOOTLOADER!
​
if you want to backup the TA or keep ur DRM keys,first root the device and then check this out
Warning!
This procedure will wipe the /data partition of your tablet, so you will loss all ur stored data, settings. SDCARD will BE WIPED!!!
For Xperia™ devices released 2013 or later (for example Xperia™ Z and Xperia™ ZL), the SD card of your device will be formatted and you will lose all content (for example photos, music, videos) when you unlock the boot loader.
Click to expand...
Click to collapse
DRM keys WILL be lost forever
schaggo said:
I'd add what losing DRM keys means, e.g. no more Music ID/Gracenote within the Walkman app plus probably most importantly, as asked all the time and all over the place in the T/mint forums: loss of Bravia Engine.
Click to expand...
Click to collapse
older Xperia devices sometimes got issues after unlock of bootloader (BRICK after FOTA update) - you have been warned
why to unlock bootloader?
u can flash custom ROMs/Kernels
u dont need to worry if the new firmware can be rooted or not as with unlocked bootloader u can always ROOT ur device
Sony gives sneak-peaks/preview builds of latest OS which requires unlocked bootloaders, as they did with Xperia 2011/2012 line, so who knows may be Sony may give early builds of next android OS
Most of this is taken from lollylost100's his tutorial from ARC thread (all credits for that concise tutorial go to him, i have elaborated on a few things and added device specific changes)
btw i dont have this device, most of this testing was done remotely on a users phone... so thanks a lot to him for helping out!!!
[ before we begin unlocking bootloader ]
download the fastboot package
IMPORTANT: if you are using Windows 8 you will need to enable few things to allow driver installation
download the latest FlashTool Xperia Driver Pack and install fastboot drivers (common) & adb drivers for this device from the list!
make sure u have a windows PC with USB cable to connect the phone
power down ur tablet and keeping the Volume Up button pressed connect the USB cable to PC this will trigger FASTBOOT mode and windows will start driver installation, which should be automatically done
once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
Go to: http://unlockbootloader.sonymobile.com/ and read everything!
At the bottom click 'Start Unlocking the Bootloader'
First, you should confirm that it is possible to unlock the boot loader of your tablet by checking the service menu. On your tablet, open the dialler and enter *#*#7378423#*#* to access the service menu.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
after u have verified that u can unlock bootloader, scroll to the bottom of the page and click "Continue"
you will get numerous prompts, read all info and if u agree click on "Accept"/"OK"/"Proceed"
finally u will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
You should now receive your unique unlock key via EMAIL, SAVE THIS KEY SAFELY
Extract fastboot_with_Android_USB_file.rar and open fastboot folder
Hold SHIFT and right click on the background of the folder
Select 'Open command window here'
Connect your tablet in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the tablet is correctly connected
Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
If this tutorial is too much for you then itskapil wrote a step-by-step guide (and recorded a video also):
-Instructions: http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
-Video: http://www.youtube.com/watch?v=LRH3pC7MhEA
(the above videos and some steps are for Xperia 2011 devices, but most the steps are same for Xperia Z)
Relock procedure is posted here
regards,
DooMLoRD

Relocking bootloader
With the latest release of Flashtool it is now possible to relock bootloader.
Download the latest flashtool from:
http://forum.xda-developers.com/showthread.php?t=920746
Important
DO NOT USE ANY FTF TO RELOCK BOOTLOADER! THOSE OLD FTFs DO NOT WORK FOR THE 2013 DEVICES!!!
before u relock bootloader u have to be on pure stock kernel (flash only the kernel.sin using flashtool), else the device WILL NOT BOOT after relock
Steps:
now start Flashtool and click on BLU button
u will be asked to connect device in flashmode
once u connect the device u will get a prompt to "Relock"
click on it and when prompted disconnect the device
Want to UNLOCK again after relocking? read this!

Obviously since we must unlock to root, no TA backup can bedone...

Diomorgan said:
Obviously since we must unlock to root, no TA backup can bedone...
Click to expand...
Click to collapse
Asking or telling..........either way, correct. TA needs root, to get root you need to unlock lol

Mikey said:
Asking or telling..........either way, correct. TA needs root, to get root you need to unlock lol
Click to expand...
Click to collapse
I'm confused now.....

Pondy said:
I'm confused now.....
Click to expand...
Click to collapse
No TA backup can be done, the guide is the same of Z1 that can be rooted withouth unlock.

Pondy said:
I'm confused now.....
Click to expand...
Click to collapse
It is very confusing indeed. In other words it actually says, do not unlock yet. Wait for an exploid to be found and released so you can root without unlocking the bootloader. Then you can safely make an TA backup, and then safely unlock the bootloader. If you unlock now, your warranty is void.
Sent from my SGP511 using XDA Free mobile app

When a root exploit is found, unlocking the bootloader or backing up TA is not necessary anymore. (Except if one wants to install a custom ROM or custom kernel.)

Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app

dumbl3 said:
Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app
Click to expand...
Click to collapse
OK thanks for clarifying that! I figured that was the case. And yes thats why I'm here, custom rom! This thing would rock with Slimkat or something similar (if it ever gets ported).

For all those who worry about unlocking I would like to cite Doomlord from the Z2 phone CWM recovery thread:
Dont worry I have been on unlocked Bootloader on all my Xperia phones and honestly there is no functionality that I missed.
Click to expand...
Click to collapse
This!
(Yes, I know, the warranty, blah... )

dumbl3 said:
Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app
Click to expand...
Click to collapse
Actually I have customs on all my device, but on z1 (same for z2) never needed one, just root and exposed framework+adaway.
About unlocking, as far as I know the only "useful feature" you will disable should be the bravia engine.

Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.

hasenbein1966 said:
Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.
Click to expand...
Click to collapse
i agree on that but it voids your warranty.
Im not saying we should all wait till your warranty is over, but at least fully test your device before making a irrational decision, dead pixels, speakers, loose corners (have had 2 devices with that problem), waterproof test, etc...

LitoNi said:
i agree on that but it voids your warranty.
Im not saying we should all wait till your warranty is over, but at least fully test your device before making a irrational decision, dead pixels, speakers, loose corners (have had 2 devices with that problem), waterproof test, etc...
Click to expand...
Click to collapse
True, last thing you want is to void the warranty and find out something covered by it goes bad. I can wait. This baby is running nice so far. Dont need custom rom, but im missing that root!!

SD card write
Is anyone else having issue to write to external sdcard ?

nizammoidu said:
Is anyone else having issue to write to external sdcard ?
Click to expand...
Click to collapse
That's the new rule implemented in kit kat, not Sony's fault.
This problem can be solved if root is available
Sent from my C6603 using XDA Premium 4 mobile app

what s that rule? I have been using kitkat with omni since it released in note 2 nd hammerhead. initially it had issues with selinux, then i wrote a patch to omni source as well. but here selinux is not the bad guy I suspect something to QUCOMSEC nd drm keys. l have root, can u give me pointer to fixes. This s my first sony device so I have idea, Thank u

nizammoidu said:
what s that rule? I have been using kitkat with omni since it released in note 2 nd hammerhead. initially it had issues with selinux, then i wrote a patch to omni source as well. but here selinux is not the bad guy I suspect something to QUCOMSEC nd drm keys. l have root, can u give me pointer to fixes. This s my first sony device so I have idea, Thank u
Click to expand...
Click to collapse
custom roms probably already coded it, thats why you didnt encounter the problem. Explanation of the problem can be found here provided by the OP.
If you have root already you can try both of the following,
*please note that Ive tried the xposed module on my Xperia Z running stock kit kat not Z2.
**please note, back up your stuff before proceeding, just incase something goes wrong and wipes your files.
[XPOSED] HandleExternalStorage requires Xposed framework installed. I am currently running this module and working fine.
[Playstore] SDFix: KitKat Writable MicroSD this was suggested by kingvortex in another thread, havent tried it yet, but the reviews seem to suggest it works.

hasenbein1966 said:
Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.
Click to expand...
Click to collapse
Sorry - but I just have to add my own experience as a "noob".
First: I gave that X-Reality thing a deeper check; I had two Z2 tablets for simultaneously checking how HD videos look with and without that X-Reality feature.
I usually dislike all kinds of "enhancers", whether for audio or video enhancement. First things to switch off.
But I have to admit: X-Reality really works. The Z2 with the feature on produced a far more lively, absorbing experience. It's hard to tell what exactly makes the difference, it's just there. Among other videos, I used the famous Samsung "build-a-helicopter" video for comparison. Contrasts were better, details improved a bit, colors got slightly accentuated, became deeper. The slightly oversaturated color reproduction of the Z2 of course is there - but with and without X-Reality.
In short: Videos were just more fun and pleasant to the eye.
Best of all: You can switch it off; but you don't want to.
To be honest: X-Reality is THE feature preventing me from rooting the Z2 now. I don't care for DRM keys, I don't care for a true-to-life color rendition. But I care for pictures and videos looking simply better.
Quite lenghty explanation - but I guess this is an issue to consider prior to unlocking your bootloader and waving X-Reality goodbye forever.
Second: Beats Audio is a bit more than a "bass-booster for music-unsensible juvenile oomph-oomph listeners".
I seem to be a 45 years old "music-unsensible" listener. In fact, I am a former professional musician, knowing just a bit about sound.
I don't see anything wrong with utilizing software techologies to overcome some of the acoustic issues tiny smartphone or tablet loudspeakers suffer of. It's not just about creating that "oomph-oomph" redneck sound; it's about compensating the shortcomings of problematic speaker setups.
That's what devices like HTCs One clearly demonstrated.
I'd be quite happy if our Z2 had anything similar to offer. :/
So please try to be a bit more reluctant if it comes to demonizing modern features not everybody may like, but which will be gone forever if you go the hasty way.

[TOOL] Robin Toolkit (v1.2) - Root, TWRP, rescue device...

"I'm not responsible for any damage suffered by your device. You decide if you want to use my tool or not. Also you won't be able to update via OTA."
Ok guys, so as I promised, as soon as I received my Robin I started to work on this to finish it, and after some days of working and testing, here you have a toolkit for the cute Robin:
- Unlock/Lock the Robin (You should unlock your Robin the first time you use this tool. If not, as most of the tools below need the bootloader to be unlocked, you will lose your data when running any of them for the first time. In that case, creating a backup would be really unuseful. Unlock once, unlock forever)
- Backup/Restore
- Root
- Install TWRP
- Wipe Cache/Data (with and without TWRP installed)
- Install factory images (System, Boot and/or recovery, up to you - Not the last version, I have to update it)
- Install non-forced-encryption patched boot by @d3xt3r (Thanks bud!) [Possibly adding the @deadman96385 version too in a near future!]
Root, Install TWRP and Backup/Restore work 100% sure. Other like install factory images or the non-encryption mod I haven't tested them (I have zero time, literally), but they should work (95% sure).
Thanks also to @deadman96385, @d3xt3r, and @Baymax, who helped me testing and giving me their knowdledge!
Any suggestions and bug reporting are welcome!
Changelog
v1.2
No more using C:\ to store all the necessary files
Now using temp files, they're deleted when the Toolkit window is closed
No need to install adb anymore, it's installed the first time you run the .exe file
Update check added. You will get a message to download the new .exe everytime an update is available
Backup fixed (wasn't working)
DEAD

Great job mate! ^^

Nice job buddy!

good job david ? ? ?

Sharing violation
Getting sharing violation when I go to install adb. Any thoghts? Windows 10
Steve

flsocialist said:
Getting sharing violation when I go to install adb. Any thoghts? Windows 10
Steve
Click to expand...
Click to collapse
Can you give any more specific info (or screenshots)? Did you already have adb installed or not?
D

Good job David!! (I'm Darragh lol )

I can't seem to get this to detect that I have ADB installed...

daavm said:
"I'm not responsible for any damage suffered by your device. You decide if you want to use my tool or not. Also you won't be able to update via OTA."
Ok guys, so as I promised, as soon as I received my Robin I started to work on this to finish it, and after some days of working and testing, here you have a toolkit for the cute Robin:
- Unlock/Lock the Robin (You should unlock your Robin the first time you use this tool. If not, as most of the tools below need the bootloader to be unlocked, you will lose your data when running any of them for the first time. In that case, creating a backup would be really unuseful. Unlock once, unlock forever)
- Backup/Restore
- Root
- Install TWRP
- Wipe Cache/Data (with and without TWRP installed)
- Install factory images (System, Boot and/or recovery, up to you - Not the last version, I have to update it)
- Install non-forced-encryption patched boot by @d3xt3r (Thanks bud!) [Possibly adding the @deadman96385 version too in a near future!]
Root, Install TWRP and Backup/Restore work 100% sure. Other like install factory images or the non-encryption mod I haven't tested them (I have zero time, literally), but they should work (95% sure).
Thanks also to @deadman96385, @d3xt3r, and @Baymax, who helped me testing and giving me their knowdledge!
Any suggestions and bug reporting are welcome!
DOWNLOAD
Click to expand...
Click to collapse
Only if u had released this 3months earlier i wouldnt hav hard bricked my phone broo......... I've bcom a fan of urs bro....

Mountainmohawk said:
I can't seem to get this to detect that I have ADB installed...
Click to expand...
Click to collapse
@Mountainmohawk can you give me any more specific details? Thanks
D

Sunderesh said:
Only if u had released this 3months earlier i wouldnt hav hard bricked my phone broo......... I've bcom a fan of urs bro....
Click to expand...
Click to collapse
@Sunderesh at least nextbit's warranty covers accidental bricks!
D

Updated to v1.2!!
D

I got a trojan warning from this rootkit. Any thoughts? Or am I the only one?

joeminati said:
I got a trojan warning from this rootkit. Any thoughts? Or am I the only one?
Click to expand...
Click to collapse
@joeminati yes, it's already been reported. Some Antivirus software take any non-signed .exe package as a virus (trojan in this case). Better answer about this, in stackoverflow: http://stackoverflow.com/questions/...015-community-trojan-heur-qvm03-0-malware-gen
PD: Obviously my .exe is not signed
D

Attempted
I attempted to use this tool and it wouldn't acknowledge that my Robin was connected to it. I've installed adb and unlocked bootloader and twrp and custom rom without the tool but I wanted to try the tool and it didn't work.

dispatcher2412 said:
I attempted to use this tool and it wouldn't acknowledge that my Robin was connected to it. I've installed adb and unlocked bootloader and twrp and custom rom without the tool but I wanted to try the tool and it didn't work.
Click to expand...
Click to collapse
@dispatcher2412 yeah, some users are having the same problem. Thanks, will try to solve it!
D

daavm said:
@Sunderesh at least nextbit's warranty covers accidental bricks!
D
Click to expand...
Click to collapse
Really therz nothing like that in my country bro......

Sunderesh said:
Really therz nothing like that in my country bro......
Click to expand...
Click to collapse
@HyderAbad where did you buy your Robin? It usually has 1 year warranty from Nextbit, which covers accidental bricks. Contact Nextbit support and they will help you!
D

Does this toolkit also unroots the device to factory??

utsav_94 said:
Does this toolkit also unroots the device to factory??
Click to expand...
Click to collapse
I believe you can flash factory images. If not, you can check out our forums for more information. I did provide an unbrick tool that helps to do this.

Unlock bootloader - bootloader mode reboots phone

Hello, I am a proud new owner of the ZTE blade v8 pro, I have been trying to unlock the bootloader to see if I could work on getting root. I enabled OEM unlocking in the debugging and also ADB. The issue I am having is that every time I either use ADB reboot-bootloader or use the traditional hardware keys to get to the bootloader the device just reboots back to normal. I have even tried recovery mode which has an option for bootloader, but when I select bootloader in recovery (which is working) it still reboots normally. I am new to the forum's but I created this one to see if there is anyone else with this issue that has found a workaround. Thank you in advance!

Most likely they locked access to bootloader and adb commands. Just like they did to the ZTE ZMAX pro. Best advice is return the phone and get something else
Sent from my Z981 using XDA-Developers Legacy app

903tex said:
Most likely they locked access to bootloader and adb commands. Just like they did to the ZTE ZMAX pro. Best advice is return the phone and get something else
Click to expand...
Click to collapse
Thank you for the reply, the only thing that makes me wonder if that is the same is the fact that in the developer options it has a toggle for OEM bootloader unlocking. I have never owned a ZTE device so I am not super experienced with their manufacturer and their ideas on what a good smartphone is but why would they put that option in there if they locked the bootloader and ADB commands? (ADB works in all modes I tested btw). Just trying to see if maybe it is my device or everyone that owns this product. (Example being a corrupt boot image that will start the phone but not fastboot) and once again, thank you for your reply.

:crying:Hello I have the same phone Blade V8 Pro and I hope I don't have to return my phone last night horizontal lines started showing up on the screen I never dropped the phone they show up when in recovery mode also so I know that doesn't look good because recovery is outside the operating system it comes and goes back to normal so is my get worse later on :crying::crying::crying:

Daha3ker said:
Thank you for the reply, the only thing that makes me wonder if that is the same is the fact that in the developer options it has a toggle for OEM bootloader unlocking. I have never owned a ZTE device so I am not super experienced with their manufacturer and their ideas on what a good smartphone is but why would they put that option in there if they locked the bootloader and ADB commands? (ADB works in all modes I tested btw). Just trying to see if maybe it is my device or everyone that owns this product. (Example being a corrupt boot image that will start the phone but not fastboot) and once again, thank you for your reply.
Click to expand...
Click to collapse
I just bought this device a week ago and I was surprised to find "Unlock Bootloader" in Dev Options. I tried the same thing as you (booting into bootloader and recovery) but it didn't work for me either. Did you by any chance managed to figure out how to root the device?

pri10 said:
I just bought this device a week ago and I was surprised to find "Unlock Bootloader" in Dev Options. I tried the same thing as you (booting into bootloader and recovery) but it didn't work for me either. Did you by any chance managed to figure out how to root the device?
Click to expand...
Click to collapse
MiFavor is a tuff bootloader that this company uses. I can find no valid method to write files (locked bootloader) via ADB or FTM. I know its a necro here, but I want to warn anyone thinking they might find a method or one will be discovered... it wont.

jollymonsa said:
MiFavor is a tuff bootloader that this company uses. I can find no valid method to write files (locked bootloader) via ADB or FTM. I know its a necro here, but I want to warn anyone thinking they might find a method or one will be discovered... it wont.
Click to expand...
Click to collapse
Yeah, I realized that. Bought Huawei Mate 9 a couple of weeks ago.

ZTE V8 SE root!?

emilioangeles95 said:
This guide is technically for all ZTE phones. ZTE phones are quite friendly with developers (but still can’t hit the level of Google and HTC).
How to root
Restart your phone to bootloader (“volume down” + “battery”)
Open up your adb tool and rename TWRP as “recovery”. Drag it into the ADB toolkit and input the following command: “fastboot flash recovery recovery.img”. When finished, type “fastboot reboot” then reboot into system
Transfer SuperSU into phone’s internal memory, find the suitable SuperSU version ( SuperSU V2.64 and SuperSU V2.79)
Switch off your phone. Then press “volume up + start” to enter recovery mode
Install SuperSU by sliding it right in
Reboot, and you are all set XD
https://www.unlockbase.com/unlock-phone/zte/
Click to expand...
Click to collapse
lol

Im looking to buy this phone but would like to actually have it rooted, anyone has any idea if the device is rootable or will be in the near future?

catsruul said:
lol
Click to expand...
Click to collapse
so if im looking to root my phone via reboot I can't write that on my system files.. I tried, so how can I Hard set it into boot mode? or any other option rather then trying to write system files w/o root

Blackbear.immortal said:
so if im looking to root my phone via reboot I can't write that on my system files.. I tried, so how can I Hard set it into boot mode? or any other option rather then trying to write system files w/o root
Click to expand...
Click to collapse
Any luck?

BootStomp – A Bootloader Vulnerability Finder
Have you tried this weapon? It is the only solution for ZTE Blade V8 Pro.
BootStomp – A Bootloader Vulnerability Finder
https://pentesttoolz.com/2017/12/10/bootstomp-a-bootloader-vulnerability-finder/
https://github.com/ucsb-seclab/BootStomp

cmon people I'm about to buy the blade v8 pro, it's such a nice phone
if we had an unlocked bootloader and root that would me amazing!!!

ZTE open source website
Found this site that you can download the kernel it appears, it's a ZTE site I guess and, I'm no expert on kernels but it's this file.
ZTE Z978 Marshmallow Kernel(3.18.24)
P853A10V1.0.0B18_kernel.tar.gz
If it isn't the actual kernel I'm sorry as again I'm not an expert, I just would like to be able to root this phone as the hardware is very good for a cheep ass like me. lol
You'll have choose the "smart phone" category and z978 from the selection menu (not too far down), which has most any ZTE device on there also.
Website: opensource.ztedevice.com
I know that you can't load the kernel if you not able to get past the bootloader, but there aren't any posts in the "kernel" section and maybe there may be a clue in the kernel code on how to unlock and root this phone?, but that's above my current skill level and need the pros like y'all to help if you can.
Hope it helps.

This phone would be glorious with lineageos

Bootloader vulnerabilities of Sony Xperia XA (MT6755)
The next task is the implementation of BootStomp: a bootloader vulnerability finder.
https://github.com/ucsb-seclab/BootStomp
The bootloader vulnerabilities of Sony Xperia XA (MT6755 Helio P10) are here:
https://github.com/ucsb-seclab/BootStomp/tree/master/bootloaders

SafeStrap is a Recovery for phones with a locked bootloader. It is just like like TWRP 3.2.1.
https://www.xda-developers.com/snapdragon-samsung-galaxy-s8-galaxy-note-8-safestrap-recovery/
Sent from my takee 1 using XDA Labs

Device Info HW version: 4.9.4
Device Info HW
version: 4.9.4
Check if you can retrieve more info on partitions and other missing components of ZTE Blade V8 Pro using the new version 4.9.4 of Device Info HW, please. The new apk is attached at the end of post #1.
https://forum.xda-developers.com/android/apps-games/app-device-info-hw-t3558335

We dont have root acess for use safestrap recovery.