Database Info

Boot UBCD

Boot UBCD (Ultimate Boot CD) from your Android phone (T-Mobile G1)
Step 1:
Get a microSD or SDHC card that is at least 500Mb and install it in your G1. For newbies: the slot flips open just below the green call button, you’ll have to put the keyboard up to see it.
Step 2:
Get a USB cable and hook your G1 into your computer. Slide the notification pane down and select the item named ‘USB Connected’ then choose ‘Mount’ from the popup options.
Step 3:
Download and install UBCDfix2.exe which I have re-hosted on this blog here. If you don’t trust me, an alternate location is listed on the pendrivelinux.com post. Run the EXE and extract the files to a folder named UBCD on your desktop.
Step 4:
Download the most current UBCD image. Here’s a link. Move it into the root of the UBCD folder you created on your desktop and pout the UBCDfix2 files in.
Step 5:
From the UBCD folder on your desktop, click fixubcd2.bat and follow the onscreen instructions.
DONE! You should now be able to reboot into your thumb drive. Be sure your motherboard both supports booting from a USB device and has the priority for that set above the normal hard drive. On a newer Dell, you can hit F12 to directly choose what to boot off of. Not only can you still save data to your thumbdrive from your G1 like usual, but you can get to all the stuff on your G1 via the UBCD you boot off of too.
Click to expand...
Click to collapse

Now, can you boot Ubuntu from your android device?

skyred said:
Now, can you boot Ubuntu from your android device?
Click to expand...
Click to collapse
Of course, it supports USB mass storage. There is nothing new to see here, really.

Yup. the latest version of Ubuntu even includes a utility to do the dirty work for you. It can install to any USB media.

[GUIDE] Rooting and flashing your patched Hero. (Windows) [Updated: 12/19]

Constructive criticism is welcome.
This is my first guide and it's quite late here so I'm going to go through this lightly first, and more in detail later.
Note: I am NOT responsible for any damage your phone may or may not receive. It is your fault for following this guide, not my fault for writing it. Just for the sake of saving you from a headache, I would recommend backing up your contacts before starting this guide.
Phase 1: Prepping your CDMA Hero for rooting/flashing.
1. Ensure that USB debugging and installing apps from unknown sources is enabled. You can do this by going into Settings> Applications Check unknown sources. From there go into Development and ensure that "Enable USB debugging" is checked.
2. Mount your SD card on your computer by plugging in the USB cable, and dragging down the notification area. BACKUP YOUR DATA! ALWAYS!
3. After your data is backed up, Safely remove hardware (I find it annoying to get the "this disk may contains errors" every time i plug it in) your Hero. Using your notification area, unmount your SD card.
4. On your hero, navigate to Settings> SD card and phone storage> unmount SD card. Then format your card. It should Auto re-mount after this.
5. Download FlashRec (great tool!) and Amon-RA's recovery image. Place them onto the root of your SD card (not in any folders, just drag and drop them.) Unmount your SDcard.
6. I used Linda File manager (from the market), but you can use one of your choice. Navigate to the root of your SDcard (you'll probably start there, if you dont just click sdcard.) Open flashrec with the installer, and wait until it's finished.
7. Open FlashRec, and attempt to make a backup (i simply named mine "/sdcard/backup"). If it success proceed to the next step. if not, refer to post 2.
8. In FlashRec, type "/sdcard/recovery-RA-heroc-v1.5.2.img" without the quotes. Linux is Case-sensitive, so the capital letters have to be included. tap "download recovery image". Wait for it to finish, when it does reboot into recovery mode by powering off your phone. After it's off, hold HOME and the power button. You should see some green text on a black background.
9. First things first, Make a nandroid backup. It can, and will save your ass at some point in time. Before you flash ANYTHING to your phone, ALWAYS do a nandroid backup. Congratulations, you can now flash a custom ROM!
Phase 2:Flashing your custom ROM
Since I love Flipz and his work so much I'll be using his ROM in my guide (let me know if you have a problem with it Flipz).
0. Do a nandroid backup before you even think about downloading a ROM
1. Download Fresh 1.0.
2. Do not unzip it, leave it as it is and copy it to the root of your SD card. You can do this either from recovery mode (by enabling usb mode) or through the notification bar. Proceed to recovery mode by holding HOME+END CALL (or just disable USB mode) and select "flash update from .zip" Select the Fresh ROM and wait. It should automatically reboot after it finishes installing.
3. Be patient while it's booting, it took me about 5 minutes for the first boot, after that it gets much faster. Once it loads, everything should be all fine and dandy. If it's not, well aren't you glad you made your backup? Just proceed back into recovery and do a nandroid restore.
4. You can now delete all those .apks and .zips and whatnot. Mount your SD card on the computer, and move your backed up files back onto your card.
5: Enjoy! If you don't like the clear lock, Flipz has a patch on his website (geekfor.me) to replace it with a clear screen. This should keep all of your contacts and settings in place, but I make no promises.
Sources:
The Unlockr

How to unpatch your Sprint CDMA Hero.
Phase 1: Installing the SDK/Drivers
1. Download the SDK from Google. Create a folder at the root of your C:\ drive called android (it doesn't have to be your C:\, you can put it anywhere, but this guide will use "C:\android" as it's path.)
2. If using Windows Vista or earlier, proceed to the next step.
3. Download the driver for your system.
Windows 7 32Bit
Windows 7 64bit
To find out which drivers are right for your system, go into your control panel, and change the view type to small icons. Click on system, and check and see if it says 64-bit Operating System or 32-bit Operating System. Extract the contents into:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x64 (for the Windows 7 64-bit)
or
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x86 (for the Windows 7 32-bit)
4. If you have not plugged your Hero into the computer yet, it's as simple as navigating to where you extracted the contents of the archive, and right clicking androidusb.INF (should be the second from the top) and clicking install.
5. Ensure that USB debugging is enabled by navigating to Settings>Applications>Devolopment. If it does not have a check next to it, tap it. Plug your phone in and wait for the drivers to install.
6. In Windows, navigate to the command prompt.
XP: Start>run type "cmd" and press enter.
Vista or later: Start/"orb" in the search box right above it, type "cmd" and press enter.
if you see a window pop up with "C:\Windows\system32\cmd.exe" if you have done this correctly.
7. type "cd \android\tools" and press enter. now type "adb devices". It should start a daemon, and show you a series of numbers. If it does, then congratulations! your drivers are installed properly! I'll come back and add later how to reinstall the drivers if they do not install correctly.
Phase 2: Unpatching your Hero
Ensure that you have an adaptor to plug your SDcard into your computer. I didn't use an adaptor when i did this, but I highly recomend it just to make things easier. If your phone or SDcard or computer or toaster blows up, catches fire, shoots lazer beams and burns your curtains, or causes any damage to your or anything else I take no responsibility.
1. Backup all of the data from your memory card onto your computer. Navigate to Settings> SD and phone storage. Unmount your SD card and format it.
2. Go to Settings> Applications> Devolopment and ensure USB debugging is enabled.
3. Open command prompt, as you did in Phase 1, and navigate to "C:\android\tools". Type "adb shell" and press enter. Now you're in your phones console. Type "cat /sys/class/mmc_host/mmc1/mmc1:*/cid"
4. Copy down the code you get EXACTLY. Double, triple, and qraduple check. If the code is wrong, you may destroy your SD card.
5. Reverse the code.
Example:
123456789
Would become
987654321
6. replace the first two numbers/letters with zero zero. (007654321). Now on your PC, navigate to Here. Copy the number (with the zeros in place!) to the box that says CID. Click continue and wait for the email with your goldcard key. Save it to your computer.
7. Download this hex editor and install it. run it (requires administrative priveledges), and put your SDcard into your computer, or mount your SDcard.
8. In the hex editor, click on the extra tab, and open both your SDcard and the Goldcard you downloaded earlier. Ensure that "Open as read only" is unchecked when you open your SDcard. Sector size should be at "512 (Hard Disks/Floppy Disks)".
9. Go to the Goldcard tab, and press Ctrl+A to highlight all of it, then press Ctrl+C to copy it. Go to your SDcard tab, and select from 00000000 to 00000170. Now click on the edit>paste write.
10. click File>save. Remove and replace your SDcard, or unmount and remount your phone. If you can navigate into the drive, congratulations you have a Goldcard.
Phase 3: Downgrading your Hero.
1. Download the1.29 RUU. Plug your phone into the USB port with your goldcard inserted. Have your phone powered on when you do this, and ensure that it is not locked.
2. Ensure that you have HTC Sync installed, and that it connects to your phone.
3. Run the RUU and wait for it to finish. After it is finished, proceed to post 1.

If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?

Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?

saintirish said:
If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?
Click to expand...
Click to collapse
As far as I know, you just have to reinstall your programs. This guide will also work for loading ROMs other then Freshhh, but some ROMs require you to do a wipe before you install them. Check to see if that specific ROM requires a wipe before doing an install. Yes, I have used this method to upgrade from RA's 1.2.3 to 1.5.2 with no problems.
@_Chris_Kirkland said:
Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?
Click to expand...
Click to collapse
I have no idea about Droid modding, as I don't have a Droid. I'm not to fond of the idea of writing a guide for a phone I don't have because I wouldn't be able to verify that it works with minimal problems.

Alright, I've completed the basics of how to do this. I'll add a problems and solutions section once people start having problems.

great job, this should help folks out a good deal.

That's my intention. Just trying to make things easier for those who aren't so good with the console. I think I'm gonna go ahead and do the Win7 driver workaround now.

In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.

jfoster38122 said:
In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.
Click to expand...
Click to collapse
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?

So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a custom rom that I could downgrade to 1.29 or is there something different now?

mark920 said:
So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a customer rom that I could downgrade to 1.29 or is there something different now?
Click to expand...
Click to collapse
This is a guide to try and simplify patching, but it also covers a section on how to downgrade a phone that Sprint/HTC patched so that the 1.29 RUU method wouldn't work.

How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?

mark920 said:
How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?
Click to expand...
Click to collapse
Ether get a newer Hero, or run the software update in the phone. I ran the software update >_>

abcdfv said:
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?
Click to expand...
Click to collapse
Once I enter the recovery image in, the 2 options are "Flash Recovery Image" and "Restore Backup Image"
There's no download recovery image option.
- JustPyro

It may have been updated since I used it... I'll look into it
EDIT: Click on FlashRecovery image.

Excellent work! I just want to let you know that the link for the RUU 1.29 does not work (at least for me). Great guide though.

Link updated.

[Guide] Backups - After Rooting, before ROMing, take this step:

Return to Contents Page - doubleshot Developers Reference
Also, see this post on Preparing for backup.
Hey all, time for a quick public service announcement to help people make sure they don't lose things they may want to use later that came on their phone.
Post 1 - ADB backup methodology. Does not create installer package.
Post 2 - Clockworkmod Backup methodology. Does create installer package usable through CWM.
****Post 2 to be updated for Official CWM 5.0.2.7 - Meantime the method is the same.
Post 3 - To be announced.
IMPORTANT: Make sure you back up all your unique user data ( phone numbers, saved files and the like ) before doing anything to the phone. If something happens and you lose your data, don't blame me. The point of this guide is to backup your stuff, and stress the importance of backups, so ( Duh! ) make sure you backup anything you've done to the phone before you start.
-Back up your SDcard as well before starting. Just plug your phone into your computer and open up a window to it, you can drag and drop all the files off the SDcard. You could also power off the phone ( fastboot off! for best results ) and take out the SDcard and plug it into your computer with a card reader to accomplish this.
-After you back up your stuff, might be a good time to do a factory reset to your phone. If you haven't flashed a ROM yet, then perfect! Do a factory reset anyway to make what we're gonna do next as "stock" as possible. After a factory reset you will probably have to re-install superuser and busybox.
( To do a factory reset, open your app drawer and go to settings. Then go to "SD & Phone Storage" and select "Factory data reset". Yes, you do want to wipe your SDcard too. )
By the end of this guide you will understand why everyone here playing around with this kind of stuff should have the Android SDK on their computer, so on to the guide:
Today's workshop is going to require the use of ADB ( android debug bridge ), but don't be afraid of it - it's not as hard as it seems. I will also be assuming the use of a windows computer ( I'm using XP, other versions are probably similar in executing these instructions )
What we're going to do is make a quick backup of all the stuff you can easily save on your device.
You will need root access to the device to make this happen, or you will get : permission denied.
So, after you successfully S-OFF, then install Superuser (Root) and busybox, ( don't forget to check that you have root & busybox installed correctly ) put the phone down for a few minutes and take the time to get ADB running on your computer.
You'll need to download the Java Development Kit and install that on your computer. Next, you'll need the Android SDK downloaded and installed on your computer. Don't forget to run the SDK manager to get the rest of the android tools you need to make it work. Plenty of guides around on XDA if you need help with that. You will need platform-tools to use ADB.
Also, configuring the Android SDK itself to work on your computer is beyond the scope of this guide, but again, there are tons of resources all over XDA to find out how to do this.
For the rest of this posting, I will assume you have ADB set up, and I will assume you install the Android SDK to the following location:
C:\Android
That's a folder on your C: drive called Android. So far, pretty simple, right?
(If you installed it somewhere else, just modify the command to account for that)
Okay, now that that's all done, let's go ahead and get your phone backed up.
*Note: This does not make some kind of installable package you can put back on your phone, or anything like that. It will simply put everything you can copy from your phone into a folder on your computer, that you can use to get original stuff from.
For instance: You can use a stock .apk file and re-install it on your phone, or maybe you lost your stock fonts and want them back again. Simply find the font folder and copy them back onto your phone.
Click to expand...
Click to collapse
First thing you have to do, is pick up your phone and make sure it's in USB debug mode. You can accomplish this by going to:
App drawer - Settings, then Applications, then Development, then selecting "USB debugging"
Click to expand...
Click to collapse
You might want to also select "Stay awake" while there too, to prevent the phone from sleeping while you work with it.
That being done, plug your phone into the computer with the USB cable it came with. Don't do anything else to it yet, just forget about it for a little while.
(I will put all commands you type in bold so you can see them easily. Make sure to not miss any empty spaces between letters or symbols, and type them in exactly as shown.)
Now, kick up your command prompt. Go to Start, Run, and type in cmd and hit enter (or click ok).
Next, type in CD \ and hit enter. Your command prompt should now just look like:
Code:
C:\>
Now, type in CD C:\Android\platform-tools and hit enter. Before hitting enter, it will look exactly like this:
Code:
C:\>CD C:\Android\platform-tools
Your command prompt should now look like:
Code:
C:\Android\platform-tools>
Okay, stop. Go to your C drive on your computer. Make a new folder, call it "AndroidPhone" (no quotes or spaces in the name). We called it that so it will sit right next to your Android folder, making it easy to find.
Okay, go back to your DOS window, and make sure you still see...
Code:
C:\Android\platform-tools>
...as the last line in the window.
Now you want to type in: adb pull / C:\AndroidPhone and hit enter.
Before you hit enter, the whole line should look like this:
Code:
C:\Android\platform-tools>adb pull / C:\AndroidPhone
Note the spaces, and where they are. Make sure to get the forward and backward slashes right.
After you hit enter, sit back and wait. The DOS window is going to light up with a whole mess of stuff that will scroll down the screen. Some things will be skipped, others won't be. Just be patient and wait for it to be finished, it's going to take a while. Some things will happen faster then others.
When done, your DOS window will sit there and the last line will look like:
Code:
C:\Android\platform-tools>
...and have a blinking underscore right after it.
Go check the AndroidPhone folder, and make sure you got it all. It should be somewhere around 700MB in size. If it's a lot less, then you weren't successful.
That's it! Congratulations, you now have a copy of most of what was on your phone when you got it. Wasn't that hard, was it?
Let's take a look at some other ways we can use the pull command:
If you want to back up a specific folder, the "system" folder for instance and put it in a different folder called "NewBackup", then you would type this in as your command instead:
adb pull /system C:\NewBackup
...and it should look like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system C:\NewBackup
Make sure to create the "NewBackup" folder before running the command!
If you only wanted to back up the system apps on the phone, and wanted them in a seperate folder called "AppBackup" and then in a folder inside that one called "stockapp" - you would type in this command:
adb pull /system/app C:\AppBackup\stockapp
...and it would look like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system/app C:\AppBackup\stockapp
Don't forget to make the folders you will be saving to before you run the command.
For our last example, if you wanted to back up a specific app, to just your C drive, you could do this command:
adb pull /system/app/Calculator.apk C:\
...and it would look like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system/app/Calculator.apk C:\
Two things to note here:
1- Typing this does not work:
Code:
[COLOR="Red"]BAD CODE EXAMPLE DO NOT DO THIS[/COLOR]
C:\Android\platform-tools>adb pull /system/app/[COLOR="Red"]c[/COLOR]alculator.apk C:\
Why? the app name is typed with a lower-case "C" at the beginning. This is case sensitive, and the app we are talking about has an upper-case first letter. Compare that bad code example to the previous good one for the same app.
2-The HTC optimized apps have an "Odex" file there as well. Backing up this specific app directly, which also has a companion file Calculator.odex, doesn't get the other file. We also have to get it manually by doing it this way, type in the following command:
adb pull /system/app/Calculator.odex C:\
...which looks like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system/app/Calculator.odex C:\
...and you will have both the app and it's odex file saved.
You don't need the .odex files to re-install the app on your phone, they will work without them. Re-installing the .apk file doesn't re-install the .odex file, you would have to put the .odex file back on the phone manually.
So that about covers it, and shows how to use the command to place things in different locations, get different folders, and specific files.
I tried to show the command with just enough variation that you could easily see what parts of the command affected which part of the outcome, and make it very plain to see how it all worked.
I even made sure to show you that you can open other folders on your computer with the DOS prompt open, do things like create folders, and then come back to the DOS window and execute a command you already typed in.
I wrote this because i've seen people already asking for things like stock system fonts, and so forth, and you should already have that backed up before you go ahead and flash a ROM. To account for the wide range of familiarity people have with the adb pull command, I tried to make the whole thing targeted to someone who has never used that specific command before.
As I said above, installing and configuring the Android SDK and the adb command specifically are beyond the scope of this thread, since it's been covered to death elsewhere on XDA and we don't need yet another one of those threads.
I think you can now see why doing such a thing is a good idea even if you just flash ROMs and don't actually create them. The Android SDK can be useful for users, too, since flashing a ROM is not something a typical user of the phone is expected to be doing. By flashing a ROM, or trying to, you take that step that makes you an advanced user of your phone.
I am extremely cautious when it comes to backups of my data, and make many of them. In my experience, most people seem to only think about backups when they need them, and by then it's too late to make one. Doing this right after you get root can save you from losing anything you might want back again some day.
For bonus points, you can then burn that folder you made of all your phone data to a DVD. Don't forget to put the Java SDk, Android SDk, and anything else you downloaded or used to make this work on the DVD as well so you can do this again or on another computer...without having to download all the software packages over and over again.
Just a friendly public service announcement/guide, and as a helpful bonus, i'm going to list all the stock system apps below with their complete location listed. This may make it more helpful to browse the other threads in our corner of XDA telling you what apps you can remove and such.
My most worthwhile contribution to the development community at this time is time itself, so trying to map out and explain where everything is on the device is where i'm at. If you are reading this, then you're along for the ride too.
Edit to add:
I was going to list the stock apps here by .apk name for reference. When I sat down to do it, this came out:
MT4GS Stock App Developers Reference
Go there for a list of apps if you need it, but the reference was written for developers - the apps are listed in alphabetical order according to .apk name, not by any other names programs might call them.

Clockworkmod Backups
***Note: Posting to be updated for Official Clockworkmod 5.0.2.7 - Update forthcoming.
In the second post we will talk about Clockworkmod backups, or CWM backups.
We will be discussing Clockworkmod version 4.0.0.9
If you are still using 4.0.0.8, then you should go Here to upgrade.
Now that we're all on the same, most recent version of the MT4GS CWM recovery utility, let's take a look at how we can use just the phone itself to generate and restore our backups.
Before we start:
- Charge your battery to full. You don't want to lose power while doing this.
- Make sure you have enough free space to make the backup. A stock backup fresh after S-OFF should be right around 700MB. Try to have about a gig available on your sdcard to make sure you get the whole backup.
First, boot into recovery mode.
- Turn off fastboot in ( settings: Power: [uncheck] fast boot.
- Power off the MT4GS
- wait until it completely powers down, there will be a red light faintly blinking inside the trackpad. Wait until it stops.
Then:
+ Hold the volume-down button
+ Then press the power button
+ Hold the volume down button until you see your HBOOT menu, then release.
+ Wait for HBOOT to load, then use the volume up and down keys to navigate to recovery, and the power button to choose it.
+ Clockworkmod will load, and then you see the main menu of your recovery utility:
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- power off
Click to expand...
Click to collapse
*Within CWM itself, you can use either the volume up and down buttons or the trackpad to scroll the menu selections.
*You may press either the trackpad or the camera button to choose your selection.
To make a backup:
+ Scroll to 'backup and restore', then select it.
At the next menu you see:
- backup
- restore
- advanced
Click to expand...
Click to collapse
Okay, as soon as you select backup, it will immediately start the backup process.
Before we do that, we just want to make sure we have a full or decent charge on the battery, and we won't be shaking or jarring the phone while it's working. Don't do this in a moving car or train or anything.
Just put it down on a table or something, choose 'backup' and then walk away from it for 5-15 minutes.
( The amount of data and class rating/brand of your MicroSD card directly impacts the time it takes to create or restore a backup. )
When you come back, the last line of text on the screen will say:
"Backup complete!"
Now you have two choices for what you should do next. First go back to the main clockworkmod menu ( hit the hardware 'back' key if necessary ) and then choose:
- power off. If you want to turn the phone off, and take the memory card out to copy the backup to something else.
- reboot system now. If you want to boot up and transfer the backup off the phone using the phone somehow.
+ I recommend reboot, then after fully booted plugging your phone into a computer through the usb cable. Then you can transfer the file to a computer without opening the phone and exposing the internals.
Once you copy the backup onto the computer, you should probably burn it to a cd or something to make sure you don't lose it.
About the 'image' files in the folder with the current time/date on it:
-Some will be saved, some will read as an error on the screen probably...
+++As long as you have these 3 images you are okay:
-Boot
-Recovery
-System
Anything else is not really necessary, but can be helpful. If you have those 3 core image files and an MD5 checksum that matches up, you're in good shape.
...and that's basically it. CWM will make the backup or not, and if not you need to figure out why. Ask questions in this thread if this happens to you and you can't figure out why.
CWM makes the backup in a folder on the sdcard called 'clockworkmod', then the 'backup' folder, then your backup in it's own folder, the name of which is the current time and date.
/sdcard/clockworkmod/backup/
Attached below is a picture I made showing the process, including some errors of partitions not found. This is still a good backup, because I have boot, recovery and system.

Saving the third too.
Information forthcoming...

Man, you are intense!

[Tool] WhatsApp Key/DB Extractor | CRYPT6-12 | NON-ROOT | UPDATED OCTOBER 2016

** Version 4.7 Updated October 2016 - Supports Android 4.0-7.0 **
SUMMARY:
Allows WhatsApp users to extract their cipher key and databases on non-rooted Android devices.
UPDATE: This tool was last updated on October 12th 2016. and confirmed working on Android 4.0-7.0 using WhatsApp version v2.16.304 (latest available).
IMPORTANT: If you wish to extract media files or WhatsApp databases from Google Drive backups then you need: WhatsApp Google Drive Extractor instead.
TUTORIAL:
BRANCH UPDATES:
v4.0 - Fixed issues with Android API 14-17 (4.0-4.2 Jelly Bean).
v4.1 - Added support for Android API 23 (6.0-6.0.1 Marshmallow).
v4.2 - Added support for specifying adb backup passwords.
v4.3 - Added PowerShell version as optional alternative to bat version.
v4.4 - Changed primary mirror for legacy apk.
v4.5 - Fixed issue pushing cipher key to emulated storage.
v4.6 - Updated primary mirror for legacy apk (again).
v4.7 - Added new sanity checks and support for Android API 24 (7.0 Nougat).
PREREQUISITES:
O/S: Windows Vista, Windows 7, Windows 8, Windows 10, Mac OS X or Linux
Java - If not installed: Download Java
ADB (Android Debug Bridge) Drivers
USB Debugging* must be enabled on the target device. Settings -> Developer Options -> (Debugging) USB debugging
Android device with Android 4.0 or higher. I.E. Ice Cream Sandwich, Jelly Bean, KitKat, Lollipop, Marshmallow or Nougat.
*= If you cannot find Developer Options then please go to: Settings -> About phone/device and tap the Build number multiple times.
INSTRUCTIONS:
Extract WhatsApp-Key-DB-Extractor-master.zip maintaining the directory structure.
Click on WhatsAppKeyDBExtract.bat (Windows) or WhatsAppKeyDBExtract.sh (Mac OS X / Linux).
Connect your device via USB, unlock your screen and wait for Full backup to appear.
Enter your backup password or leave blank (if none set) and tap on Back up my data.
Confirm backup password in your command console and then check the "extracted" folder.
TROUBLESHOOTING:
If you have never used USB Debugging before, you may also need to verify the fingerprint.
If you have set a default backup password in your Android settings, then this MUST be the
backup password that you provide when prompted to backup your data. Else it WILL fail!
Linux and Mac OS X users may need to set the script permissions as executable. Depending on the
adb permissions, you may also need to sudo ./WhatsAppKeyDBExtract.sh from your command console.
If you're having issues with WhatsAppKeyDBExtract.bat then right click WhatsAppKeyDBExtract.ps1
and select Run with PowerShell. You may have to enter "y" at first run for script execution policy.
If you get an error saying "AES encryption not allowed" then you need to update your Oracle Java
Cryptography Extension (JCE) to Unlimited Strength Jurisdiction Policy Files.
DOWNLOAD: WhatsApp-Key-DB-Extractor-master.zip
AUTHOR: TripCode
THANKS: dragomerlin for Android Backup Extractor and Abinash Bishoyi for being cool.

alternatives
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.

droopyar said:
Yes, this is a normal backup method. There are automatic tools that do the same without using PC, just on device side.
Apart from normal ADB method, you could use ECLIPSE for that, using the memory module, you could transfer files from and in.
If you have physical access to the device, there are many solutions.
regards.
Click to expand...
Click to collapse
The only way to access private application files (such as a WhatsApp's cipher key) without root is the ADB method. You can backup some files on the device without a PC (APK's etc...), but there is currently no way to access private files and folders. All the "My Big Fat Backup" style apps and tools will either require root or ADB. Eclipse also utilizes ADB. Basically, device side backups of application data require root. There are no other alternatives to this. If there was, then Android would be too infeasible and insecure as a viable operating system. Physical access translates into only two solutions. 1.) The ability to root and 2.) The ability to utilize ADB (Eclipse, Bats, Exe's doing nothing more than calling a simple command line). Of course if you are aware of a 3rd method (disregarding the user interface) and is not based on root or ADB then please feel free to share.

Thanks for this tool!
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Thanks!!
Mia
PS I got JDK installed and still not working

MiaNet said:
I've just tried to use it, but it installs the java constantly (while java is properly installed on computer as other applications uses it without any problem )
By any chance, do you have any idea how to pass that?
Click to expand...
Click to collapse
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.

still showing this message attached
TripCode said:
The bat file automatically checks for the presence of java.exe on your system. If it's not found then it starts the install. It would appear that for some reason it's not finding Java and hence why you're stuck in this loop. Please find attached a bat file without the Java check. Just put it in the same folder as the original and run this one instead. Let me know how you get on. Java also needs to be callable from the command line. To check this is working you should click on Run... within Windows, type cmd, click OK and type "java -version" (without quotes) and press Enter. This will confirm java is in the command path and print out your JRE build number. I have also updated the release in the OP and removed the Java check, as I have had a couple of similar reports of the loop issue.
Thanks again.
Click to expand...
Click to collapse
Still showing the attached message

mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).

Many thanks! I'll test when home and let you know.
Just to let know, the path command do not fix the prior version with Java check as I first thought this might be the problem.
Thanks!
Mia

Could even be use with ADB from phone to phone? without using the pc? Or I must install the app on the phone and do it offline?

I have find my way! Re-installed Java, manually clicked on java.exe stored in Java folder in Program files (or Program files (x86) ) I've clicked on Javacpl as well and enabled all options, not sure if this is necessary though.
I've then rerun the program without Java check (the Java check one is bugging now) and was able to do the back up.
Thanks!!
Best regards,
Melanie

Cannot tap button
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!

Permission denied
Hi, I followed all instructions and I generated this error.
I would appreciate your help.

Error
mesho_alaa said:
Still showing the attached message
Click to expand...
Click to collapse
I, too am showing the same error.

Curwens said:
Hi! i've done all the previous steps, but when i unlock the phone, to confirm the backup, i cant tap on "back up my data", it doesnt even grey at hover, just like the button wasn't there...
I can choose not to backup, that button works perfectly, and write the password too, i've tried all the screen, but nothing happends, so i can't backup the phone...
Does anyone think how to solve that? Thanks!
Click to expand...
Click to collapse
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
kharloz_jc said:
Hi, I followed all instructions and I generated this error.
I would appreciate your help.
Click to expand...
Click to collapse
cardinalaa said:
I, too am showing the same error.
Click to expand...
Click to collapse
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.

