Database Info

Sideloading Samsung Captivate

How to sideload for samsung captivate?
1. Download Terminal Emulator from android market (or any terminal).
2. Go to this post on your samsung captivate.
3. Copy this Below
su cd /dbdata/databases/com.android.providers.settings
sqlite3 settings.db
update secure set value = "1" where name = "install_non_market_apps";
.quit
reboot
4. Your phone will reboot and you can sideload. try to download an app from pandaapp.com.
5. Success!!!!!!!!!! Made very easy compared to using Android SDK.
-I dont claim to find this. But i havent seen this on youtube or any where else-
Hope You Luck!
-Jordan5555

Thanks for the info!
Sent from my GT-I9000 using XDA App

It's explained Tip: Enable Non Market App Installs on the Samsung Captivate]here[/url, I used a little variation on that method:
Can I suggest an even easier way of editing and manipulating the settings.db file? I used a combination of Root Explorer, SQLite Editor and Dropbox, modified from this link. You zip and copy settings.db from your Captivate to Dropbox, then you can edit it in Firefox, zip it, copy it back, and manipulate it from there - or I found I could copy the file to another folder I created (modified market), edit the file in there with SQLite, save the file and then copy it back to the original folder following their directions. The one thing you have to be careful of is making sure you're mounted R/W instead of R/O in Root Explorer or you'll get errors, something like 'permission denied'.
The Sideload Wonder Machine is nice, but I'm not always at my computer when I find something I want to try, this method made sideloading totally contained on the Captivate. Works a charm
{
"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"
}

i tried the first method by copying the code and i got "Permission Denied" so then i just typed in the first line. got the same "Permission Denied"
is there a step i need to do first?
sorry if there is something obvious i should do first, i'm a bit of a noob

gisxer said:
i tried the first method by copying the code and i got "Permission Denied" so then i just typed in the first line. got the same "Permission Denied"
is there a step i need to do first?
sorry if there is something obvious i should do first, i'm a bit of a noob
Click to expand...
Click to collapse
What are you using, Root Explorer? You have to click the r/w at the top of the screen to enable writing. If it's r/o, that means read only.

Root Explorer? no, just Terminal Emulator and pasted the code into the Terminal window. i take it that's not what it meant

gisxer said:
Root Explorer? no, just Terminal Emulator and pasted the code into the Terminal window. i take it that's not what it meant
Click to expand...
Click to collapse
Ah, no, I see, you're referring to the first method. I dunno, I used what I posted, and it worked well.

nevermind lol

sorry should have mentioned that. the method posted by jordan5555 got the error

Permission denied (Jordans mthd)
Sent from my SAMSUNG-SGH-I897 using Tapatalk

While the process described here isn't technically sideloading, it is enabling installation of non-market applications without being attached to a computer, a.k.a. De-crippling . I have already simplified this process into one click, with no need for running any console commands or downloading the android SDK. Check out One Click De-Cripple for Captivate here.
BTW, your phone will need to be rooted before this process will be successful.

rafter109 said:
While the process described here isn't technically sideloading, it is enabling installation of non-market applications without being attached to a computer, a.k.a. De-crippling . I have already simplified this process into one click, with no need for running any console commands or downloading the android SDK. Check out One Click De-Cripple for Captivate here.
BTW, your phone will need to be rooted before this process will be successful.
Click to expand...
Click to collapse
Having to be rooted is why I went wit the method I posted above - because at the time I wasn't ready to root. What that method did do is force me to learn a bit about Android file structure and how to 'fiddle around' with the innards of the system. Eventually, of course, I got brave, rooted, and it's been all customizing from then on.
Of course, once you've rooted and gone to a custom ROM you never have to worry about all this again

Cant you just use the sideload wonder machine? Worked for me when I didn't have the "install_non_market_apps" file changed.

yentlequible said:
Cant you just use the sideload wonder machine? Worked for me when I didn't have the "install_non_market_apps" file changed.
Click to expand...
Click to collapse
Sure, but then I have to be at my computer to load anything. I far prefer what I did, so it's just plain done. Plus I don't want the constant reminder that AT&T has crippled my phone - a phone I'm paying way too much for monthly.

reinbeau said:
Sure, but then I have to be at my computer to load anything. I far prefer what I did, so it's just plain done. Plus I don't want the constant reminder that AT&T has crippled my phone - a phone I'm paying way too much for monthly.
Click to expand...
Click to collapse
Good point... The only reason I used the sideload wonder machine in the first place was to get root explorer on my phone since the market was not working. After that I just modified the database file.

[Win32 Tool]GUI Root with Check and Recovery!

{
"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"
}
ShiftRRv1.0
Shift Root and Recovery will be able to root you're phone in a pretty safe manner. The program is designed to only flash the eng boot if the MD5 checksums are correct.
This does it by simply pushing / pulling the hboot from the phone and checking the MD5 as if you were to manually do it. Only this just does it automatically.
Check Root:
This will just run a quick and simple SU test to make sure you are or are not rooted.
Root:
You will click on this to install the ENG Hboot and load the correct files after the Hboot has been flashed.
Install Recovery:
You simply select the recovery image you want to use with your HTC Evo Shift. Leave the phone at the home screen and click install. It will auto reboot you to bootloader, flash the zip then auto reboot you to recovery to make sure it flashed successfully.
Backup / Restore WIMAX:
This option lets you quickly and easily backup your wimax keys to your home pc. It will also let you restore your wimax keys to your phones partitions.
[WHAT THIS PROGRAM DOES]
When you click on root, and click "NO" for this phone does not have a ENG Hboot. The program push's the ENGHboot from the Hboot folder to the phone and push's busybox. From there it gets a temp root shell. It then cross checks the MD5sum on the phone itself using busybox md5sum /data/local/eng_hboot if the MD5Sum math's it then proceed's with the dd if cmd. Once the dd if cmd is done. The program then sends the dd if cmd to /data/local/eng_hboot_check, it runs the cmd busybox md5sum again and verifies that the MD5Sum matches if so everything went well, the program cleans up its mess off the phone and alerts you its safe to reboot. IF IT FAIILS it will try 1 more time. The program is designed to check the HBOOT md5sum and verify if its the ORIG hboot if it is not and the MD5Sum doesn't check between the ENG and ORIGINAl it will attempt to flash the original and notify you if it succeeds. IF IT FAILS AGAIN. IT WILL NOTIFY YOU NOT TO TURN OFF YOUR PHONE AND COME HERE FOR FURTHER INSTRUCTIONS. I ADVISE YOU TO LISTEN.
After this YOU MUST REBOOT THE PHONE.
When phone is powered up again Click Root again this time select "YES" that the phone has a ENGHboot, this will get temp root again and push all the needed files, "SQLITE3", "BusyBOX", "SU", "Superuser.apk" to there proper location.
If YOU CLICK "YES" and didnt have the ENG Hboot thats fine it simply will temp root you and push files to your phone, but when you reboot they will be gone. Just start from the begining again and do it again.
Download V1 Here
DOWNLOAD NOW HERE
User's having trouble opening the application please download the latest dotNET framework from:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=0a391abd-25c1-4fc0-919f-b21f31ab88b7
THIS IS FOR XDA MEMBERS ONLY. PLEASE DO NOT POST IN OTHER FORUMS AND PLEASE DO NOT MIRROR THE PROGRAM.

download link added
Image of program added.
Reserved...

Thanks for sharing. No need for me to try it now but if I ever replace or need to re-root. Really like the option to backup wimax keys too.

Looks great but too bad I don't need it! Like the option to back up wimax, but what about restoring them!?

Im giving this a try now

It "did its thing" after rebooting the program is still "waiting" and the phone is booted. Hmmm help?

xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?

ahhhh!! I'm back 2 download it and.. well I'll wait again lol Thanks a lot for this..
I RUUed my phone and Wanted an easy way to re-root..

working?
other than the OP has anybody got this to work properly?

amoamare said:
xstingstreetx,
Can you give me more information?
Were you trying to root, or where you trying to do recovery?
Version of windows as well?
Click to expand...
Click to collapse
I was trying to root, and I have windows 7 64 bit

Where is the link ! someone please give me the file , pretty please please please been waiting for this !!!

I don't know if this is what it's trying to achieve or not. I don't know how to do it either. Judging by all my previous phones, an all in one script could be written to do everything the s-off, root, and recovery post is telling how to do. Just a "simple" batch file and some support files and presto, it's all done!
Zip everything needed together and just unzip and run. I could probably teach myself by ripping apart other all in one packages and adjusting my port to follow loosely what they are doing but I just don't have the free time to spend on that project. By the time I would get around to doing it, someone else would have finished it. I just don't know things like telling the phone to reboot into different modes so it could continue it's job. I can visualize it in my head but making it a reality is completely different. Doh!

