Related
for those who do not know how to do this yet, follow directions given here.
Just took this info from the web. None of this except for the guide is written by me.
I am not responsible for anything please do not contact me if a green sludge starts attacking your neighborhood eating one person at a time.
************************************************************
************************************************************
************************************************************
http://code.google.com/p/unyaffs/downloads/list
made for linux, but if you know a bit of c, you can probably change it to work with windows, maybe I will do that if I have some time this week.
********OR********
http://jiggawatt.org/badc0de/android/unyaffs-x86-win.zip
or http://www.4shared.com/get/fgryPnPx/unyaffs-windows.html
for windows..... instructions below apply for both
if not included in the zips above, cygwin1.dll and unyaffs.exe are included as an attachment of this reply.
open up a command line, in windows vista/7 just press start and then type cmd press enter and change the directory to the folder with the unyaffs and the img in it. in xp press start>run>cmd... then the same
the usage is: unyaffs /path/to/img
example:
(if unyaffs.exe and system.img are both in c:\temp)
"c:\temp> unyaffs /temp/system.img"
note: the '/' is the way linux determines the pathname of a file and since it is built using cygwin(a file allowing for windows) it is preferrable that the path to the actual file is in unix POSIX format ie: / instead of \ between folders and files.
*********WARNING************
this will extract to directory that unyaffs binary is in.
That's so weird -- I was gonna post the same thing tonight. Thx for writing this up. It's odd that more people don't talk or ask about this tool!
I remember reading this stuff back when I got my G1, and tonight I was trolling the themes and apps section cause I couldnt sleep. (which I rarely look at)
I was baffled that this wasnt common knowledge. I figured if there was no threads about it that people just knew how and didnt have any problems with it. My mistake lol...
enjoy.
can you please explain what is it? what it does? thanks
ericizzy1 said:
can you please explain what is it? what it does? thanks
Click to expand...
Click to collapse
Umm, it expands nandroid img files not sure how else to explain it. Clockworkmod backups are in the img file format. This process allows you to extract those files to get stuff out of them
Sent from my SPH-D700 using XDA App
When you create a backup in Clockwork recovery, it leaves you with a folder like this:
2010-11-18.08.52.49
As you can prob figure out, I made that backup on 11/18 at 8:52am
Inside that folder are .img files, such as: data.img and system.img
Those files basically contain your data (like apps you've installed from market) and system (..system apps that might've come with the phone).
In the orig post, he's explaining how to extract the files from these large .img files.
To give an example, I had a couple of corrupted clockwork backups, and wanted to ONLY pull out some database files (like text messages and call logs) which were not corrupted. Even tho the backup was messed up, I could still extract the files I needed by using the method above, then copied them manually to my phone.
decalex said:
When you create a backup in Clockwork recovery, it leaves you with a folder like this:
2010-11-18.08.52.49
As you can prob figure out, I made that backup on 11/18 at 8:52am
Inside that folder are .img files, such as: data.img and system.img
Those files basically contain your data (like apps you've installed from market) and system (..system apps that might've come with the phone).
In the orig post, he's explaining how to extract the files from these large .img files.
To give an example, I had a couple of corrupted clockwork backups, and wanted to ONLY pull out some database files (like text messages and call logs) which were not corrupted. Even tho the backup was messed up, I could still extract the files I needed by using the method above, then copied them manually to my phone.
Click to expand...
Click to collapse
thx
Sent from my SPH-D700 using XDA App
smeyerhuky said:
Umm, it expands nandroid img files not sure how else to explain it. Clockworkmod backups are in the img file format. This process allows you to extract those files to get stuff out of them
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Right, like if you wanted a file or a few files from clockworkmod img backup, then this process would give you an extended file system, other than what you would normally use to extract the img files. Just trying to understand this so, please correct me if im wrong.... I've been trying to get more knowledge of this, so im still learning.
I prolly sound like a complete idiot, lol...
Sweet! Thanks for this man. I'd been looking for how to do this for some time and kept ending up learning about emulation or some other tangential topic. This is the basic functionality I was looking for. Thanks for posting!
Np. I'm working on writing some stuff on top of the source code that should allow you to browse and pull just one our more file
Its been a but since I looked theory source code so it might take a while... Maybe in between semesters?
Sent from my SPH-D700 using XDA App
Dode you saved my as** thx big thx
Great, now how can I re-compress back to .img after I've made the changes that I want?
EDIT: Nevermind. I just made a zip of the new system folder and flashed it in CWM.
This worked great for me.
Thanks,
Bud
Man, I do not know how to thank you. I was able to recover some important stuff off of my cwm recovery backup. THANKS!!
Hi
I have an Asus Fonepad 8 (K016 or FE380CG. 2GB RAM, 16GB ROM), I know it's not popular around here.. But any help is very welcome.
My initial device's state
- Stock rom 4.2.2
- Root (installed: Greenify, App Ops, Coolify, System App Remover (Jumobile))
- I uninstalled about 20 system apps
then I received OTA update to Lollipop and it displayed the infamous android "error" with the red exlamation mark. so i uninstalled every root app, EXCEPT System App Remover (silly me i forgot the most crucial part), probably meaning that some system apps are still gone. I also did full unroot inside SuperSU.
I tried factory resetting in order to successfully update to Lollipop, but once I get to the setup Welcome screen, these dreaded messages show up. ENDLESSLY
Unfortunately, com.android.phone has stopped working
Unfortunately, com.android.systemui has stopped working
Unfortunately, com.process.acore has stopped working
Click to expand...
Click to collapse
One time, the endless torture stopped and I was able to access Settings. I opened Applications and there was very (infact, too) few apps installed. Less than 200MB of RAM is used. I thought the factory settings failed, so I tried doing the same thing again in fastboot mode. But still a no-go.
Then I tried
Code:
fastboot -w
and it did say "success" but it couldn't format. "File system not supported". I forgot the exact message but that, i think is the point.
In Droidboot Provision OS, there is an option called "SD download". I put the official ROM for my device (.zip) in my SD card, then tried doing exactly that. Still no-go. Below is the entire (not exact) process
Copying E:\ASUS_UPDATE.zip to /cache (i renamed my firmware .zip file to that)
Copying asus update file (i have no idea where this file (if it even is a file) is located)
then my device reboots
a brief "no command" error appears
reboots back to my faulty state
Click to expand...
Click to collapse
I then tried to erase cache and userdata, and ran
Code:
fastboot update fw.zip
This appears
archive does not contain android-info.txt
archive does not contain android-product.txt
Click to expand...
Click to collapse
Desperate enough, I tried to again erase cache and userdata and system (probably my worst decision). and the device is now stuck in boot logo screen.
My awesome representation of my device's boot logo screen
ASUS
powered by
ANDROID
Click to expand...
Click to collapse
I booted my device back to fastboot, and my serial number was shown as "unknown". The same appeared when i type below code in cmd in my PC.
Code:
fastboot devices
One thing to be noted. I am really confused with ASUS's official firmware.
There is no recovery.img, system.img, userdata.img or cache.img
Here is a list of files and directories inside of it:
META-INF (folder)
recovery (folder, 2 files: recovery-from-boot.p and install-recovery.sh)
system (folder, a lot of folders inside like "app", "bin", "etc", "fonts")
boot.img
fastboot.img
splash1.img
splash1_s.img
splash2.img
splash2_s.img
splash2.img
splash2_s.img
ifwi.zip
modem.zip
Click to expand...
Click to collapse
I do not have nandroid or any kind of backup.
I have googled and tried everything I could find for the past 9 hours. So, i think it's high time I ask experts about this.
I am thinking of taking it to the service center. But any more knowledge regarding this beforehand is very valuable to me.
I know this is too long but I've highlighted the most important parts.
Any kind of help is welcome.
Hi, thank you for using XDA Assist. Unfortunately there is not a dedicated forum and there is very little information about your device on XDA. There is nothing on how to flash the stock firmware. But it sounds like that's what you need to do right now. Looking at ASUS's web site it looks like there should be another zip file. ifwi.zip, in the one you extracted. That's most likely where the image files you are missing reside.
jd1639 said:
Hi, thank you for using XDA Assist. Unfortunately there is not a dedicated forum and there is very little information about your device on XDA. There is nothing on how to flash the stock firmware. But it sounds like that's what you need to do right now. Looking at ASUS's web site it looks like there should be another zip file. ifwi.zip, in the one you extracted. That's most likely where the image files you are missing reside.
Click to expand...
Click to collapse
Hi. Thank you so much for replying and taking the time to read my long "story".
Sadly, yes. There is little to no community for my device.
Regarding ifwi.zip, below is part of the content of the file.
FE380CG_16_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_16_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_1_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_1_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_2_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_2_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
FE380CG_32_BOM_TOKEN_v79.54_CRAK_DEV.bin (3.608 bytes)
FE380CG_32_IFWI_v79.54_CRAK_DEV.bin (4.194.468 bytes)
Click to expand...
Click to collapse
I doubt that it's the system image. The file size is just way too small.
The folder with the largest size is System, and inside there are a lot of folders (app (system apps and asus's bloatwares are inside), bin, etc, fonts, framework, etc, and build.prop). It almost looks like ASUS doesn't package system into a .img file, rather in a folder. That's why I am also looking for a script file that "copies" this folder into the device, if it exists.
I am now downloading the latest (was just uploaded by ASUS) firmware, which is Lollipop.
I'll dig in the file and see if I can find anything interesting.
Ok, download's finished.
Below is the root directory of the new firmware.zip
META-INF (folder)
recovery (folder)
system (folder)
boot.img
droidboot.img
splash.img
file_contexts (no extension)
l_recovery.fstab
partition.tbl
ifwi.zip
modem.zip
Click to expand...
Click to collapse
ifwi.zip has the same contents, only a newer version.
I tried fastboot update fw.zip and the same error pops up
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I have attached a screenshot of updater-script I found inside META-INF/com/google/android. and screenshots of the directories of the firmware zip's contents. Hoping any is helpful to solve this.
First, I know nothing specific about your device. But do you have a custom recovery on your device? CWM or TWRP. The updater-script looks like it should be flashed in a custom recovery, not with fastboot. Edit, also, what's in the system folder, etc. Are there image files in there?
jd1639 said:
First, I know nothing specific about your device. But do you have a custom recovery on your device? CWM or TWRP. The updater-script looks like it should be flashed in a custom recovery, not with fastboot. Edit, also, what's in the system folder, etc. Are there image files in there?
Click to expand...
Click to collapse
Sorry for the late reply.
I just got the device back from the service center.
I inquired about where I can get the firmware file, and the guy said ASUS's website, but to flash it I need a tool.
It seems that this tool then copies the entire system folder to the device.
Anyways, the problem is solved now. Thank you very much for your help.
Glad you got it fixed. I'll close this thread.
Hello everyone
Please, I need help my phone "MATE 7 L09 " which i come to replace the file "oeminfo"
which the file from phone "Honor 4C" now I can't updated phone any more with any roms
Please, who owns the same phone "mt7-L09 " and have a root upload located in the following path of the file" [/device]/dev/block/platform/ff1fe000.dwmmc0/by-name/((oeminfo)) " to be able to replaced
Thank you ...
In this location there are plenty system symlinks like boot, recovery, modem, not single files. Can you enter fastboot?
gahu777 said:
In this location there are plenty system symlinks like boot, recovery, modem, not single files. Can you enter fastboot?
Click to expand...
Click to collapse
I don't try but I can root my phone again then replacing the file with the right file for mt7
You see structure of this folder, i think it cant be copied by copy/paste. Only can be flashed by img files via fastboot
gahu777 said:
You see structure of this folder, i think it cant be copied by copy/paste. Only can be flashed by img files via fastboot
Click to expand...
Click to collapse
Thats right but when I replace it with another file from honor I just doing copy and paste now I have honor logo when I switch on or restart it
So I will try replacing it can you copy and upload ?
With all the random qhsusb_bulk hardbricks coming around, I've decided to create a thread to share debrick.img files just in case. You do not need to create this, but if you ever need it, you'll be glad you did.
EXPLANATION:
If you ever HARDBRICK your phone, which can be caused by flashing an incompatible ROM, bad bootloader flash, or anything, your processor will fallback into a mode called USB_BULK mode. In this mode, it will await an SD card with a special image flashed to it, called debrick.img, and boot to that. Once booted from the SDcard, it will await a firmware flash from a computer (download mode.)
However, this image needs to be specific to the bootloader version the phone was running before the hardbrick occured. That's why I've created this thread: people on different bootloaders can share their debrick images.
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
HOW TO USE ONE:
If you ever have the unfortunate luck of needing to use a debrick image, here's what to do:
-Download Win32DiskImager
-Put your microsd into your PC (yes you will need an adapter in some cases)
-Use Win32DiskImager to write the debrick.img to the SD card
-Take battery out of phone
-Put the SDcard into the phone and put the battery back in
-Do Vol Dn+Power+Home
-Your device should boot into Download Mode, and you should see "SDCARD MODE" at the top right
-Flash stock firmware using Odin
Downloads will be added to the 2nd post
Downloads
PB1 BOOTLOADER DEBRICK
PD1 BOOTLOADER DEBRICK (thanks @klabit87)
PLEASE SHARE YOUR OWN DEBRICK IMAGES! I WILL ADD THEM HERE
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
al50 said:
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
Click to expand...
Click to collapse
It is completely based on bootloader version. You can use "Phone Info - Samsung" to confirm before creating an image.
This is great would be nice if you could create Bod5 img for us who are still able to downgrade
Sent from my SM-G900V using Tapatalk
When I get a chance I'll make one for the OC4. Just want to be sure to do it correctly. Since I'm on UL OC4 Bootloader, PB1 firmware
Nandr0idC0nsumer said:
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card
Click to expand...
Click to collapse
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
ben_pr said:
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
Click to expand...
Click to collapse
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
[email protected] said:
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
200mb is all thats needed on sd.
Only for samsung devices.
Nandr0idC0nsumer said:
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
Click to expand...
Click to collapse
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
ben_pr said:
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
Click to expand...
Click to collapse
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Nandr0idC0nsumer said:
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Click to expand...
Click to collapse
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
Nandr0idC0nsumer said:
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
Click to expand...
Click to collapse
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
ben_pr said:
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
Click to expand...
Click to collapse
Good point. I will update the OP later. This is not my package btw
Nandr0idC0nsumer said:
Good point. I will update the OP later. This is not my package btw
Click to expand...
Click to collapse
My mistake; I thought you made the zip!
Nandr0idC0nsumer said:
200mb is all thats needed on sd.
Only for samsung devices.
Click to expand...
Click to collapse
Thanks
Sent from my SM-G900V using XDA-Developers mobile app
ben_pr said:
My mistake; I thought you made the zip!
Click to expand...
Click to collapse
Lol nope. Usually I like to have it all in the updater-script so I wouldn't have had a seperate script
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
akaplo said:
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
Click to expand...
Click to collapse
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Nandr0idC0nsumer said:
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Click to expand...
Click to collapse
See my thread. http://forum.xda-developers.com/showpost.php?p=67159556&postcount=14
Hi, i own an Oneplus 8 India Version.
As soon as i purchased the first thing I did was to take the persist.img backup as that seemed to be an important thing to do from my reading through the articles.
After a few months now, I seem to be in need of using this image and realized the image file is not accessible. from the articles and videos I read/seen, everyone is able to EXTRACT the image file using the 7zip or similar tools. However, i am unable to extract using any of the tools.
I took the latest persist.img from the already troubled device and that too is not working. 7zip says "Can not open the file ...."
command i used was this :
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
similarly, i manually copied the file using root file manager aad that too is giving the error
Please help
Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.
crazynapkinman said:
Fastboot flash persist persist.img
I believe that's how you would restore persist.
I could be very wrong. Proceed with caution and I'm not liable if you break it.
Click to expand...
Click to collapse
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.
firoz3321 said:
Hi thank you. The concern is related to the image not being extracted. From what i have read and seen in YouTube too is they are able to extract the img file. But my files are not readable.
Click to expand...
Click to collapse
Does anyone know if he can flash someone else's backed up persist.img?
crazynapkinman said:
Does anyone know if he can flash someone else's backed up persist.img?
Click to expand...
Click to collapse
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.
firoz3321 said:
There was a thread in this forum that mentioned the persist cannot be shared or doesn't work with others. Apparantly it contains sensor calibration data which usually will be unique.
Can someone confirm if your persist image is extractable with 7zip or similar. If so what am i doing wrong.
Click to expand...
Click to collapse
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img
crazynapkinman said:
You need to be unlocked and rooted. Then you will reboot to fastboot. From there, BOOT twrp (fastboot boot twrp.img)
Once booted, use TWRP to backup persist.img
Click to expand...
Click to collapse
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.
firoz3321 said:
Using root explorer i copied the persist image but that too was un extractable. The persist image that i took backup using the command in OP when i bought the device also doesn't extract.
And one more thing is TWRP doesn't seem to be working with 11 OS yet.
Click to expand...
Click to collapse
Need to downgrade to 10.
I pulled my persist image off of 10.
---------- Post added at 07:20 PM ---------- Previous post was at 07:08 PM ----------
From what I've read there's not reason to unzip the persist.img
If you backed it up with a WORKING persist present, then you simply need to boot to fastboot and flash your persist.img
It will replace the corrupted partition and you're good to go. No one on any forum I read said they actually extracted anything from the persist.img file itself.
They all had to extract (see backup) the WORKING persist.img and flash that with fastboot command.
You can extract working persist.img with the following command in adb:
dd if=/dev/block/by-name/persist of=/sdcard/persist.img
This will save it to your sdcard. Transfer that backup to your adb folder on pc. Reboot into fastboot and use the following command to flash it:
fastboot flash persist persist.img
I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.
firoz3321 said:
I do have working persist. There is a youtube video regarding same issue and ye extracted files from working persist. Your steps are clear and thank you for that .
My reason for asking was. If my files are corrupted i may damage more than solving. Hopefully the files i have are good.
Click to expand...
Click to collapse
Hopefully you're using the good backup you made and not something you downloaded...
GL!
crazynapkinman said:
Hopefully you're using the good backup you made and not something you downloaded...
GL!
Click to expand...
Click to collapse
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.
firoz3321 said:
Today i gave it to service.
Un rooted, locked boatloader and sent to service. Just wasn't daring enough as i wasn't sure if my image backup was safe.
Click to expand...
Click to collapse
Received the mobile back and the FP reader is working fine. :angel: