Database Users

[HOW-TO] Return to Factory Stock using fastboot commands

DISCLAIMER: I am not responsible for what you do to your tablet. I've done these steps dozens of times without issue on Windows and Linux. PLEASE READ THIS ENTIRE THREAD FIRST TO UNDERSTAND IT BEFORE ACTUALLY PERFORMING THEM ON YOUR DEVICE!!!
This is done using the Android SDK, the command incorporated in that called fastboot. No toolkit, I don't do them, never have, so I cannot support anyone trying anything from a toolkit. Doing this process will take you from start to finish no more than two minutes.
I haven't seen a "How-To" on returning to 100% out-of-the-box stock using fastboot commands and Google's factory N7 2013 images. If I've overlooked this, I apologize in advance. I've seen a lot of people asking how to do this in the forums, so I thought this may help.
This will work on Linux or Windows. I use Windows 7 x64 for work, Linux Mint 15 x64 otherwise. With Linux you will need to add permissions for the USB device in /etc/udev/rules.d. I had to do this on my Linux Mint 15 x64 laptop, you may not. If you get an error stating something to the effect of "insufficient permissions...", you'll want to Google "android udev rules setup". I won't cover that here.
This guide should work for the LTE N7 2013, but I don't have one to test.
Before we begin, back up anything on your internal /sdcard partition you want saved. This will 100% wipe your device to what it was when you first unboxed it. I warned you. You'll be erasing everything, and it will be reloaded. Stock Android recovery will be loaded, and you will not be rooted.
What you'll need:
Android SDK - specifically fastboot working
Google factory images from here.
Unlocked Nexus 7 tablet
Here we go (this will be based off of the N7 2013 Wifi-only device, JSS15R image):
1. Extract from the compressed image from the .tgz/.tar, you'll want to extract the folder called razor-jss15r. Extract this folder to your SDK/platform-tools location. My SDK is on my C:\, so my path to it on Windows is C:\sdk\platform-tools. Linux it would be at /home/ryan/sdk/platform-tools. Once extracted, you should have a folder called: razor-jss15r. There should be 5 files in there, 1 is a zipped folder called image-razor-jss15r.zip. DON'T UNZIP IT!
2. Open command prompt, and change directories to your SDK/platform-tools location. Boot your tablet to the bootloader, and plug it into your computer. We're ready to issue commands now.
3. After each command, hit Enter. I'm not going to state that to make sure people don't get confused. Each line is it's own command. I recommend copy then pasting each command below, one by one, into the command prompt window.
Code:
fastboot erase boot
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot erase system
Code:
fastboot erase userdata
Code:
fastboot flash bootloader razor-krt16o/bootloader-flo-flo-03.14.img
Code:
fastboot reboot-bootloader
Code:
fastboot -w update razor-krt16o/image-razor-krt16o.zip
NOTE: You can remove the -w in the above to prevent internal sdcard from getting wiped.
After the last command, the tablet will automatically reboot itself.
Go through setup, hook up the device to your computer and copy anything you'd like on your device, I recommend a SuperSU flashable zip if you want to root. Download a custom recovery image, and place it into your SDK\platform-tools folder. You can then boot back into the bootloader and flash the custom recovery of your choice (fastboot flash recovery recoveryfilename.img). At that point you can reboot into that custom recovery, and flash the SuperSU zip to have root. Reboot. Done.
Some of the commands may take up to 30 seconds or so, just let them run. The ones that will take that time are erasing system and userdata, and the last command will take time.
OPTIONAL:
If you want to re-lock your bootloader, which is usually ONLY done if you are returning for warranty purposes (and WILL erase your internal sdcard!), boot back to the bootloader and run:
Code:
fastboot oem lock

RMarkwald said:
Code:
fastboot -w update razor-jss15r/image-razor-jss15r.zip
Click to expand...
Click to collapse
If you omit the -w from this step, doesn't it leave your sdcard intact?

Possibly I don't actually know as I've never run it without the -w.
- Sent from my Galaxy S3

