Develop Bugs

TRWP Install help

I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.

You did the unlock bootloader bit in settings?

ReneX10 said:
You did the unlock bootloader bit in settings?
Click to expand...
Click to collapse
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.

GigahurtzUK said:
Hi cheers for replying.
Yeah I've unlocked bootloader in settings.
not sure what I'm not seeing.
Click to expand...
Click to collapse
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment

ReneX10 said:
Love to help more, but I've always used linux to fastboot.
Pretty sure with my swift the erase cmd didn't work for me, but the flash sudo fastboot -i 0x2970 flash recovery '/home/XXXX/Downloads/crackling-t0x1.img' did
Have you tested fastboot with any other devices? just as an experiment
Click to expand...
Click to collapse
No other devices to test with.
I will have to try linux then. I just need a usb to make a linux live usb
Cheers

GigahurtzUK said:
I am trying to install TWRP on my swift.
I have installed android sdk and google drivers. Windows 10 adb and fastboot dont see the swift.
ABD shows no devices listed
Fastboot shows "8bce440" when "fastboot devices" is run
fastboot -i 0x2970 erase recovery sits at "waiting for any devices"
I have uninstalled sdk twice. Restarted laptop. Tried two different usb cables.
I am stumped. Any help guys.
Click to expand...
Click to collapse
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.

Is this the norm when changing recovery.img?
M_Kay said:
If you see the device when command "fastboot devices" is used,
just enter "fastboot erase recovery" without the -i parameter.
This worked for me.
Click to expand...
Click to collapse
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?

noob2016 said:
i have cm-13.0-20160127-NIGHTLY-crackling-recovery.img installed, should i do the erase? i just flash it using TWRP 2.8.7.1, it is working when i install the cm13.0 but i couldn't install gapp - just hang. Is this the norm when changing the recovery? also can i revert back to the previous recovery img?
Click to expand...
Click to collapse
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.

Thanks for the fast reply and help
M_Kay said:
I would replace the nightly recovery with the TWRP recovery img, because it has more options and you can backup your whole system.
So yes erase it and flash TWRP .8.7.1 recovery.
Are you stuck in a bootloop?
If you have intalled TWRP recovery boot into it and under option Wipe format the system and data folder (carefull your data will be lost!!!) . After that flash the nighthly rom again without gapps and check if you can boot.
Click to expand...
Click to collapse
1st thanks for fast reply and help
im not in bootloop, thank goodness!
I'm currently in TWRP, when the recovery was in CM the gapp-arm64-aroma-5.1 it installed flawlessly following the cm12.1 flash but after the update 13.0 the gapp can't be installed even reverting back to 12.1 and using the same files. I did wipe all prior to change of rom also match it (i.e. cm13.0 to gapp 6.0).
Maybe this will solve it. I will try to erase recovery and re-install TWRP
i will report back after. Thanks

Works
Thanks it worked on pico gapp but not in aroma
followed the erase command and install TWRP again.
Many thanks

TWRP not working in Aroma Gapp need fix
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me

