Related
Please help me I was installing a custom rom cyanogen in LG D175F BRA and ended up catching him, then connecting the device after the logo of LG displays black screen Kernel Panic and not out of it, it does not come into download mode, or fastboot and the devices appears an unrecognized driver QHSUSB_BULK
If you have QHSUSB_BULK, you need a mmcblk0 backup at least till the end of the laf partition (first 166MB), which includes the partition table.
Ask for someone with the same model and rooted to run this command @ android terminal or adb:
su
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=1024 count=168960 (to save the file in the internal storage)
OR
dd if=/dev/block/mmcblk0 of=/storage/external_SD/unbrick.img bs=1024 count=168960 (to save the file in the microSD)
Then follow this tutorial using the unbrick.img you got from the command above: http://forum.xda-developers.com/lg-l90/help/bricked-d410-t3094018/post61741908
Actually there is a smarter way to recover from this kind of brick without any backup, it's just a matter of extracting the partitions of your kdz and flash them with an image writer. People from LG G2 forums have been doing this for months, they even have a dedicated tool for this: https://www.youtube.com/watch?v=ERZvlJIC9dE
As should be well known, using the current CM14.1 OTA update results in a bootloop into recovery.
I was able to get out of bootloop by zeroing the FOTA and MISC partitions. But, turns out, something in there was important. I can no longer connect to WiFi. (I ran a full reset, wiped system + reinstalled, so I'm fairly certain it was my dumb a** wiping the MISC partition without making a backup first. In fairness, I'd just come home from an 18 hour shift, but I should have known better.)
I'm requesting an image of the misc partition from anyone on here with a working LG G4 H811. The phone can be running any ROM, and prior to flashing was ideally running V20P or V20O (the two stock T-Mo MM builds). The resulting raw image should be 16,777,216 bytes. Compressed as a ZIP, it should be around 31 KB.
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
Thanks in advance!
aorbiy said:
As should be well known, using the current CM14.1 OTA update results in a bootloop into recovery.
I was able to get out of bootloop by zeroing the FOTA and MISC partitions. But, turns out, something in there was important. I can no longer connect to WiFi. (I ran a full reset, wiped system + reinstalled, so I'm fairly certain it was my dumb a** wiping the MISC partition without making a backup first. In fairness, I'd just come home from an 18 hour shift, but I should have known better.)
I'm requesting an image of the misc partition from anyone on here with a working LG G4 H811. The phone can be running any ROM, and prior to flashing was ideally running V20P or V20O (the two stock T-Mo MM builds). The resulting raw image should be 16,777,216 bytes. Compressed as a ZIP, it should be around 31 KB.
Process to generate a image of misc is as follows:
Reboot into TWRP recovery.
Run "adb shell" or open a recovery terminal.
Run "ls /dev/block/platform/*/by-name/misc" to identify the path to your misc partition.
Mine is "/dev/block/platform/f9824900.sdhci/by-name/misc"
Run "dd if=/dev/block/platform/f9824900.sdhci/by-name/misc of=/sdcard/misc.img"
Replace "f9824900.sdhci" if appropriate for your device, using the value found in step 3.
You now have a file misc.img in your storage directory. You can either use "adb pull /sdcard/misc.img" to download it onto your PC, or you can upload it directly using XDA mobile.
If anyone here can follow the above steps and upload the resulting image, I'd be deeply grateful.
Thanks in advance!
Click to expand...
Click to collapse
you can download it from here
you've been served....
TURBO
And WiFi works. Beautiful.
BTW, I pulled this up in a hex editor, and noticed the lines "recovery --wipe_data".
Do you know if this have any special meaning, like the next OTA I receive (that works) will wipe data? (I don't really care if it will, but could be useful to know.)
Edit: Nevermind, found the answer at http://forum.xda-developers.com/showpost.php?p=54355114&postcount=486
Thanks for the help! Have a beer on me!
aorbiy said:
And WiFi works. Beautiful.
BTW, I pulled this up in a hex editor, and noticed the lines "recovery --wipe_data".
Do you know if this have any special meaning, like the next OTA I receive (that works) will wipe data? (I don't really care if it will, but could be useful to know.)
Edit: Nevermind, found the answer at http://forum.xda-developers.com/showpost.php?p=54355114&postcount=486
Thanks for the help! Have a beer on me!
Click to expand...
Click to collapse
thank you. my pleasure...... please, allow me to be the first to hit thanks on you.....
TURBO
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
doesitburn said:
hi,
so heres the deal,
before oem unlocking,installing twrp, installing modify rom. (with out ads)
i did a backup of my phone via recovery mode.
it created 6 files userdata_xxxx_xxxx.backup (.backup 0 to 6) in total of 11.4GB , i have tried to see if its a tar file, i tried to open it with 7zip and tried to dd the first 512bytes , nothing worked.
i would like to know how can i extract / view /open these backups that i made to restore some pictues, since twrp wont recognize the backup that i've made with the stock recovery , i dont want to erase the files and data that i have at the moment so i would not restore it right into the phone , so manual way is only way.
i am on win10 and linux
after omit all the packages as one
doing file gave me this userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
trying to mount with mount -t ext4 -o loop,rw userdata_xxxx_xxxx.backup "tmp" gave me an empty result "empty thumb drive"
help will be appreciate thanks alot!
Click to expand...
Click to collapse
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
mrmazak said:
read through this thread.
https://forum.xda-developers.com/showthread.php?t=2528969
it covers this situation. There is a script to automate this on post 17, I have not tried, but comments show it works
Click to expand...
Click to collapse
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
doesitburn said:
i have followed this before opening a thread, it did not work for me,
when using the bash script omit all the backup files to one and then tried mount it. problem is i let it ran 8h+ and it filled up my whole hdd when trying to mount it .
so it did not help me :s
Click to expand...
Click to collapse
I know you said you have data currently on phone you dont want to loose. But it seems it might be easier to make twrp backup of phone now. then put factory recovery on and restore that back up you have from before , save off it what you wanted, then put twrp back and restore the twrp backup.
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
doesitburn said:
where do i get the factory recovery img ?
also thats sound alot more easier to extract/view the data instead of removing everything that i have now :S
when using file the output is that
userdata_xxxx_xxxx.backup: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (errors) (extents) (large files)
this file was made by the bash script bckp2cwm.sh
Click to expand...
Click to collapse
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
mrmazak said:
Of course it sounds easier to just mount the backup and browse for the files. But you are not able to do it, so not an option.
I have the stock recovery , will post a link when I get home tonight, if still needed by then
Click to expand...
Click to collapse
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
doesitburn said:
well i have tried another alternative such a recovery program such r studio, it worked to recover some pictures but not all of them and it was quiet messy i guess i will do a recovery with the stock img that u will provide
thanks alot <3
i am on 7.4.2 modified firmware , does it matter? or stock recovery will work even if its from another version
ii found this http://rootjunkysdl.com/files/Blu R1 HD Amazon/Firmware/SP_Flash_Tool_BLU_R0010UU_V6.5_Firmware.zip will it work with his recovery even tho its 6.5 ?
i will wait for ur stock recovery
Click to expand...
Click to collapse
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
mrmazak said:
that one should be ok. but large download for only small needed file.
here is recovery from 6.1
unzip it and use "fastboot boot" to test boot it. should also be able to use it for restore without flashing it.
Click to expand...
Click to collapse
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
doesitburn said:
thanks alot
u mention i can use that recovery with out flashing it ? how can i do that ?
i was about to use SP FLASH, if its possible without whats good
(also if i cant use ur way to use it with out flashing it, dont i need a scatter file ?)
Click to expand...
Click to collapse
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
mrmazak said:
use fastboot.
power off phone. Power on while holding volume up.
you get a boot menu
use volume to select fastboot, power to select
connect phone to usb. Open terminal window , verify connected to phone, and confirm drivers, type "fastboot devices"
as long as connection return with "fastboot" and your "serial number" it is working.
type "fastboot boot ENTER FILE NAME AND LOCATION OF DOWNLOADED RECOVERY"
Click to expand...
Click to collapse
ok so for that matter
fastboot boot c:\downloads\recovery.img
that it ? sweet thanks alot.
learning something new every day
could someone with this model run these and give me the images
dd if=/dev/block/platform/.../.../by-name/nvram of=/sdcard/nvram.img
dd if=/dev/block/platform/.../.../by-name/nvdata of=/sdcard/nvdata.img
suckme69 said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post75038379
Click to expand...
Click to collapse
I would, but those are not block partitions that can be pulled like that.
Sent from my Moto E (4) Plus using XDA Labs
i dont know the excact block but my imie wifi baseband and bluetooth do not work ans was told i flashed my nv ram wouldyou know how to repair this?
Those are not block partitions on this device. I think they are only on Mediatek devices and your XT1776 is Qualcomm. You should probably try flashing stock firmware with fastboot or RSDlite. Download the one with owens_sprint_7.1.1 in the title.
i have like 5 times and i get null imei
Try flashing this modem/fsg:
https://www.androidfilehost.com/?fid=962157660013069126
nope did nothing
https://youtu.be/I8V9ud4PGUk
thats how i been flashing because in windows 10 rsd lite dont work
You should thank me later !
Copy and paste.
Click Here ! #Post8
EDIT : i don't have that device anymore. so i can't help you with this. unable to remind the full directory name.
EDIT : Here is the correct path.
---- For MediaTek Variant ----
Nvram :
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvram of=/sdcard/nvram.img
Nvdata :
dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/nvdata of=/sdcard/nvdata.img
---- For Qualcomm Variant ----
Nvram :
dd if=/dev/block/bootdevice/by-name/nvram of=/sdcard/nvram.img
Nvdata :
dd if=/dev/block/bootdevice/by-name/nvdata of=/sdcard/nvdata.img
They are not at that path on the Qualcomm variant. I'd post a screenshot if I could here.
drop here you device recovery.fstab data.
how do i get that?
https://github.com/ReimuHakurei/twrp_device_motorola_owens/blob/twrp/twrp.fstab
did anyone figure anything out?
Yes, your phone is probably basically a tablet now. When your problem started, what exactly did you do? Did you flash LineageOS or something without activating the phone on stock firmware first? Did you run any fastboot erase commands like fastboot erase recovery? If so, you should not ever do either of those. The only thing I can say to try, is to remove the sim card, flash stock firmware, boot the phone to the setupwizard and then power it off. Next re-insert the sim card and turn the phone back on. If you don't get it to connect now, or if you didn't activate it already, try calling your carrier customer service and see if they can help you.
In MediaTek, variant IMEI stored in Nvram partition (non-volatile random access memory). whereas in Qualcomm Variant it is stored in raw EFS, modemst1 & modemst2 partition. Probably you lose your device nvdata and it is of no use. Service center guy can fix this by replacing a small chip within the motherboard (in my case its *PCB*). After all this you will get a new imei number.
Hope this helps.
i flashed the files in the order my flash file said i generated the commands by hand because i could not find any on xda for my device
@suckme69 Try this, either with adb with the OS booted or with a terminal emulator on your device, type:
reboot nvbackup
With terminal emulator you'll have to type su then enter for su permissions. Hope this works!
thanks for your guys help but i finally figured it out for some reason my modem image from my sprint stock package i downloaded didn't work or i wrote the sequence wrong.but i decided to flash the partition package for boot on my sprint phone from getoffmylawns forum but it was giving my crashing for my phone ,phone has crashed but i got service!. so i opened up the boost flash package and got the modem image off there. after flashing my stock firmware package threw the boot-loader i then flashed the modem i pulled from the boost partition zip . i was also flashing threw Ubuntu with the rsd lite someone posted because rsd lite doesn't work with windows 10 .and the reason i decided to flash the boost package because well it was the same model phone and the carriers boost and sprint are the same they use the same towers and sprint owns boost so i saw no harm done.
Disclaimer: I am not responsible for the results of any of these operations.
Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just faced, then solved the problem and I want to share the solution that could maybe help other persons.
This was how it happeded:
While I was flashing the phone, I erased the partition called "persist" accidently. When I was trying to flash the persist partition, the phone returned a message said that you can't flash the controlled partition. I suddenly relized something bad happened. Then I reboot the phone and find that many sensors stopped working. But the worst thing is the carrier network signals lost. I want to contact the service center at first. But I think as long as the phone is unlocked, there are tons of possibilities to fix it, unless it's hard-bricked. So I wanted to try to fix the partition.
As we know, Xiaomi phones have backup partitions for most of the important partitions. For example, vbmeta and vbmetabak partitions. The vbmetabak usually is the backup of vbmeta. This persist partition also has a backup partition called "persistbak". This backup partition can be used to repair the persist partition. There are 2 ways to fix the persist partition. Choose the method you preferred.
1. This way is for users have erased the persist partition, but haven't modified/erased the persistbak partition. If you don't want to type commands just use method 2.
Go to fastboot, flash the twrp recovery first. Then hold the POWER and VOLUME UP to force the phone boot to twrp recovery. Connect the phone to your PC and open adb command window. Type the following commands in order:
adb shell
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition immediately. For example, the persist partition and persistbak partition correspond to mmcblk0p$$ and mmcblk0p%% respectively (persist---->mmcblk0p$$ and persistbak---->mmcblk0p%%). Run this following command to restore your persist partition:
dd if=/dev/block/mmcblk0p%% of=/dev/block/mmcblk0p$$
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partition block name.
Now the persist partition has been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
2. This way is for users that have erased persist partition and persistbak partition or can't restore the partition using method 1. Also, this method is a universal and easy way to fix both persist partition and persistbak partition. It doesn't need to type any command but only a swipe.
I have made the persist partition repair tool for both global version and Chinese version. Both of them are in attachments. These tools make the repair process very easy. Both flashable zip files are tested on my Redmi Note 8 and they work fine.
I have also posted them to Mi Community.
Flash the repair tool in attachment. Choose the right file and flash it.
Now the persist partition and persistbak partition have been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
If you think it's useful, please click the "Like" button.
Yuki1001 said:
Disclaimer: I am not responsible for the results of any of these operations.
Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just faced, then solved the problem and I want to share the solution that could maybe help other persons.
This was how it happeded:
While I was flashing the phone, I erased the partition called "persist" accidently. When I was trying to flash the persist partition, the phone returned a message said that you can't flash the controlled partition. I suddenly relized something bad happened. Then I reboot the phone and find that many sensors stopped working. But the worst thing is the carrier network signals lost. I want to contact the service center at first. But I think as long as the phone is unlocked, there are tons of possibilities to fix it, unless it's hard-bricked. So I wanted to try to fix the partition.
As we know, Xiaomi phones have backup partitions for most of the important partitions. For example, vbmeta and vbmetabak partitions. The vbmetabak usually is the backup of vbmeta. This persist partition also has a backup partition called "persistbak". This backup partition can be used to repair the persist partition. Here is a way to fix the persist partition.
This way is for users have erased the persist partition, but haven't modified/erased the persistbak partition.
Go to fastboot, flash the twrp recovery first. Then hold the POWER and VOLUME UP to force the phone boot to twrp recovery. Connect the phone to your PC and open adb command window. Type the following commands in order:
adb shell
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition immediately. For example, the persist partition and persistbak partition correspond to mmcblk0p$$ and mmcblk0p%% respectively (persist---->mmcblk0p$$ and persistbak---->mmcblk0p%%). Run this following command to restore your persist partition:
dd if=/dev/block/mmcblk0p%% of=/dev/block/mmcblk0p$$
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partition block name.
Now the persist partition has been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
2. This way is for users that have erased persist partition and persistbak partition or can't restore the partition using method 1.
Find someway to download the fastboot ROM for your device. Exract the tgz file and open the folder called "images". Copy the "persist.img" to the adb tool folder. Because of the limitations of Xiaomi, you can't flash the persist partition or the persistbak partition directly. Copy the persist img file to the internal storage or sdcard on your phone. Now reboot to twrp recovery, connect the phone to your PC. Use these command to make a file that you can dd it to the persist partition and the persistbak partition:
adb shell
simg2img /sdcard/persist.img /sdcard/persist333.img
Now you have a file that can dd to the persist/persistbak partition. Then type these following commands in order:
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition and the persistbak partition immediately. Type these following commands in order:
dd if=/sdcard/persist333.img of=/dev/block/mmcblk0p$$
dd if=/sdcard/persist333.img of=/dev/block/mmcblk0p%%
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partitions block name.
Now the persist partition and persistbak partition have been fixed/restored. Reboot your phone to system and check the whether sensors and carrier network etc. all work fine.
If you think it's useful, please click thanks button.
Click to expand...
Click to collapse
Does this fix "device storage corrupted" error?
Actually I have this error but my sensors, carrier, wifi ... Etc all working great this error still appears. Anyway I think magisk hide config props module damaged my device's persist when I changed the fingerprint then I came back to stock rom and this error happened so my question is: is this process risky Or could cause losing mac or imei? And am I going to lose widevine l1?
I'm thinking about backing up my current persist before proceeding do you think it's a good idea?
[email protected] said:
Does this fix "device storage corrupted" error?
Actually I have this error but my sensors, carrier, wifi ... Etc all working great this error still appears. Anyway I think magisk hide config props module damaged my device's persist when I changed the fingerprint then I came back to stock rom and this error happened so my question is: is this process risky Or could cause losing mac or imei? And am I going to lose widevine l1?
I'm thinking about backing up my current persist before proceeding do you think it's a good idea?
Click to expand...
Click to collapse
Yes. It can fix "find device storage corrupted" . You won't lose your imei or mac. At that time I erased the persist partition by a command "fastboot erase persist" accidently. I have tried both method 1 and 2, and the error is no longer appeared.
About backing up, the persistbak partition is a backup partition for your current persist partition. So if you failed, just restore the persistbak to the main persist partition. And you can also export the raw image of your current persist partition. Of course, the error will appear if you restore the corrupted persistbak.
Update: I have uploaded the persist partition repair tool for both global version and Chinese version. Both of them are in attachments. These tools make the repair process very easy. Both flashable zip files are tested on my Redmi Note 8 and they work fine.
realgordboy said:
Good work.
Just one query. In your original post, you mention simg2img command. I'm wondering if that is actually needed or wanted, given that the fastboot ROMs contain persist images that are not sparse.
Click to expand...
Click to collapse
Yes. You are right. I have been flashed my redmi note 5's persist partition and its a sparse img file. Look like this img file is a raw img not sparse file. Thanks for the tip. I have changed the content of method 2. And it's really easy to flash both persist and persistbak using my repair tool.
realgordboy said:
Looks like we both had the same good idea. I made a zip for my Redmi Note 8T, that does more or less the same, restoring both persist and persistbak to "pristine" condition.
My fix : https://forum.xda-developers.com/redmi-note-8/how-to/fix-persist-partition-getting-mangled-t4112133
Click to expand...
Click to collapse
Yes. That's a good work. Thanks for sharing. I really have the same idea to you. I will test your file later with replacing your persist.img in the zip file.
realgordboy said:
Are you serious?
Of course I tested it. In fact I tested it extensively, and the script has error checking for every single action command
The persist image, as I explained in my post is from the Global Note 8T 11.0.4.0 ROM. It will only probably work on the Note 8T.
It would of course work on just about any similar phone, if you replace the persist image with your own.
Click to expand...
Click to collapse
OK. Thanks for the reply I will test your zip file tomorrow. It should be a good work. Just technical discussion, nothing else.
realgordboy said:
Your original method 2 used 'dd'. Are you saying 'dd' is wrong?
Are you saying that in addition to the incorrect use of simg2img, your entire method was faulty?
And just what exactly is the difference between 'dd' and 'package_extract_file'?
These are not questions that require an answer, because one of us already knows the answers, and checks their 'advice' before posting.
Click to expand...
Click to collapse
I don't think dd is wrong if the img is a raw image. It should can be dd to the partition. I'm sorry if I said something wrong and don't be angry please. Just discussion, nothing else. I will test your file with my persist.img tomorrow.
Hi! Thanks for the input! Would I lose L1 widevine DRM validation with this method?
CesarPedetta said:
Hi! Thanks for the input! Would I lose L1 widevine DRM validation with this method?
Click to expand...
Click to collapse
Is your persist partition broken? If so just flash it. Don't think too much. The phone works normally is the first thing. And sorry, I don't know if it will effect the widevine DRM security level. Don't use it like a toy. Persist means "persist", its data should not be changed after shipping. Only flash it when your persist partition is broken or cannot works properly.
hello,
i have Mi 9T pro i have bug with light and proximity sensor, after flash persist.img with orange fox my sensor work but for few moment and stop work again look at the evidence
thx 4 the tutorial
can I flash this two files on my poco F2 Pro ? I have problem with persist image, lost my fingerprint sensor..
Is there an chance to get the the persist partition file for Willow please?
I tried to restore from bak files, didn't work.
autobrightness is not working for me. after ive flashed fastboot rom .. i noticed that my screen was very bright at nigth. so checked brightness.
manually brightness works ok up and down.. but in auto only works on high settings but it wont go down. or seems to go down but brightess doesnt change..
enter cit presing kernel verion did a test on light sensor. flux sensor goes up and down depending of light but the brightness value doesnt change down only up high.
WinBug2 said:
Is there an chance to get the the persist partition file for Willow please?
I tried to restore from bak files, didn't work.
Click to expand...
Click to collapse
Just download the fastboot ROM which version you are using. Extract it and you can find persist.img in images folder.
Hi, thanks for sharing.
im using mi note 10, im losing the /persist partition directory, somehow it losing after flashing custom rom, how to get it back? Im editing your file and change to my phone original persist.img, and flashing on twrp it end to fastboot bootloop. My sensor are working, but after loosing my /persist directory the fingerprint scanner "cant add fingerprint, try again" Error.
I check at miflash, theres no option to install/create persist.img partition at promram0.xml line to fix this (somehow im suprising about this, because at my old whyred phone theres an option to create the partition), Could you help me solving this?
Yuki1001 said:
Disclaimer: I am not responsible for the results of any of these operations.
Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just faced, then solved the problem and I want to share the solution that could maybe help other persons.
This was how it happeded:
While I was flashing the phone, I erased the partition called "persist" accidently. When I was trying to flash the persist partition, the phone returned a message said that you can't flash the controlled partition. I suddenly relized something bad happened. Then I reboot the phone and find that many sensors stopped working. But the worst thing is the carrier network signals lost. I want to contact the service center at first. But I think as long as the phone is unlocked, there are tons of possibilities to fix it, unless it's hard-bricked. So I wanted to try to fix the partition.
As we know, Xiaomi phones have backup partitions for most of the important partitions. For example, vbmeta and vbmetabak partitions. The vbmetabak usually is the backup of vbmeta. This persist partition also has a backup partition called "persistbak". This backup partition can be used to repair the persist partition. There are 2 ways to fix the persist partition. Choose the method you preferred.
1. This way is for users have erased the persist partition, but haven't modified/erased the persistbak partition. If you don't want to type commands just use method 2.
Go to fastboot, flash the twrp recovery first. Then hold the POWER and VOLUME UP to force the phone boot to twrp recovery. Connect the phone to your PC and open adb command window. Type the following commands in order:
adb shell
cd /dev/block/by-name
ls -all
Check the output, find the partitions called "persist" and "persistbak". Remember the blocks corresponding to these two partitions. They should be similar to "mmcblk0p**". Once you know these correspondences, you can restore the persist partition immediately. For example, the persist partition and persistbak partition correspond to mmcblk0p$$ and mmcblk0p%% respectively (persist---->mmcblk0p$$ and persistbak---->mmcblk0p%%). Run this following command to restore your persist partition:
dd if=/dev/block/mmcblk0p%% of=/dev/block/mmcblk0p$$
Note: You need to replace "mmcblk0p$$" and "mmcblk0p%%" with the real partition block name.
Now the persist partition has been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
2. This way is for users that have erased persist partition and persistbak partition or can't restore the partition using method 1. Also, this method is a universal and easy way to fix both persist partition and persistbak partition. It doesn't need to type any command but only a swipe.
I have made the persist partition repair tool for both global version and Chinese version. Both of them are in attachments. These tools make the repair process very easy. Both flashable zip files are tested on my Redmi Note 8 and they work fine.
I have also posted them to Mi Community.
Flash the repair tool in attachment. Choose the right file and flash it.
Now the persist partition and persistbak partition have been fixed/restored. Reboot your phone to system and check whether sensors and carrier network etc. all work fine.
If you think it's useful, please click thanks button.
Click to expand...
Click to collapse
not to hate or dislike or be rude or anything... but people will lose Widevine L1 support by this method... so if anyone doesn't want HD videos on netflix etc, go ahead with this method.. otherwise don't even touch persist partition.
Thank you so much, flashing the zip worked !
Where can i find repair_persist-willow.zip ? From gingko not work.