Database Users

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

Unbrick/Restore Amazon Fire (7in 2015 5th Gen) using Stock Recovery's ADB Sideload

for Fire 7in 2015 5th Gen Only ( KFFOWI/Ford)
Downgrading Options
If flashing Stock over a custom rom
5.3.1.0 is the safest rootable version, if original firmware is unknown. -25 Oct 2018
Fire OS 5.3.1.0 was the last rootable version for all Fires,
except the HD 10.
Do not attempt to downgrade. 24 Oct 2018
5.3.2.1 cannot be rooted, nor downgraded -28 Dec 2016
5.3.2 can not be rooted, but can be downgraded to 5.3.1.0 - 28 Dec 2016
5.3.1.0 cannot be downgraded, trying will brick - 19 Jul 2016
System version 5.1.4, 5.1.3 & 5.1.2.1 can be downgraded to 5.1.2 - 5 June 2016
System version 5.1.4, 5.1.3, 5.1.2.1, and 5.1.2 cannot be downgraded to 5.1.1 or lower
System Version 5.1.X cannot be downgraded to 5.0.X
Download Firmware
Fire (5th Generation) Software
Note:This Can be done with PC/Mac/Linux but I'm just including PC instructions for now.
Watch
[Video]How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet
Mac
How to Downgrade the Firmware on the Amazon Fire 5th gen from 5.3.2 to 5.3.1 using Mac OS
https://youtu.be/iv0VcNM8IAw
PC Steps
Install ADB Drivers and verify they are installed correctly
Setup ADB
Download the Amazon Fire Firmware and place it with your ADB.exe files
Verify that Firmware file is correct version, size, and best to check the MD5 or SHA-1 checksum
Boot into recovery: Hold Volume Down button & Power button at the same time (If it boots to Fastboot mode, use the other Volume button)
Connect to PC via usb cable
Select Sideload in recovery
Recheck Device Manager (PC)
Send adb code (change to filename of firmware)
Code:
adb sideload filename
Its going take 5- 10 minutes so be patient
Once the recovery options come back up, wipe data and cache.
Select Reboot
Reboot is going to take few minutes BE PATIENT!!

Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
A000XXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522054520.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)

saved

how can i get to recovery mode on 5.1.1 ?? i cannot see recovery mode when i hold power and volume up button it just says amazon and reboots again.

fastcar22 said:
how can i get to recovery mode on 5.1.1 ?? i cannot see recovery mode when i hold power and volume up button it just says amazon and reboots again.
Click to expand...
Click to collapse
That has been an issue with 5.1.1 after trying to flash a Rom with FlashFire.
Is rom booting?
Sent from my XT1060 using Tapatalk

sd_shadow said:
That has been an issue with 5.1.1 after trying to flash a Rom with FlashFire.
Is rom booting?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
nope got stuck in cyanogen icon mode. thats why ia m trying to recover to factory flash

fastcar22 said:
nope got stuck in cyanogen icon mode. thats why ia m trying to recover to factory flash
Click to expand...
Click to collapse
could try wiping cache and or data in fastboot mode
not sure that is even possible, but worth trying
need to setup adb/fastboot then
fastboot wipe cache command
Sent from my XT1060 using Tapatalk

sd_shadow said:
could try wiping cache and or data in fastboot mode
not sure that is even possible, but worth trying
need to setup adb/fastboot then
fastboot wipe cache command
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Can you give me the fastboot commands? i can get to fastbootcommand prompt to do this?
i even tried the "fastboot install filename.zip" it says it could not find the android-info.txt in the zip file.
Thanks

fastcar22 said:
Can you give me the fastboot commands? i can get to fastbootcommand prompt to do this?
i even tried the "fastboot install filename.zip" it says it could not find the android-info.txt in the zip file.
Thanks
Click to expand...
Click to collapse
Code:
fastboot erase data
fastboot erase cache
Sent from my XT1060 using Tapatalk

sd_shadow said:
Code:
fastboot erase data
fastboot erase cache
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
it does not recognize data in the command i get this message
erasing 'data'...
FAILED (remote: unknown command)
finished. total time: 0.000s