meekrawb said:
If you omit the -w from this step, doesn't it leave your sdcard intact?
Click to expand...
Click to collapse
Yes, that is correct.

Updated for Android 4.4 krt16o images.

[GUIDE]Nexus 9 back to stock guide - Unbrick - Restore factory firmware

The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition

Great. Is it possible to make a batch file to run all the commands at once?

albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.

i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?

Cool, thanks for the information.

Thanks for creating this! Will come in handy. Saving this for later

This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.

scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app

remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1

cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.

cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.

doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.

I also used Linux but I executed the commands individually rather than using the script. It worked.

remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s

nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.

These instructions also worked with 5.1.1

im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode

maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?

Using System Image to Update your Nexus 6 (no data loss)

Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
NOTE: You must have your bootloader unlocked. If you've never unlocked your bootloader, I don't think there's any way to do this without wiping your data.
STEP 1: Install fastboot
Fastboot is Google's utility for flashing factory images. You can also use it to flash custom recoveries like TWRP and CWM. The standard way to get is is through Google's Android SDK, but that's a bit heavy-duty, so you can also download just the most important tools (fastboot and adb) separately, packaged by users. Here are some links:
Official Google Android SDK (cross-platform): http://developer.android.com/sdk/index.html#Other[1]
Unofficial for Windows: http://developer.android.com/sdk/index.html#Other[2]
Unofficial Mac/Linux: http://code.google.com/p/adb-fastboot-install/[3]
Windows users might also need to install drivers: http://developer.android.com/sdk/win-usb.html[4] (can any Windows users confirm whether it's necessary?)
STEP 2: Prepare factory image
Download the latest Nexus 6 factory image at https://developers.google.com/android/nexus/images#shamu[5]
Unzip it and open the resulting folder
Unzip the "image-shamu-*.zip" file in there
You should now be looking at something like this: http://i.imgur.com/mzrfwrP.png [6]
STEP 3: Flash! (Ah-ahhhhh! [7] )
Connect your phone to your computer via USB, and enter the bootloader. You can enter the bootloader by holding down the power and volume-down buttons to boot. Once you see the bootloader, you can release the buttons.
Open a terminal/command prompt. The syntax might be slightly different on Windows than on Mac or Linux, but basically the same. Anything you see in <> you need to replace, e.g. with the actual path to your factory image folder. The rest you should be able to copy and paste. (Tip: you can easily enter a folder path into your terminal/command prompt by simply dragging the folder onto your terminal window. This works on Mac, Windows, and the vast majority of Linux GUIs.) Enter these commands:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Reboot the bootloader.
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
cd <image-shamu-lmy47d>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
If you DO NOT use a custom recovery (like TWRP or CWM), then also: fastboot flash recovery recovery.img
Don't worry if you see messages like "target reported max download size of 1073741824 bytes". Just wait and let it finish.
Reboot your phone and enjoy. It's normal for the first boot to take a while. Going from Kitkat to Lollipop took about 20 minutes. Going from 5.0 to 5.0.1 took 5-10, I think. YMMV.
A WORD OF WARNING: If you're moving between ROMs, you generally should do a complete reset, including wiping data. Many users have reported problems going from KitKat to Lollipop without wiping data and recommend a factory reset anyway. If you're okay with wiping everything, you can simply use Google's included flash-all scripts, or flash the userdata.img file yourself. Personally, I'm not going to bother wiping adta for an incremental update like 5.0.1->5.1. As always, be sure to back up your data!
Shamelessly stolen from: http://www.reddit.com/r/Nexus5/comments/2phqy7/howto_upgrade_android_using_nexus_factory_images/

Shouldn't you also fastboot reboot bootloader after radio flash?

This is the scenic route.

I tried to update using wugz, without unlocking the bootloader. failed. Oh well, I'll wait to receive ota
Unless this method doesnt require unlocking?

