Database Info

getting root using MAC OS ??

Is there any step by step tutorial to get my htc magic rooted
I can only find posts where they say it is like on windows but without installing files but i have no idea how to enter that prompts on terminal
it would be much appreciated any help. I know i am not the only one interested

cesardeluxe said:
Is there any step by step tutorial to get my htc magic rooted
I can only find posts where they say it is like on windows but without installing files but i have no idea how to enter that prompts on terminal
it would be much appreciated any help. I know i am not the only one interested
Click to expand...
Click to collapse
The commands are the same. Just like Linux users can follow Windows directions but with some substitutions.
Download the SDK here: http://developer.android.com/sdk/1.5_r3/index.html
Follow the instructions here: http://developer.android.com/sdk/1.5_r3/installing.html
Once you have the SDK setup, you can follow the steps given in the rooting threads/wiki. Any time it says to enter a command you do it in your terminal (which on OSX i think is Terminal.app, use Spotlight to find it).
Hope this helps a bit.

i dont get this:
Code:
On a Mac, look in your home directory for .bash_profile and proceed as for Linux. You can create the .bash_profile if you haven't already set one up on your machine
i don't have that .bash_profile how do i create it?
thanks

Google easy to use and always there for you.
Clinton

yeah but all tutorials are made for xp or even linux.
I have tried to create it using vi command then edited with the path o the sdk tools
but when i type adb it doesn't do anything
i am stuck there

Did you check my link for your bash_profile ? This help at all?
Clinton

cesardeluxe said:
yeah but all tutorials are made for xp or even linux.
I have tried to create it using vi command then edited with the path o the sdk tools
but when i type adb it doesn't do anything
i am stuck there
Click to expand...
Click to collapse
Try reading this:
http://www.tech-recipes.com/rx/2621/os_x_change_path_environment_variable/
Sounds like the Path variable may be in a different file. It is the same on linux, I think it can be in a few places.
Irf you want to use adb without messing with your path you can do the following:
Code:
cd <android-sdk-location>/tools
./adb devices
This is convoluted so get that PATH working and everything should be nice and easy! Good luck.

I use a Mac, and when I was getting started I used the linux tutorials with no problem.

i can push the 2 files using commands to my sd. Adb devices shows my htc ok
but after i enter to fastboot mode the device is no longe shown
i type
Code:
./fastboot boot recovery-new.img
but the only thing i get is
Code:
-bash: fastboot: command not found
i am on tools directory on terminal

i think fastboot is not in the tools directory ...
i'd rather say the error is caused by that then a missing connection.
Does the phone write "FASTBOOT USB" ?
if you type "ls", can you find a file named fastboot in your directory?

cesardeluxe said:
i can push the 2 files using commands to my sd. Adb devices shows my htc ok
but after i enter to fastboot mode the device is no longe shown
i type
Code:
./fastboot boot recovery-new.img
but the only thing i get is
Code:
-bash: fastboot: command not found
i am on tools directory on terminal
Click to expand...
Click to collapse
The files have to be executable. You can do that by running:
Code:
chmod -R +x /path/to/tools
This makes all the files in the tools directory executable with ./
About the .bashrc or .bash_profile if you don't have one in your home directory you can safely make one. With the following command:
Code:
echo "export PATH=$PATH:/path/to/tools/" > ~/.bashrc
or if the file exists just do:
Code:
echo "export PATH=$PATH:/path/to/tools/" >> ~/.bashrc
Remember to restart the shell after you are done with this.

the reason adb work for you is because adb is in tools directory
fastboot does not. You have to get fastboot somewhere else
Whenever you get command not found, you can run another command to check
ls <program you ran>, and see what happened
Example
in your tools directory, where you have no problem running adb push, try doing "ls adb", without the quote
in your tools directory, where you have problem running fastboot, try doing "ls fastboot", without the quote
and you should see what's going on
BTW, this is fairly basic unix environment. If you are having trouble at this stage, you need to get yourself more familiar with unix environment, which is what osx is based on
I am sorry, but i don't really know where's good tutorial on unix
On google, i just search for "mac osx unix shell tutorial:, and come across this site
http://www.osxfaq.com/tutorials/LearningCenter/
Hope this help
Edit 1: btw, here's where you can find fastboot for MAC. Put it in your tools directory. IF you keep the filename as is, you need to type fastboot-mac whenever you see someone mention fastboot
http://www.htc.com/www/support/android/adp.html

