Database Develop

Android 4.2.1 (JOP40D) for Nexus 7

Android 4.2.1 (JOP40D) for Nexus 7 Wifi and 3G+
Manual Update Available [Updated]​
Install:
Those with a custom recovery can just download the zip below, move it to their device, and flash away. If you're running stock recovery, substituting only the zip file name in Step 2.
Just after users began reporting that your Google Nexus N7 device were receiving an update to Android 4.2 Jelly Bean (build JOP40C, to be precise), it looks like the manual update package is available for download. As could be expected, this coincides almost perfectly with the launch of Google's newest additions to the Nexus family – the Nexus 4 and 10.
For those ready to download and install manually, the process is easy. If you have a custom recovery, just download the zip (linked below), move it to your device, and flash as usual. Those with stock recovery should keep the file on their computer, and just follow a few easy instructions:
Disclaimer: I'm not responsible in case of brick of your device - proceed at your own risk.​
Step 1.
- Reboot your Google Nexus 7, holding the Volume Up and Volume Down buttons while it boots up. Once you see the fastboot menu and "Start," press Volume Up to navigate to "Recovery" and press the power button. Once you see an Android with a red exclamation point icon, press Volume Up and the Power button together, which will bring you to a new menu. Navigate to "apply update from adb."
Step 2.
- Connect your Google N7 to your computer with a USB cable.
- Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
- Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the JOP40C zip file you've downloaded.
Type in the following:
For the Nexus 7 "NAKASI"
Code:
adb sideload 659e6288b87d.signed_nakasi_JOP40D_from_JOP40C.659e6288.zip
For the Nexus7 3G+ "NAKASIG
Code:
adb sideload 65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update.
Step 3.
- Reboot and enjoy! You are now running Android 4.2.1 on your Nexus

I modified my OP and put online the updates for both versions of Nexus 7

Hello
The link for the wifi N7 is broken I think

My N7 is rooted, stock rom, cwm recovery, voodoo ota rootkeeper, supersu. I d/l the update from Droid Life and copied it from my computer to the N7 internal storage. Booted into cwm recovery, chose to install zip from sdcard, chose the d/l'd file from the /0 folder (filename 659e6288b....zip), chose to reboot system, answered 'Yes' to preventing flashing stock recovery, answered 'Yes' to keeping root. All is good. Still have root and cwm recovery.

Foggy79 said:
Hello
The link for the wifi N7 is broken I think
Click to expand...
Click to collapse
I have the same issue.
Sent from my Nexus 7 using xda app-developers app

Will this wipe my data, let me know so I can make a backup, thanks
Sent from my Nexus 7 using xda premium

OP Why you don't post oficial Google link directly from Google servers? Also here is a thread already http://forum.xda-developers.com/showthread.php?t=1745781 and in instruction its better to explain how to open cmd Window/cmd prompt in a folder "ctrl+right click" in an empty space where your zip is and (select open cmd here).
Sent from my SPH-D710 using Tapatalk 2

philos64 said:
Install:
Those with a custom recovery can just download the zip below, move it to their device, and flash away. If you're running stock recovery, substituting only the zip file name in Step 2.
Click to expand...
Click to collapse
Link is Broken above...... but I worked out it is here
http://www.androidfilehost.com/?fid=9390202682628636802
What do I need to do if I have custom recovery but am still on 4.1.2?
Thanks

Try to flash this with TWRP 2.3.2.1 but got error Status 7, same with CWM 6.0.1.0, tried to google what's going on but I can find none, can someone help me with this ?

mr_gem said:
Try to flash this with TWRP 2.3.2.1 but got error Status 7, same with CWM 6.0.1.0, tried to google what's going on but I can find none, can someone help me with this ?
Click to expand...
Click to collapse
I had this problem with the first 4.2 update and now the same again with 4.2.1.
Last time I had to put the bootloader back to stock (drastic) to get the update,.
sideload doesnt work either.
Motorola Atrix (AOKP JB)
Nexus 7 (Stock)
Past life:
HTC Desire HD reboot loop overheating.
Nokia N900 micro usb port loose.

