Database Info

[Recovery]cwm-5.0.2.3-liberty-agse and stock cwm-5.0.2.3-liberty

Liberty still has something no other device has - ARIA!
{
"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"
}
..........
Downloads:
cwm-5.0.2.3-liberty-agse.zip AGSE (ARIA) Edition - with cap key lights enabled
cwm-5.0.2.3-liberty.zip Stock Clockworkmod 5.0.2.3 - with cap key lights enabled

attn1 said:
Liberty still has something no other device has - ARIA!
Download: cwm-5.0.2.3-liberty-agse.zip
Click to expand...
Click to collapse
and apparently , interesting background images
*****
I am still on v2.5.0.1 - and help on how to install this img?

Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694

here's 2 ways to do it:
if you have s-off:
boot phone into fastboot mode
hook phone to computer with usb cable
ON COMPUTER:
unzip cwm-5.0.2.3-liberty-agse.zip
command prompt
fastboot flash recovery cwm-5.0.2.3-liberty-agse.img
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img

tommyguns818 said:
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
Click to expand...
Click to collapse
yep, if you are s-off with Revolutionary or AlpharevX.
Nutshell69 said:
and apparently , interesting background images
Click to expand...
Click to collapse
that's Aria herself.

Looking forward to the HTC Jenna
Sent from my Liberty using XDA App

i was wondering.....i've got s-off but no computer around me at the moment. is there a way to install this through the terminal app? I see sObe did it via terminal way but im not sure if he's s-off or not.
EDIT: I went for it and did it through terminal just like sObe and I have s-off. Worked like a charm. Thanks guys!!!

When I chose internal card I get
E:Can't mount /emc/
???

s0be said:
here's 2 ways to do it:
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
Click to expand...
Click to collapse
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.

If your doing it through terminal, you need to make sure that your doing it exactly as shown in s0bes post. Also make sure that you have your new cwm 5.0.2.3 download in the download folder on your sd card.

Nutshell69 said:
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
Click to expand...
Click to collapse
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.

Aside from the background thing, what advantages does this recovery have over 2.5.1.7? Is it faster? are the backups compatible?
T

s0be said:
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Click to expand...
Click to collapse
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?

Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App

Nutshell69 said:
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Click to expand...
Click to collapse
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.

SoCalHTCFuze said:
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
s0be said:
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
Click to expand...
Click to collapse
In fact, you cannot flash a recovery without S-OFF, unless you use the original unrevoked tool and select custom recovery (the original unrevoked only managed to install a custom recovery which was good enough at the time).

