Related
I have troubles with developer mode on my phone.
Enable usb debug option is checked, but adb (running under gentoo linux, ubuntu, windows 7) doesn't show any devices.
But when recovery (CWM) is loaded, everything works well.
When I'm trying to start adbd with
Code:
#adbd start
I get message "cannot bind tcp:5037"
I thought it appears because adbd is already running but
Code:
ps aux | grep adb
gives nothing
Any ideas what to do? Does anyone have problems with adb even if Usb debug is turned on?
I use Debian and my command is adb start-server.
Give it a try.
Fr0zen1977 said:
I use Debian and my command is adb start-server.
Give it a try.
Click to expand...
Click to collapse
It doesn't help
Shtsh said:
...But when recovery (CWM) is loaded, everything works well...
Click to expand...
Click to collapse
Looks like ROM problem. Did you tried another one??
Yes. I'm tried several stock ROMs (2.3.6, 2.3.5), cranium, broodROM. Factory reset doesn't help.
Retrieve your CPUID
(1) Use a500Manager Tool (download at bottom of post)
This tool is your first port of call! It will download the drivers, retrieve your CPUID, and flash the unlocked bootloader.
(2) Using Terminal Emulator
Reboot your tab
Code:
dmesg | grep androidboot.serialno
some have reported this did not work for them but that this one did when they tried it:
Code:
dmesg > /mnt/external_sd/dmesg.txt
(3)Using USBDeview
Suggest you extract to the same folder you used for your adb files,
USBDeview will only work when you have previously plugged your tab into the PC WHILE
you were running HC Rom and BL
1 Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2 Click on "VendorID" along the top to sort them
3 Look for the number "0502" under VendorID or 3325 "ProductID"
4 In the serial number column will be a 15-digit number this is your device ID
5 Write the number down and put a 0 in front of it and now you have your CPU ID!!!
(4) From your nandroid backup
In the cwm folder on your ext. sd card - open one of your backup folders and look for "uid.txt" file.
From cwm 1.7.2 on, will dislay your "uid" on the menu screen, and from memory TWRP does too.-
(5) Run command "adb devices" in command prompt HC ONLY
(6) From Custom Recovery
Most of the custom recovery's now have your uid displayed on the main screen of the recovery menu
(7) From a working Tab...
open yr file explorer, esfile explorer is a great one....
navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!!! easy peasy
(8)From a bricked or non-booting Tab
then things become a little more complex. And more involved if you have no backup.
The only way is using Linux. srbeen has a guide to do this using code by eppeP. There are those who being Linux noobs have had success with this method.
Read the whole thread as there are some helpful hints all thru the guide. If you get stuck eppeP is still around and will help out, if you can show an example of
"how and where" something does not seem to be working for you. If your questions go unanswered its because its been answered before so please go thru the thread!!!
here.
srbeens guide here
Cannot boot tab because:
(1) "Write Protected - need to enter password
If you encrypt your data and forget your password - you must do a full data reset wipe to get into your system again
(2) Stuck on the Acer Screen
From user JDGM3NT4L - Want to return to stock? This is for you...
A500 Back to Factory Stock the easy way
- via stock update.zip method
- no cpuid required,
- use with or w/out patched bootloader.
- needs cwm installed
- full data wipe needed
(3) Other things to check
- check data cables, micro-usb cable required
- plug in to another USB Port
- check you have the cable actually connected to both device
Try a different PC. Vista/Win 7/XP usually have no problems, there are issues with Win8 and 64bit systems
Also a heads up for when entering your uid's into the tool generators - a space counts as a character and will produce
an incorrect sbk!!!
You CANNOT use lowercase letters in your cpuid. If you do lowercase it will give you a different result
Vaches new SBK Tool here OR [/B]
DRIVERS
The drivers are not installed properly, I can hear you all already!! I've done that over and over and its not working!!!!
sometimes if you fail to complete a nvflash you need to completely reinstall the Acer Drivers before it seems to want to finish...ssoooooooo, uninstall and reinstall!!!!
Acer Support for Acer APX/Fastboot/Recovery Drivers
Android SDK for the adb/USB drivers - You can d/l a mini zip containing just the adb and fastboot drivers attached to this post "adb_fast.zip"
GUIDES
Civs Guide to flashing the bootloader
walkthrough using apxflash tool at Step 6
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide here
Iconia Root/gingerbreak: For returning to Honeycomb
GETTING ADB SET UP
It's a pain typing "my path" into cmd, can't I just type "adb devices"
Set adb as Environment Variable or call adb direct from command prompt
first, copy the path to your install - in this case:
"Path to adb" = C:\android\
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in this case C:\android\adb
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥
I added a link to this in the V3 guide.
Thanks for this.
civato said:
I added a link to this in the V3 guide.
Thanks for this.
Click to expand...
Click to collapse
Why thank you...all good civ, anything to help really
Stock ICS unable to access any of this...
dibb_nz said:
If you are upgrading/downgrading using APX mode then you need your cpu id.
if you're having problems then keep reading...
Upgrading via an EUU/SBK method is dependant on a "successful communication connection" between your TAB and PC
If you cannot run "adb devices" and have it return your CPU ID then the flashing process will fail.
If you have a custom ICS rom AND on the HC Bootloader this number will be your serial no. please see note below
ok, lets go, you need the correct drivers installed to begin with:
1) go to Acer Support and download the Acer Drivers
2) run the Setup.exe to install them
You must also have the ADB drivers from the android-sdk (see attached zip)
3) Extract the adb files to your desktop
4) Open command prompt as admin
5) In the command prompt window type cd
6) leave a space after it
7) drag and drop the adb folder into the command window (This saves you having to enter the path manually)
8) Now, type adb devices and write your device ID down with a zero in front...done!!!
If you cannot get adb to retrieve your ID then the flashing process will not work as it should.
You need to fix this first....
*****Note: HC Bootloaders on custom ICS builds
adb will report your device ID as your serial number, which of course will not work for APX based flashing - thanks to tehdomil for the heads up
you guys will need your original HC CPU ID which you can get from the back up you made before flashing the ICS rom. For those that didn't - try usbdeview below.
*****How to retrieve your CPU ID from USBDeview
Suggest you extract to the same folder you used for your adb files, just to keep things tidy...you're bound to want these things again
1) If you haven't plugged your tab into this pc before, do so now, before you run the program.
1a) Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2) click on "VendorID" at the top to sort them
3) Look for the number "0502" under VendorID or 3325 "ProductID"
4) In the serial number column will be a 15-digit number this is your device ID
5) Write the number down and put a 0 in front of it and now you have your CPU ID
The adb guide will still apply as far as getting your tab and pc talking on the same wave length
Click to expand...
Click to collapse
Ok, followed all the steps. But cannot get my PC to recognise my tablet completely. MTP:yes, or Camera:yes, yet there is a driver missing which fails to load/install. Any ideas from you bright people?
I would like to access bootloader and flash recovery.
V frustrating.
For example, where do you find mtpfs and mount for Win 7 x64?
Thanks
DrPlumEU said:
Ok, followed all the steps. But cannot get my PC to recognise my tablet completely. MTP:yes, or Camera:yes, yet there is a driver missing which fails to load/install. Any ideas from you bright people?
I would like to access bootloader and flash recovery.
V frustrating.
For example, where do you find mtpfs and mount for Win 7 x64?
Thanks
Click to expand...
Click to collapse
What shows in the command window after typing in adb devices?
dibb_nz
/ adb devices
List of devices
/
In device manager, I have a "Other devices" Acer Iconia A500 no driver installed, yet "Portable Device" Acer Iconia A500 is fine.
I can copy and paste files from tablet while in MTP mode. No difference with SD card mounted or unmounted.
Very frustrating. The last device driver I assume is "USB device" but despite mucking around with Acer USB device drivers 1.00.0524 and 1.06.1500 no luck.
Grr
oops.....
save for later
list of devices shows but no number
DrPlumEU said:
dibb_nz
/ adb devices
List of devices
/
In device manager, I have a "Other devices" Acer Iconia A500 no driver installed, yet "Portable Device" Acer Iconia A500 is fine.
I can copy and paste files from tablet while in MTP mode. No difference with SD card mounted or unmounted.
Very frustrating. The last device driver I assume is "USB device" but despite mucking around with Acer USB device drivers 1.00.0524 and 1.06.1500 no luck.
Grr
Click to expand...
Click to collapse
sorry bit caught up at the moment
things to check first:
...1) That you do have USB debugging enabled:Settings>Applications>Development
...2) Win7/Vista work best; XP can be titchy
...3) You d/l the "Just_adb.zip" to install the adb drivers - you dont mention an entry for them in Device Manager
...4) Switch USB ports on your pc
...5) Try another USB cable
...6) Put the MTP thing aside for now, they have no bearing on this issue
If still no joy then if you can, try another pc
If thats not possible then uninstal and reboot both devices
then reinstall both acer and adb - acer ones mainly
When you connect your tab again WAIT for windows to install them and see how u go
ADB or USBDeview both tell me that my CPUID is 0123456789ABCDEF. Of course, if I get the SKB and use NVFlash to validate it, it fails with a message that says "USB device not found."
I found my CPUID (0x033c20c541a051d7) in an old nandroid backup and tried it but with the same results.
Any ideas?
CPU ID : Dev ID : UID
spoupard said:
ADB or USBDeview both tell me that my CPUID is 0123456789ABCDEF. Of course, if I get the SKB and use NVFlash to validate it, it fails with a message that says "USB device not found."
I found my CPUID (0x033c20c541a051d7) in an old nandroid backup and tried it but with the same results.
Any ideas?
Click to expand...
Click to collapse
Ok i'm amending the guide as we speak, just to be clearer.
The device ID as reported by adb is 15 digits long the (UID)
when we use this no. for an EUU based flash we add a 0 to the front making 16 digits (CPUID)
the one in your nand adds 0x to the basic UID 17 digits
the CPUID from the EUU is for Honeycomb bootloaders
Which I believe is different for ICS bootloaders
and different again for HC b/l on ICS Rom!!!
i tried the SBK generator last nite for the first time and entered only my UID
and had no probs
so give that a go (in the example you gave) 033c20c541a01d7
dibb_nz said:
Ok i'm amending the guide as we speak, just to be clearer.
The device ID as reported by adb is 15 digits long the (UID)
when we use this no. for an EUU based flash we add a 0 to the front making 16 digits (CPUID)
the one in your nand adds 0x to the basic UID 17 digits
the CPUID from the EUU is for Honeycomb bootloaders
Which I believe is different for ICS bootloaders
and different again for HC b/l on ICS Rom!!!
i tried the SBK generator last nite for the first time and entered only my UID
and had no probs
so give that a go (in the example you gave) 033c20c541a01d7
Click to expand...
Click to collapse
Thanks for your help, but no luck. I tried the 033c20c541a01d7 number already in SBK and NVFlash still gives the same error. BTW, SBK generates the same number for both 033c20c541a01d7 and 0x033c20c541a01d7. Apparently, SBK is smart enough to ignore the leading 0x.
Any other suggestions?
spoupard said:
Thanks for your help, but no luck. I tried the 033c20c541a01d7 number already in SBK and NVFlash still gives the same error. BTW, SBK generates the same number for both 033c20c541a01d7 and 0x033c20c541a01d7. Apparently, SBK is smart enough to ignore the leading 0x.
Any other suggestions?
Click to expand...
Click to collapse
that blows that theory
what does dmesg say?
edit: what tool are u using for nv flash, what b/l u on?
and if ADB or USBDeview both tell you CPUID is 0123456789ABCDEF then.....
spoupard said:
....if I get the SKB and use NVFlash to validate it, it fails
Click to expand...
Click to collapse
So, the NV Flash tool invalidates the uid/sbk where usbdeview and adb agree??
with a message that says "USB device not found."
Click to expand...
Click to collapse
i no nothing of the nvflash process "in this instance" but if device is not found then there is no "connection" happening between the 2....have u posted on the thread where you got the tool?? not trying to fob you off at all its just theres alot methods out there at the moment and i'm doing my best to keep up with them all!!!
I found my CPUID (0x033c20c541a051d7) in an old nandroid backup and tried it but with the same results.
Click to expand...
Click to collapse
are you saying cpuid here is different to what the other 2 report???
i'll be out for an hour or so but will stop in when i get back . good luck
dibb_nz said:
So, the NV Flash tool invalidates the uid/sbk where usbdeview and adb agree??
i no nothing of the nvflash process "in this instance" but if device is not found then there is no "connection" happening between the 2....have u posted on the thread where you got the tool?? not trying to fob you off at all its just theres alot methods out there at the moment and i'm doing my best to keep up with them all!!!
are you saying cpuid here is different to what the other 2 report???
i'll be out for an hour or so but will stop in when i get back . good luck
Click to expand...
Click to collapse
I'm using NVFlash from civato's post on how to flash the ICS bootloader. I have a connection because I can launch a shell in ADB and navigate around on my tablet. Also, if I didn't have a connection, "adb devices" would not return any devices. I can also see the device listed in Windows device manager.
I am running the HC bootloader with CM9 ROM. I had been using TeamWin recovery, but found out it is not compatible with the ICS bootloader. I have since replaced that with the ACER Recovery found in the Market. I did another nandroid backup after installing ACER Recovery (thor's recovery) and it gave me a cpuid of 033c20c541a051d7.
- u got adb ones all good bt not apx ones - reinstall acer drvs
spoupard said:
I'm using NVFlash from civato's post on how to flash the ICS bootloader. I have a connection because I can launch a shell in ADB and navigate around on my tablet. Also, if I didn't have a connection, "adb devices" would not return any devices. I can also see the device listed in Windows device manager.
Click to expand...
Click to collapse
yep the usb-adb drivers are all there but you said earlier u have a fail error of device not found from the flash validator, so it sounds like the issue was not the incorrect sbk but the device not found....run the acer driver setup ...windows will install the apx drivers when your tab is ready to enter apx/download mode.
I am running the HC bootloader with CM9 ROM. I had been using TeamWin recovery, but found out it is not compatible with the ICS bootloader. I have since replaced that with the ACER Recovery found in the Market. I did another nandroid backup after installing ACER Recovery (thor's recovery) and it gave me a cpuid of 033c20c541a051d7.
Click to expand...
Click to collapse
I have no idea why you have so many uid's, if any one knows how exactly these are generated from recovery, i'd love to know!!!!
dibb_nz said:
So, the NV Flash tool invalidates the uid/sbk where usbdeview and adb agree??
i no nothing of the nvflash process "in this instance" but if device is not found then there is no "connection" happening between the 2....have u posted on the thread where you got the tool?? not trying to fob you off at all its just theres alot methods out there at the moment and i'm doing my best to keep up with them all!!!
are you saying cpuid here is different to what the other 2 report???
i'll be out for an hour or so but will stop in when i get back . good luck
Click to expand...
Click to collapse
dibb_nz said:
yep the usb-adb drivers are all there but you said earlier u have a fail error of device not found from the flash validator, so it sounds like the issue was not the incorrect sbk but the device not found....run the acer driver setup ...windows will install the apx drivers when your tab is ready to enter apx/download mode.
I have no idea why you have so many uid's, if any one knows how exactly these are generated from recovery, i'd love to know!!!!
Click to expand...
Click to collapse
Well I have to admit that this whole problem was my fault. No matter how many times I read the instructions, I somehow breezed right past the part about entering apx mode. Thank you so much for your help!
I don't have enough numbers
Okay I tried using USBDeview and it came up with a 11 digits - looked where the instructions said.
dawgpoundfan said:
Okay I tried using USBDeview and it came up with a 11 digits - looked where the instructions said.
Click to expand...
Click to collapse
Try to run dmesg from yr tab first, ------ hat tip to jp
If you haven't rebooted your Tab for a while, then in the output of dmesg, the very old entries, the ones just after bootup, which contain the entry/line containing 'androidboot.serialno' are lost/overwritten.
Just reboot your Tab & run dmesg again.
Just use the command ''dmesg | grep androidboot.serialno"
Voila!
Cheers, Jp
Click to expand...
Click to collapse
I can;t seem to find my cpuid. I am running a custom ics rom, with the HC bootloader.
Do not have a nandroid backup to look at.
dmesg does not show androisboot.serialno after a reboot.
osbdeview shows an 11 digit number.
Any ideas?
For those on Windows 8.1 who have just about given up trying to get S-OFF...
For reference I have an ATT HTC One, but showing in bootloader as m7ul (didn't seem to make a difference to any downloads/steps anyway so meh)....
hboot = 1.44
S-ON (hence the inability to install the new GPE 4.4 ROMs)...
So I have tried every single fix imaginable on these forums and the Internet in general... absolutely nothing has worked... trust me....
I then seen a comment from someone mentioning using Ubuntu to do it... I thought... no way, I'm not bothering, all that effort, and it'll still fail... well tell you what, via various forums, sites, fixes etc (lol) I got there in the end.
Prerequisites:
Rooted
hboot 1.44 (I haven't tested newer versions... assume you're looking here really because you had the same problems as me - test with other hboot versions at your own risk I guess)
Not sure if the version of Rom you are currently on matters, I was on 4.3 Google edition (Eragon V14), so don't ask me which to be on
Let's do the following:
1) Download Windows Ubuntu from here:
http://www.ubuntu.com/download/desktop/windows-installer
Click "Get the Installer"
Download and save the .exe to wherever you want
2) Right click the .exe and create shortcut
3) Change the target of the shortcut (right click --> Properties) to end with the following: \wubi.exe --32bit
4) Run the installer, and just go with any defaults
5) Once rebooted in to Ubuntu we are going to download and install fastboot and adb
6) Click the Windows key, type "Terminal" and hit RETURN
7) type the following at the "command" prompt: (do not type [RETURN] <-- lol)
sudo add-apt-repository ppa:nilarimogard/webupd8 [RETURN]
sudo apt-get update [RETURN]
sudo apt-get install android-tools-adb android-tools-fastboot [RETURN]
When prompted, enter the password you set up when you installed Ubuntu in the first place.
8) To confirm Fastboot now works (yes... it was that easy)
Boot your phone in to Fastboot (hold VOL DWN + Power --> Fastboot)
Connect up the phone to USB
In the terminal, type the following then press RETURN
sudo fastboot devices
You should see your device serial, confirming it is recognised by Fastboot ----
9) Now to download Rumrunner -- get the archive from the following location:
http://rumrunner.us/rumrunner_downloads/rumrunner_HTC_0.5.0.tgz
Open the download (rather than save), and extract all files to the Home/Download folder (you can just click and drag them over)
10) Now, we need to allow the "soju" file to be executed
Right click the extracted file "soju" --> go to Properties --> Permissions tab --> Tick "allow executing file as program"
Almost there.....
11) Boot the phone back up and enable USB Debugging via Developer Options
Also change display timeout to 10mins, and set screen security to None
12) Disable Fastboot where applicable (Settings --> Power --> Fast boot)
13) Now to run the Rumrunner application....
Again, within the terminal, type the following:
cd Downloads [RETURN]
(if this doesn't work, you need to navigate to the folder you extracted the "soju" file to, so the cd (change directory) DOS command works fine here)
Now type the following (once you are in the same location as "soju")
sudo ./soju
If you are ready (definitely) to start the process, now press RETURN.
14) You will be asked twice to type "Yes" exactly as displayed followed by RETURN to confirm, please do not type Yes to the warnings that will come up periodically after the script starts (if you give them a moment, you will see them continue without any input from yourself)
15) Sit back... and wait for it to complete. The process took about 20mins in total to complete on my phone... and I've now got S-OFF. If you keep getting prompted for what to do with your phone being plugged in - just press cancel to the prompts.
p.s. if this worked - please press THANKS :good:
If anyone needs any clarification, let me know, I will try and respond as soon as possible (if others could help - that would be appreciated too)
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
whats yer firmware fella?
painnpleasure said:
whats yer firmware fella?
Click to expand...
Click to collapse
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
EM101 said:
It was 3.17.502.3 but since I achieved s-off I am now a "converted to Google Edition" with firmware 3.62.1700.1.
Click to expand...
Click to collapse
Ok thnx fella.im on 3.63.111.3 and having difficulties running rumrunners.ill give it another go then. I want to get to go Google edition aswel.
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
skythunder83 said:
sudo ./soju
I get err command not found!!
help plz should I be using the linux?
No prob I gut it :laugh:
Click to expand...
Click to collapse
Use the ls command to see what is in the directory you are in. Use the cd command to change directories. Keep searching til you find the directory where you put the soju file. Good luck.
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
EM101 said:
Registered here just so I could say you are awesome! Your guide worked for me after literally months of trying to get s-off for my AT&T HTC One hboot 1.55.
A couple things I had to do differently:
1. I used a ISO image of Ubuntu 12.04.3 32 bit burned to a dvd and just booted off it to the option to try Ubuntu without installing. I could not get your link to work with my Windows 7 installation.
2. Since I was not actually booting from my hard drive but rather a read only DVD, I had to do some improvising for the extracting of the rumrunner files. I put them on the desktop, but then had to search a bit to find them in order to run the soju file in terminal.
Again, thank you!
Click to expand...
Click to collapse
Glad to hear buddy. I also spent a considerable amount of time trying to find a solution to this and had just about given up.
Thanks for providing some additional notes on your steps too, might help someone else get theirs working too.
Sent from my One using XDA Premium 4 mobile app
alessiomoro1994 said:
Does my HTC One still have to be unlocked from HTC-Dev? Thank you in advance.
Click to expand...
Click to collapse
By whatever means, you will need to initially be rooted. Unlocking via HTC Dev was how I got root.
Ironically this also (at the time, not sure if it's changed) doesn't work in Windows 8.1 lol and I had to root my phone using my parents laptop with Windows 7 installed.
They then upgraded to 8,1 so I couldn't use it to get S-OFF later on.
Sent from my One using XDA Premium 4 mobile app
I finally got s-off on my att htc one. Was pretty much trying the same thing as OP stated here, but had some difficulties with other things.
1. OP's instructions didn't work for latest ubuntu (13.10)
2. Had linux mint installed on my pc, but it was 64bit.. tried quite a bit to get it working there (adb and fastboot work), but rumrunner was not happy with 64bit
3. Finally tried it on Ubuntu 12.04.3 LTS 32 bit and everything was smooth with it
One other thing to note.. I used live USB instead of installing ubuntu on my pc. had no issues, but had to use a bit older version of ubuntu and 32 bit (even tho my pc has 16Gigs of memory)
Don't know what's different, but Rumrunner worked for me - hboot 1.56, ARHD 41.0 and Windows 8.1
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
roose21 said:
I'm using crouton install of Ubuntu on my chromebook and after trying to install adb and fastboot I get:
E: Unable to locate package android-tools-adb
E: Unable to locate package android-tools-fastboot
Any ideas guys? I really want s-off! Any help would be appreciated!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like the location of those packages has changed? Unless the reason it isn't working is because of the version of Ubuntu you're on. Hmm.
Sent from my One using XDA Premium 4 mobile app
Try this:
http://vondroid.com/threads/how-to-...on-ubuntu-and-other-linux-based-systems.9793/
Sent from my One using XDA Premium 4 mobile app
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
punisher195 said:
My computer finally can recognize my phone in fastboot mode. Thanks !
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Use the "thanks" button and rate the thread then
Sent from my One using XDA Premium 4 mobile app
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?
Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!
feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly
*this thread is for m9+. it will NOT work on m7,m8,m9(or anything else). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that changed your banner in the bootloader screen to software status: modified,then this thread is for you.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on
the usual disclaimers:
this has been tested,but if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info) wich started off my love for chasing such things.
- @omar302 for getting the ball rolling,providing dumps,and lots of testing. he s-on'ed his phone several times during the tests,and has provided a huge amount of valuable info
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 lower)
-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 "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p11 bs=1 seek=39940
(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 software status: official
if this does not work for you
*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.
if youre still confident you did things correctly,you need to PM me:
1)the results of: fastboot getvar all
2)a link to an uploaded p11.
you get fastboot getvar all by:
-place phone in fastboot
-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy
you dump p11 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11
transfer the file on internal storage to your pc and upload it
im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.
important:
from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.
mine too
scotty1223 said:
mine too
Click to expand...
Click to collapse
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.
deleted. Better to wait Scotty's stock guide.
west2cool said:
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.
Click to expand...
Click to collapse
You cannot do it without turning s on. P9 is now being protected,and any attempts to modify it in any manner result in security being turned back on
Planning a back to stock guide once I'm fairly certain it can be done safely
Sent from my Nexus 9
yvtc75 said:
echo -ne ......
Click to expand...
Click to collapse
Don't do this unless you're ready to be stock and s on,and have all your ducks in a row. It could leave you bricked or stuck in the bootloader with a security warning.
There's good reason I didn't post it.
Sent from my Nexus 9
Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.
Worked for me! Thanks!
omar302 said:
Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.
Click to expand...
Click to collapse
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem
tbalden said:
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem
Click to expand...
Click to collapse
Apparently SunShine has some security system that detects if you are unlocking many times & then would just stop stop working & gives you message that your device is acting in an unusual way. I then had to contact their support to get it resolved.
i am rooted but s on, how can i s off to use your method? can someone help me
Rabia said:
i am rooted but s on, how can i s off to use your method? can someone help me
Click to expand...
Click to collapse
Currently they are using sunshine
Sent from my HTC One using Tapatalk
scotty1223 said:
Currently they are using sunshine
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
is that the paid thing, do they send a file accross or is it a physical thing
Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
http://theroot.ninja
Sent from my HTC One using Tapatalk
Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
You install the app & run it on your phone with a internet connection, after the app makes some tests & confirms your device is compatible you will be prompted to pay through the app itself ($25.00). The app itself will run & phone restart & then you get S-OFF. My M9+ was also from UAE (official-UAE version) & S-OFF worked from the 1st time. Very simple process.
Stock Locked bootloader?? @scotty1223
jureca said:
Stock Locked bootloader?? @scotty1223
Click to expand...
Click to collapse
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk
scotty1223 said:
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Ok thank you, see if you can :good: