Database Develop

[ROOT][CWM] Root Nexus 4 & Install Official ClockworkMod Recovery

I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.

Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.

Checked...thanks. =) Added the links.

stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied

jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.

BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.

HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.

I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.

Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.

I installed after ota
Sent from my SGH-T999 using Tapatalk 2

jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.

when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?

Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2

Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.

After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!

quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?

Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)

0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.

HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?

[Q] htc one no rom

phone is unlocked just need to flash the rom, no recovey no backup nothing, plz help step by step.

if you have no adb; get it from here: http://forum.xda-developers.com/showthread.php?t=2317790
download TWRP recovery from here: http://goo.im/devs/OpenRecovery/m7ul/openrecovery-twrp-2.6.3.4-m7ul.img
place your downloaded recovery file in your adb folder
keep your phone in bootloader/hboot and connect your device to PC
start adb command prompt and type
fastboot devices
Click to expand...
Click to collapse
if your device gets recognized type the following commands:
fastboot erase cache
fastboot flash recovery recovery_file_name.img
Click to expand...
Click to collapse
and done
if you have no ROM inside your SDcard you can sideload it by following this guide

appreciate
kamilmirza said:
if you have no adb; get it from here: http://forum.xda-developers.com/showthread.php?t=2317790
download TWRP recovery from here: http://goo.im/devs/OpenRecovery/m7ul/openrecovery-twrp-2.6.3.4-m7ul.img
place your downloaded recovery file in your adb folder
keep your phone in bootloader/hboot and connect your device to PC
start adb command prompt and type
if your device gets recognized type the following commands:
and done
if you have no ROM inside your SDcard you can sideload it by following this guide
Click to expand...
Click to collapse
let me do this if any problem occurs will let u know...

rom
dsthakur said:
let me do this if any problem occurs will let u know...
Click to expand...
Click to collapse
plz suggest the address(download link) from where i can download the rom. It's my first attempt.

dsthakur said:
plz suggest the address(download link) from where i can download the rom. It's my first attempt.
Click to expand...
Click to collapse
i suggest you to use ARHD, is the best rom for the moment, but before make sure you have the latest TWRP.
ARHD: http://forum.xda-developers.com/showthread.php?t=2183023
TWRP: http://forum.xda-developers.com/showthread.php?t=2173870
Regards,
Keli

rom
dsthakur said:
let me do this if any problem occurs will let u know...
Click to expand...
Click to collapse
nothing happens after typing fastboot devices in adb command prompt. what to do next

dsthakur said:
nothing happens after typing fastboot devices in adb command prompt. what to do next
Click to expand...
Click to collapse
Have u installed the fastboot, adb drivers nd htc sync manager? All these 3 have to be installed for tge phone to be recognized. If adb devices shows nothing, then ur phone is not being recognized.

dsthakur said:
nothing happens after typing fastboot devices in adb command prompt. what to do next
Click to expand...
Click to collapse
how are you doing this?
are you using Windows 8?
please elaborate
Sent from my One using Tapatalk

