My TMo springboard became almost useless, so - with TWRP installed - I decided to reformat system, data and cache, in the hope that the external SD would suffice to boot out of or mount a new image. No go.
I am now stuck in a loop, as follows:
- Huawei main logo
- Original lock screen
- slide to unlock
- message: "encryption unsuccessful... Data on your tablet no longer available... To resume using your tablet you must performance à factory reset...", which I opt for (choice named "reset tablet")
- Huawei mediapad logo
- teamwin splash screen
- TWRP trying to mount all sorts, but fails on all, of course
- back to Huawei mediapad
- back to Huawei main logo... and repeat all of the above
Any way I could break this cycle, by making an image available to TWRP? How? I don't seem to be able to use any touch screen or buttons to stop and a better change the options of TWRP. It just keeps trying to mount the default assumed partitions, nowhere to be found...
Sent from my SGH-T999 using Tapatalk 2
netfortius said:
My TMo springboard became almost useless, so - with TWRP installed - I decided to reformat system, data and cache, in the hope that the external SD would suffice to boot out of or mount a new image. No go.
I am now stuck in a loop, as follows:
- Huawei main logo
- Original lock screen
- slide to unlock
- message: "encryption unsuccessful... Data on your tablet no longer available... To resume using your tablet you must performance à factory reset...", which I opt for (choice named "reset tablet")
- Huawei mediapad logo
- teamwin splash screen
- TWRP trying to mount all sorts, but fails on all, of course
- back to Huawei mediapad
- back to Huawei main logo... and repeat all of the above
Any way I could break this cycle, by making an image available to TWRP? How? I don't seem to be able to use any touch screen or buttons to stop and a better change the options of TWRP. It just keeps trying to mount the default assumed partitions, nowhere to be found...
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you have TWRP installed you can simply download one ROM (CM10, CM10.1 or AOKP) in zip format and flash it from TWRP.
Just follow instructions on the DEV board.
GuZuRa said:
If you have TWRP installed you can simply download one ROM (CM10, CM10.1 or AOKP) in zip format and flash it from TWRP.
Just follow instructions on the DEV board.
Click to expand...
Click to collapse
Thank you. This is what I was hoping to hear
Would that work with an image from the external SD card (i.e. would the TWRP "see" the SD card and search for the zip file on it)? I am asking vs just trying it, because I only have one microSD, which is presently in my SGIII, so I thought of checking this before I start backing up my SD, clean it up, getting the CM 10.1, putting it on ... )
Thx again!
netfortius said:
Thank you. This is what I was hoping to hear
Would that work with an image from the external SD card (i.e. would the TWRP "see" the SD card and search for the zip file on it)? I am asking vs just trying it, because I only have one microSD, which is presently in my SGIII, so I thought of checking this before I start backing up my SD, clean it up, getting the CM 10.1, putting it on ... )
Thx again!
Click to expand...
Click to collapse
Replying to myself - I did copy the zip file to the microSD, but TWRP keeps trying to mount - at least apparently, to me - only the "known" partition (/data), then just fails and the mediapad goes back into reboot. Is there a sequence of keys that force TWRP to stop, and point it to the microSD, instead?!?
Any pointers will be appreciated.
R: Springboard w/out system or data
netfortius said:
Replying to myself - I did copy the zip file to the microSD, but TWRP keeps trying to mount - at least apparently, to me - only the "known" partition (/data), then just fails and the mediapad goes back into reboot. Is there a sequence of keys that force TWRP to stop, and point it to the microSD, instead?!?
Any pointers will be appreciated.
Click to expand...
Click to collapse
Try this:
1 reinstall TWRP with after_silence automated installer (shouldn't be necessary but... who knows?)
2 turn completety off MP by pressing on/off switch for a while (MP will shortly vibrate and turn off)
3 format a microsd in fat32 with a PC windows or linux
4 put the zip file of one of the ROM in dev board on the SD through the PC
5 insert microsd into MP
6 boot into TWRP. From device turned off, turn it on pressing on/off switch and volume up and keep volume up pressed until you see TWRP logo
7 reinstall Rom following instructions in the Dev board
Let me know....
Inviato dal mio Huawei MediaPad con Tapatalk 2
GuZuRa said:
Try this:
1 reinstall TWRP with after_silence automated installer
<snip>
Click to expand...
Click to collapse
Thank you for the reply. I pretty much already did all the steps you previously posted, except for "1." (reinstalling TWRP). I did a search for after_silence automated installer, but could not find any links to such - could you, please, post one?
Thx...
netfortius said:
Thank you for the reply. I pretty much already did all the steps you previously posted, except for "1." (reinstalling TWRP). I did a search for after_silence automated installer, but could not find any links to such - could you, please, post one?
Thx...
Click to expand...
Click to collapse
And I just noticed that TWRP continues running OpenRecoveryScript every time, which ends up trying to mount /data (unsuccessfully), wiping cache, reformating ext4fs, end then rebooting ...
netfortius said:
And I just noticed that TWRP continues running OpenRecoveryScript every time, which ends up trying to mount /data (unsuccessfully), wiping cache, reformating ext4fs, end then rebooting ...
Click to expand...
Click to collapse
One more update - I was able to get the system enough to run a:
$ fastboot flash system system.img.ext4
which worked just fine, but upon reboot TWRP takes over and starts again ... mount /data ... failure ... reformatting ...
Any ideas here on how to break this cycle?
huawei boot loop, fastboot mia
I followed the after silence cm install steps but failed at using fastboot to install the twrp image
adb connects fine & triggers a reboot into fastboot, then fastboot can't communicate so I installed the twrp recovery via goomanager
booted into twrp, made a backup, wiped system / cache / data (oops?)
tried to install cm10.1 and it said error in file
tried to reboot into recovery and now stuck on huawei logo, fastboot still kaput
anybody know why fastboot won't communicate or what I can try next???
update:
got back into twrp by holding power and vol up buttons until it reset, then releasing power while continuing to hold vol up
it appeared to loop several times then booted into twrp
Formatting the data partition was the culprit, methinks. I managed that, too.
You need to flash the third bootimg from After Silence´s Toolkit, not CWM and not TWRP. Then you can flash stock roms via a dload folder on the sdcard. Reflashing the already installed Comec v2 lite caused the aforementioned encryption error and before ending with an unrooted stock rom i tried CleanICE v1.5. Worked. Whether this rom is buggy or there just went something wrong during install, it didn´t contain the system app "networklocation.apk", so no wifi or 3g based localization would work, only gps, which is unavailable in my home. So i installed TWRP again and could successfully flash AOKP. Flashing AOKP directly after bricking wouldn´t fix the brick.
Related
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Try this
SarahAnne said:
So I followed this guide to install CM10 on my nook tablet http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1
Went great except now whenever I boot up my nook tablet it goes directly to clockwork recovery. There is currently no microsd card in the nook tablet.
I have also tried using AOKP from here: http://forum.xda-developers.com/showthread.php?t=1975214 and I have the same issue.
I also tried this build of AOKP http://forum.xda-developers.com/showthread.php?t=1641145
Click to expand...
Click to collapse
Try this : http://www.mediafire.com/?4s77jvehqvsuruu
1)Download it
2)put the files ( flashing.boot Mlo etc...) on your sdcard,
3)completely turn off your nook ,
4)put your sd card on nook and turn it on.
5) press the ''N'' button when you see ''cyaogenboot'' (it also saids press ''n'' button for BOOT MENU)
6) in Boot Menu just choose option #1 (Internal Boot) it should boot into cm10
I had the same issue, but after a time (after making some supid things) i bricked my tablet, I figured this out with some help, It worked for me so it should work for you too.
So I was able to randomly boot into the bootloader and boot into CM but now it keeps rebooting into clockwork.
I have also attempted installing CM10 using the following link including using the flashable_fix_bootloop.zip that I cannot sadly can't link to due to being a new user
and the only difference is that now CWM went from blue accents to orange.
The function of flashable_fix_bootloop.zip is to reset BootCnt counter and BCB flag (see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1) in the event they do not get reset properly in some installation/recovery process. It seems that your "recovery boot-loop problem" might have a different underlying root-cause, hence re-setting these counter+flag by itself will not cure the problem.
Which particular build version of CM10 and AOKP ROM did you try?
Also, did you do "wipe data & factory reset" & "wipe cache" as part of the ROM installation?
Have you tried reflashing the ROM once you're in CWM? (As I underestand you may have, but just making sure!)
Maybe download it again (or try another one) and the flash it again (after the usual wipes) with your new recovery.
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
SarahAnne said:
I took your advice and attempted to reflash. I did a factory reset, wiped the cache, then installed cm_acclaim_10.1_21APR2013_17_HD.zip and gapps-jb-20130301-signed.zip and I have the same problem. I continue to boot back into CWM
Click to expand...
Click to collapse
When you boot from the SD card have you tried holding down 'n' to get to the menu then selecting SDC boot? It should boot cm10.1. Try selecting SDC recovery also and see what it does. You might be doing something wrong during the process.
You can also try renaming your boot file for cm10.1 to altboot. Then try it.
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
SarahAnne said:
I am not attempting to boot off of SD, I am trying to install the zip files that are stored on SD to the internal memory. Holding down the "n" button just brings up CWM as it did before. I also downloaded an image designed to be booted off SD and renamed it to altboot like you suggested and it booted directly into CWM again.
Click to expand...
Click to collapse
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
DavDoc said:
May be nothing, but what version of CWM do you have on your NT, will be at the top of the screen in recovery?
Click to expand...
Click to collapse
6.0.3.1
SarahAnne said:
6.0.3.1
Click to expand...
Click to collapse
Still may be a shot in the dark, but try downgrading CWM to an earlier version, but not so early as to be unable to flash CM10. Maybe 6.0.2.5 to 6.0.2.9
Not ensuring this will work but it may be worth a shot. At least it won't put you in any worse condition than what you are in now.
Good Luck
Another thought, did you make a backup of your last ROM before flashing CM10? If you did I would assume you tried flashing your backup already, but have to ask.
It looks like you may have used two different builds of CWM based on one of your earlier posts - change of font color.
You also try the repart image if you don't have a stock backup. Find it on raywaldo site. It will re write your internal storage with stock ROM. Then flash cm afterward.
Woot I got the factory rom reinstalled, time to install cynogenmod again
I had the same problem
This worked:
digixmax said:
You should try to use SD-based CWM and flash "flashable_fix_bootloop.zip" posted at http://iamafanof.wordpress.com/category/cyanogenmod-2/.
Click to expand...
Click to collapse
However I was still unable to install any 4.2.2 ROMs + gapps.
I was on cwm 6.0.2.8 (or whatever the exact numbers are)
updated to cwm 6.0.3.7
wipe data
install rom
install gapps
wipe cache
wipe dalvik
everything works now.
Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Gorkytje said:
Maybe someone can help me here. Using TWRP 2.8.0.1 I am unable to fully install any rom.
I had slimkat on my phone and decided I wanted to try regular CM 11. So I wiped everything in advanced wipe so I could start fresh.
Put the Rom and Gapps on my phone then tried to flash.
However while installing CM, it just goes about its business until the progress bar hangs at updating partition details.
It also appears I cannot move files to the internal memory from the sd card.
Are my partitions messed up?
All that happens now is getting stuck at the samsung boot logo or rebooting into TWRP...
Any help?
Click to expand...
Click to collapse
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
tallman43 said:
Yes partitions could be mixed up but my first port of call would be to return to stock with odin and if that boots and works then start again and don't use twrp try PhilZ recovery.
If partitions are corrupt there are things you can try but I would first try to get your phone to boot then report back.
Click to expand...
Click to collapse
Thanks for your help! Because of you I tried PhilZ, which then told me it couldn't successfully open/read the rom from the SD card. (Something twrp didn't tell me).
I then changed my SD card for another one I had laying around and it worked. (Strange the old one failed since I formatted it atleast a few times)
Once again, thanks for your tip!
This is now solved!
SOS!
Two months ago, my phone ran into "Permanent Headphone mode", i.e. for all the sound apps, it displays headphone icon and no sound from speakers. Worked fine with headphones on, even no severe issues with the hearing speaker during calls.
Remedies applied: (X=Didn't work)
1- Tried with deleting cache. X
2- Did factory reset. X
3- Disassembled phone and removed the headphone jack, to check if it work. X
4- Unlocked bootloader, and rooted device. X
5- Tried wiping cache partition and dalvik cache, from TWRP. X
The last attempt of wiping dalvik cache and cache, did some disaster, and now on rebooting, it has stuck on "Android is starting... Optimizing apps x of 57"
I further tried resetting it to factory from TWRP recovery, it went further degraded, and on reboot stuck to Motorola boot animation, and didn't move further.
I lastly tried booting it to factory from fastboot, and this time on reboot, it has stuck at "Android is starting... Optimizing apps x of 71"
And I have disabled the USB debugging option during last successful boot.
Please help me out, I want to experiment further with custom ROMs and development. But if my phone won't work, I can't move further. Any help is appreciated.
I was using Lollipop, update provided by Motorola.
Edit:- It worked with new stock ROM, however that headphone issue is still unsolved.
Here http://forum.xda-developers.com/showthread.php?t=2755857
You'll find stock lollipop firmware images plus there's a guide too on how to restore it.
-z3r0- said:
Here http://forum.xda-developers.com/showthread.php?t=2755857
You'll find stock lollipop firmware images plus there's a guide too on how to restore it.
Click to expand...
Click to collapse
Hi, is there any other way, apart from flashing it with stock ROM?
Try this.
Do this1) Power off your phone
2) remove the sd card
3) Use a card reader and copy paste the rom and gapps file from your pc ( if you have one)
or download rom and gapps from device and move thm in your phone Or boot into recovery i.e TWRP and plug in USB cable and
copy paste the rom and gapps file from your pc
4) Insert the memory card back
5) Boot into recovery by pressing "VOLUME DOWN and POWER KEY"
and flash the ROM and gapps
DONE!!
MaddySayaji said:
Do this1) Power off your phone
2) remove the sd card
3) Use a card reader and copy paste the rom and gapps file from your pc ( if you have one)
or download rom and gapps from device and move thm in your phone Or boot into recovery i.e TWRP and plug in USB cable and
copy paste the rom and gapps file from your pc
4) Insert the memory card back
5) Boot into recovery by pressing "VOLUME DOWN and POWER KEY"
and flash the ROM and gapps
DONE!!
Click to expand...
Click to collapse
Hi Sayaji, Thanks for your prompt response. I have downloaded firmware from the link, I have got by Z3ro above. I have TWRP installed, and it is taking me into recovery. Now I have transferred the firmware into SD card. So now shall I install it like I did Super Su?
theankush said:
Hi Sayaji, Thanks for your prompt response. I have downloaded firmware from the link, I have got by Z3ro above. I have TWRP installed, and it is taking me into recovery. Now I have transferred the firmware into SD card. So now shall I install it like I did Super Su?
Click to expand...
Click to collapse
It failed through TWRP. So tried with fastboot. It flashed successfully. However, now after boot, the device is stuck at Moto Logo. Will keep this thread updated.
theankush said:
Edit:- It worked with new stock ROM, however that headphone issue is still unsolved.
Click to expand...
Click to collapse
Maybe you've got a hardware issue bro.
Factory Firmware Images(those *.bin and *.img things) are restored through fastboot mode only.
However recovery flashable zips called ROMs are flashed through recovery.
( Here you'll find some roms - Give them a try )
Bro I think it's a hardware issue use 'sound about' app......it will Chanel audio through phone speaker
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
Take a cloth put some alcohol on it and clean your headphones jack with the cloth.... After that pug the earphone which are provided by Motorola in the phone ....and keep it in same way for around two hours then remove earphone...... And check if problem is solved
Soft bricked: USB debugging was disabled, What to do, stuck at Moto logo
Hi,
I have got an issue, after my previous repair, I have installed custom ROM. Which was working fine till now.
Yesterday my cellphone got battery dead. Now whenever I am booting it, it stucks at Moto Logo.
Tried cache wipe, dalvik cache wipe, fixed permissions, factory reset.
All in vain, none worked. Moreover, when trying to fastboot the recovery.img for custom ROM, it is not detecting USB, I believe that is due to USB debugging disabled. Need help here.
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Lazer Bear said:
Hey all,
I've got a N7105 (Galaxy Note II LTE) running CM12.1 and TWRP which I was planning to change shortly as it's old and the USB port has issues (charges but doesn't pass data; luckily it has a microsd slot). As it happens, the other day I left it discharge fully and turning it back on left it stuck at Samsung logo (not boot animation, the splash screen before it) forever.
I am: not a noob, I've rooted and flashed plenty of devices before.
I tried: removing battery for a while, charging fully, removing microsd and sim, clearing Cache and Dalvik. Nothing works.
I can: get into ODIN mode (but it's useless as USB data is not working); get into TWRP recovery; explore the Data partition in TWRP
I cannot: mount the System partition in TWRP, not even manually. It just does not let me select it, and gives an error whenever it needs to access it (e.g. if I try to backup it is says Error: unable to mount System)
I want: if possible to solve the issue without formatting Data. I had a TB backup but kinda old, so I got a Nandroid of Data and Boot out from TWRP and I suppose I could then recover stuff extracting from Nandroid through TB, but I've never done it and would rather be able to get a fresh TB backup and move on from there.
A few questions I have: any idea on why I am not able to mount System in TWRP? Could it help to reflash Boot or System, and if so how do I go to do that considering what I have is the whole CM rom package? (I remember being able to fastboot flash single partitions on Nexus devices but that's because the stock rom comes packaged in separate images).
Any input would be greatly appreciated!
Click to expand...
Click to collapse
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data ?
MigoMujahid said:
The note 2 has this issue that makes it unable to be recognized by PC, so this isn't your phone problem, the only way to solve it is replacing the usb socket in your phone, anyway i can recommend dirty flashing your rom first, just flash the rom in recovery and wipe cache and Dalvik cache only then reboot.
If that didn't work, I'm afraid you might have to...... clear data
Click to expand...
Click to collapse
Thanks for the input, I was thinking something along those lines but I wasn't totally sure, I always avoided dirty flashing as I heard of people having issues. Happily, it worked! Weirdest think I saw in a while, it gave me a bunch of errors with System partition (unable to mount, unmount, find), then it gave a "proceeding to patch system partition unconditionally", then it completed. The whole thing took less than 20secs so I do not think it even actually flashed the ROM. Now I am just getting some Play Services error, likely need to reinstall gapps, but phone boots just fine!
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
kishikaisei said:
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
Click to expand...
Click to collapse
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
mecoromeo said:
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
Click to expand...
Click to collapse
I tried that, now I am a step forward I think, I flashed the stock firmware I found, and installed the latest stock ROM, rebooted (doesn't say no os anymore), but the only thing I see is a DELETE ALL DATA button and at the bottom 'Encryption was interrupted and can't be completed. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.'
Darklouis said:
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Click to expand...
Click to collapse
I have an issue with the MiFlash part, it seems that it doesn't work as I mentioned...
Aight all, formatting data partition to ext4 worked, now it is booting
kishikaisei said:
Aight all, formatting data partition to ext4 worked, now it is booting
Click to expand...
Click to collapse
Works now?
mecoromeo said:
Works now?
Click to expand...
Click to collapse
So I had an OS-less phone that don't get recognised in MiFlash, and I had orangeFox recovery.
The steps to fix were:
- Flash a full stock Firmware
- Flash the stock ROM
- Flash DFE
- Format data to ext4
- Reboot and it works
So thanks all for your help