Anyone know where the download link went? I've been having trouble with rooting my phone and wanted to try this, but theres no download link in the first post (unless my computer decided to stop showing links).

Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?

Oops, saw everything except "removed temp..." in the first post.
It looks like there isn't anything extra that needs to be downloaded. Looks like the OP figured out a way around it.

SirRipo said:
Link was removed temporarily. Learn to read guys, sheesh
On a side note, I'm pretty psyched about this OP, since I haven't had the ambition to sit down and root my phone yet. Just curious, are there any files that would need to be downloaded prior to using this (such as the ****-root.zip used in the other root method)?
Click to expand...
Click to collapse
Possibly the recovery files ( clockworkmod 2.x or 3.x ) and have HTC sync set up to even connect the phone I would guess.
Sent from my PG06100 using XDA App

Sorry guys will work on this again in a few days girl is supposed to be going in to labor today...
On the side note the issue that I ran into is that running rageagainstthecage from the windows side does not give you root. It actually disables usb connection between the phone and the computer. I was trying to make this so you didnt need anything other then the program. But now with that being a problem z4root would be needed to obtain at least temp root but if i doesnt drop you to # then it still will not work from doing it automatically using arguments. That is what i'm trying to resolve first..
Ill get back to you guys on it, and ill even add the option to restore wimax keys.

That's what I was thinking You have to Temp root with Z4root first.
Since The manual root requires super user to work.

Dude!!!! thank you so much for this. Been wanting t root badly but was afraid to try the other method. Good luck with baby!!

Perhaps someone brave could test it out by temp rooting with visionary/z4root and then running the program? If you posted the download link back up.

Do I have the "correct" nvflash blob files?

I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
{
"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"
}
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, it doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and if I find I have a bad nvflash blob file).
For other's info, I'd originally asked about re-running the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set. In preparation for recreating one, I moved the /sdcard/AndroidRoot folder to another location. I happened to reboot and noticed the AndroidRoot folder and its contents are automatically recreated upon rebooting. So for these files, there's no need to re-run the fastboot command for another set.
I did notice one "issue" viewing the /sdcard/AndroidRoot folder in Windows 7 after the initial reboot. While they display fine via my TF300T's File Manager, it took either disconnecting/reconnecting my usb cable or rebooting one more time for them to display correctly in Windows 7.
I still plan on re-running nvflash to create a new bricksafe.img, factory-config.img, and unlock-token.img set just to be extra safe.

wha2do said:
I'm running ICS v9.3.4.17 on my unlocked (but not yet rooted) TF300T. It's essentially in the same state as coming out of the box (no apps, using a temp gmail account to initially keep it "clean" while unlocking, installing nvflash, etc). I followed AndroidRoot.mobi's nvflash install instructions and everything appeared to go correctly. Is there any way to know my files were generated correctly? Below is a screen print of all my backup files:
I'm not sure if the file sizes are version or device specific, but are they all there and approximately the expected size?
I've copied them to 3 locations, but got thinking about it. Call me overly backup conscious, but I'd be better covered with two separately generated sets. If one is bad, doesn't matter how many copies I have. But having another set will give me a better chance to recover if the need arises (and I find I have a bad nvflash blob file).
Can I rerun the "fastboot -i 0x0b05 boot nvfblobgen.img" command to generate a new set? While I'm at it, I figure I should be able to rerun nvflash and create a new bricksafe.img, factory-config.img, and unlock-token.img... Is that possible and does it make sense?
Thanks!
Click to expand...
Click to collapse
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.

totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
Thanks for the confirmation. I dislike relying on an unverified backup only to find out too late that it's not valid or usable! And out of curiosity, you went through a recovery successfully? It'd be great if you had a link to the thread/post you followed.

I had missed one step after upgrading the jb bootloader (didnt force shutdown after upgrade, just let it load) and were stuck with official jb with no root or recovery, so i tried to use nv flash and messed up even more , post 3 in this thread helped me get the bootloader to work so I cound install TWRP again using fastboot.
I do not recommend testing it "just for fun" but it worked for me. Search for "nvflash restore" if you have any problems.