Omar04 said:
OP Why you don't post oficial Google link directly from Google servers? Also here is a thread already http://forum.xda-developers.com/showthread.php?t=1745781
Click to expand...
Click to collapse
Because it's my choice, and if you don't use it, don't use it :silly:
and if you read this thread, have you got some instructions for install it? NO
Have you find one link from Google servers ? Not yet - at 03.15 PM - 29 Nov 2012
Omar04 said:
and in instruction its better to explain how to open cmd Window/cmd prompt in a folder "ctrl+right click" in an empty space
Click to expand...
Click to collapse
I surprised that you don't know how to use the command lines,
And if you think about the new users , they can read a lot of guide which explain how use the command lines. It's one of the basic of installations under Android
and it's not the usefulness of this post !!!
Omar04 said:
where your zip is and (select open cmd here).
Click to expand...
Click to collapse
And if you click to "DOWNLOAD LINK" you will see that you can download the files
With a lot of pleasure

The download link for the Nexus 7 wifi aka "NAKASI" is repaired

Downloaded update from official Google link, flashed in CWM Recovery, kept bootloader, kept root. All is well.

Help Help PLEASE
OK I did everything and the update worked for JOP40C. I`m running stock so no rooting.
Then I wanted to upgrade to JOP40D.
I got to just after the little green android with the exclamation mark on it. I then held the Power button and the Up button. Instead of getting the next menu it just died on me. :crying:
So what now?

I went through this project step by step and was just about to flash manually when the OTA symbol magically appeared in my bar.
Oh well... I guess I'll take the easy way this time.

St1ck33 said:
Downloaded update from official Google link, flashed in CWM Recovery, kept bootloader, kept root. All is well.
Click to expand...
Click to collapse
Sounds good for you :good:
AfrikaansAndroid said:
OK I did everything and the update worked for JOP40C. I`m running stock so no rooting.
Then I wanted to upgrade to JOP40D.
I got to just after the little green android with the exclamation mark on it. I then held the Power button and the Up button. Instead of getting the next menu it just died on me. :crying:
So what now?
Click to expand...
Click to collapse
- If you're running stock recovery, substituting only the zip file name in Step 2.
Step 2.
- Connect your Google N7 to your computer with a USB cable.
- Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
- Open up a command prompt (cmd in Windows, regular shell in Linux and Mac) in the same directory as the JOP40C zip file you've downloaded.
type this line command for N7 3G:
Code:
adb sideload 65880f56b1c0.signed-nakasig-JOP40D-from-JOP40C.65880f56.zip
for N7 wifi only go to OP..
You should see a progress bar, which will eventually hit 100%. At this point, your device is installing the update
and reboot for finish
PMOttawa said:
I went through this project step by step and was just about to flash manually when the OTA symbol magically appeared in my bar.
Oh well... I guess I'll take the easy way this time.
Click to expand...
Click to collapse
Use the update by OTA...let's go

Running 4.2, rooted, CWM latest recovery (forget version). I had previously done the clear data from one of the Google apps and succesfully got my 4.2 from 4.1.2 OTA - CWM handled it just fine. I didn't want to take any chances doing that again, I downloaded this file, flashed in CWM, rebooted and all seems fine. Still have root, still have swype, still have cerberus.
Thanks OP!
Edit: Due to the new /0/ emulated sdcard for multiple users, I copied the zip file to my sdcard through windows - but CWM couldn't see it. I had to navigate to /0/ and then CWM could see it. Just a heads up.

Thread will be closed
Code:
[B][COLOR="Red"][CENTER][SIZE="4"]This thread will be closed very shortly because it's now useless.
"Developers Google"website has released updates ;)
I will deleted all download links.[/SIZE][/CENTER][/COLOR][/B]

philos64 said:
Code:
[B][COLOR="Red"][CENTER][SIZE="4"]This thread will be closed very shortly because it's now useless.
"Developers Google"website has released updates ;)
I will deleted all download links.[/SIZE][/CENTER][/COLOR][/B]
Click to expand...
Click to collapse
Edit: NM there's a thread linking to all OTA updates. you can delete this post.

Sorry, but your post is useless too
I have contacted Mods for close this thread

[GUIDE] How to update to Android M-Preview-2 from V1 without loosing your data