yeah you're right fastboot is not on that tools directory. in fact i have looked into the whole sdk folder and i can't find it.
thanks

hey i managed to apply the update thanks to having fastboot-mac on tools folder
but after booting i go to terminal to apply the final step and i get this
Code:
MBdeluxe:tools cesarleon$ ./adb shell flash_image recovery /sdcard/recovery-new.img
error reading /sdcard/recovery-new.img header: Is a directory
what's wrong ?
thank you people

cesardeluxe said:
hey i managed to apply the update thanks to having fastboot-mac on tools folder
but after booting i go to terminal to apply the final step and i get this
Code:
MBdeluxe:tools cesarleon$ ./adb shell flash_image recovery /sdcard/recovery-new.img
error reading /sdcard/recovery-new.img header: Is a directory
what's wrong ?
thank you people
Click to expand...
Click to collapse
Are u sure that recovery.img got transferred properly? Maybe check the rights on it (it not read only or something). What if you mount the sdcard in OS X and copy and paste (vs push)?

If you're trying to flash the recovery image, try
Code:
adb shell mount -a
adb push recovery-new.img /system/recovery.img
adb push recovery-new.img /sdcard/recovery-new.img
adb flash_image recovery /sdcard/recovery-new.img
Hope that helps

adb shell mount -a
Click to expand...
Click to collapse
didn´t work i think the parameter a is not correct
well this is almost the last step! thank you all for your explanations

cesardeluxe said:
hey i managed to apply the update thanks to having fastboot-mac on tools folder
but after booting i go to terminal to apply the final step and i get this
Code:
MBdeluxe:tools cesarleon$ ./adb shell flash_image recovery /sdcard/recovery-new.img
error reading /sdcard/recovery-new.img header: Is a directory
what's wrong ?
thank you people
Click to expand...
Click to collapse
Very odd error message
Do this to check what your phone's sdcard looks like
Code:
adb shell ls -l /sdcard/recovery-new.img
Next, you should grab the file from your phone to your computer. This step assume you are in your tools directory
Code:
adb pull /sdcard/recovery-new.img recovery-new-phone.img
Finally, try to compare the file you have on your computer against the one you got from your phone, and see if they are the same. This assume you have your working recovery-new.img in tools directory
Code:
diff recovery-new.img recovery-new-phone.img
I have not try this diff command, and I assume it'l handle binary diff
If diff can not handle binary file, do ls and check file size. both file should match
Code:
ls -l recovery-new.img recovery-new-phone.img
If your computer and phone recovery-new.img are not the same, download to phone again

cesardeluxe said:
didn´t work i think the parameter a is not correct
well this is almost the last step! thank you all for your explanations
Click to expand...
Click to collapse
You will get Failed Mounts when u run
Code:
adb shell mount -a
You CAN ignore them.
See here: http://forum.xda-developers.com/showthread.php?p=4029461

This may not be the right way to do it but I always just downloaded the recovery to the tools directory of the android sdk. Then fire up the phone in fastboot mode and do:
./fastboot flash recovery recovery-new.img
(replacing recovery-new.img with the name of the downloaded img file.)
I'm sure there is a reason people are doing it the other way, but for myself one command to do the flash is alot easier!

[Q] i have an error while i'm trying to update firmware

when i'm trying to update firmware im geting this:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
255|[email protected]:/ $
and because of that i can't go to the next step
what's wrong with it??

bobnur said:
when i'm trying to update firmware im geting this:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - [COLOR=Red]Permission denied[/COLOR]
255|[email protected]:/ $
and because of that i can't go to the next step
what's wrong with it??
Click to expand...
Click to collapse
adb shell
su
then type your commands
Maybe give link to commands or post commands to be used.

