Database Users

[Beginners Guide] Unlock & Custom ROM your TF300

I have been asked to port my "Beginners Guide" from the TF700 forum for the TF300. Since both tablets are very similar, that was not too hard to do
If I have missed to update a link specific for the TF300, do let me know please.
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
These instructions assume that you are on the latest Asus bootloader: 10.6.1.27.5
To determine which bootloader you currently have:
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.27.5-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.27.5 is your bootloader version
20130801 is the build date (and immaterial in most cases).
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF300 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery​
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: https://www.asus.com/support/Download/28/1/0/9/8BmzkQ4yoz5WzBrW/32/
Choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v7 (not v8! It says v7 is for ICS but it'll work fine on JB - see below)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. Google it if you hit that roadblock.
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!​
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8 and 10 you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Or - even better - here's a quick command line toggle to achieve the same (thank you @Jack_Hardin):
Jack_Hardin said:
If you're running W10, you can disable Device Driver Signing without following the procedure in the linked video, but by (more simply) right-clicking on the Start button, selecting Command Prompt (Admin) and then typing:
Code:
BCDEDIT /set nointegritychecks ON
Doing the same with OFF at the end of the string, as easy to guess as it looks, will reenable them.
Click to expand...
Click to collapse
Jack_Hardin said:
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
Click me: View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the drivers I linked to above. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://dl.twrp.me/tf300t/
Download the latest version of TWRP.
FYI ONLY: If, for whatever reason, you want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe. Note: More recent versions of TWRP download with an .img extension. Leave the extensions as is, rename the first part to watever is easy to type
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
or
Code:
fastboot -i 0x0B05 flash recovery twrp.img
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
You may get a dialog in TWRP offering to root the stock rom. You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
To create your Nandroid (a full system backup) touch "Backup", leave the default selection as they are and swipe the button to create a nandroid of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: http://forum.xda-developers.com/transformer-tf300t/development
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
FREE ADVICE
There are alternative methods to flash a recovery to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work - mostly - and if you have root. But I would not recommend them.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
Click to expand...
Click to collapse

Save it for later

Mine

sbdags said:
@stamatis could we sticky this please.
Brilliant post Bernd :good:
Click to expand...
Click to collapse
Can we make that happen here to @stamatis
Thx Josh

Nice one Bernd! :good::good:

boot sequence
Hi,
Is normal to see three TUX and some phrases at the power on ?
Can I hide it ?
tnkx
Nicola

You mean the penguins?
That's normal I'd you're running a Rom that uses _that's preinit scripts. You can't hide them - why would you?

thank you SO much
I love you!
Wow, I've never had so much trouble rooting a device before! And days ago, I rooted my T700 without any problems. So, I guess I should have expected the hubby's TF300T to be problematic! Recoveries didn't work, I tried multiple ones. Eventually, I had a recovery that didn't recognize any partitions. I used fastboot to erase them all and put the stock ROM back on--wouldn't boot up. This thread was an immense help! I've moved the other recoveries and ROMs into my non-working folder!
Thanks again!
Lynne

Awesome
What a well written guide! I have a decent understanding of fastboot and adb (although minimal experience), and I perfectly understood every step.
My advice to all newbies like me.... Read stuff ALL of the way through (and understand it), BEFORE stepping off in it.

ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris

scuzzo said:
ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris
Click to expand...
Click to collapse
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh

lj50036 said:
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh
Click to expand...
Click to collapse
hello,
bootloader is unlocked or at least it says it is at the boot screen.. "your device is unlocked"..
real time... just swapped ports... its says it pushed the recovery.... so... will continue along this path.... and see how it goes.... i think its good to go... just as you suggested... port swap... cool... i bought this just so i could root it and put the kit kat kis rom on it.... thanks for your help and big ups to OP.... great guide ...
thanks again.!

Nice guide!
I've been wanting to put a custom rom on my transformer for a long time. This guide worked like a charm.
The only problem I had was when I tried to flash TWRP recovery, but switching USB port fixed that problem.
I flashed the latest CM12.1 nightly and it works fine.
Many thanks!

Help please, I'm stuck!
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks

You won't see anything on the tablet screen, but what does the command window say?
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk

berndblb said:
You won't see anything on the tablet screen, but what does the command window say?
The command window didn't say anything, just blinking cursor after my command line
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Mishka79 said:
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks
Click to expand...
Click to collapse
Thanks,
After writing the question, I've restarted my tablet and did all the steps again.
The second time everything worked as it should. :good:
thanks for your great guide

Really great guide
Amazing guide thanks for the help

Thank you for this good tutorial but I have one question.
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!

ANDROIDYER said:
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!
Click to expand...
Click to collapse
I have not used CM in quite a while but I think you have to enable root in Developer Options. I think it is not enabled by default.
If hat does not work you can go to Chainfire's website and download the flashable SuperSU and just flash it in recovery

Thanks and a couple of notes on TF300T
Thanks so much for the great guide. My 300TF was nearly bricked due to slowness and freeze-ups. I'd stopped using it. The process worked and am now running KatKiss. Couple of problems and their solutions for anyone who may have the 300TF:
-When trying to "Unlock Bootloader" I kept getting to "enter Google password" but when I did so (correctly) it was not accepted. The solution was to do another factory reset and NOT install google services. Didn't ask for password after that.
-Used fastboot command line to install "twrp.blob" but nothing happened and it timed out. I had to take out other usb connect programs first (in my case "easy-tether" and my LG phone connect app.) After that everything went as per your guide.
Thanks again
Geneg

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead

I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.

Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.

Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.

thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable

I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.

SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll

Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip

"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553

Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?

got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)

Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?

bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery

Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now

bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .

I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|

When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.

My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse

bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.

After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

[GUIDE] Root Huawei Honor 8 SMART and install TWRP custom recovery (EMUI 5.X)

Note-
Applicable for Windows 7, Windows 8 and Windows 10
Similar steps are applicable for EMUI 4.X as well but TWRP file will change.
Hello Fellow Members,
Did not find any post mentioning rooting for Honor 8 SMART and got requests via PM and on FB to add it for EMUI 5. If there are any, let me know and I will take down this thread. I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
Prerequisites-
Enable the developer option in settings-
Go to Settings--> About Phone-->Tab build number 7 times to enable this setting.
Go back in setting page, just above system update, you will see a new menu as -Developer Options
Scroll for the debugging section and enable the USB Debugging
You will be prompted for the confirmation with RSA key, just accept it.
Enable OEM Unlock in Developer Options (just above the USB debugging option) – Most probably this option will not be there on EMUI 5.0 (only few have seen on EMUI but it was there on EMUI 4.1 for all but rarely on EMUI 5.0 or may be because I have used dload most of the time which grayed out this)
Please note down you build number, this may become handy in case something goes wrong to restore your phone via DLOAD. In Settings- About phone- Build Number
Installation of required Drivers.
Connect your phone to PC and install Hi Suite on PC and it will additionally install all the necessary drivers to PC and HiSUite on Mobile.
Download and Install ADB from Link
Accept all the prompts and install ADB drive system wise.
Once installation is completed, if default options are chosen, it will be under C:\adb
Downloading the necessary files.
Download TWRP from Link Thanks to @OldDroid for his Original Thread . Rest of the contributor and credit in original thread by OldDroid.
Move the downloaded file under C:\adb or wherever you have installed the ADB.
Download the SuperSU file from this Link and put it in SD card or keep handy on PC so that you can copy to internal memory later.
Get the unlock as mentioned in this thread
Actual Procedure
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run - adb reboot bootloader
Once in bootloader, Run - fastboot flash recovery twrp-3.1.1-0-venus.img (This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run - fastboot reboot
Rooting
Once booted to system, open the PowerShell or command prompt in ADB folder (can use the previous instance as well)
Run - adb reboot recovery
And your phone will boot into the TWRP recovery.
Copy the SuperU file downloaded to SD card or Internal memory.
Install the SuperSU zip.
Reboot and enjoy.
Happy Flashing.

I have try,but it doesn't work.

Snoopys Woodstock said:
I have try,but it doesn't work.
Click to expand...
Click to collapse
One of the user, imssk has tried this and worked fine for him without any problem. What is the error you are getting

Cool thanks. Different question: Why honor does not provide monthly or 3 months security updates.Very disappointed with them. I know we are not getting Oreo update but atleast provide security update in at least three months.

please help me sir im aniket from india ive rooted the phone accordingly but i made a mistake while formatting from twrp and lost encryption and then i formatted the whole os and as downloaded the stock firmware from official consumer huawei site the rom doest gets flashed i even tried flashing by extracting the update.app file but still the system file wont flash and fails every time please help me as sson as possible

Aniket02141 said:
please help me sir im aniket from india ive rooted the phone accordingly but i made a mistake while formatting from twrp and lost encryption and then i formatted the whole os and as downloaded the stock firmware from official consumer huawei site the rom doest gets flashed i even tried flashing by extracting the update.app file but still the system file wont flash and fails every time please help me as sson as possible
Click to expand...
Click to collapse
Flashing via twrp or dload method?

Custom ROMs?
Hello I have been searching for custom ROMs for ven-l22 but haven't found any. Would you know of any? Thanks.

Babakkardan said:
Hello I have been searching for custom ROMs for ven-l22 but haven't found any. Would you know of any? Thanks.
Click to expand...
Click to collapse
Use p9 lite ROM. It will work

Thanks that is very useful.
Is USB otg working on this phone?

Babakkardan said:
Thanks that is very useful.
Is USB otg working on this phone?
Click to expand...
Click to collapse
With custom ROM and root, yes.

Huawei disabled the site.
I sent them email and they refused to give me a key I am their customer.I paid them.How can I unlock it?

VFR99 said:
I sent them email and they refused to give me a key I am their customer.I paid them.How can I unlock it?
Click to expand...
Click to collapse
Via paid services like dc unlocker, Chimera tool, HCU client etc.

I don't want to pay
shashank1320 said:
Via paid services like dc unlocker, Chimera tool, HCU client etc.
Click to expand...
Click to collapse
It was free now why should I pay?Come on they are a dumb company.

VFR99 said:
It was free now why should I pay?Come on they are a dumb company.
Click to expand...
Click to collapse
Well thats something i cant comment
They have stopped providing the code long back

shashank1320 said:
Well thats something i cant comment
They have stopped providing the code long back
Click to expand...
Click to collapse
It's not your fault

[Guide] how to root and install TWRP on redmi note 6 pro

First of all at the time there is no official way to root redmi note 6 pro
This guide is suitable for the global version and mybe Indian version need to check because in India redmi note 6 pro not available
I'm not responsible if anything happens to your device. If you execute this procedure properly then you shouldn't face any problems. I tried this procedure on Redmi Note 6 pro and it worked flawlessly. I used a computer with Windows 10 insider .
Before you proceed please back up all your important data and make sure that your phone battery is charged >60%
A .Prerequisites
1. Disable driver signature enforcement in Windows
How to do this pls read here: http://en.miui.com/thread-237673-1-1.html
2. Install ADB and Fastboot tools with drivers on Windows
How to do this pls read here: https://forum.xda-developers.com/sho....php?t=2588979
3. Enable "OEM unlocking" and "USB debugging" in your device
a. Enable Developer Options in: Settings/About Phone/MIUI version. Click on MIUI version seven times
b. Now go to: Settings/Additional Settings/Developer Options and check "OEM unlocking" and "USB debugging"
4. Check if your bootloader is locked
a. After successful installation of "ADB and Fastboot" enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer via USB cable (best would be the original cable).
b. Go to the folder where you have put the "ADB and Fastboot" and open a command window inside that folder. To do that hold together "Shift + Right Click" on any empty white space inside the folder and then select "Open PowerShell Window Here" or "Open Command Window Here"
c. Enter the terminal command in command line: >>fastboot devices<<
If you don't see your device it means that the drivers weren't installed properly or the device wasn't connected properly. If this happens please reinstall your drivers from Point A. 2. or try these drivers here:
http://xiaomiadvices.com/download-xiaomi-usb-drivers/
d. If you see your device then enter the terminal command in command line: >>fastboot oem device-info<<
If your bootloader is locked, you'll get the following status (or something similar):
…………………………………………………………………….
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
finished. total time: 0.063s
………………………………………………………………………
If your bootloader is unlocked, you'll get following status (or something similar):
…………………………………………………………………….
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.053s]
finished. total time: 0.055s
………………………………………………………………………
5. Request Permission from Xiaomi to Unlock the Bootloader
a. Create a Mi Account: https://global.account.xiaomi.com/pass/register
b. Sign to Xiaomi and apply for unlocking http://en.miui.com/unlock
You have to give a reason for requesting to unlock the bootloader.
c. Wait for permission. however very few users are reporting a waiting time of up to 7 days . If your request is approved then you should receive a message with following content:
"You've been granted the permission to unlock your device (Mi Account xxxx). Donload Mi Unlock Tool At http://en.miui.com/unlock"
6. Connect your Mi Account to your Device
Go to: Settings/Additional Settings/Developer Options/Mi Unlock status and check "Add account and device"
B . UNLOCKING BOOTLOADER
Attention: Unlocking the bootloader will erase all your data! So please back up your data before you unlock the bootloader
1. You must enable "OEM unlocking" and "USB debugging" as per point A. 3.
2. You must connect your Mi Account with your device as per point A. 6.
3. Download Mi Unlock Tool here: http://en.miui.com/unlock
4. Enter the fastboot mode by holding together "Volume Down + Power" and connect your device to your computer via USB cable (best would be the original cable)
5. Start the Mi Unlock Tool
6. Enter your eMail and your password of your Mi Account
7. Connect you device to your computer and start the unlock procedure
8. Follow the unlock tool instructions until the unlock procedure is finished
9. Reboot your device
In case you get the message, that the unlocking can be done after 360h or 720h then you have to wait for that time to pass
C . INSTALL THE TWRP RECOVERY
your boot loader must be unlocked
1. Download the file https://drive.google.com/file/d/1pgcTalz8rAFWYwP8xYNmNB8uTk-OlAn4/view?usp=drivesdk
2. Extract to your computer desktop or adb folder
View attachment 4651279
3. Reboot your phone to fastboot
4. Go to your computer and connect the phone with computer
5. Open a command prompt and type
6. Fastboot devices if you phone detected in command prompt window it will show numbers of device like in picture
View attachment 4651278
7. now type [ fastboot flash recovery recovery.img] or you can do like this ( fastboot flash recovery and drag recovery file to command prompt) and hit enter
View attachment 4651277
8. now press volume+ and power at the same time until your device boot to TWRP
9. After successfully booted TWRP now flash View attachment 4651280 and wipe data
10. Enjoy your flashing
D . ROOT YOUR PHONE
1 .Donwload latest Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Put Magisk into external sd card because decryption is not for now
2 .Flash Magisk
3 .Restart your smartpphone
4 .Now set up you phone
5 .Done enjoy
telegram :- https://t.me/tulipofficial

