Database Users

Nexus one is not detected in ADB mode, yet detected in fastboot

Now I know what you are thinking: Well you need to install the drivers. Well that's all said and good, except the problem is when I boot int ADB (hboot? Unsure of what to call it.) There is no hardware at all being installed. At all. There isn't any devices that are connected and the computer doesn't detect anything. My problem is that my power button is broken, and I'm not quite able to get a new phone yet. Because of this, I cannot boot into recovery to flash a new rom, nor can I install Blackrose to use the trackball to avoid this problem. I'm just basically stuck because my phone is now a useless brick because I cannot flash a rom since I wiped my phone. Ideas?

try PASSIMG method?

will this help getting to recovery to flash rom without pwr button
http://forum.xda-developers.com/showthread.php?t=1419813

rugmankc said:
will this help getting to recovery to flash rom without pwr button
http://forum.xda-developers.com/showthread.php?t=1419813
Click to expand...
Click to collapse
Ha the ironic thing is I bought this and used it to wipe my phones rom because I was planning on installing blackrose and then QND. Sadly nope, because I can't get to the recovery itself because I can't press recovery on the bootloader bit.
////////////////
I'm unfamilliar with the Passimg method..got any links? I did a search but couldn't find anything.

Passimg is in wiki under nexus one, never used it--yet
So, not sure if it will help

Yeah not sure if it will work. If I read it correctly the OP wipe his phone clean, no OS or anything on it and can't get into recovery. I only suggest PASSIMG hopefully the phone pick it up upon reboot while holding down the VOL DOWN button.

ADB is a daemon that runs in OS, after the kernel boots.
You're booting into HBOOT. So you won't get anything but fastboot. This is normal and how it should be.
You can either use PASSIMG method, or open your phone and fix the power button for $30-something + having good hands, or even for $0 + thin wire + soldering equipment + very good hands, and optional microscope.

in this case would you be able to use fastboot boot recovery.img and restore a backup or flash a rom?

If you have unlocked bootloader - yes, by all means. But not without it.
The problem is that if power button failed, and bootloader isn't unlocked - you can't unlock it anymore, the procedure requires pressing power button to confirm.

did you try this tut on nexus one wiki?
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Unroot/restore
cheers

Question: If your power button doesn't work - how do you currently turn ON your phone?
Let's keep it simple and try the obvious first. Is USB Debugging turned on in the phone?
Go to Menu -> Settings -> Applications -> Development -> (check) USB Debugging.
2nd, make sure you have the android SDK installed on your computer (if so, download the usb drivers with the androidsdk app that's included).
You can also right click My Computer -> Manage -> Device Manager -> Make sure under Android Devices yours is listed and that there are no yellow question marks. If there is, do the android sdk drivers step and then right-click the icon in device manager, choose Update Driver and point it to the android sdk drivers folder.
Finally, ADB works in recovery and when phone it booted but NOT in Bootloader mode.
If you can get ADB working then you can install a custom recovery using Fastboot (in bootloader mode) then click Recovery to boot into the new recovery. Also, while in the recovery or ROM you can use "adb reboot recovery" to boot into recovery menu.
Hit Thanks if this helped.

Recovery menu, NO COMMAND?!

Hey guys! its what the title says, i can get into the bootloader mode fine but as soon as i hot recovery it comes up with an android on its back with a red sign, underneath saying " no command "
im trying to update to 4.2.2 with no luck
some people say press down and power but that just resets the phone for me -_-
any help, thanks

JackHanAnLG said:
Hey guys! its what the title says, i can get into the bootloader mode fine but as soon as i hot recovery it comes up with an android on its back with a red sign, underneath saying " no command "
im trying to update to 4.2.2 with no luck
some people say press down and power but that just resets the phone for me -_-
any help, thanks
Click to expand...
Click to collapse
Connect the phone to the cmd terminal on the pc and type: adb reboot recovery. You should have platform-tools from android sdk installed.

JackHanAnLG said:
Hey guys! its what the title says, i can get into the bootloader mode fine but as soon as i hot recovery it comes up with an android on its back with a red sign, underneath saying " no command "
im trying to update to 4.2.2 with no luck
some people say press down and power but that just resets the phone for me -_-
any help, thanks
Click to expand...
Click to collapse
I had to use flashboot over USB to upload CWM, then CWM protected itself and re-enabled root, I didn'tevn have to reflash super-su.
- get he recovery image recovery-clockwork-touch-6.0.2.3-mako
- flash it from bootloader:
- extract fastboot from the sdk (I extracted the whole sdk)
- restart phone while holding power+vol down (keep vol don pressed after release sing power)
- run "fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img" on your PC
- after selecting reboot it gave me the option to protect he recovery and resinstall super-su
- the right verison of super-su was already installed by CWM so I didn't even need to reflash UPDATE-SuperSU-v1.04.zip

papaschtroumpf said:
I had to use flashboot over USB to upload CWM, then CWM protected itself and re-enabled root, I didn'tevn have to reflash super-su.
- get he recovery image recovery-clockwork-touch-6.0.2.3-mako
- flash it from bootloader:
- extract fastboot from the sdk (I extracted the whole sdk)
- restart phone while holding power+vol down (keep vol don pressed after release sing power)
- run "fastboot flash recovery recovery-clockwork-touch-6.0.2.3-mako.img" on your PC
- after selecting reboot it gave me the option to protect he recovery and resinstall super-su
- the right verison of super-su was already installed by CWM so I didn't even need to reflash UPDATE-SuperSU-v1.04.zip
Click to expand...
Click to collapse
Im not rooted or anything like that, id rather stay as stock as possible

In stock recovery, hold power, press volume up.

USSENTERNCC1701E said:
In stock recovery, hold power, press volume up.
Click to expand...
Click to collapse
+1
By the way, for me it took a few tries to get it to work - I was pressing, pressing but nothing was happening but it finally worked.
So to the OP, if it doesn't recognize you pressing the two buttons the first time - try again until it works.
Sent from my Nexus 4 using Tapatalk 2

Unable to boot into TWRP

Could someone please help.
I've just updated from KK 4.4.4. to Lp 5.0.1 via OTA updates.
Then I tried to install TWRP 2.8.6.0 using Odin 3.10.6 (and 3.09), but I can't boot into TWRP, it just goes into Android System Recovery (or whatever it's called).
Before I updated, I could successfully use TWRP, root and create/restore backups etc. But, since the OS update I can't (plus I will have lost root, as I downloaded/installed the KK ROM as a "clean install".
From looking around various sites and watching videos. I think I need to side load TWRP using ADB.
But, I've visited the Dev. site, downloaded the SDK zip files. Extracted them, but the folder that should contain the files (platforms) is empty.
So, I downloaded the exe file. It wouldn't allow me to install it as I don't have Java installed.
I downloaded and tried to install Java, but it fails to install. Just F typical.
Could someone offer an easy to follow step by step advice and maybe post the files I need to use (if I do need to use ADB).
I'm using 910F and USB debugging is allowed.
Thank you.
************ EDIT ************
Never mind. I had to flash the Lp 5.0.1 stock ROM to fix the problem and now TWRP works.
******************************