totaltmega said:
I have the same files and even tried recovering with the bricksafe.img, same sizes aswell.
Click to expand...
Click to collapse
I'm curious about your sizes matching mine; more specifically my unlock-token.img file size matching yours. Maybe fine if you used your unlock-token.img file when you did your recovery. If didn't use, might want to (if you still can) go back and recreate it and compare with your original...see below why.
Being OCD on backups, I created a new bricksafe.img, factory-config.img, and unlock-token.img and compared the files. I was a bit surprised to see factory-config.img and unlock-token.img were not exact copies of the original set created. Factory-config.img had some bits that varied, but was mostly the same. I'm figuring it's something "internal" as I haven't changed anything on my table between runs and is fine...
But seeing a large size change between the two unlock-token.img files, I went back through my logs, etc. Lo and behold, I had a typo and hadn't changed the partition from 14 to 7! So I had made duplicate backups of the factory-config partition by accident. The actual file size is 8,192 KB and not 5,120 KB.
That could have been a real problem down the road if ever I need to recover (assuming this file is vital to the particular recovery procedure). So if nothing else...the lesson to learn is always double check what you've done to make sure!

Plzzz help (recovery)

hi
by mistake i forgot to backup my personal files before rooting via cf-auto root.
now im trying to recover any files via wondershare android recovery and similar software. but the problem is no software is detecting my phone! what can i do? i had some really important files. plz help!!!

There's really not a lot you can do.
Some people have reported luck with "disk digger" from play but I remain sceptical.
Otherwise, read this:
http://forum.xda-developers.com/showthread.php?t=2534010
[ info] Storage: Nexus 5 Data (info / loss / recovery / prevention)
Sent from my Nexus 5 using Tapatalk

rootSU said:
There's really not a lot you can do.
Some people have reported luck with "disk digger" from play but I remain sceptical.
Otherwise, read this:
http://forum.xda-developers.com/showthread.php?t=2534010
[ info] Storage: Nexus 5 Data (info / loss / recovery / prevention)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
DINT HELP
anyone else has any idea?

kashsih93 said:
DINT HELP
anyone else has any idea?
Click to expand...
Click to collapse
Read the link

rootSU said:
Read the link
Click to expand...
Click to collapse
tried but stuck at http://forum.xda-developers.com/showthread.php?p=50441895
Im trying to follow OPs tutorial but am stuck on step 5
"Open a Cygwin terminal and enter (This assumes your BusyBox installation is at [/system/bin/busybox]. It may be at [/system/xbin/busybox]):"
My Nexus 5 is connected as adb as seen below
{
"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"
}
But when i open a Cygwin terminal, it says command not found.
Also, i dont know for sure if i did the requirement "ADB (make sure adb.exe is in your path)," correctly. I have just pasted everything in the sdk>platform tools directory into the C:\cygwin64

kashsih93 said:
hi
by mistake i forgot to backup my personal files before rooting via cf-auto root.
now im trying to recover any files via wondershare android recovery and similar software. but the problem is no software is detecting my phone! what can i do? i had some really important files. plz help!!!
Click to expand...
Click to collapse
recovery software wont work because of MTP. in order for that kind of software to work you need to be in USB mass storage mode, which is impossible on the N5. if you dont have any luck with disk digger, then theres pretty much nothing else you can do

TheAtheistOtaku said:
recovery software wont work because of MTP. in order for that kind of software to work you need to be in USB mass storage mode, which is impossible on the N5. if you dont have any luck with disk digger, then theres pretty much nothing else you can do
Click to expand...
Click to collapse
im trying to follow the guide here http://forum.xda-developers.com/showthread.php?t=1994705
but am stuck on step 5 as described above. anyone can help?

kashsih93 said:
im trying to follow the guide here http://forum.xda-developers.com/showthread.php?t=1994705
but am stuck on step 5 as described above. anyone can help?
Click to expand...
Click to collapse
well do you have busy box installed in one of the two locations? its saying command not found which probably means you havent installed it or you have it in a differ location

TheAtheistOtaku said:
well do you have busy box installed in one of the two locations? its saying command not found which probably means you havent installed it or you have it in a differ location
Click to expand...
Click to collapse
i have it installed on my nexus 5. at /system/xbin/busybox

