Develop Bugs

fastboot mode not working

hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers

WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.

Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie

WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/

Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse

ADB device offline - after upgrading TWRP and 4.2 ?

So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?

Nobody?

hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
hxdrummerxc said:
Nobody?
Click to expand...
Click to collapse
only thing i can think of right now, before suggesting omap flash or odin, would be try a different usb port, another computer, another OS!

try installing the latest CWM recovery and see if it helps.

hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
Try going to settings and look for something related to Root Access and it would have three options:
1. Apps only
2. ADB only
3. Apps & ADB
Choose the 3rd.
You might have to hunt the exact location under Settings where this option will be available as I don't remember them exactly.
Hit Thanks, if this helps...

I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.

hxdrummerxc said:
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
Click to expand...
Click to collapse
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.

freezer2000 said:
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
Click to expand...
Click to collapse
hi. i try all this ways. i know that my usb debuging have problem, in development option i'll checked this, and it says enable. but infact it's not enable and still i got device offline error.
also i use z4root app and when i touch on root, it says that rooting need usb debuging enable (please enable it)!!
then move me to development setting to enable that, but this was checked and enable.
is any way that we make device online from my phone? for example using terminal emulator to turn on usb debuging or turn it off. this way is only my way! any one know some trying this?
i also use usb debugger app, but it move me in settings too! LOL
i need enable my device to root that.
thanks every one

I know this is an old topic, but if somebody else googles it, I had that offline issue, the solution was to upgrade adb : http://stackoverflow.com/questions/10680417/error-device-offline

You simply need to upgrade to the latest version of adb. Went thru this a few weeks ago.

[Q] Problems in adb/fastboot

Hey all,
I've been rooting phones for a little bit, so when I got my Nexus 7 a couple weeks ago and found that it was as simple as "fastboot oem unlock", I was thrilled. However, it ended up not being that simple, of course.
At first I couldn't get the device to show up for ADB or fastboot at all, even though Windows recognized the device. I downloaded the zip file of the drivers from Google, no luck. Downloaded a new version of the Android SDK, and used the adb/fastboot from it, and then ADB was able to see the N7 and was able to reboot it into the bootloader. However, once in the bootloader, it stops recognizing that the N7 is connected again. Trying "fastboot oem unlock" just causes the program to display <waiting for device> indefinitely.
So that's where I'm stuck now, I haven't been able to find any concrete details on this that are for the N7 2013 (pretty much everything I've found has either not been helpful or has been related to the original N7). Anyone able to help from here? Thanks!

Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One

DowntownJeffBrown said:
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
Click to expand...
Click to collapse
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.

tigerxchaos said:
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
Click to expand...
Click to collapse
When you have the device connected to your computer when it's at the Bootloader screen, what does Device Manager show on your computer? Does it recognize the tablet but doesn't know what it is? You may need to install the drivers when you have the device in the Bootloader menu. I use the Google USB Driver (which you can download in the SDK Manager), right click on the device in Device Manager, select "Update Driver Software", "Browse my computer for driver software", "Let me pick from a list of device drivers on my computer", then browse the list. It may be listed under Android Device, Google...just look down the list, then select the appropriate driver. I believe from there you can select "Android Bootloader Interface", and that should let fastboot commands work.
You may need to reboot the computer.

Make sure you are using the usb cable that came from asus.

Thanks for the help. I tried the process again on a different computer, and eventually got it to work. I was able to unlock bootloader and flash TWRP 2.6.3.0. However, I was only able to mount System, Cache, and USB-OTG as partitions in TWRP, so I couldn't figure out where to drop the SuperSU binary .zip file. I tried rebooting, and (this may have been a mistake) installed the TWRP SU binaries on the way out. Now the device is stuck in a bootloop. Not sure if it was related to the SU binaries or the fact that I couldn't load any sort of data partition. Any thoughts?
EDIT: Apparently the root instructions don't make it clear that you will lock your data partition if you don't boot the device after unlocking the bootloader. I went straight into TWRP from the bootloader after unlocking it, and got a password request. Hit "Cancel" and it let me into TWRP, but factory reset failed. I had to wipe data, wipe cache, then reboot, then do a factory reset and now I'm back in.

[H811] ADB Broken after Rooting?

Yesterday I decided to install ClockworkMod. I was running 6.0.0 Marshmallow
I unlocked my bootloader no problem. I decided to root before I flashed the rom. I booted into TWRP using adb, made a nandroid backup, and flashed stock-20a-rooted.zip (I was following this guide). It worked! I used a rootchecker app to ensure I had a good root. Then I went to boot into TWRP to install ClockworkMod. I turned off my phone and did the volume down + power thing, but I got the LG hard factory reset screen. So I decided to use ADB instead and rebooted my phone. However, when I tried to use adb, my device was listed as "unauthorized", and I haven't been able to use adb since! Here's what I tried (but not necessarily in this order):
Using the LG hard factory reset. Nothing changed.
clearing adbkey file on my computer. Nothing changed.
using a different computer with fresh adb and driver install. Nothing changed.
rebooting both PCs. No dice.
tried mtp and ptp on device. Neither worked. Device was not recognized on MTP (used to be recognized by adb when it was on mtp.) device was recognized on ptp, but it was listed as "unauthorized"
tried to revoke usb debugging in settings on device. That option wasn't listed in developer options.
tried to clear adbkey on device and found out that my device still hadn't generated an adbkey file!
throughout this whole time, whenever I plugged in my device, the NSA fingerprint dialog box DID NOT APPEAR.
Questions, thoughts on potential solutions:
can I somehow unroot or go back to stock? I heard we can't do this anymore because it bricks our phones....
I feel like this has something to do with how my device never created an adbkeys file.

