Im once again into this typical "I bricked my phone and spend endless hours searching for tutorials and hoping that something work" stuff. This time I broke my persist.img and noticed something strange:
There are dozen of tutorials which state that one should download a clean fastboot rom to extract the persist.img (".\images\persist.img") from the image folder and flash it either using recovery or fastboot edl in combination with a modified rom to only flash this partition.
Now I noticed that the persist.img partition is pretty empty for most Xiaomi stock roms:
{
"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"
}
In comparisation the persist partition I extracted from a friend who luckily got the same phone:
How is the above persist partition from the stockrom supposed to help someone when there are just empty files? Atleast for me it didnt bring back the sensors when I flashed it. On the contrary the persist partition from my friend fixed everything.
If the persist file of every stock rom is empty beside a few zero byte files the conclusion would be that the only way to get a working file is to get your hands on a unmodified one from someone else.
Or is there some magic that will enrich the partition with new files as soon as you boot the stockrom for the first time?
How come there are so many tutorials saying that one should flash this partition from stock?
are you sure you have downloaded a fastboot (TGZ) rom and open the TAR file?
Package Name: grus_eea_global_images_V12.5.1.0.RFBEUXM_20210526.0000.00_11.0_eea_0f94ab4db4.tgz
Related
Hi
I try cwm backup, sd card and internal sd, i have try mount everything but still backup size is only 16mb. Anyone know why?
Same here.
huoh
depserz said:
Same here.
Click to expand...
Click to collapse
I think no1 read Q&A thread. Pls someone post this bug root+cwm thread cos this forum is lame and i cant post it. " only if u have 10 or more posts, plaaplaaplaa, jaadijaadijaa"
If your CWM Recovery is 6.0.0.0 and higher then the small backup size is perfectly normal... There is another folder called blobs which actually stores the most of your backup data
The way the new CWM works is it makes a shared folder ( blobs ) that all recovery instances use... for example ( easiest example ) if you make a recovery of a fresh new device, then install a few apps , then make a recovery again , the blobs folder will hold the data that is used in both of those recovery images, and the their respective folders will only hold data that is exclusive to that particular image...
kinda like this :
{
"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"
}
the 2 gray circles are 2 recovery images , and the white area they intersect within is what they both have in common ( the blobs folder )
that way if you make many recovery images, the wont be 800MB each, they will be 15-30MB with one folder that has the stuff they "have in common"... saves on space and time
im not good at explaining , but i hope you can understand it xD
Ooh, thanks
Hi,
First of all apologies - I know this isn't dev but I wanted to post in here hoping that someone will see this and reply quickly.
I've just purchased a new nexus 5 and was about to sell my GNEX (literally later today) but have somehow managed to corrupt my <naughty word> efs partition.
Could someone please be kind enough to tell me what files they see in /factory. I think I have a non standard backup of the files but I'm not 100% sure what to do with them (yet).
Thanks in advance!
Ah balls Looks like I figured how how to restore my backup of the files but it still has the generic IMEI
sykomaniac said:
Ah balls Looks like I figured how how to restore my backup of the files but it still has the generic IMEI
Click to expand...
Click to collapse
Odin to stock. Or...if u have any any working nandroids at all simply restore that partition only.
Sent from my Galaxy Nexus using Tapatalk 2
I've tried odin to stock but it didn't fix the generic IMEI issue - I used odin files from here: http://forum.xda-developers.com/showthread.php?t=2065470
I did select the PIT file
Should this have fixed the issue?
Efs.img in my gnex was in
/Dev/block/platform/omap/omap_hsmmc.0/by-name
I sold my gnex, but I can ask for screenshots of factory folder if you want
I will post as sono as possible
EDIT:
{
"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"
}
Cheers for that. Can't get it to work ?.
Have to make sue I back up the efs on my nexus 5 now!
I have a problem. My tablet is turned on and shows only the label similar to a USB flash drive. rekaveri not go in. already tried all combinations of buttons.I am trying to solve the problem through flash tools, but nothing is impossible.
Really need your help. tablet a month is not working
I do not know. maybe the fact I am working through the flash tool? because when I try to do everything I have comes to 50% and then an error.
{
"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 have the exact same problem, and have been trying to use the Intel flash tools to fix it with not much success. I have found, though, that when using the phoneflashtoollitecli (flash tool command line utility that comes with phone flash tool lite) with the --clean-emmc option, the flash only succeeds when I hold down power and vol+ first, and then attempt the flash. All other times, it "Failed to start Dldr state machine, aborting...". Haven't been able to use this technique when flashing the os image though.
Hr.shokohi, where do you get your OS image and OS DnX files from?
download here
laoshu84 said:
laoshu84
Click to expand...
Click to collapse
https://yadi.sk/d/IdC9Pbxpj3HGC
in this file take (dnx_osr.bin) and put together os dnx, and click Show All Files at the bottom right and droidboot.img where os image
Thanks Hr.shokohi. I've had no luck using my method of flashing and your flash files, so far. I will be trying using the Linux version of the flasher to see if it makes a difference.
laoshu84 said:
Thanks Hr.shokohi.
Click to expand...
Click to collapse
If something happens write.
Do u solve the problem?
i will take n1 to factory. still cant solve the problem~ha
Nope no luck yet. I'll write back if I succeed
So what is the point of backing up your modemst 1 and 2? I have partitions back up and restore and it showsfiles highlighted. Which one do I need for conversion? At what point will I need these partitions durning conversion. How do I use or flash them? I'm hesitant to proceed with conversion until I get a better understanding of how I should back them up and restore them.
{
"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 think that I'm backing up them up just in case somethint goes wrong but I'm not 100%
Modem a for a partition, and modem b for b partition. These are the ones a TMobile device has to flash when going to a custom Rom/another Oxygen build. These can be shared, etc. The st1 and st2 is for your specific device and uses fastbootd, but these can not be shared and will result in a soft brick if I'm not mistaken. Modem a,b is the ones for conversion if on T-Mobile,etc.
jwidel said:
So what is the point of backing up your modemst 1 and 2? I have partitions back up and restore and it showsfiles highlighted. Which one do I need for conversion? At what point will I need these partitions durning conversion. How do I use or flash them? I'm hesitant to proceed with conversion until I get a better understanding of how I should back them up and restore them.View attachment 5405181
Click to expand...
Click to collapse
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Hello.
I have a problem with the purchased used Xiaomi Mi 9 SE.
I bought the phone and it had an unlocked Bootloader, it was not possible to pay with it using NFC.
The phone was probably ROM 12.0.XXX I think Global.
I downloaded the Fastboot 12.5.1 EU ROM and flashed it using MiFlash.
When uploading, I checked the option - clean all and lock
The upload went smoothly and was successful.
Unfortunately, after rebooting the phone enters recovery mode and it is looped like this, it displays the message:
This MIUI version can't be installed on this device :-(
I can enter fastboot and try to flash another Rom but then I get an error that the phone is locked.
Please, help me with this issue, I don't know what to do, is it possible to fix it? ? ?
I know there are people here with really great knowledge, please help. :-(
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash the ROM Global 12.0.1 again but I get the error as above
I have Miflash pro 7.3.706
Try to enter fastboot mode and flash the ROM using the flash_all script that's insideof the compressed rom by way of windows cmd or linux terminal.
Just extract the rom file until you see the folder structure there with all images and then look for a how to flash roms using fastboot. It way easier than that miui flash thing