persist partition destroyed - Xiaomi Mi Note 10 Questions & Answers

Noobie mistake
so I just accidentally formatted the persist partition and now my fingerprint no longer working, in some other forum they got it working by simply flash persist.img backed up from another device. Maybe if somebody could provide one or give any possible workaround this. Thanks

hayatnas18 said:
Noobie mistake
so I just accidentally formatted the persist partition and now my fingerprint no longer working, in some other forum they got it working by simply flash persist.img backed up from another device. Maybe if somebody could provide one or give any possible workaround this. Thanks
Click to expand...
Click to collapse
Re install original rom whit adb

I already flashed the fastboot image, isn't that the same?

Related

[Q] EFS Backup

Hi guys
Guess what? Yes that's right I have a corrupted efs folder from a bad flash, and my back up has disappeared from my PC. I've searched via Google and directly on xda and am aware that there is a proposed method to rebuild the efs but the tablet needs to allow adb access which I cant do as it wont boot past the boot logo and i apologize now if this has been asked previously and I've missed it. I've had numerous Android devices and flashed custom firmware on them all including this tablet so im not a complete novice when it comes to sorting them out however this time im struggling. So im throwing the following questions out there to see if you can help:
I can enter TWRP and Download mode
A: Does anyone have a backed up EFS that i could flash via recovery (is this possible/allowed due to it being a tablet and not a phone)?
B: Is it possible to force the tablet in its current state to allow ADB access?
Your Help will be gratefully accepted
I have the same problem.
Also been looking for EFS backup file. Flashed several ROM's but every time I have a bootloop.
Can anyone help?
bump.
is anyone able to offer any advice on this otherwise ill be putting the tab in the bin which i dont particually want to do
BUMP
does anyone have a backed up efs i can use??
sefo1979 said:
does anyone have a backed up efs i can use??
Click to expand...
Click to collapse
As far as I know, EFS contains the serial number as well as other device specific info so someone else's EFS might not work. If you can boot into recovery, adb should work then. If not, use Odin to flash the latest @Android-Andi TWRP recovery and then adb should work.
Sent from my SGH-T989
jrc2 said:
As far as I know, EFS contains the serial number as well as other device specific info so someone else's EFS might not work. If you can boot into recovery, adb should work then. If not, use Odin to flash the latest @Android-Andi TWRP recovery and then adb should work.
Sent from my SGH-T989
Click to expand...
Click to collapse
I can get into twrp but have not been able to get adb access, I am aware that there is a way to rebuild the EFS if this can be done(would you be able to provide assistance?) I have tried refreshing both original and custom rooms but all get stuck at the Samsung logo as I belive the boot sequence looks for the EFS info at that stage.
can anyone help??
it would be really helpful if someone could provide:crying: a copy of their backup to see if i am able to revive the tab ???

[Fixed] 64GB now shows 12.14GB total space

Not sure what's going on here. CM nightlies. Didn't notice until I got a space warning. It used to be like 50 something when I was on stock.
X10D3 said:
Not sure what's going on here. CM nightlies. Didn't notice until I got a space warning. It used to be like 50 something when I was on stock.
Click to expand...
Click to collapse
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
dansou901 said:
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
Click to expand...
Click to collapse
Are the CM nightlies based off the 16gb variant?
X10D3 said:
Are the CM nightlies based off the 16gb variant?
Click to expand...
Click to collapse
No, but apparently they've got the userdata.img files inside the zip (I don't know why). So please open the zip you are flashing and take a look at what you are actually flashing (including the flashing script).
Yep, you flashed the 16gb version.
Sent from my One using XDA Free mobile app
Ah, I see you found the problem was using a toolkit... That's why I never used toolkits I didn't create myself or have looked at thoroughly first!
dansou901 said:
Ah, I see you found the problem was using a toolkit... That's why I never used toolkits I didn't create myself or have looked at thoroughly first!
Click to expand...
Click to collapse
I was looking for easy. Already scripted. Fixed and ready to roll. I didn't even think about there being 2 userdata files. Monday...
How did you fixed this?
Ive got the same problem
I've found the userdata64G.img
but when i do:
fastboot flash recovery userdata64G.img it gives an error
when i do fastboot flash recovery userdata.img it also gives the same error -> ive renamed the file
--> error is : Size to big
how do i fix this problem
Fopflugel said:
How did you fixed this?
Ive got the same problem
I've found the userdata64G.img
but when i do:
fastboot flash recovery userdata64G.img it gives an error
when i do fastboot flash recovery userdata.img it also gives the same error -> ive renamed the file
--> error is : Size to big
how do i fix this problem
Click to expand...
Click to collapse
It stopped you becasue that would have bricked your phone, don't type fastboot commands without knowing what to do.
What you're telling fastboot to do is to override the recovery with a userdata which would have for sure bricked your phone.
You want to be doing fastboot flash userdata userdata64G.img
not flashing recovery.
16 to 64
dansou901 said:
You accidentally flashed the userdata.img for 16 GB version which repartitioned your data partition. You have to flash the userdata64.img to get it to old state again. As I don't have the phone yet, I can't help you further.
Click to expand...
Click to collapse
Hello friends,
I'm not a technician and I have the same problem with the memory.
Can someone explain step by step how do I fix my phone?
Thanks in advance!
Maldavanin said:
Hello friends,
I'm not a technician and I have the same problem with the memory.
Can someone explain step by step how do I fix my phone?
Thanks in advance!
Click to expand...
Click to collapse
1. Download 64gb userdata (find it)
2. Flash it via fastboot.
Google on how to use fastboot.
Requires unlocked bootloader
The small little details are up to you and can be found in various stickied threads. Best of luck.
try flash this stock ColorOS from here http://forum.xda-developers.com/showthread.php?t=2772627