If you have an OTA zip file, this is different than using a System Img?
I do not think you need to lose data or unlock your bootloader?
Found a link for the OTA zip file.
If I remember right you can copy the zip to you phone with a USB cable.
Go into the bootloader, Volume Down and Power.
Select the zip.
I did not think you needed a terminal and all the commands if you had the OTA zip on your phones SD card.
Am I wrong does something like this not work?
or
I can just wait.....

This worked great.
I was unbranded with VZ sim, unlocked, rooted with TWRP recovery. Didn't want to lose all that nor my apps or data. This method upgrades to 5.1 without any loss.
When I was done with the flashing, I rebooted to TWRP recovery (not system) in order to wipe dalvik and cache (just to be certain). I wiped and then rebooted to system. TWRP noticed I didn't have SuperSU installed so it installed it for me. Meaning, once I got my system rebooted, I still had root too.
All in all, this process worked great for me. Thanks.

I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
---------- Post added 14th March 2015 at 12:17 AM ---------- Previous post was 13th March 2015 at 11:53 PM ----------
Nikos2k said:
I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
Click to expand...
Click to collapse
This is the message after the radio flash command:
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.697s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing modem ...**☺
FAILED (unknown status code)
finished. total time: 3.721s​
Why the failed message?

I'm decrypted. Will this re encrypt my Nexus or do I have to flash a non enforce img?

Thank you, this really helped.
Since my bootloader was locked i had to unlock it as well.
Had a bit of a scare with the whole erasing screen staying on for too long.
Went back and redid the process, and went downstairs for 5 minutes, came back and phone was booted.
Anyway, thank you again

Will this work on an encrypted phone?

mikeadamz said:
Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
<<snip>>
Click to expand...
Click to collapse
I don't suggest that anyone read and follow someone else's instructions when doing something like this. Not because the instructions are wrong or anything, but because blindly following instructions doesn't involve *understanding* anything.
So rather than reading and following instructions, read and UNDERSTAND the process of installing factory images as delivered with the factory images (flash-all.sh). If you UNDERSTAND the process and what everything does, then (a) you *already know* what needs to be adjusted to do what you want, and (b) if something starts going wrong in the middle of it, you will understand why, and what to do to correct it.

mikeadamz said:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Click to expand...
Click to collapse
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick

Nick D said:
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick
Click to expand...
Click to collapse
Install this:
http://forum.xda-developers.com/showthread.php?t=2588979
Now ADB and fastboot are installed system wide. Put your files anywhere, I use the desktop. Hold shift and right click on wherever your files are and select "open command prompt here" and flash away. Simplified, no more dragging and dropping.

Will try with the new update (5.1.1 (LMY48M)) to ensure it works. Thanks!

[/COLOR]
handyarrow said:
Will this work on an encrypted phone?
Click to expand...
Click to collapse
Have been flashing this zip in twrp after the fastboot stage without an issue for the last few updates - http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788

Flashed LMY48M with fastboot method and it works great.
My phone is encrypted.

Root & TWRP!

Note: I am no expert at this. I used this to get TWRP and root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download Magisk's installer zip on your phone from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (Google Pay only works with Magisk v19.0+)
Download arter97's kernel .img to your PC. This kernel currently is the only reliable way to get TWRP. https://forum.xda-developers.com/razer-phone-2/development/arter97-kernel-razer-phone-2-t3914996
Reboot your phone into bootloader mode (Turn off then back on while holding vol down).
Make sure your phone is recognized by Windows before proceeding. Follow this guide to setup the proper drivers and fastboot.
Flash arter97's kernel by running
Code:
fastboot flash boot arter97-kernel-*.img
If you run into any issues, then you will probably need to specify the slot to flash. Reboot back into your system.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a arter97-kernel-*.img
if _b use
Code:
fastboot flash boot_b arter97-kernel-*.img
Reboot to recovery (either through bootloader mode or hold vol up while rebooting).
Install the Magisk .zip from TWRP.
Be amazed by the possibilities.
Old instructions (Should always work to get root):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer when in bootloader mode so I had to install the Google adb drivers and manually set the driver used to Google Bootloader Interface (or something like that)

