Database Develop

[GUIDE] How to get root on the 10.1v

BEFORE YOU BEGIN
As always, mucking with your device at this level is risky. If you follow this process, you do so entirely at your own risk. I accept no responsibility for any detrimental effects resulting from following this process, or for any problems associated with the updated files. Only if you accept these risks should you use these instructions.
PREREQUISITES
Unlocked bootloader (see my guide to do this)
Working fastboot (also see my guide )
Patience
NOTES
I developed and followed this process on Ubuntu Natty, 64bit. I see no reason why it should not work on any other platform, since the only tool used is fastboot and the syntax for fastboot is the same on any platform. if you need to know how to get fastboot working, there are already many guides for that (see my how to unlock your bootloader thread, for example)
BUTTON CONFUSION
When in landscape mode, with the camera at the top, the power button is on the left 'vertical' side of the tab. On the top is the volume rocker. In this orientation:
- The LEFT side of the volume rocker is VOLUME DOWN
- The RIGHT side of the volume rocker is VOLUME UP
This might seem obvious, but to anyone who is used to phones, this is the opposite, since they were designed to be used in Portrait mode.
PREPARE
1) With your Tab in fastboot mode (step 1 of "GETTING ROOT" below), make sure you have a working fastboot implementation:
Code:
fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won't get any response.
2) Downlad View attachment skitzandroid-10-1v-root_0.2.zip and View attachment skitzandroid-stock-recovery.zip
3) Create a folder on your desktop called "root"
Code:
mkdir ~/Desktop/root
for Ubuntu or
Code:
md %userprofile%\desktop\root
for Windows
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!)
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder should now have 1 IMG file and one ZIP file.
6) This was an afterthought - Make sure fastboot is somewhere in your path (ie can be executed from anywhere). To test, 'cd' to any random folder and type 'fastboot' and make sure it runs.
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
Code:
adb push skitzandroid-10-1v-root.zip /sdcard/
from your working directory
...now the easy part
GETTING ROOT
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
Code:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
Code:
cd ~/Desktop/root
for Ubuntu or
Code:
cd %userprofile%\desktop\root
for Windows
5) Run the following command:
Temp Root:
Code:
fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
Permanent Root:
Code:
fastboot flash recovery skitzandroid-recovery.img
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options) to select "Install zip from SDCARD" (or something like that - if someone can post the exact menu item wording, I will update the guide). Press (tap!) the POWER button to confirm the menu selection
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
8) Once complete, use the Volume rocker to select "REBOOT" from the menu and press (tap!!!) the POWER button to confirm selection.
9) You're done! Press the thanks button on this thread to continue
TESTING
1) Once your Tab boots up, check your apps menu to confirm the existence of SuperUser app.
2) With the Tab attached to your PC via USB cable, do the following:
Code:
adb shell
su
..and watch the screen on your Tab for a SuperUser prompt. If you see this, congratulations!
If you have never rooted a phone/tablet before, go get Titanium Backup Pro and ROM Manager from the market. As soon as the custom ROMs start flowing in, you'll be all set to go.
Edit: How about thanking smaskell who was very patient and persistent in dumping the image from his Google IO 10.1 - for the good of his fellow XDA members. Without his help, this would not be possible.

Note that the above process doesn't flash the recovery, just loads it.
If you want to flash the recovery permanently, all you need to do is follow the guide above and then, in step 5, use this command instead:
Code:
fastboot flash recovery skitzandroid-recovery.img
You will then have a permanent recovery which you can get to by doing:
Code:
adb shell
su
reboot recovery
at any time.
Note that doing just
adb reboot recovery
Click to expand...
Click to collapse
...for some bizarre reason does not boot to recovery. Open up a shell first, as shown above.
I will also give you credit in the guide for having "Balls of Steel" to steal a phrase from PaulObrien
EDIT:
...and the Balls of Steel award goes to *drumroll*
Egan
...for having the balls to flash the recovery. Thanks egan. If I was in a battle, I'd definitely want you in our squad