If you are in M-preview-1 and don't want to lose your dat/apps you can follow this guide, after that, you'll havw M-preview-2 installed and a rooted device.
Firstly, you need to have a pc with adb working. There are several wyas to achive that, but I presume that if you are already in M preview V1, you have it.
Then, you need to have an unlocked bootloader, again I assume that you have it.
======Skip this is you have adb and unlocker bootloader===========
In any case, in linux there is a very trivial way to get both things (probably in windows and mac is more or less the same):
In a terminal:
sudo apt-get install android-tools*
Then plug your N5 to your computer with a usb cable (depuration mode enable), check that everything is working fine:
sudo adb devices
Then;
sudo adb reboot bootloader
sudo fastboot oem unlock
Then reboot
========================================================
Again, if you are not coming from M-preview-1 I do not recommend this method
1. Download M-preview-2 from this page.
2. Download twrp from here.
3. Create a folder, move twrp to that folder and extract M-preview-2 to the same folder (no sudir, all the files in the same folder), extract again image-hammerhead-MPZ79M.zip in the same folder.
4. Download Despair kernel in your device.
5. Download SuperSU beta 2.49 in your device.
Now, we are ready to flash everything:
6. Open a terminal and cd to the folder where you keep everything from previous steps.
7. Plug your device using a usb cable
8. Type the following commands in the terminal (if you are not in Linux, use the same commands but without "sudo"):
sudo device (just to check that adb ·see your device)
sudo adb reboot bootloader
sudo fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
sudo fastboot flash boot boot.img
sudo fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
sudo fastboot flash system system.img (this step takes a while)
sudo fastboot flash cache cache.img
sudo fastboot flash recovery twrp-2.8.7.1-hammerhead.img
9. Reboot in recovery (just using the vol up or down and the on buttom).
10. Flash Despair kernel
11. Flash SuperSU
12 Wipe Dalvik and cahe (just in case)
13. Reboot

Flashing over preview 1 won't bring additional issues?

migueldbr said:
Flashing over preview 1 won't bring additional issues?
Click to expand...
Click to collapse
Of course II'm still testing, but it seems that there is not new bugs (yet).

All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.

does your guys system app crash if you open data usage (set language to something except english) ?

tugler said:
does your guys system app crash if you open data usage (set language to something except english) ?
Click to expand...
Click to collapse
Yes

I just did a clean flash via fastboot manually. Booting now. I ain't got time for issues.

Is there a reason the OP links to TWRP 2.8.6.1 instead of the latest version (2.8.7.1)?

Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?

6spdsc4 said:
Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?
Click to expand...
Click to collapse
I'm still transferring my nandroid backup to my PC and haven't tried yet, but it's possible that the kernel won't flash on preview 2 because it's not yet updated for preview 2. As @TonyHoyle said, it's probably not a great idea to use one until they've specifically been updated for preview 2.

TonyHoyle said:
All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.
Click to expand...
Click to collapse
can u explain more detailed?

Flashable zip for multirom
flashable zip to use with multirom, please ?

As TonyHole suggested, just remove the -w; basically this will do: (you can do below on a command line as long as you are in the extracted TGZ file and in the hammerhead-MPZ79M folder/directory)
fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
fastboot reboot-bootloader
fastboot update image-hammerhead-MPZ79M.zip
This works for me no issues as data is left intact but everything else is updated ; suggesting NOT to do this from an Android L to Android M Preview 2 and do a proper wipe
This will rebuild the ART app optimize on reboot
OP: Next time make a guide for doing STOCK update FIRST ; save the kernel and root for a SEPERATE post or a seperate section in the post

Hellscore kernel works great
Clean flash
I don't understand why any one would do a dirty dirty install with a preview no less
Sent from my Nexus 5 xda-dev app

The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.

NPS_CA said:
The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.
Click to expand...
Click to collapse
Do you have a link?
Sent from my Nexus 5

Is there zip file available
Sent from my Nexus 5 using XDA Premium 4 mobile app

thesebastian said:
Do you have a link?
Sent from my Nexus 5
Click to expand...
Click to collapse
Is this a real question?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Is this a real question?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5

thesebastian said:
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5
Click to expand...
Click to collapse
Surely if you go about phone. System update. Then you'll either have it or not if it's been pushed out to your device?
Sent from my Nexus 5 using Tapatalk

*UNTESTED* OE2 to OI2 While Keeping Root

I pulled this from my phone when it was released yesterday. I'm in OE2 rooted, so this file is from OE2 to OI2
THIS IS NOT AN ODIN FILE!
Build is G925AUCU3BOI2
http://www.mediafire.com/?xksb71307dofox8
designgears said:
*** UNCONFIRMED *** This hasn't been tested.
This is for upgrading from G925AUCU1AOE2 to G925AUCU3BOI2 while retaining root.
Flash with FlashFire
2400258_s6_edge.zip
https://mega.nz/#!S1BnHSSJ!emk9y52XQIaVE0KFyRBwzYmXav0MByBOPtVeZwRCUmw
Flash With Odin
boot.tar.md5
https://mega.nz/#!T05xiaDR!3SVrDVONPGfRU898PSwQ52e631ubArsSNKV4mHPqMXM
modem.tar.md5
https://mega.nz/#!D8gxkA6J!riyZ69REc0DoSBO0O43Ykfa4sI9Pl5gRVSljWTqS2lc
-----------------------------------
In Flashfire select "Flash ZIP or OTA"
Select 2400258_s6_edge.zip from your sdcard
Leave all of the settings default and flash.
After it has flashed, reboot to download mode and use Odin to flash the updated kernel and modem.
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Once the phone has rebooted you should be on G925AUCU3BOI2.
Click to expand...
Click to collapse

