My userdata.img probably became partially corrupt because I created it with cat while the phone was running, instead of in recovery mode :-(. Due to this, when I flash it, the phone doesn't boot and logs several messages related to not finding things on /data over and over, since it couldn't mount /data.
I can put back an older userdata.img just fine and boot the phone, so my methodology works. I'd guess the new userdata.img isn't entirely rubbish as a hex editor shows data.
Attempts to explore (loop-mount) or unpack (unyaffs) on my laptop or on the Android phone itself have failed without much explanations, for the new image as well as for the (known-good) old image. Notably, running the unyaffs2 coming with the latest yaffs2utils tells me it wants to unpack 147 objects but nothing ever shows up.
How can I recover?
You can also answer at android.stackexchange.com/questions/15592/how-to-recover-a-broken-userdata-img if you like.
Related
I flashed the packaged vold.fstab that is floating around the web (I don't have the link where I grabbed it from) and now I can't boot my Gtab. At the Viewsonic screen, the following messages appear in the top-left:
Code:
Detect a recovery command
Erasing MSC
Then it boots into CWM recovery. Every other boot attempt I make it past the Viewsonic screen and into the 'ANDROID' screen, but quickly reboot to Viewsonic screen with those messages.
Apparently my tab isn't recognizing the correct dir to boot from?? I'm not the most technically literate person (although I can follow other smart people's directions; I managed to get out of the dreaded boot-loop ). Can anyone help?
Reflash the ROM then right after (no reboot), flash the volds.fstab.zip again.
I'll try this out, thanks!
i had the same issue with the newer Cyanogen7 builds. I ended up just manually tweaking the vold.fstab file myself. It's really not difficult.
just change around anything that says SD Card to EMMC and EMMC to SD Card using root explorer
I noticed that the newer Cyanogen releases the file is a little different
btw, you may have to NVflash cos i tried reinstalling the rom and couldn't boot past the android screen
Hi all!
My Lenovo S6000L entered on a bootloop more than one week ago, apparently with no cause (no modifications made). The first thing I tried was entering recovery mode and wipe data and cache. Both were apparently successful. Then I reboot again and it continues with the bootloop (done this about 99 times).
Since then i have been reading as much as I could about what to do, but unsuccessfully. I decided to wipe dalvik-cache and see what happens, but the only way it came to my mind was using a update.zip file on the SD-card (because the SD-card is the only one place I can access). Here the problems became more annoying: haven't been able to run till the end any of the update.zip files I downloaded or made according with the tutorials I found. The message is always:
-- Install /sdcard ...
Installation aborted.
I have tried removing everything from the updater-script excepting the ui_print('Whatever') commands, hoping to see something else on my screen (and being afraid of errors being caused by eMMC access error), but message is the same.
Things I have tried:
Signed and unsigned zips
Unix and Windows line breaks on the script file (I'm using Sublime Text)
Writing all the commands in one line (anyways leaving one empty line at the end of the file)
No changes on the output of the screen. One of the downloaded zip files I have tried is a CWM ZIP, hoping to enter in a recovery mode that could let me delete de dalvik-cache (even if not sure yet about how much that could help).
In bootloop is quite difficult to use dba. I haven't been able to access the tablet using the computer yet. It' also quite challenging to get a stock ROM for this model.
Any help? I feel quite desperate.
Thanks for your time.
Hey All
I'm new to Android but not linux.
Bought cheap Allwinner type 5.1.1 tablet - 10.6" Fusion5 108 Octa Core Android Tablet PC
rooted it using KingRoot, messed around with Supersume to remove KingRoot and now device won't boot properly. Using adb I can see dmesg is complaining about debuggered which is actually now a zero byte file. su won't work now and I don't have the rights to fix it.
Before I did any of this the first thing I did as root was backup the mmc partitions to a USB stick.
The bootloader and recovery areas have not been changed.
Can I use my system partition backup to create a update.zip for use in recovery mode?
Or maybe in fastboot though I'm currently having problems getting fastboot to see my tablet whether I use linux or windows so recovery mode fix prefered..
lol
Looks like the solution is to post here, and then find a partial answer 5 minutes later.
fastboot command on linux didn't work (despite adb working, udev configured etc)
Then tried with manufacturer id
fastboot -i 0x1f3a
then works
Then did
fastboot -i 0x1f3a erase system
fastboot -i 0x1f3a flash system /home/user/android/13-11-16/system
It complained that about magic so I suspect this DIDN'T work. although data was sent.
fastboot -i 0x1f3a reboot
and device came up in a graphical environment asking for wireless password. Judging by network trace on my router I think it might be trying to download a factory image over the Internet. Will see.
Bit confused as my system parition backup is like 900Mb but when I did flash system I think it said device reported size was 32MB approx. More to learn
OK
The 32Mb was referring to buffer size, so can confirm system flash did work.
Device was booting, getting to graphical environment, and then trying to connect some web servers - not sure why really but seem to have got past that point.
Now can't install apps - get stuff like
W/art ( 9462): Unable to open /data/dalvik-cache/. to delete it's contents: Permission denied
W/art ( 9462): Unable to open /data/dalvik-cache/arm to delete it's contents: Permission denied
W/art ( 9462): Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Unable to relocate image '/system/framework/boot.art' from '/system/framework/arm/boot.art' to '/data/dalvik-cache/arm/[email protected]@boot.art': Only the zygote can create the global boot image.
Think /data is corrupt so will flash my backup of that.
I'm more thinking outloud at this point rather than expecting people to do it for me But I'll post anyway if that's ok if only for my own reference - though any insights by all means.
Can't flash data backup.
Ended up with 13Gb file from mmc copy when system was working so after img2img didn't seem to be working used ext2simg on it as it was a ext image.
Created a more reasonable sparse 887335016 file.
fastboot wouldn't flash it though complaining that data partition was unknown. Searching seems to suggest that sometimes the bootloader doesn't know about all partitions (though it does about system which was flashed ok).
Tried playing with other recovery environments. Not willing to flash anything at this point so trying flashboot boot <img>. No luck so far - device just stays on bootloader splash screen. Probably not great that this device is a Allwinner A38 to which there doesn't seem to be huge support at the moment.
Even tried flashboot boot <recovery partition dump> file I made and that doesn't work.
Trimmed the first 0x800 so image starts with kernel code without joy.
A binwalk of the initrd image inside the dump shows a init.recovery.sun8i.rc file, and a default.prop with
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
in init
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
write /sys/class/android_usb/android0/enable 1
start adbd
So assuming default.prop is used (I'm still learning) then that's why I can't adb when in recovery mode. Seems stupid to design it that way.
I'm thinking if I can restore data partition it will fix the can't install apps problem, though perhaps the /system part is fundamentally busted. If I can reinstall KingRoot and root again I assume the device will be usable as it would effectively undo my supersume attempt to remove it.
Env partition dump I made used by the bootloader there is
Code:
boot_normal=sunxi_flash read 40007800 boot;boota 40007800 boot
boot_recovery=sunxi_flash read 40007800 recovery;boota 40007800 recovery
Usage:
sunxi_flash read command parmeters :
parmeters 0 : addr to load(hex only)
parmeters 1 : the name of the part to be load
[parmeters 2] : the number of bytes to be load(hex only)
if [parmeters 2] not exist, the number of bytes to be load is the size of the part indecated on partemeter 1
Click to expand...
Click to collapse
So maybe I need to specify the correct memory location when I'm fastboot boot'ing
There's no image type header specifing load address at the start of the recovery part dump I made.
Didn't manage to boot the recovery image - don't know why but a challenge for another day. Would probably be easier with UART access or similar to see what is actually happening.
In the end I mounted my /system backup on my linux server, cleaned it of KingRoot crap, and flashed it. Now everything is fine! Except no root access and the script I added to give me it comes us as unlabeled in selinux and isn't accessible.
The learning journey continues
og0 said:
Didn't manage to boot the recovery image - don't know why but a challenge for another day. Would probably be easier with UART access or similar to see what is actually happening.
In the end I mounted my /system backup on my linux server, cleaned it of KingRoot crap, and flashed it. Now everything is fine! Except no root access and the script I added to give me it comes us as unlabeled in selinux and isn't accessible.
The learning journey continues
Click to expand...
Click to collapse
I know this is a 2 year old thread... but does the OP still have that firmware that fixed the tab??
I have a Fusion5_108 with the A83T allwinner processor, stuck in a boot loop, wont get past the 'no command' screen when trying to recover,
think my only option is to make an sd card with a working firmware on it, and load it onto the devise like that, but i cant find a firmware or anything for this tablet
Before I start, I'm aware there are great data recovery guides on this forum and elsewhere. Unfortunately, I was unable to find one pertaining to Nougat and my specific circumstances. Thank you for bearing with me.
How the Data Was Wiped
I ran "fastboot format userdata" to fix a "Decryption Unsuccessful" error message after going from LineageOS 14.1 to 15 on a Xiaomi Mi 5 Pro. Because I was in a hurry to get my phone back online, I foolishly assumed the wipe would leave /data/media intact, just like TWRP, without making sure of it. I know the assumption was wishful thinking at best and I can see the irony in then spending the rest of the day trying to undo the damage.
How the Data Was Dumped
Immediately after finishing the fastboot format, I booted back into TWRP 3.1.1-0 where I discovered the extent of the data loss. Since I hadn't flashed a ROM and didn't want to write anything else to my /data partition, I did a "adb pull /dev/block/sda14 sda14.img" on my computer over USB with my phone still in recovery. With a 128GB phone, the process took a whopping 8102.059s to finish.
How I attempted to Recover Data
I let both R-Studio 8.3 and UFS File Explorer Professional Recovery 5.23.4 scan through my dump to no avail. All they found were meaningless, small files, mostly in a .txt or .so format. I also attempted to mount the image using DiskInternals Linux Reader 2.6, but PhotoRec didn't recognise the volume.
Where do I go From Here?
Christian Weiske wrote about his attempt at recovering photos from a Galaxy S5 mini, running Marshmallow. He noted that data he pulled in Windows was broken using various commands until he tried "adb exec-out". Does the problem lie in my pulled data also being broken/incomplete, or is "fastboot format" actually capable of completely destroying more than 100GB worth of data in mere seconds on TRIM-enabled devices? If I am to do a second /data dump using a different method, I would have to do it directly to my computer as my phone doesn't have a microSD slot. I should add that, to the best of my memory, I never encrypted the storage, as I went directly from CyanogenMod to LineageOS using the experimental migration build.
To anyone who chimes in, if only to tell me that I should suck it up and stick to whatever data I have backed up and move on, I'll be most appreciative! Even more so if anyone can shed some light on modern-day Android data recovery/wiping and limitations.
I'm going thru a recovery process myself. Using a few guides. First I completed a raw dump of the whole phone w/out installing any os over the phone. I'm about to check that and see if testdisk can find something via https://roubert.name/joakim/androidfilerecovery/
In the background, I have another dump going on from https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705 guide. Hopefully, something comes up.
Hey all. Looking for some help with my userdata.img file. Here's the story:
I smashed my Galaxy S5 screen so it and the digitizer were not working. The phone was running Lineage OS and was encrypted with full disk encryption.
I booted into TWRP recovery and unlocked the disk using
Code:
adb twrp decrypt <password>
After this, I used dd to make an image of the block device which /data was mounted from (in my case it was /dev/block/mmcblk0p26). I dd'ed this to a file called userdata.img.
Since then I got a new S5, flashed TWRP and installed Lineage once again.
From here, what I've managed to do is dd the userdata.img file back onto the same block device which I dd'd it from.
After this I booted the phone and was taken to a page saying that the phone is encrypting. After a few minutes the phone reboots.
This boots the phone up fine, without asking to unlock the encryption. But quickly after this I start getting lots of errors including Process system is not responding and the phone and wifi causing crashes. Worst of all, after a few minutes the phone crashes and puts me at a screen which says "Phone is starting". During this time, the phone is still accessible by adb. I can also see in the time before this happens that all my apps and their content are still present.
The main reason I want to boot my phone again is to take a backup of one of my apps which contains lots of old and important messages which it is only possible to do from within the app's settings menu (due to encryption used in the app).
I can see a few ways I could do this:
1) Is there any way I can emulate the phone using the userdata.img file I took?
2) Is there any way I can modify any file the /data partition after dd'ing the userdata.img file so that encryption does not start on next boot. I think this might be causing the errors.
Hope someone can help with this!
Thanks