Related
Hi guys,
Looking for helps here.
First I want to thank the guy created the "Overcome for Gingerbread", it comes w/ a great details instruction and I successfully upgraded.
My tab was original from Bell Canada, the phone feature was locked. I was able to unlock it by modifying the nv_data.bin file...
But now after I upgraded to Gingerbread, my phone feature is disabled again so I suppose I should do the whole unlock process again. However when I looked for the nv_data.bin file, the directory /efs is empty?!?!?!. Can someone help me here?
Thanks,
Edit: I found a nv_data.bin file on my laptop (not sure if it's the orginial one), trying to copy it to the /efs folder on the tablet, but I got error "not enough space"...
What program u using to copy with. Put that file on the SD card first from your PC.
Then get EF File Explorer rooted, and copy that from the SD card to the /efs directory
The nv_data.bin edit unlocks the tablet to allow use on other carriers like rogers, fido etc.
It does not provide phone usage, you need to flash a european rom to enable the phone,
then you need to flash a suitable modem to allow 3G data and phone, then edit your apn info.
Are you sure efs is empty, maybe your no longer rooted and can't see it?
You get the not enough space error because you have most probably renamed the original file and are trying to copy the new one in the directory. Delete the file and also the.md5 correspondent (it will be recreated on reboot.
P
Thanks for all the replies guys, but my problem is still there.
@Sonictab: I'm rooted and I'm sure that my /efs folder is empty.
@StarLog: I'm using Super Manager to copy the file
Now I can't even download files from the browser nor using the market place to download any apps. Something went wrong and I'm not sure what. Should I downgrade?
Here is what I have done for my personal webtop so far.
Download
To install:
Make a partition on a SDCard, formatted ext3, so that the first partition is FAT, second partition is EXT3.(2GB should be fine, YEMV)
Extract contents of osh2.tar.bz2 to this ext3 partition.
Make a backup of /osh/ubuntu.sh
Overwrite /osh/ubuntu.sh with the one on the root of the SDCard's EXT3 partition.
Backup your /data/home/adas folder.
Remove /data/home/adas, leaving just /data/home.
Reboot the phone.
You will need Linux to extract the tar properly and create the SDCard partitions.
You do not need to be unlocked or have a different kernel, you just need to replace ubuntu.sh, so rooted, temp root, whatever. I created everything from a stock Bell phone. Android 2.3.6. If anything doesn't work, just replace ubuntu.sh with the original file or just remove your sdcard.
Cheers!
edit: changed link
what has been modified:
fuse based smbnetfs installed, stock kernel can access windows shares and play video using motorola hd media center.
open office installed, gimp, some games
lxde set up, theme preconfigured.
No need for dependencies to be fixed or webtop to sd apps run, has zero errors and sudo apt-get dist-upgrade has completed without errors several times so adding extra sources and doing dist-upgrade won't cause errors.
Replaced firefox 7 with 8, rest is Bell webtop.
Been installing and playing with it for a while now, can't recall all the mods.
Yes, you can put the tarball on the phone and extract it to the sdcard that way, you just need to mount the partition. I keep a copy in internal memory to be able to restore when I install/uninstall something I shouldn't.
EDIT:
If you use xarchiver from another webtop to untar the archive, you may need more than 2GB.
Can you put the .tar file on the phone and extract there? I ask because I only have access to Windows machines. Creating the partitions on the sdcard is easy with MiniTool Partition on Windows.
I am can't downloading this file, webserver says: "This file is no longer available."
How has this webtop been modified?
Ramble via webtop:
My approach is to avoid established scripts for fixing dependencies and apps for moving webtop to sd card. Not that I have anything against those, but they were developed using ATT phones and might miss some compatibility with Bell.
One key difference for getting going from scratch is that I installed a standard armel busybox from the busybox site, that avoided a lot of errors when installing debs. Not sure where the busybox comes from in apps2sd but it is not as up to date and results in more errors with missing command line options.
I also didn't want to change/replace the contents of the phone too much so I could easily revert to stock, there is this ICS rumour..
This is what I did:
Starting off I updated the sources.list to be jaunty and just worked through the errors by installing debs manually. lxterminal was installed via deb and tomoyo was disabled by renaming the init and start files. Basically, I did a force install via deb file of some rootfs package contents, coreutils, cpio, dbus, dhcp, gpgv, grep, udev. All references to -mot versions were stripped of the -mot suffix so they could be more easily upgraded. I left the references to ~mot and -motorola in the versions of packages, not sure why, just did. Eventually I got to a place where synaptic was installed and I had no errors. Saved the state in a tarball and kept experimenting with installing things.
I really wanted a home folder elsewhere than /data/home but there are too many hard references to it in webtop for stability, I found a lot in scripts but I suspect they are in binaries as well. You can rbind once in webtop but you need it to have stuff in there during boot, not mix and match configs.
I tried an external hard drive, but there is a fundamental flaw in that logic, they only turn on once you open the lid of the lapdock, so you can't have boot files on it.
I copied the firefox-8.0 from ATT, deleted firefox-7, updated the soft links to point to the 8 version, redid profile.zip to have xda be the home page and adblock installed already, tossed in .xdg-bookmarks to add Network to pcmanfm. I originally had all the home folder stuff in profile.zip but some part of the scripts mess with settings and not everything was carrying over.
So, I did a tarball of my home dir's dot files and put it in /osh2/home/adas so when I do a factory reset and adas is wiped it restores my config. Tip: removing the entire adas folder gives you the same effect for webtop as a factory reset. Reboot and you are back to where you were.
I tried all the window managers, avant/awn anything is annoying when it shifts items left and right when an app opened or closed. I was able to have the stock awn working with a cairo menu, but it still shifted things left and right and was slow. I tried recompiling awn on the phone to get the option to just have launchers but there is this tendency for anything new you compile to require a new libc6. Xfce is cool, menu looked odd though, went with lxde, easy enough to switch if you want. Note: Compiz anything is a waste of time.
I have removed the stock webtop theme and replaced it with clearlooks and murrine window decoration. lxpanel is transparent via manual hack of the config file, the gui for changing things always sets alpha to 0, bug into the prefs app.
I could go on and on, but I like what I have done so far, thought I would pass it along. The main bit for me is not having to install a new kernel or wipe existing partitions, make a lot of phone mods, a pure stock phone can have a custom webtop, just needs to be rooted to copy one file over. Also, I like being able to watch tv shows on my lapdock, worth the price of admission right there for me.
Oh, size is around 1.4GB untarred, so it's a least a 2GB ext3 partition. I have an option in there for using mmcblk1p3 for var if you want to copy var over there formatted with smaller clusters. There are a few flags to control things, if you didn't want to remove your sdcard, touch /osh/no_osh2 and reboot the phone to disable. /osh/var_ownp enables the mounting and use of a third partition on the sdcard dedicated to /var. Use that one carefully, commit to it before installing a lot of things, having a mix and match could break the custom webtop.
Cheers!
Thanks for putting this up, I'd like to give it a try but am having difficulties, possibly cause i'm running Nochatrix (ATT 2.3.6).
When you say 'extract properly' to the EXT3 partition, what command would you use? Should extracting first then copying over work? Because I tried that, and it didn't!
Cheers
It has to be linux, either on the phone or on a pc so that tar -xvf will keep the ownership and file permissions.
VMware Player
CaelanT said:
Can you put the .tar file on the phone and extract there? I ask because I only have access to Windows machines. Creating the partitions on the sdcard is easy with MiniTool Partition on Windows.
Click to expand...
Click to collapse
Download VMware Player and the free copy of linux.. now you can run Linux.. :highfive:
https://my.vmware.com/web/vmware/evalcenter?p=player
NFHimself said:
... so that tar -xvf will keep the ownership and file permissions.
Click to expand...
Click to collapse
That's it, thanks. I was over-complicating things, putting in unnecessary arguments and trying to copy it over using -C. In the end I just copied the tar to the EXT3 and just unpacked it there.
Anyways, it works great! Everything ive quickly tried works nicely, openoffice, synaptic, Gnometris , etc, it's clean and quick, just what I was after.
can make a .zip CWM flashable file???
---------- Post added at 08:37 PM ---------- Previous post was at 08:37 PM ----------
jpinoy said:
Download VMware Player and the free copy of linux.. now you can run Linux.. :highfive:
https://my.vmware.com/web/vmware/evalcenter?p=player
Click to expand...
Click to collapse
where can i find Linux OS??
It work on stock 2.3.4?
It work on stock 2.3.4?
Click to expand...
Click to collapse
I haven't tested it, the webtop is from Bell's 2.3.6, probably not a large difference, but can't say for sure.
Can you make a CWM zip?
Click to expand...
Click to collapse
Yes, I can.
Cheers!
Chimpdaddy;[URL="tel:28700385" said:
28700385[/URL]]That's it, thanks. I was over-complicating things, putting in unnecessary arguments and trying to copy it over using -C. In the end I just copied the tar to the EXT3 and just unpacked it there.
Anyways, it works great! Everything ive quickly tried works nicely, openoffice, synaptic, Gnometris , etc, it's clean and quick, just what I was after.
Click to expand...
Click to collapse
Glad you like it!
Cheers!
I'd love to give this one a try. I'm using Webtop2SD right now. Can someone give a more detailed step-by-step instruction please?
Chimpdaddy;[URL="tel:28700385" said:
28700385[/URL]]That's it, thanks. I was over-complicating things, putting in unnecessary arguments and trying to copy it over using -C. In the end I just copied the tar to the EXT3 and just unpacked it there.
Anyways, it works great! Everything ive quickly tried works nicely, openoffice, synaptic, Gnometris , etc, it's clean and quick, just what I was after.
Click to expand...
Click to collapse
qaplus;[URL="tel:28824484" said:
28824484[/URL]]I'd love to give this one a try. I'm using Webtop2SD right now. Can someone give a more detailed step-by-step instruction please?
Click to expand...
Click to collapse
This does not use webtop2sd, so you would need to uninstall that first as it would likely cause problems.
Not sure how detailed you need instructions.
Cheers!
NFHimself said:
I haven't tested it, the webtop is from Bell's 2.3.6, probably not a large difference, but can't say for sure.
Yes, I can.
Cheers!
Click to expand...
Click to collapse
Thanks, but not seeing any zip on OP .....
I have limited experience with linux. What I got:
1. AT&T Atrix on 2.4.6.
2. Webtop2SD created ext3 partition on SD card.
What I plan to do:
1. Wipe ext3 partiion and copy the SimpleTop tar file to it
2. Log into Webtop ( boot from the Webtop partition from the internal sd card)
3. backup .sh and adas folder
4. untar simpletop in the ext3 partition
5. copy the new .sh file.
Will these steps work? I feel it's bit dangerous to do this on the phone. But how can I do this on a windows computer?
Thanks for any suggestions.
qaplus said:
I have limited experience with linux. What I got:
1. AT&T Atrix on 2.4.6.
2. Webtop2SD created ext3 partition on SD card.
What I plan to do:
1. Wipe ext3 partiion and copy the SimpleTop tar file to it
2. Log into Webtop ( boot from the Webtop partition from the internal sd card)
3. backup .sh and adas folder
4. untar simpletop in the ext3 partition
5. copy the new .sh file.
Will these steps work? I feel it's bit dangerous to do this on the phone. But how can I do this on a windows computer?
Thanks for any suggestions.
Click to expand...
Click to collapse
That is pretty much it. Just remember to be super user and include -p if using tar for backup. Tar -cvpjf /sdcard/ADAS.tar.bz2 . for example. Also, you don't want to be in webtop2sd mode if you are doing this but from a rooted webtop on the the phone itself. Or you could do it all from an adb shell.
Cheers!
Sent from my MB860 using xda premium
NFHimself said:
That is pretty much it. Just remember to be super user and include -p if using tar for backup. Tar -cvpjf /sdcard/ADAS.tar.bz2 . for example. Also, you don't want to be in webtop2sd mode if you are doing this but from a rooted webtop on the the phone itself. Or you could do it all from an adb shell.
Cheers!
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I haven't used adb before. Can you list the commands in adb to install this? Thanks.
qaplus said:
I haven't used adb before. Can you list the commands in adb to install this? Thanks.
Click to expand...
Click to collapse
ADB is just a way to get a remote shell going over usb, so the commands are linux shell commands.
I would do something like this:
(Blank ext3 partition on sdcard, second partition)
adb shell
$ shsu
# mkdir /mnt/asec/osh2
# mount -t ext3 /dev/block/mmcblk1p2 /mnt/asec/osh2
# cd /mnt/asec/osh2
# tar -xvf /sdcard/osh2.tar.bz2
# cp /osh/ubuntu.sh /sdcard/
# cp ubuntu.sh /osh/
# cd /data/home
# tar -cvpjf /sdcard/adas.tar.bz2 .
# rm -r /adas
# sync
# umount /mnt/asec/osh2
# reboot
Cheers!
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
EDIT: If you can't run the script with the ./ command, chmod +x the file
Antonyb1995 said:
Hello everyone,
I've been playing around with adding root to my stock ROM these past few days, and have found it very slow and tedious trying to remember all the commands to unpack and repack the images.
To make things simpler I've created a script that automates almost the whole process.
I've named it worker as it does all the work for you, and it is just simply a bash script. But it makes things a lot quicker and easier.
I have only been able to test with my S3 Mini, but should work with any ROM that has boot.img and system.img
Simply extract the .img files from the tar.md5 or .zip ROM file, and place them in the original folder.
Once you have those in the original folder just simply run the worker.txt file from the terminal, making sure you are in the worker folder directory.
When the script is run you will be given the options to unpack/repack system.img, mount system.img (This is after you extract it do not try and mount the original file it wont work), unpack/repack boot.img, unpack/repack ramdisk, create ROM (This will create an odin flashable tar.md5 from the repacked files) and finally clean up (This will clear all unpacked and repacked files only leaving the files in the original folder)
To select an option simply type y then enter to execute that command or just hit enter to skip.
When the system.img is mounted it will be mounted in the mount folder.
When repacking the system.img you will be prompted to enter the file size, if you have and S3 Mini I8190N simply type s3mini for the size (This may work for other S3 models but I have no way of testing so let me know). If you have a different device use the file size of the original UNMODIFIED system.img, enter the size in bytes or MB (If entering in MB use this format, xxx being a number. xxxM).
Please give me feedback for improvements or problems,
Thanks for reading.
P.S. Sorry if in wrong place please move if necessary
Click to expand...
Click to collapse
work on gt-i8200n to?
linklusitano said:
work on gt-i8200n to?
Click to expand...
Click to collapse
No reason why not, I'm just not able to test others
Antonyb1995 said:
No reason why not, I'm just not able to test others
Click to expand...
Click to collapse
testing
linklusitano said:
testing
Click to expand...
Click to collapse
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Antonyb1995 said:
Great let me know if it works!
EDIT: Make sure you enter the right size for the system.img file, the pre entered size using s3mini may work fine as they are very similar devices.
Click to expand...
Click to collapse
how do i run worker.txt?
linklusitano said:
how do i run worker.txt?
Click to expand...
Click to collapse
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Antonyb1995 said:
Your using Linux right?
Open a terminal and change directory to the worker folder, once there type ./worker.txt and it should run. If it doesn't issue this command chmod +x worker.txt that should fix it.
Click to expand...
Click to collapse
windows 8.1
linklusitano said:
windows 8.1
Click to expand...
Click to collapse
Ah okay, If you install Cygwin you can run bash scripts in Windows.
LINK: https://www.cygwin.com/
[Q&A] [Stock ROM] Easy Stock Reset | Many Versions | Stock ROM + Recovery + Radio In
Q&A for [Stock ROM] Easy Stock Reset | Many Versions | Stock ROM + Recovery + Radio Included
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Stock ROM] Easy Stock Reset | Many Versions | Stock ROM + Recovery + Radio Included. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Can' t Flash
Every time I try to flash the Optus AU reset onto my VODAPHONE AU M7, it either gets stuck at 10% if i do it with a full wipe, or 0% if I don't. Also, it never passes and MD5 verification, after multiple separate downloads.
Anyone know what to do?
Thanks.
TWRP back up of stock rom and stock recovery OTA 6.11.980.12
Crushalot
I have a TWRP backup of stock rom from OTA 6.11.980.12 (Optus Australia) if you are interested I can pm the link to you along with the stock recovery that came with that OTA, for you to make (when you have time ect) an aroma reset tool for Optus Aussie users that is current and only just pre Android L release for sense roms.
Let me know if that would help
Australian Optus Firmware & Nand of stock rom Rom
Crushalot
In case the mood takes you, and you one day feel like making an easy aroma reset for Optus Aussie users that will reset HTC m7-ul PNO7400 devices back to a (only just) pre Android L update, here is a TWRP back up of stock rom (ota 6.11.980.12) Optus Australia as, well as the Optus Aussie OTA 6.11.980.12 (contains stock recovery) 2x OTA links originally posted by deevan
TWRP Nand of stock rom Android 4.4.3, from ota 6.11.980.12 (Australia Optus)
mega.co.nz/#!BhBXBaBT!Fjsg4FNe3AzUCR-aTdiNOwM71zx6-zzKkVbuY-rZqWk
GREAT work BTW! I used your tool to successfully return my device to stock (for the purposes of updating my firmware) worked like a charm!!
firmware.6.11.980.10.zip 43.1 MB (by deeevan)
mega.co.nz/#!QlIjzZoA!R18LEGCFJ85YV91rgiViohqw-QCzXO4fVEVm9h4ab68
firmware.6.11.980.12.zip 19.1 MB (By deeevan)
mega.co.nz/#!N4oS3aSZ!z2aM04WPtN2p1d9cWnmwkBi6UY_sNCbDB0ZBDAe 2RMY
Im still under 10 posts so I cant post full links.
This may help ppl go back to stock in time for the Android L OTA push!
GREAT work BTW! I used your tool to successfully return my device to stock (for the purposes of updating my firmware) worked like a charm!!
Joeisgood99 said:
Crushalot
I have a TWRP backup of stock rom from OTA 6.11.980.12 (Optus Australia) if you are interested I can pm the link to you along with the stock recovery that came with that OTA, for you to make (when you have time ect) an aroma reset tool for Optus Aussie users that is current and only just pre Android L release for sense roms.
Let me know if that would help
Click to expand...
Click to collapse
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
yatindroid said:
Install ubuntu open ubuntu
Extract backup file in ubuntu
Click to expand...
Click to collapse
If you want to use windows instead of linux, you can extract twrp backup using cygwin. All you need to do is to rename your backup files adding .tar extension then extract them using cygwin
Code:
tar -xvf your_file_name.ext4.win.tar
eg. If you want to extract system.ext4.win000, system.ext4.win001 and data.ext4.win, rename them system.ext4.win000.tar, system.ext4.win001.tar and data.ext4.win.tar. Move the system backup files to C:\Cygwin\Home\UserName\backup\System and data backup to C:\Cygwin\Home\UserName\backup\Data
open a cygwin command prompt and change directory to the correct location:
Code:
cd C:\Cygwin\Home\UserName\backup\System
then in cygwin command prompt:
Code:
tar -xvf system.ext4.win000.tar
tar -xvf system.ext4.win001.tar
Code:
cd C:\Cygwin\Home\UserName\backup\Data
tar -xvf data.ext4.win.tar
Then you have 2 folders, One System folder and one Data folder you can use to make you reset rom.
alray said:
If you want to use windows instead of linux, you can extract twrp backup using cygwin. All you need to do is to rename your backup files adding .tar extension then extract them using cygwin
Code:
tar -xvf your_file_name.ext4.win.tar
eg. If you want to extract system.ext4.win000, system.ext4.win001 and data.ext4.win, rename them system.ext4.win000.tar, system.ext4.win001.tar and data.ext4.win.tar. Move the system backup files to C:\Cygwin\Home\UserName\backup\System and data backup to C:\Cygwin\Home\UserName\backup\Data
open a cygwin command prompt and change directory to the correct location:
Code:
cd C:\Cygwin\Home\UserName\backup\System
then in cygwin command prompt:
Code:
tar system.ext4.win000.tar
tar system.ext4.win000.tar
Code:
cd C:\Cygwin\Home\UserName\backup\Data
tar data.ext4.win.tar
Then you have 2 folders, One System folder and one Data folder you can use to make you reset rom.
Click to expand...
Click to collapse
Yes sir, that's exactly the method i use :good:
Thank you So MUCH!
I'll try that as soon as I get a chance, and report back
Cheers for the help. ?
yatindroid said:
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
Click to expand...
Click to collapse
yatindroid said:
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
Click to expand...
Click to collapse
alray said:
If you want to use windows instead of linux, you can extract twrp backup using cygwin. All you need to do is to rename your backup files adding .tar extension then extract them using cygwin
Code:
tar -xvf your_file_name.ext4.win.tar
eg. If you want to extract system.ext4.win000, system.ext4.win001 and data.ext4.win, rename them system.ext4.win000.tar, system.ext4.win001.tar and data.ext4.win.tar. Move the system backup files to C:\Cygwin\Home\UserName\backup\System and data backup to C:\Cygwin\Home\UserName\backup\Data
open a cygwin command prompt and change directory to the correct location:
Code:
cd C:\Cygwin\Home\UserName\backup\System
then in cygwin command prompt:
Code:
tar system.ext4.win000.tar
tar system.ext4.win000.tar
Code:
cd C:\Cygwin\Home\UserName\backup\Data
tar data.ext4.win.tar
Then you have 2 folders, One System folder and one Data folder you can use to make you reset rom.
Click to expand...
Click to collapse
Thanks Mate.
I will try on Ubuntu first as I use that about 90%of the time. I'll reply with results hopefully tomorrow! Excited to make my own easy reset with aroma.
Had to unlock bootloader via HTC token when my phone is S-Off...
My HTC M7 UL (PID)PNO7400, was rooted and later S-Off with fire water.
I had custom rom and recovery ect. After 6 months of this I wanted to update my firmware but for various reasons didn't want to do it via RUU so I found and used crushalots Easy Recovery Reset Tool.
This worked perfectly.
During the aroma install I chose NOT to install any firmware, just stock recovery and rom.
I also chose not to keep root as I believed that I may not be able to install OTA updates with rooted stock. (right or wrong?)
Immediately after everything was installed I was running stock 2.24.980.2 rom and recovery on 4.20.980.x firmware.
After relocking my bootloader via fastboot, there was no issues, my phone just downloaded several OTA in a row, installed each without a hitch, and about an hour and a half later I had a stock phone with the latest 6.11.980.12 firmware and software, with S-Off.
(BTW re locking the bootloader did not delete any of my data.)
As soon as this was finished I wanted to re install my beloved eragon rom, re gain root, and get my phone back the way it was pre the firmware update.
Having S-Off I thought this would be easy (fastboot flash recovery path/to/custom/recovery.img)
Didn't work.
Unfortunately I didn't keep a copy of the error message I got in terminal, however, I didnt have write permissions on that particular partition. (apologies to anyone trying to help as I know details are important here)
This stumped me, as I have rooted 3 other (older) HTC desire by getting S-Off then flashing custom recovery.img, (These phones were running 1.44 version of fastboot as opposed to my M7s 1.57) I tried to un lock the bootloader via fastboot commands just in case that worked post S-Off ie (fastboot oem unlock) but that didn't work. Firewater doesn't install its own bootloader so locking and unlocking via the s-off tool were not an option either.
I had to re apply to HTC for an unlock token and flash that before I could flash a custom recovery. I plan go back to stock again for the purposes of taking carrier OTA when my carrier starts updating with Android L, so would like to know if this is normal, if not how I possibly stuffed up.
Can any one explain why I had to unlock bootloader via HTC site when my phone is S-Off?
I'm interested in peoples thoughts/knowledge
Many thanks
yatindroid said:
You can make that your self
You want to I can help you
It's easy
1st time with help of @crushalot I made 4 reset Rom for India version
Make TWRP backup of Rom which you want to make stock Rom reset zip
Install ubuntu open ubuntu
Extract backup file in ubuntu
You need system folder + data/preload folder + stock Recovery + boot.img + radio.img (all files from same version)
Extract any of old reset Rom zip
Replace files and folders from New one
Now edit aroma script in meta-inf folderwith notepad +
Edit details Rom version radio version etc
Zip all files and folders
It's ready
Click to expand...
Click to collapse
Hi Mate.
Thanks again. A little help needed.
When extracting the .rar from the TWRP recovery I made, using terminal command line [7z x /path/to/some.rar] in ubuntu i get 4300 of this type of error
can not open output file system/bin/mkswap
can not open output file system/bin/mkswap
can not open output file system/bin/readlink...ect
Basically at the end I get a system folder with about 3 items in it, as 7zip .rar tool cant decompress most of the files from the .rar
Right clicking on system.ext4.win.000 and system.ext4.win001 and selecting 'Extract files here' or 'open archive' results in error "could not open 'xx'. Archive type not supported."
Are you able to give me more detailed instructions on how to extract/unpack the system.ext4.win.000 and system.ext4.win001
Do I need to change the file name before extracting ?
Extracting the files from crushalots tool and extracting the files from the new TWRP then replacing relevant files and changing the manifest to reflect said change in Easy Recovery tool seems quite simple, however Im having trouble just extracting the files....
Im missing something obvious.
Thanks.
Joeisgood99 said:
Hi Mate.
Thanks again. A little help needed.
When extracting the .rar from the TWRP recovery I made, using terminal command line [7z x /path/to/some.rar] in ubuntu i get 4300 of this type of error
can not open output file system/bin/mkswap
can not open output file system/bin/mkswap
can not open output file system/bin/readlink...ect
Basically at the end I get a system folder with about 3 items in it, as 7zip .rar tool cant decompress most of the files from the .rar
Right clicking on system.ext4.win.000 and system.ext4.win001 and selecting 'Extract files here' or 'open archive' results in error "could not open 'xx'. Archive type not supported."
Are you able to give me more detailed instructions on how to extract/unpack the system.ext4.win.000 and system.ext4.win001
Do I need to change the file name before extracting ?
Extracting the files from crushalots tool and extracting the files from the new TWRP then replacing relevant files and changing the manifest to reflect said change in Easy Recovery tool seems quite simple, however Im having trouble just extracting the files....
Im missing something obvious.
Thanks.
Click to expand...
Click to collapse
I simply extract system.ext4.win000 file in Ubuntu nothing more needed not a single error
its tar not rar !
Whoops! . Tar.
Thanks again I'll keep trying.
Did crushalot send you any written instructions? Are they in a thread somewhere, or just basically what you already posted?
Thanks for your time.
Joeisgood99 said:
Whoops! . Tar.
Thanks again I'll keep trying.
Did crushalot send you any written instructions? Are they in a thread somewhere, or just basically what you already posted?
Thanks for your time.
Click to expand...
Click to collapse
I asked some questions via PM he just replied that
ask anything when you stuck
yatindroid said:
I asked some questions via PM he just replied that
ask anything when you stuck
Click to expand...
Click to collapse
For anyone else following this thread atm I solved the problem by re naming the system file extension in TWRP recovery from . win to . tar. In some TWRP back ups there were 2 system folders. A system.4ext000.win and system. 4ext001.win I just merged them during the extraction process.
Also there was no Data/preloaded folder in crushalots reset tool or in any twrp backup I have made.
Haven't tested the modified reset tool yet but will let u all know if I did it correctly!
Joeisgood99 said:
For anyone else following this thread atm I solved the problem by re naming the system file extension in TWRP recovery from . win to . tar.
Click to expand...
Click to collapse
Exactly, see post #6
In some TWRP back ups there were 2 system folders. A system.4ext000.win and system. 4ext001.win I just merged them during the extraction process.
Click to expand...
Click to collapse
Exactly, there are 2 system archive because of the file size restriction. Merging them after extracting the files is correct.
Also there was no Data/preloaded folder in crushalots reset tool or in any twrp backup I have made.
Click to expand...
Click to collapse
Without /data/preload, your reset rom will not be ota update ready. You don't have /data/preload in your backup probably because you have unlocked the bootloader and did the nandroid backup after (unlocking bootloader erase /data/preload)
Joeisgood99 said:
For anyone else following this thread atm I solved the problem by re naming the system file extension in TWRP recovery from . win to . tar. In some TWRP back ups there were 2 system folders. A system.4ext000.win and system. 4ext001.win I just merged them during the extraction process.
Also there was no Data/preloaded folder in crushalots reset tool or in any twrp backup I have made.
Haven't tested the modified reset tool yet but will let u all know if I did it correctly!
Click to expand...
Click to collapse
In Ubuntu install 7zip software
don't rename anything just open with archive manager
system.4ext000.win open this
crushalot tool not have data/preload because most of tool was 3.xx version sense 5.5 that time preload files included in system folder
yatindroid said:
In Ubuntu install 7zip software
don't rename anything just open with archive manager
system.4ext000.win open this
crushalot tool not have data/preload because most of tool was 3.xx version sense 5.5 that time preload files included in system folder
Click to expand...
Click to collapse
Thanks again yatindroid
I already have 7zip installed, However there is no option in archive manager to extract anything with it. After cd to file location I can view the . win file in terminal using [7z l file. win] but the [7z x file.win - d folder/i-want/extracted/to] command outputs the same error as stated in above post.
Q1) That aside the last step in this whole process is to zip it all up again as a . zip, so I'll be changing the file extension anyway, so does it matter if I change the file extension from . win to .tar for the purposes of extracting? If so ease explain why.
Q2) the ONLY place I have found a data/preload folder is inside a firmware .zip extracted from an OTA. It's definitely not in any TWRP back up. Did you leave that detail out of your initial instructions? Can you please tell me where to get the /preload folder from if not from the same OTA the recovery.img comes from.
Q3) do I put the data/preload folder inside the system folder of the reset tool or have it separate, along with radio.img, boot. img, recovery.img and aroma files ect.
Thanks for your time.
---------- Post added at 09:46 AM ---------- Previous post was at 09:33 AM ----------
alray said:
Exactly, see post #6
Exactly, there are 2 system archive because of the file size restriction. Merging them after extracting the files is correct.
Without /data/preload, your reset rom will not be ota update ready. You don't have /data/preload in your backup probably because you have unlocked the bootloader and did the nandroid backup after (unlocking bootloader erase /data/preload)
Click to expand...
Click to collapse
Thanks array.
I replied to the other post before yours came up. Forgive me if I ask similar questions.
I'm assuming I just copy the /preload folder from the same OTA I get the radio and recovery. img from.
Do I put the /preload folder inside any other folder within reset tool for a 6.xx version or have it beside the system folder and .img files.
Regards and Thanks.
Joeisgood99 said:
I'm assuming I just copy the /preload folder from the same OTA I get the radio and recovery. img from.
Click to expand...
Click to collapse
It should work. The data/preload folder from an ota zip usually (afaik this is true for the dev edition version) include all /data/preload files. If its the same thing for your version then you should be fine. In /data/preload you should have these files:
YOUR_CID.XML
All the weather animations (mp4 files)
some .png files for photo editing
htc preloaded app like flashlight.apk and calculator.apk. You might have more app depending your version.
Do I put the /preload folder inside any other folder within reset tool for a 6.xx version or have it beside the system folder and .img files.
Regards and Thanks.
Click to expand...
Click to collapse
the folder must be in your_reset_rom.zip/data/preload
{
"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"
}
alray said:
It should work. The data/preload folder from an ota zip usually (afaik this is true for the dev edition version) include all /data/preload files. If its the same thing for your version then you should be fine. In /data/preload you should have these files:
YOUR_CID.XML
All the weather animations (mp4 files)
some .png files for photo editing
htc preloaded app like flashlight.apk and calculator.apk. You might have more app depending your version.
the folder must be in your_reset_rom.zip/data/preload
Click to expand...
Click to collapse
Thanks for your excellent and timely reply.
More Qs.
I now have all folders as per your above post. I have taken data/preload, boot.img radio.img and recovery.img straight from OTA. 6.11.980.10
However my stock nand was of 6.11.980.12.
Q1) So do you know if having a system folder derived from a slightly newer version work? As far as I know the .12 OTA was a patch for the 'no voice during call' bug. OTA. 6.11.xxx. 12 did not contain a radio.img AND I can't get a data/preload folder for that ota as I can only find a 6.11.xxx.12 firmware. Not the whole OTA, which is why I reverted to making a . 980.10 reset tool despite having a slightly newer NAND.
Q2) I have edited the updater script in META-INF to reflect new radio and Android version ect. Do I need to update the MANIFEST. MF?
Hope that was clear enough to understand.
A big THANKS for your Help and time!
Long story short, had to send the phone in for repair, so I did the obligatory backups and unroot/reflash of factory images.
I don't have TWRP, too much hassle together with magisk for taking OTAs, so I took my backups (/data, /data/media) with tar/split/gzip.
Did my due dilligence to make sure the backup was good - resulting tar file extracts perfectly fine on my linux desktop.
Got my phone back, rerooted, ready to restore now. However, on the device, it stops extracting about 20 files in with 'invalid tar format'.
Tried again with busybox tar, and this time I get 'invalid tar magic'. Normally this suggests the tar is corrupted, but that doesn't explain why it's fine on my desktop. Note that the desktop archive I extracted is identical, e.g. it is the same one copied from the SD card I'm trying to restore now. What gives, since it's the same tar that created it in the first place... I've tried multiple versions/copies (this was a split archive since it was over 4GB in size - so I even recombined it on my host PC and pushed it to internal storage over ADB.) gzip has no issues with the outer compression (e.g I can gunzip the tar.gz fine) so the file itself doesn't seem corrupted.
Any suggestions on how I can get my /data back? Unfortunately I cannot just copy the files extracted on my desktop as this would mangle the permissions... and manually trying to fix them for the umpteen-hundred various folders is not practical...
I guess I'm hoping someone in the know might be able to point me to a different version of tar, or another tool (already tried cpio -H tar, not supported on android) that would extract things successfully.
I managed to get things to work by using a later version of tar from https://forum.xda-developers.com/android/software/utils-data-recovery-tools-testdisk-t3709380
However, I've now hit a new issue. After extracting to /data/data, or /data/app, the files are there, but vanish after a reboot, so the restore is incomplete.