Related
so my bro rebooted out of recovery (twrp) after wiping system and not flashing anything and now im stuck on splash screen. im screwed aren't I. edit: I can still boot into recovery... not sure if that will help! also I currently have no backups or rom to flash on the device ;( anyway to get adb sideload to work!? I use and it says device not found
Stryker1297 said:
so my bro rebooted out of recovery (twrp) after wiping system and not flashing anything and now im stuck on splash screen. im screwed aren't I. edit: I can still boot into recovery... not sure if that will help! also I currently have no backups or rom to flash on the device ;( anyway to get adb sideload to work!? I use and it says device not found
Click to expand...
Click to collapse
nvm I used my pc's device manager to work adb
I did something stupid like this yesterday. If you have a recent enough TWRP, you can use the Advanced-> sideload app option with adb to download a rom to where you can install it using twrp.
Stryker1297 said:
so my bro rebooted out of recovery (twrp) after wiping system and not flashing anything and now im stuck on splash screen. im screwed aren't I. edit: I can still boot into recovery... not sure if that will help! also I currently have no backups or rom to flash on the device ;( anyway to get adb sideload to work!? I use and it says device not found
Click to expand...
Click to collapse
All you have to do is put the rom zip on your micro sd card, then TURN OFF your device. Now boot into twrp then select install by browse to the micro sdcard to select the rom zip file.
buhohitr said:
All you have to do is put the rom zip on your micro sd card, then TURN OFF your device. Now boot into twrp then select install by browse to the micro sdcard to select the rom zip file.
Click to expand...
Click to collapse
I had a very similar 'No OS' problem and I wasn't sure if I would be able to reboot into recovery but thank you for answering my question!
Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...
If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Sideload worked perfectly! Thank you so much!
cm11 working only TWRP here , with cwm appears same error
mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
EDIT (FIXED)
WHAT WENT WRONG...
1. Was using CWM (When i was last active in android flashing, twrp was just another custom recovery, cwm was needed for cm)
2. When i did use TWRP, it was an older version, and did not work (did not even boot to recover, in fact)
3. When i did get twrp working, i used a bad cm.zip file (corrupted)
nishant_713 said:
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
Click to expand...
Click to collapse
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
bloodhound42 said:
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
Click to expand...
Click to collapse
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
nishant_713 said:
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
Click to expand...
Click to collapse
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
bloodhound42 said:
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
Click to expand...
Click to collapse
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Update -- Ok flashed 2.8.6.0 and now boots to revovery (even after a restart) but still can't flash cm. Something pops on screen for a fraction of screen and then recovery reboots. It says "no md5 file found". Any chance of zip being corrupt ?
Update 2 -- Now my internal memory has stopped working :/ can't even take a screenshot, nor a photo. says memory full. Doesn't even copy file to memory when connected to pc. Although in recovery mode (twrp) , with usb mounted, it does copy.
nishant_713 said:
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Click to expand...
Click to collapse
weird did u flash normal recovery or gpe recovery ? U have to flash normal recovery and one more thing are u sure that its going into cwm recovery ?
May be the ROM is corrupted buddy download again and flash or try other Roms
Haha. After a hell lot of effort, i did get TWRP installed, and after breaking my head on why cm nightly won't install, i downloaded another one, and it installed fine. Now rocking CM 12.1 (4th device which I'm using on CM, and yet never had so much trouble getting it running..)
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
jjeans said:
Hallo,
I have a problem. I flashed newest TWRP 2.8.7.1 (I also tried 2.8.7.0) onmy Mi4C and installed some ROMS (sMiUI, Decato, CM12.1) but even if flash of TWRPs and installation of ROMS was successful without error, the device is always booting into Recovery/TWRP.
So problem is that device is not starting into system!
- I tried with power button reset
- I tried with "reboot to system"
- I tried with battery removal!
- I also tried new installation of TWRP and/or several ROMS. (e.g. sideloading ADP is also working)
- I also made some (full) WIPEs / Fix Permissions
but it is always starting only to TWRP.
After device is starting, MUI-symbol appears for 5-10 seconds and then TWRP is loading, but not ROM.
What can I do? Maybe installation a new Kernel or something?
thanks in advance,
Jimmy
Click to expand...
Click to collapse
Download fastboot rom and flash it
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
jjeans said:
thank you that worked..
but I have still the problem when I flash several versions of TWRP, that a reboot/start of the system will always end up within the recovery.
Only a a reflash of fastboot rom helps, but then I have the old mi recovery that does not work for other ROMs :/
a strange behaviour.
So I can flash TWRP, but it is not possible to boot into the system...
Without a newer TWRP that can "boot into system" I cannot use Custom ROMS
Click to expand...
Click to collapse
How do you flash recovery tell me the procedure?
Talha7866 said:
How do you flash recovery tell me the procedure?
Click to expand...
Click to collapse
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
jjeans said:
Hallo,
I used some manuals for flashing.
e.g.
en.miui.com/thread-166465-1-1.html
gammerson.com/2015/10/install-twrp-recovery-mi4c-root-it.html
+ some manuals from decuro rom and sMiUI Rom
In summary:
1. Pre steps: Download USB & Adb drivers / Download TWRP Recovery 2.8.7.0 for Xiaomi Mi4C / I also tried 2.8.7.1
2. Flashing: Boot phone into fastboot --> Connect phone with USB (I tried before and after boot to fastboot) --> CMD --> "fastboot flash recovery" <recovery-name>.img
3. After successful flash of 40-50 MB TWRP recovery I tried CMD "fastboot reboot" / I tried also without reboot command (with Vol+ & Power) / I tried also only with power button
Always system boots to TWRP recovery.
When I choose ROM afterwards with new TWRP recovery and flash it, it says successful installed, but reboot does not start to ROM
At the moment I always do fastboot rom reflash, that old system will come back and work. Flashing ROMS with old system (via updater app and old Miui recovery) is not working, it is always update error, even if I rename ROM to "update.zip".
What I never did rooting the phone, so flashify says "device not rooted". I do not know If I have to root, I assume not. I do not want root, because I will use a company app that needs an unrooted phone.
thanks,
Jimmy
Click to expand...
Click to collapse
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
zhart said:
I have had the same issue, and read somewhere that it is because you tried flashing a rom in stock recovery and failed, that causes recovery bootloop. I was in same position other than i erased most og my partitions except recovery, and then installed fastboot rom, and it was all good again. Not saying ypu should erase any partitions! Rather not try and flash anything in stock recovery ever.
Click to expand...
Click to collapse
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
jjeans said:
Thank you for your answer.
So I can do:
1. Wipe all data (it is the only option in recovery)
2. Re-flash fastboot rom
3. Try again to flash new recovery & install custom ROM
Is that correct?
What partition can I securely erase? and how? because erase is only possible with newer Recovery.
Click to expand...
Click to collapse
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Sorry, what exaclty is a fastboot rom and where do i get it?
zhart said:
I would clean install fastboot rom, and then install the latest recovery, and try to install a rom. All from buttom so you know exactly what you have done
I accidentaly erased my partitions with fastboot. Data, boot, and internal ? I think. Would not recomend it.
Click to expand...
Click to collapse
I don't know what happens all the time.
Currently I used MiFlash to make a clean fastboot install. I choosed in MiFlash "flash_all.bat" to do it. (flash_all.bat means everything was reinstalled, also recovery.img). Afterwards everything was normal, MiRecovery 2.x and Mi4C MiUI 7 chinese version was installed without error. But after manual flashing TWRP with "fastboot flash recovery xxx", the recovery loop was again! :/
So AGAIN I made a clean fastboot install again with MiFlash application, but this time I REPLACED the recovery.img with the newest TWRP (renamed to recovery.img) within the fastboot rom installation folder "images". I could see that MiFlash flashed THIS! recovery.img, but after that again the old Mi Recovery was on the device and no TWRP. But why? I replaced the original recovery.img file! How can that happen?
The flash_all.bat included flashing recovery and I could confirm it during the fastboot flash. Strange.
I used fastboot rom libra_images_V7.0.16.0.LXKCNCI_20151104.0000.4_5.1_cn
MiFlash newest version and I tried with 2 TWRP versions (one from decuro and one from sMiUI)
Maybe my phone has a problem with flahing recoverys in general I don't know.
jjeans said:
Maybe my phone has a problem with flahing recoverys in general I don't know.
Click to expand...
Click to collapse
it sound very strange i did all these steps and my phone was all good after it. is it the newest recovery? the one with material theme and touch fix you are using? if not, then thats the only difference between your procedure and mine :/
i hope you can fix it
Edit: I can see that i have the following fastboot roms downloaded, so i used one of these:
libra_images_V7.0.6.0.LXKCNCI_20150917.0000.1_5.1_cn_4dd76a55cb.tgz
or libra_images_V7.0.15.0.LXKCNCI_20151104.0000.4_5.1_cn_f6e955ee14.tgz
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Hello, don't know if applicable. I've read on mi forums that dev Roms need dev recovery, that's different from twrp for stock rom.....
guegangster said:
What I would do, is fastboot original ROM, reboot to recovery, factory reset, recboot to fastboot to re-flash TWRP and then command "fastboot boot recovery" to get to TWRP and install your ROM.
Didn't has this pb on Mi4c, but had it a few times on Nexus5.
Hope this helps...
Click to expand...
Click to collapse
Hallo,
thank you, that worked for me finally
I have now used another TWRP 2.8.7.1 with touch-issue, but that is now no problem.
I flashed also xiaomi.eu rom, for now seems to be stable and cleaned.
strange everything, but now it is fixed.
BR,
Jimmy
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine