Related
I flashed my phone to JF 1.5 and in the process some how managed to screw up my sd card and lost all my apps. i did do a nandroid backup of jf 1.41 so i ahve those img files. I tried to restore to that to recover everything but it wont boot past the g1 logo. I tried downgrading firmware to 1.43 (couldnt find 1.41) and using the same restore for nandroid and still wouldnt boot. I also tried jsut applying the user data img to see if i could jsut grab that and it fialed on both firmware revisions 1.5 , 1.43.
In the end im stuck with a backup i cant use, the only thing i need off of it is the apps. I read that you can use the emulator to mount it but i couldnt figure that out. I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Anyone have a simple solution or a complex one i can follow to getting my apps out?
did you follow this?
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
darkrangr said:
I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Click to expand...
Click to collapse
You go into the source directory, type "gcc -o unyaffs unyaffs.c", then you (create and) go to some directory where you want to extract the contents ("mkdir ~/extract") "cd ~/extract", and finally you extract the image "/path/to/unyaffs /path/to/data.img".
I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?
Unless your backup was corrupted, flashing the backup should have been fine.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
You said it failed - what error did it give? Did it say it couldn't find the command? Be sure you're running these commands on your PC with your G1 connected via USB, the correct drivers are loaded, and you have the fastboot program.
As for using unyaffs - I don't think you understand what you have to do to use it. You have to compile it on your PC...all you get is the source code. I haven't looked on the google code site, but I would imagine there isn't a version for windows.
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?
it didnt fail on the restore with fastboot, it loaded up everything fine and then when i rebooted it just sat on the boot screens forever and never loaded.
I am feeling nice so darkrangr if you want to PM your image files I will unyaffs it on my ubuntu box for you.
TemporalShadows said:
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?
Click to expand...
Click to collapse
no, my apps were installed normally. I am running curent jf firmwar enow while i try to get my stuff back, but some of the apps i had are no longer available or have converted to pay apps, plus i forgot a lot of apps i had.
http://forum.xda-developers.com/showthread.php?t=497034
In the other tools archive on this post you can find the unyaffs tool fully compiled. Just move your image to the same folder, drag and drop it on the unyaffs.exe and watch the files appear.
How about YOU DIDN'T INSTALL GCC!!!
darkrangr said:
I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?
Click to expand...
Click to collapse
There seem to be a lot of posts lately from people who have failed to make a proper backup prior to rooting their NST or NSTG. The first reaction to a failed root seems to be trying to restore the image, and of course, a bad image results in lots of heartbreak. I've read Renate's posts patiently talking people through the process of attempting to recover /rom.
I understand that it's the contents of /rom that are unique to each device. In addition to using a disk imager to make a copy of the device, might it also be a good idea to copy the files within /rom to a safe place prior to embarking on any rooting adventure? At least this way, they'd be able to *see* the files and hopefully increase the odds of a successful backup. Also, depending on what gets destroyed during the failed restore, are there other backups on the device?
1. While the new device is mounted using Noogie, is making and extra copy of the contents of /rom a good idea?
2. Are the contents of /boot/romrestore.zip (/system/rom) sufficient? (/rom/BCB has the same md5 checksum, but the only bootcount shows in devconf).
3. The contents of /factory/rombackup.zip appear at quick glance to provide the missing files from devconf). Do /boot/romrestore.zip + /factory/rombackup.zip provide a good backup of the device-unique files?
And finally, is making an image of the device the best way to backup if there's no way to verify it? Would copying the files and doing checksums against the pre-rooting originals be safer? Recreating partitions is not much fun, but could be done with a cut & paste script.
I like playing it safe.
I have full image backups and copies of /rom and rombackup.zip from /factory
/rom is owned by system so you can't read it from a regular app without superuser.
I've thought of making some easy way to back things up.
If you're rooted and have ADB, you just have to adb pull /rom
I've tried to use noogie and give the p2 (/rom) partition a drive letter in Windows Disk Management but it didn't seem to work.
Renate NST said:
I like playing it safe.
I have full image backups and copies of /rom and rombackup.zip from /factory
/rom is owned by system so you can't read it from a regular app without superuser.
I've thought of making some easy way to back things up.
If you're rooted and have ADB, you just have to adb pull /rom
I've tried to use noogie and give the p2 (/rom) partition a drive letter in Windows Disk Management but it didn't seem to work.
Click to expand...
Click to collapse
I'm thinking that it might be possible to pull backups during the rooting itself. I've looked at the scripts GabrialDestruir uses in TouchNooter 2.1.31 and I believe it could be done there. The current 2.1.31 nooter script looks like straightforward shell scripting, so I can hack something together there. I've already modified my TN card to add a few files during the boot process to suit my needs, so I'm comfortable with that process.
1. Would there be a major downside to writing the backup files to the TN uSD filesystem?
2. Are /rom and rombackup.zip sufficient? Is /factory/rombackup.zip needed as well, if /rom is bad for whatever reason?
I believe I read that GabrialDestruir wants to migrate TN to a CWM configuration, and I think that's been done for the NSTG already. I'm not sure about the CWM scripts, or even what they're called to search for syntax. Can anyone point me to info on the syntax for the scripts in /META-INF/com/google/android/updater-script as used by ClockWorkMod when installing .zip files? I don't want to try something that will be obsolescent in a few weeks!
I do wonder if a single bootable uSD image could be used to back up critical info from both the NST and the NSTG though. The same files and partitions apply to both, correct? A bootable image that writes copies of these critical files to a VFAT partition on the uSD card would allow newbies to boot, run and then easily copy these files somewhere safe on their PC.
bobstro said:
I'm not sure about the CWM scripts, or even what they're called to search for syntax.
Click to expand...
Click to collapse
See: Edify script language
Renate NST said:
See: Edify script language
Click to expand...
Click to collapse
Perfect! Thank you, Renate. Now that I know what to look for, I did find a tutorial thread that I'm reading through.
Looking at the Edify options, I don't see any way to copy files, nor to write to a .zip or tarball. It looks like I can use run_program(program, arg0, ...) to execute busybox commands, but I'd need to look into that to make sure everything needed is provided by busybox.
My initial impression is that doing this via a bootable image with a shell script like TouchNooter for NST uses today might be the best option, especially if I want to add options to recreate partitions. Using CWM .zip files allows different scripts to be run by selecting a different .zip (e.g. backuppartitions, restorepartitions).
I did compare the md5sums of the files from /rom and from both /boot/romrestore.zip (/system/rom) and /factory/rombackup.zip (/system/rom). They do match, so it looks like recovery of both /boot/romrestore.zip and /factory/rombackup.zip will allow restoration if /rom is not recoverable. Do we need both?
Hi All,
I wanted to update my ideos s7-104 (best buy US) to the Joenilan froyo fusion rom and made one mistake along the way. I copied the .zip file to the external sd card not the internal sd card. So zip file is not available to CWM (2.5.1.8). I tried manually pushing the file to the tablet with ADB (from computer) but the tablet is not visible to the system (windows 7 64bit with drivers installed, I could not get HiSuite to install with upgrade.cmd). This is strange becasue the Upgrade utility which uses adb flashes the rom just fine. Of course I wiped the system and reformatted the device per the instructions. Now when the unit boots it goes the fastboot and then stops with option to reboot with back/home which works. I don't think the unit is bricked just yet since I can still get into the CWM recovery.
Does anyone have any bright ideas to move the Ideos S7 Froyo v1.3-EXT4 Stable.zip to the internal sdcard?
Thanks for all the useful information previously posted!
Bruce
St. Louis MO
Hi, let see if i can help you, if you have a backup restore, if you dont that implies some work, i dont use windows i prefer linux, you can try to create a virtual machine, with windows xp or linux ubuntu and then with fastboot commands push the file to sd card.
Another way, get the oficial rom for your tablet copy the file to ext-sdcard and follow the install instrutions of the rom, you must create the dload directory in ext-sdcard.
it look like you lost the system files and the kernel of the device, so it boot in to fastboot, fastboot does not acept adb, but fastboot has some commands to copy kernel and system file to the device, it cant copy a zip file, must be a img file.
Version 6.0.1 of cwm reads update files from ext-sdcard so you can also try to install that recovery version with fastboot.
Remember: it always a good idea to have a backup before doing anything.
Hope that helps.
Fixed
hal_2000 said:
Hi, let see if i can help you, if you have a backup restore, if you dont that implies some work, i dont use windows i prefer linux, you can try to create a virtual machine, with windows xp or linux ubuntu and then with fastboot commands push the file to sd card.
Another way, get the oficial rom for your tablet copy the file to ext-sdcard and follow the install instrutions of the rom, you must create the dload directory in ext-sdcard.
it look like you lost the system files and the kernel of the device, so it boot in to fastboot, fastboot does not acept adb, but fastboot has some commands to copy kernel and system file to the device, it cant copy a zip file, must be a img file.
Version 6.0.1 of cwm reads update files from ext-sdcard so you can also try to install that recovery version with fastboot.
Remember: it always a good idea to have a backup before doing anything.
Hope that helps.
Click to expand...
Click to collapse
Thanks so much for the tips. I was able to flash the trzmod-v3 image and now I have a working tablet again. Pretty slick I must say.
Hi, well done, i'm working with cm9 for s7 maybe in some few days you can try cm9
hal_2000
does anyone know the combination to get into recovery and cwm.
thank's
sorry my bad english
BANOUNDROID said:
does anyone know the combination to get into recovery and cwm.
thank's
sorry my bad english
Click to expand...
Click to collapse
Hi, with s7 power off press, menu + call(green key) + power, wait a few seconds and you get cwm screen if it is install
Hal_2000
When I try to copy my TWRP backup file to PC only the two boot files will copy. Is there a way around this. How would I pull the files using ADB? I have 4.3 and TWRP 2.6.
gale2000 said:
When I try to copy my TWRP backup file to PC only the two boot files will copy. Is there a way around this. How would I pull the files using ADB? I have 4.3 and TWRP 2.6.
Click to expand...
Click to collapse
Same issue....only two files copy over. It has to do with permission changes of the backup files with TWRP version 2.6. I tried doing an ADB pull in Windows, but could not get it to work (Various errors). I would also like to know the proper method to do this.
EDIT: Finally got the adb pull to work and all the files were copied over.
HI,
I have looked at various tutorials and can't seem to find one specific to what i am looking for. Apologies if it's out there and i just haven't found it.
I have a bunch (like 250) of brand new Samsung Note 3's (Canadian N900W8 build) that have stock 4.4.2. I am required to get them all configured with a specific set of apps installed and various shortcuts on the home screen along with some custom settings (APN, data limits etc). so far i have been doing this manually and it is very time consuming and tedious. If there a way to take a phone i have already configured and make a file that i can flash in odin to each of the new phones that will mirror all of the changes i need to the new phones? Or some other tool to automate the process of deploying that many devices. If anyone can point me to a tool or tutorial i would be eternally grateful and may manage to retain my sanity.
I haven't seen anything like this yet in my browsing, most of the tutorials i have seen are for compiling/building a full rom.
Thanks
bugleboy said:
HI,
I have looked at various tutorials and can't seem to find one specific to what i am looking for. Apologies if it's out there and i just haven't found it.
I have a bunch (like 250) of brand new Samsung Note 3's (Canadian N900W8 build) that have stock 4.4.2. I am required to get them all configured with a specific set of apps installed and various shortcuts on the home screen along with some custom settings (APN, data limits etc). so far i have been doing this manually and it is very time consuming and tedious. If there a way to take a phone i have already configured and make a file that i can flash in odin to each of the new phones that will mirror all of the changes i need to the new phones? Or some other tool to automate the process of deploying that many devices. If anyone can point me to a tool or tutorial i would be eternally grateful and may manage to retain my sanity.
I haven't seen anything like this yet in my browsing, most of the tutorials i have seen are for compiling/building a full rom.
Thanks
Click to expand...
Click to collapse
This might not work for reasons I don't know about, but why not make a nandroid backup of the completed ROM and Apps etc, and copy it to multiple extSDCards then run a Restore on each phone? Although I guess you'd need to flash a custom recovery first... hm...
Maybe someone who knows ADB ins and outs could suggest something - connect phone, push SW out etc.
So i found a tutorial that described how to dump an img file for various partitions using ADB commands. I used the following to dump the system partition
Code:
dd if=/dev/block/mmcblk0p23 of=/mnt/extSdCard/backup/system.img bs=4096
I then coppied the system.img to computer and used a tool i found on here to convert it to system.tar.md5. I put a new phone into download mode and open odin load the system.tar.md5 into the PDA section it verifies the file ok, but when i try to flash it it fails instantly and a message appears on the phone saying "Unsupport dev_type"
I have seen a couple different versions of this tutorial out there, and i even tried booting to a ubuntu live CD to try to use the linux commands i saw on a different tutorial to convert the .img to a .tar.md5 but the result is the same.
Does anyone have any experience getting this method to work? any suggestions?
Thanks
bugleboy said:
So i found a tutorial that described how to dump an img file for various partitions using ADB commands. I used the following to dump the system partition
Code:
dd if=/dev/block/mmcblk0p23 of=/mnt/extSdCard/backup/system.img bs=4096
I then coppied the system.img to computer and used a tool i found on here to convert it to system.tar.md5. I put a new phone into download mode and open odin load the system.tar.md5 into the PDA section it verifies the file ok, but when i try to flash it it fails instantly and a message appears on the phone saying "Unsupport dev_type"
I have seen a couple different versions of this tutorial out there, and i even tried booting to a ubuntu live CD to try to use the linux commands i saw on a different tutorial to convert the .img to a .tar.md5 but the result is the same.
Does anyone have any experience getting this method to work? any suggestions?
Thanks
Click to expand...
Click to collapse
Maybe check adb setting in Developer menu? There's an ADB over network setting in there. Not sure if it will help, after looking at it it says it is reset on boot...
I ended up using a nandroid backup as suggested earlier. However i initially had issues doing that i think because i was using TWRP recovery and it requires the backups to be in a folder named uniquely per device id or something which requires you to make a backup on that device before you can copy the backup files . TWRP also write protected the backup folders requiring root to be able to copy a backup onto it.
I changed to CWM and it works much better, all i have to do is flash CWM recovery to a new device and then boot it to copy the backup files and then reboot to recovery and restore the backup.
bugleboy said:
I ended up using a nandroid backup as suggested earlier. However i initially had issues doing that i think because i was using TWRP recovery and it requires the backups to be in a folder named uniquely per device id or something which requires you to make a backup on that device before you can copy the backup files . TWRP also write protected the backup folders requiring root to be able to copy a backup onto it.
I changed to CWM and it works much better, all i have to do is flash CWM recovery to a new device and then boot it to copy the backup files and then reboot to recovery and restore the backup.
Click to expand...
Click to collapse
Make sure all the devices have the same bootloader and modem. What Firmware version are you using as a base?
Sent from my SM-N9005 using Tapatalk
celderic said:
Make sure all the devices have the same bootloader and modem. What Firmware version are you using as a base?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
They're all using the same 4.4.2 base image, the only change i made was flashing a custom recovery to be able to create the initial backup of the configured phone and to restore the backup to the stock phones saving me having to maunally configure each device.