Database Develop

Can't access to TWRP anymore

Hello everyone,
so here is my configuration:
-latest TWRP (3.0.2) with F2S support
-bootloader unlocked
-the N6 is rooted
-ROM: AICP MM
2 days ago I tried to reboot to recovery to flash a more recent version of my AICP ROM. I just had the time to see the TWRP boot logo and then the phone rebooted to load the system. I can't access anymore to my recovery. I tried to rename the twrp directory on the internal SD but it does not change anything.
I reflashed TWRP with ADB and fastboot, but it didn't resolve the problem.
The only change I made recently was to flash a new radio to try to improve my connectivity.
I flashed 5.34 with the new bootloader in fastboot. Then I tried 5.32 without changing the bootloader and finally the 5.36 with the latest bootloader. So I don't know when the problem occured but now my phone even reboots randomly !
So if anyone has a solution you're welcome !

What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.

Had this Problem on an other device . No recovery flash with fastboot . Dont no how , but Trwp manager APP from playstore did it .

you have to flash twrp right.. if you use a toolkit or flash the recovery with fastboot boot(instead of fastboot flash) then it will only boot into twrp 1 time, then you will need to flash it again if you want to use it again.

Strephon Alkhalikoi said:
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Click to expand...
Click to collapse
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !

marcp39 said:
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
Click to expand...
Click to collapse
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.

simms22 said:
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
Click to expand...
Click to collapse
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.

marcp39 said:
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
Click to expand...
Click to collapse
sounds like you need to clear the recovery partition, then flash twrp again.

simms22 said:
sounds like you need to clear the recovery partition, then flash twrp again.
Click to expand...
Click to collapse
With "fastboot erase recovery" ?

marcp39 said:
With "fastboot erase recovery" ?
Click to expand...
Click to collapse
honestly, i dont remember how.

So here are my last attempts:
-I've tried to clean the cache with "fastboot erase cache", I thought it could be corrupted. BIG MISTAKE ! This time the phone is bootlooping when lauching the ROM...
And of course, I'm making some backups but they are on the "internal sd"... So I can't access my files anymore !
-I've also tried "fastboot erase recovery" and reflashed recovery. No improvement.
-I've downgraded the bootloader from 71.21 to 71.18. Nothing changed.
-I was asking myself if last time I didn't enter a wrong command in typing "fastboot flash boot bootloader.img" instead of "fastboot flash bootloader bootloader.img". So even if I've added benzocore on my AICP ROM, I decided to flash the boot.img from AICP zipfile on the boot partition (+ erase boot). So this time no more bootlooping of the ROM, because I'm stuck on the google logo :crying:...
I've never encounter such a desperate situation ! I don't even understand why I can't boot in recovery...
I could reflash a factory image on my phone, but this would erase all my datas !
Do you think I could reflash a factory image (except the data partition), just to be able to get a valid recovery, and access my files from the computer ? Then I could erase data partition, and reflash a new ROM ?
I don't want to precipitate the next actions because I don't have any joker... and with this stupid idea of not putting any µSD slot in most phones nowadays we're captive of the situation when the phone is bricked ! We can't recover data easily, even with adb pull (which does not work in my case of course).
So please share your ideas, they'll be welcome ! I've read A LOT of posts on XDA and others, but no solution until now....

TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.

marcp39 said:
I could reflash a factory image on my phone, but this would erase all my datas !
Click to expand...
Click to collapse
Don't use FlashAll, it's usually broken, anyway. But rather unpack the zip, flash boot and system. And either flash cache or erase it. It does the same.

HueyT said:
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
Click to expand...
Click to collapse
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?

marcp39 said:
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
Click to expand...
Click to collapse
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
Click to expand...
Click to collapse
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.

HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
Click to expand...
Click to collapse
Yeah unfortunately we can do it with adb (like this http://stackoverflow.com/questions/8650407/how-to-copy-selected-files-from-android-with-adb-pull) but not with fastboot. Tomorrow I'll try to flash each *.img from MOB30M separately and see if I can recover a working recovery to access to my datas ! Thanks for your answer btw.

Hello everyone !
So here are the last news...
I've tried an older TWRP like 2.8.x.x same problem.
I've flashed all the *.img from MOB30M except data, but my recovery was still not accessible !!!
So I was resigned to format my data and flash the *.img on it.
This time it worked, my N6 was coming back to life !!! Then I had to root it, flash the recovery, remove encryption and format data with F2FS !
I still don't understand how a corrupted (?) data partition could block the running of recovery, that's strange !
So now I have to restore the data from a TWRP image dated 04-16 I had on my NAS...I can tell you that in the future I won't let my recent backups only on internal storage !

Will you believe me if I tell you that the same problem is occuring again :crying: ?
Several days ago, it started when the impossibility to enter the recovery but this time it does not reboot in bootloader, just stuck... Now I got random reboots and stange behaviour from applications !
I NEVER had a serious problem like that with my N6 before. So I don't understand how can I get data corruption like this ? Last time I was using Benzo kernel, now DeYuS kernel but with no exceptional settings, no overclocking.
I've just disabled "forceencrypt" and convert data to F2FS (no problem before).
So does anyone have a clue about this problem ?

Cant reach TWRP

hi guys
i just unlock my bootloader
after it i tried to flash TWRP recovery. but i cant reach their..
the only things i see after rebooting to recovery is black screen white LED

Recovery does not match the formatting of your data partition. Get the correct TWRP or format your data partition correctly.

dreinulldrei said:
Recovery does not match the formatting of your data partition. Get the correct TWRP or format your data partition correctly.
Click to expand...
Click to collapse
thanks for answer but i dont think its this
i made wipe from stock recovery then made all from the start
now its working
thanks

Newb help - unable to mount storage?

Hi all,
I'm having trouble flashing a custom ROM on my Mi 9 Lite. After formatting, TWRP is unable to mount storage, probably due to encryption/decryption issues! Here's what I've done so far:
- unlock boot loader (with Mi Unlock after wait time)
- flash TWRP recovery with fastboot (mauronofrio)
- boot to TWRP worked fine
- followed the OP by gringo80 to install LineageOS 16.0 - as was said there, to do FORMAT once after flashing TWRP
Now TWRP can't mount/find internal storage, says "failed to mount data (no such device)" - can't format or wipe data anymore. All I found so far is that this will be an encryption/decryption issue due to the formatting, but no clue on how to undo this!
Any ideas? Flashing new system or restoring backup always results in bootloop, probably because the ROM can't write on internal storage either?!
Please help :crying:

.M.D. said:
Hi all,
I'm having trouble flashing a custom ROM on my Mi 9 Lite. After formatting, TWRP is unable to mount storage, probably due to encryption/decryption issues! Here's what I've done so far:
- unlock boot loader (with Mi Unlock after wait time)
- flash TWRP recovery with fastboot (mauronofrio)
- boot to TWRP worked fine
- followed the OP by gringo80 to install LineageOS 16.0 - as was said there, to do FORMAT once after flashing TWRP
Now TWRP can't mount/find internal storage, says "failed to mount data (no such device)" - can't format or wipe data anymore. All I found so far is that this will be an encryption/decryption issue due to the formatting, but no clue on how to undo this!
Any ideas? Flashing new system or restoring backup always results in bootloop, probably because the ROM can't write on internal storage either?!
Please help :crying:
Click to expand...
Click to collapse
The current twrp has issues with data try to change filesystem to f2fs and after that change back to ext4 (it forces a full data partition wipe). i've done this always on my mi9 lite AND watch out for the right firmware for lineage os that causes issues too

Layer_DE said:
The current twrp has issues with data try to change filesystem to f2fs and after that change back to ext4 (it forces a full data partition wipe). i've done this always on my mi9 lite AND watch out for the right firmware for lineage os that causes issues too
Click to expand...
Click to collapse
Changing file system to ext4 and back to f2fs did the trick - thank you so much!
Was able to install LOS 17.1 going forward. Thanks again! :good::fingers-crossed:

Need help again :crying:
I flashed the original firmware as instructed, but now all I get is fastboot - NO RECOVERY!
If I flash a recovery with fastboot, all I can to is boot to fastboot again... what can I do now? :crying::crying::crying:

.M.D. said:
Need help again :crying:
I flashed the original firmware as instructed, but now all I get is fastboot - NO RECOVERY!
If I flash a recovery with fastboot, all I can to is boot to fastboot again... what can I do now? :crying::crying::crying:
Click to expand...
Click to collapse
You may have bricked your phone. Did you tick the 'clean all and lock' option in miflash rather than 'clean all'? If so your phone is bricked and needs EDL flashing by an authorized technician to fix it.

Lucky enough, not bricked - I flashed a firmware update in the middle of all of it, one which, of course, replaced almost everything I had done so far. Forgot to flash custom vbmeta when trying to re-flash TWRP, doing so solved the issues I've had. Close call though, as the firmware update could have re-locked bootloader in a worst case scneario, so really lucky to be using my phone with MiuiMiX now, all working perfectly!
Thanks for the help though!!!

My k20 pro isnt booting up

I tried installing custom rom for the first time now i did it with xiaomitool but it gave error that it couldnt wipe data and my phone stuck on boot.
Then on my phone i booted to twrp and frm there i wiped dalvik cache and data with a wrappedkey error but i continued and flashed pixel exp plus and formatted data and when i rebooted system i again got stuck there
Then once again i went to twrp and tried wiping dalvik cache and data again but this time with wrappedkey amd some decrypted error to and formated data and then tried rebooting to system. Again nothing worked pls help my otherwose my parents are going to kill me
EDIT : Also my laptop has mac os so i think there isnt much i could do with pc and thats only why i used unofficial xiaomitool in the first place

If youre coming from xiaomi rom or xiaomi eu rom you need to format data ( option in twrp where you type yes) not just wipe data, then reboot to recovery (twrp) again and then follow instruction of rom you want to install. Some custom roms require flashing vendor firmware before flashing rom , then gapps , then magisk if you require root ( if magisk wont install then after flashing rom reboot to twrp again). Also xiaomitool is not ideal for installing custom rom but for recovery and fastboot roms ( one that came originally with phone when phone had locked bootloader, never tick wipe and lock)
Disregard my comment about xiaomitool, had thoght that you mean miflash tool

But how
That rom is not in my phone anymore nor i know how to install back to xiaomi rom btw my phone is indian varient

UPDATE
I once again tried flashing pixl exp plus using a diff tutorial which included flashing some disable force encryption and now my device wont even boot into twrp its stuck on fastboot mode.
Now i only hot two question :
1.) will i be able to charge my phone in fastboot mode (or any other way?)
2.) will i be able to flash stock miui rom in fastboot mode through my mac (or if theres any other way pls tell me)