TripCode said:
This sounds to me like you need to update your PATH Environment variable with the directory in which java is installed.
Open up a DOS window and type: "where java" (without quotes) to determine possible locations.
If it's located in: "C:\Windows\System32" then the following code should suffice:
Code:
set PATH=%PATH%;C:\Windows\System32
If it's located in: "C:\Program Files\Java\jre7\bin" then:
Code:
set PATH=%PATH%;C:\Program Files\Java\jre7\bin
The above needs to be added to the bat script BEFORE Java is called. You can edit the bat script by opening it with Notepad.
Alternatively, you could permanently update the PATH Environment (probably a better method).
To do this you would: Right click on "Computer" or "My Computer", within Windows Explorer, choose "Properties", click on the "Advanced system settings" and/or the "Advanced" tab, then click on the "Environment Variables" button. Select the "PATH" line, click the "Edit" button, and add the relevant directory to the end of any text that exists for PATH, prefixing the java path with a ";" (semicolon) if this line already contains other string paths. If PATH does not exist then you will need to add it. Sorry this paragraph is a little double-dutch (trying to cater for multiple versions of Windows).
Click to expand...
Click to collapse
Hi, I am receiving the "Cannot find the path specified" error. I have tried both changing the script and also the other method, in environment variables. I am curious if this has anything to do with the fact that its an ATT phone (since no one can even root it yet)? No other apps can access my phone, either. I have USB debugging enabled and all prerequisite programs installed. Tried on 2 computers, win7 and win 8.1
I wonder if i it is an error on my part..?