tobdaryl said:
adb shell
su
then type your commands
Maybe give link to commands or post commands to be used.
Click to expand...
Click to collapse
my tab is not rooted...
su just works with rooted tabs...

bobnur said:
my tab is not rooted...
su just works with rooted tabs...
Click to expand...
Click to collapse
Updating can usually be done by unzipping update once and placing the new zip on sdcard or external sdcard, reboot and accept request to update - shows in notification area
Have you tried that method?
also
fastboot -i 0x0B05 flash system update.blob
fastboot -i 0x0B05 reboot

tobdaryl said:
Updating can usually be done by unzipping update once and placing the new zip on sdcard or external sdcard, reboot and accept request to update - shows in notification area
Have you tried that method?
also
fastboot -i 0x0B05 flash system update.blob
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
Somehow it doesn't work...
Is it some other ways??

bobnur said:
Somehow it doesn't work...
Is it some other ways??
Click to expand...
Click to collapse
I don't know of others without being rooted or flashing a recovery ( twrp ).
Maybe someone else has a better idea!

tobdaryl said:
I don't know of others without being rooted or flashing a recovery ( twrp ).
Maybe someone else has a better idea!
Click to expand...
Click to collapse
My knowledge of linux/android is limited, but I agree with post #2. You need to have root (su) permissions in order to move that file, because I'm assuming its on the root of your tablet's internal memory. So, you could either use the "su" command, type in the appropriate password and THEN move the files, or use the (safer) sudo command, which will allow you to perform just one action. If you login as superuser (using su w/ password), you have unlimited access and could potentially really break stuff if you're not careful.
Another idea is that since you're moving it from the /data partition, and that partition is currently in use, it would deny you permission. Theoretically speaking, you could unmount the partition through CWM and then just access your tablet in fastboot mode (don't boot into Android, as it needs that /data partition).
Just my two cents, and I'm not responsible if your tablet breaks, or if the zombies eat it. You know, whichever comes first

[REQUEST] [Dumps] [Evita-Utl] Need (hboot,misc partition,radio,adsp,wcnss) imgs

Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help

Why?

tjhooker73 said:
Why?
Click to expand...
Click to collapse
Do you have the middle eastern variant?
Sent from my Evita

tjhooker73 said:
Why?
Click to expand...
Click to collapse
timmaaa said:
Do you have the middle eastern variant?
Sent from my Evita
Click to expand...
Click to collapse
Someone in other thread tell that middle east version(ul flashed) can be fixed by those 3 blocks and radio block ofcours .. but do you have any suggestions for recover my misc partition .. if I was lucky and someone upload it to me .. do you think that adb can restore it ??

dr.scofield said:
Someone in other thread tell that middle east version(ul flashed) can be fixed by those 3 blocks and radio block ofcours .. but do you have any suggestions for recover my misc partition .. if I was lucky and someone upload it to me .. do you think that adb can restore it ??
Click to expand...
Click to collapse
What's wrong with your phone?

Need the imgs because no firmwares or ruu fo this phone .. and my utl flashed ul and bricked .. then relifed with evita-ul dll because no dll for it .. so since there no firmwares for it and I replaced mine .. I need it from any working phone by dumping it .. if you can help

Anyone??
Sent from my HTC One XL using XDA Premium 4 mobile app

dr.scofield said:
Anyone??
Click to expand...
Click to collapse
I upload these 5 files on my google drive
But I can't post the link
Send me you contact at "sladefoto" a t gmail

Sladefoto said:
I upload these 5 files on my google drive
But I can't post the link
Send me you contact at "sladefoto" a t gmail
Click to expand...
Click to collapse
Thanks .. i've managed these files and fixed this phone

dr.scofield said:
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Click to expand...
Click to collapse
i have same problem and still my device (no service )not antenna after jtag with riff box
my device one xl (evita utl pj83500) s-off and super cid
i dumped this 5 files but i dont know how to solve my problem and flash misc.radio and hboot files ==> when i write fastboot flash radio radio.img say error : not allowed
how to eng-s-off this model to flash radio.img and hboot.img
pls help

How did you flash them?
I have the same problem but I don't know how to flash the partitions.

Thread Cleaned, there is no "trading", "selling" for device files or anything of that sort, of funds or gifts, as per Forum Rules.

dr.scofield said:
Hey
Please can anyone have 'Evita-Utl' (Middle eastern variant) help me by dumping (hboot,misc partition,radio,adsp,wcnss) imgs from his working device .. and here is how:
1)first you must get into recovery(cwm) because img token from booted device is useless for me
2)then while you are in cwm recovery connect to pc and adb
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
adb pull /sdcard/hboot.img
adb shell
dd if=/dev/block/mmcblk0p23 of=/sdcard/misc.img
exit
adb pull /sdcard/misc.img
adb shell
dd if=/dev/block/mmcblk0p17 of=/sdcard/radio.img
exit
adb pull /sdcard/radio.img
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/adsp.img
exit
adb pull /sdcard/adsp.img
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/wcnss.img
exit
adb pull /sdcard/wcnss.img
and upload these 5 files from your sdcard .. I will be grateful
Thanks for help
Click to expand...
Click to collapse
thanks god, could you tell me how did you do with 5 files, please share? we have the same problems, hope you help us? pls!

vincent844 said:
thanks god, could you tell me how did you do with 5 files, please share? we have the same problems, hope you help us? pls!
Click to expand...
Click to collapse
Do you have these 5 files If yes please please send them to me [email protected]
u will send for evita UTL?
and u have all the 5 files?
Hboot.img
Misc.img
Radio.img
Adsp.img
Wcnss.img
Can you send me these files please
I will also help you to flash them but please send them to me

adb no such file or directory

I am trying to replace my digitizer firmware so G01 will work in place of the 5185FC I replaced.
I was following a guide which told me to type this in:
$adb push 02-3011-4820.ekt /sdcard/
$adb push 02-3011-4820.ekt /sdcard/
$adb shell
$su
#touch_fw_update command -u /sdcard/02-3011-4820.ekt
Click to expand...
Click to collapse
every time I try to push the new touch firmware I get this
"cannot stat '02-3011-4820.ekt': No such file or directory"
adb detects my device, I havea all the naked drivers, Android studio and JDK 64bit installed.... what else do I need to do?
I'm just wondering what I can do to fix this and get my touchscreen working once and for all!
Thank you so much in advance

And you are in the folder where you have put the file you want to push?
Changed the directory in the command prompt to the correct folder?
edit: ok, if it's linux, not the command prompt, but the shell...

compact_wisdom said:
And you are in the folder where you have put the file you want to push?
Changed the directory in the command prompt to the correct folder?
edit: ok, if it's linux, not the command prompt, but the shell...
Click to expand...
Click to collapse
I put the file on the root if the sdcard. Or should i be putting it in the directory of minimaladb/fastboot?
How do i change the directory in the command prompt?
Im using Windows 7 by the way.

hkp2 said:
I put the file on the root if the sdcard. Or should i be putting it in the directory of minimaladb/fastboot?
How do i change the directory in the command prompt?
Im using Windows 7 by the way.
Click to expand...
Click to collapse
Here is the command you are using to push
Code:
adb push 02-3011-4820.ekt /sdcard/
Maybe try this instead .....
Code:
adb push 02-3011-4820.ekt /sdcard
You can change directory with this
Code:
cd
and you can list files once in adb shell like this
Code:
ls
Thx Josh

I wasn't sure what I should cd to. I also tried ls but wasn't sure what to do from there.
I did look at the tutorial for adb and pushed the file into /sdcard/ from my laptop. It seemed to be successful because this is the message I got
943 KB/s <32868 bytes in 0.034s>
Click to expand...
Click to collapse
I proceed to type in the following
adb shell
su
touch_fw_update command -u /sdcard/02-3011-4820.ekt
Click to expand...
Click to collapse
And that's where I'm stuck with a message
sh: touch_fw_update: not found
Click to expand...
Click to collapse
It seems like I'm at least moving forward a couple steps so that's good.

