Database Users

[Q] adb / fastboot issues

Using a linux PC I was attempting to unlock my bootloader following the directions at http://www.geek.com/articles/mobile/how-to-unlock-and-root-the-nexus-7-2012081/.
I can execute adb reboot bootloader just fine.... however when I issue the fastboot oem unlock command nothing happens on the tablet, and I see "< waiting for device >" in the terminal window. If I CTRL-C to break out and then do a 'adb devices' I see that there are no devices listed.
The Nexus 7 is a stock 16gb, C70 running 4.1.2/JZO54K.
Probably unrelated - I noticed in the last couple of weeks that the tablet has become slugging/laggy. Available space was at about 2gb. I removed some storage hungry games and got available space back up to about 5.5 gb.... but it's still laggy and touch detection barfs on occasion.
Any help/advice would be greatly appreciated.

Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Being on Linux make sure hat your fastboot command either has suid-bit set and owner is set to root or you need to run the command by sudo:
sudo fastboot devices
For adb there should be no problems, but adb is not working if your device is in fastboot mode.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Uggg.... Years of using Odin has made me stupid and lazy.... sudo did the trick. Thanks!!

[Q] Adb not recognize in fastboot[Q]

I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.

YoungCorruptionV2.0 said:
I tried updating my nexus 7 to 4.2.1 and i thought everything went okay but now adb doesn't recognize my device in fastboot and i can't boot up my nexus 7 because everything got wiped on my sd card. I can boot into recovery but i can't mount my sd card either. It tells me there is an error. Apparently there is no OS installed. Any help is welcomed.
Click to expand...
Click to collapse
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.

RMarkwald said:
You can boot into the bootloader, and use fastboot commands to reflash the stock Android 4.2.1 OS.
Click to expand...
Click to collapse
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2

YoungCorruptionV2.0 said:
Fast boot commands don't work because adb can't recognized my device while in fastboot. I tried "adb devices" and no devices were listed
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can't use adb in fast boot . Reboot to the boot loader. If you type 'fastboot devices' in fast boot your phone will show
Sent from my One X using xda app-developers app

I had the same problem.
What version of adb.exe Ade you using?
The latest is dated sometime in November this year. If it's earlier than that, download the SDK from android development site and use newer version of adb.exe
That should fix the issue...
Sent from my Nexus 7 using xda premium

From bootloader use fastboot commands, from recovery use adb commands.

You can't do adb commands in fastboot mode. To do adb commands you either need to be in Android or in a recovery.
Sent from my Nexus 7
Stop... MUFFIN TIME!!!

If you have twrp recovery installed you can boot to recovery and use adb sideload.
So just download a rom on your computer boot to recovery and sideload the rom to your device and then install it.
Not sure if this can be done with cwm though
Sent from my Nexus 7 using Tapatalk 2

[Q] Nexus 4 boot loop caused by toolkit

Hi guys, I have read several threads on here already so just to let you know Im not just making a thread at the first sign of trouble.
Heres my predicament:
I used a tool kit ( nexus 1 click toolkit for mac) to try and root my phone, which after diving in and pressing enter, found that they seem to be the work of the devil. So it unlocks the bootloader no problem but it cant push the su file to the nexus and comes up with this text :
Pushing UPDATE-SuperSU-v1.45.zip...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
after this it installed cwm, but obviously the su file isn't there so I can't install zip from sd card.
I've tried formatting personal data (which cwm says cant mount sdcard/android_secure, skipping format) and formatting the dalvik cache and rebooting with no avail.
I'm running a mac but can get access to a pc if absolutely necessary, at the moment I don't mind if I don't have root, having my phone back is priority!
Thanks for you help in advance.

dont use toolkits, do it the right way.
fastboot oem unlock via fastboot, fastboot flash a custom recovery, flash the latest supersu in you new custom recovery, reboot. thats it.

simms22 said:
dont use toolkits, do it the right way.
fastboot oem unlock via fastboot, fastboot flash a custom recovery, flash the latest supersu in you new custom recovery, reboot. thats it.
Click to expand...
Click to collapse
Hi thanks for putting me on the right track, when i put in ./fastboot devices
0042642ea095831a fastboot
it does come up with the serial number but when i put in ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
the list of devices attached is blank, any ideas? leading me to think i don't have debugging on
is there a way of turning debugging on from terminal?

Jack_R8 said:
Hi thanks for putting me on the right track, when i put in ./fastboot devices
0042642ea095831a fastboot
it does come up with the serial number but when i put in ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
the list of devices attached is blank, any ideas? leading me to think i don't have debugging on
Click to expand...
Click to collapse
its fastboot, adb doesnt work in fastboot.

simms22 said:
its fastboot, adb doesnt work in fastboot.
Click to expand...
Click to collapse
Just to let you know i got it fixed, thanks a lot :good:

Bricked L5.0.2 No ADB or USB

N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks

fr0d0#2 said:
N4 16Gb : Loliop 5.02, SimpleAOSPv11, AK Kernel, CWM Philz Touch 6.46.3
I foolishly ran "Clean to install new ROM" from Philz recovery (under "Factory Reset").
I don't have a ROM on the device to flash, and can't see the device over USB or ADB.
Can anyone help recover this please? Thanks
Click to expand...
Click to collapse
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
First off, you're not bricked. When you boot into recovery and your device connected to your pc what do you get when you run the command adb devices from a Windows command window?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks jd
I don't get anything no matter which mode I boot into

fr0d0#2 said:
Thanks jd
I don't get anything no matter which mode I boot into
Click to expand...
Click to collapse
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Are you on a Windows pc? Do you have adb and fastboot setup on the pc? Had the pc recognize the device in the past?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.

fr0d0#2 said:
Windows 8 with adb installed that has previously seen the N4, yes.
I've had an HTC M8 connected recently. Just now, before wiping, I was connected via USB.
Click to expand...
Click to collapse
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Ok, so it doesn't seem like a driver or software issue. With your device booted into recovery and connected to the pc what do you see the device in device manager? It should show up as an android adb composite interface, or something like that.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have an exclamation mark next to N4

Driver re-installed - now recognised as Android Composite ADB Device

fr0d0#2 said:
Driver re-installed - now recognised as Android Composite ADB Device
Click to expand...
Click to collapse
Good, download a rom.zip to your pc if you don't already have one. Then you're going to want to boot into recovery and push the zip to your device using adb. Once there you'll be able to flash it in philz
adb push rom.zip /sdcard/Download. I might have the / backwards. I always forget which way they go. For rom.zip use the full name of the rom. You'll want to have the rom.zip in the same folder as adb.exe and open your command window in that folder too.
Sent from my Nexus 9 using XDA Free mobile app

Thanks jd
You had the slashes the right way around - back in a bit

I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.

fr0d0#2 said:
I'm still not getting the device listed at the command prompt, and get an error saying the same when I try the push command.
WUGs toolkit says it's there and in fastboot mode, and says it's pushed the file successfully but there's nothing there.
Click to expand...
Click to collapse
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'm not that familiar with philz. Does it have an option to enable mtp when you're booted into it? If it did you can copy and paste the rom from your pc to the device. Twrp has that option under mount. I may have you boot into twrp with fastboot to use that option. How familiar are you with fastboot?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.

fr0d0#2 said:
Not that I can find JD. There are several mount options but USB doesn't work... because it's looking for an external source I presume.
Not very familiar.
Click to expand...
Click to collapse
Well,a good time to learn. Download the latest twrp image from here http://techerrata.com/browse/twrp2/mako. Rename it recovery for simplicity. I'm going to have you re-install fastboot from, Google 15 second adb install xda. That'll simplify the path issues using fastboot and adb, it sets an environment variable so you don't have to worry about the path to adb or fastboot.
Then open a command window in the same folder as the twrp image is in. With your device booted into the bootloader and connected to your pc run the command
fastboot boot recovery.img.
That'll boot you into the twrp recovery. Go to mount and in the lower right hand corner you should see and option to mount mtp. Then you should see your device in Windows just like you normally would. That should make it easy to copy and paste the rom.zip to your device. Once it's copied just install it using twrp. You shouldn't have to reboot or anything.
Sent from my Nexus 9 using XDA Free mobile app

Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:

fr0d0#2 said:
Thank you so much JD
twrp installed and mtp enabled - plain sailing from there on.
I owe you a pint :good: :highfive:
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 9 using XDA Free mobile app

For future reference a USB otg cord and pen drive would of been very easy and cheap glad you got it fixed!!
Sent from my LG-VS985 using XDA Free mobile app

Desire 626s All Things Root (BL unlock, Root, Rom, Recovery, Unbrick)

Root Guide: http://goo.gl/g3oTAW
RUU: http://goo.gl/JY3YzK
Kernel Source Code: http://goo.gl/iLFXwU
TWRP Recovery: https://goo.gl/sO4Huz
Cyanogenmod Recovery(and stock recovery): http://goo.gl/dbXyaA
S-Off($25)ADVANCED USE: http://goo.gl/o9kTmM
Credits
@jtrosky
@hackvcs
@Piplup702
@Captain_Throwback
 @jcase
Anyone else I may have forgotten
If anyone has questions please refer to the appropriate threads under the Q&A section

