Database Develop

KindleFire2 Backup Help

I need some help. The Standard Backup/Restore process seems to not work well on the Kindle Fire 2nd Generation.
I am asking if someone can try something new for me, (I have a bricked device)
Back up raw partitions from kindle responsible for recovery, boot and system and upload them.
**this requires root**
adb shell su -c "chmod 777 /dev/block/*"
adb pull /dev/block/mmcblk0p9
adb pull /dev/block/mmcblk0p10
adb pull /dev/block/mmcblk0p11
I am hoping this process of backing up the raw partitions will allow them to be flashed again in fastboot.
If I can prove this is a viable backup and get my device going again I am going to work on the applying the bootloader crack to the KF2.
Once we have the bootloader crack applied CM10 roms should be cominmg,
Thanks.

[Q] HELP rom problems.

ALL IS FIXED THROUGH RUU!!! OMJ'S RUU POST SAVES LIVES. +1 TO THAT MAN.
Hi, I've recently installed clockwork mod and just wanted to try out the HD revolution roms and missed having battery percentage. I used the all-in-one toolkit. After installing the ROM through ADB sideload i rebooted my phone to having it go right back to the bootloader screen. I tried to restore my backup and it says it has a md5 mismatch. If anyone has any guidance please help!!!
Sincerely,
A lost noob

download a new rom, sideload via adb, try flashing with that.
after downloading the new rom, boot into recovery, plug device into computer, open up terminal window and type:
for linux/osx:
Code:
adb push /path/to/new/ROM /sdcard/Download/
for windows:
Code:
adb push C:\path\to\new\ROM /sdcard/Download/
You can also delete the old rom (quotes are required):
Code:
adb shell "rm -f /path/to/ROM/on/device"

treyswell said:
Hi, I've recently installed clockwork mod and just wanted to try out the HD revolution roms and missed having battery percentage. I used the all-in-one toolkit. After installing the ROM through ADB sideload i rebooted my phone to having it go right back to the bootloader screen. I tried to restore my backup and it says it has a md5 mismatch. If anyone has any guidance please help!!!
Sincerely,
A lost noob
Click to expand...
Click to collapse
Did you rename your backup to something other than the date and time? This caused me to have a md5 mismatch.
Sent from my HTC One using xda premium

If you're absolutely sure your backup is complete then type this in cmd:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2013-05-01.20.22.53 (name of your backup stored in /clockworkmod/backup )
# rm nandroid.md5
# md5sum *img > nandroid.md5
This will allow your backup to restore

Redbull I wish that was my problem.! lol. So update : I tried switching recoveries to TWRP since there was a cache recovery erroor in my CM. BUT after that I lost my nandroid. :C So I either install with CM where my phone is recognized but my cache will fail the install or TWRP where my phone isn't recognized. I also flashboot the boot.img from the rom after downloading. My also has shut off in random times.FML
2nd UPDATE: I now have TWRP working. I've been trying to use O.M.J's deoxed rom. My phone makes it to the main menu with no service and then after a minute it will say process system not responding and shut itself off and reboot. If its any constellation my twrp time is only an hour off.

[Q] network problem g800f

i install an official rom 4.4.2 but after that i can't make calls then i install the "CyanogenMod 12.1 for G800F" but without result (when i shearch manually for network i found many in my country but i can't choose any one)
imei is changed (in phone): 350695200123951
in the package imei is: 352960063276330
im tired for search in internet for fixing this problem but without result. Help me please

First, I'd strongly advise against posting your IMEI publicly.
Your problem is most likely due to a corrupted EFS partition which can occur during botched firmware upgrades. If you'd like a guide to fixing it you can search again for "Samsung EFS repair", but to summarize:
- Make a backup of the current EFS partition, from ADB you can run : "adb shell su -t dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img"
- Obtain a "mkfs.ext4" ARM binary and use it to format the EFS partition: "adb shell su -t mkfs.ext4 /dev/block/mmcblk0p3"
- Re-flash the stock firmware in odin, boot up and all should be fine.
Otherwise a repair center will probably fix it for you.
NOTE: You may want to copy the EFS backup off of your device before flashing

full-backup partition tool - script for terminal

