Related
Hello everyone, last night i was trying the PhilZ Touch CWM recovery and in the wipe section it has an option to format /persist and /firmware, so being very stupid i formatted those partitions and when i tried to install a new rom i couldn't connect to wifi, i fixed that with this http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308 and everything seems to work perfectly in stock rom, i must admit i was very afraid, but now i'm curious because i search a little and others phones have drm files or more folders (i only have a lost+found folder and to 2 more .bin archives) and i was wondering if any of you ever had done the same as me or know more about it and could help me if i'll have problems in the future for my stupid behavior. Thanks
kievam said:
Hello everyone, last night i was trying the PhilZ Touch CWM recovery and in the wipe section it has an option to format /persist and /firmware, so being very stupid i formatted those partitions and when i tried to install a new rom i couldn't connect to wifi, i fixed that with this http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308 and everything seems to work perfectly in stock rom, i must admit i was very afraid, but now i'm curious because i search a little and others phones have drm files or more folders (i only have a lost+found folder and to 2 more .bin archives) and i was wondering if any of you ever had done the same as me or know more about it and could help me if i'll have problems in the future for my stupid behavior. Thanks
Click to expand...
Click to collapse
/firmware = modem = flash NON-HLOS.bin from stock package.
And this is how /persist should look like:
Code:
[email protected]:/persist # find
.
./lost+found
./WCNSS_qcom_wlan_factory_nv.bin
./WCNSS_qcom_wlan_nv.bin
./sensors
./sensors/sensors_settings
./.bt_nv.bin
./prov
./prov/randomString1_
./prov/randomString1_/randomString2_
./prov/randomString1_/randomString3_
./prov/randomString1_/randomString4_
./prov/randomString1_/randomString5_
./data
./data/app_g
./data/app_g/randomString1_
./data/app_g/randomString1_/randomString6_
./data/app_g/randomString1_/randomString7_
./data/app_g/randomString1_/randomString8_
LuK1337 said:
/firmware = modem = flash NON-HLOS.bin from stock package.
And this is how /persist should look like:
Code:
[email protected]:/persist # find
.
./lost+found
./WCNSS_qcom_wlan_factory_nv.bin
./WCNSS_qcom_wlan_nv.bin
./sensors
./sensors/sensors_settings
./.bt_nv.bin
./prov
./prov/randomString1_
./prov/randomString1_/randomString2_
./prov/randomString1_/randomString3_
./prov/randomString1_/randomString4_
./prov/randomString1_/randomString5_
./data
./data/app_g
./data/app_g/randomString1_
./data/app_g/randomString1_/randomString6_
./data/app_g/randomString1_/randomString7_
./data/app_g/randomString1_/randomString8_
Click to expand...
Click to collapse
Thank you so much for the answer!, i only have ./lost+found ./WCNSS_qcom_wlan_factory_nv.bin y ./.bt_nv.bin, any idea what are the others for?
kievam said:
Thank you so much for the answer!, i only have ./lost+found ./WCNSS_qcom_wlan_factory_nv.bin y ./.bt_nv.bin, any idea what are the others for?
Click to expand...
Click to collapse
No, I dunno.
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
shouldn't you be flashing disable_encrypt zip too?
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
PROdelision said:
shouldn't you be flashing disable_encrypt zip too?
Click to expand...
Click to collapse
No, its not required.
chiplovez9x said:
repair or change file system option.Click on it..Click on repair and resize file system. I don''t get this one. There are a few options inside
Click to expand...
Click to collapse
Make sure you have allowed modifications on system partition and also you dont have system as read only.
Does fingerprint working on GSI?
what is gsi?
I don't know much but gsi means u can flash almost all roms (which have images). And most of ROMs do have gsi images.. So u can install any rom on your phone. I don't know the steps to do so.. ?
bryanngapopala said:
what is gsi?
Click to expand...
Click to collapse
Simple speaking it's a image with clear android from google
Has anyone tested RR PIE GSI on RN7? Does it work?
Is it possible to boot Android O GSI? :silly:
letsmakecakes said:
No, its not required.
Click to expand...
Click to collapse
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Is the. Method the same for the global version with global rom?
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Which GSI should be needed to take? A-only or A/B ?
PROdelision said:
here's everything i did:
on miui beta.....already encrypted.
did fastboot -w
flashed latest RR gsi via fastboot
booted to twrp, flashed magisk(v19), repair and resize
reboot
asks for decryption password
where exactly am i going wrong?
able to boot if im using decrypt zip but lockscreen doesnt work.
Click to expand...
Click to collapse
I have no experience with GSI images, but I know in general that PIE breaks the encryption, if you roll back the security patch level. I don't know it this happened in your case, but I have lost couple of times my encrypted storage when I have tried to restore a backup of rom with older android patch level. After that, the bootup encryption pin is no longer accepted, neither by android nor by twrp, so the only option is to format data to remove encryption and start from scratch.
Were your miui beta and rr gsi of the same android security patch level?
Getting WRONG PIN error after setting up pin ???
letsmakecakes said:
[GUIDE] STEPS TO FLASH GSI ON REDMI NOTE 7 [lavender]
Many of us tried Flashing GSI on our Redmi Note 7 but failed due to various reasons even though it is absolutely bugless for Redmi Note 7 .
Here are the steps which i will mention below that will let us use the full potential of GSI.
Requirements :
Bootloader Unlocked
TWRP Installed
Ofcourse a working device
Installation Method :
First of all we need the flash the latest chinese beta rom.It gets updated everyweek. Since I have the cn rn7 i prefer to update the vendor partition everyweek for fixes and latest updates.But you can try on your stable rom too (I can't gurantee if things will work out on stable rom or not) .So, first of all be on china beta rom.
Go to fastboot mode and connect your pc to your device .You need to have installed xiaomi drivers to make this work properly. Once you are in fastboot ,open a terminal/cmd and type : fastboot -w ( this will erase your existing system partition and data and internal storage too , so make sure to have a backup if you have something essential on ur device)
Now considering that we have already downloaded a gsi i.e a phh GSI ..now for this case we are gonna assume its aosp as an example.. while in the fastboot mode type : fastboot flash system system.img ( here system.img(it can be of different name too) is the gsi img which you download from phh thread).
Remember : once the flash is completerd reboot to TWRP and not to system.
Once you are in twrp , flash magisk ( flash magisk latest canary as it has support for system as root devices) then press on wipe button of twrp,,,then advanced wipe..then tick mark on system and you will see repair or change file system option.Click on it..Click on repair and resize file system.
Now go to mount settings and mount system partition. Now you can flash gapps if you want .
After flashing gapps finally reboot to system
Voila! After in about 5 mins you will be booted to GSI rom
Post Installation Method :
You will have almost everything working after booting into gsi except you will run into brightness bug which you can fix by the following way
Connect your device with pc and enable mass storage
open a cmd/terminal on ur pc
type the following codes : adb shell
su ( in this case you will have to give permission from your device ; grant it)
setprop persist.sys.qcom-brightness 4095
Congragulations Now you have installed a gsi perfectly on your device
In this way you can flash almost all the gsi available on phh thread Hope this clarifies all of our problems.
Hit Thanks if I helped you somehow with this
Click to expand...
Click to collapse
Hi!
Did you not disable dm-verity and force-encryption?
Another question, the dev MIUI roms contain both the system and vendor partitions, right? How do you install only the vendor partitions from them? Or do you just flash MIUI and then reflash the custom ROM system? In that case, won't that affect dm-verity and encryption on the data partition?
Flashing correctly a GSI like in this guide; with vendor ecc ecc, will gcam work? Actually i'm on stock MIUI 10 and obv all working fine with a perfect version. My doubt is it.
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Forever Alone said:
Getting WRONG PIN error after setting up pin ???
Click to expand...
Click to collapse
Did you not erase your /data partition through TWRP?
any recommended gsi rom with no bug?
booladi said:
Did you not erase your /data partition through TWRP?
---------- Post added at 03:06 AM ---------- Previous post was at 02:46 AM ----------
Did you not erase your /data partition through TWRP?
Click to expand...
Click to collapse
I did wipe userdata but not internal storage. heard its because i have unencrpyed data partition?
Hello everyone , I was wandering if someone could help me with this issue.
First My phone State and system :
I got an Unlocked k20 Pro , flashed with MIUI 12.0.2 Global (Mi 9T Pro) , rooted wigh magisk (Twrp of course too v3.4 ) , Encrypted storage too.
I am trying to edit some files in the vendor partition but all the changes I make get reversed back , tried everything , Partition mounted as R/W in root explorer , changing the SE Context , but it seems as if all my work is on memory only, and not commited to disk, and everytime I restart the phone it rolls back on how it was before.
Tried copying my edits through TWRP , same result , restart and changes are gone.
So my question is what is happening exactly ? and what should I do to edit the vendor partiton?.
Thought about DM-Verity , tried disabling it using different methods (flashing Universal Zip amd manual editing ) always end up in a bootloop.
The root seems only to allow editing system partition.
Are the files backed up? and then restored if edited ?
Thank you in advance
urbanmec said:
Hello everyone , I was wandering if someone could help me with this issue.
First My phone State and system :
I got an Unlocked k20 Pro , flashed with MIUI 12.0.2 Global (Mi 9T Pro) , rooted wigh magisk (Twrp of course too v3.4 ) , Encrypted storage too.
I am trying to edit some files in the vendor partition but all the changes I make get reversed back , tried everything , Partition mounted as R/W in root explorer , changing the SE Context , but it seems as if all my work is on memory only, and not commited to disk, and everytime I restart the phone it rolls back on how it was before.
Tried copying my edits through TWRP , same result , restart and changes are gone.
So my question is what is happening exactly ? and what should I do to edit the vendor partiton?.
Thought about DM-Verity , tried disabling it using different methods (flashing Universal Zip amd manual editing ) always end up in a bootloop.
The root seems only to allow editing system partition.
Are the files backed up? and then restored if edited ?
Thank you in advance
Click to expand...
Click to collapse
1.Mount vendor image in ubuntu pc... Edit and flash it.
2.In twrp edit in
/system/vendor
Confirm vendor partition mounted in twrp.
[email protected] said:
1.Mount vendor image in ubuntu pc... Edit and flash it.
2.In twrp edit in
/system/vendor
Confirm vendor partition mounted in twrp.
Click to expand...
Click to collapse
Thank you for the answer, however, and after doing some reading, the situation is much more complex, and might be, at the moment, not possible.
It might have something to do with miui dynamic partitons, and twrp not supporting it.(read only mode).
Also, mounting on linux wont work because the dedup ext4 , and unpacking repacking then flashing wont work because , at the moment, I found no way to disable DM-verity on miui 12.0.2(The phone will not boot).
I solved my problem anyway , via Magisk , I just created a module and done what I wanted.(Thats what magisk is for in the first place )
Hi, I have a redmi note 9 that I wanted to mod but I had a lot of problems modding it. I initially installed crDroid 8.7 but the control center animation was lagging and the battery drains fast, so I decided to change the ROM with Project Elixir (Android 12 all ROMs). I saw that crDroid 8.9 came out (September 22, 2022) and there had been some notable changes, as the battery did not run out anymore the animations were fluid, but i was not able to get working google apps.
I tried everything and it wasn't right. (Nik, OpenGapps, MTG nothing) indeed I installed the gapps I had on 8.7 and them didn't work .. So I decided to move to pixel experience android 12 but I had these problems:
On all the roms that I have installed (except I think MIUI) the system is encrypted. I tried flashing a zip, via commands, via recovery but nothing the system is encrypted. I can't access it and in addition I wanted to change the bootanimation but I can't move the zip because it says it's read only and following these commands too I couldn't do it:
adb root
adb disable-verity
adb reboot
adb remount
adb shell
mount -o rw,remount /system
for these commands i also used ADB Sideload (ofc) but also some zips
It says the /dev /<number>/block is read-only and I have not been able to unlock it. (I tried with all these recoveries: TWRP, SHRP (SkyHawk, OrangeFox [UNOFFICIAL but is only for A11]). (If I go from TWRP to sdcard / I have all the files encrypted. I have the phone rooted with magisk.
In addition, I also had problems formatting the phone because the system with both TWRP and SHRP was not deleted or if I restarted the phone after formatting the ROM would open again so to format it I used Pixel Experience which has worked very well so far.
But custom rom already have ability to rw
Anyway you're lucky there thread available google it like
Universal method to get rw
Idk. I have installed Project Elixir, crDroid and this Pixel Experience and are encrypted.
I already googled it....
/dev/* will be always read-only.
And how i can modify the boot animation? Files are encrypted and the zip is in /system/product/media/.zip
/dev/ and /system/ are not same.
Stock MIUI is system read-only.
If you want to mount system as read-write, you need "universal mount system r/w" by @lebigmac
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Oh ok, it will work on A12?
I'm not sure.
Ok so tried flashing systemrw_flashable (Universal RW) with sideload bcs i have crypted files.
This is the error that it gave me:
Extracting ...
There was an error extracting the file. Please install unzip and try again.
I tried flashing with SHRP (TWRP based) bcs twrp can't work with adb sideload (for me).
Edit: searched on xda the problem, i installed the BusyBox module in magisk (From Fox Modules Manager) but nothing to do, still same error.
Deltwin said:
Oh ok, it will work on A12?
Click to expand...
Click to collapse
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
But how can be you make sure without some beta testers you neef guys like me and this op who have device in hand to test it and give you feedback
lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
Oh so it cant work in sideload... Good tip if it will work u made a very good script
To be honest I've never used this sideload feature before... What are the advantages of sideloading versus flashing the .zip as usual?
Mr Hassan said:
But how can be you make sure without some beta testers you neef guys like me and this op who have device in hand to test it and give you feedback
Click to expand...
Click to collapse
That's a good idea. I should release an open beta before releasing the final program.
That way we can make sure it works on as many devices as possible
lebigmac said:
To be honest I've never used this sideload feature before... What are the advantages of sideloading versus flashing the .zip as usual?
That's a good idea. I should release an open beta before releasing the final program.
That way we can make sure it works on as many devices as possible
Click to expand...
Click to collapse
Thanks for appreciating the idea
Hope we'll get beta soon but is there any idea date how many days still need to release it
Ok let me show my progress
I make my vendor sys odm to ext4
And ser the logs according to logs
I have rw now
OnePlus8:/ # mount | grep "dm-0"
/dev/block/dm-0 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-19"
/dev/block/dm-19 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-3"
But the weird thing is still not able to edit
Any file in these parts.
lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
How i can run ur script directly from android?
Like on magisk?
Deltwin said:
How i can run ur script directly from android?
Like on magisk?
Click to expand...
Click to collapse
Hi. Please check the Manual Installation and Examples section of the thread in my signature
And if you're running Android 12+ don't forget to disable the sdkCheck() function in the systemrw.sh script file @ line # 425 like this #sdkCheck
It should work if your only problem is the shared_blocks read-only feature. If your device got the new erofs read-only protection feature then you must wait for next version of my script or try your luck one of the copycat imitations that are floating around.
Good luck!
So after an hard brick at work (so i leaved it for 5 hours with redmi logo on lol) and after many steps i reinstalled MIUI with root... it's running A11 so how i can install it? I need to disable the sdkCheck? I think no if you need it on A12...
Second question i need to flash it before the first boot or i can do it after the first boot?
Deltwin said:
So after an hard brick at work (so i leaved it for 5 hours with redmi logo on lol) and after many steps i reinstalled MIUI with root... it's running A11 so how i can install it? I need to disable the sdkCheck? I think no if you need it on A12...
Second question i need to flash it before the first boot or i can do it after the first boot?
Click to expand...
Click to collapse
I thought hard bricks were unrecoverable?
If your Xiaomi device is running Android 10 or 11 then you don't need to disable the sdkCheck() function in my old script.
Ok here are all the necessary steps in chronological order for you
unlock bootloader
flash stock ROM
install systemrw_1.32
root
debloat
customize
enjoy
No it's possible, i tought not but here i am with my redmi note 9..
jk apart i unbrick with SP Flash tool but i had other problems like NVRAM warning (it fixed automatically with updates idk lol..) and the IMEI was deleted but fortunately i had a flashable backup..
I need to flash the stock rom? I have pixel experience with A12/13
Edit: I tried to flash it (i have the file on the microSD) but it gave me this error:
There was an error extracting the file. Please install unzip and try again.
Well my script was designed for stock A10, A11 ROMs ( or A12 if you're lucky and your device only uses the infamous shared_blocks read-only feature + you must disable sdkCheck() function in script itself ) but I don't see why it shouldn't work on a custom ROM as well
Ok let me try this again but only because it's you
Boot phone into Android OS and make sure it's properly rooted
download the systemrw_1.32_BUNDLE_proper.zip and extract it
extract the systemrw_1.32_flashable.zip
copy the systemrw_1.32 folder into /data/local/tmp/ on your phone
open adb shell or terminal app and type
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
chmod +x ./systemrw.sh
./systemrw.sh in=`realpath /dev/block/by-name/super` size=50
Good luck!
So, I recently unlocked the boot loader of my phone, Redmi Note 11 (spes). The thing is due to water damage I had to change my Screen and certain components. Obviously to stay cheap, I installed a Third party Screen and Didn't care much. So today when I tried installing PixelExperience and other Cutom ROMs, Things weren't working like they should. It turns out, the custom rom kernel didn't have support to third party replacement screens. So I tried to root my MIUI Install and Backup certain files, like Kernel and other Stuff, so that when I install Custom ROMs, I can replace the new kernel with my backup kernel. While doing that I accidentally flashed a wrong image to the persist partition. I tried decompiling the official ROM, but didn't find any persist.img file, like literally it screwed up the whole Partition Table so bad, I can't even revert to orignal State. Here are the log files, which I think might help.
Custom ROMs use stock kernel (found in MIUI) due to lack of source code. I don't think the problems were kernel related, correct me if I'm wrong though
hadrbass89 said:
AFAIK Custom ROMs use stock kernel (found in MIUI) due to lack of source code. I don't think the problems were kernel related, correct me if I'm wrong though
Click to expand...
Click to collapse
well, the problem was kernel related indeed, because after i locked my phone and pressed the power to wake it, but touch input was acting like mouse hover. Also, I don't really care about this issue anymore, I just want my phone restored first. I want is, Someome upload their TWRP Backup here, so that I restore it to the Original Condition.
Can you use a fastboot rom ( MIUI )?
Also, if there is a way to run this command on a rooted terminal, like after booting a custom recovery:
Code:
ls -l /dev/block/by-name | grep persist
It should show you which block device has the persist partition. On mine it's sda2, I think.
Vagelis1608 said:
Can you use a fastboot rom ( MIUI )?
Also, if there is a way to run this command on a rooted terminal, like after booting a custom recovery:
Code:
ls -l /dev/block/by-name | grep persist
It should show you which block device has the persist partition. On mine it's sda2, I think.
Click to expand...
Click to collapse
I managed to find the persist.img, But still have other errors to deal with, like:
Failed to mount '/system_ext' (Block device required)
and other Messages as well like this for product vendor and system_root!
You know these fall under the super partition. And I am totally unable to fix these errors, even though I have the corresponding images from the miui payload.bin. But I will surely try your method to try to fix it. Thanks
arnv2004 said:
I managed to find the persist.img, But still have other errors to deal with, like:
Failed to mount '/system_ext' (Block device required)
and other Messages as well like this for product vendor and system_root!
You know these fall under the super partition. And I am totally unable to fix these errors, even though I have the corresponding images from the miui payload.bin. But I will surely try your method to try to fix it. Thanks
Click to expand...
Click to collapse
That command is to find the partition, not fix it.
You should try to flash a fastboot rom.
Better unlock the bootloader if you locked it.
Okay, So now I have system system_ext vendor product images with with. Now since, these fall under the super partition, how can I flash them separately?
arnv2004 said:
Okay, So now I have system system_ext vendor product images with with. Now since, these fall under the super partition, how can I flash them separately?
Click to expand...
Click to collapse
Find and flash the appropriate fastboot rom
Done! Flashed MIUI Back using the help of Telegram Community
Now its back to normal!