I have read about some problems with ported (from whyred ?) twrp and MIUI 10 on RN6 pro,
but I could not remember where
so there are no problems ??

Perfect

perfect with MIUI 10 ?

phonepete said:
perfect with MIUI 10 ?
Click to expand...
Click to collapse
Yes

...

Great wanna try it..?

twrp is ok now

are there any possibility to re-lock?

hi! I was trying to unlock my bootloader but I have an error at 99% with a message in chinese that it says something like: "The phone has not been used for the specified time and cannot be unlock"
Someone has the same problem or knows the solution?
Very thanks

I have problems with this twrp.
When i enter in recovery it ask for a password to decrypt the data storage. I tried everything but i don't know how to decrypt, So i can't mount Internal and SD Partition and neither root my phone
I tried to wipe data, but even in this case i can't navigate into internal storage.
Should i wait for an official TWRP?

raexan said:
hi! I was trying to unlock my bootloader but I have an error at 99% with a message in chinese that it says something like: "The phone has not been used for the specified time and cannot be unlock"
Someone has the same problem or knows the solution?
Very thanks
Click to expand...
Click to collapse
You have to apply for unlock and then wait for 14 days.

Has anyone successfully unlock other LTE bands after root? I have the global version but it does not have LTE band 12 & 17 which are critical for AT&T