I made a script to backup any partition in our A7:
YOU HAVE TO BE ROOT, TO USE IT.
To run it simply push to the sdcard fire up adb shell to launch the script.
from the computer while connected to the A7 with usb debugging turned on
Code:
adb push PATH_to_the_script/full-backup.sh /sdcard
and
Code:
adb shell
su
cd /sdcard/
sh full-backup.sh
you will see a menu to choose which partition to backup.
As in the attachment.
enjoy, and please hit the thanks button.

the script v1.00
and a terminal screenshot.

Could you use terminal emulator to run this from on the phone thus cutting out the need for a pc?

ultramag69 said:
Could you use terminal emulator to run this from on the phone thus cutting out the need for a pc?
Click to expand...
Click to collapse
yes you could run it directly form the device:
fire up a terminal emulator app:
RUN IT AS ROOT
Code:
su
sh /sdcard/full-backup.sh

thank you. we can backup unmodified firmware via this tool right?

RealSchule said:
thank you. we can backup unmodified firmware via this tool right?
Click to expand...
Click to collapse
So you need to be root to use this script, so not really..

RealSchule said:
thank you. we can backup unmodified firmware via this tool right?
Click to expand...
Click to collapse
The root modifed just the boot partition so you could backup every stock partition but the stock boot... but you could get the stock boot from other places...

manu7irl said:
The root modifed just the boot partition so you could backup every stock partition but the stock boot... but you could get the stock boot from other places...
Click to expand...
Click to collapse
we can backup all images except boot.img with this tool but we can find boot.img from other topic. so we have full stock images right?

If you have root you can backup every single partition. This is not full stock rom! This is for backup and restore easily.

manu7irl said:
If you have root you can backup every single partition. This is not full stock rom! This is for backup and restore easily.
Click to expand...
Click to collapse
So what is the process to restore these images? Is it as simple as flashing in twrp?

Go in TWRP, fire up adb shell on your PC, then do:
Code:
dd if=/sdcard/[backup_folder]/[partition].img of=/dev/block/bootdevice/by-name/[partition_name]
example:
Code:
dd if=/sdcard/backup-part/[date-folder]/system.img of=/dev/block/bootdevice/by-name/system
I will also make a restore part in this little script. If you are intersting in one to do so.

Sure that would be great. Thanks.
manu7irl said:
Go in TWRP, fire up adb shell on your PC, then do:
Code:
dd if=/sdcard/[backup_folder]/[partition].img of=/dev/block/bootdevice/by-name/[partition_name]
example:
Code:
dd if=/sdcard/backup-part/[date-folder]/system.img of=/dev/block/bootdevice/by-name/system
I will also make a restore part in this little script. If you are intersting in one to do so.
Click to expand...
Click to collapse

Been waiting for just that.

[Q] Backing up and restoring with ADB

Hi everyone,
I wanted to unlock the bootloader on my OP3T but I don't want to lose all the data. So I wondering if I could back my phone with the command,
adb backup -all -apk
and then unlock the bootloader and then restore the backup that I made. Are there any disadvantages to this? Will I lose out on updates? Will I lose any data? Anything else I should know?

I think you will in the end need root via adb to accomplish this. Imagine this, if without unlocking phone you can use adb to make a backup then anyone can do that(who have enough knowledge) and this can be a major security concern.
Soo I think it is not possible.

It is possible. As stated on Titanium Backup's webpage:
1. How to make your first backup WITHOUT root:
Before beginning, you need to setup your ADB and have your device detected. You must also running Android version 4.0 and above. Also, make sure you have a file manager installed. Our favorite is the ES File Explorer.
Connect your device and make sure its listed with the following command:
Code:
adb devices
Run a FULL backup with the following command:
Code:
adb backup -f FullBackup.ab -apk -all
This will create a “package” called “FullBackup.ab” on the current location in your command prompt. This is your backup package.
Now you can root your phone.
Once finished rooting, insert the “FullBackup.ab” package on your sdcard
Hit the menu button and look for “Extract from ADB backup” option. This will prompt you to search for the file. Use the file manager that you installed earlier and navigate to the directory and select the FullBackup.ab file.
Now restore like as if the backup was made with Titanium Backup. Don’t forget to make a fresh copy of the backup using Titanium Backup. You’re Done!
Click to expand...
Click to collapse