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.

Can my Nexus 7 be revived or not?

Hi everyone,
My Nexus 7 3G 2012 was getting unbearably slow.
For this reason I decided to TRY to flash Cyanogenmod on it using the NEXUS ROOT TOOLKIT.
Except for rooting I have NEVER tried this before.
What the result is is:
. I can still charge it
. It will only boot to the Google Logo.
. I still can get into Recovery Mode.
. My PC can no longer recognise this device.
Is there a way for me to revive it, or does it qualify as being hard bricked.
Please understand that besides using NEXUS ROOT TOOLKIT I understand nothing .

As long as you can get to your bootloader you should be fine, unless your having eMMC issues which im running into right now. If this is WugFresh Nexus Root Toolkit you should be able to use that to complete all the tasks needed for last resort restore. First though, since you have recovery, ill assume TWRP since i think that is default for NRT, you can sideload a new rom if you dont have it on your device right now. Install adb/fastboot if you dont have it already.
Google USB Drivers: https://developer.android.com/sdk/win-usb.html
1. Boot into recovery
2. Tap Wipe -> Advanced Wipe -> Check Dalvik Cache, System, Cache, Data (Not Internal Storage, unless you want to wipe your internal SD) -> Swipe to Wipe
3. Go back home once your done (lower left home button)
4. Tap Advanced -> ADB Sideload -> Swipe to Start Sideload
5. Connect to your PC and start ADB from terminal/command prompt.
6. type adb sideload [location of cyanogenmod-update.zip]
7. repeat again with Gapps or boot, then download to device and flash normal in recovery.
If that fails or you just want to return to stock and start over:
1. boot into bootloader (turn device off, press vol down + pwr)
2. If you have had the drivers installed before then you should be fine, when the device is booted into recovery or just booting (before bootloader) your computer may not recognize it but should once bootloader is loaded.
3. connect to computer and select the option under Restore/Upgrade/Downgrade: Current status: Device Soft-Bricked/Bootloop and click Flash Stock + Unroot
4. Follow NRT prompts

Hi RLM703,
Because of your easy to follow instructions I was able to restore my Nexus.
I had to use the 2nd part of your instructions and return to stock.
My PC did not want to recognize the device.
In the PC Device Manager I finally got him to recognise MTP_USB_Device.
I was so happy to see the four balls spinning again.
I guess burning your fingers is a way to learn.
I will have to put my hands back in the fire again get Cyanogenmod.
I am very gratefull for your assistance.
THANK YOU VERY MUCH !

Bricked my device. Oops...

Hey all.
I've looked far and wide and cannot find a solution for my phone. I was following this tutorial (Sorry can't post links)(Unlock Bootloader, Install TWRP and Root ZTE Axon 7 (A2017G) Droidviews) and got all the way to unlocking my bootloader. Did all the steps correctly but when I clicked start on my unlocked bootloader it went to the ZTE logo and never actually started. I then held the power button down until the device restarted and went into twrp and tried installing lineage and gapps because somewhere I read that someone fixed this problem by installing an update.zip file for nougat 7.0. I used this tutorial (Again cannot post links)(How to Install Lineage OS 14.1 on ZTE Axon 7 Droidviews) to install lineage. Needless to say that did not work and my device was stick stuck in the ZTE logo so I went back into twrp and tried installing the update.zip file for B11. Now my device goes past the ZTE logo but then goes to the bootloader. When I click the power button to boot a Linux symbol appears on my screen and will not leave until I hold the power button for 20 seconds or so, then it goes into what I assume is the default axon 7 recovery. It has a few options such as; reboot device, reboot into bootloader, update via microSD card, update via ADB. When I try to reboot noramlly or to bootloader the previous Linux screen happens. I can't use any commands on ADB aside from sideload and am kinda stuck. Any help would be very much thanked...
P.S. all this has happened on my A2017G that was running Nougat 7.0 B11.

FOUND A SOLUTION!!!
Because I wasn't able to use adb or fastboot in the bootloader or the recovery mode that inbuilt into the phone, I had to instead go into factory test mode by powering on the device whilst holding the power down button, it took a few tries and I kept accidently going into the bootloader instead but eventually I got it. Then you can connect your phone to adb and run the command "adb reboot edl" after that use "axon7tools -w recovery". This didn't work at first for me because I was using an older version of TWRP. After a heap of frustration I finally tried downloading the newest version and voila! It worked. From there I was able to go into TWRP recovery and unlock my bootloader and then finally reboot my phone. Lots of stress but glad I found a solution.

I don't think anyone has posted that adb works in the test menu. good to know.

Unable to enter fastboot mode after flashing

I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.

