i am stuck with a problem and need your help, i created a data partition backup from TWRP, but when i tried to restore it gives an error extrac(tor) fail 255 i understand the data win files got corrupted, but i used winrar to extract all the data win files & got /data folder with most of the files inside, now i want to create a twrp flashable zip to write the extracted data to data partition of my htc10, i dont know how to create update script for mounting and writing to data partition if someone can please help in creating a simple zip file with correct meta-inf folder i'll copy my extracted files & flash to get my data back. please do reply guys i am counting upon you fellow members
Related
I've successfully scripted the automated creation of a file structure into which the contents of BOOT.IMG, SYSTEM.IMG, DATA.IMG, CACHE.IMG and SD-EXT.IMG are extracted. The script also creates a valid update-script file under ./META-DATA/....
The only issue I have is that I'm using windows so the .IMG files extracted as a yaffs file system, looses the original file permissions. I need someway to recreate the permissions in the update.zip.
Thats all.
Having a way of converting a nandroid backup to an update.zip means you can very easily cook custom roms from a nandroid backup, and port ROMs across phones using a portable .ZIP format.
hi all,
i want to ask for a help.
can u please explain to me, how do i go back to my backup.
i on stock rom before, then i rooted my phone and i flash custom rom.
and suddenly, it doesn't work.
but somehow i manage to install this rom.
http://forum.xda-developers.com/showthread.php?t=2013506
but, i cant read my sdcard.
and when i try to read my sdcard on recovery, it create folder 0 on my sdcard.
then , i copy out my backup to pc.
i flash my backup boot.img and flash it.
and try to restore my backup.
but my cwm recovery keep saying no directory found , and no files found.
not when i see back my , sd card on my pc, there is no 0 folder.
but in my recovery, it still read my 0 folder.
please help
Like i said, you mount the sdcard as a usb mass storage device in the recovery. There you see the directory \O
Copy all from there back to the root of the sdcard !
And like i said .... Send me a login and password by PM and i can check.
Download the program called teamviewer 8 free and install it on the pc. Open it and send me the codes tonight !
the problem solve!
based on mr hofs,
i mount sdcard in recovery.
copy back all my files in .0 directory and paste it in my root sdcard.
delete the .0 directory, flash my boot.img backup files.
and restore, it read my backup and successfully restore.
thanks a lot:laugh:
hi i flash i8160L with i8160 arabic files after that i edit some files in system folder for unknown baseband and i done job successfully
now everything are working fine (wifi,signal,Bluetooth)
i want to dump system partition and make a odin flash able file from that i know how to create ondin flash able file but i dont know
how to dump systemfs.img from phone even i dont know in which partition system file is located
please help me in this
need urgent replay
thanks
I recently tried a tethering hack I found on here after installing the Android 4.3 OTA update. The thread can be found here: http://forum.xda-developers.com/showthread.php?t=1732262&page=11. The specific hack I used was from user BlvJohn. He created a flashable zip file and I flashed it and afterwards my phone failed to boot. My phone is rooted and running TWRP recovery (latest version).
Steps I completed:
1. downloaded zip file to flash to desktop computer
2. made a copy of the file and renamed it to org_no_tether.zip
3. opened org_no_tether.zip so I could delete the new framework-res.apk file
4. copied my phone's current framework-res.apk file to the org_no_tether directory I created when unzipping file using droid explorer to access file
5. rezipped org_no_tether directory to org_no_tether.zip
6. placed both files on my external sd card
7. flashed
When I rebooted it just hung during the AT&T boot animation sequence. I tried wiping the cache, user data, dalvik cache, etc...to try and get it to boot to no avail. I ended up just having to reinstall the ROM using a zip file I found on these forums and everything runs great now. The file I used to reinstall the ROM via recovery was loserskaters found here http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18http://. Everything works great now but I'd still like to get the tethering hack.
In the instructions it said to copy the file to the external sd card so that's what I did, but what I'm wondering is if I was supposed to copy it to my sdcard instead where I place all other files to be flashed? I just wanted to be sure I didn't do something else wrong before I go through this process again and end up having the same result.
Thanks a lot for any help!
I've successfully rooted my Pixel C running Android 7.0, booted into TWRP, and made a set of backup files. These are 11 files with extensions like .win, .win.md5, .win000, .win001, and .win001.md5. Is there a way to convert these to image files?
[email protected] said:
I've successfully rooted my Pixel C running Android 7.0, booted into TWRP, and made a set of backup files. These are 11 files with extensions like .win, .win.md5, .win000, .win001, and .win001.md5. Is there a way to convert these to image files?
Click to expand...
Click to collapse
what is the purpose of creating image files ?
not sure if there is an tool existing .. but you can build an image file by hand.
rename the twrp backup files and add the extension ".tar" -> data.ext4.win000.tar
( data.ext4.win003 -> data.ext4.win003.tar )
untar all the files into one folder.
build a new image file.
as well you can use "dd" command .. to make a full dump of the partition.
this will be a big image file (approx. 25GB) .. the complete data partition.
just shrink the raw image afterwards .. (resize2fs -M)
If you have encrpyted data partition you need to decrypt ..
anyway .. the most important partition is "data" .. make a backup of data only.
flash the other partitions from stock/custom images and use fastboot.
hope this helps ...