My phone recently I have done a flash rom as usual, but all the problems started from this point. I miss miui 9 because it's stable and fast. I have downloaded the 9.5 mui flash on the OrangeFox Twrp. After that, I waited a long time. But the flash did not finish for a time I can't wait to do so. Press and hold the button to turn on twrp again and get back to miui 10 again. Yes, it's done.
And after that I started to flash my rom again because I broke my rom
I have to format
Now I can't flash any rom.
Most messages have failed to mount system or failed to mount data and are usually accompanied by error 7 while the flash rom
My friends told me to change twrp.
I try
twrp-3.2.3-0-vince
OrangeFox R9
OrangeFox R8.3-unified
PitchBlack
All are the latest versions. As far as I can find Of course, I can't solve the problem.
And I tried to edit the text in updater-script Which still does not work
And I have tried using MiFlash
MiFlash is used. I can go to Rom Dev, but I can not go to magisk. It caused me to bootloop and I made a flash. lazyflasher-no-verity-opt-encrypt But still not working
I have been using MiFlash continuously. Sometimes I wait 300 seconds and finish, but the cause of Bootloop is unknown or sometimes shows the system has been destroyed.
MiFlash. Maybe I use it. I waited more than 300 seconds until 1500 seconds. Nothing happened. I continued to do this and successfully, but not three cars. I did not have to go to the magisk as usual and caused Bootloop.
Lastly, I was able to use it, but my imei number is missing, so I can't use the SIM. I can format it to flash rom, but it's still not successful.
How should I solve this problem? Please help me I have tried many ways, please. :crying: :crying: :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was also having this problem, you need the twrp 3.2.3-1: https://drive.google.com/file/d/167Uoh8Zi7km6eGIZdg3PS9HDhi7a5W_d/view
I'm sorry for the strange English. I use google translate. Hope you guys understand my problem.
I will experiment with rom miui_HM5PlusGlobal_8.11.15_dd40bfa136_8.1_2
joelzombie said:
I was also having this problem, you need the twrp 3.2.3-1: https://drive.google.com/file/d/167Uoh8Zi7km6eGIZdg3PS9HDhi7a5W_d/view
Click to expand...
Click to collapse
It doesn't work
I experimented with miui_HM5PlusGlobal_8.11.15_dd40bfa136_8.1_2 and crDroidAndroid-8.1-20190221-vince-v4.7.2
As far my experience goes, looks like you messed up your partitions. Look for a tutorial to recreate partitions from scratch.
What do I have to do? Can you teach me
bot88 said:
As far my experience goes, looks like you messed up your partitions. Look for a tutorial to recreate partitions from scratch.
Click to expand...
Click to collapse
Now imei number is missing and the auto reboot symptoms have happened. And if I do root, it will cause bootloop symptoms
not6248 said:
Now imei number is missing and the auto reboot symptoms have happened. And if I do root, it will cause bootloop symptoms
Click to expand...
Click to collapse
Imei number missing means you lost efs partitions. This is the first partition to backup after installing custom recovery. These partition can also be backup by adb. sorry to say you messed up real bad,
And how do I have to solve
bot88 said:
Imei number missing means you lost efs partitions. This is the first partition to backup after installing custom recovery. These partition can also be backup by adb. sorry to say you messed up real bad,
Click to expand...
Click to collapse
I have no intelligence
not6248 said:
I have no intelligence
Click to expand...
Click to collapse
sorry bro, but i have no experience in this kind of situation.
but here is a link which may help https://xiaomifirmware.com/guides-and-tips/how-to-restore-redmi-5-plus-and-fix-bootloop/
There's one solution. Fastboot flash any miui rom then Use orange fox recovery. ?
Related
Hello
I'm having problems finding the error causing the incorrect storage space being reported on my compact; 16GB instead of 32GB. Has anyone encountered this before?
It's definitely something I am doing with adding the recovery - as a virgin 32.3.A.0.376 flash reports 32 GB correctly.
I've tried rootkernel 5.23, and the androplus kernel, and also with and without root/SuperSU. Previous installation of TWRP 3.0.2 on 32.2.A.0.305 with SuperSU displayed correct storage spaces with my Device Key intact.
Is anyone able to give me a hint as to what I should be looking for? I might try again and this time check with SD Maid or Apps2SD what the filesystem is doing once it does it's Google first boot setup. I was using TWRP in recovery and the default Storage Menu in Nougat settings to check previously.
Thanks
Just reverted to Marshmallow and it's interesting that it now reports 16GB. I have no idea what is happening
NeoBeum said:
Just reverted to Marshmallow and it's interesting that it now reports 16GB. I have no idea what is happening
Click to expand...
Click to collapse
happened with mine on both marshmallow and nougat, tho it corrected itself after a few restarts
Ok, thanks. I don't know if I'm game enough to test to see what happens if I fill up my marshmallow internal storage beyond 16gb, backup, flash Nougat, and revert... I'm curious though
Is there anything out of place in this? I'm new to Linux, I only just installed Ubuntu on my laptop today, and am learning
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know why it's doing this now... a moderator can delete this thread - tis related to TWRP + Nougat + Rootkernel
Had the same problem. I could solve it:
I flashed the stock rom. Then I restart mobile phone. Then flash the kernel and TA...
When i dont start the phone between flashing rom and kernel, then it's always 16 gb...
f4t1 said:
Had the same problem. I could solve it:
I flashed the stock rom. Then I restart mobile phone. Then flash the kernel and TA...
When i dont start the phone between flashing rom and kernel, then it's always 16 gb...
Click to expand...
Click to collapse
ah ok... i might look at what the persist files are doing in TWRP, i think when you do a restart, after the stock rom is flashed, it creates the data partition for the internal.
in the current build for rootkernel and twrp - i think it needs a prexisting directory
NeoBeum said:
I know why it's doing this now... a moderator can delete this thread - tis related to TWRP + Nougat + Rootkernel
Click to expand...
Click to collapse
Not a Nougat specific problem, it can happen on MM too. Speaking from experience.
I'm going to put TWRP on to a Virtual Device as part of my mini project... I just made a Z5 Compact skin for Android Virtual Device Manager
In twrp one can select data and or system, to repair, don't wipe it!
There one can press also repair and or resize wich may help. Maybe reboot needed but it has helped me before, also with nougat
The permission and partition information is not always correct during both format and wipes, that's the problem
jutphaas said:
In twrp one can select data and or system, to repair, don't wipe it!
There one can press also repair and or resize wich may help. Maybe reboot needed but it has helped me before, also with nougat
Click to expand...
Click to collapse
Jutphaas is correct, if you are performing a DRM fix with Root procedure via fastboot and TWRP then the wrong drive size will be stored. Booting into TWRP, advanced wipe, repair filesystem, resize filesystem, backing out and then going to install or somewhere else where you can select storage and selecting the onboard drive should now show the full amount of storage instead of the halved amount. This worked for me on Oreo, thanks Jutphaas.
Help! I just unbricked my Le Max 2, it reboots with the screen splitted into two, the left half on the right and the right half on the left. Please can anyone kindly help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after unbrick.
I use FlashOne 1.9 and a QFIL rom to unbrick it.
unbrick it again.
AhmadSant said:
unbrick it again.
Click to expand...
Click to collapse
re-unbricked, same result.
ok, can you do firstly reset factory, then try to install another rom.
AhmadSant said:
ok, can you do firstly reset factory, then try to install another rom.
Click to expand...
Click to collapse
factory reset and flashed another rom via fasboot, but reboot stuck at the start screen, just like the left one on the photo I submitted.
Do another unbricking, and everything back to the state I reported.
It's confirmed to be a hardware problem, when the monitor is replaced, everything back to normal.
I think there is problem with build.prop .. try google ... To restore build.prop
It seems that the Kernel is also affected so it must be hardware problem
hi did you solve this?
I have the same problem
KM141 said:
Click to expand...
Click to collapse
Hi, I have exactly the same problem after following the tutorial in here to get rid of the vendor encrypted god damn rom. Everything was working right before it so I don't buy the hardware issue. After flashing using flashone 2.0 I did ended up with my screen like this.
I tried several qfill file from severals sources and always the same result. I even try to go on and flash TWRP and RR rom but screen stay that way.
Please, I'm seriously desperate right now... I need your help guys and looks like i'm not the only one.
KM141 said:
Click to expand...
Click to collapse
Bambulbizarre said:
Hi, I have exactly the same problem after following the tutorial in here to get rid of the vendor encrypted god damn rom. Everything was working right before it so I don't buy the hardware issue. After flashing using flashone 2.0 I did ended up with my screen like this.
I tried several qfill file from severals sources and always the same result. I even try to go on and flash TWRP and RR rom but screen stay that way.
Please, I'm seriously desperate right now... I need your help guys and looks like i'm not the only one.
Click to expand...
Click to collapse
It was solved without replacing the screen!
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!) and not from one installed
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
For complete version :
https://forum.xda-developers.com/showpost.php?p=74890577&postcount=138
Bambulbizarre said:
It was solved without replacing the screen!
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!) and not from one installed
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
For complete version :
https://forum.xda-developers.com/showpost.php?p=74890577&postcount=138
Click to expand...
Click to collapse
To put a file on the phone while in twrp just use adb push
KuranKaname said:
To put a file on the phone while in twrp just use adb push
Click to expand...
Click to collapse
That's what I tried but as stated in the last link, I had no connection to adb while in twrp after cleaning up.
Anyway that's settled for me, it's mor for other that have encountered this as well. Replacing screen is not the only way.
It has reached me a Mate 10 Lite with error when unlocking the Bootloader ... once made it sends you to the custom recovery TWRP but it shows in its description that they wipe the system and do not load it, I have tried to recover with backups uploaded by other users but it does not ... someone has gone through this ... and what suggestion they give ... The same does not allow to install the Stock recovery, to use the file update.app ... Nor does it allow to i
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nstall other types of recoverys.
Try a different twrp that has helped me kingmezi is working for my but keep in mind you need to format data (and check the mount setting and swipe to modify at start)
Thks
KOALAaufPILLEN said:
Try a different twrp that has helped me kingmezi is working for my but keep in mind you need to format data (and check the mount setting and swipe to modify at start)
Click to expand...
Click to collapse
Thanks for the answer, but it does not allow as the previous message says ... it does not allow to install any type of recovery either stock or custom ...
It does not allow to mount any partition, Boot, Recoery, etc ... from the TWRP Menu
Unlock bootloader install via command
thks
I do not think I'm spying.
1. The Bootlaoder even if it is released ... it sends you immediately to the TWRP ... once inside it says no OS installed, and it does not allow doing anything because it does not load any of the partitions.
2. Even if you release the Bootloader, it does not allow you to install another type of TWRP ... nor restore backup files ... it only allows you to flash the different OEMINFOs as if it were a rebrand.
KOALAaufPILLEN said:
Unlock bootloader install via command
Click to expand...
Click to collapse
Then you might try dc phoenix but its not free
That can install even if you have a locked bootloader firmware or even if you are bricked like your cellphone
you can download the latest firmware without problems googe it and try it (cost about 15dollar to unbrick)
If the twrp dont work cause the parameters are wrong what twrp are you using we have here 3 differents for the Huawei if im right try kingmezi twrp its working fro my l21-b432 i think it was
Thks
I managed to install another custon recovery, that allows to see the partitions, and that the team has a system ... but at the time of restart the bootloader error comes out ... and giving low CMD fastboot has the same unlocked ... perfect ... when I send the command fastboot flash (Boot, recovery, recovery2) it says Failed ... and I can not install the recovery stock.
P.S: Thanks for the advice of DC Phoenix ... I had seen it and I will try ...
KOALAaufPILLEN said:
Then you might try dc phoenix but its not free
That can install even if you have a locked bootloader firmware or even if you are bricked like your cellphone
you can download the latest firmware without problems googe it and try it (cost about 15dollar to unbrick)
If the twrp dont work cause the parameters are wrong what twrp are you using we have here 3 differents for the Huawei if im right try kingmezi twrp its working fro my l21-b432 i think it was
Click to expand...
Click to collapse
solved?
hi men, please you can solved this?, i have de same problem
Hi, I am a K20 Pro, China Variant (6,128GB) User wanna share a horrible experience that happened with me.
let's start from the beginning. I was trying AOSP based rom because I wanted to leave MIUI.
I was happy with Evox rom. Then One day I have found Corvus OS 7.5 review , comes with OSS Vendor.
So I have flashed Corvus with OSS Vendor it was really awesome. I have never experienced that much smoothness in k20 Pro.
Then I thought Lets try F1Xy kernel. Mistakenly I have flashed The LOS FOD and boom.
My Raphael stucked into OrangeFox Recovery. I have tried Flashing F1xy with Mi9 FOD , No help. Booting into Recovery.
I had Evox Backup, Tried restoring the Backup, the backup included everything, kernel, model bla bla bla.
But even after restoring my phone was booting into recovery.
Then I thought Lets clean flash.
I have clean flashed Xiaomi.EU rom, Evox, Corvus and guess what it was still booting into recovery only.
I have wiped internal too. No help. everytime I have flashed rom I have also flashed DFE and Magisk.
Then I have Flashed Latest MIUI fastboot rom using Mi Flash Tool.
Guess what Its still booting into recovery. This time stock Chinese recovery.
Then I have flashed official TWRP, XiaomiEU rom. And phone just booted .
Then I have seen only 32GB INTERNAL storage . I was like what the haak.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Than I have fixed the internal storage using this command.
if you are rooted, get a terminal app such as termux then:
1. su (press enter)
2. Press grant when asked
3. resize2fs /dev/block/bootdevice/by-name/userdata (press enter again)
or do this in recovery, but skip 1 and 2
Thanks Superuser1958 for helping me on this.
So what was wrong? why my phone was booting into recovery even after clean flash
i do think every oss does not support custom kernels and its the inly idea i can think of
I recieved two complaints from other users have the same experience but with PE rom.
I'm assuming its the f1xy kernel issue. (haven't been active enough to confirm.)(I could be completely wrong here)
Anyways, I'll let superuser1958 (tg username) aka @joshuah1971 (xda username) confirm.
glad you got it fixed. Is everything else working perfectly?
(and v190 is known to be broken, so anything other than that.)
If it's making modifications that survive a clean_all MiFlash that's worrying. Nothing should be messing with device partitions.
Something similar happened with a Magisk mod. "FDE AI" if I remember correctly. Irreversibly mangled some Mi9T/K20 handsets and wasn't fixed by clean_all.
I do wonder whether EDL would be more thorough in putting devices in a factory state - but it's locked off. Heck, I'm astonished that today's devices can still be screwed up.
phones partition was somehow fked up and i bet even developer of the kernel couldnt say how, as it didnt even booted after clean flash from miflash tool that author states. Something similar happened to me when i was experimenting with kernels on different roms on redmi note 7 , firstly i was not even able to mount any storage and didnt see any partitions then reduced its size by half and only edl saved the day. it was predator kernel when issues started.
need helpi too having same issue how to resolve this, stuck on with orange fox and in computer there are three internal storage showing up of 107gb
I just want to finally try and install a custom rom into my Mi A3 which I rooted a while ago. I know I need this tool called TWRP, after encountering a myriad of errors trying to follow this guide step-by-step, I finally got to the point when I need to type "fastboot boot twrp.img" to boot into TWRP temporarily. But alas that couldn't be so easy now could it... Now I get this thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it's 11:41 PM and I'm about to burst a vein. I made an account solely to make this post because I can't seem to get an actual answer anywhere else... Any ideas before I give up?
is the bootloader unlocked ?
i think i got same message and it was because i forgot this.
I think there are better guides. Not sure what state your system is in. I would re-install the stock rom and start afresh. Unlock your bootloader, check which slot 'a' or 'b' is the current slot, and then follow the instruction of the Custom ROM you are trying to install. It might need TWRP but Lineage Recovery is equally as good.
#1jonna said:
is the bootloader unlocked ?
i think i got same message and it was because i forgot this.
Click to expand...
Click to collapse
Yes sir it very much is, don't think it'd have been possible to get this far otherwise
bjlabuk said:
I think there are better guides. Not sure what state your system is in. I would re-install the stock rom and start afresh. Unlock your bootloader, check which slot 'a' or 'b' is the current slot, and then follow the instruction of the Custom ROM you are trying to install. It might need TWRP but Lineage Recovery is equally as good.
Click to expand...
Click to collapse
how do I do this?
2. does Lineage Recovery even work on Mi A3s? I don't find anything about this device on their website
Follow the guide in the thread 'Slot A is destroyed'.
bjlabuk said:
Follow the guide in the thread 'Slot A is destroyed'.
Click to expand...
Click to collapse
I assume this means I can just go back to magisk and hit restore images, then return to fastboot and switch to slot b and install twrp there?
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ said:
View attachment 5554333
I assume this means I can just go back to magisk and hit restore images, then return to fastboot and switch to slot b and install twrp there?
Click to expand...
Click to collapse
As I said, as I am not sure what state your system is in I would suggest 're-installing' the stock rom from your PC, rather than 'restoring' an image from your phone. If you have backed up your data etc (eg on Google Drive) you can restore it after you have re-installed the stock rom. You can then start again from scratch.
The latest stock rom fastboot images can be found here
https://xiaomifirmwareupdater.com/miui/laurel/
Tbh I haven't restored an image from magisk myself so I can't confirm what you are proposing, though yes I switched to slot b and installed TWRP.
You might also want to read this article on A/B partitions
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Try this
https://play.google.com/store/apps/details?id=com.smartpack.smartflasher
Flash TWRP installer through the app
Just a few tips when you do get to TWRP:
Disable dm-verity
Format data and wipe cache after you flash the new rom before first boot
Use a patched boot method instead of flashing magisk in TWRP on custom ROMs. High chance of soft brick.
DM me if you need help.