How To Unbrick/Return To Stock
WARNING: THE FOLLOWING METHOD WILL WIPE ALL DATA
Using the appropriate RUU from above you can return to complete stock to unbrick or unroot multiple variants of the Desire 626.
1) Boot device into download mode using VolumeDown and power while the device is off.
2) Open the folder you have Fastboot installed in and open a command prompt.(shift+right click=>open command prompt)
3) Type "Fastboot oem rebootRUU"
3a) Type "Fastboot oem lock" if your bootloader is unlocked.
4) Open the RUU and follow on-screen instructions.
5) The RUU process can take upwards of 10 minutes, so be patient. The first boot of your phone can take 1-5 minutes, again be patient.
6) If the RUU process fails or phone fails to boot up be sure to reply with an error code and a specific description of what happened.
This will put all partitions, including the recovery partition, to stock values. Effectively returning your device to complete stock

gingrbred said:
Root Guide: http://goo.gl/g3oTAW
RUU: http://goo.gl/JY3YzK
Kernel Source Code: http://goo.gl/iLFXwU
TWRP Recovery: https://goo.gl/sO4Huz
Cyanogenmod Recovery(and stock recovery): http://goo.gl/dbXyaA
Credits
@jtrosky
@hackvcs
@Piplup702
@Captain_Throwback
Anyone else I may have forgotten
If anyone has questions please refer to the appropriate threads under the Q&A section
Click to expand...
Click to collapse
fyi added 626s support to sunshine

jcase said:
fyi added 626s support to sunshine
Click to expand...
Click to collapse
That's amazing thank you

Ok, I'll bite - what is "sunshine"?
Sent from my HP SlateBook 10 x2 PC using Tapatalk

jtrosky said:
Ok, I'll bite - what is "sunshine"?
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
A commercial tool that sets devices s-off

jtrosky said:
Ok, I'll bite - what is "sunshine"?
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
its a tool to s-off your device which will allow you to alter protected partitions such as the bootloader

gingrbred said:
its a tool to s-off your device which will allow you to alter protected partitions such as the bootloader
Click to expand...
Click to collapse
Has this been Compared to different carriers? I'm on Verizon and don't even have the same system settings as other carriers do. I have no oem unlock function.
Sent from my HTCD200LVW using XDA Free mobile app

20twins10 said:
Has this been Compared to different carriers? I'm on Verizon and don't even have the same system settings as other carriers do. I have no oem unlock function.
Sent from my HTCD200LVW using XDA Free mobile app
Click to expand...
Click to collapse
well i would pm @jcase seeing as its a $25 license. But I don't think it will work because verizon generally locks things down pretty hard

20twins10 said:
Has this been Compared to different carriers? I'm on Verizon and don't even have the same system settings as other carriers do. I have no oem unlock function.
Sent from my HTCD200LVW using XDA Free mobile app
Click to expand...
Click to collapse
gingrbred said:
well i would pm @jcase seeing as its a $25 license. But I don't think it will work because verizon generally locks things down pretty hard
Click to expand...
Click to collapse
I would need to get my hands one one to see what i can do

Sunshine for firmware 1.23.1550.3?

who wants to help me build for this device?

[email protected] said:
who wants to help me build for this device?
Click to expand...
Click to collapse
What do you need?

I'm trying to build a device Tree. I have cm 1 2.1 sources downloaded and the source code for the device. I want to build cm for our phone.

Once u have the rom built I'll be glad to test it I got all my stuff on backup thanks to twrp

Will this root process work on the Desire 626s for Boost Mobile (Model OPM92) with Android 5.1 ?

After going back to stockRUU will this delete TWRP recovery and delete root?

Yes - you'll need to re-install TWRP and re-root.
Sent from my HP SlateBook 10 x2 PC using Tapatalk

TWRP Breaks ROOT
jtrosky said:
Yes - you'll need to re-install TWRP and re-root.
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
After restoring nandroid, it will not let me uninstall system apps or modify build prop.

I am tryign to return my device back to stock after a twrp mishap leaving my device with only twrp recovery. The problem i am having is my device is not recognized by my pc in bootloader mode or download mode. The only time adb devices shows my device is when im in twrp recovery. This is what happened.
C:\HTC626s>adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
FA5AVB000544 recovery
C:\HTC626s>fastboot oem rebootRUU
< waiting for device >
...
OKAY [ 0.007s]
finished. total time: 0.007s
C:\HTC626s>adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
C:\HTC626s>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\HTC626s>adb devices
List of devices attached
C:\HTC626s>adb reboot
error: device '(null)' not found
C:\HTC626s>adb reboot-bootloader
error: device '(null)' not found
C:\HTC626s>adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
FA5AVB000544 recovery
C:\HTC626s>fastboot oem lock
< waiting for device >