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/

[TWRP & ROOT] Ticwatch E/S & Unroot Instructions for Updates - v003

{
"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"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!​
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!

You're the best! I'm gonna try as soon as I can, and let you know.

Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?

Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.

Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.

Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.

Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.

TWRP is now persistent! Check the updated guide

Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer

Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.

EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.

Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?

elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.

Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!

elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)

EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!

Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol

hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.

[Help] Fastboot mode missing?

I have A2017G, came with MM. I unlocked the bootloader, flashed TWRP and rooted, then flashed Nougat B04 and the corresponding B04 boot.img (was that necessary?)...
IIRC, TWRP came up once, but was then replaced with the stock recovery. I went to flash TWRP again, but the bootloader seems screwy. I get this screen for a few seconds:
{
"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"
}
If I touch the volume in time, this comes up:
But if I select fastboot, it just goes back to the first screen, then boots up after a few seconds. ADB shows no fastboot device on either of these screens. Hours of googling has gotten me nowhere...
The stock recovery will let me sideload a zip, but I gather it's no help with a img. OEM unlocking in developer options is greyed out; stuck on.

Select Fastboot and if the first screen comes again press the power button to continue and it wait it should boot itself to fastboot.
Or activate adb in the developers settings and type ADB reboot fastboot in ADB on Windows or Linux

I ended up with this too after trying to flash a custom rom, my just kept cycling around and around. I could not access any recovery.
I rescued mine from this point using the Miflash app and an edl package.
"DM verity enforcing" is what you need disable if you can get back to twrp. (Nfound has a twrp with all your needs covered)
Or try Voenix suggestion
I hope this helps
Edit: this is my rescue guide
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700