Is reactivation lock enabled? If yes, disable and try again

abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
abdyasar said:
Is reactivation lock enabled? If yes, disable and try again
Click to expand...
Click to collapse
Thank you for your help.
The reactivation lock is disabled.
To update my OP, other things I've tried:
I've downloaded and installed the basic files for ADB as well as the full SDK.
Some site say to update the ADB files to the Google USB Drivers (found in the SDK). It just says I'm up to date when I try to find newer drivers via Device Manager.
Tried flashing CWM instead of TWRP using Odin.
Tried installing TWRP (zip) when in the Android System Recovery mode via SD card.
When using ADB. My device is listed when I type "adb devices".
But when I type "fastboot flash recovery <the name of the TWRP file .IMG> I just get "waiting for device".
I get this message if I'm in Bootloader mode or using the phone "normally".

Hopefully it works out
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P

Battlehero said:
Firstly download TWRP from the website : https://dl.twrp.me/trltexx/twrp-2.8.6.0-trltexx.img.tar.html
Then turn your device off and remove the battery for around 10 seconds (make sure the device isn't connected to any charger or anything via the USB cable).
Then after the 10 seconds put the battery back into the device and hold the home, volume down and power button.
Once you are in download mode and it says 'Downloading', plug your device into computer using the USB cable.
Open up Odin as admin and make sure no security software is interfering; once your device shows up in Odin select 'PDA' and then browse to the directory of the recovery file.
Then press start, however while it's flashing press the volume up and home button and this should boot the device directly into recovery. This is important as sometimes stock firmware might revert to stock recovery if you don't boot into recovery at least once.
I hope this helps you out.
UPDATE:
Crap, I didn't read that it worked out XD Ignore me ;P
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I did fix it by re-flashing.
But, the info will be useful if I get into a similar situation again. Or will help anyone else who's stuck.

Unbrick via Lollipop Recovery (Fastboot is dead)

So, I have a ZenFone 5 (A500CG) WW running on a stock-based custom Lollipop ROM (Recreated Remix-Leopard). In an attempt to return to KitKat in order to test some app, I accidentally flashed a bad fastboot.img file. All was too late after I pressed the ENTER key. Although the device still booted and could also enter the stock Recovery mode, attempting to boot into fastboot is a fail (stuck on ASUS logo.)
Now, after an attempt to fix it by ADB Sideloading ASUS' stock 3.24.x Lollipop firmware, my device is technically bricked. Trying to boot it only takes me to the "dead droid" screen (Recovery mode). Attempting to boot into Fastboot (whether Power + VolUp or Reboot to bootloader via the Recovery menu) is a failure. I remain stuck at the ASUS logo.
I've seen the tutorial about unbricking the ZenFone 5 without Fastboot and Recovery (even with ruined partitions) but I found it too bothersome. I'm thinking that since I still have the stock Recovery in my pocket, is there a way to at least restore Fastboot via Recovery? Or better yet, a one-mode solution to install stock ASUS firmware without having to downgrade the Recovery menu (because Fastboot is dead.) Thank you for any help.

to enter recovery mode, u can try key combination :
POWER + VOL UP... when your phone's vibrate, pres VOL DOWN until "dead droid" come, u must release all button then press and hold POWER, press VOL UP Once.

CrazeVjr said:
to enter recovery mode, u can try key combination :
POWER + VOL UP... when your phone's vibrate, pres VOL DOWN until "dead droid" come, u must release all button then press and hold POWER, press VOL UP Once.
Click to expand...
Click to collapse
I know that's how you get to Fastboot, but if you read my entire post, I wrote that I could not access Fastboot, whether through hardware (Power + VolUp) or through the Recovery menu's "Reboot to bootloader" option.

cnswico said:
I know that's how you get to Fastboot, but if you read my entire post, I wrote that I could not access Fastboot, whether through hardware (Power + VolUp) or through the Recovery menu's "Reboot to bootloader" option.
Click to expand...
Click to collapse
sorry, i just read that u want install stock fw. everything is ok if u can access recovery without any error...just sideload via adb (do downgrade/upgrade).

CrazeVjr said:
sorry, i just read that u want install stock fw. everything is ok if u can access recovery without any error...just sideload via adb (do downgrade/upgrade).
Click to expand...
Click to collapse
It's cool.
Yea. I tried doing that. Doesn't work:
I have the Recovery mode for 3.24 Lollipop FW. If I tried to install an older one (i.e. a KitKat stock ROM), it just throws me an error saying that I can only sideload an older FW. However, if I tried sideloading the same 3.24 FW, it just throws me an "Unknown command" upon the sideload reaching about 36%. It's always been like that, I can assure. I am very certain it is not caused by a faulty data connection.
Any way around this? Thanks!

cnswico said:
It's cool.
Yea. I tried doing that. Doesn't work:
I have the Recovery mode for 3.24 Lollipop FW. If I tried to install an older one (i.e. a KitKat stock ROM), it just throws me an error saying that I can only sideload an older FW. However, if I tried sideloading the same 3.24 FW, it just throws me an "Unknown command" upon the sideload reaching about 36%. It's always been like that, I can assure. I am very certain it is not caused by a faulty data connection.
Any way around this? Thanks!
Click to expand...
Click to collapse
try flash with 5.3.3.3 FW that's FW for downgrade all lolipop zenfone 5...
note : just make sure your 5.3.3.3 region (TW/WW/CH/CHT)

CrazeVjr said:
try flash with 5.3.3.3 FW that's FW for downgrade all lolipop zenfone 5...
note : just make sure your 5.3.3.3 region (TW/WW/CH/CHT)
Click to expand...
Click to collapse
Done, and BAM! Problem solved! Thanks!:good:

Bootloop on Lineage 15.1 08.April Build without USB Debugging enabled

Hi guys,
i managed to f*ck up.
I had a running LOS 15.1 build until today where it bootloops .
THe thing is that I am not able to access the storage for saving files or using ADB for flashing stock.
adb does not recognize my device since I didnt enable USB Debugging. What do I do now?
I need to boot to twrp at least or flash a stock image but I can't connect my phone..
what do I do?
PLease helpe, its urgent!!

Ragonexus said:
Hi guys,
i managed to f*ck up.
I had a running LOS 15.1 build until today where it bootloops .
THe thing is that I am not able to access the storage for saving files or using ADB for flashing stock.
adb does not recognize my device since I didnt enable USB Debugging. What do I do now?
I need to boot to twrp at least or flash a stock image but I can't connect my phone..
what do I do?
PLease helpe, its urgent!!
Click to expand...
Click to collapse
Power down your device, and power it back on. Just after vibrate press vol - that will take you to fastboot mode.
I have screwed up on every possible way and fastboot saved me every damn time!!!
Just get the timing right , go to fastboot , connect miflash -> flash stock image.

Anantha47 said:
Power down your device, and power it back on. Just after vibrate press vol - that will take you to fastboot mode.
I have screwed up on every possible way and fastboot saved me every damn time!!!
Just get the timing right , go to fastboot , connect miflash -> flash stock image.
Click to expand...
Click to collapse
Already tried MiFlash in Fastboot mode, but it doesnt seem to recognize my device, although I'm pretty sure I have the right adb drivers installed on my Windows 10 machine. MAybe I gotta reinstall them, but I'm not sure which are 100 percent right.
Thanks!!