I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.

figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3

Twiggy000b said:
figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3
Click to expand...
Click to collapse
I know the feeling, my last device was the Nexus 5

my last "decent" device was the essential phone. then i went to the xperia xa2 ultra, then the iphone 6 then.... zte quest. -.-

CurtisMJ said:
I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.
Click to expand...
Click to collapse
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot

CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down and run `fastboot flash boot patched_boot.img`.
Reboot, and open up magisk manager to confirm everything is working.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?

CalebQ42 said:
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot
Click to expand...
Click to collapse
Interesting. The bootloader isn't exactly what I'd call a masterpiece of coding (weird cause I still maintain the ROM is excellent) so it might have just been a momentary glitch.
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
ctakah27 said:
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?
Click to expand...
Click to collapse
Yes, yes and not really (you get a file chooser so you just need to locate it)

I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!

CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
Good luck it's a easier process compare to years ago. I would do it but I have no need for root or custom recovery. If you fail on the TWRP I will do it in time for people.

Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.

CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
jonchance_84 said:
Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.
Click to expand...
Click to collapse
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE

Warrior1988 said:
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE
Click to expand...
Click to collapse
I see the separate firmware. I'm only asking because of past shadyness from AT&T trying to tell manufacturers what to do. Years ago on my Xperia x10, if on AT&T firmware, you needed to flash the global generic firmware to get around their crap.

CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Would this procedure be the same as far as mac/win?

I understand all of that, I am simply asking if someone has tried this with the AT&T variant yet. I want to know before I go order this phone.

I love a rooted phone, but as far as I know, if you unlock the bootloader, Netflix will no longer work in HD mode. To me, this is a deal-breaker. If anyone knows about a work-around, I'd love to know.

Razer phone 2 root
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen

andy1011 said:
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen
Click to expand...
Click to collapse
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next

CurtisMJ said:
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next
Click to expand...
Click to collapse
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.

andy1011 said:
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.
Click to expand...
Click to collapse
Adb and fastboot are separate things. You should only need download mode and fastboot. What are you trying to use ADB for? If in doubt, the guide on Razer's website should be quite sufficient
EDIT: You can get to download mode by holding Vol Down and Power Button while the device is off. You can force reboot by holding down power for approx 15s as well

MSM and "the current image have been destroyed and can not boot"

Hey,
so yesterday I tried to install TWRP recovery.
While trying I assume that I hard bricked the phone and got the message that the current image has been destroyed and cant boot.
I've tried using MSM but the device wasnt recognized, I installed the qualcomm usb drivers and it worked for some time but still wasnt recognized in MSM.
Now I have the problem that when I plug it in, it only shows the above mentiond message. When I shut it off and press vol +/- it then goes into fastboot but cycles through it and is still only shown as android device in the device manager.
I'm using the usb 2.0 and original OP cable. Build number was IN2023...c.36, A12 and OOS12
ADB does not work, fastboot commands still work while it is in the fastboot cycle.
Does someone have any solutions for that?
Thanks

How did you "install" twrp?
via fastboot? or through booted twrp? Because from what i read, twrp or orangefox likes to patch boot image instead of flashing recovery partition.
So my suggestion is to flash via fastboot original boot.img and recovery.img

I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had

w4rdl0rd said:
I watched a tutorial for that. I tried to get it running through fastboot but as I mentioned it didnt work out that well.
Do you know where I can get the original boot.img and recovery.img? I found other versions but not the one that I had
Click to expand...
Click to collapse
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask

Thank you, it finally works

