Related
is there a command in adb shell to remove a whole directory? i tried the rm command and it didnt work
try
Code:
rm -r /dir
you need to delete dirs with explicit recursion.
kendong2 said:
try
Code:
rm -r /dir
you need to delete dirs with explicit recursion.
Click to expand...
Click to collapse
thanks, ill give it a try
If there is nothing in the directory try...
rmdir nameofthedirectory
** sorry double post**
i didnt want to make a new thread for MY adb question, so i decided to post it here for anyone to help me figure it out. Just so you know adb was working fine and ok awhile ago.
Lately with adb ive been getting some weird early adb command errors.
this is the jist of what i get:
((Phone is connected to computer and USB debugging is on))
C:/Androidsdk/tools/adb devices
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
((then i try again))
C:/Androidsdk/tools/adb devices
adb server is out of date. killing...
* daemon started successfully *
list of devices attached
HT99******* device
It used to just give me my device number right after the command, i never used to get that adb server out of date thing. anyone know why i am getting this new line?
happens to me when using eclipse.
I think the ADB server out of date is because ADB has been running for a long time without anything using it.
and how do i fix this do you think?
re download the sdk? or what?
frostrunner said:
and how do i fix this do you think?
re download the sdk? or what?
Click to expand...
Click to collapse
I am having the same issue. I have SDK 1.5 and Eclipse on Win Vista. Anyone how to fix "adb server is out of date. killing..." issue?
I am using the PRS complete rooting guide. And when it tells me to type cat /sdcard/su > su, i am getting this error message - cat: can't open '/sdcard/su': No such file or directory.
Can anyone help with this?
Do you have su on your sdcard?
use unrevoked. one click root
just use the one click method by unrevoleved its easier
Su is not on the SD card. The sd card is a brand new PNY card. I have Su in the sdk/tools folder.
Then obviously, that command will not work. Use the unrevoked method if you are unsure what these commands do/how they work. Less headache on your end.
where is it located?
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
This is what it's asking me to do.
From PRS Complete Rooting Guide
Now type the following commands to make it persistent through reboot
Code:
adb shell
su
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su /* IF YOU GET AN ERROR HERE DO rm /system/xbin/su THEN REDO */
chmod 06755 su
k_flan said:
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
Click to expand...
Click to collapse
I don't know what that guide does, but it doesn't seem right --- it'll mess up the privs, that's why the old root was written as an update-payload.
It's redirected I/O since you can't copy across filesystem boundaries -- ie /sdcard to a different mountpoint.
So if I reboot my phone now, do you think I'll lose root and have to start over?
csills said:
So if I reboot my phone now, do you think I'll lose root and have to start over?
Click to expand...
Click to collapse
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to http://unrevoked.com/ and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
askwhy said:
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
Click to expand...
Click to collapse
AND - if you appreciate unREVoked's work - please donate. They do amazing work and they do it all for free! We're the lucky ones to have such [email protected] developers out there who do this kind of stuff so that we don't have to figure out the exact second to push in our SD cards, push files to the SD card, and then push them to the phone at exactly the right time...... just download, run, and you're done.
Just use the unrevoked 3 you will save plenty of pain and struggle
unrevoked3 worked! Thanks for the help guys.
No problem were glad to be of assistance
Generic Nvidia Tegra Secure Boot Key Dumper, v0.4
**************************************
YOU MUST GET ROOT BEFORE PROCESSING!!!
This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
**************************************
I am not sure it work for your devices or not, because I only get a SU660 device!
So , you must knew that P880 use a Secure Boot Key to encrypt its nflash communication, if you don't know the SBK, you can't use nvflash backup/restore your partitions.
I found that in the linux kernel, there is some protection that block the user try to read out SBK when the phone in "odm_production" status. So I designed a little software try to patch the phone RAM to bypass the protection.
This is a kernel patcher which will remove the protection when trying to read /sys/firmware/fuse/secure_boot_key
The dumper will patch the kernel in memory, and let you show the secure_boot_key.
Hope it work for all tegra devices.
Usage:
1. adb push dumpSBK /data/local/
2. adb shell
su
chmod 0777 /data/local/dumpSBK
/data/local/dumpSBK
After that, you can
4. cat /sys/firmware/fuse/secure_boot_key
dumpSBK will search the first 1MB physical address(which kernel will be there), and try to patch it.
Usage: dumpSBK [star_mem_addr in KB]
for example: dumpSBK 32
which will search the 32KB~1MB physical memory.
2012/12/31:
re-compile it with -static switch, so it can run on all android platform.
update instructions.
2013/01/01:
modify the program, and let you select which memory range to patch.
usage: dumpSBK [start_memory_addr] [end_memory_addr]
for example: dumpSBK 1 1024
which will search 1MB ~ 1024MB memory and try to patch the kernel.
2013/01/01:
v0.3 add more error detection in the file.
2013/01/06:
v0.4 wil search the first 1MB physical memory, you can specify the start_address , for example dumpSBK 32
and update the search pattern , it will fit for more compiler options.
2013/01/07:
Secure_Boot_Key Dumper for tegra2/tegra3 v0.1
1. adb push ss.ko /sdcard/
2. adb shell
su
cd /sdcard/
insmod ss.ko
dmesg
3. at the end of dmesg, you should see the secure_boot_key.....
2013/01/08:
v0.2 dump all known fuses.....
If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.
marsgod said:
If you get a error:
Kernel patching failed! Abort....
that means your device kernel has a differnt tegra source code, or compiled with a different compiler........
Please let me know which kernel source code and compiler / compile switch it used.
Click to expand...
Click to collapse
will it hard brick the phone???
razerblade17 said:
will it hard brick the phone???
Click to expand...
Click to collapse
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:
SimonTS said:
Do you want to try and find out? I certainly don't.
I like my phone and don't want to end up with an expensive paperweight instead :banghead:
Click to expand...
Click to collapse
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up
The Troll said:
i'd have tried if i didnt sell mine
plus this wont brick the device
nothing can since bootloader's lock so u practically cant mess up anything that matters for booting up
Click to expand...
Click to collapse
Yep, i think Troll isn't trolling us i would try it out ,but i'm waitin' for my LG, factory reset via recovery bricked it.
This is a temp memory only fix, after you reboot your phone, everything will restore to it's original status. So it WILL NOT brick your phone at all!
The patcher will patch a single byte in your phone RAM, it will not modify any bit in your NAND Flash.
C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
Click to expand...
Click to collapse
^ You guys have rooted phone and debugging turned on? maybe that's why these errors.
phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
C:\o4xr>adb push dumpSBK /data/local/
push: dumpSBK/Readme.txt -> /data/local/Readme.txt
failed to copy 'dumpSBK/Readme.txt' to '/data/local/Readme.txt': Permission deni
ed
Click to expand...
Click to collapse
So i put those files there with es file explorer and try to run second comand:
C:\o4xr>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
Click to expand...
Click to collapse
Who can explain why?
s7ar73r said:
phone rooted, recheked with root checker.
I have debuging mode one.
But i cant push files to /data/local/
So i put those files there with es file explorer and try to run second comand:
Who can explain why?
Click to expand...
Click to collapse
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*
k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
I get the this,too.
the v1 patch did not completely work.
The Troll said:
uhmm
as i seem to recall, the hello world rooting method *only known method* turns on access to that location..
thats where superuser and binaries are added
so if im correct u'd be able to push it if u follow the rooting method and adding the commands to the root.bat *or whatever its name it* that we run in pc by using notepad or anything..
so it should reroot and push ur desired file as well
*again, dun remember, been months but im sure hello world/backuptest thingy will be useful*
Click to expand...
Click to collapse
Its not the only known method... but now I don't have time, even to think... I just woke up and came to the computer.
You need to think widder
Gonna back to sleep :angel:
k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
En.... I think it is due to I compiled the dumpSBK with 4.1.2 android, so it will not work on a ICS rom... I will check it later...
s7ar73r said:
C:\adb>adb shell chmod 0777 /data/local/dumpSBK
Unable to chmod /data/local/dumpSBK: Operation not permitted
I got this
Click to expand...
Click to collapse
You MUST root your device.
then type
adb root
to get the adb rooted work.
Of couse, you must have your device USB debug ON.
please do all the steps the right way , starting with the OP instruction you the right way.
OP is assuming we got a "unsecure" booted device, which we have not exactly due to the locked bootloader.
so its pointless to write "root" instruction froms adb when the device is in secure mode. OP is now told and should update the instructions, thank you.
ignore all the "adb shell" instruction and log into the device with "adb shell" once only.
in that shell which is opened execute the "su", so you get a root # prompt.
then run instructions given and skip all "adb shell" infront.
thats it, good luck.
edit:
adb remount,adb root and running root commands only work on unsecure devices , we got ro.secure=1 here and adb not allowed to run root commands
i think it's better toroot Your 4X with Dexter http://forum.xda-developers.com/showpost.php?p=30574547&postcount=85 because it doesn't have any issues, for me with 1st root method for example titanium backup wasn't working.
@marsgod, yep - we don't have 4.1.2 but 4.0.3, but u can leave this version because we'll get 4.1.2 in january
k1337Ultra said:
Here is a log of what happened, after I ran the program on my 4X with 10H F/W:
Click to expand...
Click to collapse
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?
bullghost said:
[email protected]:/data/local # /data/local/dumpSBK
/data/local/dumpSBK
[1] + Stopped (signal) /data/local/dumpSBK
[email protected]:/data/local # cat /sys/firmware/fuse/secure_boot_key
cat /sys/firmware/fuse/secure_boot_key
[1] + Segmentation fault /data/local/dumpSBK
i have same result . segmentation fault
whats wrong?
Click to expand...
Click to collapse
after adb shell type su, u should have [email protected], not [email protected]
@edit so... anyone tested it in right way?
Code:
#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/
Over the last few months development on the LG L90 has made some great strides, up to the point where we can actually install roms! In order to do this, however, you'll need an unlocked bootloader.
The problem that arises is that there are different models of the L90, being the D405, the D405n, the D410 and the D415. For most of the models the unlock process is very similar, but for the D415 another method is needed.
This guide is aimed at explaining the entire unlock process in a complete and simple way, so even if you have no experience flashing custom recoveries or roms at all, you should still be able to follow this guide. If you run into problems, please just post a reply or send me a PM and I'll do my best to help you.
First of all I'd like to note that I did not develop any of the bin files or apks in this guide, I'm only collecting all the unlock methods in one place for easy reference. Therefore I am not responsible for you bricking your device or causing any kind of damage to it. You follow this guide AT YOUR OWN RISK! That being said, let's get to the unlocking!
What you'll need to unlock the bootloader
1. A rooted LG L90
You can root the phone by going to https://towelroot.com in your mobile browser and tapping the lambda sign. Save and install the apk (make sure unknown sources are enabled in "menu > general > security"). Google will warn you about the app, this is because of the exploit which will enable the root access. Execute the program and tap "make it ra1n", then install supersu from the play store. Open supersu and choose to rebuild the binaries. This will fail, but after a reboot supersu should be installed and working properly.
UPDATE: If towelroot doesn't work for you, you've probably got the L90 with an updated firmware. In that case you can follow this guide by @gdjindal to obtain root access. Afterwards you can follow the rest of this guide again.
2. Have adb installed.
just download the Android sdk and install it or, if you don't care about the SDK itself, the minimal adb from the bottom of this post (thanks to @shinobisoft for the upload). Now add the C:/path_to_the_sdk/sdk/platform-tools to your windows PATH variable (Windows 7: right click my computer > properties > advanced system settings > environment variables) or the foler in which adb.exe is located if you downloaded the minimal adb..
On your phone go to "menu > general > about phone > software information" and tap build version a few times untill it says you're a developer, then go to "menu > general > developer options" and enable usb debugging. Connect the phone with your PC and choose to connect in software mode and install the drivers and tools. When you get a message on your phone that your PC want to access usb debugging make sure you check the checkbox and accept. Now open a cmd prompt and type "adb devices" without the quotes. If it shows a series of letters and numbers followed by device, you're good to go. If it says unauthorized, you haven't accepted the prompt on your phone yet. If your device doesn't show up at all you haven't installed the drivers correctly.
3. Find out which device and software version you're running.
Go to menu > general > about phone > Hardware information for your Model number. Mine is LG-D405n, so my model is D405n.
Go to menu > general > about phone > Software information for your Software version. Mine is V10b-EUR-XX, so I've got version v10b.
4.1 If your model number is D405, D405n or D410, you'll need a modified aboot.bin to unlock the bootloader.
Go to the bottom of this post and download the file with your model and software version. I used the L90_D405n_v10b_hack.zip. Extract the aboot.bin in the zip file to a folder on your PC.
4.2 If your model number is D415, you'll need another method to unlock the bootloader, which is explained in this thread made by @aSuperSaiyanG0D.
Unlocking the bootloader on the D405, D405n and D410
1. Open a cmd window an CD to the folder where you've saved the aboot.bin you've downloaded in step 4.1
2. Execute the following commands:
Code:
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Right after the su command, supersu will give you a root request on your phone that you'll have to accept!
This will also make a backup of your current aboot partition as stockaboot.bin on your external SD card. If you don't have an external SD card, this won't work and you'll have to use /storage/emulated/0 (this is a zero, not the letter o) instead of /storage/external_SD/ like this:
Code:
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin 5429599
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
3. That's basicly it, you can now install a custom recovery. I suggest downloading the latest TWRP (2.8.0.0 right now) from @shoxxy's thread, which can be found here. Just use ROM Toolbox to install it, choose rom installer, press settings > flash image and select the TWRP image from @shoxxy's thread. Afterwards you can boot to recovery using ROM Toolbox, or by shutting down the phone, holding volume down and power untill the lg logo shows, then releasing and immediately pressing those buttons again. You should get a screen asking to perform a factory reset. Choose yes twice (don't worry, it wont actually perform the reset) and TWRP should boot up. Now you can create backups and install custom roms too!
If you're a fan of cyanogenmod, you should visit @Quarx's thread, which can be found here. His CM11 is already mostly functional (right now on some models the front camera doesn't work and the ir blaster doesn't have any software, but most other functions actually do work very well, while it is faster than LG stock and gives almost twice the battery life), so if you like CM it's a thread worth keeping an eye on.
Flashing back the stock rom (in case of a brick)
If you've bricked your device, or want to revert to stock for any reason, you can follow this guide made by @gdjindal.
Post reserved
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Gabe.INc said:
So, I did everything, but when I try to do the 4.2, I cant do it.. The reason why is because it says "No stat file"
Click to expand...
Click to collapse
If you have a problem with step 4.2 only, I assume you have a D415 and you should actually ask this question in the thread that step 4.2 links to. Or isn't that what you meant?
EDIT: please note that step 4.2 is for the D415 ONLY.
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Gabe.INc said:
Sorry, my bad, I though tha step 4.2 was the wole thing that comes next, my device is D405
Click to expand...
Click to collapse
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
SubliemeSiem said:
No sweat If you've completed step 4.1, just head to step 1 of the next section and you should be good.
Click to expand...
Click to collapse
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Gabe.INc said:
but thats the problem, I've donwloaded my file, and then, put it on a folder in my desktop.. Then what do I do?
Click to expand...
Click to collapse
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Mind that I've only tested this using the external SD, but it should work both ways.
Error 1
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Open a cmd screen (go to start > all programs > accessories > Command prompt) and from there run this:
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/external_SD/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/external_SD/stockaboot.bin
dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
if you use an external SD card. Else run
Code:
cd Desktop/Folder_you_put_the_aboot_in
adb push aboot.bin /storage/emulated/0/aboot.bin
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/storage/emulated/0/stockaboot.bin
dd if=/storage/emulated/0/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
It give me this error, in both external and internal storage
Click to expand...
Click to collapse
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
BTW: what's the output of
Code:
adb devices
?
SubliemeSiem said:
Gabe.INc said:
That is stange, never had that error myself. In that case I would try another way to put the aboot.bin on the root of the SD card (google drive for instance) and continue from the adb shell part..
Click to expand...
Click to collapse
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Gabe.INc said:
SubliemeSiem said:
Can't I just simply paste it on my SD card?
Edit: I think I found what my problem was, something in developer settings..
2nd Edit: Nop, it still gives the same read-only error..
3rd Edit: The output of adb devices is LGD410bc(..) Device
Click to expand...
Click to collapse
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
SubliemeSiem said:
Gabe.INc said:
Strange, but yes, you can simply paste it on your SD card and continue from the "adb shell" line. You can also try
Code:
adb shell sysrw
before the push command to mount the filesystem as RW. If you do this, it is recommended to use
Code:
adb shell sync
adb shell sysro
after the psuh command (so you'll mount the filesystem as RO again).
Click to expand...
Click to collapse
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Gabe.INc said:
It says, not found..
BTW: I flashed stock again..
Click to expand...
Click to collapse
Where did you get the not found message? And what do you mean you flashed stock again? If you couldn't execute the dd commands then your bootloader is still locked and all you've done so far is root the device..
UPDATE: I don't get a response, but it seems this user previously flashed the wrong aboot.bin (or did something else, unfortunately he's not being very clear on that) so please only follow this guide when you have a stock recovery + aboot partition. If you did try some things before, please flash the stock rom back first and then follow this guide.
Thats awesome! Thank you! :cyclops:
guilherme.fuzo said:
Thats awesome! Thank you! :cyclops:
Click to expand...
Click to collapse
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
SubliemeSiem said:
No problem! Just let me know if you run into any problems so I can update the guide accordingly (and hit the thanks button if it worked of course).
Click to expand...
Click to collapse
I found no problem, but anyway thanks dude! :laugh:
guilherme.fuzo said:
I found no problem, but anyway thanks dude! :laugh:
Click to expand...
Click to collapse
Then don't say thanks, but hit the thanks button on the first post!
Does anyone know where I can find step by step instructions for rooting my mini on a Mac? Online i've found very little info on rooting the HTC One Mini 2, and where I have found guides, they have been using a PC.
I would appreciate greatly if someone could direct me to a step by step guide for rooting the Mini 2 from scratch using a Mac, or can tell me how to do it, as I have very little experience in this and don't want to risk doing something wrong:/
Thanks, Tzveti.
tzveti said:
Does anyone know where I can find step by step instructions for rooting my mini on a Mac? Online i've found very little info on rooting the HTC One Mini 2, and where I have found guides, they have been using a PC.
I would appreciate greatly if someone could direct me to a step by step guide for rooting the Mini 2 from scratch using a Mac, or can tell me how to do it, as I have very little experience in this and don't want to risk doing something wrong:/
Thanks, Tzveti.
Click to expand...
Click to collapse
1-Download HTC drivers/root files Win/Mac unzip to downloads/HTCRootMac.
2-open terminal
3-type: (after connecting your phone, make sure is recognized)
cd downloads
cd HTCRootMac
chmod 755 * (this will change permitions)
(dot) ./adb-mac backup -apk -all -f backup.ab (this will backup your phone)
4- turn phone into bootloader mode
5- type in terminal and following htc dev instructions until get token
(dot) ./fastboot-mac oem get_identifier_token
6- paste Unlock_code.bin into downloads/HTCRootMac folder
7- terminal type
(dot) ./fastboot-mac flash unlocktoken Unlock_code.bin
8- check phone and follow instructions (choose yes, this will erase your phone)
8.1 finish setup and send super user to somewhere in phone or sdcard keep as .zip file
9- put phone back into bootloader (should say at the top "tempered / unlocked")
10- download TWRP and put same folder in mac (downloads/HTCRootMac)
11- terminal type:
(dot) ./fastboot-mac flash recovery twrp-2.8.1.0-20142812-memul.img
(dot) ./fastboot-mac erase cache
12-in phone try to enter recovery (you should get into TWRP
13- inside TWRP install super user
14- turn phone on and inside settings tick USB debugging
15- (dot) ./adb-mac restore backup.ab (this will restore your phone (optional))
DONE.
let us know how it go.
Oh my god thank you so much)) I'll try this tomorrow and hopefully it will go well, there aren't any chances of me hard bricking my phone in this procedure right?
Again thank you so much this is very useful
kativiti said:
1-Download HTC drivers/root files Win/Mac unzip to downloads/HTCRootMac.
2-open terminal
3-type: (after connecting your phone, make sure is recognized)
cd downloads
cd HTCRootMac
chmod 755 * (this will change permitions)
(dot) ./adb-mac backup -apk -all -f backup.ab (this will backup your phone)
4- turn phone into bootloader mode
5- type in terminal and following htc dev instructions until get token
(dot) ./fastboot-mac oem get_identifier_token
6- paste Unlock_code.bin into downloads/HTCRootMac folder
7- terminal type
(dot) ./fastboot-mac flash unlocktoken Unlock_code.bin
8- check phone and follow instructions (choose yes, this will erase your phone)
8.1 finish setup and send super user to phone
9- put phone back into bootloader (should say at the top "tempered / unlocked")
10- download TWRP and put same folder
11- terminal type:
(dot) ./fastboot-mac flash recovery twrp-2.8.1.0-20142812-memul.img
(dot) ./fastboot-mac erase cache
12-in phone try to enter recovery (you should get into TWRP
13- inside TWRP install super user
14- turn phone on and inside settings tick USB debugging
15- (dot) ./adb-mac restore backup.ab (this will restore your phone (optional))
DONE.
let us know how it go.
Click to expand...
Click to collapse
Should I unzip the SuperSU and TWRP files before placing them on my phone?
Also, I haven't yet done this step but when you say this: "8.1 finish setup and send super user to phone", where do I send this file? as later on I also notice that you mention "10- download TWRP and put same folder", which folder is this? Is it the same folder as the Super user has been sent to? And if so where is this folder?
Sorry for all the questions
tzveti said:
Should I unzip the SuperSU and TWRP files before placing them on my phone?
Also, I haven't yet done this step but when you say this: "8.1 finish setup and send super user to phone", where do I send this file? as later on I also notice that you mention "10- download TWRP and put same folder", which folder is this? Is it the same folder as the Super user has been sent to? And if so where is this folder?
Sorry for all the questions
Click to expand...
Click to collapse
keep super user as .zip. and put it anywhere in phone where you can find easily .you gonna use TWRP to install it.
10- will be same folder you been using in mac (downloads/HTCRootMac) where adb files are.
instructions updated for this...
I got this message after trying step 3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb: unable to connect for backup
tzveti said:
I got this message after trying step 3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb: unable to connect for backup
Click to expand...
Click to collapse
did you install htc drivers? is the phone showing/mounted?
I downloaded all the stuff in the link provided, i'm not sure if there are other HTC drivers I should have downloaded.
Whether or not the phone is mounted i'm not sure of, as I can access it through Android File Transfer and can move files around, however it does not show as a device on my finder window.
tzveti said:
I downloaded all the stuff in the link provided, i'm not sure if there are other HTC drivers I should have downloaded.
Whether or not the phone is mounted i'm not sure of, as I can access it through Android File Transfer and can move files around, however it does not show as a device on my finder window.
Click to expand...
Click to collapse
install htc sync manager for latest drivers
kativiti said:
install htc sync manager for latest drivers
Click to expand...
Click to collapse
I now get this message:
adb server is out of date. killing...
* daemon started successfully *
adb: unable to connect for backup
In addition, now that I have installed HTC Sync Manager I can no longer use Android File Transfer, I'm not sure whether this is causing some kind of problem.
kativiti said:
install htc sync manager for latest drivers
Click to expand...
Click to collapse
I now get this message:
adb server is out of date. killing...
* daemon started successfully *
adb: unable to connect for backup
In addition, now that I have installed HTC Sync Manager I can no longer use Android File Transfer, I'm not sure whether this is causing some kind of problem.
tzveti said:
I now get this message:
adb server is out of date. killing...
* daemon started successfully *
adb: unable to connect for backup
In addition, now that I have installed HTC Sync Manager I can no longer use Android File Transfer, I'm not sure whether this is causing some kind of problem.
Click to expand...
Click to collapse
did you run this command " chmod 755 * " to change permitions?
kativiti said:
did you run this command " chmod 755 * " to change permitions?
Click to expand...
Click to collapse
Yes, however when I write the command nothing happens. When using the android file transfer application some text had appeared though.
tzveti said:
Yes, however when I write the command nothing happens. When using the android file transfer application some text had appeared though.
Click to expand...
Click to collapse
you can skip the backup. or do a backup using htc manager.
you must use a OTG cable (original htc cable)
I'm backing up the phone now using manager, and I am using the original cable however it is still not working:/
Done, fantastic, thanks a bunch mate
tzveti said:
Done, fantastic, thanks a bunch mate
Click to expand...
Click to collapse
glad i could help. change thread title to "Step by step MAC Rooting instructions" so others can find it too
kativiti said:
glad i could help. change thread title to "Step by step MAC Rooting instructions" so others can find it too
Click to expand...
Click to collapse
Thanks for the clear instructions,
i also have a question abut HTC ONE REMIX can you help me change modelid: 0P8B10000 to any european MID ?