Kimmoth said:
I have A2017G, came with MM. I unlocked the bootloader, flashed TWRP and rooted, then flashed Nougat B04 and the corresponding B04 boot.img (was that necessary?)...
IIRC, TWRP came up once, but was then replaced with the stock recovery. I went to flash TWRP again, but the bootloader seems screwy. I get this screen for a few seconds:
If I touch the volume in time, this comes up:
But if I select fastboot, it just goes back to the first screen, then boots up after a few seconds. ADB shows no fastboot device on either of these screens. Hours of googling has gotten me nowhere...
The stock recovery will let me sideload a zip, but I gather it's no help with a img. OEM unlocking in developer options is greyed out; stuck on.
Click to expand...
Click to collapse
I'll make it quick: No fastboot, but you don't need it really. Just use EDL. You can install TWRP via EDL Tool or axon7tool.exe
axon7tool is finicky and hasn't got a GUI so you should try with edl tool first.
Download EDL Tool and TWRP, follow instructions on how to set up edl tool, put the twrp .img on Flash - Recovery (rename it to recovery.img just in case [BE SURE that show file name extensions is enabled]) then flash. Then reboot the phone, AND ENTER TWRP (otherwise it'll get replaced). simply reboot the phone after twrp is flashed and select "recovery" from the 5 seconds screen on boot.
Once you're in TWRP you simply have to flash Magisk to avoid losing it again, if you are on stock N firmware you should flash Magisk 16.7 (17.1 will bootloop). But I recommend that you format data (Wipe - Format data) and THEN flash magisk, so that you unencrypt the internal storage and don't lose it if you change your ROM or whatever

Choose an username... said:
Download EDL Tool and TWRP, follow instructions on how to set up edl tool, put the twrp .img on Flash - Recovery (rename it to recovery.img just in case [BE SURE that show file name extensions is enabled]) then flash. Then reboot the phone, AND ENTER TWRP (otherwise it'll get replaced). simply reboot the phone after twrp is flashed and select "recovery" from the 5 seconds screen on boot.
Click to expand...
Click to collapse
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Once you're in TWRP you simply have to flash Magisk to avoid losing it again, if you are on stock N firmware you should flash Magisk 16.7 (17.1 will bootloop). But I recommend that you format data (Wipe - Format data) and THEN flash magisk, so that you unencrypt the internal storage and don't lose it if you change your ROM or whatever
Click to expand...
Click to collapse
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?

You need to enter,
"DM verity enforcing" in twrp advanced settings.
To remove corruption message.
NFound has a twrp with a specific advanced setting for this.

Kimmoth said:
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?
Click to expand...
Click to collapse
The password is because data is corrupted - the system tries to unencrypt it but it isn't encrypted. You just have to format data again (If you have the error, it might be hard - try unmounting and mounting data, or changing its filesystem, it might work. If it doesn't, you'll have to install Fastboot (if it is a G, you can use Raystef's zip from the bottom of this post) and go to it, then do "fastboot erase userdata", it usually works.
And that screen is the 5 seconds screen, you should leave it there, it's useful. Only way to enter Fastboot without commands, plus you can also enter recovery and stuff
also, flash magisk AFTER formatting. I think Magisk Manager is installed in /data so you are essentially removing it
https://www.google.com.ar/url?sa=t&...FjAAegQIBhAB&usg=AOvVaw0mLcRna7wHd0MBSXcBI3sr

So I installed Nfound's TWRP, allowed it to modify the system, disabled DM verity enforcing, and that damn message still comes up (it also shows up instead of fastboot, and choosing fastboot gets me no fastboot), and what's more, now I just get a little linux penguin instead of the boot animation, which just sits there forever, even after re-flashing the ROM...

Check the comments here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
I'm not sure which ROM you are installing, this one is Lineage Os 15.1.
Check this twrp
https://forum.xda-developers.com/axon-7/development/twrp-3-1-0-2-t3591075
You may have to "delete inscription" too
I hope this helps.

I've flashed this rom: A2017G-N-B04 (australian) from here: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Is it it necessary to flash the boot.img that's listed with it, or is that included in the rom zip, or can you run a different one?
I tried adb reboot "dm-verity enforcing" from the pc, and typing reboot "dm-verity enforcing" straight into the terminal on twrp, and the phone rebooted both times but the same 'your device software can't be checked for corruption' thing still comes up...
Is there some way I can wipe the slate clean and start fresh? Something seems a bit off. I'm trying to install Xposed (I have the right one, sdk25-arm64), but when I flash it the phone just hangs at the end of the boot animation.
I could really use a comprehensive primer on all this business... I kind of half get the hang of it, then it's a year or so until I need to do it again, and I've forgotten most of what I learned the last time, with some portion of it that's become obsolete anyway... I feel like I'm groping in the dark here.

Check this post
https://forum.xda-developers.com/axon-7/help/encryption-password-boot-t3667446
Here flashing the ROM and doing a factory reset.
I'm in Australia too (running A2017G) and if you use the wrong software it can cause grief.
Did you flash all 3 files recovery, boot and firmware
From Raysteffs post? If not, you should.
I soft bricked mine by accident and recovered it with a stock edl package.
Edl has all the IMG files needed
Recovery (stock) fast boot, splash, firmware (usually 3 IMG files) and all associated.
I'm currently running B15 Oreo Chinese global (switched modem files to work here in Oz)
I would go back to as stock as possible to restart then use the Axon7 tool kit
Toolkit is here
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
If you mix and match recovery, boot and ROMs this can lead you too bootloop or system hangs because its looking for associated files that aren't there.
Sometimes 1 file can make all the difference.
Good luck, I hope you get it sorted

Kimmoth said:
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?
Click to expand...
Click to collapse
This just worked for me too!

Help! OnePlust 6t rebooting into recovery by itself after rooting

Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system: https://youtu.be/WZKhjJhivmg
Here is a fastboot info:
{
"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"
}

No need to panic yet. I don't know about this tool, never used them. What I would do at this point personally is try and boot (BOOT) the TWRP IMG file. That is the first step in TWRP installation. This will get you into TWRP, with a USB cable hooked to the PC you should be able to transfer any data you need.
Then you can try and fix the issue, likely an easy fix. Might be as easy as flashing TWRP, rebooting to recovery and then Magisk. Or you might need to reflash the ROM, but if you do it as is, reflash TWRP, reboot to recovery, flash Magisk, boot, you shouldn't lose anything.
If you aren't sure at this point, ask, as you will lose data if you do the wrong thing. Also the MSM Tool (since I'm sure this will come up) should always be your last resort as that will lock your bootloader. So I always recommend the Fastboot ROM first before that, especially since you have Fastboot working, but try the other stuff first.

a4abbas said:
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system:
Here is a fastboot info:
Click to expand...
Click to collapse
Just fastboot twrp on your phone. Install the installer again. Reboot and, you will be good to go.

OhioYJ said:
No need to panic yet. I don't know about this tool, never used them. What I would do at this point personally is try and boot (BOOT) the TWRP IMG file. That is the first step in TWRP installation. This will get you into TWRP, with a USB cable hooked to the PC you should be able to transfer any data you need.
Then you can try and fix the issue, likely an easy fix. Might be as easy as flashing TWRP, rebooting to recovery and then Magisk. Or you might need to reflash the ROM, but if you do it as is, reflash TWRP, reboot to recovery, flash Magisk, boot, you shouldn't lose anything.
If you aren't sure at this point, ask, as you will lose data if you do the wrong thing. Also the MSM Tool (since I'm sure this will come up) should always be your last resort as that will lock your bootloader. So I always recommend the Fastboot ROM first before that, especially since you have Fastboot working, but try the other stuff first.
Click to expand...
Click to collapse
scorpio76r said:
Just fastboot twrp on your phone. Install the installer again. Reboot and, you will be good to go.
Click to expand...
Click to collapse
Thanks for your reply.
Shall I use this tool here: https://forum.xda-developers.com/on...t-oneplus-6t-using-oneplus-6t-rooter-t3864238 to flash TWRP using this tool:
or you recommend using something else? and what point should I flash it? after going into stock recovery or fastboot screen? One more thing I almost forgot adding that my phone was already rooted but after doing OTA update and then I use the tool to root again which caused me to stuck in this loop of auto power off.
BTW I have set a password on my phone will that cause any issue accessing TWRP if I do manage to flash it? Please advice