FAQ
Does it need unlocked bootloader? Yes, see my other guide for this.
Do I need to wipe, or will it wipe my device? No and No.
Can I return my device to factory default config? Yes. This process does not flash the partition unless you follow the process in post 2 which is optional.
Changelog
0.2 - Added busybox (can be flashed over the top of 0.1 without wipe)
0.1 - Initial Relase
Factory Voda Tab Images
Recovery
Boot
System

Awesome news! Thanks to everyone who worked on this - I can't wait!

Great, great job you guys! This thing needs root so it can grow

Thanks a lot bcmobile and smaskell! Ill give it a go around launch.
Sent from my LG-P990 using XDA Premium App

Thank you guys, it's working great on my 10.1v

I'm pretty sure I know the answer to this already - but is there anyway of getting temp root on these devices so I can backup all my apps and data (properly) before unlocking / flashing recovery / rooting??

This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition

Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..

gjroeleveld said:
Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..
Click to expand...
Click to collapse
That's all the backup I have done so I hope so
Just uploading a new version of the update zip (v0.2) which includes busybox

bcmobile said:
This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition
Click to expand...
Click to collapse
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..

gjroeleveld said:
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Click to expand...
Click to collapse
Sorry for the ignorance, but are these fastboot or a adb commands?

Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Regards
EDIT:
black beard said:
Sorry for the ignorance, but are these fastboot or a adb commands?
Click to expand...
Click to collapse
These are adb commands you need to do with su!

black beard said:
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..
Click to expand...
Click to collapse
That is part of the recovery image, not the unlocked bootloader.
You can always put back a stock image using fastboot which is one of the really nice things about fastboot unlocking vs bootloader exploits. "fastboot oem unlock" can then be undone by "fastboot oem lock" and nobody would know the diff.

seraphimserapis said:
Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Click to expand...
Click to collapse
Thanks!
Yeah, oem unlock doesn't actually do anything until the next boot

Egan said:
Thanks a lot bcmobile and smaskell! Ill give it a go around lunch.
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .

Egan said:
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .
Click to expand...
Click to collapse
Are you going to flash it?
You will earn the official "Balls of steel" badge

Thanks,
Also remember to enable USB debugging after you have done the unlocked bootloader, took me 5 min to to realize why adb did not want to work, 5 scary min after the reboot.

I've tried to make a proper nandroid backup but haven't been able too.
Tried with romdump 0.72 but that crashes :-(
Most tutorials use Rom Manager, but that needs some work from @koush before we can use it.
I'll google on
Sent from my GT-I9000 using XDA Premium App

[WIP] [REQUEST] Misc partition dumps

Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.

Edit: nvm
Here is the dump. Thanks for your work.

KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.

KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?

I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.

KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command

I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....

KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"

Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method

KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.

Glad I could help. Now folks have less things to worry about when they decide to root

KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.

efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.

KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).

For science

KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.

osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.

[Easiest Method] Tutorial to Unlock Bootloader | Install Twrp | Root | Decrypt Data