Is cygwin in the exact same folder as adb? If so and adb still not found, try dropping adb into c:\windows\system32 folder and reboot
Sent from my Nexus 5 using Tapatalk

rootSU said:
Is cygwin in the exact same folder as adb? If so and adb still not found, try dropping adb into c:\windows\system32 folder and reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
tried but no use. get another error now
had some really really imp files i need to recover.

I cannot read the error. Can you crop it please?
Sent from my Nexus 5 using Tapatalk

kashsih93 said:
tried but no use. get another error now
had some really really imp files i need to recover.
Click to expand...
Click to collapse
Caveats: I have never done this; I don't have the tools in front of me to even try it myself.
That said it looks like you're having path issues -- you should *not* copy adb.exe and the other platform-tools into your cygwin directory. When the referenced HOWTO says to make sure adb.exe is in your path, they mean that your PATH environment variable should include its directory. The simplest way to do that is to edit your user PATH variable and tack ";c:\users\.......\sdk\platform-tools" on the end -- get the full path that you used in your very first screenshot, where "adb devices" worked for you.
Then, log out and back in to make sure the new variable takes effect. You should be able to start a cygwin terminal and run "adb devices" just the same as from your Windows command prompt.

rootSU said:
I cannot read the error. Can you crop it please?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse

Ghengis042 said:
Caveats: I have never done this; I don't have the tools in front of me to even try it myself.
That said it looks like you're having path issues -- you should *not* copy adb.exe and the other platform-tools into your cygwin directory. When the referenced HOWTO says to make sure adb.exe is in your path, they mean that your PATH environment variable should include its directory. The simplest way to do that is to edit your user PATH variable and tack ";c:\users\.......\sdk\platform-tools" on the end -- get the full path that you used in your very first screenshot, where "adb devices" worked for you.
Then, log out and back in to make sure the new variable takes effect. You should be able to start a cygwin terminal and run "adb devices" just the same as from your Windows command prompt.
Click to expand...
Click to collapse
Ok so your advise worked! (atleast partial)
now my issue is im getting a 0 byte file!
I am having a nexus 5 16 GB, so i should type in "mmcblk0p28.raw" according the post here http://forum.xda-developers.com/showthread.php?t=2517503, right? or will it be different for nexus 5 16 gb?
please check the screenshots below and advice:
thanks a lot for helping!

28 is userdata so yes
Sent from my Nexus 5 using Tapatalk

rootSU said:
28 is userdata so yes
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So what can I do about the 0 byte problem?

I don't know. Probably nothing. I wouldn't expect you to be getting your data back. Sorry
Sent from my Nexus 5 using Tapatalk

ok....so even if i use ncat in the 2nd window, still no luck.
Also, please see that in the first window it says "nc: invalid option -- 1". is this normal?

kashsih93 said:
ok....so even if i use ncat in the 2nd window, still no luck.
Also, please see that in the first window it says "nc: invalid option -- 1". is this normal?
Click to expand...
Click to collapse
No. I don't think you want the flag to be a digit *one*, you want a lower-case L. It means "listen" -- you're running a "server" on your phone that will execute the dd (disk-dump or data-dump) command and output its results to whoever connects to the open socket. You're getting a 0-byte file because the command on your client side (i.e. the computer) doesn't actually connect to anything.

Question How to make full pixel 7 backup to image ?

I would like to make a full backup of the system before I update so that I can restore the full system with all applications and their settings in case the update fails.

You'll need TWRP afaik for a full nandroid backup. Which doesn't exist for the P7P I guess.
But Google backup does a pretty good job, excluding the settings. You could also try Migrate or Swift backup, but I don't think full images are possible like in the older days.

{
"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"
}

m3ath said:
View attachment 5811723
Click to expand...
Click to collapse
Does this take a full image backup?

krakout said:
Does this take a full image backup?
Click to expand...
Click to collapse
I didn't try it

m3ath said:
I didn't try it
Click to expand...
Click to collapse
As far as I know this just applies to regular file transfer to a PC via USB, it does nothing special and nothing of the sort that OP asked...

I would like to use TWRP but it doesn't seem to work on Pixel 7 yet, I'm looking for something that does just that.

daveyyy said:
I would like to use TWRP but it doesn't seem to work on Pixel 7 yet, I'm looking for something that does just that.
Click to expand...
Click to collapse
Your best bet is to use Swift Backup for your apps/data, backed up to Drive or some other cloud Storage and then after the reset, let Google restore your G-Apps and Phone/Messages/WiFi points, etc while you restore your apps from Swift