SOLUTION
I have been working on this today and I found a solution. I had read that downgrading/unrooting bricks our devices, and so I had ruled it out as an option. After further research I found that we can revert to stock without downgrading and avoid a brick. Since I have an H811 on 20o, I found firmware here and flashed it using LGUP, which you can find here. I suggest using this link to learn how to flash the firmware. After that, ADB worked fine and the NSA fingerprint dialog once again showed up on my device when I ran ADB. Good luck to any of you with the same problem!!! Reply if you need help.

No ADB. No TWRP. No Magisk. Am I screwed?

Basically, I installed Havoc OS, tried flashing a couple kernels, kept getting systemui crashes, so I decided to dirty flash HavocOS again, and forgot to flash TWRP again before I exited TWRP.
Next, I boot back into my phone, opened Magisk Manager to find that Magisk is not installed, just the manager. I can't install Magisk as I have no TWRP...Which leads me to my next point, trying to boot into recovery brings me no avail as I forgot to flash TWRP. I have zero recovery right now.
Thirdly, HavocOS Suffers from the whole issue of needing SELinux set to permissive, for ADB to work...I can't do that, because I don't have Magisk/root.
Please tell me that someone has an idea here? I'd like to get TWRP back, or back to 100% stock and I can start over, or something other than a custom rom with serious SystemUI crashes and no root...
SOS!

This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.

As d-m-x stated boot twrp with fastboot boot not fastboot flash. Twrp will load into the phone then you can flash twrp and magisk.

I'd tried Fastboot already, will try again momentarily though.

D-m-x said:
This is not even close to a softbrick. Just boot TWRP using Fastboot and flash the zip from inside TWRP to install it. Also, there are various other solutions to fix your problem. Another one would be to simply use Deuces Recovery Script and go back to Stock.
Click to expand...
Click to collapse
Fastboot hasn't worked either. Unless I'm doing something wrong, but I just get "waiting for any device" despite having adb on/off, being in bootloader/fastboot mode or being booted into android, etc.

For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.

D-m-x said:
For Fastboot to work you have to be in the Bootloader Menu. How did you unlock and root your Phone in the first place? That should have taken you through those steps.
Anyways, it's likely that the computer just doesn't recognize the phone. Connect it and go into your Device Manager and see if it's properly recognized. If not install the correct USB Drivers and try again. If everything is set up correctly you can type "fastboot devices" while in the bootloader and you should see your Devices address which means it is connected and ready. Then boot TWRP as stated and install the zip from within.
Click to expand...
Click to collapse
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.

Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Have you tried different USB A to USB C cables and ports?

Dragostini said:
Bootloader is unlocked etc. I initially did everything using the P2XLToolskit 2.0
You're correct, I think its simply a case of the PC not recognizing the device. I've already checked device manager, and it's not properly installing the device. I've multiple times tried reinstalling the universal driver, and various other fixes. I think it relates to the whole issue of HavocOS being screwy about USB. Many people have reported issues with USB recognition issues when ADB is turned on. The consensus from how I understand it, is that ADB ON = Phone won't be recognized. ADB OFF = Device should be recognized for file/data transfer...However even with ADB off my PC is still not installing drivers properly / recognizing the device.
The Device Manager lists my device as "Unknown USB Device (Device Descriptor Request Failed)"
Also tried:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
^ did not work.
Click to expand...
Click to collapse
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!

Az Biker said:
Try these troubleshooting steps:
- make sure you're running the LATEST SDK Tools
- Try diff USB cables (switch from 2.0 to 3.0, or vice versa)
- Try a diff USB port
- Make sure you're in the proper fastboot folder with the fastboot application
- Boot into bootloader type fastboot devices see if you get a serial number
In my sig is a link for troubleshooting, and step by step that includes links to get latest SDK Tools.
If all else fails, I'd reco a fresh factory image install and get back to your cust Rom from there, rather than spend a day or two chasing ghosts.
Good luck!
Click to expand...
Click to collapse
Spoke with Google; getting the phone RMA. Blatantly told the guy it was rooted previously, bootloader unlocked, and running a custom ROM. He said it didn't matter. I will report back on this thread once I have new phone in hand, just to confirm all went well.

Reporting back.
Brought phone to virgin mobile, obviously still heavily modified.
Was given a loaner phone. Signed a paper saying I'd pay 150 for the loaner if it broke. Broke loaner screen same day.
Just picked up a brand new pixel 2 xl they shipped (phone only) because mine was considered unrepairable. I was charged 169 for the loaner phone, to my account with virgin. No cash transaction.
All in all, they honoured googles view of not minding the modifications so long as it's an issue they don't feel is related.
Cheers.