Hi All ,
Steps To Unlock Bootloader
1. At First, open About phone on setting menu , then tap 4 times on Build Number. Now Developer Mode is enabled.
2. Open developer Mode menu and set oem unlock and usb debugging to ON. [Important Step]
3. Download and Extract the zip file which you have downloaded from the link given below.
4. Now enter into fastboot mode :
Press volume + power button and then phone will boot into fastboot interface.
5. Now connect the phone to computer and then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here)
Now type:
Code:
fastboot devices
The list of devices connected will be displayed.
Then enter the command :
Code:
fastboot oem unlock
6. Now you will see a Unlock Bootloader Warning page. Hit the Vol button to select Yes and turn it Blue and Hit Power Button to confirm the selection.
7. Thats it . Now your Bootloader is unlocked.
Steps To Install TWRP Recovery
1. After you have successfully unlocked the bootloader, now enter into the fastboot mode and connect the phone to pc.
2. Now navigate to the folder where you have extracted the downloaded zip file and open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here)
Now type:
Code:
fastboot devices
3. The list of devices connected will be displayed.
4. Then enter the command :
Code:
fastboot flash recovery twrp-3.1.1-0-oneplus5.img
or
Code:
fastboot flash recovery (name of the twrp file).img
5. When the file is flashed successfully , unplug your phone from pc and manually boot the phone into recovery by pressing Power + Volume Down button.
6. Now the TWRP Recovery will be opened .
For the Users who face Max download error while flashing Twrp, Kindly check the post here
Steps To Disable Forced Encryption i.e, Decrypt Data
1. At first time when you open twrp, it will ask you to allow system modification.
2. Allow it and then flash the no-verity-opt-encrypt.zip file .
3. Then Go to Wipe-->Format Data.
4. Type Yes to confirm wiping of Internal Storage.
5. Now you have decrypted the data sucessfully.
Note: Dont try to restore the nanodroid backup which you have taken before. It may end in bootloop.
Steps To Root Your Phone
1. Download the SuperSu SR1 flashable zip from here and copy that zip file into internal storage.
2. Now Enter into the TWRP Recovery.
3. Now navigate to the downloaded SuperSu Zip file and Swipe to install SuperSu.
4. Reboot your device.
5. Now your device is rooted successfully. :fingers-crossed:
Steps To Backup IMEI [Important]:
For some cases you may lead to lose your device's Imei. It will lead to loose of network signals etc.
So we have to take backup of Imei and we can restore it on any such case.
There are two method to backup imei.
Method 1 :
Boot the phone to Twrp , take Backup of EFS partition to internal storage and copy the backup files to PC . In case , if you have lost your IMEI, this backup will help you to restore imei back.
Method 2 :
1. This method works on the Terminal window. So download any Terminal App .
2. Open the app and type su , then grant SuperUser permission when you are prompted to do so.
When you see the Terminal Emulator box, type the following command:
Code:
dd if=/dev/block/sdf1 of=/sdcard/modemst1.bin bs=512
Code:
dd if=/dev/block/sdf1 of=/sdcard/modemst2.bin bs=512
Please note that all commands are case sensitive and even a minor mistake will hider the successful backup. Type the command line carefully.
Now you have successfully took backup of imei to you internal storage . Copy that to your pc .
To Restore
Enter the following commands in Terminal Emulator Box:
Code:
dd if=/sdcard/modemst1.bin of=/dev/block/sdf1 bs=512
Code:
dd if=/sdcard/modemst2.bin of=/dev/block/sdf1 bs=512
Thats it your imei is restored :fingers-crossed:
Download Section
For TWRP recovery and other files Download Here
If u need Only twrp, Den click here
1. twrp-3.1.1-1-cheeseburger.img[official]
2. twrp-3.1.1-0-oneplus5.img [chinese]
3. Twrp latest by xdvs23

Thank you very much! Good to see TWRP here

HatRiGt said:
Hi All,
Steps To Unlock Bootloader
1. At First, open About phone on setting menu , then tap 4 times on Build Number. Now Developer Mode is enabled.
2. Open developer Mode menu and set oem unlock and usb debugging to ON. [Important Step]
3. Download and Extract the zip file which you have downloaded from the link given below.
4. Now enter into fastboot mode :
Press volume + power button and then phone will boot into fastboot interface.
5. Now connect the phone to computer and then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here)
Now type:
The list of devices connected will be displayed.
Then enter the command :
6. Now you will see a Unlock Bootloader Warning page. Hit the Vol button to select Yes and turn it Blue and Hit Power Button to confirm the selection.
7. Thats it . Now your Bootloader is unlocked.
Steps To Install TWRP Recovery
1. After you have successfully unlocked the bootloader, now enter into the fastboot mode and connect the phone to pc.
2. Now navigate to the folder where you have extracted the downloaded zip file and open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here)
Now type:
3. The list of devices connected will be displayed.
4. Then enter the command :
5. When the file is flashed successfully , unplug your phone from pc and manually boot the phone into recovery by pressing Power + Volume Down button.
6. Now the TWRP Recovery will be opened .
Steps To Root Your Phone
1. Download the SuperSu flashable zip from here and copy that zip file into internal storage.
2. Now Enter into the TWRP Recovery.
3. Now navigate to the downloaded SuperSu Zip file and Swipe to install SuperSu.
4. Reboot your device.
5. Now your device is rooted successfully.
Download Section
Download the required zip file from Here
Credits : Thanks to chinese Dev for Twrp
Click to expand...
Click to collapse
Hey,
Thanks for the guide. However, where does the TWRP comme from? I'm a bit afraid of this, truth to be told ^^'

