hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
did you try to pull out the battery?
if not take it off,put it again
then hold volume down + power button until it shows the bootloader screen
mmcr said:
hey guys
i have a HTC Sensation that is password locked, but the real problem is that it won't enter recovery mode.
the volume down key is working as i've tested it in a "sos call", the volume up doesn't work when the phone is turned, but that's not important as it's not needed.
is there any other way to get into recovery mode?
also, if i hold the up key with the power switch, it boots up in "safe mode"
Click to expand...
Click to collapse
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?
mmcr said:
several times sir, even went as far as draining the battery inside the phone completely, trying it with another battery, leaving the battery out of the phone for a whole day...
are there no usb hacks or something like there is with the samsung android phones?
Click to expand...
Click to collapse
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.
heavy_metal_man said:
Are you on a stock rom? if you are the you would have to have un-ticked fastboot from the settings to be able to boot into the bootloader...
try to attach the device to a usb port of a laptop and see if the usb debugging symbol shows up in the status bar. if it does you can use the adb command adb reboot recovery to force a jump into the recovery.
Click to expand...
Click to collapse
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?
mmcr said:
i have no idea if the phone has a stock rom on it, can't access the menu and it's not in usb debugging mode, coz when i access it in adb cmd i get this msg, "error: device not found"
the pc does pick it up, but as a disk drive anything else i can do?
Click to expand...
Click to collapse
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.
heavy_metal_man said:
ok try battery pull, the hold down both volume keys and power for 10 seconds to see if it boots into stock recovery.
Click to expand...
Click to collapse
boots up in safe mode
mmcr said:
boots up in safe mode
Click to expand...
Click to collapse
hmmmm. running out of ideas now. was this your device? do you know the google account ect?
heavy_metal_man said:
hmmmm. running out of ideas now. was this your device? do you know the google account ect?
Click to expand...
Click to collapse
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.
mmcr said:
no sir, i have a cellphone repair kiosk, the client doesn't remember the account that he used to create the security feature and his kid busted the pattern lock.
Click to expand...
Click to collapse
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.
So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?
se1000 said:
So, no bootloader? When you hit vol down + power it should land you in the bootloader screen, where you then select recovery. Have you tried with the cover, SD, and SIM removed from the phone?
Click to expand...
Click to collapse
i've tried that several times bro, just the same out come everytime
heavy_metal_man said:
can you take a photo of the pattern lock screen
also what do you know about the device? is it eu,uk,us? also what carrier is the device on? is it on ice cream sandwich or gingerbread? you may be able to run a RUU (rom update utility) on the device, updating the firmware and remove the lock that is currently on the device.
Click to expand...
Click to collapse
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.
mmcr said:
i don't know any of the above, how do i check any of these without getting into the bootloader? the device only connect to the pc as a disk drive.
Click to expand...
Click to collapse
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.
heavy_metal_man said:
you will need to talk to the owner of the phone, without that info your stuffed tbh. with fastboot enabled in the stock rom you cannot boot into bootloader. without the info like what carrier they are on you dont know what ruu to run to reset the device. without usb debugging you cannot use the pc to send commands as far a i am aware :/ assuming you have the correct htc drivers installed connect the device to the pc, open cmd in your adb directory and type in adb reboot bootloader and see if it responds. again without that info you've pretty much had it. you can try to flash ruu's from the pc at random in the hope that you find the correct firmware and cid, but without usb debugging on there is no guarantee that the ruu will even find it.
Click to expand...
Click to collapse
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices
mmcr said:
yeah, tried the adb reboot recovery, no dice. just error, no device connected.
the owner bought it 2nd hand, so he has no clue, i'm just going to return it. pity that htc doesn't have a "usb key" like samsung that forces "download mode" on the android devices
Click to expand...
Click to collapse
indeed so. but you cannot fault it as a security measure :silly:
Related
My sensation recently developed the touchscreen issue. It having previously been s-off/revolutioned/supercid, I thought it best to undo these things before sending it in for warranty. I ran the appropriate TMOUS RUU_***.exe, but now I cannot access the bootloader at all.
The vol down + power on does not work, it just boots normally.
Adb can't access the device (probably because I can't enable usb debugging).
I had previous changed the superCID back to stock, so that should be find, but the secureoem flag (whichever it is) i believe is still unset (or just not to 3).
Any suggestions?
Thanks XDA
Kremnari
Kremnari said:
My sensation recently developed the touchscreen issue. It having previously been s-off/revolutioned/supercid, I thought it best to undo these things before sending it in for warranty. I ran the appropriate TMOUS RUU_***.exe, but now I cannot access the bootloader at all.
The vol down + power on does not work, it just boots normally.
Adb can't access the device (probably because I can't enable usb debugging).
I had previous changed the superCID back to stock, so that should be find, but the secureoem flag (whichever it is) i believe is still unset (or just not to 3).
Any suggestions?
Thanks XDA
Kremnari
Click to expand...
Click to collapse
Go into Settings -> Power and disable the Fastboot checkbox. That is what is preventing you from getting to HBOOT by holding the Volume Down/Power button. Also Under Settings -> Applications -> Development is the USB debugging checkbox.
Sorry, I should've been more specific. My touchscreen issue is that it's completely unresponsive. So I am unable to change any of the settings.
Is there a rom that would already have usb debugging and/or fastboot off enabled?
Kremnari said:
Sorry, I should've been more specific. My touchscreen issue is that it's completely unresponsive. So I am unable to change any of the settings.
Is there a rom that would already have usb debugging and/or fastboot off enabled?
Click to expand...
Click to collapse
most new ones do have usb debug enabled, but not fastboot off...but if you cant access bootloader, how are you gonna flash another one?
EDIT* another alternative is to try something like this http://www.cyrket.com/p/android/org.l6n.remand/
there are several *better* variations of it on the market, you can use your pc mouse to control your fone, must have root tho
Try this:
- Disconnect your phone from USB.
- Plug off the battery and put it again.
- Hold Volume Down and Power button.
If that doesn't work, try flashing RUU again and repeat the above steps.
Good luck
most new ones do have usb debug enabled, but not fastboot off
Click to expand...
Click to collapse
Usb debug is not enable because adb can't access the device.
...but if you cant access bootloader, how are you gonna flash another one?
Click to expand...
Click to collapse
You are correct in this matter. My lapse was with the ruu's being able to flash the phone without fastboot or adb. Which brings up an important (somewhat off-topic) point...is anybody attempting to determine how the RUU's are able to communicate with the phone without using the adb?
Try this:
- Disconnect your phone from USB.
- Plug off the battery and put it again.
- Hold Volume Down and Power button.
If that doesn't work, try flashing RUU again and repeat the above steps.
Click to expand...
Click to collapse
This is unsuccessful. I have tried both builds of the RUU for tmo.
Any other suggestions?
Thanks anyways so far guys!
Kremnari said:
This is unsuccessful. I have tried both builds of the RUU for tmo.
Any other suggestions?
Thanks anyways so far guys!
Click to expand...
Click to collapse
For me pulling the battery was always the way to enter the bootloader... It bypasses the set fastboot option.
As this is not working for you - is the volume down button broken as well?
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
SlashSpeed said:
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
Click to expand...
Click to collapse
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
cahir_cz said:
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
Click to expand...
Click to collapse
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
SlashSpeed said:
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
Click to expand...
Click to collapse
Congratulations Never knew you can use adb while booting Good luck with the cleaning
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
uxmanz said:
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
Click to expand...
Click to collapse
I can get into the fastboot menu, but I can't use the volume up/down buttons and I don't think that my computer recognizes the device in fastboot at all, because of the broken power button. If you could help me somehow, then I would really be in your debt.
SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
polobunny said:
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
Click to expand...
Click to collapse
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
SlashSpeed said:
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
Click to expand...
Click to collapse
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
polobunny said:
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
Click to expand...
Click to collapse
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
SlashSpeed said:
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
Click to expand...
Click to collapse
If you can enter bootloader mode you can enter download mode.
polobunny said:
If you can enter bootloader mode you can enter download mode.
Click to expand...
Click to collapse
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
SlashSpeed said:
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
Click to expand...
Click to collapse
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
polobunny said:
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
Click to expand...
Click to collapse
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
SlashSpeed said:
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
Click to expand...
Click to collapse
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
polobunny said:
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
Click to expand...
Click to collapse
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
SlashSpeed said:
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
Click to expand...
Click to collapse
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
polobunny said:
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
Click to expand...
Click to collapse
If nothing else helps, I guess I'll just send it to a repair center for the power button. I wanted to do that anyway and I sadly I have a real reason.. :/
Polobunny, I appreciate your efforts though.
Edit: Took my phone to a repair center, screw it.
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
xymic said:
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Click to expand...
Click to collapse
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
xymic said:
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
Click to expand...
Click to collapse
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Mr.Ak said:
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Click to expand...
Click to collapse
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
xymic said:
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
Click to expand...
Click to collapse
Click "Thanks" button
Hi,
I have a problem with my Motorola Moto G4. I bought it 2 months ago and unfortunately the power button broke and I am therefore not able to turn my phone on/off. That is in general not a problem since the device is still under warranty and I will get the phone repaired. The problem is that I want to backup my data, which I am not able to, before getting the device repaired since the workshop will reset the phone.
I am still able to unlock the phone but no apps or windows can be opened (taping on an app icon does not do anything). Dragging down the notification bar is possible and if connected via USB I can still see the status, unfortunately I am not able to change the setting from charging only to data connection. Since the power button is broken I am not able to reboot the device. I tried to use the adb tools to reboot but the device is not authorized and I would need to change that on the phone which I am not able to. Is there any way to reboot the phone or to access the data.
Any help would be really appreciated.
you might be able to try the commands for adb reboot recovery as the phone is booting up - iv never tried it but adb should be working after the moto splash screen (during the boot animation)
Im not sure if it needs authorisation during that stage but if you cant get into recovery and you cant change the usb connection/authorise adb then I cant see any other way to get the data off
TheFixItMan said:
you might be able to try the commands for adb reboot recovery as the phone is booting up - iv never tried it but adb should be working after the moto splash screen (during the boot animation)
Im not sure if it needs authorisation during that stage but if you cant get into recovery and you cant change the usb connection/authorise adb then I cant see any other way to get the data off
Click to expand...
Click to collapse
I am not really sure how to follow your advice since I am not able to shut down / reboot the phone (power button is not working).
Nem1c said:
I am not really sure how to follow your advice since I am not able to shut down / reboot the phone (power button is not working).
Click to expand...
Click to collapse
In that case I don't see how you can access anything if you have no adb & you can't select anything on the phone
TheFixItMan said:
In that case I don't see how you can access anything if you have no adb & you can't select anything on the phone
Click to expand...
Click to collapse
If I would drain the battery to "shut down" the phone, would there be a way to turn the phone on without the power button?
Nem1c said:
If I would drain the battery to "shut down" the phone, would there be a way to turn the phone on without the power button?
Click to expand...
Click to collapse
with older samsung devices you could use a usb jig to get into download mode without the power button (its a usb cable with some pins crossed you can buy them for only £1 off amazon/ebay)
even if it did work you would still need the power button to select the option to restart phone so the answer is nothing that I can think of
TheFixItMan said:
with older samsung devices you could use a usb jig to get into download mode without the power button (its a usb cable with some pins crossed you can buy them for only £1 off amazon/ebay)
even if it did work you would still need the power button to select the option to restart phone so the answer is nothing that I can think of
Click to expand...
Click to collapse
I found some mechanisms to get the phone turned on and I will try them out. I guess I have nothing to lose.
The interesting thing is that my phone is still receiving messages and news (I see them in the notification bar), so things like that are still working but unfortunately new "widows" can't be opened.
Thank you for your help.
I was able to get the phone rebooted and after the restart everything works as it should.
This is what I did:
Drain the battery (using the flash light), once the battery is flat connect the phone to the PC
Press and hold the volume down button until the Fastboot menu appears
Download ADB tools (the minimal version with adb and fastboot is sufficient)
Install the Motorola driver on the PC (I was not aware that I need this, since connecting the phone without the driver being installed and running adb device results in the device being shown)
run fastboot reboot
Hello,
My Pixel 2 was unlocked bootloader and Rooted.
I went to Magisk app then pressed Uninstall All, then my phone rebooted and brick at boot (Screenshot "No command").
I tried to flash back to stock rom but computer cannot reconize the phone. (I supposed USB debugging was not turned on yet).
Please advise how I can make my Pixel 2 back to work?
Many thanks in advance.
thieuvn said:
Hello,
My Pixel 2 was unlocked bootloader and Rooted.
I went to Magisk app then pressed Uninstall All, then my phone rebooted and brick at boot (Screenshot "No command").
I tried to flash back to stock rom but computer cannot reconize the phone. (I supposed USB debugging was not turned on yet).
Please advise how I can make my Pixel 2 back to work?
Many thanks in advance.
Click to expand...
Click to collapse
Anyone can help?
thieuvn said:
Anyone can help?
Click to expand...
Click to collapse
Hi! Can you see your Pixel in device manager when you connect it to PC?
somin.n said:
Hi! Can you see your Pixel in device manager when you connect it to PC?
Click to expand...
Click to collapse
I cannot see it.
Nothing happen when I plug the phone in.
thieuvn said:
I cannot see it.
Nothing happen when I plug the phone in.
Click to expand...
Click to collapse
Try to power off the phone and than hold power button until phone will vibrate and try again connect to pc ...
somin.n said:
Try to power off the phone and than hold power button until phone will vibrate and try again connect to pc ...
Click to expand...
Click to collapse
Thanks. I will try one more time
somin.n said:
Try to power off the phone and than hold power button until phone will vibrate and try again connect to pc ...
Click to expand...
Click to collapse
Still cannot connect my phone with the PC.
Tried 03 different PCs already.
thieuvn said:
Still cannot connect my phone with the PC.
Tried 03 different PCs already.
Click to expand...
Click to collapse
Do you have google usb drivers on your PC?
Code:
[url]https://developer.android.com/studio/run/win-usb[/url]
somin.n said:
Do you have google usb drivers on your PC?
Click to expand...
Click to collapse
Yes I had it all.
But still cannot connect, I tried All in one tool, 15s ADB , and all cannot reconize phone
thieuvn said:
Yes I had it all.
But still cannot connect, I tried All in one tool, 15s ADB , and all cannot reconize phone
Click to expand...
Click to collapse
And do you use original usb-c cable?
somin.n said:
And do you use original usb-c cable?
Click to expand...
Click to collapse
Yes i do.
The ADB driver keeps not working is the main problem.
thieuvn said:
Yes i do.
The ADB driver keeps not working is the main problem.
Click to expand...
Click to collapse
It is really weird :/ I tried to boot to bootloader with usb debuging off and still my PC correctly recognize my phone. Just last idea, try to boot to bootloader with key combination (power of phone and hold Power + vol down)...
Here is the version of usb driver which I have ...
somin.n said:
It is really weird :/ I tried to boot to bootloader with usb debuging off and still my PC correctly recognize my phone. Just last idea, try to boot to bootloader with key combination (power of phone and hold Power + vol down)...
Here is the version of usb driver which I have ...
Click to expand...
Click to collapse
Thank you.
Let me buy another cable then try again...
Download and extract the latest version of Platform Tools to a folder, then run all ADB and fastboot commands in command prompt or powershell within that folder. Don't rely on Windows drivers for ADB.
DuckRuckus said:
Download and extract the latest version of Platform Tools to a folder, then run all ADB and fastboot commands in command prompt or powershell within that folder. Don't rely on Windows drivers for ADB.
Click to expand...
Click to collapse
I already did it but no respond so far
thieuvn said:
I already did it but no respond so far
Click to expand...
Click to collapse
Forget about ADB, you need Fastboot access. While in the bootloader interface, connect your phone, look for it in the Device Manager and change its driver to Android Bootloader Interface, or something of the sort. Next try "fastboot devices" on the command line, see if it detects your device.
I brought my phone to repair shop and they detected that the hard disk was dead.
Just bought another Pixel 2 to have more awesome photos
You have no fastboot I guess.
Boot into fastboot, plug in the usb cable and press and hold the volume down button for like 15 seconds, and then it will be recognized by the PC. You can flash back the stock rom after that.
Hey I had the same problem. Just stuck in bootloader mode. In my case, the boot slot changed itself from b to a (access denied, same as your problem). What I did:
1. I boot my phone, then it'll be in bootloader mode (same as the first picture when it says 'operation denied')
2. I kept pressing the power button, then my phone boot into bootloader again (bootloop). I kept holding my power button until my phone boot into right boot slot. (It took me 10 bootloop to boot into right boot slot, I just keep holding my power button when in the bootloader mode)
You can add my telegram : (@)Djkuns if you're confused. Hope I can help! Goodluck!