noob2016 said:
In the previous post, i was able to install twrp but i found out on many trial and error that open gapp aroma/full doesn't work both on cm12.1 and cm13.0 using TWRP. Also cm13.0 recovery will not work with open gapp aroma/full.
What works: (haven't tried all version)
On TWRP - i was able to use arm64-pico-6.0 on cm13.0 20160130
On CM Recovery - arm64-aroma-5.1 on cm12.1 20160107
This is based on my experience with the HELP of the awesome people in the forum. I just want to let you know and maybe it will be useful to other noobs like me
Click to expand...
Click to collapse
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP

Thanks
robin0800 said:
This TWRP works wioth aroma gapps
https://s.basketbuild.com/devs/beroid/Wileyfox%20Swift%20-%20Crackling/TWRP
Click to expand...
Click to collapse
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb

noob2016 said:
Thanks for the info and fast reply.
Will this work on Wileyfox Swift? i currently have TWRP 2.8.7.1 size 24.4mb but the link above is in 2.8.7.0 size 15.1mb
Click to expand...
Click to collapse
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial

I will try
robin0800 said:
Works well on mine both for AROMA and cryogenmod nightly updates and to install c-apps for cm13 unoficial
Click to expand...
Click to collapse
Thanks for the reply and also on my other post.
Since this is for swift, i will try to install but sadly i have given it back already. It was just here for the upgrade and when i got the chance to get hold of it again i will definitely try and report back.
Many thanks.

Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks

msiviter said:
Following the various instructions for both TWRP and CM recoveries provide the same frustrating result: I'm getting a black screen when I reboot into recovery.
Everything seemed to go ok on the flashing using ADB but then when replacing the battery and vol-down +power to reboot into recovery I'm greeted with nothing.
Subsequent reboots into recovery from the OS reinstate the Cyanogen recovery.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495

robin0800 said:
The easy way
Install recovery in bootloader mode with fastboot flash recovery "the name of your recovery"
Hold volume down
issue this command fastboot reboot
when phone restarts you can release volume down the phone should now boot to your new recovery
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
I think it was a windows 10 problem, I gave it all another try this morning firstly using the WinDroid Universal Android Toolkit to Unlock Bootloader and flash TWRP . I then rebooted into recovery and hey presto TWRP. Flashing CM13 nightly and pico gapps was then childsplay.
Any ideas why google play didnt offer to auto restore all my apps? Thats a bit of a pain.
Otherwise very pleased, phone seems a bit more responsive using CM13 than CyanogenOS. I tried to format my SD to use as internal storage too but i couldnt see them separately afterwards to free up device storage so I reverted back.
Thanks for trying to help.

Yey!!!
robin0800 said:
Note TWP version 3.0.0 is out https://www.androidfilehost.com/?w=files&flid=48495
Click to expand...
Click to collapse
Confirmed!!! It works... i used TWRP 3.0. Works on both aroma and pico. Thanks so much!!!!

Got stuck in a TWRP loop after installation. Regardless which reboot option I choose, always TWRP 3.0.0 comes up. No idea what I did wrong but for me it is of more interest how to get rid of it. Accessible external SD contains cm14-zip and also Stock 6.0.1. Installed CM14 multiple times, but has no impact on what comes up after selecting reboot/reboot recovery/reboot fastboot - it is always TWRP. Tried it also via adb sideload from within TWRP, no change of behaviour. Same when I tried to install stock rom.
Bootloader issue? How to get it back? I have 2 further Swifts available so I can dump several necessary partitions from them, but I need to know which tools are required, since I usually deal with MTK-based androids. Backup of userdata and sdcards is available, so if a reset to stock is necessary, this is not a problem from that point of view - if I only would have the info, how to get back a working bootloader.
Even though I love this recovery, it is obviously annoying ... Any help appreciated. Tnx in advance!
Edit: Fixed. I removed the battery for several hours and without battery with plugged in USB cable (not the WF one, I have tons of them lying arround here) I was able to reboot to normal fastboot. From then on it was strraightforward:
checked OEM lock status via fastboot command on PC
flashed newest TWRP
rebooted to TWRP
installed Stock ROM to get all partitions reinitialized correctly
rebooted to OS - YEAH, the swift lives again
Rebooted to recovery
Installed CM14 and OpenGApps Nano (ARM, not ARM64, since it produces an error)
Reboot to OS - YEAH, here we are.

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers

Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?

JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk

I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.

Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.

Thanks a lot guys, that did the trick, and done with flashify

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk

Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.

Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!

HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.

GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...

m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time

http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me

JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me

This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!

gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..

After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.

Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse

Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

Moto G5 automatically boots into TWRP

Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?

I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.

I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings

CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.

SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?

Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates

Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings

grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully

OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards

SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect

Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup

rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.

Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737

grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?

Very strange issue OP3

Hi, I just bought a second hand OP3, the version installed was the last Open BETA 26.
So everything was working properly but when I reset it the phone was extremly laggy, even the bootamination.
And when the phone booted-up it was very laggy and after some seconds it crash (freeze and turn off after few seconds).
I tried a lot of flashs :
- ADB slideload (impossible to flash a firmware, sometimes the command don't work and when it works it stops after 47% or 97/94%
- The ultimate flash for bricked devices (https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/), the flash worked, but the freeze problem was still here even if the version flashed was OxygenOS 3.1.2
- From this firmware I managed to flash OxygenOS 4.5.1 (the last stable one) with ADB Slideload and same problem again.
- I tried to lock / unlock the bootloader but changed nothing, I even tried to flash TWRP to flash a custom rom but impossible to find a working version.
Now I need the help of XDA Gods !
Sorry for my bad english :silly:

The worst case scenario here is that you have a bad case of corrupted or broken storage (by 'storage' I mean the entirety of the phone's NAND storage) — have you tried wiping /data (labeled as Internal Storage in TWRP) or switching its filesystem back and forth (so, for example, if you have F2FS you'd need to switch to EXT4).
I'd say you might want to start backing up whatever data left in the phone.

try turning off advanced 4g mode. I have the same problem when flashing oos (cpu usage at 50%+ when idle) and this helped me.

F4uzan said:
The worst case scenario here is that you have a bad case of corrupted or broken storage (by 'storage' I mean the entirety of the phone's NAND storage) — have you tried wiping /data (labeled as Internal Storage in TWRP) or switching its filesystem back and forth (so, for example, if you have F2FS you'd need to switch to EXT4).
I'd say you might want to start backing up whatever data left in the phone.
Click to expand...
Click to collapse
Thanks for your answer, I didn't find a working version of TWRP to test (every TWRP i tried was black screen or stuck on TWRP logo) but I already tried full wipes from stock recovery (very very many times), I will try all TWRP avaliables and try your method.
But now I think the problem is the worst case that you said :/

hellcat50 said:
try turning off advanced 4g mode. I have the same problem when flashing oos (cpu usage at 50%+ when idle) and this helped me.
Click to expand...
Click to collapse
Thx i'll try if the phone don't freeze before I access settings^^
where is exacly this option ?

Bryandu13 said:
Thanks for your answer, I didn't find a working version of TWRP to test (every TWRP i tried was black screen or stuck on TWRP logo) but I already tried full wipes from stock recovery (very very many times), I will try all TWRP avaliables and try your method.
But now I think the problem is the worst case that you said :/
Click to expand...
Click to collapse
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.

F4uzan said:
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
Click to expand...
Click to collapse
Okay i'll focus on it ! Thanks !

Bryandu13 said:
Okay i'll focus on it ! Thanks !
Click to expand...
Click to collapse
https://forum.xda-developers.com/devdb/project/dl/?id=27068
the twrp i recommned

Bryandu13 said:
Thx i'll try if the phone don't freeze before I access settings^^
where is exacly this option ?
Click to expand...
Click to collapse
It is where you can set up apn and switch data roaming

I have the exact same problem
Changing the data format doesnt work for me.

Skinpipe said:
https://forum.xda-developers.com/devdb/project/dl/?id=27068
the twrp i recommned
Click to expand...
Click to collapse
Thanks, this TWRP works !

F4uzan said:
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
Click to expand...
Click to collapse
I tried change everything to EXT4 (only DATA wasn't EXT4 but "emmc") but it doesn't worked

zainhateszayn said:
Changing the data format doesnt work for me.
Click to expand...
Click to collapse
That's sad :/
I hope we'll find a solution

Bryandu13 said:
I tried change everything to EXT4 (only DATA wasn't EXT4 but "emmc") but it doesn't worked
Click to expand...
Click to collapse
Unbrick guide method 2 doesn't work? I'll say start contacting Oneplus.

Puddi_Puddin said:
Unbrick guide method 2 doesn't work? I'll say start contacting Oneplus.
Click to expand...
Click to collapse
Yes, it don't work...
I don't know about conctacting OnePlus because it's a second hand model without bill, only the box.

Now I noticed that is was possible to flash any OxygenOS ROM or any OxygenOS based ROM with TWRP (the problem is still here) but impossible to get a booting AOSP based or any no-OxygenOS based ROM.
I'm trying to get the bill to get the help from OnePlus customer service.

So my phone is dead right ? We can't even find a motherboard on internet :/

Can you try
"fastboot format userdata"
"fastboot format cache",
"fastboot format system",
" fastboot erase recovery"
"fastboot reboot bootloader"
commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery? This may help.

qhsusb_bulk said:
Can you try
"fastboot format userdata"
"fastboot format cache",
"fastboot format system",
" fastboot erase recovery"
"fastboot reboot bootloader"
commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery? This may help.
Click to expand...
Click to collapse
Thanks I will try, but I don't understand your last sentence "commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery?"

Bryandu13 said:
Thanks I will try, but I don't understand your last sentence "commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery?"
Click to expand...
Click to collapse
It is your choice, you can copy zip with TWRP then flash Oxygen recovery via fastboot or just sideload it with ADB.

[LineageOS 19.1] Reboots to fastboot despite successful install

Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.

woelkchen said:
Hey
couldn't find anything related to my situation so I decided to ask. Here it goes:
After having to wait an entire week to unlock the bootloader (really??) its finally unlocked and I decided to install LineageOS.
Got a Mi10T Lite, gauguin, M2007J17G. It managed to snuck in an update to something like August 2020 security level at some point but after unlocking it got reset, so I suppose it had Android 10 and MIUI 12(?).
Simple enough, have done that countless times before.
- Flashed recovery, format data/factory reset as explained in wiki
- adb sideloaded ROM (nightly builds 20220822 and 20220815) - both succeeded
After rebooting the devices enters the bootloader again.
The wiki never mentions behaviour like this and I couldn't find anything online.
Do I need to flash latest MIUI ROM again?
Any ideas what went wrong and how to solve this issue?
I unzipped the ROM and fastboot boot boot.img which just resulted in a reboot to fastboot again.
Any idea or, preferrably, a solution would be most welcome
Thanks in advance.
Click to expand...
Click to collapse
Try to flash the last firmware or rom
V13.0.4.0.SJSMIXM
https://xiaomifirmwareupdater.com/firmware/gauguin/
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
TWRP
https://androidfilehost.com/?w=files&flid=318225

Thx. Went ahead and did that which ofc solved the issue. Thx a lot

Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?

BolognaTown said:
Hi, I have same issue. I installed lineage 19.1 2022-09-26 on Mi 10T lite, actually last nightly, and after succesfull installation, after reboot lineage doesnt start and i have just fastboot mode. I have lineage recovery installed, and if i try to install recovery-rom, i dont feel comfortable on installing fastboot-rom, i get error, just after 47% i get unknown signature and it ask if i want continue, if i choose yes continue, on device it says it cant downgrade so its stopped. I also deleted cache but it didnt help, im not very happy to format system partition, im worried to brick it. Should i format system partition? And how deal with missing signature when i try to push stock rom? should i allow it?
Click to expand...
Click to collapse
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

NOSS8 said:
Cant use LOS recovery for stock rom.
go back to Miui
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?

BolognaTown said:
i didnt understand completely, should i find stock recovery and 'fastboot flash recovery stock-recovery.img'
or just using miflashtool without adding any stock recovery?
Click to expand...
Click to collapse
Use Miflash and read the tutorial carefully.
Miflash=Fastboot rom

Thank you, i unbricked it, and i installed lineage. Great Job