rom
kamilmirza said:
how are you doing this?
are you using Windows 8?
please elaborate
Sent from my One using Tapatalk
Click to expand...
Click to collapse
after unlocking i followed this step the one in the image 1(this snapshot is from video which i followed, i didn't took mine during that), then i came to 2nd stage recovery, i don't know whether it was in the phone earlier or came after 1st process. I'm stuck at this only because i don't know anything about this, only want to start my phone in any how. have downloaded all the stuff :
1.minimal_adb_fastboot_v1.1.3_setup
2.recovery_v.0.5.img
3.openrecovery-twrp-2.6.3.4-m7ul_6.img
4.UPDATE-SuperSU-v1.91
5.Android_Revolution_HD-One_51.0
OS is windows 7 x64.

dsthakur said:
after unlocking i followed this step the one in the image 1(this snapshot is from video which i followed, i didn't took mine during that), then i came to 2nd stage recovery, i don't know whether it was in the phone earlier or came after 1st process. I'm stuck at this only because i don't know anything about this, only want to start my phone in any how. have downloaded all the stuff :
1.minimal_adb_fastboot_v1.1.3_setup
2.recovery_v.0.5.img
3.openrecovery-twrp-2.6.3.4-m7ul_6.img
4.UPDATE-SuperSU-v1.91
5.Android_Revolution_HD-One_51.0
OS is windows 7 x64.
Click to expand...
Click to collapse
please follow the steps from my first post

dsthakur said:
after unlocking i followed this step the one in the image 1(this snapshot is from video which i followed, i didn't took mine during that), then i came to 2nd stage recovery, i don't know whether it was in the phone earlier or came after 1st process. I'm stuck at this only because i don't know anything about this, only want to start my phone in any how. have downloaded all the stuff :
1.minimal_adb_fastboot_v1.1.3_setup
2.recovery_v.0.5.img
3.openrecovery-twrp-2.6.3.4-m7ul_6.img
4.UPDATE-SuperSU-v1.91
5.Android_Revolution_HD-One_51.0
OS is windows 7 x64.
Click to expand...
Click to collapse
You can try it this way:
Copy ROM zip file to c:\mini-sdk and rename it to "rom.zip"
In the same command prompt window type and confirm each command with ENTER:
mount /data
mkdir -p /data/media/0
exit
adb push rom.zip /data/media/0
Copying rom.zip to the device will take a few minutes. Wait until it's done. The output should be: xxxx KB/s (xxxxxxxxxx bytes in xxx.xxxs). Now you can flash rom.zip from inside custom recovery. Done!
http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html

[GUIDE] LG L90 D415 (US - Lollipop) - Install TWRP

My terrible video guide to follow: http://youtu.be/1UkPPqfz3kE (really really bad video guide that i just winged but it explains the basics of what you need and what you do)
Here's the textual guide:
Requirements:
1. Rooted Lollipop D415 - http://forum.xda-developers.com/lg-l90/general/guide-root-lg-l90-running-d41510e-t3072568
2. Terminal App (Must have SuperUser Enabled to work)
3. twrp.img - https://drive.google.com/file/d/0B08SrD985jkQMko3LTFZRFpZdG8/view?usp=sharing
4. Unlocked Bootloader (Supposedly) http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
(Hopefully those are all)
Steps:
1. Turn on the phone (no brainer)
2. Ensure your phone is rooted
2.5. Put twrp.img into /sdcard
3. Go to your terminal app and type in this command (WITH SU): dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
It should take a few seconds before it gives out a little output saying so and so was transferred.
4. Type in 'reboot recovery' with SU and you should boot right into a fresh custom recovery.
I do not take credit for any of the stuff made here. I just made the guide, not the .img, or the apps. Just the guide.
(TWRP on KitKat 4.4: http://forum.xda-developers.com/lg-l90/general/video-guide-installing-twrp-custom-t2975417)
Disclaimer: I do not take responsibility for damage done to your phone. You do this at your own risk.

TWRP will not flash no matter what flash tool I use, I'll flash the img. & boot to recovery but no TWRP. Any suggestions?
Sent from my LG-D415 using XDA Premium 4 mobile app

GENIUS!
Sadcamp said:
My terrible video guide to follow: http://youtu.be/1UkPPqfz3kE (really really bad video guide that i just winged but it explains the basics of what you need and what you do)
Here's the textual guide:
Requirements:
1. Rooted Lollipop D415 - http://forum.xda-developers.com/lg-l90/general/guide-root-lg-l90-running-d41510e-t3072568
2. Terminal App (Must have SuperUser Enabled to work)
3. twrp.img - https://drive.google.com/file/d/0B08SrD985jkQMko3LTFZRFpZdG8/view?usp=sharing
4. Unlocked Bootloader (Supposedly) http://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
(Hopefully those are all)
Steps:
1. Turn on the phone (no brainer)
2. Ensure your phone is rooted
2.5. Put twrp.img into /sdcard
3. Go to your terminal app and type in this command (WITH SU): dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
It should take a few seconds before it gives out a little output saying so and so was transferred.
4. Type in 'reboot recovery' with SU and you should boot right into a fresh custom recovery.
I do not take credit for any of the stuff made here. I just made the guide, not the .img, or the apps. Just the guide.
(TWRP on KitKat 4.4: http://forum.xda-developers.com/lg-l90/general/video-guide-installing-twrp-custom-t2975417)
Disclaimer: I do not take responsibility for damage done to your phone. You do this at your own risk.
Click to expand...
Click to collapse
You my friend are a freaking genius! this saved my D415 and I was so worried. It works just awesome!
Thanks once again!

stevenDROID said:
TWRP will not flash no matter what flash tool I use, I'll flash the img. & boot to recovery but no TWRP. Any suggestions?
Sent from my LG-D415 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Extremely sorry for my late reply, but
are you sure you have not tried the terminal app i suggested in the video?

I used flashify. No computer. From stock to cm 13 in 10 minutes. Lol. This is one of my many fun hack phones all budget. My note 5 is staying unrooted

Another really simple way is a rooted device and LG L90 utilities app. Search XDA it's made by member shinobisoft
Wonderful app. Doesn't work on 6.0 & 6.0.1

TWRP version
Can I use another (recent) version of TWRP or this way is just functional with the linked twrp.img?

AlexJSK said:
Can I use another (recent) version of TWRP or this way is just functional with the linked twrp.img?
Click to expand...
Click to collapse
Any TWRP in IMG format should work. Just mke sure you have a D415 since it has a partition map that's is different from other models and this tutorial uses an adb command that is suitable to D415 only.

Need help i put in the command exactly as posted "dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17" and it keeps giving an error that it doesn't exist i did move the file to the sdcard after installing it but still same thing. The fileyou linked once downloaded actually downloads as "0B08SrD985jkQMko3LTFZRFpZdG8.bat" should i replace the twrp.img line with this name or rename the file to twrp.img or what? Im confused as im trying to learn but not fluent in this process.
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
xxlcountryguy83 said:
Need help i put in the command exactly as posted "dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17" and it keeps giving an error that it doesn't exist i did move the file to the sdcard after installing it but still same thing. The fileyou linked once downloaded actually downloads as "0B08SrD985jkQMko3LTFZRFpZdG8.bat" should i replace the twrp.img line with this name or rename the file to twrp.img or what? Im confused as im trying to learn but not fluent in this process.
Click to expand...
Click to collapse
0B08SrD985jkQMko3LTFZRFpZdG8.bin sorry it downloads as .bin not .bat

xxlcountryguy83 said:
Need help i put in the command exactly as posted "dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17" and it keeps giving an error that it doesn't exist i did move the file to the sdcard after installing it but still same thing. The fileyou linked once downloaded actually downloads as "0B08SrD985jkQMko3LTFZRFpZdG8.bat" should i replace the twrp.img line with this name or rename the file to twrp.img or what? Im confused as im trying to learn but not fluent in this process.
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
0B08SrD985jkQMko3LTFZRFpZdG8.bin sorry it downloads as .bin not .bat
Click to expand...
Click to collapse
Are you still on KitKat? If you are already rooted, and probably are, you can use an app like Hashr or Flashfy to flash recovery, both free from Play Store. I haven't tested the file but I recommend that you flash img only, double check the download procedure, there are many ads that lead to wrong downloaded files...

Stuck....TWPR works but ADB sideload does not. Phone has no OS.

I am stuck. I tried to update to OREO and the update wouldnt take. I kept saying that update is for "oneplus 3t" and you have " ". I wiped device and have been trying to get an OS back on my device. I tried using ADB with ADB sideload through TWRP and the Command Prompt but I get an error "you need adb 1.0.32 or newer to sideload to this. My ADB is version 1.1.3 and TWRP is 3.1.1-2
I dont know what else to do........

Try a slightly older version of ADB. Also make sure you kill the old adb.exe in taskmanager since it runs on the background.

Read the OP in the official Open Beta 16 forum. All answers are there.

zdaddi said:
I am stuck. I tried to update to OREO and the update wouldnt take. I kept saying that update is for "oneplus 3t" and you have " ". I wiped device and have been trying to get an OS back on my device. I tried using ADB with ADB sideload through TWRP and the Command Prompt but I get an error "you need adb 1.0.32 or newer to sideload to this. My ADB is version 1.1.3 and TWRP is 3.1.1-2
I dont know what else to do........
Click to expand...
Click to collapse
Did you follow all the steps correctly? I think this occurs when one doesn't flash the right firmware beforehand. I also believe that you require an oreo compatible recovery such as blu spark.
All the flashing instructions are in the 2nd post of this thread: https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240

Here is the Zip file containing edited xml files to stop unbrick tool to erase your internal data.
Link to edited script : https://drive.google.com/open?id=0Byn304jb_hlqZ29XM1oxUUZwbzg
(Personally I made , Tested and used these files and successfully recovered device without data loss)
Link to the unbrick tool download : https://mega.nz/#!Q1YnTTAT!gnLf6NEkSRy7W-WY8J0H2SmJJLzO91-vReKx7B1VVpI
Thread : https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306.
Steps to be followed :
1. Download the unbrick tool
2. Extract the Zip File.
3. Download my edited script zip file.
4. Extract the zip and copy and replace the extracted files in the unbrick tool.
5. Follow the steps in the unbrick thread .
Dont forget to hit Thanks Button ............
Sent from my OnePlus3T using XDA Labs

Push the ROM to your phone using the adb push command and flash from your phone

[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!