TripCode said:
Try rebooting the device and trying again. If it is still greyed out, the backup feature maybe disabled on the device. Some manufacturers / service providers have specifically disabled usb backups.
It would appear that the key was extracted, but the "copy" wasn't pushed to the sdcard. KitKat? You don't need a copy of the key on your sdcard unless you want to use a supported app. As the key was extracted successfully, you could attempt to copy it by other means.
Click to expand...
Click to collapse
I have reviewed the "Extract" folder and there was the key. I have managed to decrypt it.
Thanks for the help and the tool!
PD: sorry for my bad English, I use translator is haha.

Nothing happens
Hi, first, thanks for this iniciative. A lot of people would apreciate this
I think I did everything as u said, but when I open the WhatsAppKeyExtract,bat and then conect my phone in debuggin mode to PC, nothing happens. Ive waited for 10 minutes and.. nothing happens. Keep showing the initial message: "Please connect your Android device..." and in my phone nothing happens too. Just show a messagem at the upper tab saying: "USB debbugin conected".
Theres any kind of setting to do futher in the debbug options?
Thanks
Update: I had do install de universal adb driver for my phone, and now it starts the download, but now im having problem with java... the messagem says "'java' isnt a recognizable command". I tried all solutions in this post and nothing.. I need heeeelp!