how to use this..i am in stock 5.0.2

Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
Did you retain root?

Yes. I was prepared to lose it imo, but still have it so that's kind off weird. But I won't be complaining. Now I'll wait for deodoexed rom then I can go xposed with flashfire..

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
Can you please post pic to confirm you have root still on 5.1.1 and please provide instructions on how you sideloaded this with adb?

I unlocked my phone and i still didn't get the update yet is that a problem?

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
How did you do this? I get a DM-Verification error in recovery.

Please help me:
when i'm in recovery 3e and choice apply update from adb but he said Update from ADB is disabled
then i choice apply update from external storage but not ok. 'apply update from external storage is diabled'
Someone know please help me. Thank a lot!

tronghienk32 said:
Please help me:
when i'm in recovery 3e and choice apply update from adb but he said Update from ADB is disabled
then i choice apply update from external storage but not ok. 'apply update from external storage is diabled'
Someone know please help me. Thank a lot!
Click to expand...
Click to collapse
Same errors I'm getting. That's why I'm waiting for a response on how he got it to work.

teamfresno said:
Same errors I'm getting. That's why I'm waiting for a response on how he got it to work.
Click to expand...
Click to collapse
Did you sideload it from your storage or your computer? From previous phones, I know it has to be sideloaded from a computer.

Rodman101 said:
Did you sideload it from your storage or your computer? From previous phones, I know it has to be sideloaded from a computer.
Click to expand...
Click to collapse
The computer. I put the phone into recovery mode, then I scroll down to install from ADB, but I always get an "ADB is disabled". I thought you have to get into there and then ADB sideload xxxx.cfg from the command prompt.
Am I doing it wrong?

Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum

krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
It worked and you remained rooted?

krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
Like others are saying, everyone gets ADB is disabled message when they select apply update. What did you do for that?

srideep said:
Like others are saying, everyone gets ADB is disabled message when they select apply update. What did you do for that?
Click to expand...
Click to collapse
same problem!

krolla03 said:
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked.
This taken from the S4 forum
Click to expand...
Click to collapse
AT&T? Seems like you have a custom recovery. We don't have "ADB sideload", it comes up as "install from ADB".

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
He couldn't have been rooted because the OTA has build in checks.
Designgears created a flashfire zip that updates from OE2 to OF3 while maintaining the OE2 Recovery and Bootloader. I have been trying to mimic his form, but I haven't been able to take the .p files and work with them.
Here're the threads if anyone is knowledgeable enough to work with these things or can get a hold of him or Wesgarner who created a similar zip between OF3 and OF4
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135

Rodman101 said:
He couldn't have been rooted because the OTA has build in checks.
Designgears created a flashfire zip that updates from OE2 to OF3 while maintaining the OE2 Recovery and Bootloader. I have been trying to mimic his form, but I haven't been able to take the .p files and work with them.
Here're the threads if anyone is knowledgeable enough to work with these things or can get a hold of him or Wesgarner who created a similar zip between OF3 and OF4
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135
Click to expand...
Click to collapse
Well here is a zip like the ones you linked to. I can't test it but I tried to make as safe as possible. removed all checks so it won't fail. I don't let it patch boot.img sboot.bin, etc. Idea is that IF something does mess up you should be able to odin back to OE2. outside of that, this *should* take you from G925AUCU1AOE2 to G925AUCU3BOI2. If anyone wants to give it go: 2400258.zip

Krestic said:
Thank you!
Downloaded this, then sideloaded it with ADB Sideload while having OE2. Worked perfectly!
Click to expand...
Click to collapse
mrRobinson said:
Well here is a zip like the ones you linked to. I can't test it but I tried to make as safe as possible. removed all checks so it won't fail. I don't let it patch boot.img sboot.bin, etc. Idea is that IF something does mess up you should be able to odin back to OE2. outside of that, this *should* take you from G925AUCU1AOE2 to G925AUCU3BOI2. If anyone wants to give it go: 2400258.zip
Click to expand...
Click to collapse
ADB sideload right?

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!