fastcar22 said:
it does not recognize data in the command i get this message
erasing 'data'...
FAILED (remote: unknown command)
finished. total time: 0.000s
Click to expand...
Click to collapse
i was afraid of that, I do not have any ideas how to fix.
could try flashing stock boot.img, then return to Amazon
Sent from my XT1060 using Tapatalk

sd_shadow said:
i was afraid of that, I do not have any ideas how to fix.
could try flashing stock boot.img, then return to Amazon
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
i even tried that it says flashing not allowed
target reported max download size of 134217728 bytes
sending 'boot' (4348 KB)...
OKAY [ 0.140s]
writing 'boot'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.156s
is there anythign else in fastboot commands to delete the files?
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
can you tell me how to get to adb mode using volume up and power button, some are sayiing that it does not show recovery command but remove finger from power button when u see logo and side load?

fastcar22 said:
i even tried that it says flashing not allowed
target reported max download size of 134217728 bytes
sending 'boot' (4348 KB)...
OKAY [ 0.140s]
writing 'boot'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.156s
is there anythign else in fastboot commands to delete the files?
---------- Post added at 04:53 PM ---------- Previous post was at 04:52 PM ----------
can you tell me how to get to adb mode using volume up and power button, some are sayiing that it does not show recovery command but remove finger from power button when u see logo and side load?
Click to expand...
Click to collapse
there is no button combination, for adb
but it is not possible that adb is available during part of the boot, unlikely though
Power off then power on
try
Code:
adb reboot recovery
Sent from my KFFOWI using Tapatalk

sd_shadow said:
there is no button combination, for adb
but it is not possible that adb is available during part of the boot, unlikely though
Power off then power on
try
Code:
adb reboot recovery
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
i am sorry i meant to ask a different question, is there a way to get to stock recovery mode in 5.1.1 when flashfire is used?

fastcar22 said:
i am sorry i meant to ask a different question, is there a way to get to stock recovery mode in 5.1.1 when flashfire is used?
Click to expand...
Click to collapse
what likely happened is FlashFire moved the wipe option to last task
so the rom was wiped from system, then device rebooted
for some reason those with the 5.1.1 bootloader, lose recovery, for some reason.
if the rom was Bootable, i believe stock recovery would also still work.
right now I have no idea how to fix it.
Sent from my KFFOWI using Tapatalk

sd_shadow said:
what likely happened is FlashFire moved the wipe option to last task
so the rom was wiped from system, then device rebooted
for some reason those with the 5.1.1 bootloader, lose recovery, for some reason.
if the rom was Bootable, i believe stock recovery would also still work.
right now I have no idea how to fix it.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
thanks for your replies, i will wait for a solution until then i will stick with my bricked device

Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea

Nea123 said:
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Click to expand...
Click to collapse
There seems to be a few of us with this problem but all we have is fastboot to work with so it doesn't look good, without adb i don`t know how we can flash anything.

Nea123 said:
Hello, i have the same problem. Is it possible to unbrick my device with 5.1.1? Maybe is it now possible, i hope so.
Thanks a lot.
Nea
Click to expand...
Click to collapse
All 2015 Fires are within 1 year warranty. Contact Amazon for replacement options.

I think this is not a good idea. The fire hangs on the boot screan with cm12.1 .

LG LGMS550 Stylo 2 Plus?

Just delete this if it's considered in the wrong place. If and when is the the Stylo 2 Plus getting its own forum and has anyone come up with an exploit for rooting this phone yet?

Hiya
Yes this is the wrong place. This is for the g stylo not the stylo 2 plus as can be seen in the name of the forum.
No there is not an exploit yet. Kingroot, kangoroot, one clove root, etc all do not work yet. Soon i would imagine
I even have trouble looking on the web for things because it seems we share a model number ms550 with the lg optimus m. Weird

You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.

Reserved

Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
mustangtim49 said:
You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6

Remote: unknown command
Rmontoya83 said:
Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6
Click to expand...
Click to collapse
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.

I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Rmontoya83 said:
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.
Click to expand...
Click to collapse

[email protected] said:
I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Click to expand...
Click to collapse
Then Twrp didn't flash