Solution to path problem
Is working perfect. For someone else that can happen the same thing as me. I have to fix something (i am spanish) about:
java is not recognized as an internal or external command, operable program or batch file
Here is the solution:
java .com/en/download/help/path.xml
Or here:
1. Right-Click My Computer and select Properties
2. Then Click The Advanced Tab
3. Then Click Environment Variables
4. Select Path In The Bottom Box and Click Edit
5. Find Where You installed Java (E.g "C:\Program Files\Java\bin)
Its different on each computer
6. Make Sure to add a semicolon after the word bin in the path to seperate it from the other important paths
7. If this doesnt work then you may have to reinstall Java and Try Again
Setting Path on Windows
For Windows XP:
1. Start -> Control Panel -> System -> Advanced
2. Click on Environment Variables, under System Variables, find PATH, and click on it.
3. In the Edit windows, modify PATH by adding the location of the class to the value for PATH. If you do not have the item PATH, you may select to add a new variable and add PATH as the name and the location of the class as the value.
4. Close the window.
5. Reopen Command prompt window, and run your java code.

https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!

tzuyang said:
https://www.dropbox.com/s/nm1goi6m0oob15u/Screenshot 2014-06-15 22.25.27.png
I am getting this error.
using java run time 7 update 60
any ideas?
Thanks!
Click to expand...
Click to collapse
Have seen this error before (not related to bat file). You may need to revert to an earlier Java version.

Need help booting Windows 10 in MSDOS laptop

I had made a copy of ISO file of Windows Media file on a USB drive.
In my new MSDOS laptop, I inserted my pen drive and started installing Windows.
After installation black screen appeared and it again asked me to install windows.
I tried to install it again but while choosing the partition it showed me an error:
There was an error installing Windows​
I pressed the power button and the laptop switched off.
I turned it on but the same error persisted while installing the Windows.
Somewhere I found the option for System Recovery and clicked on it.
It showed an error something like:
The installation media could not be found in the external disk.
Contact your system administrator for a media file.
Error code:0xc000000f​
The error was quite longer than this but the main points were these.
And every time I am turning on my pc I find the above-given error.
I think I had done some mistake choosing the partition while installing the Windows 10 for the first time.
There were two partitions 1 and 2 and an unallocated space for more than 950GB.
I chose the unallocated space.
HP 15-BW096AU 2017 15.6-inch Laptop (A6-7310/4GB/1TB/DOS/Integrated Graphics)

Insert your USB drive again, reboot, choose "Advanced (options)", open a command line, then enter the following commands:
bootrec /fixboot (press Enter)
bootrec /fixmbr (press Enter)
Restart your PC, and try to install Windows again.
EDIT: see here for more info https://neosmart.net/wiki/0xc000000f-error-read-boot-configuration-data/
@moderators: it would be nice to be prompted to identify ourselves BEFORE we start to reply, instead of after, so as not to lose everything we've entered in the reply box...