Please help me! Cant install any ROM on my OnePlus!

Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!

bricked, need help

it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx
nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do
Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)
Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot
Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try
Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.
U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101
Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?
Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs
Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand
Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device
You both are awesome ???
Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files
venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.
Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro
Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.

All sensors stopped working

Hi,
Seems like I flashed the wrong ROM variant for my OnPlus 7 pro, I flashed the international version, but maybe I should have flashed the EU stock ROM, although I bought the phone from the UAE.
Phone model: GM1913
The phone is working smoothly, but all the sensors are not working.
I'd there a way to fix this without flashing a new ROM and loosing all my data.
Can I flash vendor.img on fastboot, will this fix it?
Phone model: GM1913
Android version: 9
EU stock ROM code: GM21BA
Global stock ROM code: GM21AA
Well, I took the risk and flashed the vendor.img to the vendor partition from the EU ROM, guess what... It didn't work, it bricked the phone!
So I flashed a new EU stock ROM to the phone, and the sensors still didn't work!!
I lost all my data and customization for nothing.
So it seems this has nothing to do with the ROM variant, my speculation was wrong.
Searching online seems that the problem is caused by Android 10, which I installed before and then downgraded to Android 9, because I couldn't get root.
It looks like it corrupted the "persist" partition. according to this article, many Pixel owners faced the same issue, which is complicated to fix.
I'd appreciate if anyone can help me fix this issue. First thing I need is an image from the persist partition.
Edit: a relevant xda post: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
vegatr0n said:
Phone model: GM1913
Android version: 9
EU stock ROM code: GM21BA
Global stock ROM code: GM21AA
Well, I took the risk and flashed the vendor.img to the vendor partition from the EU ROM, guess what... It didn't work, it bricked the phone!
So I flashed a new EU stock ROM to the phone, and the sensors still didn't work!!
I lost all my data and customization for nothing.
So it seems this has nothing to do with the ROM variant, my speculation was wrong.
Searching online seems that the problem is caused by Android 10, which I installed before and then downgraded to Android 9, because I couldn't get root.
It looks like it corrupted the "persist" partition. according to this article, many Pixel owners faced the same issue, which is complicated to fix.
I'd appreciate if anyone can help me fix this issue. First thing I need is an image from the persist partition.
Edit: a relevant xda post: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
Click to expand...
Click to collapse
Use the MSM tool for your device to return it to stock and repair the partitions. Then update using the correct rom for your device.
Thanks, but I want to try flashing the persist partition first, if that doesn't fix it then I have no choice but to go that route.
vegatr0n said:
Thanks, but I want to try flashing the persist partition first, if that doesn't fix it then I have no choice but to go that route.
Click to expand...
Click to collapse
Hi,
Did you manage to get the sensors back working without reflashing the whole phone and losing everything?
I'm in exactly the same situation and so far I tried flashing via flashboot 3 different persist images in the hopes that at least at some point in time something would work.
I was sadly wrong.
Am also wondering if what flashboot utility does is recreating the partition from 0 (mkfs and all the works) or only tries to overwrite some info.
skyraven83 said:
Hi,
Did you manage to get the sensors back working without reflashing the whole phone and losing everything?
I'm in exactly the same situation and so far I tried flashing via flashboot 3 different persist images in the hopes that at least at some point in time something would work.
I was sadly wrong.
Am also wondering if what flashboot utility does is recreating the partition from 0 (mkfs and all the works) or only tries to overwrite some info.
Click to expand...
Click to collapse
Unfortunately, flashing the persist partition didn't my problem, I had to use the MSM tool to reflash the entire OS.
solution is flash miui 10 rom.....problem almost solved
vegatr0n said:
Unfortunately, flashing the persist partition didn't my problem, I had to use the MSM tool to reflash the entire OS.[/QUOTE
Click to expand...
Click to collapse

Categories

Resources