Related
The attached ZIP includes scripts for Windows and Linux to backup your Galaxy Tab.
Linux users will need to install 7zip
Code:
sudo apt-get install p7zip
May also work on OSX but you're on your own with 7zip
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Windows
Code:
skitzbackup.cmd
Linux / OSX
Code:
chmod a+x <folder where you extracted it>/skitzbackup/skitzbackup.sh
cd <folder where you extracted it>/skitzbackup
./skitzbackup.sh
The script will pull the following partitions and pack them in a 7zip archive for safe keeping:
efs
recovery
boot
system
radio
cache
misc
Before you ask, I have no idea what the 'misc' partition is. Haven't had time to explore that yet
I have NOT tested flashing these back as yet, except for boot and recovery so you use this entirely at your own risk.
DOWNLOAD HERE
View attachment skitzbackup.zip
Enjoy!
Code:
alias del=rm
mkdir skitzbackup
cd skitzbackup
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/sdcard/cache.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/sdcard/misc.img bs=4096"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/radio.img bs=4096"
adb pull /sdcard/efs.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/cache.img
adb pull /sdcard/misc.img
adb pull /sdcard/radio.img
adb shell rm /sdcard/efs.img
adb shell rm /sdcard/recovery.img
adb shell rm /sdcard/boot.img
adb shell rm /sdcard/system.img
adb shell rm /sdcard/cache.img
adb shell rm /sdcard/misc.img
adb shell rm /sdcard/radio.img
7z a skitzbackup.7z *.img
del *.img
Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition
working perfectly!You're great
djmasque said:
Could this be used to backup apps and app data before unlocking bootloader? I can't see a /data partition
Click to expand...
Click to collapse
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.
bcmobile said:
No. Unfortunately, using this method to backup needs to write to the 'sdcard' which is what you want to back up.
Writing a script to back up data is a bit tricky since you can't reference it as a drive in windows and you can't know, for sure what the mount point will be in linux.
My main aim with the first version was to write a script which would work on either Windows or Linux, which it does. I might do seperate scripts to do a data backup.
Click to expand...
Click to collapse
Okay, good work nonetheless
Looks a lot like rotobackup, hehe.
Chainfire said:
Looks a lot like rotobackup, hehe.
Click to expand...
Click to collapse
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App
bcmobile said:
Yes, it is based on rotobackup method, but compresses and cleans up too
Sent from my GT-P7100 using XDA Premium App
Click to expand...
Click to collapse
Whats needed now is a kind of automated restore
bcmobile said:
You will need adb access to your tab whichever platform you use.
All you need to do to run it is extract the attached archive and run
Click to expand...
Click to collapse
Sorry for the noob question but how do i do this true windows?
Will this work for me?
Hi bcmobile,
This looks excellent.
I'm currently running a P7100 (10.1v) with ISI-Galaxy 1.2.5v (HC3.2) but my baseband/modem is still P7100BUKE2.
I would like to get the GSM working (for sending USSD commands) but I would need to flash my modem, and I would like to backup the modem before I flash it with the P7500 modem.bin, if something goes wrong, I can always go back to the old one.
In your script, is radio.img the modem.bin?
Also is the "/dev/block/" always the same on all the different versions of the tablet? (in other words if I have a 10.1v will this backup my modem).
Thanks so much. You help is much appreciated.
seraphimserapis said:
Whats needed now is a kind of automated restore
Click to expand...
Click to collapse
/!\ IN THEORY /!\ you'd just have to copy the .img files back to the tab and switch the command line arguments for dd. (e.g. dd if=/path/to/file.img of=/path/to/directory)
soo i know this is kind of old but does this work for any device? if so what am i doing wrong? its stuck on deamon started successfully...
------------------------------------SOLVED---------------------------------------------------------------------
JUST CARRIED OUT THE COMMANDS IN CWM RECOVERY ....THAT SOLVED ALL PROBLEMS
I have htc j one ...japanese htc one
Hboot is 1.52 and android 4.1.2
I have been able to s off, unlock bootloader using revone
I have flash cwm and rooted phone
Now I need to sim unlock the phone with some adb commands given in the below mentioned website :-
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
You can easily auto translate the above page if u open it in google chrome
Can anyone help me with that ?
Thanks in advance
Sent from my GT-N7000 using xda premium
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
criszz said:
download and unrar this in adb folder >>> http://www.androidfilehost.com/?fid=23159073880933098
they edited misc.img and say to do this :
adb push misc.img /
adb shell
# dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
hope it helps
Click to expand...
Click to collapse
Thanks for replying
I will download this file and put in adb folder
I shud do
adb push misc.img
( is this commabd correct or do I need to to put / ar back)
Then
Adb shell
It shows $ at the end
So it type
Su
Now it becomes #
Then I shud type
dd if=/misc.img of=/dev/block/mmcblk0p19
# reboot
Am I correct ?
Plz help as I am noob in this ...but am trying to learn
Sent from my GT-N7000 using xda premium
The auto-translated instructions are not good enough, and this is a very risky procedure. Fortunately, with code you usually don't need to read the words to understand it. Fortunately, with my Japanese-speaking colleague's help, I understand everything. Some things to know:
- Don't try this unless you are content to risk your phone, because I can tell he made mistakes in his instructions
- To reiterate, you either need to follow his incorrect instructions or you need to listen to me (why would you do that?)
- Look at the code blocks--all that code is meant to be run on your computer while the phone is connected to USB.
- There is only one complicated step, and this is the one with the incorrect instructions.
What he says:
Open misc.img in a hex editor, represent [00001023] as [11] and save. If you are lazy, use the file I modified already. <link>
There are two problems with this statement. First, "00001023" is not a reasonable position in the file. It means "line 10, column 3" (lines start with zero, columns start with zero). But there are 16 bytes per line, so what he really means is "byte 147". (Each pair of hex characters is a byte. The lowest value is 00, the highest value is ff.)
The second problem is that in his "already modified" file, that byte is "00", not "11". This is what I expected, because it's not reasonable for number="11" to mean "unlocked". More likely, "11" is his carrier and "00" is when the phone is unlocked.
What I advise is getting your carrier to unlock the phone, and if that's not possible, proceed only if you are willing to risk your phone. Follow his instructions, but when you get your misc.img file, download his modified version and compare them. If they differ in only one position, install his file to your phone (as per the instructions). If they are very different but the same size, you can try changing byte 147 to 00 (if the surrounding bytes are also all 00). Save the unmodified .img file, because you might be able to use it to rescue your phone if this fails.
Note: this is risky, with or without language barrier issues. At least 10% chance of bricking your phone.
Thanks a lot for your advice.
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Currently am stuck ...
Sent from my GT-N7000 using xda premium
sitanshu91 said:
But it is not possible to carrier unlock the phone
Is there any safe way to sim unlock the phone ?
Click to expand...
Click to collapse
I think it's probably safe to flash the misc.img file he uploaded and linked to, if (and only if) it is exactly the same as yours, except for that one byte. Low chance of bricking the phone.
But currently can you tell me to how to pull the image coz I havr followed his command ...
Adb shell
It strt with $
Su
Now # come
Then somd dd comand
Here it shows operation cannot complete(will update what is exactly error in few min)
Exit
Adb pull misc.img
Here it shows error device not detected
Can you help me to first pull file so I can compare
Sent from my GT-N7000 using xda premium
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
fenstre said:
Weird... you got a successful ADB shell, then it stopped detecting your device? I suppose you should just try again.
My phone is not the same as yours, so you shouldn't compare your partition19 to mine. You have a phone specific to Japan, right?
Click to expand...
Click to collapse
see this is what i get
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ #
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
requesting your help
thanks
sitanshu91 said:
can you tell me why it says " /misc.img: cannot open for write: Read-only file system "
Click to expand...
Click to collapse
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
fenstre said:
That's actually normal (because you're not supposed to write to the root of the phone's filesystem). Every time the instructions say "/", you can replace it with "/sdcard/", and every time they say "/misc.img", you can think "/sdcard/misc.img". (The instructions were carelessly written.)
Click to expand...
Click to collapse
so you say i should proceed
see again i did the same
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT35Z******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
/misc.img: cannot open for write: Read-only file system
1|[email protected]:/ # exit
exit
1|[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
now how should i proceed ....please help
Guys requesting help before the new year starts
So I can use my phone in new year
Sent from my GT-N7000 using xda premium
sitanshu91 said:
/misc.img: cannot open for write: Read-only file system
Click to expand...
Click to collapse
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Kasi!995 said:
are you doing this is fastboot? / recovery? is your device bootloader unlocked through htc dev?
Click to expand...
Click to collapse
yes this is unlocked bootloader ...i have done it thru revone
now i have installed busybox
and i can progress
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb devices
List of devices attached
HT3******* device
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
sitanshu91 said:
can you help me now
i want to do as written in this
http://htcsoku.info/htcsokudev-news/au-m7-device-sim-unlock/
thanks
Click to expand...
Click to collapse
what Recovery do you have flashed? TWRP?
Its cwm recovery
Sent from my GT-N7000 using xda premium
Run adb pull outside of adb shell.
1st problem :-
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p19 of=/misc.img
dd if=/dev/block/mmcblk0p19 of=/misc.img
2045+0 records in
2045+0 records out
1047040 bytes transferred in 0.106 secs (9877735 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ adb pull misc.img
adb pull misc.img
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $
can you tell me where is my mistake
What can I do can you type command
2nd problem
similiarly when i try
C:\adb\adt-bundle-windows-x86-20131030\sdk\platform-tools>adb push misc.img /
failed to copy 'misc.img' to '//misc.img': Permission denied
request you to please help me
thanks and regards
Sent from my GT-N7000 using xda premium
what is your status now?
criszz said:
what is your status now?
Click to expand...
Click to collapse
i am very glad that you asked .....happy new year
Now my status is sim unlocked ....but i can use only to make and receive phone calls and sms ...
now here is the problem
i cant use data (2g/3g) on my phone
do u know how to do that
thanks
sitanshu
Thanks to @evoname for showing me how to do this! [emoji4]
This is if you are interested in pulling the system images for whatever reason. I'm not responsible if you brick your device. Use at your own risk!
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/abootb.img
dd if=/dev/block/mmcblk0p16 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/laf.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/system.img
exit
exit
adb pull /sdcard/aboot.img
adb pull /sdcard/abootb.img
adb pull /sdcard/boot.img
adb pull /sdcard/laf.img
adb pull /sdcard/recovery.img
adb pull /sdcard/system.img
exit
Sent from my LG-D415 using Tapatalk
Welcome to Flashe!:victory:
Flashe is basically an all-in-one installer which only requires a few clicks and you are root,unlocked(bootloader), and you can choose a recovery to install in the process. This is much easier than using ADB commands or fastboot.:good:
The program does included a feature that allows you to use a custom boot image and get rid of the "unlocked bootloader" screen.
WARNING: USE AT YOUR OWN RISK
Requirements:
-Atrix HD,Razr HD,Razr MAXX
- .bin logo file(rename to logo when put in flashe folder)
- .iso for your recovery(CWM,TWRP, or Philz)
Future Update:
-Downloads the required files from a server
-Menu(choose to install other things
-GUI, instead of text there is a actual button interface.
Errors:
You MUST allow the program to boot you into recovery otherwise the custom recovery is lost due to the android os overwriting it. If you have any other errors pm
me!
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Enjoy!
Alienware258 said:
This uses djrbliss's exploit,special thanks to him for his exploit, but the rest is all coded in by me.
Click to expand...
Click to collapse
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I totally agree
quasihellfish said:
But how is this any different than MythTools? : http://forum.xda-developers.com/showthread.php?t=2262726
And if this is a Windows program, then we have no idea what commands you're sending to the phone. No Open Source? No thanks. I really suggest everybody use Myth instead...
Oh, and Trend Micro identified it as a virus and deleted it: http://about-threats.trendmicro.com/us/malware/ANDROIDOS_ROOTRAZR.A
Click to expand...
Click to collapse
I looked at the threat, and it calls it a threat because it is a rooting tool.
Also,When I first started rooting I did not get how to use it at all(Mythtools).Instead I used programs on my android.So I made this to help new users coming to the atrix community once I finished learning ADB commands and some fastboot commands.
Here is the source:
Code:
adb kill-server
adb wait-for-device
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb install Superuser.apk
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/busybox
adb reboot
adb wait-for-device
adb push unlock /data/local/tmp
adb shell chmod 755 /data/local/tmp/unlock
adb shell su -c /data/local/tmp/unlock
adb shell rm /data/local/tmp/unlock
adb reboot bootloader
fastboot getvar all
fastboot continue
adb wait-for-device
adb reboot bootloader
echo [-] To continue you will need a boot file which will
echo [-] replace the "Unlocked Bootloader" image. Name it:
echo [-] logo.bin
echo [-] Continue when you are in the bootloader and have the file.
pause
fastboot flash logo logo.bin
fastboot continue
echo [-] Processe complete!
echo [-] -Root installed
echo [-] -Bootloader unlocked
echo [-] ---------------------
echo [-] This next step will install a recovery.
echo [-] Recovery will allow you to install your own roms,etc(depending on the selected recovery)
echo [-] Rename your recovery image "rec" so it should be 'rec.img' then continue.
pause
adb reboot bootloader
echo [-] Continue once in bootloader
pause
fastboot devices
fastboot flash recovery rec.img
echo [-] Once finished flashing continue...
pause
adb reboot recovery
echo [-] Complete! You now should have recovery installed. Enjoy!
pause
I was trying imei repair. So i unlocked and rooted successfully. After that, i make backups with qpst without any problem. After all i wrote following codes like my guide saying and restarted
” ls -al /dev/block/platform/soc/624000.ufshc/by-name ”
dd if=/dev/zero of=/dev/block/sdf3
dd if=/dev/zero of=/dev/block/sdf5
dd if=/dev/zero of=/dev/block/sde28
dd if=/dev/zero of=/dev/block/mmcblk0p40
dd if=/dev/zero of=/dev/block/mmcblk0p41
dd if=/dev/zero of=/dev/block/mmcblk0p39
After screen never came it's only black and it's shown as Qualcomm hs-usb qdloader 9008 on device manager
I tried using adb but adb doesn't detected device
I tried using fastboot but it gets stuck on waiting for device
iscannn said:
I was trying imei repair. So i unlocked and rooted successfully. After that, i make backups with qpst without any problem. After all i wrote following codes like my guide saying and restarted
” ls -al /dev/block/platform/soc/624000.ufshc/by-name ”
dd if=/dev/zero of=/dev/block/sdf3
dd if=/dev/zero of=/dev/block/sdf5
dd if=/dev/zero of=/dev/block/sde28
dd if=/dev/zero of=/dev/block/mmcblk0p40
dd if=/dev/zero of=/dev/block/mmcblk0p41
dd if=/dev/zero of=/dev/block/mmcblk0p39
After screen never came it's only black and it's shown as Qualcomm hs-usb qdloader 9008 on device manager
I tried using adb but adb doesn't detected device
I tried using fastboot but it gets stuck on waiting for device
Click to expand...
Click to collapse
do you know what did you done ?
what are these partitions ?
iscannn said:
I was trying imei repair. So i unlocked and rooted successfully. After that, i make backups with qpst without any problem. After all i wrote following codes like my guide saying and restarted
” ls -al /dev/block/platform/soc/624000.ufshc/by-name ”
dd if=/dev/zero of=/dev/block/sdf3
dd if=/dev/zero of=/dev/block/sdf5
dd if=/dev/zero of=/dev/block/sde28
dd if=/dev/zero of=/dev/block/mmcblk0p40
dd if=/dev/zero of=/dev/block/mmcblk0p41
dd if=/dev/zero of=/dev/block/mmcblk0p39
After screen never came it's only black and it's shown as Qualcomm hs-usb qdloader 9008 on device manager
I tried using adb but adb doesn't detected device
I tried using fastboot but it gets stuck on waiting for device
Click to expand...
Click to collapse
I think the easiest way to restore imei is by flashing efs image. And you can get this image file from downloadable fastboot rom.. And what you've did to your phone is a mess... Correct me if I am wrong ?