Related
I trying to unlock my XOOM WIFI from COSTCO, when I ran the command
adb reboot bootloader
The XOOM reboots show the message STARTING FaSTboot protocol support and stuck in there, I have to VOL UP & Power to reset it.
What I am doing wrong.?
I do not want to do the ONE CLICK to avoid wiping the machine completely.
Do I need to wipe it the first time?
you need to have fastboot in your machine, then you can run:
fastboot oem unlock
it will ask you to use volume up/down keys to confirm "twice" the terms of service and will unlock it for you.
please not that unlocking it will void your warranty right away, so unless you are a developer or have a very good reason to do so, I would not recommend it.
You are doing it right.
adb reboot bootloader
is supposed to bring you to "Starting Fastboot protoco"l screen. Just continue and enter the commands as the instructions entail. If this is the first time you are rooting the device though you will end up wiping everything fyi.
ubuntu and fastboot....waiting for device
I am running Ubuntu 10.10. When I do adb reboot bootloader....when I run any fastboot command it says <Waiting for Device>…do I need to install USB drivers and how would I do that on Ubuntu.
Any help would be greatly appreciated...
Type in adb devices.
Does it list your device there?
Most likely it's a driver issue when it says "waiting for device."
I know nothing about ubuntu though so i wont be any help getting those drivers installed.
Yes it does before I get into the bootloader. After I get into the bootloader I get nothing.
Sent from my PC36100 using XDA Premium App
adb not reconized
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx
wmchristian said:
Hello First thank you soo much for this wonderful information.
Sorry in advance if i am just not smart enough to follow your wonderful directions on how to overclock but when i put in adb my Command prompt says it is unreconizable and will not get past that. it is rooted i did that the other day thx
Click to expand...
Click to collapse
Make sure you are running the commands from the directory on your computer that the adb file is in. For example, make sure you do a CD "\Program Files\Android\android-sdk\tools" if that is where adb and all the necessary files are.
thx for reply
Thought I did ill try again this weekend to over clock my xoom never was good at dos.
I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
CoatedMoose said:
I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
Click to expand...
Click to collapse
Did u try to do a adb remount then try adb devices
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
CoatedMoose said:
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
Click to expand...
Click to collapse
Did u download motohelper drivers so your adb will recognize the device
if the xoom is in fastboot adb wont recognize it hold power and volume up to reboot and try again
The xoom is recognized already. I am able to send the adb reboot bootloader command. When the xoom is trying to load into fastboot, it is not visible, which makes it impossible to enter the oem unlock command.
I gave up on the device, I was having issues with geolocation as well which didn't exist on another device. I returned the device and am waiting to receive the 3g version from the US.
I have the same problem. Does anyone know how to get around this?
Sent from my Xoom using XDA Premium App
If when you can run the adb reboot bootloader command and don't get fastboot to work, then as yet I have not found a solution. Instead I just returned it and ordered the 3g version from verizon and had it shipped. The commands worked fine. If you cannot use the adb command to reboot, then check the instructions for installing adb and fastboot and/or post the error messages you are getting.
On a side note, where did you get your xoom (country/store etc). I wonder if it is a problem with a certain batch, or all the Canadian ones etc. I my wifi only version from bestbuy in Canada.
I'm having the same problem right now on my xoom.
I was preordered on Amazon and delivered to New York 3 weeks ago...
no solution as for now..
returning isn't an option for me, since I live in Poland :/
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
I'm not sure if you're using Windows or not but I didn't had any issues when I used fastboot. Just need to make sure you have the drivers installed, and when you do adb reboot bootloader check the device list to make sure it still shows your device listed in there and not as a question mark. If you don't see your device listed in the Device List or does show but with a question mark, double check to make sure you have the drivers installed or else fastboot will not work.
And don't bother trying to use adb when you're in the bootloader since adb will not work.
*** edited: just noticed now that you are using ubuntu 10.10 (I need to stop over reading stuff). Can't remember how the drivers aspect works in Linux since it's been forever since I've used a Linux flavor but you will still want to make sure you have the correct drivers installed or make the changes that niematunikogo did and see if that worked.
niematunikogo said:
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
rrainz said:
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
Click to expand...
Click to collapse
before typing all the commands, first type "sudo su". adb and fastboot both need to be executed as root (adb actually works without root in case you already edited the USB rules before)
I had same problem but just returning device was not what I intended to do
niematunikogo said:
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
This worked for my Ubuntu, thanks!
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
The solution is well documented on the web: Install new drivers. I have been installing drivers from just about everywhere for the last week without success. With the phone connected, I get this from Device Manager:
Computer
Android Device
Android Composite ADB Interface
The driver information is as follows:
Driver Provider: Google, Inc.
Driver Date: 7/9/2013
Driver Version: 8.0.0.0
Driver Signer: Google, Inc.
Driver Details:
Driver Files:
C:\Windows\System32\Drivers\Winsub.sys (File Version 6.2.9200.16384(Win8_rtm.120725-1247))
C:\Windows\System32\WdfcoInstaller01009.dll(File Version 1.9.7600.16385 (Win7_rtm.090713-1255)
C:\Windows\System32\WinUSBCoInstaller2.dll (File Version 6.1.7600.16385 (win7_rtm.090713-1255))
I am running a Dell XPS-17 I7 laptop with Windows 8 (not 8.1) 64 bit
If I could find a way to unlock without using Fastboot, that would probably be a good solution, but I can’t. And I have absolutely no success at getting Fastboot to work.
I do notice that the Device Manager lists Android Composite ADB interface (ADB works) but noting about a Fastboot interface. Does that mean anything?
Please help I am at my wit’s end.
For what it is worth, I did read all the tutorials here, and the only thing I could figure out was if I have the right drivers everything works fine. I also reviewed the posts here, including "Diagnosing USB Driver and ADB issues in Windows," which discusses ADB (which I have no problem with)
this article helped me out a bunch. http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
you'll have to edit the "android_winusb.inf" with the correct hardware id.
in Device Manager make sure you go to "Android Device" > "Android Composite ADB Interface" go to Properties. on the Details tab and then click on the drop down box and select "hardware ids" you might see 2 ids there. i believe the one you'll need is the bottom one. if you only have one. thats fine too.
so, read the article. grab your hardware id and edit your driver. see if it works. you may have to reboot after you edit the driver. hope this works for you.
krdu said:
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
Click to expand...
Click to collapse
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Sounds like you need to boot your phone into fastboot mode. Power off the phone and hold volume down and hit the power button.
Then the fastboot devices command should work and you should be able to unlock the boot-loader then. Unlocking the boot-loader will wipe your phone just so you know.
erikivy said:
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Click to expand...
Click to collapse
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
You realize that the two command line interfaces (ADB and fastboot) don't work in the same state, right? ADB is for use in recovery and while booted, whereas fastboot only works in bootloader. It sounds to me like everything is working exactly as it should.
I'm no expert or anything, but I always assumed that they were two different ways to interact with your device while it is in different states. If I'm mistaken, someone please correct me.
krdu said:
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
Click to expand...
Click to collapse
ADB is used in android and the recovery.
Fastboot is used only in the bootloader.
Aloha. So I lost my HTC One X. Sucks cuz I loved it. So I picked up a used one off of ebay. Looks new, everything great....EXCEPT... It's stuck on 4.0.4 and I hate it. I tried the OTA via Wifi and get the error message service unavailable. I took it to the ATT store...they said "Um try somewhere with stronger wifi." Then downloaded Htc one x RUU 5.18.502.1 and installed Htc Sync manager. Everything would start out great, and then it waits for the bootloader, I lose the usb connection between the phone and the computer at the exact same point every time I attempt the RUU update. Its always as the computer is waiting for the phones bootloader to start. The computer says connection lost, and the phone gets stuck on a black screen with a white htc logo. I'm soooo stuck. Need help badly. Here's some more info. Andriod Version:4.0.4
HTC Sense- 4.0
Kernel Version 3.0.8-01558-g7f75e5b
[email protected] ABM009 #1
SMP PREEMPT
Any help or instruction anyone can offer would be much appreciated. As I stated above, I am noob... But I take instruction well. Thanks for taking the time to read this.
Take a look here: http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html.
Its a tutorial for one s but method is same
adamussg said:
Aloha. So I lost my HTC One X. Sucks cuz I loved it. So I picked up a used one off of ebay. Looks new, everything great....EXCEPT... It's stuck on 4.0.4 and I hate it. I tried the OTA via Wifi and get the error message service unavailable. I took it to the ATT store...they said "Um try somewhere with stronger wifi." Then downloaded Htc one x RUU 5.18.502.1 and installed Htc Sync manager. Everything would start out great, and then it waits for the bootloader, I lose the usb connection between the phone and the computer at the exact same point every time I attempt the RUU update. Its always as the computer is waiting for the phones bootloader to start. The computer says connection lost, and the phone gets stuck on a black screen with a white htc logo. I'm soooo stuck. Need help badly. Here's some more info. Andriod Version:4.0.4
HTC Sense- 4.0
Kernel Version 3.0.8-01558-g7f75e5b
[email protected] ABM009 #1
SMP PREEMPT
Any help or instruction anyone can offer would be much appreciated. As I stated above, I am noob... But I take instruction well. Thanks for taking the time to read this.
Click to expand...
Click to collapse
Wrong forum mate here is the International One X /ENDEAVORU/ forum not AT&T /EVITA/
adamussg said:
Aloha. So I lost my HTC One X. Sucks cuz I loved it. So I picked up a used one off of ebay. Looks new, everything great....EXCEPT... It's stuck on 4.0.4 and I hate it. I tried the OTA via Wifi and get the error message service unavailable. I took it to the ATT store...they said "Um try somewhere with stronger wifi." Then downloaded Htc one x RUU 5.18.502.1 and installed Htc Sync manager. Everything would start out great, and then it waits for the bootloader, I lose the usb connection between the phone and the computer at the exact same point every time I attempt the RUU update. Its always as the computer is waiting for the phones bootloader to start. The computer says connection lost, and the phone gets stuck on a black screen with a white htc logo. I'm soooo stuck. Need help badly. Here's some more info. Andriod Version:4.0.4
HTC Sense- 4.0
Kernel Version 3.0.8-01558-g7f75e5b
[email protected] ABM009 #1
SMP PREEMPT
Any help or instruction anyone can offer would be much appreciated. As I stated above, I am noob... But I take instruction well. Thanks for taking the time to read this.
Click to expand...
Click to collapse
Before you run any RUU you need to check that you don't have SuperCID, because SuperCID + s-on + jb RUU = brick. I'm assuming you have a working fastboot environment, if not you'll need to set that up first, if you don't know how Google is your friend. Anyway, issue this command and post the result.
Code:
fastboot oem readcid
Post your bootloader details too please.
Aloha. Thanks for taking the time to read my post. I have trying to figure this out on my own for a while now and am ready to lose my mind...lol So her's what I have for ya.
***Locked***
EVITA PVT SHIP S-ON
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
Open DSP-v29.1.0.45.0622
eMMc-boot
Jun 11 2012,14:36:28
HBOOT
I am running Win 8 which is a major pain in the ssa. I have read so much I'm really frustrated that I can't figure this out on my own. So I have downloaded and installed android sdk on my computer, java runtime,HTC sync manager, and java eclipse. I know I need to unlock my bootloader... but can't. Here's my dilemma. I enter bootloader screen on my phone. I select fastboot. I hook it via usb to my computer. Windows says it doesn't recognize the device that was connected. I open cmd... C:\Users\Awesome\ cd\android gets me ...system cannot find the path specified. So Timaaa , I can't even enter what you have requested. I'm ready to sell this thing on ebay(even though I just got it off of there.) and get one that has already been updated Any suggestions?
Instead of using the "cd" command to get to your fastboot folder you can just open the command prompt from within that folder. Navigate to your fastboot folder on your PC (usually c:\android), press shift + right click, select open command prompt here. Now you should be able to give fastboot commands. To check your connection you can use this one:
Code:
fastboot devices
It should return the serial number for your device.
Sent from my Evita
Okay.. So I got to where I think I needed to be... and typed fastboot oem readcid.... and it just said waiting for device.....and sticks there.... also, where do I get my bootloader details to post them? lol I feel like such a hopeless noob. Bleh
You've already posted your bootloader details above. As far as getting fastboot to work on Windows 8 goes, it's a pain in the butt, it took me days and to be honest I can't even remember which method ended up working for me. It isn't 8.1 is it?
Sent from my Evita
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Awesome>fastboot devices
C:\Users\Awesome>fastboot
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
format <partition> format 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
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\Awesome>C
Crap it is 8.1 I'm going to fire up my old laptop with win 7, install everything on that one... get back up to the point I;m at now... and I'll be back. Thanks for your help and patience.
Ahh, glad you said that before we spent too much time trying to get fastboot working on 8.1, which will never happen. Windows 7 should be fine.
Sent from my Evita
So I'm now on win 7... and fastboot oem readcid gets me <waiting for device> just like it did in win 8. The phone is turned on, and connected via htc sync manager. Should I be in the bootloader when issuing this command?
So now I'm on Win7, and entering fastboot oem readcid gets me <waiting for device> Just like it did in win 8. It just hangs. I am connected via usb using htc sync manager and the phone is turned on... but not in the bootloader. Should I be in the bootloader when issuing this command?
Yeah, fastboot commands only work when you're connected in fastboot mode (device in bootloader). If you continue to have problems getting it to connect, uninstall HTC Sync Manager, it can get in the way. Leave the drivers installed obviously.
Sent from my Evita
So I get <bootloader> cid: CIS__001
OKAY [0.013s]
finished. total time: 0.014s
cid CWS not CIS
Ok, you're good to go. But to run the RUU you definitely want to uninstall HTC Sync Manager (again, leave drivers installed), it only gets in the way. I'd put the phone in fastboot mode and initiate the RUU, sometimes you need to do that.
But, here's one very important note:
If you ever want to unlock your bootloader, root your phone, install custom ROMs, you must do it before you take this update or you'll never be able to.
Even if you don't want to install custom ROMs, by unlocking the bootloader you can install stock(ish) ROMs that would allow you to use tethering, which is deliberately broken on at&t ROMs. So even if you don't want to do it now, if there's even a slight chance that you'll want to do it in future, you must unlock the bootloader before taking this update via the RUU.
Sent from my Evita
So.. I decided that I am not going to unlock, or do anything else to my phone other than the 4.2,2 update. I am fine with that and will probably keep the phone for another year and then sell it on ebay. So, I went into bootloader, Ran the RUU from my desktop, and got to where it tried to connect with my phone. And then I get error.170 usb connection error... I haven't uninstalled htc sync manager, but will try doing that and will keep the drivers.
Ok so can't run RUU when connected via bootloader... and can't connect unless connected to sync manager which I am now reinstalling. Bleh What a nightmare..
What do you mean can't connect unless connected to sync manager? Are you using a usb 2.0 port? Are you using an original HTC cable?
Sent from my Evita
My OnePlus One just went screwy on me and so I tried to do a reset with TWRP. The factory reset didn't work. The phone is in a bootloop as the loading screen stays on and that's it. I noticed in recovery that the " /persist" file could not be mounted so I figure it's corrupted. The problem is this: NO drivers can be loaded and my phone will not be recognized in device manager, OPO toolkit, or any other means! This thing is bricked!! I tried ADB, Google, Samsung, and Universal drivers to no effect. I just don't know how I can get my phone recognized again. It did at one point come up as QSHub or something like that but I can't even get that now. Fastboot mode comes on my phone but does nothing and the MTP USB device driver will not install! I don't know what to do and just wasted 6 hours trying to figure this out! I am not very savvy with phones when it comes to this sort of thing. I can root a phone but that's as far as I can go comfortably. If someone has a solution to this problem, please advise me but you may have to hand hold me through it as I am not really up on how to do things the way they may have to be done. Thanks!
Your phone isn't bricked. Are you making sure that you reboot your PC after each uninstall and install of any drivers?
XDA Moderator
Transmitted via Bacon
Yes, I rebooted after installation of any drivers. It didn't make any difference as my phone still wasn't recognized by my computer.
Alright, maybe try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
XDA Moderator
Transmitted via Bacon
Well, my phone is recognized when I type "fastboot devices" but I do not know where to go from here. I got the device to be recognized using info from http://forum.xda-developers.com/show....php?t=2839471. According to your guidelines in [GUIDE] [UNBRICK] Unbrick Oneplus One, I am soft bricked, it would seem. What should my next step be? I tried to unlock the bootloader but it gives me this in the CMD window.
C:\Users\Se7en\Desktop\MTP>fastboot devices
5e1c4e77 fastboot
C:\Users\Se7en\Desktop\MTP>fastboot oem unlock
...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Se7en\Desktop\MTP>fastboot oem device-in
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So what is the next step to get this thing working? Am I heading in the right direction or am I getting ahead of myself?
Thanks in advance for any help
kristorm said:
Well, my phone is recognized when I type "fastboot devices" but I do not know where to go from here. I got the device to be recognized using info from http://forum.xda-developers.com/show....php?t=2839471. According to your guidelines in [GUIDE] [UNBRICK] Unbrick Oneplus One, I am soft bricked, it would seem. What should my next step be? I tried to unlock the bootloader but it gives me this in the CMD window.
C:\Users\Se7en\Desktop\MTP>fastboot devices
5e1c4e77 fastboot
C:\Users\Se7en\Desktop\MTP>fastboot oem unlock
...
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Se7en\Desktop\MTP>fastboot oem device-in
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.005s]
finished. total time: 0.005s
So what is the next step to get this thing working? Am I heading in the right direction or am I getting ahead of myself?
Thanks in advance for any help
Click to expand...
Click to collapse
If you've got fastboot working you're on your way. Your bootloader doesn't seem to be unlocking though, did you relock it at some point? If so, why? As long as you still have TWRP installed you can flash a token to unlock it again (this won't wipe your data). You'll find it in this thread:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
So just flash that and your bootloader will unlock. Then download this:
https://docs.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Put it in your fastboot folder on your PC, put your phone in fastboot mode and connect it to your PC, then issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
XDA Moderator
Transmitted via Bacon
Heisenberg said:
If you've got fastboot working you're on your way. Your bootloader doesn't seem to be unlocking though, did you relock it at some point? If so, why? As long as you still have TWRP installed you can flash a token to unlock it again (this won't wipe your data). You'll find it in this thread:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
So just flash that and your bootloader will unlock. Then download this:
https://docs.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/edit?usp=docslist_api
Put it in your fastboot folder on your PC, put your phone in fastboot mode and connect it to your PC, then issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't relock it, at least I didn't set out to intentionally lock it. Through my experimentation to get this phone running again, it is very possible that I may have. I'll try the info you gave me and let you know. Thanks very much!
Sorry for being a noob but do I unzip the Bootunlocker.zip file you directed me to or leave it as is? Secondly, what is the exact procedure to flash this with TWRP? I just don't want to make any mistakes as this is all new to me. Thanks!
kristorm said:
Sorry for being a noob but do I unzip the Bootunlocker.zip file you directed me to or leave it as is? Secondly, what is the exact procedure to flash this with TWRP? I just don't want to make any mistakes as this is all new to me. Thanks!
Click to expand...
Click to collapse
Don't unzip it, just transfer it to your phone, then go to the install menu in TWRP and find the zip on your phone and swipe tip install.
XDA Moderator
Transmitted via Bacon
There's the problem: My phone isn't being recognized in Windows so I cannot transfer anything to it. How can that be remedied? The driver software for QHSUSB cannot be found and MTP device fails to install all the time!
EDIT: I think I got it! I changed the USB ADB interface driver and it recognized my phone as "One". I can now follow your instructions. I will keep you posted.
IT FREAKING WORKED!!! I am sooooo happy right now. Thank you so much!!! You can't believe how grateful I am for your help with this! Fantastic! This is awesome!! I sent you a small token of my appreciation
kristorm said:
IT FREAKING WORKED!!! I am sooooo happy right now. Thank you so much!!! You can't believe how grateful I am for your help with this! Fantastic! This is awesome!!
Click to expand...
Click to collapse
Awesome, I'm very glad to see it worked! You're welcome, happy to help.
XDA Moderator
Transmitted via Bacon
The only thing I can see right now is that I do not have a keyboard. How do I get that back?
kristorm said:
The only thing I can see right now is that I do not have a keyboard. How do I get that back?
Click to expand...
Click to collapse
You don't have a keyboard at all? Haven't seen that before. So there's no keyboard at all showing up when you go into Settings/Language & Input?
XDA Moderator
Transmitted via Bacon
I guess this process wiped all my data because it's asking me to set up my accounts again. However, when I go try to input anything, I only have Google voice and no keyboard. Sometimes I see a keyboard icon but it doesn't respond when I touch it. If I could access my settings, I'm sure I could change things but obviously, I can't at this point.
kristorm said:
I guess this process wiped all my data because it's asking me to set up my accounts again. However, when I go try to input anything, I only have Google voice and no keyboard. Sometimes I see a keyboard icon but it doesn't respond when I touch it. If I could access my settings, I'm sure I could change things but obviously, I can't at this point.
Click to expand...
Click to collapse
What you could do is access the Play Store on your PC and find a free keyboard to install, press the install button in the web browser on your PC and it'll download the keyboard to your phone.
XDA Moderator
Transmitted via Bacon
Great idea. I'll do just that. Thanks!
It doesn't work. The keyboard file isn't being pushed to my phone. SUX! Cannot root either as OPO toolkit says no ADB device detected (debugging on). Also, the log from OPOTK says that my device is unauthorized.
Here's the log:
Information: Checking ADB Status
adb devices
List of devices attached
5e1c4e77 unauthorized
Any thoughts to any of these things mentioned?
kristorm said:
It doesn't work. The keyboard file isn't being pushed to my phone. SUX!
Click to expand...
Click to collapse
Bummer. It might be time to start from scratch. Go to my guide and follow section 8 to flash the stock images with fastboot, just don't flash the userdata image or you'll wipe your internal storage.
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon
kristorm said:
It doesn't work. The keyboard file isn't being pushed to my phone. SUX! Cannot root either as OPO toolkit says no ADB device detected (debugging on). Also, the log from OPOTK says that my device is unauthorized.
Here's the log:
Information: Checking ADB Status
adb devices
List of devices attached
5e1c4e77 unauthorized
Any thoughts to any of these things mentioned?
Click to expand...
Click to collapse
Get rid of the toolkit, it really isn't needed for this phone, and they cause more problems than they're worth. If you want to root all you need to do is download the SuperSU zip to your phone and install it with TWRP. I'd suggest flashing the stock images as I've described above though.
XDA Moderator
Transmitted via Bacon