Can you please tell me if this TWRP edition can see the SD card ?
Thanks

Password required in mount operation
Just after entered TWRP is asking for a password to Decrypt Data.
Tried all password for my account with no success.
I am not able to actively root my phone.
Any suggestion?
Many thanks

toni.pace said:
Just after entered TWRP is asking for a password to Decrypt Data.
Tried all password for my account with no success.
I am not able to actively root my phone.
Any suggestion?
Many thanks
Click to expand...
Click to collapse
in that menu I think that you can press cancel and enter in the menu of recovery
Enviado desde mi Redmi Note 6 Pro mediante Tapatalk

same thing happened to me .. as I enter to the TWRP, I have being asked for the pin unlock password, which is not the one I have previously set on the miui. I rebooted to system, removed the pin protection and yet again it didn't helped with the TWRP asking the pass .. if I hit the cancel, I enter to the TWRP yet no any storage is mounted and can't do nothing further. So for a lot of us this guide is not 100% good.

clemenza011 said:
same thing happened to me .. …..
Click to expand...
Click to collapse
I was finally able to root the phone, but i don't know exacly how.
BTW
My TWRP is V.3.2.3 v3 Special Edition mod by Mr-r00t
In TWRP just click "Cancel" to password request, then you should be able to see the content of the Sdcard.
From there i flashed "Disable_Dm-Verity_ForceEncrypt_09.02.2018.zip" and "Magisk-v18.0(18000).zip"
Rebooted in system and did some setup in Magisk app
I did install also "Root checker basic"," Root Browser" , "Titanium Backup" from PlayStore.
In "Root checker basic" installed BusyBox too.
Finally root is working, and i was able to copy a new "Hosts" file in \system\etc, just to get rid of annoying ads .
Good luck

Right, I managed the same last eve *with the other recovery to be honest) .. root after magisk works, and tapatalk is clean after adaway was installed .. yet my data is encrypted and I cannot for instance do the full backup from the twrp. I am concerning format data, as I understood that it should remove the encryption, yet I am not sure would I have to flash something (ROM?) after I format the data, or I could just reboot to the system, as is?
magisk manager shows ticked 'preserve force encryption' and unticked 'preserve avb2.0/dm-verify', I suppose that such situation corresponds to the fact that I am encrypted, and I have flashed disable_dm_verity, just like being said.
also, our (RN6PRO) devices have activated anti-roll-back (mine arb index is 4) so there should be no much space for mistakes.

clemenza011 said:
Right, I managed the same last eve *with the other recovery to be honest) .. .
Click to expand...
Click to collapse
Sorry i cannot help with that question about format DATA , my skills are limited.
My Magix manager shows the same " ticked 'preserve force encryption' and unticked 'preserve avb2.0/dm-verify', "
I am ok with my phone now, and don't want the risk to loose everything or to be forced reinstall all.
I hope someone else could answer this question.
Have a nice day.

[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