Related
hi there,
been busy all evening on my Mac trying to unlock and root my nexus one retail. Got the phone unlocked after extensive reading on SDK and ADB Hoped that the positive flow would continue when switching over to the rooting process, but unfortunately I seem to get stuck and have failed
I downloaded the correct superboot version for my phone and placed it in my home folder (on same drive as where I successfully did the fastboot procedure for unlocking). And then I entered this in Terminal:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /superboot
suikerchiller-macbook-3:superboot suikerchiller$ chmod +x install-superboot-mac.sh
suikerchiller-macbook-3:superboot suikerchiller$ ./install-superboot-mac.sh
ERROR: could not get pipe properties
downloading 'boot.img'... OKAY
booting... OKAY
suikerchiller-macbook-3:superboot suikerchiller$
---
As a result my phone automatically reboots into basic settings. Does anybody know what I'm doing wrong??? I'm a total n00b but am really eager to learn In a bit of trouble now as well, because I don't know what to do anymore and dare to touch my fone either.
Any help would be great. Can't wait to finally be released from Vodafone's retail nexus one terror and want to challenge all those ignorant iphone studs out there and show how cool and superior my Nexus one actually is
P.S. I searched for quite some time on the forum and couldn't find a post/thread that was related to my problem. Please forgive me if this is some sort of double post.
If your phone is unlocked, don't bother with superboot, just flash a custom recovery and use it to install the su zip...
http://forum.xda-developers.com/showthread.php?t=682828
Place the recovery image in your sdk tools folder, place the su zip on your sd card, connect via fastboot and type:
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
Flash the su zip from recovery, and you're done!
many many thanks for the quick reply I placed the recovery image in my sdk tools folder.
However, still have a couple of questions:
I don't know what you exactly mean with a su zip??? Where can I get this file?
what do you mean with: "flash the su zip from recovery"?
I put a link in my original post. The eclair/froyo version works for gingerbread, also...
Once in recovery, you chose the flash zip from sd option, and then the chose zip from sd option, find and select the zip... It will be obvious when you do it...
sorry, it's still too much rocket science for me I guess
I uploaded the su zip file (did not unzip or rename file) to my sd card (activated usb storage and dropped the zip via Mac in the main folder of my phone).
what do you exactly mean with "connect with fastboot"? I shut down my fone first and pressed power button at same time with track ball. Then I did this:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:~ suikerchiller$ fastboot flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$ cd ~
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
As you can probably see it didn't really work haha what am I doing wrong? Sorry for my n00biness!
You said you have already unlocked your bootloader. In order to unlock the bootloader I you have to connect with fastboot...
How did you unlock the bootloader?
I unlocked it via the first 7 steps of this procedure (sorry have to copy paste a lot of text because im not allowed to post outside links on forum yet haha):
-----
Connect your Nexus One to your PC/Mac and turn it off.
Hold the trackball and hit the power button (while holding the trackball). You should see the following bootloader screen.
Now from the files you downloaded previously, you will see a folder called ‘fastboot‘ (if you extracted fastboot.zip that is!).
On a Windows machine – launch Command Prompt and CD to fastboot folder. (Type in ‘cd ‘ (without the quotes and drag and drop the fastboot folder to the command prompt). Type in ‘cd fastboot‘ again and now type the following command ‘fastboot-windows oem unlock‘ (without quotes) and hit enter.
On a Mac or Linux machine – launch the Terminal and CD to fastboot folder (type in ‘cd ‘ and drag and drop the folder. Now hit enter.). Now CD to the other fastboot folder and type the following (without quotes): ‘./fastboot-mac oem unlock‘ (for Mac) or ’./fastboot-linux oem unlock’ (for Linux) and hit enter. You will see the following. Ignore the error.
This is the screen that you will see now. Use the volume button (on the side) to select ‘Yes’. (Please read the full message displayed on the screen thoroughly). Now push the Power button to select this option (weird, I know. Trackball would have been a better choice to select!).
Great! You have successfully unlocked the bootloader! You will see the unlock image while your phone boots up.
----
I did this successfully and had the black screen and selected unlock phone. So when I press the power button & trackball at same time now I get a white screen now and it says in pink on top: ***Unlocked***
Ok substitute the term fastboot-mac instead of fastboot, into my previous instructions
damn, still doesn't seem to be working:
---
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:~ suikerchiller$ cd /fastboot
suikerchiller-macbook-3:fastboot suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
----
it's really weird, it looks like my fastboot is not responding anymore... Any idea what's going wrong here???
thanks so much for taking time and helping with figuring this one out!!!
Just tested something. When my phone is switched on normally and connected via USB, Terminal recognizes it as an adb device. However, when I switch into fastboot, Terminal doesn't recognize it:
---
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
HT07YP804207 device
suikerchiller-macbook-3:tools suikerchiller$ adb devices
List of devices attached
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???
adb will only work when it can see the adbd on your phone, so the phone had to be booted to either recovery or fully bolted.
fastboot will only connect when your phone is booted in fastboot. If its not connecting, reboot your phone and mac and try again...
suikerchiller said:
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
---
Is this where the problem resides?? Anyone know how I can fix this???
Click to expand...
Click to collapse
Sorry, just re-read this...
Command not found, NOT device not found.
You should be typing fastboot-mac, not fastboot...
Do you have a file called fastboot-mac in the same folder as your adb and recovery img?
rebooted my mac and phone... Still no difference, this is my latest command:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
---
can this be the reason: my fastboot folder is in a different (other) folder than my 'android sdk' folder... should i drag and drop fastboot into the tools folder of sdk???
YES!
Put the fastboot-mac file in the same folder as the other stuff!! xD
haha ok, so I copied my fastboot-mac file (original file from fastboot folder) into AndroidSDK/tools folder. It's in the same folder now where the .img file is in as well.
But it still doesnt seem to be working. These are the commands that I have been using:
---
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac boot recovery-RA-passion-v2.2.1-CM.img
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot-mac devices
-bash: fastboot-mac: command not found
suikerchiller-macbook-3:tools suikerchiller$ fastboot devices
-bash: fastboot: command not found
suikerchiller-macbook-3:tools suikerchiller$
---
What's going wrong??? I'm going slightly mental now. Also running out of beer at same time. Not a good combination
can you list the contents of that folder, and tell me what result you get?
this is the list of files in my AndroidSDK/tools folder:
--
suikerchiller-macbook-3:tools suikerchiller$ ls
Jet hierarchyviewer
NOTICE.txt hprof-conv
adb-mac layoutopt
adb_has_moved.txt lib
android mksdcard
ant monkeyrunner
apkbuilder proguard
ddms recovery-RA-passion-v2.2.1-CM.img
dmtracedump source.properties
draw9patch sqlite3
emulator traceview
etc1tool zipalign
fastboot-mac
---
and here are the commands for fastboot, in case they can be of any usage
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
Hmmmmm, well the file is there, so that's really weird because you mac is definately saying that it's the command it can't find...
I'm not much of a mac guy, but I do know that your mac is the one having the problem...
Try:
./fastboot-mac flash recovery name-of-recovery.img
suikerchiller-macbook-3:~ suikerchiller$ cd /"Android SDK"/tools
suikerchiller-macbook-3:tools suikerchiller$ ./fastboot-mac flash recovery recovery-RA-passion-v2.2.1-CM.img
sending 'recovery' (3380 KB)... OKAY
writing 'recovery'... OKAY
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage & No ROM to Flash [19 May 15]
How to Sideload in TWRP if you erase your Internal Memory and don't have a ROM to Flash or Restore
Warning!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
Code:
#include
/*
* Unlocked Phone @ HTCDEV
* Custom Recovery
*/
Before You Start - Update Android SDK - How to set up Android SDK (ADB)
Instructions
MAKE SURE YOU BACK UP YOUR SD CARD FIRST!!!!!!!!
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit andvanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device conntected and say sideload
6. Your ZIP file should already be in your adb folder - See Example Below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip <------------See Example Below
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Click to expand...
Click to collapse
If You have any Troubles with ADB
Koush Universal ADB Driver - Works on Windows 8 - Thanks xeroxide
YouTube Video for ADB Help
How to install ADB Drivers for any Device
FAQ
If your Output looks similiar to this below, then you are not in sideload mode or you typed the command incorrectly
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\William>cd Downloads\ADB
C:\Users\William\Downloads\ADB>adb sideload Slim-nozomi-4.2.2.build.6-OFFICIAL
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d: \
'-d:' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>:-d
C:\Users\William\Downloads\ADB>-d\
'-d\' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB>-d
'-d' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\William\Downloads\ADB
DO THE FOLLOWING - (Refer to Post 1 Before you start for Picture Example)
1. Run sdk manager and update all the 4.1.2 - 4.4.2 binaries, you will see installed if you have done so
2. Reboot into TWRP
3. Go to advanced
4. Touch ADB Sideload
5. Swipe To start sideload
6. in command promt example: cd c:\android\sdk\platform-tools (that is where my adb files are at)
7. Once you have navigated to where your adb is at in command promt type adb devices
8. When you type adb devices, it should show your HTCxxjxihdjiw (whatever yours is) and Sideload which indicates you are set up properly
9. Once you see the above type adb sideload nameofzip.zip
bdorr1105 said:
Reserved if needed
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
get em greezemeister!!!!
I have never had to do it... but if I do I know there are easy to understand directions.. Thanks
slimc84 said:
get em greezemeister!!!!
Click to expand...
Click to collapse
Lol thanks greezemeister
Sent from my HTC One using xda premium
Wow amazing that you posted this on the very day like an idiot I bricked my new HTC one. I followed your directions with no luck however. What I did to get in this mess was to wipe the phone before realizing I forgot to put the viper rom in internal storage. (I have an OTG cable on the way but wont be here for a few days.) So I open an adb command window and when I type in adb devices it does show my device with the following text:
"List of devices attached
FA345S900209 host"
I have the rom zip file in the correct directory on my desktop but when I type adb sideload it just brings up the entire adb help menu.FWIW on the phone it shows "starting ADB sideload feature" but it never does anything after that. ANy thoughts would be greatly appreciated!
Thanks!
I have not ran into this for a while, but I thought you could just adb push the Rom to the phone and flash as normal.
Sent from Taptalk on HTC One on some awesome custom Rom!
avwheeler said:
I have not ran into this for a while, but I thought you could just adb push the Rom to the phone and flash as normal.
Sent from Taptalk on HTC One on some awesome custom Rom!
Click to expand...
Click to collapse
Is there any trick to doing that ? I tried adb push and the rom name but is there something I'm missing ?
pitchristian said:
Wow amazing that you posted this on the very day like an idiot I bricked my new HTC one. I followed your directions with no luck however. What I did to get in this mess was to wipe the phone before realizing I forgot to put the viper rom in internal storage. (I have an OTG cable on the way but wont be here for a few days.) So I open an adb command window and when I type in adb devices it does show my device with the following text:
"List of devices attached
FA345S900209 host"
I have the rom zip file in the correct directory on my desktop but when I type adb sideload it just brings up the entire adb help menu.FWIW on the phone it shows "starting ADB sideload feature" but it never does anything after that. ANy thoughts would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Try using the tool kit and relocking boot loader and run the RUU
Sent from my HTCONE using xda app-developers app
pitchristian said:
Is there any trick to doing that ? I tried adb push and the rom name but is there something I'm missing ?
Click to expand...
Click to collapse
It has been a while, just remember that the paths/location need to be right. Might have to mount storage or something like that too. Lots of threads on adb. Wish you luck, that sucks.
Sent from Taptalk on HTC One on some awesome custom Rom!
thanks guys I fixed it after relocking the bootloader and running the stock RUU from toolkit as mentioned! I really appreciate it. (FWIW I could never get sideload through TWRP to work)
Added you guide HERE Q14 Thanks OP
pitchristian said:
thanks guys I fixed it after relocking the bootloader and running the stock RUU from toolkit as mentioned! I really appreciate it. (FWIW I could never get sideload through TWRP to work)
Click to expand...
Click to collapse
Glad you got it back up and running. You really should read up on adb. And how to get your paths correct. The toolkits are great but its always good to know ADB just in case you.
Sent from my HTCONE using xda app-developers app
Sorry guys I am 6hrs behind east coast. I live in Hawaii
You can use adb push if the phone is picked up in recovery but a lot of times my phone isnt recongnised. You have to go in advanced and swipe to start adb sideload...You literally dont have to pick a path because by default side load pushes to the root of your sd card...All you have to do is have the zip in the right place on your computer and type the command as instructed and it will push the zip to your sd card
pitchristian said:
Wow amazing that you posted this on the very day like an idiot I bricked my new HTC one. I followed your directions with no luck however. What I did to get in this mess was to wipe the phone before realizing I forgot to put the viper rom in internal storage. (I have an OTG cable on the way but wont be here for a few days.) So I open an adb command window and when I type in adb devices it does show my device with the following text:
"List of devices attached
FA345S900209 host"
I have the rom zip file in the correct directory on my desktop but when I type adb sideload it just brings up the entire adb help menu.FWIW on the phone it shows "starting ADB sideload feature" but it never does anything after that. ANy thoughts would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Hey man I think you already fixed your phone but in the future you have to be booted into TWRP already then what you do next is go to Advanced and then Sideload then you swipe to enable sideload on the phone...After you have done that the phone will say starting adb sideload...It's important you update Adnroid SDK so you have the latest binaries....Once sideload is enabled on your phone then you you type the adb devices and it shouls show your device and say sideload, if it does you are solid...
After that then you type adb sideload nameofzip.zip and it will start pushing to the root of your SD card and then you just flash like normal...
Glad locking the bootloader and using the toolkit worked for you bro
bigdaddy619 said:
Added you guide HERE Q14 Thanks OP
Click to expand...
Click to collapse
Thanks man appreciate it. Thanks for the heads up
avwheeler said:
I have not ran into this for a while, but I thought you could just adb push the Rom to the phone and flash as normal.
Sent from Taptalk on HTC One on some awesome custom Rom!
Click to expand...
Click to collapse
You can use adb push but if your phone is in recovery adb didn't recognize my phone, it did when I was booted in my ROM but this is worst case or upgrading and you wipe the internal memory before you flash and your sd is blank and you can't flash adb sideload is different than regular adb commands...
When I wiped my SD on accident a few days ago I managed to adb push while in recovery.
I think it has to do with which drivers you have installed. I just use the ones that come with the Android SDK ( /sdk/extras/google/usb_driver/android_winusb.inf ), and I have the driver set to "Android Composite ADB Interface".
Always good to have options though. :good:
Harfainx said:
When I wiped my SD on accident a few days ago I managed to adb push while in recovery.
I think it has to do with which drivers you have installed. I just use the ones that come with the Android SDK ( /sdk/extras/google/usb_driver/android_winusb.inf ), and I have the driver set to "Android Composite ADB Interface".
Always good to have options though. :good:
Click to expand...
Click to collapse
Yeah it is good to have options, there is no need for paths pretty much sideload puahes to the root of your sd card automatically so it's easier in my opinion. Anyway thanks for the info
Sent from my HTC One using xda premium
bdorr1105 said:
Yeah it is good to have options, there is no need for paths pretty much sideload puahes to the root of your sd card automatically so it's easier in my opinion. Anyway thanks for the info
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
So what happens when all the abve has occurred and now in TWRP it states, Sideload failed?
Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
andrey o said:
Guys, I have a problem with my HTC One M7. I am trying to unlock the bootloader using the HTCDev guide (available at htcdev site).
But suddenly I am not able to complete Step 8 (running command "fastboot oem get_identifier_token").
Command "fastboot devices" shows my phone in a fastboot mode:
\> fastboot devices
mt6589_phone_720pv2 fastboot
But none of fastboot oem commands executes successfully (including "get_identifier_token").
Instead I get only three dots ("...") and nothing changes after that:
\> fastboot oem get_identifier_token
...
Other commands (like fastboot reboot) function, but not "fastboot oem get_identifier_token". I can't unlock my bootloader, could you please help!
Click to expand...
Click to collapse
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
If you're using Windows 8, I would use the following link that I've seen floating around here"
http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
I had issues getting the token for mine until I used that guide to convert my Microsoft USB 3.0 drivers into Intel drivers.
gunnyman said:
Never seen that before but since we have S-off now you can unlock the bootloader without HTCDev
check out the revone thread in the Original Development section.
Click to expand...
Click to collapse
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
andrey o said:
Thanks for this advice, I am now trying to do it with revone.
I have successfully pushed the file to the phone, but when executing adb shell commands I get a error:
"- exec '/system/bin/sh' failed: No such file or directory"
How to fix it?
Click to expand...
Click to collapse
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
gunnyman said:
Not sure, but the folks in that thread are super helpful
you're in an ADB shell when you execute the command?
Click to expand...
Click to collapse
Yes, I am now reading that thread to find the answer.
Here's what i do and what I get:
> adb devices
List of devices attached
0123456789ABCDEF recovery
> adb push revone /data/local/tmp/
4584 KB/s (648208 bytes in 0.138s)
>adb shell cd /data/local/tmp
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Start the shell. Then do the cd command separately
gunnyman said:
Start the shell. Then do the cd command separately
Click to expand...
Click to collapse
same result
> adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Is the phone in recovery or booted up? Needs to be booted
gunnyman said:
Is the phone in recovery or booted up? Needs to be booted
Click to expand...
Click to collapse
It was in recovery mode - my mistake, thank you for pointing.
I have booted it and executed the needed commands, but still another mistake:
>sudo adb shell
[email protected]:/ # cd /data/local/tmp
[email protected]:/data/local/tmp # chmod 755 revone
[email protected]:/data/local/tmp # ./revone -P
revone v0.2.1
revone failed (error code = 1)
1|[email protected]:/data/local/tmp #
Step by step I am coming closer to the result, thanks so much for your help
READ THIIS!
*this thread is for desire 510. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or unlocked back to stock.
advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on. its not a way to magically unlock
the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of plastic goo,its not my fault.
credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
*i have tested this on my gsm cricket desire 510 variant(a11_ul). let me know if you try it on a different variant,or if youd like to dump partitions and have me take a look
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "lock status flag"
to LOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now locked
_____________________________________________________________________________________________
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
other useful threads:
remove your tampered banner: http://forum.xda-developers.com/desire-510/general/how-to-remove-tampered-banner-t3179866
mine too
I have been going at it for a week straight and unable to find help. I am using Nexus Root Tool Kit 2.1.0. My Device is unlocked and OEM unlocked. However when i try to root the phone restarts into AP Fastboot Mode and nothing happens but the program seems like its trying but just unable to finish.
Log File:
Nexus Root Toolkit v2.1.0
Masterlists:
- LatestToolkitFiles.ini 3099
- AndroidDeviceListFull.ini 3099
- AndroidDeviceListFlash.ini 3099
SHAMU-SHAMU: Android 6.0.0 - Build: MRA58N
Live log initiated [2015-11-28]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Flashing Root Kernel to BOOT partition...
fastboot flash boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Root_Files\root_kernel_shamu_mra58n.img"
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Rebooting your device...
Waiting for your device...
I have also tried to flash a custom boot.img but NRT stops at rebooting device.
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G225J9J fastboot
Connectivity Status: Fastboot Device Connected
Flashing boot.img to BOOT partition...
fastboot flash boot "C:\Users\Dave\Desktop\volantis-mra58n-boot-system\boot.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
my screen just never does anything i remember last time i rooted on Android L it went with no problems.
just stays at
AP Fast boot Flash Mode (Secure)
BL: moto-apq8084-71.15 (sha-96f7faf, 2015-08-04 11:36:17)
Base Band : D4.01-9625-05.27+fsg-9625-02.104
just installed ADB and tried from command prompt to flash TWRP and i got failed (data transfer failure (unknown error) )
well, you are doing it wrong for a nexus owner, you dont need a root toolkit. to root m you need to flash any custom kernel for m as well as the latest supersu(as well as the latest twrp recovery so you can flash a custom kernel and supersu).
Don't use Root kits and follow these steps. Start from step 1 if you already have your bootloader unlocked and if you have SDK tools installed (adb and fastboot). And you should be fine...
yes wont let me install recovery TWRP
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11700 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.012s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
thats because you dont use adb for this. you have to use fastboot while you are in your recovery. read that again, FASTBOOT instead of ADB. you always use fastboot to flash the factory image or any part of it, or twrp recovery.
simms, the command he posted that failed WAS fastboot.
HOWEVER, if adb is reporting devices, you are likely either booted to android or recovery... reboot to the bootloader
(turn off device, then hold volume down and while holding vol down press and hold power until the device boots to the bootloader mode.
Make sure that you have twrp in the same folder, and that you have renamed it to recovery.img (not .img.img as a lot of people accidently do) That last part isn't completely necessary, as its really just "fastboot flash recovery <file name>", and you can replace <file name> with the name of the recovery image it doesn't HAVE to be recovey.img, and it doesn't have to be in the same folder if you include path... but people find it easier to just rename it to recovery.img, copy it to their platform tools folder and use the command you ran.
ahh.. yea @scryan i didnt see that fastboot was used(later in the post). now i see hes uding adb devices instead of fastboot devices.
As far as I can see, you are trying to flash recovery using fastboot flash recovery recovery.img while not in bootloader (or you didn't copy everything you did).
You should:
1. adb reboot bootloader (your phone will reboot into bootloader)
2. now you can write "fastboot devices" to see if your phone is recognized
2. then if it's there: "fastboot flash recovery recovery.img"
EDIT: If you still did everything correctly, quick google search said it could be problem with computer's USB port. Try another port...
I have tried every port on my pc some give unrecognized USB error while others work. If I am able to charge and transfer files along with send adb commands (restart phone,adb sees my phone) does that rule out the USB cable? I bought a pack of four on ebayhttp://m.ebay.com/itm/4x-6Ft-Micro-USB-Charger-Sync-Data-Cable-Nylon-Braided-for-Samsung-Galaxy-HTC-/221891441910?txnId=1650092351012
I no longer have the cable I used to flash marshmallow but I did use this to unlock the device.