Flashing
Rmontoya83 said:
Then Twrp didn't flash
Click to expand...
Click to collapse
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?

[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
What software version are you running?

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
Wrong command your trying to boot twrp
The correct command is "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse

It was something I found in another tutorial when I started trying other things, since the "fastboot flash recovery recovery.img" was not getting me past the standard Android recovery. I'm about to try the file you sent me last night. I'll let you know the result.
---------- Post added at 10:25 PM ---------- Previous post was at 10:13 PM ----------
Rmontoya83 said:
What software version are you running?
Click to expand...
Click to collapse
Android version 6.0.1
Android security patch level 2016-08-01
Kernel version 3.18.20
Windows 7 Pro x64
The recovery.img you sent also said it flashed, but I got to the same Android factory reset screen after the key press procedure (volume down, power, release power, repress power, release all)
Here's the latest:
C:\Users\Darin\Downloads\platform-tools-latest-windows\platform-tools>fastboot f
lash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15518 KB)...
OKAY [ 0.495s]
writing 'recovery'...
OKAY [ 0.362s]
finished. total time: 0.865s

Once you boot into recovery, let the screen fully dim, do not touch it... once the screen is completely blacked out, turn it back on and all touch features will be up and running... and don't mess with the adoptable storage feature..migrating data.. because TWRP will not recognise any data if you have this enabled.

[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
You have to push the ing to and directory. Fastboot push img
Sent from my LG-K550 using Tapatalk

[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
Are you on the newest firmware for that phone?
If you are downgrade that could be a fix to lock down the recovery

I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it? Usbhost mode..mount
Usb pendrive-
Mouse
Usb hub
Keyboard...etc
They say LG STYLO 2 PLUS DOES NOT SUPPORT OTG...LIES....LIES....THEY JUST DISABLED IT...WHY?...WELL..
FOLLOW THESE STEPS TO ENABLE FULL OTG SUPPORT
1-in root explorer go to:
-/sys/devices/soc/78db000.usb/power_supply/usb/usb_otg and edit from =0 to 1save
then-/sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit disabled to enable.. plug in otg cable..
Done

WoodEe23 said:
I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it?
Click to expand...
Click to collapse
You enabled it by adding it to the build prop lol

Dig waaayyyy deeper ..like
/sys/devices/soc/78db000.usb/power_supply/usb/ scroll to usb_otg and edit it from disabled to enable.
Then /sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit it to enabled..
VOILA!!!"PLUGIN OTG CABLE AND UR IN THERE LIKE SWIMWEAR

P 8 lite bootloop on stock firmware

Hello all,
I have Huawei P8 lite bought from Romania. I install the android 6 and I wanted to go back to 5, so I go trough the steps on the official huawei website :
1) download an install rollback package - all went fine, the B500 firmware was shown
2)download an install B132 - on this step the problem appear; after the installation the phone is in a continuous bootloop, it can;t even shut down for good. I hear the start up sound, then if I press the volume keys it's beeping, so somehow is booting but without showing nothing(strange random colors ). The PC is recognizing the phone, but ADB won't .
The phone isn't going in to the recovery mode or update mode.
I search the forum and found methods to unbrick the phone, but only using fastboot. Since my phone isn't rooted , I can't use this method. What can I do?

Moshu646 said:
Hello all,
I have Huawei P8 lite bought from Romania. I install the android 6 and I wanted to go back to 5, so I go trough the steps on the official huawei website :
1) download an install rollback package - all went fine, the B500 firmware was shown
2)download an install B132 - on this step the problem appear; after the installation the phone is in a continuous bootloop, it can;t even shut down for good. I hear the start up sound, then if I press the volume keys it's beeping, so somehow is booting but without showing nothing(strange random colors ). The PC is recognizing the phone, but ADB won't .
The phone isn't going in to the recovery mode or update mode.
I search the forum and found methods to unbrick the phone, but only using fastboot. Since my phone isn't rooted , I can't use this method. What can I do?
Click to expand...
Click to collapse
You don't need to be rooted to use fastboot. However you need to unlock the bootloader in order to use it and don't tell me that your bootloader is locked otherwise it's a bad news.