hkp2 said:
I wasn't sure what I should cd to. I also tried ls but wasn't sure what to do from there.
I did look at the tutorial for adb and pushed the file into /sdcard/ from my laptop. It seemed to be successful because this is the message I got
I proceed to type in the following
And that's where I'm stuck with a message
it seems like I'm at least moving forward a couple steps so that's good.
Click to expand...
Click to collapse
Where is this command coming from, a guide or somewhere like that ?
Code:
touch_fw_update command -u
Thx Josh

This guide
snart[dotcom]/replacing-tf300t-digitizer/
Click to expand...
Click to collapse
I'm getting the adb tutorial from here
http://forum.xda-developers.com/showthread.php?t=2266638
Click to expand...
Click to collapse

What kind of information can be restored after the factory reset?

Hello,
The question is pretty straightforward - is it possible to restore the data on the phone that had existed before the factory reset was made?
If I sell my phone on ebay can someone get any glimpse on what has been done with my phone?

e2com said:
The question is pretty straightforward - is it possible to restore the data on the phone that had existed before the factory reset was made?
Click to expand...
Click to collapse
It is still possible to recover much data after an factory reset. Unless you cleaned the drive properly. Fact is that there are user data still accessible on almost 40% of all phones bought at pawn shops.
To clean a drive you basically overwrite every single bit of the storage with an binary zero. This an very hard process to do manually therefore I would recommend using an data eraser tool such as:
Jihosoft Mobile Privacy Eraser - $49 /One-time
MobiKin Eraser for Android - $49 /One-time
Dr.Fone Data Eraser - $14.95 /Year or $19.95 /One-time
Or just use ADB to wipe all partitions you made changes to. As jwoegerbauer suggested.
e2com said:
If I sell my phone on ebay can someone get any glimpse on what has been done with my phone?
Click to expand...
Click to collapse
So short answer yes, it is very much likely that they can recover your data. Therefore I recommend wiping before selling it.

A sequence of 3 ADB commands is enough to unrecoverably wipe Android's user-data, provided the /data partition is mounted as RW
Code:
adb devices
adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=4096"

jwoegerbauer said:
A sequence of 3 ADB commands is enough to unrecoverably wipe Android's user-data, provided the /data partition is mounted as RW
Code:
adb devices
adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=4096"
Click to expand...
Click to collapse
I learned something new today.

jwoegerbauer said:
A sequence of 3 ADB commands is enough to unrecoverably wipe Android's user-data, provided the /data partition is mounted as RW
Code:
adb devices
adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/userdata bs=4096"
Click to expand...
Click to collapse
Hello,
when I run adb shell "dd if=/dev/null of=/dev/block/bootdevice/by-name/userdata bs=4096"
I get this:
dd: /dev/block/bootdevice/by-name/userdata: Permission denied
even though I run the command as sudo and enter my admin password. Any idea what I am doing wrong?

Are you sure that /data is mounted as RW?

TrulyPain said:
Are you sure that /data is mounted as RW?
Click to expand...
Click to collapse
no. How do I check it please?

e2com said:
no. How do I check it please?
Click to expand...
Click to collapse
It is quite different whether which device and android version you have. But usually, you write cat /proc/mounts in ADB. Then you shall see whether /data are mounted as RO or RW.

TrulyPain said:
It is quite different whether which device and android version you have. But usually, you write cat /proc/mounts in ADB. Then you shall see whether /data are mounted as RO or RW.
Click to expand...
Click to collapse
Okay, just ran your command and could not find /data at all.
I can see /proc /dev /sys /run but not /data
Maybe it has not been mounted at all?
Sorry, I am not very experienced with this but I am familiar with the terminal

How do I mount /data partition ?

android smartphones are encrypted by default. simply factory reset is enough nowadays to render userdata unrecoverable. on factory reset, the encryption key is securely deleted. there is no way to recover encryption key, therefore no way to decrypt data.