matssa said:
Hey,
Thanks for the guide. However, where does the TWRP comme from? I'm a bit afraid of this, truth to be told ^^'
Click to expand...
Click to collapse
source link added . check bro.

HatRiGt said:
source link added . check bro.
Click to expand...
Click to collapse
Erm, "Chinese dev" doesn't mean anything really. Don't you have a thread link, a github link, or anything in particular? It's almost like saying "Here an app", without really saying where it comes from. Kinda risky... Especially if it isn't the "Chinese dev" that shares it.
EDIT/// NVM, just was the source link... Sorry for that, was refreshing the wrong one...

matssa said:
Erm, "Chinese dev" doesn't mean anything really. Don't you have a thread link, a github link, or anything in particular? It's almost like saying "Here an app", without really saying where it comes from. Kinda risky... Especially if it isn't the "Chinese dev" that shares it.
Click to expand...
Click to collapse
kindly check the source link i.e, thread link
-----
Tested by me. Works fine.

HatRiGt said:
kindly check the source link i.e, thread link
Click to expand...
Click to collapse
Yeah just edited my comment, wasn't looking at the correct page... Gonna take a look, might wait a bit before testing.

I went to the source OP provided. It's 30 pages of people saying thanks...so I bit the bullet (after unlocking bootloader).
It works. Just flashed Magisk 13 beta using TWRP provided by OP.
SafetyNet passes with Magisk Hide. Cheers!

it work for me, thanks

HatRiGt said:
kindly check the source link i.e, thread link
Click to expand...
Click to collapse
When checking your link, I can't really see if everyone managed to test it correctly, Google translation shows some icky stuff in terms of device bricking.

matssa said:
Yeah just edited my comment, wasn't looking at the correct page... Gonna take a look, might wait a bit before testing.
Click to expand...
Click to collapse
I'm in the same boat, I like that it's done but the fact it isn't open-sourced and is provided by a sketchy Chinese version of a fake Oneplus site (take a look at the lack of SSL for example), I think I may hold off..
Thanks for sharing though OP, hope this might spark what we need to get the official version!

SonicSamZ said:
I went to the source OP provided. It's 30 pages of people saying thanks...so I bit the bullet (after unlocking bootloader).
It works. Just flashed Magisk 13 beta using TWRP provided by OP.
SafetyNet passes with Magisk Hide. Cheers!
Click to expand...
Click to collapse
bretzelpopo said:
it work for me, thanks
Click to expand...
Click to collapse
How did you make this work? Tried flashing in fastboot using
fastboot flash recovery twrp.....
However, doesn't work, still on OP recovery
EDIT/// Apparently worked Can't wait for a more open and official one

Have make a backup and this working. Only light dimming not work for now.

SonicSamZ said:
I went to the source OP provided. It's 30 pages of people saying thanks...so I bit the bullet (after unlocking bootloader).
It works. Just flashed Magisk 13 beta using TWRP provided by OP.
SafetyNet passes with Magisk Hide. Cheers!
Click to expand...
Click to collapse
Flashed it too after reading your post. Working flawless.

The China TWRP only work first time. After reboot again i see the stock recovery.

Schrotty35 said:
The China TWRP only work first time. After reboot again i see the stock recovery.
Click to expand...
Click to collapse
Maybe you need to delete recovery-from-boot.p from your system folder, and the twrp will be permanently

mauronofrio said:
Maybe you need to delete recovery-from-boot.p from your system folder, and the twrp will be permanently
Click to expand...
Click to collapse
Have you test this?

Schrotty35 said:
Have you test this?
Click to expand...
Click to collapse
If I had OnePlus 5 I would have resolved the problem inside the twrp, but no device is impossible for me. A complete recovery will soon be released.
The recovery-from-boot.p is the file that restore stock recovery when you reboot your phone (It is in all android firmware)

