Develop Bugs

[GUIDE] Using ADB & FASTBOOT in OSX / Mac

Hi,
I thought I'd add this here because I've recently starting using OSX after building my own hackintosh out of PC parts. I got very fed up with Windows and the need for drivers all over the shop so I'm moved over now.
I've also just got into flashing my HTC Desire and it was made very easy by lots of the guys here. One thing that will always be useful when rooting and flashing your phone is ADB. There are lots of guides out there for ADB on Windows but I wanted to run in natively in OSX.
After a lot of research and a few failed attempts .... I've now worked out how to run ADB in OSX.
What you will need:
A Mac
USB cable
Android SDK for OSX- http://developer.android.com/sdk/index.html
At the time of writing this the version was "android-sdk_r08-mac_86" so please have a look at the above link and let me know if you can't find that same version.
So download the zip file and I would extract it to a folder where you are happy to keep it such as within your user home folder i.e. Macintosh HD/Users/{Your User Name} and for my mac it is Users/siedkins which is how I have my OSX set up.
Then open then still in Finder, open "android-sdk-mac_86" then "tools".
Now launch Terminal - ⌘ + space then type Terminal or Applications>Utilities>Terminal
Now drag and drop the file called "android" in the "tools" folder into your terminal window and you should see something like:
/Users/siedkins/android-sdk-mac_86/tools/android
Then hit enter - this should load Android SDK
Next go to Available Packages on the left and Android Repository > Android SDK Platform-tools, revision 1 -tick the box and hit "Install Selected"
It should download and install the Platform Tools which includes ADB !!!!
Now quit Android SDK after it has downloaded and go back into Finder. Now you should see a new folder "platform-tools" in the "android-sdk-mac_86" folder. Open that and you can now see a file called adb.
Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it.
Go back to your Terminal window and type (or copy & paste):
Code:
cd ~
The screen should then look like
NAME_OF_YOUR_MACHINE:~ USERNAME$
For me I have:
Mac-Pro:~ siedkins$
Next, type
Code:
touch .bash_profile
to create your new bash / path file
Next, type
Code:
open -e .bash_profile
to open it in TextEdit.
Now into Text Edit please copy:
Code:
export PATH=${PATH}:
Then go into Finder and navigate your your "android-sdk-mac_86" folder. Then click on the "platform-tools" folder and drag and drop this into TextEdit at the end of the code above that you copied. Mine looks like:
export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools/
Yours should look like:
export PATH=${PATH}:insert your path to the "platform-tools" folder in your Android SDK here
All you need is that one line. Then Save and exit TextEdit and then very importantly QUIT TERMINAL.
***** If you have issues being able to save the file at all then please jump to the bottom of the post*****
Now ........ to turn on USB Debugging in your handset Settings > Applications > Development > USB Debugging - ticked and also go to Settings > Connect to PC > Default connection type > Charge Only and also UNTICK "Ask me ..." there also. You can always go back here and change these settings back.
Now plug in your phone to a USB port. I noticed that if I plugged my phone into one of the standard USB ports on the front of my machine I couldn't see the phone further down the line and if I plugged it into a powered USB port on the front (I have an "akasa AK-ICR-08" which has a powered connector behind the 5 USB ports. But you guys will probably be using a MacBook or MacPro and there shouldn't be any issues with the power to your USB ports.
Now to launch ADB - re-open terminal (remember that you had quit it - very important!) then type in:
Code:
adb devices
And you should see:
List of devices attached
HXXXXXXXXXX device
where XXXXXXXX is your unique phone ID.
Now you can run all of your favourite ADB commands straight by typing:
adb shell
etc straight into Terminal. I won't go into that here as there are plenty of guides about what to do with ADB once it's installed!
Now you have ADB setup on your Mac and can run it without the need for installing HTC Sync - un-installing it - loading some modified drivers over the top !!!!
It all just works !!!!!!
Please drop me a line if you have any queries about this !
******************
If you are have user account issues such as Terminal or TextEdit says that you can't do anything then try adding "sudo" to the front of your terminal command as this will allow you to execute the account as a superuser or root user for OSX! ROOT!!! Note that you will have to enter your password to enable the superuser access rights and you won't see anything as you type in your password.
i.e. try:
Code:
sudo touch .bash_profile
then
Code:
sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit .bash_profile
(slight change in the coding here to ensure that TextEdit opens
Or you could do:
Code:
sudo pico .bash_profile
This will open up the Pico text editor instead of TextEdit. Here you will have to type out all of the text then you press "ctrl+x" to exit and then you can save on the next screen. To check that has worked you can then open the file in terminal again and check it with the normal command:
Code:
open -e .bash_profile
******************
Please see post #37 for How To Use ADB Over WIRELESS !!!!
************************************************************************
EDIT - 27th JAN 2010
FastBoot
I've now found you all a precompiled version of Fast Boot:
http://developer.htc.com/adp.html
Please download and unzip the precompiled version for OSX to your "SDK/platform-tools" folder.
Rename the unzipped file from "fastboot-mac" just to "fastboot". You need to fix the permissions of the fastboot file using CHMOD in Terminal.
In Terminal navigate to your "SDK/platform-tools" folder and then type:
Code:
ls
You should see all of the files in your "platform-tools" folder such as adb, aapt, fastboot, etc.
Then type:
Code:
chmod 777 fastboot
PLEASE NOTE THAT I AM ASSUMING THAT YOU HAVE CHANGED THE FILE NAME ABOVE !
Now with the permissions fixed you should be able to run fastboot.
Connect your phone via USB and set to "charging only". Then turn off your phone and leave the USB in. Then hold the back key and then turn your phone on again. You will have a white screen with 3 skateboarding androids on.
Now in Terminal type:
Code:
fastboot devices
And you should see your unqiue phone ID! (Note that you have to be at that white screen with the skateboarders for the "fastboot devices" code to run!
Now you have a fully working fastboot !!!
Sorry this explanation is a bit short - I did write out a longer one but my browser crashed and I lost it all. However if you cannot follow the above then I think it's maybe best that you don't use fastboot as you could seriously brick your phone.
NOTE - I HAVE NEVER USED FASTBOOT TO FLASH A RADIO OR PHONE SO I PROBABLY WON'T BE ABLE TO HELP IF YOU GET ERRORS IN USING FASTBOOT OR FLASHING YOUR DEVICE ! The above information is how to shortcut the navigation to the folder. Please don't blame me if you break the recovery image of your phone!

Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
which last step ?

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
What version of MacOS? Also are you sure your device is properly rooted? I'm assuming you are getting the error when typing "adb devices"?
EDIT: That's what I get for being distracted while typing this.. ;-)

The easiest way to get the sdk is by using homebrew, which is an amazingly useful tool. https://github.com/mxcl/homebrew
Code:
brew install android-sdk
It doesn't add adb to your path however, you have to do that manually by adding /usr/local/Cellar/android-sdk/r8/platform-tools to your path.
Hope that makes it a little bit easier.

I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices

Thanks for the walk through
This work great. I put the the SDK folder on the root of Macintosh HD and renamed it to AndroidSDK. Then in the .bash_profile my path was /AndroidSDK/platform-tools/ . I then made a backup of my SD card with adb pull from /mnt/sdcard to my local machine.

mun-key said:
I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices
Click to expand...
Click to collapse
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.

It doesn't even have to be this complicated. Download the sdk, whatever files you want to push to your phone put it in the same folder. Then do the commands (./adb push). Simple.

Great and easy tutorial! Got it working in 5min ^_^

madj42 said:
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.
Click to expand...
Click to collapse
Ok - that makes sense now. And reading Krisrk's reply, that's exactly how I did it.
On my device I only needed to push a single file. Don't really need adb anymore. Your post was like 12-hours too late for me though. I spent 3 hours trying to figure out why it wouldn't work, then saw the ./ in a youtube video. After that I was rooted with a new rom in minutes
thanks for all the great info guys

Just wanted to thank you! I already had ADB working on my Mac OSX but didn't have the "environment variables" in the .bash_profile. So now I can just use adb commands directly without going into the finder and find the adb!
Also, kudos for the very detailed guide with your own examples, that reads very well!

Thanks for the comments guys.
I know that you can navigate to the SDK folder and just run it from there but I thought that people might like the above guide to do the shortcut once and then never have to jump around folders again in terminal which is a bit of a pain. Plus my method removes the need for the "./" prefix.
anyways I'm easy I'm sure that everyone will have their own preferred method if you already use adb on OSX

i cannot get beyond the command:
touch .bash_profile
the terminal returns permission denied. what do i need to add or what am i doing wrong?

What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?

Thanks for this!!!!!
Nobody ever shows macs love.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

siedkins said:
What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?
Click to expand...
Click to collapse
it popped up and asked my password, then it said i entered the wrong one and i never was asked this again. this is incredibly frustrating as i cannot even get it to work in windows
edit: ok got to the part where i bring up text edit, but it will not let me save. states i do not have permission to save. is there a way i can turn off this password crap for the time being? all i want to do is push files to my phone, i can't even get this far

Ok...
I'm trying not to look stupid, but for gods sake, im stuck at the first command. I copy paste cd~ and nothing happens. press enter nothing. I've been reading up on terminal and i still feel quite stupid considering how im stuck on step one
edit: got it! I got lost going back into the same terminal and not closing the android sdk window. there fore I was still in the sdk and not telling the computer anything. a dur. Opening a new terminal and doing all of the steps did the trick. Thanks for this btw!

thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!

monstereo said:
thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!
Click to expand...
Click to collapse
Hey just a random note, nice prof pic stig ftw

[ROOT]How to Root KVT49L.D85110r and Install TWRP. My experience

I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
First of all thanks to all amazing people on this forum ( thecubed,777jon,Dees_Troy, chainfire, supernoman, crashfocus, etc)
This is not my work . It is a compilation of what it worked for me from the work made by others. It is directly toward newbie users.
Instructions
1- Make sure you install LG G3 drivers in your computer( you can get them attached on this thread). Connect phone to the PC using USB cable. Make sure the phone is recognized when you plug it in with the usb cable
Also phone shall be connected as Media device (MTP), if it is in Charge Phone change it to MTP.
Scroll down this post. You will find the correct usb drivers attached. Install them in your pc.
2- Enable Developer options in your phone on Setting > General> About phone > Software information > and click seven times Build number until it enables it
3- Enable USB debugging on your LG G3 from your phones Settings > Developer options > tick ‘USB debugging’ check box. A window should pop up in your phone display to allow USB debugging. Select Allways Allow from This Computer and hit OK.
It will also be convenient to Enable installation of apps from Unknown Sources: Open phone’s Settings » select Security » Tick the “Unknown sources” check box (under Device administration section)
4- Download and unzip
- Pupledrake-Lite at http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R03.tar.gz Thanks to Codefi.re
- Download and unzip the attached ADB LOCAL READY with TWRP recovery.img
Thanks to @Dees_Troy & TeamWin - for TWRP Touch recovery
ATTACHMENT IS HERE- JUST CLICK HERE
5- Download -Latest SuperSu at http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip Thanks to Chainfire
6- Transfer UPDATE-SuperSU-v2.40.zip to the internal sdcard
7- Open Purpledrake-Lite and Run purpledrake_windows.bat. It should detect your devices if it is not, you need to check if the drivers were installed properly and unplug-plug back your phone.
Hit Enter as instructed on the computer screen until it gains temporary root.
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD.
Hit Ctrl+C to exit to use adb.
This process takes a few seconds and The phone start on download mode and it will stay on it.
8- Open ADB LOCAL READY folder you downloaded and hit Start Here.bat
Type "adb devices" to ensure that your phone is connected and it accept adb commands . On list of devices attached it should show LGD851........
Unplug it and plug it back if it is not .
NOTE: SOME PEEPS HAVE REPORTED PROBLEM WITH ADB NOT WORKING PROPERLY ON USB 3.0 PORTS. PLEASE USE USB 2.0 PORTS
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
Note: you may need to push it a few times if you do not find the recovery file on the /temp folder when you do step 12.
Some members stated that they need to push it ..5 times.
rubbamade tip
" This does work. If after you do the "adb push....", Hit the up key on your keyboard. What you just typed " adb push...." will appear again. Hit enter. It will "push" again. Hit up again. Hit enter. Do this at least 5 times. Now proceed with next step "adb shell"..... Should work now"
For some reason others user needed to push it more than 5 times, i assume that it is due to the file size of the image and your operating system and pc settings(i used win7). It is recommended to verify if it was pushed on step 12.
10- Type "adb shell" and it should go to shell command $
11- Then type "/temp/fakesu". This will put you in a superuser shell on your device. It should show su command line # .
12- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
14- Type type "reboot recovery" It should boot onto TWRP Touch recovery. it could take a few but it should
15- Once in TWRP, select install,go to the SD card directory, select UPDATE-SuperSU-v2.40.zip and install it. Reboot the phone once complete. Do not panic, it should take a while to cook and update applications, but it will, be patient.
16- Your device is rooted and with TWRP custom recovery. IF you do not see SuperSu in your application drawer, do not panic, just install it from the Play Store.
17- Now you are ready to install custom Roms, any application that requires root, or enjoy root features.
Quick References
How to Boot into TWRP(Recovery Mode)
1.Turn off your phone
2.Now, press and hold Power and Volume down buttons at the same time.
3.When the LG logo appears, release the keys.
4.Immediately press Power and Volume Down buttons again until the Hard Reset menu will be displayed.
5.Press volume down to Select "YES" on reset data. Do not panic, it will not . Select "yes" again . It will boot into TWRP recovery mode.
If you do not like hardware method you can use Quickboot or TWRP Manager applications from the Play store
How to Boot LG G3 Download Mode
-Disconnect your phone from PC.
-Power off your G3 and wait 4-5 seconds after lights go off.
-Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable
If you get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error..on purpledrake temproot step 7.
Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running
Disclaimer: It worked for me, but I am not responsible for any damages to your phone.

Your experience is very interesting vcurbel!
I was under the impression there was no way to root untouched stock 10R.
It would appear you have found a way! :good: Thanks for your contribution.
I am curious if anyone else has replicated this?

thank you so much had a little trouble but successfully rooted my device

Where was this guide yesterday?
Last week I just thought rooting build R was impossible as of yet, got fed up, and 5 minutes ago ran the LG Update tool to revert my phone back to stock/ Build C and root that way.

vcurbel said:
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
Click to expand...
Click to collapse
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!

NO GO
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
AT THIS POINT I AM GETTING "NOT FOUND". DID THE STEPS ABOVE SEVERAL TIMES.
I saw 8xxxkb data pushed after 'push'
==========================================================================================
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9716 KB/s (11245568 bytes in 1.130s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
#
=========================================================================================

sharkoparko said:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
/temp/fakesu: Is: not found
#
=========================================================================================
Click to expand...
Click to collapse
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13

vcurbel said:
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
Click to expand...
Click to collapse
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
===================================================================================
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
===============================================================================================
DO I NEED TO RE-ROOT?

sharkoparko said:
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....
DO I NEED TO RE-ROOT?
Click to expand...
Click to collapse
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

vcurbel said:
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).

sharkoparko said:
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
Click to expand...
Click to collapse
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app

Just got home with a Craigslist buy.
rooted in 15min thanks vcurbel !
now to find CM12 for this baby

hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated

tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app

all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
vcurbel said:
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator

tomez206 said:
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
Click to expand...
Click to collapse
It seems your windows os is missing the default mintty.exe terminal...
Google it and you will find a solution to manually install it.
Or use other pc
Sent from my LG-D851 using XDA Free mobile app

tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
If I recall if the PD batch file/script is closing on you or giving you trouble, then you can run the script manually.
See link below to thecubed PD lite thread and read the 5th grey portion down of the OP, it is titled:
"But, what if I don't want to run your script to root?"
If you must use command line because the PD batch file/script is closing immediately just be sure to STOP after gaining temporary root!
From OP step 7:
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD. [/FONT]

lagvoid said:
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
Click to expand...
Click to collapse
Hello,
I am also having the same issue. I tried the above steps a couple times and am not sure if I am doing something wrong (more than likely I am). What did you mean by repush recovery?

Try step 9 again
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds

vcurbel said:
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9682 KB/s (11245568 bytes in 1.134s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
# dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/temp/recovery.img: cannot open for read: No such file or directory
#
--------------------------------------------------------------------------------
Yes, The phone is recognized and the file as you see was pushed (see script above). I think there is some issue with this method, as other people are reporting problems following the procedure in post #1??!! I guess it work for some and it does not for others.

Razer Phone with no OS system

Hi
i wasn't able to make this a thread but thought i would try and give a hand to people who accidentally wipe their razer phone of any OS whilst trying to root
If you have got no OS you will need to switch your phone into (download mode) for the following operations.
To get to download mode, turn off device and hold volume down button and download mode will load with razer symbol, (download mode will be stated in top left corner)
You will need to have ADB and Fastboot pre installed on your PC/Mac before starting this procedure
You will need a USB C cable to connect your device to your PC/Mac
Your BOOTLOADER should be unlocked, if you have wiped your phone of an OS, you most likely have it unlocked already as you were trying to Root your phone!
You will need to obtain the Stock firmware from the Razer website, getting it from the Razer website will stop you from accidentally downloading a corrupt file.
Once file is downloaded extract the .zip file and locate the (Windows) flash_all.bat, (mac) flash_all.sh
Open the flash_all.sh or flash_all.bat as a text format, from there you can see what files will be loaded to your razor phone.
You will need to delete the end of each command line for example: ${FASTBOOT_CMD} flash partition:0 gpt_both0.bin (this is the command line in original text format), Now delete the end of the command line (gpt_both0.bin), your new line should read ${FASTBOOT_CMD} flash partition:0, after drag and drop the file (gpt_both0.bin) from the original folder into the text editor, this will apply the address for the file and update your command line.
Once you have edited each following command line, with what it states at the end of each command line, save the document to original folder.
Open up terminal or CMD (CMD run as administrator), once loaded type the command line; adb
This will allow the ADB to run in the terminal
Now check that your device is connected to your PC/Mac, type the command line; adb devices
This should show you a ID number for your phone and what state it is in.
Now drag and drop the file flash_all.sh (mac) or flash_all.bat (windows), this needs to be your edited version, from you original folder and drop into your terminal or CMD page. Now hit enter
This will start the process to re-loading your stock firmware onto your phone.
Wait until the end of the process is complete, after your phone should reboot and load to the phones guide of setting up a new phone
If this has not worked then try the process again or check that your bootloader is unlocked and try again.
After all is good you can re-lock your bootloader by putting your device into (download mode) and typing the command line; fastboot flashing lock
When the bootloader page loads click on yes by using the volume buttons and power button for accepting
Now your device should reboot to working order with stock firmware!
This is my first time trying this so if i have missed stuff out please forgive me and let me know and i will update.
I hope this helps you into getting your razer phone back to life

You. Are. A. Life. Saver.

Isn't it easier to just type "flash_all.bat" (without quotes) directly???
Just use cd.. to go back to a previous folder or type the name of the folder that you want to access directly on CMD, for example, asuming that your OS folder is directly placed on "C" and the name of the folder is RAZER, just type:
cd..
cd..
cd RAZER
flash_all.bat
All the instructions can be found directly on the official Razer site: https://developer.razer.com/razer-p...885.617132994.1525376764-984967671.1524497635
Thank you tho.

Jonlines94 said:
Hi
i wasn't able to make this a thread but thought i would try and give a hand to people who accidentally wipe their razer phone of any OS whilst trying to root
If you have got no OS you will need to switch your phone into (download mode) for the following operations.
To get to download mode, turn off device and hold volume down button and download mode will load with razer symbol, (download mode will be stated in top left corner)
You will need to have ADB and Fastboot pre installed on your PC/Mac before starting this procedure
You will need a USB C cable to connect your device to your PC/Mac
Your BOOTLOADER should be unlocked, if you have wiped your phone of an OS, you most likely have it unlocked already as you were trying to Root your phone!
You will need to obtain the Stock firmware from the Razer website, getting it from the Razer website will stop you from accidentally downloading a corrupt file.
Once file is downloaded extract the .zip file and locate the (Windows) flash_all.bat, (mac) flash_all.sh
Open the flash_all.sh or flash_all.bat as a text format, from there you can see what files will be loaded to your razor phone.
You will need to delete the end of each command line for example: ${FASTBOOT_CMD} flash partition:0 gpt_both0.bin (this is the command line in original text format), Now delete the end of the command line (gpt_both0.bin), your new line should read ${FASTBOOT_CMD} flash partition:0, after drag and drop the file (gpt_both0.bin) from the original folder into the text editor, this will apply the address for the file and update your command line.
Once you have edited each following command line, with what it states at the end of each command line, save the document to original folder.
Open up terminal or CMD (CMD run as administrator), once loaded type the command line; adb
This will allow the ADB to run in the terminal
Now check that your device is connected to your PC/Mac, type the command line; adb devices
This should show you a ID number for your phone and what state it is in.
Now drag and drop the file flash_all.sh (mac) or flash_all.bat (windows), this needs to be your edited version, from you original folder and drop into your terminal or CMD page. Now hit enter
This will start the process to re-loading your stock firmware onto your phone.
Wait until the end of the process is complete, after your phone should reboot and load to the phones guide of setting up a new phone
If this has not worked then try the process again or check that your bootloader is unlocked and try again.
After all is good you can re-lock your bootloader by putting your device into (download mode) and typing the command line; fastboot flashing lock
When the bootloader page loads click on yes by using the volume buttons and power button for accepting
Now your device should reboot to working order with stock firmware!
This is my first time trying this so if i have missed stuff out please forgive me and let me know and i will update.
I hope this helps you into getting your razer phone back to life
Click to expand...
Click to collapse
my phone is just stuck in the green and white loading screen and it wont get past anything i can do

Djcall11 said:
my phone is just stuck in the green and white loading screen and it wont get past anything i can do
Click to expand...
Click to collapse
Hi have you managed to find a way to resolve your issue, i have been on the forum for a long while so sorry for late replies

Jonlines94 said:
Hi have you managed to find a way to resolve your issue, i have been on the forum for a long while so sorry for late replies
Click to expand...
Click to collapse
you have to reinstall the image add me on discord #7136

My guy!
You saved another Razer Phone with this post, just thought I should let ya know. much appreciated, man!

Doesn't work
I think this is really good and all, but it doesn't work. You suggest removing the extensions such as the gpt_both0.bin and to drag the file itself into the text editor. This doesn't work at all, all it does is open the gtp_both0.bin as a text file as opposed to doing whatever it was you were doing. Am I doing something wrong?
I've tried launching the bat file with all the img and bin files in the ADB folder so that I can just double press the flash_all.bat file, but the response to that is that in the CMD it says that over majority of the things have failed with the message "FAILED (remote: 'Flashing is not allowed for Critical Partitions')".
The only ones that do work are the flash system_b system_other.img, yet system_a system.img don't.

People says that if u want to enter Download mode just hold voulme down and plug the cable , but mine goes direct to bootloader page, phone is not working , brick and says your phone is corrupt

Yahyoo said:
People says that if u want to enter Download mode just hold voulme down and plug the cable , but mine goes direct to bootloader page, phone is not working , brick and says your phone is corrupt
Click to expand...
Click to collapse
HEllo I have a problem I install the firmware from razer to fix my phone but it says the file is corrupted

ADB no longer working

I have the latest Google driver on Windows 10 Pro. I have the latest 29.0.6 platform tools. I open a cmd prompt with admin privileges in platform tools and run "adb devices" and I get an error that I have attached. I have uninstalled and reinstalled Google driver to no avail. I have downloaded the platform tools again to make sure it was not corrupt, that didn't help. Afer I connect to the phone with usb debugging turned on it does not ask me if I want to trust the fingerprint of the computer. Can anyone give me some help? Thank you.

first attempt
Holysmoke99 said:
I have the latest Google driver on Windows 10 Pro. I have the latest 29.0.6 platform tools. I open a cmd prompt with admin privileges in platform tools and run "adb devices" and I get an error that I have attached. I have uninstalled and reinstalled Google driver to no avail. I have downloaded the platform tools again to make sure it was not corrupt, that didn't help. Afer I connect to the phone with usb debugging turned on it does not ask me if I want to trust the fingerprint of the computer. Can anyone give me some help? Thank you.
Click to expand...
Click to collapse
Download the latest:
https://developer.android.com/studio/releases/platform-tools
Unzip in a dir.
Copy following files to test dir:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Create one .bat file in the same 'test' dir:
adbreboot.bat:
@Echo off
set PATH=%CD%;%PATH%;
adb reboot
save it .... connect your device ... and run it (if necessary with admin privileges)
Good luck

Thanks for the advice but nothing happened.
I attached the folder contents. That is correct?

second attempt
Holysmoke99 said:
Thanks for the advice but nothing happened.
I attached the folder contents. That is correct?
Click to expand...
Click to collapse
Download and extract:
https://www.uwe-sieber.de/files/devicecleanupcmd.zip
On a windows X64 machine:
copy DeviceCleanupCmd.exe from extracted x64 folder to your previous test folder (with adb.exe, AdbWinApi.dll, etc...)
set the properties of DeviceCleanupCmd.exe for all users to run as administrator
create 2 .bat files:
DeviceCleanupCmdLoad.bat:
@Echo off
set PATH=%CD%;%PATH%;
DeviceCleanupCmd.exe * -t
PAUSE
DeviceCleanupCmdRemove.bat:
@Echo off
set PATH=%CD%;%PATH%;
DeviceCleanupCmd.exe * -s
PAUSE
Run the 2 . bat files (don't connect your device yet !)
Follow the instructions on the messages: ex: 'press any key to close': press any key, etc...
After that:
1. connect your device and run adbreboot.bat... see what happens
2. if no luck, run DeviceCleanupCmdLoad.bat and DeviceCleanupCmdRemove.bat again : REBOOT your windows, connect your device and run adbreboot.bat... see what happens
Good luck

It still did not work. Thanks again.

third attempt
Holysmoke99 said:
It still did not work. Thanks again.
Click to expand...
Click to collapse
- Disconnect USB between PC and device
- On device use "Revoke USB debugging authorizations" in "Developer Options"
- Reboot device
- Reconnect the device to the PC
- You should see now: the fingerprint of the computer ... allow it!
- run adbreboot.bat... see what happens

Thanks again, I have tried to revoke authorizations all day to no avail. I tried all the steps above and added revoking but it still won't give me option to trust fingerprint.

Holysmoke99 said:
Thanks again, I have tried to revoke authorizations all day to no avail. I tried all the steps above and added revoking but it still won't give me option to trust fingerprint.
Click to expand...
Click to collapse
last attempt
fully uninstall magisk (root)
update to the latest OTA firmware of google....
revoke the authorizations again

I had altered boot.img to obtain root. This morning the phone was running very slow so I did a factory reset. I updated to the latest OTA. Is magisk still on the phone?

After installing 15 seconds ADB Installer v1.4.3 your batch file worked and brought up the prompt to accept fingerprint!!!!!!!!! Thanks so much for taking the time to help me!

Holysmoke99 said:
I had altered boot.img to obtain root. This morning the phone was running very slow so I did a factory reset. I updated to the latest OTA. Is magisk still on the phone?
Click to expand...
Click to collapse
I always complete remove magisk before installing the latest OTA ... just in case

biontx said:
I always complete remove magisk before installing the latest OTA ... just in case
Click to expand...
Click to collapse
do you have to alter boot.img each time you install OTA to keep root?

Holysmoke99 said:
do you have to alter boot.img each time you install OTA to keep root?
Click to expand...
Click to collapse
Each time before I install an OTA I remove root and magisk
Download the latest factory image for you device:
https://developers.google.com/android/images#bonito
Unzip it and copy boot.img to a dir on your device
Reinstall magisk apk with the permissions (my favorite: Magisk v20.4: MagiskManager-v7.5.1.apk)
https://github.com/topjohnwu/Magisk
Patch your boot.img with MagiskManager-v7.5.1.apk
Copy your magisk patched . img to your computer to a dir with: adb.exe; AdbWinApi.dll;AdbWinUsbApi.dll;fastboot.exe
Create 2 .bat files:
0001fastbootmagicpatched.bat:
@Echo off
set PATH=%CD%;%PATH%;
fastboot boot <FullPathTo your magisk patched img file>\magiskpatched.img
example:
fastboot boot D:\PROJECTS\NOUGAT\PIXEL3A\magisk\20200405Stable\magiskpatchedboot\magiskpatched.img
0002fastbootflashbootmagicpatched.bat:
@Echo off
set PATH=%CD%;%PATH%;
fastboot flash boot <FullPathTo your magisk patched img file>\magiskpatched.img
example:
fastboot flash boot D:\PROJECTS\NOUGAT\PIXEL3A\magisk\20200405Stable\magiskpatchedboot\magiskpatched.img
Put your device into bootloader.
Connect your device and run 0001fastbootmagicpatched.bat
Disconnect your device.
After a full start of your device, don't start any other app... put your device into bootloader again.
Connect your device and run 0002fastbootflashbootmagicpatched.bat
After de cmd window ends on your computer, press start on your device
Once fully started, all should be well on your device.
Start magisk app and adapt to your needs

System Power app
@Holysmoke99
System Power app (see attachment): could you test this app please:
Preview: see pictures in attachment.
Made for android 10 or higher.
Root is needed.
Contains a tile to be added in your quick settings: makes it more easy to take a screenshot.
Contains the following functions:
- Power off
- Restart
- Recovery
- Bootloader
- Torch (toggle torch: added v 3.1 b 30013)
- Screenshot
- Screen off
Any comments appreciated

How To Guide How to set up adb and fastboot on a Mac

Hi guys,
This is a tutorial meant to show you how to set up adb and fastboot to be used on a Mac running Catalina or newer OS.
Requirements:
platform-tools from Google.
a Mac (duh) running Catalina or newer OS. Mac not included with this tutorial.
Sublime Text.
There are other ways to achieve the same thing (using Terminal commands), I just like this better cause it's more user friendly, and this way you also get a pretty awesome text editor which you can use in the future. If you already know how to do it from Terminal, you can skip this step and the coresponding steps below.
How to:
Press "Shift + CMD + ." to toggle on/off hidden files. To hide them again, just press the same key combination again.
The "." symbol is important. It's not punctuation. Not that punctuation isn't important, but this is part of the key combination to show hidden files, not part of grammar. So make sure you do it right.
Create a folder called /Developer in your Home folder (under ~/Users/[your username]).
This is optional. It's just to keep things more organised. You can skip it if you either already have a in mind, or you want to place this folder somewhere else.
Download and install Sublime Text.
Go to File > New File and paste this inside:
if [ -d "$HOME/Developer/platform-tools" ]; then
export PATH="$HOME/Developer/platform-tools:$PATH"
fi
NOTE: this assumes that your Developer folder is under your Home folder, and the platform-tools folder that you downloaded from Google is inside it. If that's not the case, adjust accordingly.
save the file and name it ".zshrc".
Yes, the "." is part of the deal, so make sure you include it, too. Also, don't add any extensions to the filename. So NO .rtf, .txt, .omg etc. If you've done it right, the file's icon should show as semi-transparent. That means the file is generally hidden, but it's shown to you now so you can work with it.
move the .zshrc file to your Home folder (~/User/[your username])
unzip and extract the platform-tools folder (you should have adb and fastboot inside it, among other things)
copy-paste it under ~/Users/[your username]/Developer/ (in the end, it should look like this: ~/Users/[your username]/Developer/platform-tools)
done
Now, connect your phone via USB and test adb and fastboot with the following commands:
adb devices
For this command to work, USB Debugging under Developer Options needs to be enabled.
If everything ok, it should show your device's serial number.
After that, you can do:
adb reboot bootloader to go into fastboto mode, and then:
fastboot devices
to check if your device is properly recognised.
If all goes well, congratulations, you've successfully managed to brick your device. Oups, sorry, I meant set up adb and fastboot on your Mac! Now you can start bricking your device.
I'm joking, of course! That would be bad. But on a more serious note, you should now be able to start developing, flashing custom ROMs, fixing your device if it's already broken etc.
N-joy!