a4abbas said:
Please help me I am stuck. My international version of one plus 6t after Rooting using the oneclick root tool here on XDA my device is rebooting and going into recovery mode - the TWRP isn't installed by itself. Please advise me on what to do. I have important data that i missed to backup so I dont want to do something stupid. Shall I install TWRP with the tool? Is there a way to run the device in safe mode? please advice
Here is a video of me trying to get into the system:
Here is a fastboot info:
Click to expand...
Click to collapse
Hello
Try this, it may help you out and you should have twrp back on your phone:
Download "minimal and adb fastboot" to your pc
Find this folder and open it and you should see twrp image in it, rename it "twrp. img"
In a blank space hold shift button and right click to bring up command window.
Once in this window, you should see fastboot. Type "fastboot boot twrp.img" and hit enter.
you should then have twrp on your phone.
Do this and let me know what happens :

Using 'tools' is a bad habit 'cause you don't know what they do.
Read in twrp thread how to install it manually.
The idea is to temporary boot twrp using the .img file in fastboot (fastboot boot twrp.img) then when you're in twrp flash the installer (file name ending with .zip)

Libraplum76 said:
Hello
Try this, it may help you out and you should have twrp back on your phone:
Download "minimal and adb fastboot" to your pc
Find this folder and open it and you should see twrp image in it, rename it "twrp. img"
In a blank space hold shift button and right click to bring up command window.
Once in this window, you should see fastboot. Type "fastboot boot twrp.img" and hit enter.
you should then have twrp on your phone.
Do this and let me know what happens :
Click to expand...
Click to collapse
Exactly, hopefully the member has the twrp installer on his pc so that it can be moved to the device and, installed to maintain twrp after a reboot.
---------- Post added at 11:36 AM ---------- Previous post was at 11:24 AM ----------
Striatum_bdr said:
Using 'tools' is a bad habit 'cause you don't know what they do.
Read in twrp thread how to install it manually.
The idea is to temporary boot twrp using the .img file in fastboot (fastboot boot twrp.img) then when you're in twrp flash the installer (file name ending with .zip)
Click to expand...
Click to collapse
The msm tool is a definite must have if you own a oneplus device. It has saved many lives here, lol

a4abbas said:
BTW I have set a password on my phone will that cause any issue accessing TWRP if I do manage to flash it? Please advice
Click to expand...
Click to collapse
As stated the tool is probably a bad idea. You should install ADB and Fastboot and use these yourself. The password is not an issue at all, TWRP will just ask you for a password and decrypt your data. You just need the correct version of TWRP for your ROM. Most likely you need:
TWRP 3.3.1-6, from here. As mentioned boot the img, using fastboot. Get your data, then try installing TWRP. Do not install the IMG, you install the zip.
Do not use OTA, with a modified device. Use the instructions for TWRP located here. Download the Zip, install in TWRP. Install TWRP again, reboot to recovery again, flash magisk again. The instructions say to uninstall Magisk, and it's probably a good idea to follow the instructions, but personally I never uninstall Magisk. However I don't have a bunch of a mods installed or anything like that.

I've experienced the same and it sounds like you rebooted to a slot without an operational OS
This is what I did. You can also use MSM recovery tool, very handy when you brick
install google SDK platform on your PC if you don't already have it
Download the latest TWRP zip installer and TWRP img boot image, rename them to TWRP.zip and TWRP.img respectively
I create a folder on my C: Drive as ADB and install the contents of the SDK there and the TWRP zip and TWRP img
you can also place your OOS version there, i name mine OOS_90XX.zip
while fastboot screen is open, connect your phone to your PC
Open Command Prompt window
type "cd \ADB"
"adb devices" to ensure that your phone is connected
"fastboot boot TWRP.img"
TWRP should boot
when in TWRP, go to advanced, then ADB sideload
swipe right to intiate sideload
Type "adb sideload TWRP.zip"
after sideload completes, reinitiate sideload
Type "adb sideload OOS9015.zip"
reboot to recovery
you can then reboot to the other slot, repeat steps above and reboot to system

Frozilla said:
You can also use MSM recovery tool, very handy when you brick
Click to expand...
Click to collapse
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.