Yes you will be able to charge through fastboot
Just flash twrp again thn boot into twrp and go to wipe - format data and type yes.
Until and unless you format data you will not be able to do anything
Thn download Indian vendor zip ,your required rom and disableforceencryption.zip in your pc and copy it to the phone while in twrp.
Go to wipe and wipe cache ,dalvik ,data,system,vendor
Thn flash vendor zip followed by rom and dfe
Now reboot

device is jusr stuck on fastboot
Pronoy_ said:
Yes you will be able to charge through fastboot
Just flash twrp again thn boot into twrp and go to wipe - format data and type yes.
Until and unless you format data you will not be able to do anything
Thn download Indian vendor zip ,your required rom and disableforceencryption.zip in your pc and copy it to the phone while in twrp.
Go to wipe and wipe cache ,dalvik ,data,system,vendor
Thn flash vendor zip followed by rom and dfe
Now reboot
Click to expand...
Click to collapse
i did the sameexcept for vendor as i had latest miui but phone got stuck in fastboot and twrp is not accessible.
now what if i install official fastboot rom will it relock the bootloader and brick my phone for good?

ak20prouser said:
i did the sameexcept for vendor as i had latest miui but phone got stuck in fastboot and twrp is not accessible.
now what if i install official fastboot rom will it relock the bootloader and brick my phone for good?
Click to expand...
Click to collapse
Only if you forget to change the option in the Mi Flash Tool, which is easily done if you're not paying attention. If the fastboot ROM is the correct version for the phone then you won't brick the phone if you forget to change the flash option. You will just need to unlock the bootloader again before doing anything else.
After flashing a fastboot ROM, boot into MIUI once so that the install finalises itself.
Then flash TWRP and boot into TWRP.
Do a factory reset, then format data. No need to wipe anything else.
Reboot into TWRP to ensure the newly formatted data partition is properly mounted.
Now copy across and flash the ROM of choice plus any optional extras.
There is no need to flash dfe files or vbmeta, etc.
Assuming you've flashed the latest fastboot ROM, then there's no need to flash vendor or firmware files.

Just go through this post
Trust me it has solved all of my issues
http://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543

Pronoy_ said:
Just go through this post
Trust me it has solved all of my issues
http://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
Click to expand...
Click to collapse
Hello Bro. I flashed the latest firmware and the evolution x rom but now my phone is stuck on the redmi logo. I am able to go back to recovery but what do I do now?

Stuck in recovery bootloop

Hello guys
I tried to flash my K20 Pro today with a custom ROM and somehow ended up with a bootloop (I wiped everything pretty much, Data, Vendor (which was probably the mistake, dunno), System, caches, all that). So, I went ahead and flashed the stock ROM through the MiFlash tool, and I can use the stock ROM. After that, I flash TWRP and repeat the process. Wipe, flash, reboot. And I get the bootloop.
Bootloader is unlocked as should be.
Anyone know what's causing this and what I can do to fix it?
Thanks in advance
EDIT: Just noticed that after this last attempt where it bootlooped into the recovery, everything's encrypted, don't know if that helps but it's there.

Format data

camp70 said:
Format data
Click to expand...
Click to collapse
Had it running on the fastboot MIUI ROM, flashed TWRP, wiped caches, system and data. Then data again. Storage shows up in 3 "partitions" and I can't paste files to them. When I try to reboot back to TWRP it just goes to fastboot and after reflashing TWRP, it still will boot to fastboot instead of the just flashed recovery. Using fastboot oem reboot-recovery if that helps.
After the wipe, doing fastboot boot twrp.img will fire up a "Failed to load/authenticate boot image: Load Error"

Format is not the same that wipe

From MIUI
Install TWRP.
Boot TWRP.
Go to wipe menu and factory reset.
Return to wipe menu and select format data.
At no point do you need to go into the advanced wipe menu.
Return to the main menu.
Go to boot menu.
Select (re)boot recovery to allow TWRP to correctly mount the newly formatted data partition.
Copy across the files you want to flash, then flash them.