The whole point of S-OFF is that you can flash the system partition. Like Gene said, if you don't have S-OFF, you'd need to unroot and use unrevoked again.
If you do have S-OFF, it's easy:
(OS X)
md5 /path/to/cwm-5.0.2.3-liberty-agse.img (confirm md5 sum)
./adb devices (confirm you're connected)
./adb reboot bootloader
./fastboot-mac devices
./fastboot-mac flash recovery /path/to/cwm-5.0.2.3-liberty-agse.img
./fastboot-mac reboot
./adb reboot recovery (wait to hit enter until the boot animation starts)
I haven't used it yet but I hear the backups are faster in 5.x

^^^ 5.0.2.3 is a little faster. I saw the new option to fix permissions in the recovery and tried it. Man it took like 30 min to run and chewed about 60 percent of battery. From now on I'll just use ROM manager. It never failed me and is way quicker. On further note....I like it. Go miss aria!

s0be said:
If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago.
Click to expand...
Click to collapse
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.

drumist said:
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
Click to expand...
Click to collapse
egads - got this error
Error: failed to get root. Is your firmware too new?

[Guide] How to Downgrade Latest Hboot 2.00.0002>> without using HTC Dev V2

This method works for software version 2.11 and above and doesn't work for version 2.10 below.. Please use zegRush if this doesn't work for you.
FOR PHONES THAT ARE NOT ROOTED
Note: For locked bootloaders only. Do not use Htc dev prior to using this guide.
First thanks to:
1. mtothearkus
2.petarpLab..
3.jcase for TacoRoot..
4. amidabuddha
5.zryvffn (misc_version_universal)
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY HAPPEN TO YOUR DEVICE..
This was tested on latest OTA ASIA 2.15.xx with latest Hboot 2.00.0002.
Latest 2.15 cannot be rooted with zegRush so did some research..
Things Needed:
1.tacoroot
2.misc_version (download attachments below)
3.OLDEST RUU for your "REGION/ BRAND".. i repeat, specific region to avoid customer ID error.
4. adb (you know how it works)
5. phone in USB debugging mode.
STEPS:
1. download tacoroot and misc and put all files in your desired directory.
2. Run terminal and change location to where you files are.
3. now type:
Code:
adb push tacoroot.bin /data/local/tmp/tacoroot
adb push misc_version /data/local/tmp/
4.After pushing all the files, run tacoroot by typing:
Code:
adb shell
chmod 777 /data/local/tmp/*
/data/local/tmp/tacoroot --setup
5. After this commands your phone "REBOOT" the phone to recovery. Now press vol up then power then REBOOT to boot the phone normally. Wait till it boots completely and then type:
Code:
adb shell
/data/local/tmp/tacoroot --root
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6
7. After its done you can now flash your "REGION/ BRAND specific RUU".
8. After your done with RUU. Proceed to http://revolutionary.io..
Happy Flashing
FOR ROOTED PHONES
*Proceed with:
STEP 3
STEP 6
STEP 7
STEP 8
-Done
*Added misc_version_universal thanks to zryvffn

Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App

scan6 said:
Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Say if you did it by this procedure.

Yes! it works very wellwith my version 2.13 to1.47
It's quite easy to do it
Thx a lot!
Sent from my HTC Desire S using XDA App

Thx for the guide. Worked great. I downgraded from 2.15 to 1.31 asia wwe.
From my Desire S Using XDAP

Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.

nodeffect said:
Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.
Click to expand...
Click to collapse
hey dude thanks.. btw this guide is for those who can't downgrade using mtothearkus method.. those recent 2.15.x versions..its just the same but it uses different root methods.. all credits to mtothearkus..appreciate it dude..thanks..

Thanks, noted.

After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002

qpkqkma said:
After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002
Click to expand...
Click to collapse
Dude what your software version number? brand if any?.. if this root doesnt work.. try zegRush method..
or try this
Update to latest available firmware, then try.
If that fails, do a factory reset and try.

Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
Zergrush method from mtothearkus's thread should work for you

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
That's it.. hehe. 2.10 is an old firmware.. ASIAN OTA is 2.15.. so try the zegrush method.. this tut was developed for those who can't root using the zegRush..thanks amidabuddha..=)

Signed up here at xda just to say that this worked nicely on my Desire S.
I had difficulty making the ADB code given by shadi22 work at first, but after redoing them and just copy pasting them in terminal, they worked. My Desire S also had an Asia 2.15 ROM and 2.00.0002 Hboot. Used the Asia WWE 1.48.707.1 RUU to downgrade the HBOOT after changing the misc-version and tacorooting, then Revolutionary all the way
At first, I thought that I made a mistake choosing this phone (My Desire's display got borked and SISPH's repair quote was way too expensive for a nearly two year old device ) because of the need to downgrade the hboot before getting S-OFF, but shadi22's method is probably the most elegant of all the S-OFF methods on 2.00.0002 devices

HAHAHA.. thanks dude.. Anyway.. SISPH are full of dumb people.. i had problem with my device too.. a green dot on an LCD screen. my phones on warranty but never had it repaired since they have no replacement part yet. so give up on the idea for that damn SISPH.. They had the worst customer service.. they should never have been contracted with HTC on the first place.. No HTC on my next phone. The reason to go with HTC was mainly for the developers in this beloved site.. But now im seeing great dev from other phone section..=)

Try to do a zergRush method. Everything run fine, i do steps 1-5, do a step 6 (run RUU etc etc.) but RUU say me error updating, phone stuck on HTC logowhen i pull out cable it load in HBOOT and say "RUU Security Fail ! Update Fail!".
Sucks.....im downloading RUU with SW 2.10.401.8 to recover phone.....
Any other method ?

Hey guys,
So I tried this method but encountered the following issue as shown in the image 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"
}
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.

dontjudgemekk said:
Hey guys,
So I tried this method but encountered the following issue as shown in the image below:
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.
Click to expand...
Click to collapse
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?

tpbklake said:
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?
Click to expand...
Click to collapse
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?

dontjudgemekk said:
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?
Click to expand...
Click to collapse
Yes after you create the adb shell and get the $ prompt type:
chmod 777 /data/local/tmp/misc_version
chmod 777 /data/local/tmp/taco root.bin

[Root][Guide] Rooting ICS 4.04 leak from the 2.3.6

FILES WERE ATTACHED. I HOPE IT IS VIRUS FREE BUT I CANNOT PROMISE AS THERE MAY BE SOME TROJANS BECAUSE I DOWNLOADED AT SOMEWHERE. You've been warned. That's why I placed the list of files originally.
0. Your system must be in version 2.3.6 or below, which can be rooted by motofail. Do double wipe before you flash.
a) Place the following files in the same folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
motofail
su
Superuser.apk (script default) / supersu.apk
b)(optional) Prepare the modified RSDlite which can flash any roms...
c) Prepare the Motorola driver and install it.
d) use notepad to create a script (root.bat)(provided below) and save it in the same folder with the files above.
1. Connect your phone to the computer. You'd better install the drivers for your phone first. Turn on "USB debugging" and connect it as "charging mode".
2. You CANNOT unplug your usb cable and you CANNOT close the rooting program/script in the whole process.
3. Run the root.bat.
4. it will push some files into your phone and reboot your phone.
5. You will see the caution symbol with the Android robot.
6a. Flash your rom by the stock recovery
OR
6b(i). Pull the battery out.
6b(ii). HOLD the volume-down button and put the battery back.(Power ON) It will boot into the AP mode. (If you can see the blank secreen but not showing "USB CONNECTED, FLASH OK" , release the volume button or retry)
6b(iii). run the RSDlite to flash your rom
7. The phone will reboot and update few(1-3) times.
8. The phone will be rooted after the final reboot.
9. Take out your SD card and do factory reset. (The root will be kept) (I found this may solve some problems)
Script is here :
Code:
@echo off
cls
adb kill-server
adb wait-for-device
adb.exe shell mv /data/local/12m /data/local/12m.bak
adb.exe shell ln -s /data /data/local/12m
adb.exe reboot
adb.exe wait-for-device
adb shell rm -r /data/local/tmp
adb shell mkdir /data/local/tmp
adb push motofail /data/local/tmp
adb shell chmod 755 /data/local/tmp/motofail
adb shell /data/local/tmp/motofail exploit
adb reboot
adb wait-for-device
adb remount
adb.exe shell rm /data/local/12m
adb.exe shell mv /data/local/12m.bak /data/local/12m
adb.exe shell mv /data/local.prop /data/local.prop.bak
adb.exe shell "echo 'ro.kernel.qemu=1' >> /data/local.prop"
adb.exe reboot recovery
echo The phone will boot into the recovery mode
echo please follow the tutorial for the rooting process
echo do not close this window
ping -n 8 127.1>nul
adb wait-for-device
adb remount
adb push su /system/bin
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb shell chmod 666 /system/app/Superuser.apk
adb shell rm -r /data/local/tmp
adb shell mkdir /data/local/tmp
echo Your phone is rooted!!!
PAUSE
The script is provided by the crc3334404 at gfan.com .Some text is modified by me.
The guide is mainly based on his guide too. (with several modification and addon etc)
Tested on ME865

attach the required files
Edit:- thanks will try

may be i am noob but when i run the bat file it say
C:\root>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
Click to expand...
Click to collapse
and stays there waited for 15 min but nothing happend
EDIT:- as i said i am noob, forgot to tick usb debugging

shamsud said:
may be i am noob but when i run the bat file it say
and stays there waited for 15 min but nothing happend
Click to expand...
Click to collapse
probably bad drivers or something

shamsud said:
may be i am noob but when i run the bat file it say
and stays there waited for 15 min but nothing happend
EDIT:- as i said i am noob, forgot to tick usb debugging
Click to expand...
Click to collapse
So sorry that I didn't mention originally.
Actually I can't sure whether it works in MB865. May you please tell us after trial. Thanks

Results?
Sent from my Atrix II using xda premium

lilhaiti said:
Results?
Sent from my Atrix II using xda premium
Click to expand...
Click to collapse
Id really like to know as well! Haha

sorry guys am unable to flash with stock recovery it say "assert failed" i downloaded the file from below thread
http://forum.xda-developers.com/showthread.php?t=1684443
Click to expand...
Click to collapse

shamsud said:
sorry guys am unable to flash with stock recovery it say "assert failed" i downloaded the file from below thread
Click to expand...
Click to collapse
do you have a MEARET phone? are you fully stock?

fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works

shamsud said:
fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works
Click to expand...
Click to collapse
Could you upload a backup.i need it to work on getting cm9 working with data. I cant just use the ics update because its only patch files.i need the already patched files.pm me the link to the upload if u can upload it as soon as possible. I just need the system.ext3.tar
Sent from my MB865 using xda premium

rdavisct said:
Could you upload a backup.i need it to work on getting cm9 working with data. I cant just use the ics update because its only patch files.i need the already patched files.pm me the link to the upload if u can upload it as soon as possible. I just need the system.ext3.tar
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
He sent me a PM I told him to do a cwm backup and give us the system and also to dump boot with dd in case we need it for anything

I rooted failed....
It stock after RDS 4.0.4....
I plug the usb and all drivers are ok, then press anykey, then.....it stock...
My OS windows 7 64bit...

dickluo said:
I rooted failed....
It stock after RDS 4.0.4....
I plug the usb and all drivers are ok, then press anykey, then.....it stock...
My OS windows 7 64bit...
Click to expand...
Click to collapse
Questions may help:
1. did you flash it back to 2.3.6 First?
2. Did you root the 2.3.6 successfully by the batch?
3. Flashed the 4.0 after root with no Window closed?
4. Always connected with usb?
5. Usb debugging enabled?
6. No superuser.apk? May be you don't need to do factory reset after rooting. Please let us kvow.
If all yes, please tell us your 2.3.6 version too. E. G. 55.109.xxx
Sent from my ME865 ICS4.0 using XDA premium.

Double post, deleted

shamsud said:
fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works
Click to expand...
Click to collapse
Which cheesecake rom did you start with?
Sent from my ME865 ICS4.0 using XDA premium.

4.0.4 drains battery very fast
Two observations after testing ICS on MB865
1/ battery drains twice as fast for ICS 4.04 compared to GB 3.6.6
2/ Screen slower response

austin_boy said:
Two observations after testing ICS on MB865
1/ battery drains twice as fast for ICS 4.04 compared to GB 3.6.6
2/ Screen slower response
Click to expand...
Click to collapse
Never tried GB 3.6.6 and am afraid it doesn't exist.
My battery is ok:
{
"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"
}

xanadu said:
Never tried GB 3.6.6 and am afraid it doesn't exist.
My battery is ok:
Click to expand...
Click to collapse
Maybe because you are on T-mobile and don't use 3G

socialx said:
0. Your system must be in version 2.3.6 or below, which can be rooted by motofail. Do double wipe before you flash.
Click to expand...
Click to collapse
Can anybody help me to find 2.3.6 firmware for ME865?

[BETA][TOOL] adb_bak2computer [MAC & LINUX][UPDATED: 11/15/2012]

BETA TESTERS NEEDED!!
DESCRIPTION: adb_bak2computer.sh
- tool (set of scripts) to backup d2vzw (SCH-I535) partitions directly to a users computer.
{
"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"
}
PROGRESS:
- Beta5 - Now in two flavors, Mac and Linux!!
- Fully functioning tarballs are attached to the OP (as always)
TO-DO/KNOWN BUGS
- Re-wrote the code so it actually works on Linux now. (See the _Linux tar)
- All known bugs fixed. Unless someone points one out.
- To Do: Add functionality to wrap backups into a flashable zip (it'll be a big zip, but its one file to keep track of instead of blobs or sets of img files) This should be the first restore option I explore.
- To Do: Automate a standard backup (include: System, Boot, Data)
- To Do: Automate a set of backups that are compatible with TWRP. Why TWRP, cause I like it, and the differential backups that CWM does will be problematic for this tool. (I may need some help on this one.)
WARNING USE AT YOUR OWN RISK
I am not responsible if this tool destroys your soul, or your phone, or it makes a rainbow rhinoceros shoot out your bum.
NOTE: We all know the risks of doing stuff like this by now right? But the warning is still par for the course I guess. Is there a standard warning file I could link to, and make it all fancy and legal? Kinda like creative commons license only creative warning instead? Moving on...
PREREQUISITES
YOUR DEVICE MUST BE ROOTED
Linux or Mac operating system (maybe Cygwin might work, but I haven't tested it)
If you are on Linux you must have xterm installed (gnome-terminal or konsole alone won't work)
Must have the android SDK installed, and "platform-tools" must be in your $PATH
Process Viewer, "pv", must be installed
NOTE: To check if you have Process Viewer installed run pv --version in your terminal, if its not there download from here and install.
INSTRUCTIONS:
Download the appropriate tar for your OS
Extract it to a folder named "adb_bak2computer" in your $HOME directory.
Chmod everything so its all executable (chmod -Rf 777 ~/adb_bak2computer ).
Make sure your SGS3 is plugged into your machine via USB, and that you have USB debugging enabled.
If you are on CM10 or some other AOSP based ROM check the preference that keeps the screen on while plugged in.
If you are on a TouchWiz ROM use something like Wake Lock - PowerManager and force a full wakelock so your device doesn't go to sleep and or lock out adb debugging.
Run adb_bak2computer.sh from the terminal.
Pick a number
ALL CREDIT GOES TO:
das7982 - for ODIN guide here:
http://forum.xda-developers.com/showpost.php?p=28876440&postcount=1
scandiun - for "nandroid" backup directly to computer guide here:
http://forum.xda-developers.com/showpost.php?p=29862574&postcount=1
(and whomever they credited in their guides as well)
Feel free to fork, download, mod, make it all pretty, whatever you want. Its all open for sharing.
REPOS:
http://github.com/ALQI/adb_bak2computer-Mac
http://github.com/ALQI/adb_bak2computer-Linux
PM me if you want to help me with this tool, or just want to have a nice cup a tea.
Ta,
ALQI
REFERENCE THREADS:
El Grande Partition Table Reference -- E.V.A
Unlock Bootloaders -- AdamOutler
Android Kitchen -- dsixda

Look's kinda cool. Can't wait till this is finished!

Why not just use "rsync for android" from the market?
Sent from my Galaxy Note 10.1 using Tapatalk 2

blulite said:
Why not just use "rsync for android" from the market?
Sent from my Galaxy Note 10.1 using Tapatalk 2
Click to expand...
Click to collapse
That's for file based backups, which is great and I love rsync and ssh, but its not what I'm looking for. I want full on partition images going directly from my phone to my laptop (hopefully at USB2.0 speeds). So far the only way that I have seen that can do this is with scandiun's guide here:
http://forum.xda-developers.com/showpost.php?p=29862574&postcount=1
It works. I've tried scandiun's original directions and it does produce viable iamges. What I want to do is automate/simplify that process.
So far, I haven't had a chance to figure out how to get adb to play nice with spawning subprocesses in bash scripts.
like :
Code:
#!/bin/bash
function1(){
echo "function is running"
adb forward tcp:5555 tcp:5555
adb shell /system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd bs=4096 if=/dev/block/mmcblk0p17
}
function2(){
echo "function2 has to finish execution before either function can exit"
adb forward tcp:5555 tcp:5555; cd ./Cache_Test; nc 127.0.0.1 5555 | pv -i 0.5 > ./mmcblk0p17_cache.img
wait
echo "function2 is done"
}
function0(){
(function1)&
(function2)&
wait
exit
}
function0
wait
exit
This code doesn't work though. And I'm pretty sure its because adb needs actual separate terminals (not subprocesses) to run the two instances of adb forward.
This means I need a portable way to spawn new terminals. I've tried xterm -e [command] and that kinda works on linux but not on mac and I doubt it would on cygwin/windows. I may have to re-write this in python, but I'd rather use bash cause not everyone has python installed or is comfortable using it. Also, I'm lazy and I don't want to have to re-write what seems to be perfectly viable code.
Ta,
ALQI
FYI - I thought the cache partition would be a small safe partition to play around with, but its like 800MB on my device. I'll pick another for my next test/example.

Eureka (I think)
Ok, so I have a set of scripts now that can do what I need. That is execute in new terminal windows and play nice with adb.
This script (which can be .sh file), calls the other two .command files and actually backs up my cache partition.
Code:
#!/bin/bash
cd ./adb_bak2computer
open ./cache_bak1.command
sleep 2
open ./cache_bak2.command
wait
echo "cache should be backed up."
Here's the first command file:
Code:
#!/bin/bash
cache_bak1(){
echo "cache_bak1 is running"
adb forward tcp:5555 tcp:5555
sleep 2
echo "/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd bs=4096 if=/dev/block/mmcblk0p17" | adb shell
wait
}
cache_bak1
Here's the second one:
Code:
#!/bin/bash
cache_bak2(){
cd ./adb_bak2computer
echo "cache_bak2 is running"
adb forward tcp:5555 tcp:5555
sleep 2
nc 127.0.0.1 5555 | pv -i 0.5 > ./mmcblk0p17_cache.img
wait $!
echo "cache_bak2 is done"
}
cache_bak2
For some reason I to pipe in an echo of the command I wanted to run in "adb shell".
Also, depending on your terminal settings, the windows for the two command files will stay open even when they are done. To fix that, just make sure your preferred terminal emulator is set to close when a process is complete.
I'd still like to get subprocesses (from post #4) to work but its stating to look like adb no likey.
I'll try and have the rest of the code for all the paritions up within the next few days, I still have some things to figure out though. I can use a menu to seperate the dd instances or loop/wait for the pid's of each instance to quit before moving on to the next partition, I'm on the fence as to whether I want everything to run consecutively or to give users the option to pick each partition they want to back up. Maybe I can do both, but that will take longer for me to finish.
Please excuse the crap typing as I'm doing this all in my "spare" time, which means I should be sleeping.
Ta,
ALQI

Why not just make scripts pull each partition? Adb can simply pull them......
Sent from my SCH-I535 using xda app-developers app

tonu42 said:
Why not just make scripts pull each partition? Adb can simply pull them......
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
IIRC, adb pull is for files only. It can't pull full partition images.
I'm getting full partition images that can be (hopefully) used for Odin restoration and maybe nandroid or cwm restore.
Thanks for the input.
Ta,
ALQI
Sent from my SCH-I535 using xda app-developers app

ALPHA Version
OP is updated with fully functional alpha release of the tool.
Ta,
ALQI

Going to have to check this out over the weekend when I can sit down and read first.
Thank you for providing us with an alternative backup solution.
Sent from my SCH-I535 using Tapatalk 2

ok, so backing up the data block is HUGENORMOUSBIG
maybe mmcblk0p15 is including the internal sdcard because of that /data sub folder link to the sdcard?
I dunno for now, I'm going on 45mins and 6Gigs. I'll have to take a look in teh morning

Just wanted to let people know that this is not abandoned.
I only have one last hurdle. And that's getting an img file for /data without backing up /data/media (which is essentialy your internal sdcard). I can't really do a block dump cause mmcblk0p15 (am I even close there) is all userdata including /data/media.
Any ideas would be helpful? (Hint Hint)
Ta,
ALQI
Sent from my SCH-I535 using xda app-developers app

update ready to roll for Beta testers
alquimista said:
Just wanted to let people know that this is not abandoned.
I only have one last hurdle. And that's getting an img file for /data without backing up /data/media (which is essentialy your internal sdcard). I can't really do a block dump cause mmcblk0p15 (am I even close there) is all userdata including /data/media.
Any ideas would be helpful? (Hint Hint)
Ta,
ALQI
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I got /data backup working (yay me).
OP updated!!

alquimista said:
- Thread title updated with your American way of noting the date
Click to expand...
Click to collapse
My American way of noting the date is an ISO standard... YYYY-MM-DD

OP updated with new beta2 version of the tool.
Github commited as well.
ALL mmc blocks are set for backup now, check in the "CRAZY BACKUP OPTIONS" menu for the crazy backup options.
Next up:
Fix the echo [command] | adb shell scripts not exiting without CTRL+C
Option to have the basic backups turned into an "update".zip
Ta,
ALQI

Beta3
OP Updated with Beta3
Android side adb hang bug is fixed. Yay me.
GitHub updated as well.
Ta,
ALQI

HAAAAALLP!!!
I'm struggling a bit with creating a flashable zip with the files I get using my tool.
Basically I can pick whatever partition I want, but lets just say I want a standard backup and I've run my tool pulling the following:
Code:
boot.emmc.img
cache.ext4.img
data.ext4.tar
recovery.emmc.img
system.ext4.img
Actually, ican name them whatever I want and use whatever I want, so lets simplify that even greater and just go with:
Code:
boot.img
data.tar
system.img
The updater-binary and accompanying updater-script is pretty straight forward for the boot.img and system.img, the script would have something like:
Code:
write_raw_image PACKAGE:system.img SYSTEM:
write_raw_image PACKAGE:boot.img BOOT:
That's a bit of an over simplification depending on the updater-binary I wind up using, but its the right idea (some of the wording might change a bit but the "write_raw_image" part is whats important).
But what do I do with data.tar? Can I unpack that tar directly to "DATA:"? Something like:
Code:
package_extract_dir PACKAGE:data DATA:
I don't know if the updater-binary supports this with a tar??
I could unpack the tar file before creating the zip, but then I have to set all the permissions, which should have been preserved in the tar. Or can I just write a little script to go inside the zip that will essentially "tar -xf /tmp/data.tar /data" and unpack the tarball while in recovery?
I dunno, any ideas??
This would be alot easier if I could workout a way to dd a data.img without including the internal sdcard.
Ta,
ALQI

Beta4
OP Updated with Beta4
Github as well
Added funtionality to backup internal and external SDCards.
Ta,
ALQI

Important: Mac only
I just realized that this code probably won't work on Linux.
I'm on a Mac for most of my work, so I've been making all this on a Mac (OS X Lion 10.7). The "open" command probably won't work on linux or Cygwin.
I just need to add a quick check for for the OS and then use "xterm" instead of "open" for the .command files.
Actually, since I'm doing alot of cleanup and such, I will probably remove file extensions for most of the scripts.
Anyway, sorry for any confusion. I haven't been awake for most of this. But its definately a great big FAIL on my part. Well at least until I fix it.
Ta,
ALQI

BETA5 - Now works on Linux!!
OP Updated (as well as new repos) for new linux version.
Had to seperate out a version for linux cause Macs are dumb and can't open new terminal windows without the "open" command.
Tars are attached to the OP!!

[Q] Htc one X (AT & T) bricked and does not switches on

hello.. FRiends
i have htc one x(AT & T), i tried to install custom firmware but it bricked and it does not switches on.
Steps i followed:
1) rooted the phone
2) unlocked the boot loader
3)then tried to install custom firmware but got an error, so i googled... and found something called superCID
4) so i followed those steps, it included some token generation and image file generation
5) still i got an error with flashing the firmware and googled again and found to remove 1st line from a specific file... and i followed it
6) and again there was an error so i removed 2nd line which almost read like 1st line , and it gave me success dialogue..
7) then i clicked reboot.... AND the problem was here... it did not rebooted and remained switched off (or something else).
Present Condition:
It does not switches on.
It does not charges.
It is detected by the pc.

Did you know there is a dedicated forum for your device, which has many guides and tutorials as well as a Q & A Thread?
You can also check out these two threads there:
Frequently Asked Questions (AT&T, Rogers HTC One X, Telstra One XL)
{Answers} 2.20 Root Questions & Answers

mhadonis said:
hello.. FRiends
i have htc one x(AT & T), i tried to install custom firmware but it bricked and it does not switches on.
Steps i followed:
1) rooted the phone
2) unlocked the boot loader
3)then tried to install custom firmware but got an error, so i googled... and found something called superCID
4) so i followed those steps, it included some token generation and image file generation
5) still i got an error with flashing the firmware and googled again and found to remove 1st line from a specific file... and i followed it
6) and again there was an error so i removed 2nd line which almost read like 1st line , and it gave me success dialogue..
7) then i clicked reboot.... AND the problem was here... it did not rebooted and remained switched off (or something else).
Present Condition:
It does not switches on.
It does not charges.
It is detected by the pc.
Click to expand...
Click to collapse
What ROM were you trying to flash? What were the lines you removed? If they were safeguards against flashing something not meant for your device that was a huge mistake.
Sent from my Evita

ROM: cm-10.1.2-endeavoru.zip
sry i dont remember well but started from "abstract" , and second line which i removed also started from "abstract"...

That's a ROM for the international HTC one x not for north american one x.
Sent from my HTC One X using xda app-developers app

Well you've bricked your phone by removing the safeguards that stop you from flashing a ROM not intended for your device. I have no idea why you did that.
Sent from my HTC One XL using XDA Premium 4 mobile app

:good:thanks.... I was wrongly guided by the tutorial...
Is there any solution to the problem...???

Your only solution now is to pay for a jtag repair (about $60) or pay HTC to replace the motherboard (about $200).
What tutorial told you to remove safeguards from the update script? I'd really like to know.
Sent from my Evita

mhadonis said:
:good:thanks.... I was wrongly guided by the tutorial...
Click to expand...
Click to collapse
I'm not familiar with any tutorials that instruct what you mentioned (modifying lines of text). Can you link?
Also, improvising on the tutorial steps (modifying the 2nd line) means you weren't really following it anymore, opening all that much more risk. If you aren't extremely confidant in what you are doing, and willing to live with the consequences, making stuff up is not a good idea when modding phones.

I'm willing to bet the tutorial does not exist, 99.99999% sure.
Sent from my Evita

timmaaa said:
I'm willing to bet the tutorial does not exist, 99.99999% sure.
Sent from my Evita
Click to expand...
Click to collapse
I've actually stumbled on a few you tube vids for other phones telling how to remove the device checks... Just wasn't gonna follow that sort of advice.
Sent from my HTC One XL using xda app-developers app

31ken31 said:
I've actually stumbled on a few you tube vids for other phones telling how to remove the device checks... Just wasn't gonna follow that sort of advice.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Thanks for clearing that up. I'd never follow that advice either, it's bound for tragedy. I'm still not sure why anyone would obtain their information from anywhere but XDA (unless linked by XDA). Places like YouTube just don't have the facility to differentiate between devices properly.
Sent from my Evita

timmaaa said:
I'm still not sure why anyone would obtain their information from anywhere but XDA (unless linked by XDA). Places like YouTube just don't have the facility to differentiate between devices properly.
Click to expand...
Click to collapse
Completely agree. Unfortunately it seems increasingly common for folks to look for YouTube guides as a shortcut to proper learning and reading.

redpoint73 said:
Completely agree. Unfortunately it seems increasingly common for folks to look for YouTube guides as a shortcut to proper learning and reading.
Click to expand...
Click to collapse
To me learning is half the fun. And I've been doing this since my first Android.. T-Mobile G1
Sent from my HTC One XL using xda app-developers app

trying unbrick....
i used below method but got stucked at step 15, but emmc_recover could not see my phone... i tried several times....
Unbrick process
11. Let's see if Linux sees the phone.
Code:
$ sudo dmesg | grep "qcserial"
You should see "Qualcomm USB modem converter detected" as the last line of the output. If not, you can unplug and replug the USB cable or run...
Code:
$ sudo modprobe qcserial
...to reload the driver.
12. Reset the driver, which removes any old block devices associated.
Code:
$ sudo modprobe -r qcserial
13. Now create the block device that emmc_recovery needs.
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
14. Emmc_recovery needs to know what disk to write to. An easy way to find this out is to run
Code:
$ ./getbrickdrive.sh
Which will tell you if it sees your bricked phone, and also give the proper disk. Mine was /dev/sdc and so I use that in the following instructions. Replace /dev/sdc* with /dev/sdb* or /dev/sdd* or whatever yours is.
15. Now we load the 1.12 HBoot (how exciting!)
Code:
$ sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576
You can hit enter at all of the prompts here. If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone for more than 30 seconds, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed. Flashing Hboot will take several minutes, as it has to load data in ~23K chunks followed by a reset after each.
16. Once that is finished. We have to reset the qcserial driver again.
Code:
$ sudo modprobe -r qcserial
17. And then recreate the block device.
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
18. Now we restore our original block 4.
Code:
$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576
Again, if it hangs, hold your phone's power button for more than 30 seconds then release. This file will flash very quickly (it's only 1K) and once it completes, you'll immediately notice that your chargin light turns back on.
19. Unplug your USB cable and hold the power button to hard reset the phone. In a few seconds you'll be greeted by the familiar HTC screen. Enter bootloader and check out your HBoot version. 1.12!
20. Look for some pandas to feed.
I['m sure someone will boil this process down even further or script it. Hopefully this lets folks willing to brave a Linux shell accomplish this now though.
ATTACHED FILES
File Type: zip EVO4GLTE112DG.zip - [Click for QR Code] (895.8 KB, 554 views)
File Type: zip bakp4.zip - [Click for QR Code] (263 Bytes, 511 views)
File Type: zip getbrickdrive.zip - [Click for QR Code] (668 Bytes, 658 views)
link for this method
http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107

mhadonis said:
i used below method but got stucked at step 15, but emmc_recover could not see my phone... i tried several times....
Unbrick process
11. Let's see if Linux sees the phone.
Code:
$ sudo dmesg | grep "qcserial"
You should see "Qualcomm USB modem converter detected" as the last line of the output. If not, you can unplug and replug the USB cable or run...
Code:
$ sudo modprobe qcserial
...to reload the driver.
12. Reset the driver, which removes any old block devices associated.
Code:
$ sudo modprobe -r qcserial
13. Now create the block device that emmc_recovery needs.
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
14. Emmc_recovery needs to know what disk to write to. An easy way to find this out is to run
Code:
$ ./getbrickdrive.sh
Which will tell you if it sees your bricked phone, and also give the proper disk. Mine was /dev/sdc and so I use that in the following instructions. Replace /dev/sdc* with /dev/sdb* or /dev/sdd* or whatever yours is.
15. Now we load the 1.12 HBoot (how exciting!)
Code:
$ sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576
You can hit enter at all of the prompts here. If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone for more than 30 seconds, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed. Flashing Hboot will take several minutes, as it has to load data in ~23K chunks followed by a reset after each.
16. Once that is finished. We have to reset the qcserial driver again.
Code:
$ sudo modprobe -r qcserial
17. And then recreate the block device.
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
18. Now we restore our original block 4.
Code:
$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576
Again, if it hangs, hold your phone's power button for more than 30 seconds then release. This file will flash very quickly (it's only 1K) and once it completes, you'll immediately notice that your chargin light turns back on.
19. Unplug your USB cable and hold the power button to hard reset the phone. In a few seconds you'll be greeted by the familiar HTC screen. Enter bootloader and check out your HBoot version. 1.12!
20. Look for some pandas to feed.
I['m sure someone will boil this process down even further or script it. Hopefully this lets folks willing to brave a Linux shell accomplish this now though.
ATTACHED FILES
File Type: zipEVO4GLTE112DG.zip - [Click for QR Code] (895.8 KB, 554 views)
File Type: zipbakp4.zip - [Click for QR Code] (263 Bytes, 511 views)
File Type: zipgetbrickdrive.zip - [Click for QR Code] (668 Bytes, 658 views)
link for this method
http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
Where did you find that unbrick method?
Sent from my Evita

On the evo forum I read through it before. Our device is actually really close to the evo
Sent from my HTC One XL using XDA Premium 4 mobile app

same forum
timmaaa said:
Where did you find that unbrick method?
Sent from my Evita
Click to expand...
Click to collapse
i found the method on this forum....
link
http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107

31ken31 said:
On the evo forum I read through it before. Our device is actually really close to the evo
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
mhadonis said:
i found the method on this forum....
link
http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
Yeah it is very closely related, but that method calls to load a hboot that isn't for our phone.
Sent from my Evita

timmaaa said:
Yeah it is very closely related, but that method calls to load a hboot that isn't for our phone.
Sent from my Evita
Click to expand...
Click to collapse
True but I would assume if you substituted the evita hboot it may work. .. I'm not gonna brick and try personally
Sent from my HTC One XL using XDA Premium 4 mobile app