Schrotty35 said:
Have you test this?
Click to expand...
Click to collapse
did you restore your backup, after reboot . If yes, just uncheck boot when you restore and you dont need to format anything when flash recovery or kernel because these thing boot before system . For me twrp work good for me, the only thing is that i have flash supersu and when i want to switch to magisk, i delete all root on supersu app, and then impossible to boot on twrp, even after flash it with bootloader . The trick is to flash stock recovery from folder and then flash twrp .

Thanks

[ROM][STOCK] OOS International 9.0.6 Fastboot For Windows/Linux/Mac

Hey there everyone! Seeing as there's not a publicly released 9.0.6 Fastboot only ROM for the T-Mobile variant users, I've taken the liberty to package something up for you!
This tool includes the most recent fastboot for Windows, Linux, and Mac.
Please do not unzip the images.zip file, as it will be done by the tool automatically!
This tool can be used to correct a soft brick (as long as you can get into fastboot you can fix it!), as well as simply flash the International Variant to both the T-Mobile version, as well as the International model.
You must be in fastboot mode prior to running these scripts!
On Windows:
Simply unzip the zip and double click the windows-flash-all-partitions.bat file.
Wait for the images.zip file to finish extracting. (This requires powershell, if you don't have it, unzip the images.zip file to the images directory)
You will be prompted with the option to format your device. Type Y or y for Yes, N or n for No.
Fastboot will begin flashing the partitions for you!
Your device will reboot at the end.
On Linux:
Simply unzip the zip and then cd to the directory with your console.
Ensure you have the unzip command available. If you don't, for some reason, unzip the images.zip file to the images directory.
cd to the unzipped folder and run the following command: sudo ./linux-flash-all-partitions.sh
You will be prompted with the option to format your device. You can type the following: Y,y for Yes, N,n for no.
Fastboot will begin flashing the partitions for you!
Your device will reboot at the end!
For Mac Users: (Console/Terminal Use)
Simply unzip the zip and then cd to the directory with your console.
Ensure you have the unzip command available. If you don't, for some reason, unzip the images.zip file to the images directory.
Run the following command: sudo ./mac-flash-all-partitions.sh
You will be prompted with the option to format your device. You can type the following: Y,y for Yes, N,n for no.
Fastboot will begin flashing the partitions for you!
Your device will reboot at the end!
Upgrading from 9.0.5 should not require a data wipe, but your mileage may vary.
This does not touch any critical partitions, nor does it even try to.
While this should work for the International version as well, it does not flash any critical partitions.
Google Drive Link v1.1: https://drive.google.com/open?id=1oGMQ80He9ORD2yT7jEeOtvUPvRa4U9h_
Of course, let me know if you have any trouble!

Dameon87 said:
Hey there everyone! Seeing as there's not a publicly released 9.0.6 Fastboot only ROM for the T-Mobile variant users, I've taken the liberty to package something up for you!
This tool includes the most recent fastboot for both Windows and Linux.
Please do not unzip the images.zip file, as it will be done by the tool automatically!
On Windows:
* Simply unzip the zip and double click the windows-flash-all-partitions.bat file.
* Wait for the images.zip file to finish extracting. (This requires powershell, if you don't have it, unzip the images.zip file to the images directory)
* You will be prompted with the option to format your device. Type Y or y for Yes, N or n for No.
* Fastboot will begin flashing the partitions for you!
* Your device will reboot at the end.
On Linux:
* Simply unzip the zip and then cd to the directory with your console.
* Ensure you have the unzip command available. If you don't, for some reason, unzip the images.zip file to the images directory.
* run the following command: sudo ./linux-flash-all-partitions.sh
* You will be prompted with the option to format your device. You can type the following: Y,y for Yes, N,n for no.
* Fastboot will begin flashing the partitions for you!
* Your device will reboot at the end!
Upgrading from 9.0.5 should not require a data wipe, but your mileage may vary.
This does not touch any critical partitions, nor does it even try to.
While this should work for the International version as well, it does not flash any critical partitions.
Google Drive Link: https://drive.google.com/file/d/1ii59cmGVUcohZAiJB47fKoJQyikJVaLR/view?usp=sharing
Of course, let me know if you have any trouble!
Click to expand...
Click to collapse
Says TMO. Is this the t-mobile rom?

lollyjay said:
Says TMO. Is this the t-mobile rom?
Click to expand...
Click to collapse
No, it the international version! Sorry!

Dameon87 said:
No, it the international version! Sorry!
Click to expand...
Click to collapse
Thanks you might want to rename it to avoid any confusion
Sent from my crosshatch using XDA Labs

lollyjay said:
Thanks you might want to rename it to avoid any confusion
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Already done!

So can I follow this to flash 9.0.6 on my TMobile 9.0 version? I just received the unlock bin.
Sent from my ONEPLUS A6013 using Tapatalk

Have tmobile purchased phone. unlocked of course and already running 9.0.5 international rom with no issues.
I am rooted with magisk.
when updating from 9.0.5 to 9.0.6 do I need to do any prep work? Uninstall magisk first?
OR just do what's in the OP and choose not to wipe?

raing said:
Have tmobile purchased phone. unlocked of course and already running 9.0.5 international rom with no issues.
I am rooted with magisk.
when updating from 9.0.5 to 9.0.6 do I need to do any prep work? Uninstall magisk first?
OR just do what's in the OP and choose not to wipe?
Click to expand...
Click to collapse
As long as you don't have any magisk modules that are known to bootloop when uninstalled (The Always on Display one will do this), you should be just fine! I was rooted with Magisk and upgraded to 9.0.6 without a wipe just fine.
Of course afterwards you will need to root again!

_nkay_ said:
So can I follow this to flash 9.0.6 on my TMobile 9.0 version? I just received the unlock bin.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Yes. After you unlock your bootloader you can use this to flash 9.0.6 to your device. You will -need- to wipe, though. So when the question is prompted to format your device, type Y.

@DaeMon87 your instructions say if you do not have power shell, I am on windows 7, so extract the image to the working adb folder?

Some strange reason didnt work for me. im on 9.0.5 right now..

phillymade said:
@DaeMon87 your instructions say if you do not have power shell, I am on windows 7, so extract the image to the working adb folder?
Click to expand...
Click to collapse
Windows 7 has powershell I believe. Try running the bat file. It's safe. It literally won't let you continue if the files don't exist.

djhotsauce said:
Some strange reason didnt work for me. im on 9.0.5 right now..
Click to expand...
Click to collapse
Gimme 5. When I made a find/replace I accidentally deleted a part of each command! Sorry about that! I'll upload an updated bat here in a min for you.
Updated Tools attached to post.

Dameon87 said:
Gimme 5. When I made a find/replace I accidentally deleted a part of each command! Sorry about that! I'll upload an updated bat here in a min for you.
Updated Tools attached to post.
Click to expand...
Click to collapse
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
still getting two errors
***nevermind i just got the file from the .zip.***

djhotsauce said:
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
still getting two errors
Click to expand...
Click to collapse
Likely those files were not properly unzipped. Try extracting them directly from images.zip and putting them into the images directory.

Dameon87 said:
Windows 7 has powershell I believe. Try running the bat file. It's safe. It literally won't let you continue if the files don't exist.
Click to expand...
Click to collapse
How do I force the .bat file to load in powershell rather than cmd. I am on Windows 10 so I know I have powershell just not familiar with it. Second question, since I used the OnePlus one rooter before to install magisk can I use that again or do I have to do it the old fashioned way ? Thank you for putting this together by the way!

OP updated with a new copy of the files including the mac version and the fixes for the flashing files.

feezler said:
How do I force the .bat file to load in powershell rather than cmd. I am on Windows 10 so I know I have powershell just not familiar with it. Second question, since I used the OnePlus one rooter before to install magisk can I use that again or do I have to do it the old fashioned way ? Thank you for putting this together by the way!
Click to expand...
Click to collapse
You don't need to! Just double click the .bat file. It simply runs the unzip command in powershell to avoid having to package anything else in the zip.
However, if you haven't grabbed the fixed bat file from the OP, please do so!
As for the OnePlus rooter, you can just use it again

Dameon87 said:
OP updated with a new copy of the files including the mac version and the fixes for the flashing files.
Click to expand...
Click to collapse
Does the google drive link have the updated tools? Or should users also download the updated tools?
Sent from my crosshatch using XDA Labs

Dameon87 said:
You don't need to! Just double click the .bat file. It simply runs the unzip command in powershell to avoid having to package anything else in the zip.
However, if you haven't grabbed the fixed bat file from the OP, please do so!
As for the OnePlus rooter, you can just use it again
Click to expand...
Click to collapse
Fantastic! I will give this a shot tonight ...fingers crossed!

I need HELP. My Pixel 4xl is stuck on fastbood mode

Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.

blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/images and flash manually it's work with me
Sent from my BASIC using Tapatalk

When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.

TENN3R said:
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
Click to expand...
Click to collapse
Just to add to this, make sure you left the image-coral-[buildnumber].[builddate].zip ZIPPED. Your folder should look something like this one, although you might also have your platform-tools in that same directory, which is perfectly fine, but not necessary if you have them added to your path.
Just try redoing the flash-all.bat again. This time, though, do it from powershell. Here's what to do. Right click in the folder, not on any item, just in the folder, and you should see "open powershell" (or command prompt, if this is the case, then just type powershell into the cmd window), click that. Then, type or copy and paste into the powershell prompt while in that directory:
.\flash-all.bat | Tee xda-flash-attempt.log
and if it still doesn't work and you're stuck in fastboot, just upload that .log file, so we can see what happened. If you're curious, what Tee does is it simultaneously takes standard input (i.e. what you see on the screen, the output of programs) and shows it to you, as well as sends it to a file, in this case, the xda-flash-attempt.log If you really don't want to use powershell, you can accomplish what's needed by typing flash-all.bat > xda-flash-attempt.log, but you will not see any of the output, as it will all be piped into that file. The | key is the one directly below backspace, which is the same key as \, but with shift held down.
Also, if it's not working, it might be worth checking that the checksum of the zip file you downloaded is correct, possibly redownloading it, and also checking what the flash-all.bat contents are. There are two files named flash-all in the folder, one a .sh for *nix systems, and a .bat for windows. While it should automatically assume you meant the .bat, it's best to be explicit. The .sh really wouldn't do anything different, if it worked, so it's a minor issue that really wouldn't make a difference, but still.
Edit: when you do type flash-all, the cmd prompt was in the directory with the flash-all.bat file as well as all of the other necessary files, yes? Seems obvious, perhaps, but just based on the "cd\pp\p" command you ran, which doesn't do anything, you should be changing directory to the directory that holds the flash-all.bat as well as the firmware.

blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today ...
Click to expand...
Click to collapse
Like others have said, you need to extract the Google image which has a nested zip file (which you leave alone unless you need something in there). Since you apparently are stuck and cannot boot, I suggest you extract the boot.img from that nested zip file into your tools folder and fastboot flash the boot.img to be able to boot the phone to system. You may need to do the vol-down button press to enter fastboot mode. Once you have your phone back and running, boot into fastboot mode and run the flash-all again. If you extracted the Google image completely, now the script can finish. Not sure if you want to wipe the phone while doing this, so you can also "dirty flash" . If you would like to retain all your apps and app data, edit the flash-all script with notepad and remove the wipe flag (-w) from the script and SAVE it before running. Best of luck. :good:

blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Put the unzipped factory image files (should be 6 of them) in your platform tools folder and then open up the command prompt in the platform tools folder and execute the flash-all command. Make sure all remnants of previous factory images, etc. are removed from the platform tools folder beforehand as well so you just have the platform tools default files in there as well as the 6 files from the factory image.
The latest version of platform tools is 30.0.4 I believe so make sure you have that version.

I just switched from a Pixel 2 xl and ran into the exact same problem with the no valid slot to boot error yesterday. It turned out I was not using the latest platform tools when flashing the factory image. I upgraded my platform tools to 30.04 and everything flashed and booted as expected.

Make sure you're using an A to C and not the C to C that comes with the phone when flashing. Yes, it matters.

Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.

blackbomb1991 said:
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
Click to expand...
Click to collapse
Woohoo! This worked perfectly. Thanks for following up with the instructions.