krakout said:
Does this take a full image backup?
Click to expand...
Click to collapse
Its for an adb backup, which is pretty similar to what gooble backs up, and respects application manifest flags specifying if an application's data should be backed up or not.

96carboard said:
Its for an adb backup, which is pretty similar to what gooble backs up, and respects application manifest flags specifying if an application's data should be backed up or not.
Click to expand...
Click to collapse
Cheers, googling for it actually gave me results for mtp transfers. Gotta Google me some adb then...

Use DD

Lossyx said:
Use DD
Click to expand...
Click to collapse
What is DD ?

IIRC (this is a normal Linux command, but the method for obtaining an Android backup is pretty old) it is used to get a binary image of your selected partition. Someone correct me if I'm wrong.

@krakout: that's correct, dd is used to create 1:1 bit per bit copies of partitions. When the device is encrypted the issue is that the 1:1 copy contains the encryption. When you do a new clean setup of your phone the encryption key is reset, which will result in the backups not being usable ... this means it should work on non-encrypted devices, but restoring full partitions has always been a risky business.
I do change phones quite often (oder reflash the existing ones ), my process for backup and restore is (you need to be rooted for #1):
Backup/Restore apps and app data using Swift Backup (or free tools like OAndXBackup) - sadly this does not work for all apps (mainly security critical ones like banking apps), but still for most
Backup and restore internal storage using ADB, either with Total/Double Commander and a plugin or using a python tool - connecting the phone via USB. Transfer speed is quite high (depending on phone and PC ~30-150Mbps). Positive here is that you automatically have a full backup of your phone on a PC
use Android native backup/restore for settings

@s3axel thanks for the confirmation and the write up! Seems like indeed these days Swift is probably the best option.
Damn I got excited when you mentioned the TC plugin, thought it was something for the Android version! Not using it on my PC (love my Directory Opus setup!) but I think I'm gonna try this

While it is technically possible to do a "dd" style backup by stopping the zygote service and dd'ing it to something like a USB stick, it won't be useful because the cryptographic keys tied to the data will not be accessible.
Despite being recommended by some people, I would caution against "swift" backup software. This is something you are giving an unprecedented level of access to (for example, it could access the internet, even without internet permission!) and therefore needs to comply with the highest level of trust and security, none of which can be guaranteed by closed source software written by someone you can't even hold accountable.
Instead, I would suggest Neo Backup: https://github.com/NeoApplications/Neo-Backup (also available on F-Droid). This is OPEN SOURCE software, and you are therefore able to read every single line of code to verify that it is actually safe to use.
Others I see have suggested a TWRP backup. Believe it or not, this kind of a backup would actually be very similar to what you would achieve with Neo-Backup. However, the old "nandroid" backup is basically a historical relic -- like a "dd" backup, and didn't last much beyond the very very early solutions since it requires just so much storage space, and because its technically impossible without an external storage device (like an SD card) that is LARGER than the device's total internal storage. Even the name "nandroid" = "nand" + "android". Well direct usage of nand memory is not something you see any more, that was replaced by eMMC, which also was replaced by UFS!

Many thanks for your reply, indeed it is all about trust and I agree with you on that you never know what a software will or can do. However this also applies to the so-called open source software because you (or, more aptly: I as a user) never know whether the distributed binary is really using only the published code parts or something on top....

s3axel said:
Many thanks for your reply, indeed it is all about trust and I agree with you on that you never know what a software will or can do. However this also applies to the so-called open source software because you (or, more aptly: I as a user) never know whether the distributed binary is really using only the published code parts or something on top....
Click to expand...
Click to collapse
F-Droid is a repository for open source software, and they build the open source software themselves (as in the repository, not the software developer), and signed with F-Droid keys. They provide the exact source code archive used to produce the binary, so you know *exactly* what source code was used to build it.
Alternatively, you have the option to build from source yourself. Its not as complicated of a task as it seems as first.

Many thanks and no offense intended ... I'll have a closer look at Neo Backup for the future...

@s3axel wow, how come I missed this solution! From a cursory look, it seems awesome!
Pity it doesn't support backup services, but at least I can use MiXplorer as a document provider to pick up my NAS as a destination...