Database Info

[GUIDE] Unlock/Root/Flash for Moto X Style/Pure

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+2]Moto X Pure[/SIZE]​
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)​
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me

This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk

Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes

This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.

Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?

You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?

Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery

elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.

Oops

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588

Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/

I flashed SU and it didn't give me root, any suggestions?

mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?

Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.

mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.

Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.

mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?

Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.

mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.

Sony Xperia XZ Unlock bootloader, TWRP and ROOT.

For rooting Xperia XZ, we need recovery and for recovery flashing the bootloader must be unlocked.
PREREQUISITES:
1. ADB/FASTBOOT. View attachment 4715074
2. Drivers for Sony Xperia XZ. View attachment Xperia_XZ_driver.zip
3. Backup all your data, Apps, Contacts & everything you need.
4. Charge ur device above 60% to avoid any shutdown during the process
UNLOCKING BOOTLOADER
Unlock Bootloader: Opens the door to System files of your device. This allows you to flash images onto the main system partitions of the phone, after unlocking you will lose the DRM keys and phone's warranty will be void, it will also factory reset your device.(backup is recommended)
1. Open Dialer.
2. Dial *#*#7378423#*#*
3. Press service info than configuration.
4. Check if “Bootloader Unlock” is yes under Rooting status.[If not then your device can not be unlocked]
5. Check what android you are running on. Go to Settings -> About Phone -> Android Version. If you have 6.x.x then goto step 9 but if you have 7.x.x then you have to downgrade to Marshmallow.
6. Download and install FlashTool from its official website.
7. Install the drivers for fastmode and for your device in the driver folder of the FlashTool. [C:>FLASHTOOL>drivers]
8. Download ftf for your device using XpiriFirm and flash it using flashtool.
How to flash ftf?
9. Goto settings>about phone >developers option and ensure that OEM Unlock and USB Debugging is on.
10. Goto Xperia BLU page and Choose Xperia XZ at the bottom of the page.
11. Enter your Email and you will receive a link in your mail. Follow the steps given by Sony.
12. BE CAREFUL and, from now on, DON’T ENABLE the MyXperia. It could hard brick your phone.
Now your phone is unlocked
We will now go over some other fixes.
FLASH ANDRO PLUS KERNEL.
This kernel will help your device cope up with some battery issues and it also has some DRM Fixes. To install it, follow the steps :
1. Download the kernel version supported for your buildnumber.{AndroPlus}
2. Unzip the downloaded file and paste them into your fastboot/adb directory.
3. Now Boot into Bootloader mode by turning the device off and pressing volume up then plug in the USB.
4. Run the command prompt where you pasted the extracted zip . Do this by shift+right click and selecting Open command prompt here.
5. Enter the command "fastboot flash boot boot.img"(without double quotation)
6. Unplug and reboot your device
FLASH CUSTOM RECOVERY [TWRP]
A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default(XZ doesn't have stock recovery). Custom recoveries bring lots of functionality and allows you to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
This process will provide your device a custom recovery (TWRP) This can be used to flash root script, ROM and custom kernels at anytime without PC.
1. Download the TWRP image file.
2. Paste it in your Fastboot directory and rename it as recovery.img
3. Open cmd in the folder where you pasted recovery.img
4. Enter the command "fastboot flash recovery recovery.img"(without double quotation)
5. Reboot your device.
FLASHING MAGISK
Now the final step. To root your device you just need to flash the Magisk zip.
1. Download the zip.
2. Paste it in your device.
3. Now boot into recovery by turning off and press power+volume down at the same time and release the power key after vibration.
4. If TWRP is decrypted use this guide.
5. Now select install and navigate to the pasted zip, swipe for flash.
6. Reboot and check if the Magisk app is installed on your device.
________________________________________________________________________________________
-- If You Liked My Work--
-- Press the Thanks :good: Button --
​

Hi there.
May downgrade from N 7.1.1 to MM 6.0.1 causing lost DRM key ?
Thanks for your reply.

anhyeuviolet said:
Hi there.
May downgrade from N 7.1.1 to MM 6.0.1 causing lost DRM key ?
Thanks for your reply.
Click to expand...
Click to collapse
No downgrading not.
Drm keys r lost when u unlock bootloader

Have someone tried this guide????

awadnisar said:
No downgrading not.
Drm keys r lost when u unlock bootloader
Click to expand...
Click to collapse
This is my Screenshot from Security (inside Service test).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you have any idea ?
My XZ looks different to another pics from Internet.

anhyeuviolet said:
This is my Screenshot from Security (inside Service test).
My XZ looks different to another pics from Internet.
Click to expand...
Click to collapse
It should ...
Looks normal for a new device.
Check
Service Info -> Configuration -> Bootloader unlock allowed

DHGE said:
It should ...
Looks normal for a new device.
Check
Service Info -> Configuration -> Bootloader unlock allowed
Click to expand...
Click to collapse
Checked and it show:
Bootloader unlock allowed: Yes.
Is it ok ?

anhyeuviolet said:
Is it ok ?
Click to expand...
Click to collapse
For me: yes
For the larger part of Society? Hmmm :silly:
read my [Guide]

DHGE said:
For me: yes
For the larger part of Society? Hmmm :silly:
read my [Guide]
Click to expand...
Click to collapse
Mailed to Sony Support. They said that Okay, too.
If XZ is not lagging as it right now, I will be more satisfied.

Quick Info After Unlocking Bootloader
awadnisar said:
For rooting Xperia xz (DUAL), we need recovery and for recovery flashing the bootloader must be unlocked.
CONTINUE AT YOUR OWN RISK
PREREQUISITES
1. ADB/FASTBOOT. Download https://drive.google.com/open?id=0B4IlcVrKbV2qT1V1T2RFQmxXNU0
2. Drivers for Sony Xperia XZ. Download https://drive.google.com/open?id=0B4IlcVrKbV2qeloxN01ESkZZTkU
3. Backup all your data, Apps, contacts & everything your need. we need to create backup in order to restore if anything goes wrong. [hopefully not]
4. Charge ur device above 60% to avoid any shutdown during the process
UNLOCKING BOOTLOADER
Unlock Bootloader: Opens the door to System files of your device. This allows you to flash images onto the main system partitions of the phone, after unlocking you will lose the DRM keys and phone's warranty will be void, it will also factory reset your device.(backup is recommended)
1. Open your dialer.
2. Dial *#*#7378423#*#*
3. Press service info than configuration.
4. Check if “Bootloader Unlock” is yes under Rooting status.[If not then your device can not be unlocked]
5. Check what android you are running on. Go to Settings -> About Phone -> Android Version. If you have 6.x.x then goto step 9 but if you have 7.x.x then you have to downgrade to Marshmallow.
6. Download and install FlashTool from its official website. http://www.flashtool.net/downloads.php
7. Install the drivers for fastmode and for your device in the driver folder of the FlashTool. [C:>FLASHTOOL>drivers]
8. Download ftf for your device, for [F8332/dual (https://drive.google.com/open?id=0B4IlcVrKbV2qSnBCRWxHLWY5RjQ)] and flash it using flashtool.
how to flash ftf https://forum.xda-developers.com/xperia-z/general/tutorial-how-to-flash-stock-roms-t2240614
9. Goto settings>about phone >developers option and ensure that OEM Unlock and USB Debugging is on.
10. Goto (https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/) and Choose Xperia XZ at the bottom of the page.
11. Enter your Email and you will receive a link in your mail. Follow the steps given by Sony.
12. BE CAREFUL and, from now on, DON’T ENABLE the MyXperia. It could hard brick your phone.
Now your phone is unlocked
We will now go over some other fixes.
FLASH ANDRO PLUS KERNEL.
This kernel will help your device cope up with some battery issues and it also has some DRM Fixes. To install it, follow the steps :
1. Download the kernel https://github.com/AndroPlus-org/android_kernel_sony_msm8996
2. Unzip the downloaded file and paste them into your fastboot/adb directory.
3. Now Boot into Bootloader mode by turning the device off and pressing volume up then plug in the USB.
4. Run the command prompt where you pasted the extracted zip . Do this by shift+right click and selecting Open command prompt here.
5. Enter the command "fastboot flash boot boot.img"(without double quotation)
6. Unplug and reboot your device
FLASH CUSTOM RECOVERY [TWRP]
A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default(XZ doesn't have stock recovery). Custom recoveries bring lots of functionality and allows you to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
This process will provide your device a custom recovery (TWRP) This can be used to flash root script, ROM and custom kernels at anytime without PC.
1. Download the TWRP image file https://drive.google.com/open?id=0B4IlcVrKbV2qWF9QaDhPd2hONmc
2. Paste it in your Fastboot directory and rename it as recovery.img
3. Open cmd in the folder where you pasted recovery.img
4. Enter the command "fastboot flash recovery recovery.img"(without double quotation)
5. Reboot your device.
FLASH SUPER SU ZIP
Now the final step. To root your device you just need to flash the super su zip.
1. Download the zip. https://drive.google.com/open?id=0B4IlcVrKbV2qOExRekY3M3ZPVG8
2. Paste it in your device.
3. Now boot into recovery by turning off and press power+volume down at the same time and release the power key after vibration.
4. Now select install and navigate to the pasted zip, swipe for flash.
5. Reboot and check if the Super SU app is installed on your device.
Click to expand...
Click to collapse
Good Tutorial As Iam Quite Familiar With This Rooting Method I Would Like To Highlight a Line
2. Paste it in your Fastboot directory and rename it as recovery.img
Because it Is Necessary Guys Without Renaming It , It Would Be Difficult to Enter in TWRP Recovery.
Rename To "recovery.img" is Must to Replace The Stock With This One.
and To Enter TWRP MENU After Everything Done.-----> Follow The Steps. <------
1 - Completely Power OFF The Phone , ( You Can Also Power off the Phone Anytime By Holding VOLUME UP + POWER BUTTON For 5 Secs Until There is 3 Vibration. )
2 - Hold Volume Down + Power Button , After That SONY Logo is Shown , Then Release ONLY THE POWER KEY and KEEP HOLDING the VOLUME DOWN Button.
3 - Wait Till TWRP Appears and Start Doing What You Like.
I Hope This Info Helps To Beginners.

CALL ME SUBH said:
Good Tutorial As Iam Quite Familiar With This Rooting Method I Would Like To Highlight a Line
2. Paste it in your Fastboot directory and rename it as recovery.img
Because it Is Necessary Guys Without Renaming It , It Would Be Difficult to Enter in TWRP Recovery.
Rename To "recovery.img" is Must to Replace The Stock With This One.
and To Enter TWRP MENU After Everything Done.-----> Follow The Steps. <------
1 - Completely Power OFF The Phone , ( You Can Also Power off the Phone Anytime By Holding VOLUME UP + POWER BUTTON For 5 Secs Until There is 3 Vibration. )
2 - Hold Volume Down + Power Button , After That SONY Logo is Shown , Then Release ONLY THE POWER KEY and KEEP HOLDING the VOLUME DOWN Button.
3 - Wait Till TWRP Appears and Start Doing What You Like.
I Hope This Info Helps To Beginners.
Click to expand...
Click to collapse
Thanks, when i was writing the post i took too long so i can't explain each and every step.

awadnisar said:
Thanks, when i was writing the post i took too long so i can't explain each and every step.
Click to expand...
Click to collapse
No Prob Bro

Do I still need to downgrade to MM when I'm running latest version of Oreo?

odarpsahc said:
Do I still need to downgrade to MM when I'm running latest version of Oreo?
Click to expand...
Click to collapse
If you want Unlock bootloader, as I know, Yes.

magisk/super su
hi, how to install magisk instead of super su in marshmallow, thanks

ciqbalz said:
hi, how to install magisk instead of super su in marshmallow, thanks
Click to expand...
Click to collapse
Just install latest magisk zip

odarpsahc said:
Do I still need to downgrade to MM when I'm running latest version of Oreo?
Click to expand...
Click to collapse
Yes coz for unlocking bootloader it's necessary

awadnisar said:
Yes coz for unlocking bootloader it's necessary
Click to expand...
Click to collapse
Hmm.. Not really, if he wishes to save and back up his DRM keys then yes it is nessecary to downgrade but if he's not worried about them he can do everything from oreo, unlocking the BL, installing a Kernel, TWRP ect.... But let me be clear to save your DRM Keys you need to downgrade..

Yota 3+ root,twrp, updates

Please put in this thread all the news about our yota3+ so we can update and custom safely together.

This is the first update that i know, still not tested by me:
Originally Posted by Allleeexxx5
Who can try this files on his Y3+ ? It is a test version. It can break your phone.
Better ask to Allleeexxx5
Quote:
fastboot flash boot boot.img
https://drive.google.com/file/d/1Rez...RGc9WOKna/view

I have not still download the 2 OTA update.
Anyone has tested, any issues?

paolinger said:
This is the first update that i know, still not tested by me:
Originally Posted by Allleeexxx5
Who can try this files on his Y3+ ? It is a test version. It can break your phone.
Better ask to Allleeexxx5
Quote:
fastboot flash boot boot.img
https://drive.google.com/file/d/1Rez...RGc9WOKna/view
Click to expand...
Click to collapse
Ok How do I get this installed on my YotaPhone 3+ 64 Gb?
Please give me some instructions, I have updated from the YotaPhone 3 Chinees to the YotaPhone 3+ but after this update the IMEI's are empty and I need to add them it looks now I need to root to be able to add the IMEI from the box it came with.
If you have a tool to re-enter the IMEI without rooting is the best, but it look the only way to do this is to root the YotaPhone 3+

HvMES said:
Ok How do I get this installed on my YotaPhone 3+ 64 Gb?
Please give me some instructions, I have updated from the YotaPhone 3 Chinees to the YotaPhone 3+ but after this update the IMEI's are empty and I need to add them it looks now I need to root to be able to add the IMEI from the box it came with.
If you have a tool to re-enter the IMEI without rooting is the best, but it look the only way to do this is to root the YotaPhone 3+
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2317790

fastboot oem unlock-go
to unlock

Yota 3+ Root
Instruction 1: Magisk system-less root (ref: https://www.xda-developers.com/what-is-magisk/), which is less invasive as it doesn't have to remove user data, but more fragile if something goes wrong on your system (e.g you will attempt to modify your storage outside of booted OS), you will have to fully re-install your OS. But is less detectable by apps and playstore that your device is rooted, which is good.
Instruction 2: Full root which includes TWRP, Magisk and disabled storage encryption, meaning you can freely modify your storage outside of booted OS and if something goes wrong your will be able to boot into TWRP and potentially fix the issues / make or restore backups . But this method has to remove and fully re-install your system to work.
Note: leaving your device unencrypted is not secure as if your device is lost then your personal data can be retrieved from it. Hence, once you've done installation of all rooted apps and ensured that everything is working fine in long term (e.g couple of days) it is recommended to do following:
- Encrypt your device (Settings > Security & location > Encryption & credentials > Encrypt phone)
- Lock boootloader (Settings > System > Developer options > OEM unlocking > OFF)
This will make your device secure again, but note that you will not be able to modify / access user data from TWRP anymore. Moreover, you won't be able to successfully modify system partitions unless you re-apply Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip (https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389)
Instruction 1 - System-less root method
Note: this is a system-less root method, meaning that if you attempt to modify your system partition from custom recovery, then it will fail to boot again!
Pre-reqs (important!):
All you personal data is backed up
Developer options is enabled:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
USBdebugging is on:
OEM unlocking is on:
adb, fastboot tools are installed on PC
Device pin is enabled (Settings > Security & location > Screen lock > PIN)
Steps:
Get new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Extract new9008-0112.zip > copy boot.img to your phone
Boot image is copied to phone:
Install Magisk. : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Open Magisk > Install > Patch Boot Image File > direct to copied boot.img > It will generate a file > Close
Copy created patched_boot.img from device Downloads to your PC:
Run cmd on pc from place where you copied file > adb reboot bootloader > fastboot boot patched_boot.img
Device will boot > Open Magisk app > It will ask you to grant root permission > grant it > Click Install button again > Direct Install (Recommended) > Reboot
Grant permissions:
Click on install button:
Click on install in dialog:
Click on direct install in dialog:
It will patch your boot partition, click reboot:
Observe two green tick boxes are still green after reboot:
Congratulations, your device is now rooted!
Instruction 2 - Yota 3+ 8.1 System Root with TWRP recovery, Magisk and storage encryption disabled
I've managed to create a TWRP specific for Y3+ and wrote .bat script which automatically re-installs OS 8.1 with latest ota 54 update, magisk and root and disables storage encryption.
Pre-recs (Important!):
Your phone is charged to at least 50%
adb, fastboot installed on your pc and accessible through home path system environment variable
adb debugging enabled
Developer options > OEM unlocking > ON
backup all your personal data
Steps:
Download: mega.nz/#F!yMBGBYIY!24gGnv0DXNhqBvE7IbrEmA
Double click on install.bat
Follow on-screen instructions
Important! As soon as you are on home screen browse your e-ink screen at least once, otherwise the OS might crash after ~ 5-10 minutes due to inability to properly access its launcher. Once done, Reboot your device.
References:
The work is done based on:
- TWRP repacking using Android.Image.Kitchen.v3.4-Win32.zip from: https://forum.xda-developers.com/showthread.php?t=2073775 thanks to @osm0sis
- TWRP for Y3 from: https://forum.xda-developers.com/yotaphone-3/development/yota3-firmware-root-magisk-t3830405 thanks to @gor516don
- new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999 thanks to @paolinger
- Disabling storage encryption using Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip from: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 thanks to @Zackptg5

vvinjj said:
Pre-reqs (important!):
All you personal data is backed up
Developer options is enabled
adb debugging is on
OEM unlocking is on
adb, fastboot tools are installed on PC
Steps:
Get new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Extract new9008-0112.zip > copy boot.img to your phone
Install Magisk: https://******************/downloading-magisk-manager
Open Magisk > Install > Path Boot Image File > direct to copied boot.img > It will generate a file > Close
Copy created patched_boot.img from device Downloads to your PC
Run cmd on pc > adb reboot bootloader > fastboot boot patched_boot.img
Device will boot > Open Magisk app > Install > Direct Install (Recommended) > Reboot
Congratulations, your device is now rooted!
Click to expand...
Click to collapse
Hi I have tried all but it is not clear to me I'm not able to root the YotaPhone 3+.
If it possible to give me a more clear instruction step by step. Also how to test if it is rooted?
It was a YotaPhone 3 and I updated it successful to the YotaPhone 3+ only I lost the IMEI 1 and 2. To add them I need to rood the Phone to add the EMEI or is there a option to add them NOT rooted.
Please help!!

vvinjj said:
Pre-reqs (important!):
All you personal data is backed up
Developer options is enabled
adb debugging is on
OEM unlocking is on
adb, fastboot tools are installed on PC
Steps:
Get new9008-0112.zip from: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999
Extract new9008-0112.zip > copy boot.img to your phone
Install Magisk: https://******************/downloading-magisk-manager
Open Magisk > Install > Path Boot Image File > direct to copied boot.img > It will generate a file > Close
Copy created patched_boot.img from device Downloads to your PC
Run cmd on pc > adb reboot bootloader > fastboot boot patched_boot.img
Device will boot > Open Magisk app > Install > Direct Install (Recommended) > Reboot
Congratulations, your device is now rooted!
Click to expand...
Click to collapse
All nice but if I do so on point 7. and it reboot it ask me for a pincode.
What is the pincode? or code I have to enter?

HvMES said:
All nice but if I do so on point 7. and it reboot it ask me for a pincode.
What is the pincode? or code I have to enter?
Click to expand...
Click to collapse
Before attempting to root the device I already had fingerprint / pin setup, hence just simply needed to re-enter the pin in that case. But, I was not sure if it is a must. Unfortunately, to fix it you will need to reset your os, using same steps as in https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999. Then ensure your device has pin installed, and then re-try rooting steps. I've updated my post with pin pre-req step.
---------- Post added at 04:12 PM ---------- Previous post was at 04:06 PM ----------
HvMES said:
Hi I have tried all but it is not clear to me I'm not able to root the YotaPhone 3+.
If it possible to give me a more clear instruction step by step. Also how to test if it is rooted?
It was a YotaPhone 3 and I updated it successful to the YotaPhone 3+ only I lost the IMEI 1 and 2. To add them I need to rood the Phone to add the EMEI or is there a option to add them NOT rooted.
Please help!!
Click to expand...
Click to collapse
To determine if you're device is rooted you will see in Magisk app two green tickboxes (Latest Version: v18.0; Installed Version: v18.0) even after you reboot your device.
Please specify what steps you're unclear about, but before doing that please read through comments in: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999 or google the step you're unclear about (especially pre-req ones)

vvinjj said:
Before attempting to root the device I already had fingerprint / pin setup, hence just simply needed to re-enter the pin in that case. But, I was not sure if it is a must. Unfortunately, to fix it you will need to reset your os, using same steps as in https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999. Then ensure your device has pin installed, and then re-try rooting steps. I've updated my post with pin pre-req step.
---------- Post added at 04:12 PM ---------- Previous post was at 04:06 PM ----------
To determine if you're device is rooted you will see in Magisk app two green tickboxes (Latest Version: v18.0; Installed Version: v18.0) even after you reboot your device.
Please specify what steps you're unclear about, but before doing that please read through comments in: https://forum.xda-developers.com/yotaphone-3/development/yota-3-firmware-news-t3862999 or google the step you're unclear about (especially pre-req ones)
Click to expand...
Click to collapse
Well I did now with a password and it looked OK but still it is not rooted.

has root been yota phone 3+ yet?
I have followed the instructions many times but still cannot succeed

Yota 3+ Stock Recovery access
1. On the phone off, press and hold the "Volume up" and "Power" keys
2. A robot will be lying with an open belly and an error on the lack of a command.
3. Lock the "Volume Down" and "Power" buttons, briefly pressing the "Volume Up" button

Yota 3+ 8.1 System Root with TWRP recovery, Magisk and storage encryption disabled
Merged 2nd instruction into 1st post.

I've tried the latest instruction; failed in cmd as following :
"Ensuring the bootloader is unlocked..."
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
Anyone?

nnlife82 said:
I've tried the latest instruction; failed in cmd as following :
"Ensuring the bootloader is unlocked..."
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
Anyone?
Click to expand...
Click to collapse
Can you check if in developer options OEM unlocking is ON (as in first instruction > pre-recs > step 4).

vvinjj said:
Can you check if in developer options OEM unlocking is ON (as in first instruction > pre-recs > step 4).
Click to expand...
Click to collapse
Yes, it's on.
So technically I don't have to unlock bootloader first right?

nnlife82 said:
Yes, it's on.
So technically I don't have to unlock bootloader first right?
Click to expand...
Click to collapse
If it was ON, the expected message in script should've been "Already unlocked" instead of message you've seen ("Need wipe userdata. Do 'fastboot oem unlock-go"). Maybe because in my case I had already unencrypted userdata at point of re-testing the script, it was working for me. Hence, I will fix the script by replacing "fastboot flashing unlock" to "fastboot oem unlock-go" to see if it fixes the issue for you.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
vvinjj said:
If it was ON, the expected message in script should've been "Already unlocked" instead of message you've seen ("Need wipe userdata. Do 'fastboot oem unlock-go"). Maybe because in my case I had already unencrypted userdata at point of re-testing the script, it was working for me. Hence, I will fix the script by replacing "fastboot flashing unlock" to "fastboot oem unlock-go" to see if it fixes the issue for you.
Click to expand...
Click to collapse
I've updated the script, please re-download install.bat

vvinjj said:
If it was ON, the expected message in script should've been "Already unlocked" instead of message you've seen ("Need wipe userdata. Do 'fastboot oem unlock-go"). Maybe because in my case I had already unencrypted userdata at point of re-testing the script, it was working for me. Hence, I will fix the script by replacing "fastboot flashing unlock" to "fastboot oem unlock-go" to see if it fixes the issue for you.
---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------
I've updated the script, please re-download install.bat
Click to expand...
Click to collapse
Thx dude, trying it.:fingers-crossed:
ps I just tried instruction 1 . When it told me to enter the pin after reboot, I did, but it says it's wrong. Can't boot, so reflashing now:silly: My phone is absurd lol

nnlife82 said:
Thx dude, trying it.:fingers-crossed:
ps I just tried instruction 1 . When it told me to enter the pin after reboot, I did, but it says it's wrong. Can't boot, so reflashing now:silly: My phone is absurd lol
Click to expand...
Click to collapse
Before you did the instruction 1 attempt, one of pre-recs was that your device had already pin setup (Settings > Security > Screen lock > PIN), did you have it? As the only use case I am aware of this situation is if you didn't have pin setup before. It would still ask you for pin, but it does't exist, hence wrong.

Pioneer XDP-300R Digital Audio Player - Root, TWRP Recovery, and Mods

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been successful at porting over TWRP (Team Win Recovery Project) Recovery to the Pioneer XDP-300R Digital Audio Player! The recovery can be flashed directly over the stock recovery using Fastboot, or you can temporarily boot into it using fastboot.
First off, TWRP, replaces the stock recovery and allows users to backup and restore system, data, boot and other partitions on their player onto their storage or sdcards. It also can install superuser (root) access if you want that feature to allow editing and modifying of the system folder. That opens the door for additional mods.
You can also install Magisk, which is a systemless root feature that is a little safer since it does not touch your system folder, but instead patches the bootloader and then creates a layer above system that stores the mods and changes within the Magisk system in.
First off, I made system image, bootloader and recovery images of the stock 300R prior to going into this full swing. I had already rooted my device using Kingoroot but this is no longer needed and is much more safe now.
So you'll want to get the recovery first.
https://drive.google.com/open?id=1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV
The link in my google drive will take you to a folder where I have backups of my images. The TWRP recovery is located in the Recovery folder, along with the stock Recovery image.
Tools Needed:
Android USB drivers for ADB and Fastboot
ADB and Fastboot
Terminal or Command Prompt
Some basic knowledge on how to use these tools
Pre-Installation:
In android, go to Settings, and turn on Developer Mode. To do this, click Settings, then Device Information, then scroll to Build Number. Tap this several times until you unlock Developer Options.
Now, go back to the Settings Menu and go to the new Developer Options menu. Check the OEM Unlocking option to allow the bootloader to be unlocked.
Installation of TWRP:
1. Download the TWRP image and place it in the same folder as ADB/Fastboot tools.
2. Open a terminal or cmd prompt window and go to the folder in (1)
Code:
EXAMPLE: cd /android
3. Turn off the 300R. Then hold next track (the button closest to SD slots) and press power and let go while holding the next track button. A Penguin will appear on screen. Then let go, and plug device into computer.
4. In terminal, check to see if fastboot works.
Code:
fastboot devices
5. If it does not show a device, check your drivers! If you see a device, let's go forward!
6. Now we will install the recovery.
First we need to unlock bootloader:
Code:
fastboot oem unlock
If you are nervous, and want to verify it works, you can do a temporary test by typing the command:
Code:
fastboot boot TWRP-XDP-300R.img
This will boot directly into the TWRP recovery and will go away when you restart. But you can see if it works this way and mounts each folder correctly.
If you're ready to take the plunge, use this command:
Code:
fastboot flash recovery TWRP-XDP-300R.img
7. Once it flashes, you can always reboot into recovery by powering off. Then holding PREV TRACK (button closest to power) and power on. It'll show the penguin, and then load recovery soon after.
8. Once you see the TWRP screen youre good to go! I recommend making a System, Data, and Boot backup immediately so you have it ready. I also have the stock recovery in the folder for backup purposes too!
Root Access
When you exit TWRP, you have the option of installing SuperUser (root) access. You're welcome to install or decline it. I recommend using Magisk at this point, by looking up Magisk Manager and loading that onto your device. It'll also provide root access along with other goodies like Xposed, some adblocking stuff, and if you like, Viper4Android, and other mods.
To first start the process of Magisk, you need to unlock the bootloader. Go into Fastboot mode again on the phone, as described above, and go to command prompt:
Code:
fastboot oem unlock
This command will unlock the bootloader. In the future, you can lock it by replacing unlock with lock: fastboot oem lock
Magisk only installs correctly when you use the magisk zip file that can be downloading through Magisk Manager. This zip file needs to be flashed in TWRP Recovery. Once you do that, it'll patch the bootloader and allow Magisk to work correctly. You can verify by opening Magisk Manager in Android, and seeing if it is activated.
Once activate, you can click the menu on the left side of the Manager app, and click DOWNLOADS to find a list of modules available for use. Not all are compatible with the older Android Lollipop that is on XDP-300R, so be careful of that.
Magisk Modules
Some modules I use are:
Xposed Framework - another modding system - see below
LKT - tweaks to the kernel for battery management
Magisk Manager for Recovery Mode - Recovery command line manager (seems buggy)
SafeMode4Magisk - Boots into safe mode for disabling bad modules
Swap Torpedo - Optimizes Swap files for RAM management
Youtube Vanced - Themes and removes ads from Youtube
Greenify - adds additional features to Greenify app
Xposed Framework (now systemless using Magisk!)
Some modules I use are:
Amplify - Standalone app that needs Xposed for disabling or reducing amount of system wakelocks and alarms which greatly save battery life
Greenify - Standalone app that hibernates unused apps to save battery life and uses Xposed for additional features
Youtube AdAway - Removes ads from Youtube
BUILD.PROP MODS
The Drive Link at the top of this page has my modified build.prop in it. You can replace your existing build.prop with this if you want. Make sure you make a backup just in case!
Diverting sound away from Android OS to the DAC:
Open up BUILD.PROP in /System in your android device and look for PCM Offload
There are two lines there, that start with audio.offload...
Remove the Hash in front of each of them if they are present and that's it!
it should read:
Code:
#PCM offload
audio.offload.pcm.16bit.enable=true
audio.offload.pcm.24bit.enable=true
Also verify that this is enabled:
Code:
av.offload.enable=true

Hi ! Thank your for your work ! There are a version for the XDP-100R please ?
(sorry for my bad english)

HI, I'm thankful for your development. But is there any chances to reflash the firmware if something goes wrong?

A few days ago on my xdp300r part of the system spilled out and actually are system applications. Nothing can be installed on it, is there any possibility of restoring the original state? Restarting and recovery mode unfortunately did not help.

Thanks alot. I needed this so bad. A long time after I bought XDP300R I can only dare to use superSU to get root access and that's it. And now xposed and magisk are possible, Thank you soo much.

Hi thanks. I managed it fine. I used su as majisk would not install. Luckily I followed your advice and made a backup(I don't usually bother). I installed your build.prop and the pioneer would not boot. I have restored using twrp and changed my own build.prop so alright now. Thanks.

HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel

gavroche33 said:
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
Click to expand...
Click to collapse
have you enabled the OEM unlock in the developer setting?

I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel

Grazie mille per il tuo lavoro

gavroche33 said:
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Click to expand...
Click to collapse
Go to setting, to Device Information, to Build Number. Tap 7 times. You get Developer Options
Back up go to Developer Iptions, select OEM Unlocking.
Re-do OEM unlocking as described in OP

Hi,
I tried to follow this tutorial but my device is not show I checked the drivers!
But still the same, is it possible to had any help ?

Since we already have an open bootloader, is there a chance to make a newer android, I propose version 9 because in newer ones you lose the ability to play some formats, it would certainly give a second life for this model

Dear XDA forum readers/members,
I have an issue with my Pioneer XDP-300R. At this stage I can only boot into it with the TWRP (TWRP-XDP-300R.img) image provided in the first post. I also have downloaded the recovery files, including the (stock?) system image (system-noxposed.img).
When I try to flash the same image from within TWRP, I can only select the "boot" or "recovery" partitions. In this screen, there is no option to boot towards a "system" partition.
If I boot from a ZIP file containing the system-noxposed.img file, I obtain either a different error which complains about a META-INF and binary not found? , or I obtain an error which (of course) writes there is too little space to write a system image in a boot or recovery partition.
My question(s) is/are: Is there any method to flash a system image towards the system partition from within TWRP, and/or how to solve the "unknown chunk type" error?
Any help would be greatly appreciated.
EDIT: The issue has been solved, but there is another problem now. When the device would not boot TWRP anymore (as in: froze at TWRP logo) I decided to look at the partitions (with dd): Now, I had made the mistake of overwriting the very first boot partition, and now the device will not power up anymore. By all means and purposes, he is hard bricked now If there is anyone who would like to help, I'd be very grateful, assuming there are still options left.
Greetings from a new member in need of help

Question Rooted tablet but not showing as being rooted P11 TB-J606F

This has been a roller-coaster ride so far getting a root on this tablet! Everything goes well but it still says I'm not rooted??
Branching off from this thread that I followed all the steps below from.
The adb and fastboot files I use come straight from Lenovo's dev community for flashing Android 13.
I go through all the step:​1) Download the newest version of Rescue And Smart Assistant (v6.1.1.9).
2) Had Rescue And Smart Assistant "rescue" in order to put on the newest firmware on the tablet (Android 11).
3) Waited until it said it was successful and it was.
4) I opened a cmd box with administrator rights.
5) Typed in the command adb devices to make sure I could see it and I did.
6) Typed adb reboot bootloader. The tablet restarts in bootloader mode screen.
7) Typed fastboot devices to make sure I could see it still and I did.
8) Typed fastboot flashing unlock. It brings up the warning. I chose continue and it does its thing.
9) Reboots back into normal Android Lenovo home screen.
10) I downloaded the newest Magisk v.25.0 app from their GitHub and place it into the download folder on the tablet.
11) Installed Magisk on the tablet. All goes well.
12) On my pc where Rescue And Smart Assistant placed the new firmware I copied over the boot.img file from it to the downloads of the tablet.
13) Open Magisk and went to install > Select and patch a file > download folder > boot.img. Patching goes fine.
14) Copied the boot.img from the tablet to my desktop.
15) Typed fastboot flash recovery boot.img and all goes fine.
16) Reboot back into normal Android Lenovo home screen.
17) Open Magisk and see that it's not rooted. Still says Installed: N/A.
19) I double-check this using SuperSU and it also says I'm not rooted.
This is my 5th time trying this and still no root.
Is doing fastboot flashing recovery boot.Img needed or is fastboot flash boot boot.img what needs to be used?
I’m seeing if Magisk shows Yes for the Ramdisk that you should use the flashing boot instead of the flash recovery because that means there is also a vbmeta.img file. Anyone use the flash boot command instead of the other?
Along with the above I have also noticed on some forums that you need to flash the vbmeta.img file after the boot.img? But also seen some do everything but that and it still worked?
Can someone who has the P11 help me out with this? Not sure what else to do?

stealthrt said:
This has been a roller-coaster ride so far getting a root on this tablet! Everything goes well but it still says I'm not rooted??
Branching off from this thread that I followed all the steps below from.
The adb and fastboot files I use come straight from Lenovo's dev community for flashing Android 13.
I go through all the step:​1) Download the newest version of Rescue And Smart Assistant (v6.1.1.9).
2) Had Rescue And Smart Assistant "rescue" in order to put on the newest firmware on the tablet (Android 11).
3) Waited until it said it was successful and it was.
4) I opened a cmd box with administrator rights.
5) Typed in the command adb devices to make sure I could see it and I did.
6) Typed adb reboot bootloader. The tablet restarts in bootloader mode screen.
7) Typed fastboot devices to make sure I could see it still and I did.
8) Typed fastboot flashing unlock. It brings up the warning. I chose continue and it does its thing.
9) Reboots back into normal Android Lenovo home screen.
10) I downloaded the newest Magisk v.25.0 app from their GitHub and place it into the download folder on the tablet.
11) Installed Magisk on the tablet. All goes well.
12) On my pc where Rescue And Smart Assistant placed the new firmware I copied over the boot.img file from it to the downloads of the tablet.
13) Open Magisk and went to install > Select and patch a file > download folder > boot.img. Patching goes fine.
14) Copied the boot.img from the tablet to my desktop.
15) Typed fastboot flash recovery boot.img and all goes fine.
16) Reboot back into normal Android Lenovo home screen.
17) Open Magisk and see that it's not rooted. Still says Installed: N/A.
19) I double-check this using SuperSU and it also says I'm not rooted.
This is my 5th time trying this and still no root.
Is doing fastboot flashing recovery boot.Img needed or is fastboot flash boot boot.img what needs to be used?
I’m seeing if Magisk shows Yes for the Ramdisk that you should use the flashing boot instead of the flash recovery because that means there is also a vbmeta.img file. Anyone use the flash boot command instead of the other?
Along with the above I have also noticed on some forums that you need to flash the vbmeta.img file after the boot.img? But also seen some do everything but that and it still worked?
Can someone who has the P11 help me out with this? Not sure what else to do?
Click to expand...
Click to collapse
What you need to do is
Code:
fastboot flash boot
not
Code:
fastboot flash recovery

stealthrt said:
15) Typed fastboot flash recovery boot.img and all goes fine.
Click to expand...
Click to collapse
This is where you get it wrong.

Yep it was due to not using the fastboot flash boot img.img command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Though when opening Magisk it says Your device needs additional setup for Magisk to work properly. Do you want to proceed and reboot?
Did you run into that as well?

No
stealthrt said:
Yep it was due to not using the fastboot flash boot img.img command.
View attachment 5638573
Though when opening Magisk it says Your device needs additional setup for Magisk to work properly. Do you want to proceed and reboot?
View attachment 5638575
Did you run into that as well?
Click to expand...
Click to collapse
No I did not.

stealthrt said:
This has been a roller-coaster ride so far getting a root on this tablet! Everything goes well but it still says I'm not rooted??
Branching off from this thread that I followed all the steps below from.
The adb and fastboot files I use come straight from Lenovo's dev community for flashing Android 13.
I go through all the step:​1) Download the newest version of Rescue And Smart Assistant (v6.1.1.9).
2) Had Rescue And Smart Assistant "rescue" in order to put on the newest firmware on the tablet (Android 11).
3) Waited until it said it was successful and it was.
4) I opened a cmd box with administrator rights.
5) Typed in the command adb devices to make sure I could see it and I did.
6) Typed adb reboot bootloader. The tablet restarts in bootloader mode screen.
7) Typed fastboot devices to make sure I could see it still and I did.
8) Typed fastboot flashing unlock. It brings up the warning. I chose continue and it does its thing.
9) Reboots back into normal Android Lenovo home screen.
10) I downloaded the newest Magisk v.25.0 app from their GitHub and place it into the download folder on the tablet.
11) Installed Magisk on the tablet. All goes well.
12) On my pc where Rescue And Smart Assistant placed the new firmware I copied over the boot.img file from it to the downloads of the tablet.
13) Open Magisk and went to install > Select and patch a file > download folder > boot.img. Patching goes fine.
14) Copied the boot.img from the tablet to my desktop.
15) Typed fastboot flash recovery boot.img and all goes fine.
16) Reboot back into normal Android Lenovo home screen.
17) Open Magisk and see that it's not rooted. Still says Installed: N/A.
19) I double-check this using SuperSU and it also says I'm not rooted.
This is my 5th time trying this and still no root.
Is doing fastboot flashing recovery boot.Img needed or is fastboot flash boot boot.img what needs to be used?
I’m seeing if Magisk shows Yes for the Ramdisk that you should use the flashing boot instead of the flash recovery because that means there is also a vbmeta.img file. Anyone use the flash boot command instead of the other?
Along with the above I have also noticed on some forums that you need to flash the vbmeta.img file after the boot.img? But also seen some do everything but that and it still worked?
Can someone who has the P11 help me out with this? Not sure what else to do?
Click to expand...
Click to collapse
Do you installed android stock on Tab p11 wifi versione?

iaio72 said:
Do you installed android stock on Tab p11 wifi versione?
Click to expand...
Click to collapse
Yes whatever RSA had for it. Android 11 is what it put on it before rooting it with Magisk.

stealthrt said:
Yes whatever RSA had for it. Android 11 is what it put on it before rooting it with Magisk.
Click to expand...
Click to collapse
all that guide is just to install magisk on the original fw?

Yes with transferring the .img file back and fourth.

i know this is a couple months later, im sorry but because of all the issues being answered this is no longer clear to follow. some people say they didnt need to do something that another person said they did need to do its become muddied. will someone please clear this up for me. and i cannot follow the guide on twrp it might need to be updated for android 11 or something. the xda guide for the m10 fhd2 now that is clear and i got that to work. but my p11 J606F is ready to root with unlocked bootloader but after that i get bootloops everywhere i try. thanks in advance to anyone willing to give a hand to someone caught between adv-noob/intermediate-r. after all this i might be closer to midranger. anyway goal is my p11 rooted with twrp and magisk both working fine like my m10 if its even possible yet.