pieemme said:
I have unlocked my phone, hoping to find a fix to USB external camera not being recognized. As a consequence, I am not able to update my system through OTA. Moreover, I am no longer able to enter fastboot mode. Whatever key combination I tried, my phone will do a normal boot. When I power up or I press volume - I only end up doing a normal boot or powering off. If I press all 3 keys together I get into the e-recovery boot, which fails. I have only been able to boot into TWRP after downloading a system update and choosing to install it. With this procedure, the update will not be installed, but I will boot into TWRP. From here, if I choose recovery, I do boot into fastboot, but my fastboot is not recognized by my computer, as it was before. Running either ADB or Fastboot will not reveal any device connected.
Click to expand...
Click to collapse
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".

DeathBell said:
When you use key combinations, you must shutdown your phone first, not reboot or you can boot into system, make sure that usb debugging is turned on, open adb and type "adb reboot bootloader".
Click to expand...
Click to collapse
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).

pieemme said:
Thanks, I followed your instructions but with no success. As soon as I plug into USB it will power on and go on with a normal system boot, no matter how quick I am in typing the command "adb reboot bootloader", which invariably returns "no devices/emulators found", or whether I press the volume - button or not. This also happens when I am in the charging screen (not sure whether this also equals power off).
Click to expand...
Click to collapse
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?

DeathBell said:
No, you need to boot to Android to use adb.
Is your device bricked or stuck in a bootloop or something?
Click to expand...
Click to collapse
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.

pieemme said:
I wouldn’t call it properly bricked, inasmuch as it is actually doing its job. However, It does some strange things: it gets the OTA updates, but when I click on Download and Install, it restarts in the TWRP menu (which I cannot otherwise access. I have 2 TWRP apps installed, which don’t seem to be of any use: official TWRP App and TWRP Manager). When I am in the TWRP menu, I can choose to restart in the bootloader. However, once there, with the green window telling me that my phone is flashed, the phone is still not detected by ADB or Fastboot commands. I don’t know when the bootloader started to be unaccessible because I left the tinkering a couple of months ago, when I realized that nobody so far has had any success in getting a P10 Lite to work with a USB Endoscope.
Click to expand...
Click to collapse
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?

DeathBell said:
Thats normal behaviour, when you have a custom recovery installed and do anything in the stock recovery then it boots you into the custom recovery, it should also boot to TWRP when you do factory reset in the stock recovery. And when your phone isn't detected by fastboot then its probably a adb and fastboot installation issue on your PC, type "fastboot devices" to see if it detects your device. And what do you even want to do in fastboot?
Also are you in Nougat or Oreo?
Click to expand...
Click to collapse
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"

pieemme said:
I am not too sure to have any working recovery at all, right now. If I press all 3 buttons, I get into the Huawei recovery mode, which fails. I am on EMUI 5.1.1 (Nougat) and would like to install a stock recovery to Oreo. If I am able to get to a working bootloader mode, I would like to install this file which seems to be a stock recovery with Oreo (WARSAW L21C432B182_EU_SERVICE_ANDROIDHOST.RU.RAR). Otherwise, I will buy a MicroSD card reader and try copying this installation to the card, which, according to this video (https://www.youtube.com/watch?v=0vDgDXePAR4&feature=youtu.be) should be the last resort, if everything else fails. I would be perfectly happy to return to a working and updated standard EMUI. I'm told that if I installed the OTA version this would not be working correctly on my my phone. According to an app called Rootchecker, my phone is not properly rooted either, but there are a lot of crappy apps out there, so I don't know what to believe.
BTW: I don't believe there is any problem with my adb fastboot installation (on MacOS). It was working earlier on. When I type "fastboot devices", it returns: "waiting for any device"
Click to expand...
Click to collapse
I still can't uderstand you. Can you boot into Android or not? And Does TWRP work? When you device is softbricked, what did you do to brick it?
At one point you say that you can access fastboot by choosing reboot to bootloader in TWRP and then you say that you have no working recovery at all.
Anyway I can't help you with the fastboot thing then and that file isn't Oreo it's an old version of Nougat, B360 and up is Oreo and also B321 witch is Oreo Beta. You can only flash image files in fastboot anyway as that file needs to be unpacked and put on the dload folder on your sd card.
When you want to get to Oreo you can either use service roms from this thread https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946, you need to copy the two zip files into the dload folder in your SD card. You can also use HWOTA but that wouldn't work since fastboot isn't working for whatever reason. Or when your custom recovery is working you can use HuRUpdater. But you need to be on the newest version of Nougat B210 or B209 to update as otherwise you may brick your phone.

TicWatch Pro 2020 Boot Load Loop Issue

Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).

Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...

Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?

i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate

unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself