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.
Related
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. ?
Ok I started this thread in hopes that I could get some answers from someone more knowledgeable than me on these MTK phones.
I've been reading online about flashing these GSI roms but I've seen multiple different methods. Some say use TWRP others say fastboot, or should I use SP flash tools...? And what are the proper wipes to prep for GSI flash? I've seen some say wipe everything except internal and others say just wipe dalvik/cache, and still others that say you must wipe in stock recovery then flash and boot twrp to flash system image...? Can any Umidigi Pros enlighten us a little? I'm sure google will bring more people to this page in time...or not?
I have flashed some GSI ROMs but everyone I've tried I cant seem to get root with Magisk. Magisk shows to be installed but when root apps call for root it just sits there and times out and I never get the prompt to grant root. This means I can't edit the APN which means no data which is not an option.
PS I've tried posting over in Umidigi community but it seems like a ghost town over there and I don't want to hijack any of the other threads here for our device as none of them are related to this issue.
Here also seems to be a ghost town unfortunately.....
ogeid79 said:
Here also seems to be a ghost town unfortunately.....
Click to expand...
Click to collapse
Yeah unfortunately... It's a shame such a good phone is going to waste. I blame Umidigi
razen_kain said:
Ok I started this thread in hopes that I could get some answers from someone more knowledgeable than me on these MTK phones.
I've been reading online about flashing these GSI roms but I've seen multiple different methods. Some say use TWRP others say fastboot, or should I use SP flash tools...? And what are the proper wipes to prep for GSI flash? I've seen some say wipe everything except internal and others say just wipe dalvik/cache, and still others that say you must wipe in stock recovery then flash and boot twrp to flash system image...? Can any Umidigi Pros enlighten us a little? I'm sure google will bring more people to this page in time...or not?
I have flashed some GSI ROMs but everyone I've tried I cant seem to get root with Magisk. Magisk shows to be installed but when root apps call for root it just sits there and times out and I never get the prompt to grant root. This means I can't edit the APN which means no data which is not an option.
PS I've tried posting over in Umidigi community but it seems like a ghost town over there and I don't want to hijack any of the other threads here for our device as none of them are related to this issue.
Click to expand...
Click to collapse
There are several methods to flash the GSI:
1.- BY FASTBOOT
2.- FOR A PERSONALIZED RECOVERY (TWRP)
3.- FOR FLASH TOOL.
But looks like you've already flashed them.
But you have problems with the root, this is because the libdirect-coredump.so file was installed in the vendor folder and not in the system folder.
What you have to do is the following:
/vendor/lib/libdirect-coredump.so
COPIED TO
/system/lib/libdirect-coredump.so
and
*
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
drkiro said:
There are several methods to flash the GSI:
1.- BY FASTBOOT
2.- FOR A PERSONALIZED RECOVERY (TWRP)
3.- FOR FLASH TOOL.
But looks like you've already flashed them.
But you have problems with the root, this is because the libdirect-coredump.so file was installed in the vendor folder and not in the system folder.
What you have to do is the following:
/vendor/lib/libdirect-coredump.so
COPIED TO
/system/lib/libdirect-coredump.so
and
*
/vendor/lib64/libdirect-coredump.so
COPIED TO
Code:
/system/lib64/libdirect-coredump.so
Click to expand...
Click to collapse
Wow! I can't believe someone finally responded. So was this an error in the build or is there something I can do with the system image to correct it?
I still have this phone but I don't use it as my dd but I'd still like to know.
razen_kain said:
Wow! I can't believe someone finally responded. So was this an error in the build or is there something I can do with the system image to correct it?
I still have this phone but I don't use it as my dd but I'd still like to know.
Click to expand...
Click to collapse
If you have TWRP, ENTER MOUNT and mount the System partition and the vendor partition, with the TWRP file manager copy the files that I put before
I'm never able to mount anything in TWRP 3.2.3 or 3.2.3v2 on the OnePro, what am I doing wrong ?
targa said:
I'm never able to mount anything in TWRP 3.2.3 or 3.2.3v2 on the OnePro, what am I doing wrong ?
Click to expand...
Click to collapse
Are you getting errors when you attempt to mount them? They should be like "invalid argument" or something like that. In this case, you should use SP Flash Tools to flash the entire Eragon v2.5 OS with it's scatter file to your device, it -should- disable the encryption stopping you from tampering with /system and /data, and other partitions.
Also, I've been seeing people saying that you can't pass safetynet checks on the Umidigi One Pro, you can.
- Running Havoc OS 2.0
- Using Magisk v23 with modules: MagiskHide, MagiskHidePropsConfig
- Force BASIC key attestation spoofed to OnePlus 6
- Device Fingerprint spoofed to OnePlus 6
{
"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"
}
Something to note, I was not able to get the module Universal SafetyNet Fix working on the One Pro.
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
Hi,
I have a big problem.
My brother tried to root my Xtrons Px6 rk3399 gs. with Su user. He updated superuser. Now the radio is in the boot loop and it won't start. He then tried a new firmware to bottles which does not work either, the radio only shows the logo. I get into recovery. I just do not know how to go on:-(
it's the Xtrons PQ80UNV
Sorry for my english.
Greez
{
"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"
}
TF? Why would you want to root that?
Did you try factory resetting?
He said it would be better. then you have more options. Because of some sound patch, I don't know much about it. Factory reset? I pressed Restet button but no change. It doesn't just start the boot logo from Vw.
I don't even get to the Adroid. Only in recovery.
Did a wipe, but it still doesn't start.
You chose wipe cache partition. I meant "Wipe data/factory reset"
Try choosing it.
If your brother is the one who did this as you say, if it's me I'd force him to fix it or at least pay for it.
I tried that too. I also tried the original firmware here, but always the same.
Yandex
Finds everything
yadi.sk
Yes, that's right, he's currently doing assembly work. I'm really desperate :-(
What I noticed is that with every firmware I install it is always the same recovery version.
voxdie said:
What I noticed is that with every firmware I install it is always the same recovery version.
Click to expand...
Click to collapse
Can I ask how did you root it?
Unfortunately, I don't know. I only know that an rk3399 mcu was previously a gs version
voxdie said:
Unfortunately, I don't know. I only know that an rk3399 mcu was previously a gs version
Click to expand...
Click to collapse
I don't believe you can root a device and suddenly you forget about it...
Do you have unlocked bootloader? You may need to flash the stock ROM if you can find it.
It works again, I have now flashed the img instead of the ota. Now it works again. Great. Thank you so much for your help
voxdie said:
It works again, I have now flashed the img instead of the ota. Now it works again. Great. Thank you so much for your help
Click to expand...
Click to collapse
I don't think I did anything but happy to see everything work out fine.
Make sure your brother doesn't do something like that again.
NO, he can't get to this radio anymore .. thanks again
the UNIT you have, looks almost the same as ICE/HU/PBX89UNV ( except mine has android 9 ) XTRONS ? 64GB -4GB ?
correction- there are multiple versions of this exact same unit. (even one with a qualcomn)
yours has the HDMI out pigtail ?
firmware link -
word instruction -
codes to ENABLE DEVELOPER OPTIONS
To start debugging, enter adbon in the factory settings input password box
if you want to change the factory settings, boot image, etc,, enter 126 in the factory settings input password box.
may i ask fellow members , to root this ,
unlock boot-loader,
flash updated BOOT.img (magisk patched)
-- because this is android 9, do i need a BLANK VBMETA flash?
funny fact--- this unit, will BOOTLOOP if you put a 512GB micro SD card in the slot, it boot loop cycles..
(anything above 128GB causes issues )
the micro SD slot for MAP/GPS , --- can we use this for anything else ?
and does anyone know of there are any custom roms and or TWRP already built for this > (this should share similar/same across a few brands ?)
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.