Database Users

Unbrick method.

So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.

eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help

subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.

eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....

Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...

Very useful guide, I revived my soft - bricked Moto G

still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?

sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks

My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom

I solved this issue with twrp sideload.It worked great.

Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..

Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error

When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c

eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .

@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.

Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071​
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.

lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071​
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .

Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip

Where do i put the command in the 4th step?
Please help

[GUIDE] How to * Unlock * Flash TWRP * Root * OnePlus X [Including Oxygen 3.1.3]

Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________​
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps​
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X​
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.

Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess

I could try today evening... will update here.

@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..

Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.

I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly

Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.

CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/

Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.

Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.

CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...

Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.

mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted

Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!

Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here

mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit

CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD

Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0

ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.

@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/

[GUIDE] How to unlock your bootloader, install TWRP and gain root access

There doesn't seem to be a comprehensive guide on this, so I thought I would provide one.
READ THIS FIRST
DO NOT TAKE ANY OTA UPDATES!!!
Please consider the following:
Ask yourself these two questions: "Why do I want to unlock my bootloader? Why do I need root access?" If the answer to either one of those is "I don't know," don't do it. Both of these actions weaken the security of your phone, and there's no reason to do that if you're not sure why.
This guide is for the Droid Turbo, model XT1254. It is not for the Droid Turbo 2, and it is not for any phone that is not named Droid Turbo.
Standard XDA rules apply. I'm not responsible for anything you do, and neither is anyone else other than you.
I'm assuming that you are running a Windows PC. If you have a Mac, I can't help you. If you're running Linux, you shouldn't need help.
This method is not free. It costs $25 (USD). If that's not okay with you, don't do this.
Once your bootloader is unlocked, you CANNOT safely re-lock and unlock it again. See this thread for what happens when you try to do that: http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081#post65095391
Still here? Cool.
Section 0: Installing Firmware Version MCG24.251-5
1. Go to Settings -> About phone -> Build number. If it says SU4TL-44, SU4TL-49 or MCG24.251-5, skip to section 1 of this guide. If it says MCG24.251-5-5, you need to take an extra step to unlock your bootloader. I'll explain later. For now, just skip to section 1 of this guide. If it says anything else, keep reading.
Flashing MCG24.251-5 using this method will erase all of your data. Back up any important files/information before proceeding.
2. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
4. Download the MCG24.251-5 firmware package from here: https://www.androidfilehost.com/?fid=889764386195901169
5. Extract the contents of the MCG24.251-5 firmware package to the installation directory of Minimal ADB and Fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot on any 64-bit installation of Windows).
6. Power off your phone.
7. Hold down the volume down button and power on your phone. Release the volume down button when you see that the phone has booted into bootloader mode. You'll see a dead green android.
8. Plug the phone into your computer.
9. Open the Minimal ADB and Fastboot shortcut on your desktop. This will open a command prompt.
10. Type "fastboot devices" and press enter. If it displays your device's serial number, you're ready to go. If it displays nothing, your computer is not recognizing your device properly.
11. Navigate to the installation directory of Minimal ADB and Fastboot and double click on FlashAll.bat. This will flash MCG24.251-5 to your device and erase all of your data.
12. Use the power button to select Start in the bootloader menu to boot normally.
13. Set up your phone at least to the point where you can install apps if you want to.
For now, just try to ask someone nicely to help you out with this. I'll try to get this done before the end of the day.
Section 1: Unlocking the Bootloader
1. Download Sunshine from here: http://theroot.ninja/download.html
2. Move the apk file to a convenient location on your phone. If you downloaded it with your phone, it's in your downloads folder already, so leave it there.
3. Use any file browser on your phone to navigate to the folder that contains the Sunshine apk file. Tap on it to install it.
4. If a message comes up and says that you need to enable installation of apps from unknown sources, follow the instructions on that message to enable it.
5. Enable Wi-Fi on your phone if it is disabled. Even if you aren't connected to a Wi-Fi network, it still needs to be on.
6. !!!DO THIS STEP ONLY IF YOU'RE ON MCG24.251-5-5!!! Follow the instructions here to obtain temporary root: https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/. DO NOT perform the uninstall step.
7. Open your app drawer and start Sunshine.
8. Follow the instructions.
9. !!!FOR MCG24.251-5-5 ONLY!!! Sunshine will reboot your phone automatically, and it will go into a bootloop. This is normal. Don't panic. Hold down the volume down button until the phone goes into bootloader mode. Plug your phone into the computer, start Minimal ADB and Fastboot (see Section 0 for link if you didn't have to install it before this point), and enter the command fastboot oem config fsg-id "". This will disable the temporary root exploit. Reboot your phone normally, and everything should be happy again.
10. If, when your phone reboots, you see a "Warning: The bootloader is unlocked" message, you have successfully unlocked your bootloader. If you do not see this message, open Sunshine again and follow the directions again. If you're on MCG24.251-5-5, you'll have to gain and uninstall temproot again at the appropriate times.
Section 2: Installing TWRP
Team Win Recovery Project is arguably the most important tool to have on a bootloader-unlocked phone. This is how you install it:
1. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790. If you already did this in section 0, you don't have to do it again.
2. Download the latest TWRP .img file from here: https://www.androidfilehost.com/?w=files&flid=39562
NOTE: The TWRP file that you download should have a .img extension. Make sure you can see this. If you don't see .img at the end of the filename, Google how to make file extensions visible on your version of Windows and do it. If you do not do this, you may run into trouble later.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481. If you already did this in section 0, you don't have to do it again.
3. Rename the file that you downloaded in step 2 to TWRP.img
4. Copy TWRP.img to the directory that you installed Minimal ADB and Fastboot to. The default location on an installation of 64-bit Windows is C:\Program Files (x86)\Minimal ADB and Fastboot.
5. Turn off your phone.
6. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Poor little guy...
7. Plug your phone into your PC.
8. Double click on the Minimal ADB and Fastboot shortcut that's on your desktop. It will open a command prompt.
9. Type "fastboot devices" without quotes and press enter. If it gives you your phone's serial number, you're good to go. If it gives you nothing, your device is not detected. This can happen for several reasons, and I won't discuss them here. However, if you followed these directions and all of your hardware is functioning properly, you should be good to go.
10. Type "fastboot flash recovery TWRP.img" without quotes and press enter. It should tell you that the flash was successful. You might see some "not found" errors. These are normal and can be ignored.
11. Highlight "Recovery mode" on your phone using the volume up and down buttons.
12. Press the power button to boot into TWRP.
13. TWRP will boot, and it will ask you if you want to allow write access to the system partition. IT IS VERY IMPORTANT THAT YOU ALLOW THIS. Check the box that says to never ask this question again.
14. Select Reboot, followed by System to boot the phone normally.
Section 3: Gaining Root Access
If you intend to install a custom rom, these steps are not necessary. Custom roms almost always come with root access built in. Refer to the thread of your custom rom of choice for installation instructions.
If you do not want a custom rom, and you simply want root access on the stock Droid Turbo rom, continue reading.
1. If you are on the stock marshmallow rom, build MCG24.251-5 or higher, download the latest version of both Magisk and Magisk Manager to your phone: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
NOTE: You need to be on marshmallow to use Magisk to root your phone. The Magisk thread says it supports lollipop and higher, but it only supports lollipop for some stock Samsung roms. This does not apply to you. If you want to root your phone on lollipop, you'll need to use SuperSU. I won't go into that here because I don't think there is a lot of demand for it, but if you need help with that, reach out to someone here. It's not difficult.
2. Install Magisk Manager the same way you installed Sunshine.
3. Turn off your phone.
4. Hold the volume down button and press the power button to boot into bootloader mode. You should see a green android lying on his back with his chest open, and some information about your phone. Andy, what have they done to you?
5. Use the volume up and down buttons to highlight "Recovery mode."
6. Press the power button to select Recovery mode.
7. Select Install from the TWRP main menu.
8. Select the most recent version of Magisk (the .zip file, NOT the Magisk Manager .apk file) that you downloaded.
9. Swipe the bar at the bottom of the screen to flash this zip file.
10. When it finishes, select Wipe Cache/Dalvik and swipe the bar at the bottom of the screen.
11. Select Reboot System
Section 4: Passing Safetynet using Stock, Unrooted Marshmallow
If you are running stock marshmallow with an unlocked bootloader, you will fail safetynet verification (and be unable to use Android Pay). Installing Magisk is the only recommended method, as of this writing, to bypass this limitation. If you completed Section 3, you shouldn't have any trouble. Understand, however, that there is a constant game of cat and mouse going on between Google and Magisk's developer, so sometimes Google will update safetynet to beat Magisk. If that happens, wait for Magisk Manager to tell you that a new version of Magisk is available, and it will install the new version for you. That's your best bet for passing safetynet again.
If you really want to pass safetynet, but you really don't want to be rooted, you can disable root (Superuser access) in the Magisk Manager settings.
Section 5: Miscellaneous
Here are some links to stuff you can flash now that your bootloader is unlocked:
Official LineageOS 12.1 (Android 5.1.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3260253
Official LineageOS 13.0 (Android 6.0.1): http://forum.xda-developers.com/dro.../moto-maxx-xt1225-droid-turbo-xt1254-t3353298
AOSPExtended (Android 7.X): https://forum.xda-developers.com/moto-maxx/general/rom-aospextended-rom-v3-1-t3555361
Unofficial LineageOS 14.1 (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-t3494646
crDroid (Android 7.X): http://forum.xda-developers.com/moto-maxx/development/rom-crdroid-android-t3491257
Android Open Kang Project (Android 7.X): http://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Resurrection Remix (a great LineageOS-based rom, Android 5.1.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-5-5-5-t3197643
Resurrection Remix (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3316232
Resurrection Remix (Android 7.X): https://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109
Computerfreek274's optimized stock rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
MoKee Open Source Project (Android 6.0.1): http://forum.xda-developers.com/moto-maxx/development/rom-mokee-opensource-project-t3188936
Bliss Rom (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-bliss-rom-6-4-team-bliss-t3422937
Android Open Kang Project (Android 6.0.1): http://forum.xda-developers.com/droid-turbo/development/rom-android-kang-project-t3422456
Android Open Kang Project (Android 7.X): https://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629
Change the splash screen (the bootloader unlocked warning message) that you see when you first start your phone: http://forum.xda-developers.com/dro...custom-boot-logos-accepting-requests-t3262873
Xposed framework and installer (make sure to use the sdk22-arm version if you're running a lollipop rom, sdk23-arm if you're running marshmallow. Not available for nougat yet.): http://forum.xda-developers.com/showthread.php?t=3034811
Alternative Material Design Xposed Installer that provides additional features: http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Pon-3 Audio Mod (modified and improved Viper4Android. It makes your phone sound better.): http://forum.xda-developers.com/showthread.php?t=2530976
Other modded Viper4Android versions that are better than PON-3: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Theme your TWRP with different colors: http://forum.xda-developers.com/android/themes/theme-twrp-3-0-0-0-dark-stock-colors-t3310235
More TWRP themes: http://forum.xda-developers.com/showpost.php?p=66276401&postcount=2889
Android N Emojis: http://android.wonderhowto.com/how-to/get-android-nougats-all-new-emojis-right-now-0170328/
Section 6: Troubleshooting
Issue: When you try to boot TWRP, you see a screen that says "no command." TWRP does not boot.
Solution: The screen you are seeing is the stock Droid Turbo recovery menu (the menu that you're trying to replace with TWRP). If you see this after flashing TWRP, one of two things happened:
-You did not boot into the recovery menu immediately after flashing TWRP, and it was therefore replaced by the stock recovery menu.
-When you flashed TWRP, the process did not complete successfully.
The solution to both of these problems is to repeat section 2 and follow the instructions more carefully.
Issue: When TWRP asked you if you wanted to allow write access to the system partition, you selected no. Now you cannot flash anything.
Solution: At the main TWRP menu, select Mount. Uncheck the box that says "Mount system partition as read-only."
Issue: Fastboot says "cannot load TWRP.img" when you try to flash it.
Solution: This error indicates that Fastboot cannot find TWRP.img. The most common source of this problem is that you did not make your file extensions visible, and so when you renamed the TWRP file to TWRP.img, you actually renamed it to TWRP.img.img (including the hidden .img file extension that you didn't realize was there). Google how to enable file extensions on your version of Windows, follow those instructions, and if this is the issue you will see it.

nice write up - will follow these when I get my phone tomorrow.

worked!
Just tried this. Worked amazingly, and exactly as you described! Thanks!!

Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.

I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?

22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk

SpyderPride said:
So you can't boot into twrp?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Nope, no matter what I do, it stays on that screen. I have to reboot and then it returns to normal. I've followed all of the steps twice now and got the same results each time. I do have the phone still plugged into the computer charging.

s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before

5.1
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?

CatMan8 said:
HI, I am on SU3TL-39, android 5.1, system 23.11.39.quark_verizon.verizon.en.US vzw.
I have been holding off on an OTA that my phone keeps prompting me to do, should I now take that OTA?
Click to expand...
Click to collapse
if u want an unlocked bootloader then take the OTA

22e said:
I keep getting a "no command" screen after step 6 in section 3. Everything else worked perfect. Any ideas?
Click to expand...
Click to collapse
The screen that you're seeing is the stock Droid Turbo recovery menu, which means that TWRP is not getting flashed. What result does it give you after section 2, step 10?

s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Yeah, I did the exact same thing. The MDK bootloader is golden. I broke my phone once and almost cried. Luckily, I was able to get another MDK on Swappa. The seller wasn't even charging extra for it! He/she must not have known what they had.
As for Viper4Android, I've added a link to section 4 that you might want to look at.

iceblitz4 said:
https://www.androidfilehost.com/?w=files&flid=44797 try this just flash it through TWRP its basically viper4android i've used it before
Click to expand...
Click to collapse
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.

s4shield said:
Thanks! If I can only remove all the brony stuff from the app. Lol. I guess I can change the icon. I have to pretend at least that I don't have a mangina when I'm with my friends. No seriously this post made my day. I thought I was stuck without viper on my phone.
Click to expand...
Click to collapse
Such is life. Sometimes if you want the wubz, you gotta take the brony.

TheSt33v said:
Such is life. Sometimes if you want the wubz, you gotta take the brony.
Click to expand...
Click to collapse
Ha ha ha!

successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.

Awesome post. It definitely will come in handy. One question, at what point should I create a backup image via twrp? Is it before section 3 step 7?

s4shield said:
Thanks just got this phone yesterday. I came from a Verizon s4 with a unlockable bootloader so now running cm on a phone is really awesome for me. Although I was concerned about the $25. I love paying people for there work but it seemed different and I was expecting the app to be a scam or something. However everything went okay. I wish there was a way to get viper4android working. Does anyone know about that? I thought installing cm would have fixed the issue. Anyways thanks a lot. I wonder if I can change my username. Lol.
Click to expand...
Click to collapse
Download the file www.viperforandroid.com install goto menu set as expert ui under ui setting open viper4android check on click box click appropriate sound changer so it sounds right to u I suggest doing on headphones than use thoose settings as base settings for phone bt ect.. The the real good sound comes in under conolover files you must download impulse response files or. Irs files dfx_pro_surround_2.irs, Dolby,, dfx ect. After u download you unzip and using a file manager find unzipped file and goto sd card u will see viper4android folder inside that folder you will see 2 other folders one being kernel place irs files in kernel folder. Now when you click impulse response you will have the audio producing files. Like Dolby digital cinema, stereo, HD. Ect there are hundreds I'll post my walk though install video

can you help me sir
my friend have verizon moto droid ultra xt1254 and he already give it to me
and i got this phone with google account privacy and he forgot last email in this device, so i cant finished setup wizard and go to home screen
this device locked bootloader so i cant do something to
what should i can do?

jco23 said:
successful for me, thanks!
to comment on @22e issue, I had the same problem. i was able to correct it by copying the TWRP.img file to the same directory as the minimal adb fastboot files were installed in.
also, a shortcut after flashing TWRP is to type "fastboot reboot-bootloader". this will return back to bootloader rather than having to reboot, power off, and then press the buttons to get to bootloader.
hope this helps.
Click to expand...
Click to collapse
Thanks for the help.
After I got stuck, I downloaded and installed KingRoot. It successfully rooted my phone. I downloaded two different root checkers and they confirmed. Everything works correctly within Rom Toolbox Pro now, I can remove apps (stupid NFL mobile, Amazon, etc). My software status says "Modified". I did not need to format or anything like that. Is that normal? My only issues are with XBlast Tools and SuperSU, when I change a setting in XBlast, it does NOT get updated. Even after a reboot. In SuperSU cannot update binaries for some reason.
I cannot post outside links for screen shots yet.

[Guide][How-To] Root Android 8 Oreo - Pixel (XL) + SafetyNet Pass

This is how to root with SuperSU and includes flashing SuperSU Hide for Android O
Requirements:
Unlocked BootLoader
Latest fastbook/adb drivers (https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240)
Android O image (https://developer.android.com/about/versions/o/download.html#top)
SuperSU 2.82 SR3 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133)
Modded Version of the TWRP that works for Pixel/XL DP4/O (https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896)
If you want SuperSU Hide for safety net passing (as of (8/21/2017 this is working) for Android Pay, Pokemon GO, Snapchat download SuperSU Lite from here (https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855)
The How to part
Flash the Android O factory image on your device
Let the divice boot and go through setup and i advise you set a lockscreen method (Pin, Pattern, Password whatever you want but this will allow TWRP to decrypt your data more consistently) then reboot to bootloader
boot into the TWRP linked above
Go to "Wipe" select "Advanced wipe" check just "internal storage" and swipe to wipe
your device's internal storage should now be accessible via your PC/Mac/Linux so copy of the linked SuperSU SR3 we downloaded from above
Back to TWRP and the device, flash the SuperSU you copied over
let it finish then swipe to reboot to system (do not install the TWRP installer app it asks you to install before the reboot)
let the system boot up and check to make sure supersu is there
reboot back to bootloader and boot into the TWRP
Enter your lockscreen login (Pattern will show up if you used a pattern otherwise type in you password or pin when it asked for password)
copy the supersu hide lite from your PC/Mac/Linux to the internal storage of the device
flash it in twrp then swipe to reboot to system
Finally when it boots you should have supersu and SUHide installed!
Few Notes:
-It is very important to know that we are not flashing TWRP to our system when in fastboot/bootloader. If you're coming from an older device or just new to the Pixel in general this will be kinda weird to you I'm sure. The reason we do no do this is (long story short) A/B partition devices like the Pixel's are a whole new ball game and there is still development being done to get traditional methods of installing aftermarket recoveries working. But till then we have to boot into things so the change is temporary and does not alter the device's recovery partition.
-How SuperSU Hide works is pretty self explanatory but if you're like me, the whole safety net thing is annoying and i haven't felt like reading about it. So using the "suhide" app you now have, you want to make sure root is hidden from the apps that watch for it and stop themselves from running is they see root (Snapchat, Android Pay and Pokemon GO are all examples of these apps)
the "About" tab in the "suhide" app is very helpful
Old instructions for Android O DPs
Early reports say boot-to-root (the method covered here) works for DP4
Rooting DP1-4 is very easy.
Make sure bootloader is unlocked
Make sure Fastboot/adb drivers are fully up to date. (Follow this guide to make sure: https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240 )
Download dp1-3 (https://developer.android.com/preview/download.html)
Download SuperSU 2.82 SR 1 for Pixel (or pixel xl) (https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481) [Updated to new fixed version that repaird system mounting issue]
Just flash Dev Preview like normal
boot into system and setup android
Reboot to bootloader
Exact the downloaded supersu
Reboot to bootloader
open a cmd in the extracted supersu location and type
Code:
fastboot boot boot-to-root.img
it will take about 7 minutes to boot but when it does you should have root
Original Instructions for rooting DP1
So after a few weeks of being without root on Android O for the Pixel user Sachi315 discovered how to get root on O by installing 7.1.2 on one slot and android O on the other. This allows Android O to fully boot after installing SuperSU. I wont go into the details of how it works because thus far its all speculation on my part and hopefully someone out there who knows more about these new partitions could better explain it. But for now I'm just going to show you how to do it.
Requirements
+Download 7.1.2 for your Pixel (XL)
-----N2G47E (https://developers.google.com/android/images)
+Download Android O for your Pixel (XL)
-----(https://developer.android.com/preview/download.html)
+SuperSU RS4 2.79 Extra Delay
-----(https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip)
+TWRP RC1 bootable image & RC2 Flashable zip
-----For Pixel (https://dl.twrp.me/sailfish/)
-----For Pixel XL (https://dl.twrp.me/marlin/)
+Backup everything on you device, it will be purged
-----Make sure you have the latest fastboot binaries (I HIGHLY recomend you set this up manually. How to do so can be found in my tutorial here)
+Unlocked bootloader
To make sure you have the latest fastboot binaries press the windows key and type cmd. In the command line type "fastboot" This should return you get. Showing all the available fastboot commands including the new "--slot" commands. If this list has the options --set-active[=<slot>], --slot <slot> listed towards the bottom then you're all ready to move on. (see screenshot for list of other commands you should see)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Editing the flash-all.bat from your downloaded 7.1.2 and android o factory images
-Extract both to your working folder
-Find the "flash-all.bat" in the extracted 7.1.2 (N2G47E) right click and select "Edit"
-At this point we are going to clean the flash all up a bit. Its not a necessity but if you don't add some much needed line breaks it can get messy and confusing.
-Below i have a screen shot of what mine looks like cleaned up. Just press enter in the places i did. *Adding the line breaks does NOT mess with the code at all*
-----Toward the end of the commands you will see i added '--skip-reboot" between "update" and "image-sailfish-n2g47e.zip" This command makes it to where the device will not restart after the flash-all is finished. It is important you add this in the same place.
​-Now that we have this cleaned up, go ahead and save it really quick before we start adding to it.
-We are going to add a few "--slot" commands to it so it only installs to one slot. Below you can see what mine looks like after i added the commands. Match yours to mine (highlighted by red boxes)
-If you are on marlin, your image and zip names will be different but it's the same principal
​-after you add what i have above, save the flash-all.bat and close out of it.
Now we move over to the android o dev preview
-Open the extracted dev preview and right click on its flash-all.bat. Select "Edit"
-We are basically doing the exact same thing in this one BUT instead of the new commands being "slot _a" they will be "slot _b" (See below for the difference and we are still adding the "--skip-reboot" command)
​-Once your changes have been made in this flash-all.bat, save and close out.
Flashing the Images
Go ahead and get your Pixel into bootloader mode and plug it in.
before we start flashing we are going to clean the device up. This step will erase everything on the device.
Go into command prompt and type:
Code:
fastboot --slot _a -w
let it finish its thing then type
Code:
fastboot --slot _b -w
Device is cleaned. Now staying in bootloader type
Code:
fastboot --set-active=_b
then
Code:
fastboot reboot-bootloader
Now close out of this command prompt and run the flash-all.bat from the android o dev preview folder.
Let it do its thing and after its done, it should be left in bootloader.
now run the flash-all.bat from the 7.1.2 image folder you have.
Same thing; let it run its course and finish up.
Now you should be still in bootloader.
type in cmd
Code:
fastboot --set-active=_a
now type
Code:
fastboot reboot-bootloader
when it comes back up look at the phone and make sure is says the slot is "a" if it does, you're good to move on!
Installing TWRP and Root
From here; boot into TWRP (RC1)
-Make sure youre in slot A by going to "Reboot" then looking at the bottom (It should be slot A at this point, if its not something wasnt done correctly in the above steps)
+At this point i had the issue that my pixel would show up under "This PC" in explorer and was recognized by adb BUT none of the internal storage could be interacted with via my PC (this includes adb commands) so i couldnt get TWRP RC2 or SuperSU SR4 2.79 Extra Delay on the device to be flashed.
-To fix this: got to wipe>advanced wipe>check internal storage ONLY then wipe this partition.
-Unplug your phone and plug it back in and Windows Explorer should be able to work with the internal storage now.
-Now transfer TWRP RC2 and SuperSU sr4 2.79 Extra Delay to your Pixel
-From TWRP on your device, flash just TWRP RC2 for now. After it is installed, switch to slot b in TWRP. Then reboot to recovery.
-When TWRP comes back up, check to make sure youre in slot B still.
-If you are, now flash SuperSU SR4 2.79 Extra Delay.
-Now reboot.
-It should boot into android o, walk through setup and make sure supersu is installed.
-If it is, Congratulations you have rooted android O on your Pixel!
This method has was discovered by @Sachi315 (here)
Make sure you give him tons of thanks for getting the method up and running!
Im storing this here for my own sake testing wise please ignore https://forum.xda-developers.com/showpost.php?p=72604085&postcount=10323
Off Topic is welcome as long as its still Pixel/Root/TWRP/Development/Questions but back and forth bickering will be and should be reported.

finally, thx for this guide! will give it a try and feedback. BTW, can I share this guide with my native language? source url and your ID will be declaimed, of course.

can it be done on a locked BL?
like EE (uk) or Verizon?

y2grae said:
can it be done on a locked BL?
like EE (uk) or Verizon?
Click to expand...
Click to collapse
Nope, nor would you want to.

Queentus said:
finally, thx for this guide! will give it a try and feedback. BTW, can I share this guide with my native language? source url and your ID will be declaimed, of course.
Click to expand...
Click to collapse
As long as credit is given, by all means!!!

bobby janow said:
Nope, nor would you want to.
Click to expand...
Click to collapse
Why is that? Just curious.

bobby janow said:
Nope, nor would you want to.
Click to expand...
Click to collapse
awakenedwithin said:
Why is that? Just curious.
Click to expand...
Click to collapse
Yes I too am curious

awakenedwithin said:
Why is that? Just curious.
Click to expand...
Click to collapse
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.

bobby janow said:
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.
Click to expand...
Click to collapse
Oh I miss understood what you were trying to say.
Right. I should probably put unlocked bt as a requirement

eqbirvin said:
Oh I miss understood what you were trying to say.
Right. I should probably put unlocked bt as a requirement
Click to expand...
Click to collapse
You can, sure. But hopefully your walk through is read before attempting to do this and it clearly states to boot into TWRP. That's impossible with a locked bootloader.

bobby janow said:
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.
Click to expand...
Click to collapse
Thank you for the reply!

Thanks for this. I just got a sailfish this evening. I should be trying this out tomorrow. :good:

sheesh.....becoming harder and harder to root now.....yikes

mikeprius said:
sheesh.....becoming harder and harder to root now.....yikes
Click to expand...
Click to collapse
Dev previews are always a bear at first, I do hope this doesn't become the norm though. Pixel doesn't make it any easier haha

Thanks
@eqbirvin
I successfully rooted my new sailfish with o preview following your instructions. :highfive:
One place I got stuck was not knowing that there is no recovery partition in Pixel. I tried
fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-sailfish.img and obviously failed.
A little bit of searching led me to the right command
fastboot flash boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Thank you for decoding the rather cryptic post https://forum.xda-developers.com/showpost.php?p=71865004&postcount=1266 from @Sachi315 and creating a step-by-step process that works. :good::good::good:

Is that fastboot boot twrp or fastboot flash boot twrp?
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
Is that fastboot boot twrp or fastboot flash boot twrp?
Click to expand...
Click to collapse
Boot TWRP.img, flash doesn't work on pixels

Do you always let the phone boot up normally after stock, then go into bootloader and boot TWRP, the flash the TWRP zip ?
Afterwards, do you reboot TWRP into recovery again then stock, or just flash the .zip of TWRP then go right into stock ?
The process for this has been more confusing than the Nexus b/c there are slots a and b.

eqbirvin said:
Boot TWRP.img, flash doesn't work on pixels
Click to expand...
Click to collapse
That's what I thought. Just correcting the above post is all.

mikeprius said:
Do you always let the phone boot up normally after stock, then go into bootloader and boot TWRP, the flash the TWRP zip ?
Afterwards, do you reboot TWRP into recovery again then stock, or just flash the .zip of TWRP then go right into stock ?
The process for this has been more confusing than the Nexus b/c there are slots a and b.
Click to expand...
Click to collapse
Don't boot into system after 7.1.2 flash or Android O flash. Just boot into TWRP, flash the TWRP rc2 (after dealing with internal storage issue) change to slot b (while still in TWRP) then reboot to recovery and make sure you are in slot b again. Finally flash SuperSU package.
Ugh I know. I love the pixel but is slot/partition change is a headache haha

Unable to Boot TWRP in Recovery mode, bootloop issues

Hello guys, I'm a beginner in this flashing stuff. I have watched youtube over a guy flashing Android 10 on his Samsung note 3. I carefully took his steps and i make sure that my model is compatible with said ROM, Mine is Samsung note 3 lte (N9005), Snapdragon. The issues that i am currently having is on flashing TWRP on my Samsung Note 3, because it won't boot on recovery mode despite i press the exact button as the Video describe, it just boots in recovery and then restarted on the same logo boot repeatedly. I have tried flashing LineAgeOs using the tutorial provided by LineAgeOs team and again, i make sure that the rom is fully compatible and still end up same result. Please help me on this issue. Thank you very much for giving your time reading my problems

Please describe your issue again with more details.

From you're post, it seems as though you are having issues with TWRP. Below I will give you a full tutorial on how to get TWRP up and running for your specific device. Do give this a go, as I have done the research for your specific model, and it should work just fine.
First things first, unlock your devices bootloader. You may not have done this correctly, so if it is possbile to boot into android, then try this:
How to unlock Bootloader on Samsung Galaxy Note 3 | Softstribe
Unlocking bootloader in Samsung Note 3 made easy and you can simply enable developers mode where you can perform OEM unlock.
softstribe.com
If you're bootloader is already unlocked, then proceed.
Now that the bootloader in unlocked, we need to install TWRP for your specific device. Your device is the N9005, which is the international snapdragon model. It's codename is hlte, or hlte*. For TWRP, it is also categorised as the Europe/American model (hltexx).
For flashing TWRP correctly to a samsung device, we will need odin. Odin is a flashing software for samsung devices.
Download Odin.zip from here:
Samsung Odin - Root Android download page for one click root
Samsung odin download - Root android and oneclickroot for flash / install custom ROM with one click root method
odindownload.com
(Download the latest version (v13.4.1 at the time of writing this)
Now, extract Odin.
Once we have Odin downloaded, we will need to install the correct usb drivers for Samsung phones.
Download the file below, then extract the zip and run the installer:
Samsung_USB_Driver_v1.7.31.0
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now that odin and the drivers are ready, we need the actual twrp image which we need to flash to our device.
Here is the link, download the latest .img.tar file (3.6.1_9-0 at the time of writing):
Download TWRP for hlte
Download TWRP Open Recovery for hlte
dl.twrp.me
Do not download the normal .img file, as that cannot be flashed via odin.
Now that we're past the prerequisites, we need to actually flash twrp to your device. To begin, we must put your note 3 into download mode. To enter download mode, power off your phone completely and then press Power+Home+Vol Down at the same time and keep these three buttons pressed until your phone shows a "download mode, do not power off target!!!" screen, you can follow this video tutorial below:
Now that we are in download mode on the device, we need to get back to our computer and configure odin to flash twrp. First things first, open odin. Now, connect your phone to the computer. You should see a little "COM-" show up in one of the empty boxes in the top row under the word "ID:COM". This is good, it means that your pc successfully recognises your device.
Now, go to the options tab on the left side, makse sure that repartition is UNCHECKED. Now, click on the "AP" button, and navigate to and select the TWRP.img.tar file that you downloaded earlier. After you have selected it, click on start at the bottom right. Now it will begin to flash twrp, which should not take long. Make sure that you do not disconnect the device while flashing, wait for the phone to complete. Once it is done, the phone will reboot.
Now, just remove the battery, then put it back in. To enter TWRP recovery, keep Power+Home+Vol Up pressed, then once you see the samsung boot logo upon the phone powering on, let go of power, but keep home and volume up pressed.
Congrats! You've just flashed TWRP to your device, amazing!
Now you can go and look for custom roms to flash to your device. Since your model is the N9005, look for hlte/hlte* roms, don't use any roms if they don't support the hlte/hlte* variant.

Alright, now since you have mentioned that you want to use lineage os, here's a guide for that too.
So currently, it is recommended to use android 11 lineage os nightly builds as they are stable and official, so they should not have any bugs. So unfortunately, I cannot recommend installing lineage os android 10, as you had originally wanted, though the installation process for that will be somewhat similar. It is still not recommended to use old or unofficial builds due to bugs and lack of security updates.
First, we need to download lineage os for this device onto our pc, here's the link to the latest nightly build:
https://mirrorbits.lineageos.org/full/hlte/20220319/lineage-18.1-20220319-nightly-hlte-signed.zip
Next we need to download a GApps package for google play functionality. OpenGApps is recommended as it is open source, secure and reliable, usually with no bugs. I recommend using the nano package instead of pico if your device can handle it (your's can handle it just fine), as it contains google play functionality, and some extra google features which cannot be downloaded from google play. Here is the link to the nano package for your device (only for android 11 roms):
https://sourceforge.net/projects/opengapps/files/arm/20220215/open_gapps-arm-11.0-nano-20220215.zip/download?use_mirror=udomain&r=&use_mirror=autoselect
Now, if you want to get your device play protect certified, you will also need to download magisk for rooting, and magisk modules (so that you can download netflix and use banking apps etc.), but that is something you can do later on, and you can find any tutorial online for this.
Once the download is complete, move the lineage and opengapps .zip files to an sd card and insert it into the phone. Enter TWRP, go to wipe and click on Advanced. From here, wipe System+Data+Cache+Dalvik/ART Cache. Your files such as photos and media will not be wiped.
Next, go back to the TWRP main menu and select install. Click the select storage button at the bottom left and click on Micro SD Card. Now, click on the lineage os zip file, then click on the Add Zips to Queue button and select the opengapps zip file, then click install. This will take some time, do not interrupt it. Once it is complete, you can reboot the phone. The first reboot will take some time, and the first boot may be slow, after setting up your device, make sure to reboot it at least once.
Congrats, you've just installed a custom rom with google play functionality via TWRP!
Unfortunately, sometimes there are issues. If you still cannot get into lineage os despite waiting at least 10 minutes on the boot screen, then follow these steps below:
The lineage team says that booting issues may be due to incompatible recoveries, this means that we will have to use lineageos's own recovery to flash the rom.
For this, download the lineage os recovery.img from here:
https://mirrorbits.lineageos.org/recovery/hlte/20220319/lineage-18.1-20220319-recovery-hlte.img
Now copy this image file to your sd card and insert it into the phone.
Enter TWRP. First of all, click on wipe, then click on advanced and select System+Data+Cache+Dalvik/ART Cache and wipe. Now, go back to the main menu and click install. At the bottom right or left, there will be a button to "Install Image". Click on that button, and select the lineage recovery zip file and install it. Now go back to the main menu and click on the reboot button, then click on reboot to recovery.
Now you will boot into the lineage os recovery, from here you can install lineage os and the gapps zip files. Here is a tutorial:
This tutorial is for a oneplus phone, but it will be the same process on your samsung device.
Once it is complete, you can restart the device. If you would like TWRP back after flashing, just follow the steps from my first post and use odin to flash the twrp file again. I recommend that after installing lineage os, flash twrp again, as twrp recovery is much better than lineage recovery, and you dont need lineage recovery after installing lineage os.

If I helped you out, please mark my post as the solution, Thanks!

PhotonIce said:
If I helped you out, please mark my post as the solution, Thanks!
Click to expand...
Click to collapse
I did exactly with all your instructions. The end result is still the same that it won't boot TWRP after flashing, I don't really understand what the heck is wrong with my Samsung Note 3 Hlte. However i did try again with Lineageos Recovery, heck same thing too! This is really frustracting man, it just restarted itself and goes into normal boot.

LeEpic69 said:
I did exactly with all your instructions. The end result is still the same that it won't boot TWRP after flashing, I don't really understand what the heck is wrong with my Samsung Note 3 Hlte. However i did try again with Lineageos Recovery, heck same thing too! This is really frustracting man, it just restarted itself and goes into normal boot.
Click to expand...
Click to collapse
Did you follow my instructions from the beginning, using the files I linked, instead of your own?
How did you even try lineage recovery if you can't boot into TWRP? You need to boot into TWRP to flash lineage recovery..
HECK, how did you even flash lineage os if you can't boot into twrp???
Please answer these questions, as it is literally impossbile to do what your doing without entering twrp.
Just follow my instructions step by step, using only the files I linked, then tell us what happens.
I think your problem is that you aren't even entering recovery mode. You need to keep Power+Home+Volume Up pressed, then once the samsung logo appears, wait for 2 seconds and let go of power, without letting go of home or volume up. Now keep home and volume up pressed, eventually you will boot into twrp.
If you can't get into twrp, it means that you didn't flash it correctly, in which case make sure that your bootloader is unlocked.
It is also possible that your devices buttons or broken or something, in that case, download platform tools from here:
https://magiskupdate.com/wp-content/uploads/2021/12/platform-tools_r31.0.3-windows.zip/
Next, download and install adb and fastboot drivers from here:
Download in progress... - My USB Drivers
Preparing your download... Please wait...! Facing issues downloading the file or the download link is broken? You can report us here.
myusbdrivers.com
Install the drivers, then reboot. After that, extract platform tools and open the folder. Note the location of the folder (e.g. C:\Users\Name\Downloads\platform-tools). Now open a command prompt window (cmd), then type:
cd location of platform tools folder here
e.g.
cd C:\Users\Name\Downloads\platform-tools
Now, boot your phone into download mode (power+home+vol down), then connect it to the pc. Type:
adb reboot recovery
and
fastboot reboot recovery
This will force your device to boot into recovery, if your device still doesn't boot into twrp, then you have incorrectly flashed twrp to your device. If that's the case, please carefully follow my instructions from the first post, using my linked files only.

PhotonIce said:
Did you follow my instructions from the beginning, using the files I linked, instead of your own?
How did you even try lineage recovery if you can't boot into TWRP? You need to boot into TWRP to flash lineage recovery..
HECK, how did you even flash lineage os if you can't boot into twrp???
Please answer these questions, as it is literally impossbile to do what your doing without entering twrp.
Just follow my instructions step by step, using only the files I linked, then tell us what happens.
I think your problem is that you aren't even entering recovery mode. You need to keep Power+Home+Volume Up pressed, then once the samsung logo appears, wait for 2 seconds and let go of power, without letting go of home or volume up. Now keep home and volume up pressed, eventually you will boot into twrp.
If you can't get into twrp, it means that you didn't flash it correctly, in which case make sure that your bootloader is unlocked.
It is also possible that your devices buttons or broken or something, in that case, download platform tools from here:
https://magiskupdate.com/wp-content/uploads/2021/12/platform-tools_r31.0.3-windows.zip/
Next, download and install adb and fastboot drivers from here:
Download in progress... - My USB Drivers
Preparing your download... Please wait...! Facing issues downloading the file or the download link is broken? You can report us here.
myusbdrivers.com
Install the drivers, then reboot. After that, extract platform tools and open the folder. Note the location of the folder (e.g. C:\Users\Name\Downloads\platform-tools). Now open a command prompt window (cmd), then type:
cd location of platform tools folder here
e.g.
cd C:\Users\Name\Downloads\platform-tools
Now, boot your phone into download mode (power+home+vol down), then connect it to the pc. Type:
adb reboot recovery
and
fastboot reboot recovery
This will force your device to boot into recovery, if your device still doesn't boot into twrp, then you have incorrectly flashed twrp to your device. If that's the case, please carefully follow my instructions from the first post, using my linked files only.
Click to expand...
Click to collapse
I did follow your instructions using your own files that you provided for me. I did press Power + Home + volume up exactly as you told me to and let go of power button and keep pressing Volume up and Home, It just won't boot correctly into Twrp and restarted itself. There is alternative than using TWRP which is Lineageos Recovery os, i flashed that on my Samsung Note 3 HLTE, but it also don't work as well. However the link you sent to me right now is broken. Mind sending new one?

i forgot to mention one thing, i already unlocked the bootloader on Devs setting by turning on USB Debugging. There is no saying about bootloader option. I'm 100% sure i am doing it correctly. I downloaded literally everything from you and did as the instruction told. Even when i keep pressing Home + Volume up, it goes into bootloop without any successful attempt into booting twrp correctly and once i let go of Home + volume up button will boot my Samsung note 3 hlte into Normal boot and work as normal.

there should be an oem unlocking option in developer options. you need to select that, then reboot into downlaod mode and confirm to unlock your bootloader. To check it if it is unlocked, boot into download mode and send a picture of the text which it shows at the top right here on this forum and ill be able to confirm it for you.

N9005 does not have a locked bootloader .
Check its actually a N9005

PhotonIce said:
there should be an oem unlocking option in developer options. you need to select that, then reboot into downlaod mode and confirm to unlock your bootloader. To check it if it is unlocked, boot into download mode and send a picture of the text which it shows at the top right here on this forum and ill be able to confirm it for you.
Click to expand...
Click to collapse
You can see the video for the devs option, there is only usb debugging, i turn it off so that you can notice it and turn it back on in the video. You can try look at the download mode picture too. Let me know if i am doing anything wrong. Anyways the SDK Platform tool link you sent me is broken bro, i haven't try that solution yet.

JJEgan said:
N9005 does not have a locked bootloader .
Check its actually a N9005
Click to expand...
Click to collapse
It is N9005 my bro, I checked the spec with CPUZ and also reFlashed with Stock ROM N9005 with same Country region just for sure and it works fine. After i flash the stock rom, it can boot into recovery mode with no issues. However, with TWRP... It just won't work... I don't know why...

Will an older TWRP 2.8.70 etc flash , it could then upgrade TWRP .

JJEgan said:
Will an older TWRP 2.8.70 etc flash , it could then upgrade TWRP .
Click to expand...
Click to collapse
I'll try flashing Old twrp version and soon update about it.

Okay. it seem to be work out. But i realised that my Samsung note 3 hlte lcd screen is not original... So is this the reason why i can't flash custom rom? Or is there any alternative that may help me flash any good custom rom other than stock?

LeEpic69 said:
Okay. it seem to be work out. But i realised that my Samsung note 3 hlte lcd screen is not original... So is this the reason why i can't flash custom rom? Or is there any alternative that may help me flash any good custom rom other than stock?
Click to expand...
Click to collapse
Changed parts doesnt affect the installation of a custom rom. What issue are you encountering, you said that it worked out..? Just use twrp to wipe system+data+cache+dalvik, then flash acustom rom which is compatible with the hlte

PhotonIce said:
Changed parts doesnt affect the installation of a custom rom. What issue are you encountering, you said that it worked out..? Just use twrp to wipe system+data+cache+dalvik, then flash acustom rom which is compatible with the hlte
Click to expand...
Click to collapse
Twrp 2.8.70 is too old to read modern custom rom, it seem that i can't flash Lineageos 18.1 at all. That's what i mean, although Android 7.1 Lineageos seem to work out on my samsung note 3 hlte

flash 2.8.70, then install a 3.3x image via twrp's "install image" option in the install menu