OhioYJ said:
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
Click to expand...
Click to collapse
Agreed, it's more of a last resort when the device is unresponsive. That's why i said handy when bricked. The steps that I laid out were intended for him to forego that and retrieve his info.

OhioYJ said:
He's already said he wants to get data off of it. The MSM Tool will wipe the device, and lock the bootloader. The MSM Tool is a handy tool but it should always be a last resort. This device has a working Fastboot, it can very likely be fixed by many other options that don't include locking the bootloader.
Click to expand...
Click to collapse
Agreed

Frozilla said:
Agreed, it's more of a last resort when the device is unresponsive. That's why i said handy when bricked. The steps that I laid out were intended for him to forego that and retrieve his info.
Click to expand...
Click to collapse
Yep, and those where great. I just wanted to make sure it was very clear to the OP that the MSM Tool would wipe his data as it would appear the OP is still learning this device, and the MSM Tool has become lots of people's go to, and while it's handy, it needs to be conveyed it should be used only after all other options have been exhausted.

OhioYJ said:
As stated the tool is probably a bad idea. You should install ADB and Fastboot and use these yourself. The password is not an issue at all, TWRP will just ask you for a password and decrypt your data. You just need the correct version of TWRP for your ROM. Most likely you need:
TWRP 3.3.1-6, from here. As mentioned boot the img, using fastboot. Get your data, then try installing TWRP. Do not install the IMG, you install the zip.
Do not use OTA, with a modified device. Use the instructions for TWRP located here. Download the Zip, install in TWRP. Install TWRP again, reboot to recovery again, flash magisk again. The instructions say to uninstall Magisk, and it's probably a good idea to follow the instructions, but personally I never uninstall Magisk. However I don't have a bunch of a mods installed or anything like that.
Click to expand...
Click to collapse
Yo
Thanks for the detailed instructions however the link you have given me only has IMG (twrp-3.3.1-6-fajita.img) Where do I get the TWRP ZIP file and when I follow the link the instructions are different:
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install
So I wonder where is the TWRP ZIP part?
I still couldn't find it

a4abbas said:
Yo
Thanks for the detailed instructions however the link you have given me only has IMG (twrp-3.3.1-6-fajita.img) Where do I get the TWRP ZIP file and when I follow the link the instructions are different:
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
So I wonder where is the TWRP ZIP part?
I still couldn't find it
Click to expand...
Click to collapse
There is a thread about twrp in ROM section everything is in there

a4abbas said:
So I wonder where is the TWRP ZIP part?
Click to expand...
Click to collapse
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.

Striatum_bdr said:
There is a thread about twrp in ROM section everything is in there
Click to expand...
Click to collapse
Yes I am trying to follow the TWRP thread here, no where there is mention or link for TWRP.ZIP file the only instruct to flash the IMG file even at the last part. https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line
5. Copy the recoveryimgfilename.img in the phone memory
6. Go in advanced menu
7. Click on "Install Recovery Ramdisk"
8. Choose the recoveryimgfilename.img
9. Swipe to install

OhioYJ said:
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Click to expand...
Click to collapse
Bummer! Sorry about that , just found it

OhioYJ said:
There are two links there, the top one is the IMG file the one marked "installer" is the ZIP file.
I honestly haven't looked at the instructions in quite some time. It appears the new instructions are to avoid the step rebooting to recovery and reflashing Magisk. As if you just flash the recovery ZIP it will wipe out Magisk. I always do the way I listed, I haven't tried it the "new" way. mauronofrio, the developer of TWRP for our device won't steer you wrong. You can do that if you want.
Click to expand...
Click to collapse
By the way, there is a button under the advanced section of TWRP that say "Fix Recovery Bootloop" I wonder if it can help in my case?
UPDATE: Finally I JUST TAP "Fix Recovery Bootloop" AND IT FIXED my **** bootloop and now i can access system without issues :good:
@OhioYJ Thanks so much for directions, Do you have Paypal/LTC/ETH address? I am gonna gift you some $ as appreciation
BTW I am trying to backup with TWRP however I am having "255" error during the backup of Data partition, any ideas how to fix that one?

a4abbas said:
@OhioYJ Thanks so much for directions, Do you have Paypal/LTC/ETH address? I am gonna gift you some $ as appreciation
Click to expand...
Click to collapse
No gift necessary, we're all here to learn and enjoy our devices.
a4abbas said:
BTW I am trying to backup with TWRP however I am having "255" error during the backup of Data partition, any ideas how to fix that one?
Click to expand...
Click to collapse
It most likely has to do with parallel apps / multiple users.
This post here, is from the TWRP thread. (It's at the top of the TWRP main thread, the DEV posted the link)
This post maybe helpful (The first method is what mauronofrio the DEV of our devices TWRP posted a link to, so that would most likely be the route to take)