ShadoV90 said:
You need to download EU OOS12 C36 FULL Package (i found it in this forum here), extract it via payload dumper and after that you will have every .img which is used to flash. Then you will need to go to folder where you have fastboot.exe, click shift+right mouse button and click open command prompt here.
Next: fastboot commands.
First (it's optional, but you will know that your device is "connected" via fastboot)
fastboot devices
you should have output, and if it's that then:
fastboot flash boot <drag boot.img file>
by dragging file, system automatically fill location of this boot file, next
fastboot flash recovery <drag recovery.img file>
and then
fastboot reboot
If you have questions, then ask
Click to expand...
Click to collapse
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for

w4rdl0rd said:
I'm now somehow stuck in recovery. So after I select the language I get the message "system error, after select language, please select Online update". When I try to format data I'm getting back to recovery. Maybe you can tell me how to proceed since I don't really know what to search for
Click to expand...
Click to collapse
Wait... system can't boot up?

ShadoV90 said:
Wait... system can't boot up?
Click to expand...
Click to collapse
yeah, it goes always back to recovery

Hmm... Then i'm afraid that MSM is now your only option. Sincerely, i never used that, so i found thread with guide how to do it.
Look please here, read carefully, and i hope you will be able to recovery your device.
I guess it will rollback your system to OOS11.
PS. Give feedback if it was succesfull (or not).

Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work

w4rdl0rd said:
Right now I tried to do again the steps you mentioned. When I dragged the boot file into command prompt I got the message that the .img file is damaged. Maybe that is the reason for not booting up. When I first did it I also received the message but after dragging it a second time over it was still installed.
I also tried downloading the firmware from the op website, extracting everything via the payload dumper and installing everything as you mentioned. Like that I was stuck in fastboot.
Thanks for your help, maybe it will work
Click to expand...
Click to collapse
I hope it will work.
BTW, next time when you will try recovery like twrp or orangefox, don't flash it but boot it via fastboot.
fastboot boot <drag file of twrp/orangefox>
If it will work, and everything will work, then use fastboot flash recovery <drag file of twrp/orangefox>
Don't flash it via twrp/orangefox, because like i said, it will probably try to patch boot partition and in result boot will be unusable.

thanks for the advice, I'll try it next time or when I get it running again

w4rdl0rd said:
thanks for the advice, I'll try it next time or when I get it running again
Click to expand...
Click to collapse
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD

ShadoV90 said:
I have one more idea. I thought about changing active slots in fastboot. Normally on inactive slot is fully working rom before update to c36. With proper boot etc. So when you change active slot, you should have fully working ROM. Problem is that you must figure out which slot is your active now.
Normally this command is fastboot getvar all and it should show you wall of text and information (bootloader) current_slot: a (or b)
then you can switch active slots (if you see other slot is bootable).
There are two methods:
1. Checking active slots and if current active slot is A then in fastboot type this
fastboot set_active b otherwise fastboot set_active a
2. Idk if it will work here, but there is a command fastboot set_active other which just switch active slot no matter what it was earlier.
But sincerely idk what will happen if you will switch to unpopulated slot. I think if you upgrade your phone normally or didn't erase this inactive slot, it should be populated with previous version of ROM.
When i installed OOS12 and due to destroying my boot image i switched slots i was able to run A11 xD
Click to expand...
Click to collapse
I tried/am trying to get MSM working. It connected now in edl, in MSM it still freezes. No matter what I do it has the status "waiting for communication".
If I remember correctly then there was somethin with ..._b. But since I've closed the command prompt I can't look it up anymore.
I'll try to change slots and let you know if there will be a result.

With MSM there is one problem. After succesful operation your phone will be locked. I mean bootloader will be locked.

I did as you wrote...it works fine now. I think. There is still A12 and OOS12 installed but it is lagging a bit.
I attached a screenshot of the terminal with the slots. Does having switched them pose some problem? Do I have to switch them back?

Just check if you have an update. If you have, then install it via system update. For now, you have working system. Now you have much more possibilities to use. Like if you don't have update you can apply manually one which you downloaded. In system ofc.

There are no updates, there is the most recent version installed.
Thank you for the help in solving it

w4rdl0rd said:
There are no updates, there is the most recent version installed.
Thank you for the help in solving it
Click to expand...
Click to collapse
So, this is C36 installed?

yeah there is c36 installed