Yes, it is locked

Moshu646 said:
Yes, it is locked
Click to expand...
Click to collapse
Use Huawei restore mode from hi suite.

I manage to enter in recovery mode(thus nothing is shown on the screen) , the HI Suite tells me that I successfully entered in recovery mode, but when I press Recover I get: Your device is not supported for system recovery

Moshu646 said:
I manage to enter in recovery mode(thus nothing is shown on the screen) , the HI Suite tells me that I successfully entered in recovery mode, but when I press Recover I get: Your device is not supported for system recovery
Click to expand...
Click to collapse
Is there an option for flashing rom? If then select that option and then select official firmware and then continue.

Suleiman01 said:
Is there an option for flashing rom? If then select that option and then select official firmware and then continue.
Click to expand...
Click to collapse
I don't see nothing on screen.
Now I discovered that if I enter in recovery mode ( Volume down + Power ; still nothing showing on the screen), fastboot is recognizing my device but when I want to write something I get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash BOOT boot.img
target didn't report max-download-size
sending 'BOOT' (21708 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s

Moshu646 said:
I don't see nothing on screen.
Now I discovered that if I enter in recovery mode ( Volume down + Power ; still nothing showing on the screen), fastboot is recognizing my device but when I want to write something I get this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash BOOT boot.img
target didn't report max-download-size
sending 'BOOT' (21708 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
You can't because your phone is locked. Did you find that rom flashing option on Hisuite?

Suleiman01 said:
You can't because your phone is locked. Did you find that rom flashing option on Hisuite?
Click to expand...
Click to collapse
It has an Update option but HI is not connecting to my device because I have to tap something on my phone in order to connect.

Moshu646 said:
Yes, it is locked
Click to expand...
Click to collapse
Hello ,
I have an update : I manage to unlock fastboot
I also manage to write successfully the boot, cust, recovery an system img's , but the phone is still not working: it starts up, the screen is lightening, I hear the Huawei sound, but no logo, and then the phone shut's down

Moshu646 said:
Hello ,
I have an update : I manage to unlock fastboot
I also manage to write successfully the boot, cust, recovery an system img's , but the phone is still not working: it starts up, the screen is lightening, I hear the Huawei sound, but no logo, and then the phone shut's down
Click to expand...
Click to collapse
Can you go to recovery?

Moshu646 said:
I have an update : I manage to unlock fastboot
Click to expand...
Click to collapse
How did you do that? My phone is also in bootloop and I am not sure how to unlock the bootloader...

cunami said:
How did you do that? My phone is also in bootloop and I am not sure how to unlock the bootloader...
Click to expand...
Click to collapse
There is a program called Huawei product ID generator. You need Imei,Serial no.(both are on the box) and Product ID (via Huawei product ID generator). Through this you can obtain unlocking code
In Fastboot and rescue mode type this in minimal adb and fastboot
fastboot oem unlock XXXXXXXXXXXXXXXXX
Where XXXXXXXXXXXXXXXXX is the unlocking code.

Moshu646 said:
It has an Update option but HI is not connecting to my device because I have to tap something on my phone in order to connect.
Click to expand...
Click to collapse
I was talking about this (see the picture below).

Suleiman01 said:
There is a program called Huawei product ID generator. You need Imei,Serial no.(both are on the box) and Product ID (via Huawei product ID generator). Through this you can obtain unlocking code
In Fastboot and rescue mode type this in minimal adb and fastboot
fastboot oem unlock XXXXXXXXXXXXXXXXX
Where XXXXXXXXXXXXXXXXX is the unlocking code.
Click to expand...
Click to collapse
Thanks! Will try definitely.
Last question - does the bootloader unlock wipe the user data on the phone? I want somehow to extract it before flashing any ROM over. So my idea was to unlock it, flash some better recovery and make a backup of data partition.

I don't have that option
Maybe it appear when the devices is connected.

Moshu646 said:
I don't have that option
Maybe it appear when the devices is connected.
Click to expand...
Click to collapse
It appears on 64 bit version of Windows I tried it on 32 bit it wasn't there.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
cunami said:
Thanks! Will try definitely.
Last question - does the bootloader unlock wipe the user data on the phone? I want somehow to extract it before flashing any ROM over. So my idea was to unlock it, flash some better recovery and make a backup of data partition.
Click to expand...
Click to collapse
No. At least when I unlock my phone bootloader didn't wipe my data.
Just press thanks button if you don't mind

Suleiman01 said:
It appears on 64 bit version of Windows I tried it on 32 bit it wasn't there.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
No. At least when I unlock my phone bootloader didn't wipe my data.
Just press thanks button if you don't mind
Click to expand...
Click to collapse
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?

Moshu646 said:
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?
Click to expand...
Click to collapse
I have 4.0.6.301 version of Hisuite. Download it from this link(use chrome to translate it's Chinese).
http://consumer.huawei.com/minisite/HiSuite_cn/index.html
---------- Post added at 11:25 AM ---------- Previous post was at 11:05 AM ----------
Moshu646 said:
I also have X64 windows, but my HI version is 4.0.5 and this is the last one, and only this I found to download. Where do you have the 4.0.6?
Click to expand...
Click to collapse
Try this multi tool by sokoban.
http://huaweip8lite.blogspot.com/2016/04/mod-p8-lite-multi-tool-by-sokoban.html?m=1

The ROM flashing option is not active- I think because the device is not connected.
Tried with the multi tool, same result

[GUIDE]Android 11 how to root T-MOBILE OP8 5G

THIS GUIDE IS FOR THE T-MOBILE ONEPLUS 8 5G ONLY!!!!
This method has only been tested on the above mentioned device. It may be possible to use *parts* of this guide on other oneplus/android devices, but you do so at your own risk!
Furthermore no warranty or liability of any kind is offered or implied for any damages to any person(s), devices, or other property by following, or otherwise using any information contained in this guide be it inaccurate information or otherwise.
By using this guide you're agreeing to these terms.
MAKE SURE TO READ THROUGH THE ENTIRE GUIDE BEFORE ATTEMPTING TO FOLLOW IT!
That said I've done my best to ensure this guide is an accurate representaion of the steps I followed to do the things laid out in this guide.
Required items:
Bootloader unlock token from OnePlus.
adb fastboot drivers installed to path. (Not provided)
Now that all that is out of the way. Let's get started!​Rooting with provided boot.img
Spoiler: Click to show
1. Make sure that you are running some version of Android 11 via Settings>About phone.
2. Take note of your Build Number you'll need that later.
3. Click on build number five times to enable developer options.
4. Navigate to developer options under Settings>System>Developer options.
Turn on oem unlocking, as well as usb debugging & turn off automatic updates.
5. Open a cmd prompt on your pc, or terminal on linux. Enter the following lines.
Code:
adb devices
*Check the always allow from this device checkbox then hit allow.
You should see your device listed. If it says unrecognized re-enter the line above.
Code:
adb reboot bootloader
*Your device should reboot into fastboot. Once it has proceed.
6. Now we must unlock the bootloader. cd to the directory where you have saved your unlock token.
For example if you saved it to the Desktop of a windows machine the directory would most likely be
users/*yourusernamehere*/Desktop.
7. Enter the following lines. One at a time.
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
*Follow the prompts on your device to unlock your bootloader *****THIS WILL WIPE YOUR DEVICE SO MAKE SURE TO BACKUP YOUR DATA*****
8. Get past setup on your device re-enable developer options, and usb debugging, turn off automatic updates.
9. Follow the process to get back into fastboot via adb.
10. Remember your build number. Download the boot image that matches your build number here:
https://www.androidfilehost.com/?w=files&flid=322713
(I've only tested this on the device I pulled from, but unless something drastic has changed since the last time I dealt with stuff like this these should work fine as long as the device is a Tmobile OP8, and the build number is the same.)
(I will try to keep this updated as new updates are released, but work keeps me rather busy so it may not always be quickly.)
11. Now open a cmd prompt (if you haven't already) navigate to where you saved the boot img. Enter the following.
Code:
fastboot devices
*You see your device listed in that case proceed.
Code:
fastboot flash boot_a boot.img
*If the process completes without errors then continue
then
Code:
fastboot flash boot_b boot.img
*If the process completes without errors then continue
finally
Code:
fastboot reboot
12. Your device should boot up. Install the magisk manager app if it is not installed. Open MM & follow the prompts to finish setup. Enable magisk hide, and reboot. SafetyNet should pass.
Congrats! You have a Tmobile Oneplus 8 with root!
Using/Acquiring your own boot.img
Spoiler: Click to show
This section of the guide will assume you are familiar with using adb/adb shell commands, as well as being familiar with android, and other terms.
To put it plainly it will be a lot less hand holdy lol. This process requires root. So technically you won't be required to pull you're own image.
However it should be noted that doing so will streamline the process for later in the event that you need to restore to stock, and re-root later on.
*****YOU MUST BEGIN ON ANDROID 10 TO USE THIS METHOD*****
If you are not downgrade via the msmtool, re-unlock your bootloader & make sure automatic updates are disabled in developer options.
Let's begin.
1. Connect your phone to your pc with usb debugging enabled & reboot into fastboot.
2. Copy a Magisk zip file to your internal storage.
3. Boot the latest twrp (DO NOT TRY TO BOOT OR INSTALL TWRP ON AN ANDROID 11 DEVICE TWRP DOES NOT CURRENTLY SUPPORT IT!!!!)
Code:
fastboot boot recovery "twrp.img"
*****replace twrp.img with the filename of your twrp minus the quotes.*****
4. Flash the magisk zip and reboot.
5. Download & install the latest update, but do not reboot.
6. Open magisk click install>Install to inactive slot(after ota).
*Before rebooting make a note of which slot magisk says it's installing to.
We will need this later to know which boot image slot to pull from.
7. Reboot through magisk.
*You should now be on the latest update with root.
8.Open a cmd prompt and enter the following
Code:
adb shell
then
Code:
su
*grant the su request on your device.
9. Now we must find the location of both boot paritiions. Enter the following
Code:
ls /dev/block/bootdevice/by-name/ -all
10. This will display a list of all partitions on the device there are 2 we must make a note of, and 1 that is optional but highly recommended.
These are boot_a, boot_b, and optionally persist.
Open a notepad, and copy and those lines into a txt document and save.
(You can optionally delete the part of the lines before boot_a, boot_b etc. To make it easier to read.)
11. Now whichever slot magisk flashed to is what we need to pull from open your previously saved txt document, and find the path to which slot it is
Ex: /dev/block/******
12. In the command propt enter the following.
Code:
dd if=/dev/block/***** of=/sdcard/boot.img
*****Replace the "*'s" with the rest of the path for the slot you need!*****
NOTE: If you wish to backup your persist partition then repeat step 12. Replacing the "if" path with that of the persist partition you made note of earlier, and the boot.img part of the "of" path with persist.img.
13. Copy those files from your internal storage to your pc using explorer or adb pull -p from the command prompt in the directory you would like them stored.
And that's it Congrats! You've learned how to pull your own boot.img from your device, and have root on android 11!
If you ever need to restore from stock you can just update back to android 11, and flash your boot images via fastboot.
Note: I would recommend storing your boot images in folders named as the Build Number to ensure you don't mix them up. YOU WILL NEED TO REPULL YOUR BOOT IMAGES AFTER EVERY UPDATE!
Updating in the future
Spoiler: Click to show
To update to new Android versions & keep root follow these steps.
1. Make sure automatic updates in developer options are off.
2. Download and install the update, BUT DO NOT REBOOT.
3. Open magisk select install>Install to inactive slot(after ota).
4. Reboot through magisk.
5. You should reboot into the update with root preserved.
6. Pull the new patched boot image if you wish.
A few things to leave you with.
It's been a while since I've dabbled with this side of development (I've mostly been focusing on app development, and occasionally magisk rom development.)
So.
Some things, and processes in this guide may change as future updates occur.
I'll try to update it as neccesary, but my work usually keeps me pretty busy.
Don't be afraid to ask any questions or suggest any corrections to this guide.
I'll do my best help anyone with any problems or issues, but be sure to provide as much information as humanly possbile to help me or others assist with the problem.​

(Reserved)

Does bootloader need unlocked through tmobile

wwe9112 said:
Does bootloader need unlocked through tmobile
Click to expand...
Click to collapse
Yes you still need your bootloader unlocked through OnePlus/T-Mobile. Sorry for the confusion. I'll add that to the Op. I just wanted to lay out how to obtain/provide a patched boot image for T-mobile users on Tmo's OxygenOS. Since all I've seen is global/Eu versions.

1 is there a way to unlock and root without wipe? :C
2 What could be the advantage of changing from t-mobile version to global? is there a hardware diference or something to be afraid of?
Thank you

rophiroth said:
1 is there a way to unlock and root without wipe? :C
2 What could be the advantage of changing from t-mobile version to global? is there a hardware diference or something to be afraid of?
Thank you
Click to expand...
Click to collapse
1. No unlocking the bootloader will always perform a factory reset.
2. This guide isn't for that. It serves as a repository for T-Mobile variant patched boot, or explains how to get your own images to flash via fastboot to be able to root past Android 10. Since Twrp doesn't support Android 11 yet.
As for the perks of switching to global a few I can think of would be.
No T-mo bloat.
Updates from Oneplus containing all features.
I believe it enables the local upgrade option for downloading, and installing updates downloaded via The OP website. (Only global/non tmo updates are available on the site).
I'm sure there are probably a few other minor differences.
As far as I'm aware the process isn't as straight forward as it used to be with the 6t, 7 etc. So there is more of a potential for something to go wrong. Could be off putting for some I suppose. For more details I suggest looking at one of the conversion guides.

TheLogicalGamer said:
1. No unlocking the bootloader will always perform a factory reset.
Click to expand...
Click to collapse
Why a factory reset should be needed in that part... :/
thank you

rophiroth said:
Why a factory reset should be needed in that part... :/
thank you
Click to expand...
Click to collapse
I'm not entirely sure as to why. It just part of the process (on every device with an unlockable bootloader).
Aside from potentially saving on troubleshooting down the line. Perhaps it's a liability issue. Since technically unlocking the bootloader does make your device less secure. The manufacturer can't be to blame for stolen/lost data since anything you would've put on the device would have been put there yourself. The warning message doesn't appear until after the bootloader is unlocked. So by wiping the device before hand/during the process it insures that you have seen the warning, and are choosing to put said data on the device of your own free will after having been warned.
So my best guess would be to protect themselves from potential lawsuits. Assuming that there is no technical reason for needing it. (Which I'm not entirely sure that there isn't).

Im in troubles. I do flash the cust-unlock, no errors but nothing really happens T,T im using android 11
Code:
PS C:\WINDOWS\system32> fastboot flash cust-unlock 'C:\Android\Oneplus 8\unlock_code.bin'
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.014s]
finished. total time: 0.027s
When I try to flash anything else, it says:
PS C:\WINDOWS\system32> fastboot flash boot_a 'C:\Android\Oneplus 8\rooted boot tmobile.img'
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.117s]
writing 'boot_a'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 2.139s
Click to expand...
Click to collapse
I had to run an adittional command:
PS C:\WINDOWS\system32> fastboot flashing unlock
...
OKAY [ 0.035s]
finished. total time: 0.038s
Click to expand...
Click to collapse

rophiroth said:
Im in troubles. I do flash the cust-unlock, no errors but nothing really happens T,T im using android 11
Code:
PS C:\WINDOWS\system32> fastboot flash cust-unlock 'C:\Android\Oneplus 8\unlock_code.bin'
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.014s]
finished. total time: 0.027s
When I try to flash anything else, it says:
Click to expand...
Click to collapse
Try running
Code:
fastboot getvar unlocked
And let me know what it says.
Also did you let the phone boot up all the way before attempting to flash the boot image?
Edit: Did you run the fastboot oem unlock command after flashing the unlock code?

rophiroth said:
Im in troubles. I do flash the cust-unlock, no errors but nothing really happens T,T im using android 11
Code:
PS C:\WINDOWS\system32> fastboot flash cust-unlock 'C:\Android\Oneplus 8\unlock_code.bin'
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.014s]
finished. total time: 0.027s
When I try to flash anything else, it says:
I had to run an adittional command:
Click to expand...
Click to collapse
Yeah just looked at the guide, and it seems I forgot to include that step. Everything is fine. Your device is unlocked just not the bootloader. Before you can flash the boot image you'll need to run this:
Code:
fastboot oem unlock
Then confirm using the volume keys on your phone. Then you'll be able to flash the boot image. I've added that step to the guide. Sorry for the mistake.

TheLogicalGamer said:
Yeah just looked at the guide, and it seems I forgot to include that step. Everything is fine. Your device is unlocked just not the bootloader. Before you can flash the boot image you'll need to run this:
Code:
fastboot oem unlock
Then confirm using the volume keys on your phone. Then you'll be able to flash the boot image. I've added that step to the guide. Sorry for the mistake.
Click to expand...
Click to collapse
Yes, I unlock my phone, run magisk... and safety check mark everything wrong z,z Happen to anyonemore?

rophiroth said:
Yes, I unlock my phone, run magisk... and safety check mark everything wrong z,z Happen to anyonemore?
Click to expand...
Click to collapse
Try enabling magisk hide, and rebooting.

TheLogicalGamer said:
Try enabling magisk hide, and rebooting.
Click to expand...
Click to collapse
I'm sorry, I didn't see there wasn't enabled by default. That's works well.
Pd: some one experience heat after root? Maybe it's just te restoration of files and all..
Thank you

rophiroth said:
I'm sorry, I didn't see there wasn't enabled by default. That's works well.
Pd: some one experience heat after root? Maybe it's just te restoration of files and all..
Thank you
Click to expand...
Click to collapse
Sorry was doing some repairs on a phone. I haven't noticed any different. It could a get a bit hot during first boot from what I remember. Just keep an eye on it, see if it cools down. But rooting itself shouldn't cause that no.

If anyone needs to SIM UNLOCK & OEM UNLOCK the bootoader: goto Settings> WiFi&Network> SIM&Network> Network Unlock. If anyone can help on how to get the token unlock code, it would help some. For PUK and other unlocks https://www.t-mobile.com/support/devices/android/oneplus-8 and then scroll down to Security. There you have option to unlock several things.

How can you find out if your SIM Unlocked?

ink718 said:
If anyone needs to SIM UNLOCK & OEM UNLOCK the bootoader: goto Settings> WiFi&Network> SIM&Network> Network Unlock. If anyone can help on how to get the token unlock code, it would help some. For PUK and other unlocks https://www.t-mobile.com/support/devices/android/oneplus-8 and then scroll down to Security. There you have option to unlock several things.
Click to expand...
Click to collapse
You can only unlock the bootloader if you have the sim unlocked. Which usually happens when you paid off your device, but if you've been on the network for 40 days, and made a couple of payments you can usually get them to do it for you. Might have to annoy them a bit. As for the unlock token you have to submit an unlock request to oneplus, and they'll email it to you. However this must be done AFTER getting the sim unlocked. The sim & Bl unlocks are tied together. Can't do one without the other unless a work around is found.

Updating in the future
Spoiler: Click to show
To update to new Android versions & keep root follow these steps.
1. Make sure automatic updates in developer options are off.
2. Download and install the update, BUT DO NOT REBOOT.
3. Open magisk select install>Install to inactive slot(after ota).
4. Reboot through magisk.
5. You should reboot into the update with root preserved.
6. Pull the new patched boot image if you wish.
[/QUOTE]
How or where to download the update?
Thank you!

ink718 said:
If anyone needs to SIM UNLOCK & OEM UNLOCK the bootoader: goto Settings> WiFi&Network> SIM&Network> Network Unlock. If anyone can help on how to get the token unlock code, it would help some. For PUK and other unlocks https://www.t-mobile.com/support/devices/android/oneplus-8 and then scroll down to Security. There you have option to unlock several things.
Click to expand...
Click to collapse
Never Settle - OnePlus.com
OnePlus creates beautifully designed products with premium build quality & brings the best technology to users around the world. No tradeoffs, we #NeverSettle.
support.oneplus.com
Detailed unlock instructions