Database Info

[Q] Too many pattern attempts... No Recovery menu

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:

[Q] Stuck in bootloader with non-working power and volume buttons

I restored a backup with TWRP and am now stuck booting to the bootloader. To make things worse neither by volume buttons or my power button works so I can't get back to recovery.
The bootloader screen says Fastboot Mode at the top in red letters but I cannot gain usb access to reflash a new rom. Is there something I need to do to enable USB in the bootloader (I have the SDK and drivers installed on my PC already) or could my usb connection also be busted

Type from CMD:
fastboot devices
Click to expand...
Click to collapse
That should get you some info. If it doesn't work, your computer isn't set up properly.

Ted Mosby said:
Type from CMD:
That should get you some info. If it doesn't work, your computer isn't set up properly.
Click to expand...
Click to collapse
Nothing comes up which makes me think the usb connection is busted as well. I dropped my phone a few weeks ago which ended up breaking my power and volume buttons but now that I think about it I haven't used the usb data connection since then so I wouldn't know if something happened to that too. I can still charge my phone though. adb/fastboot are set up correctly because I've used it from my PC before. When I'm in the bootloader and plug the usb it doesn't show up on my pc so I think the drop broke it too

[Q] Bootloop - how to recover file?

Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander

Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?

alexs77 said:
Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander
Click to expand...
Click to collapse
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :

el_daYa said:
Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?
Click to expand...
Click to collapse
Yes, I do have a custom recovery setup. Yes, I do have adb and fastboot setup on my computer.
No, I don't get into fastboot or the custom recovery. If I try to, it will reboot right away, as shown on the video. [emoji30]

bitdomo said:
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :
Click to expand...
Click to collapse
Uhm, well, losing my warranty is of course also something, I would not want [emoji26]

Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.

el_daYa said:
Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.
Click to expand...
Click to collapse
I do know my way around adb
adb devices will only show the device , if it is booted. It does not boot - what happens, is visible in the Google+ post, which contains a video.
I tried plugging it in and it is not shown. Also not with the fastboot command (ie. "sudo fastboot devices" shows nothing. Adb also does not find the device). That is, what I meant with "I cannot adb to the device".

Then I am afraid you'll need assistance from a higher level my friend, sorry I wasn't much help.

bricked: a confession,

1) stuck in bootloader
2) changed to B slot thru terminal . following a thread I guess
3) got into recovery (.IMG) but couldn't flash zip
4) seen "edl" and thought, what's that? So I clicked it
5) screen now blank
6) buttons have no response
7) I've owned the phone for 2 days (new)
Am I out a lot of $ or is there a hope for me

does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.

Seems like you stuck at edl mode. Try holding vol down (or up) + power buttons for at least 30 seconds. Than you can try flashing stock rom from fastboot mode.

alexkalicharan said:
does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.
Click to expand...
Click to collapse
Everytine I plug it in (windows8: test mode) the PC makes a sound but can't seem t find the device in the device manager.
Msmdownload tool finds nothing

Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots

alexkalicharan said:
does your computer detect the phone at all when you plug it in? I know it isn't responsive, but try powering it on when you plug it in via USB and see if your PC detects anything.
Click to expand...
Click to collapse
elmarian756 said:
Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots
Click to expand...
Click to collapse
Used a newer PC, w/win 10
Held volume up+down + power , plugged in USB to PC
Held those 3 buttons until of made a second sound
(almost 30 secs)
I can now see battery charging, woohoo
I seriously can't wait to installed mclroG
And rid myself from G00g1e
Still reading hard brick guide
I apologize to everyone reading this but sometimes you have to interact w/ someone to get the solve

elmarian756 said:
Hold volume up + power button together for 10 to 30 seconds. Then release. Wait a few seconds. Now press and hold power button until it vibrates to see if it boots
Click to expand...
Click to collapse
OnePlus 7pro bought directly from OnePlus
( i think its GM1915)
windows 10 pc
device manager lists phone as Kedacom USB Device ---> Android Bootloader Interface
i downloaded "10.0.3-GLOBAL-OnePlus7ProOxygen_21.O.23_OTA_023_all_1912032357_76b445-FASTBOOT"
ran the "flash-all" batch file
when it's done, phone reboots into "Qualcomm: CrashDump"
I can press the up+down volume buttons w/ the power button and get back to Fastboot mode
I can also get into the Chinese mode.. with that, i click ENGLISH then WIPE EVERYTHING
still no luck.... truly is an interesting BRICK

Well, you can try flashing using "TOOL ALL IN ONE".

Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/

I also bricked mine a couple days ago , restored it by using MNSTOOL , you can find threads or youtube videos how to use it , it will finish it in around 5 minutes and also it will lock the bootloader.

Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
so many times i've tried the msmdownload tool
my device is not recognized... so i figure it's the driver
i followed the instructions.. it says with phone off ,hold the vol up+down for 5 secs then plug in to usb on pc
the drivers should auto download into the pc
it did.. i see in Device Manager under PORTS the qualcomm driver appear when phone is plugged in
but phone is in Qualcomm CrashDump mode
when i reboot to FASTBOOT MODE (by holding volume up+down and power button) the Device Manager
recognizes the phone as Kedacom USB Device/Android Bootloader Interface
(not Qualcomm)
and of course MSMDownload tool does not recognize phone... i'll keep trying

csmooth2001 said:
so many times i've tried the msmdownload tool
my device is not recognized... so i figure it's the driver
i followed the instructions.. it says with phone off ,hold the vol up+down for 5 secs then plug in to usb on pc
the drivers should auto download into the pc
it did.. i see in Device Manager under PORTS the qualcomm driver appear when phone is plugged in
but phone is in Qualcomm CrashDump mode
when i reboot to FASTBOOT MODE (by holding volume up+down and power button) the Device Manager
recognizes the phone as Kedacom USB Device/Android Bootloader Interface
(not Qualcomm)
and of course MSMDownload tool does not recognize phone... i'll keep trying
Click to expand...
Click to collapse
I will tell you the full guide.
1. Extract msm(whatever).zip
2. Turn off your phone
3. Open msm.exe (green icon) as admin
5. Hold vol+ and vol- for 30 (no less)
5. Connect usb while holding both volume buttons and release after connecting the usb
6. As soon as you connect the usb hit start.

msmtool does not recognize
Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
i figure it's the driver.. windows keeps installing a specific driver for the phone.
but i think it's the wrong driver
(doesnt say QUALCOMM in the device manager)
so now i have to force install the driver
by right clicking on the phone in the device manager and working thru the menu to get to 'HAVE DISK'
so i have to be in windows as an admin
https://www.technipages.com/windows-administrator-account-login-screen
then after downloading the Qualcomm driver in a .cab file as admin i can right click and choose install .cab file
***AAAAAND nope can't right click to have "install" appear in the menu
FUDGE FUDGE FUDGE
all because windows says the driver is already installed... and has a kaed???? driver instead of the Qualcomm
can my life with this phone be any more difficult??

csmooth2001 said:
i figure it's the driver.. windows keeps installing a specific driver for the phone.
but i think it's the wrong driver
(doesnt say QUALCOMM in the device manager)
so now i have to force install the driver
by right clicking on the phone in the device manager and working thru the menu to get to 'HAVE DISK'
so i have to be in windows as an admin
https://www.technipages.com/windows-administrator-account-login-screen
then after downloading the Qualcomm driver in a .cab file as admin i can right click and choose install .cab file
***AAAAAND nope can't right click to have "install" appear in the menu
FUDGE FUDGE FUDGE
Click to expand...
Click to collapse
You can just use the drivers which are provided in the msm archive.

tried manually install a .cab with a terminal command as admin
but i get error "An error occurred trying to open - c:\usb.cab Error: 0x80070003
maybe i have to rename it KB(+number).cab in order for it to work (instead of usb.cab)
NOPE THAT DIDNT WORK

Zed Kay said:
Did you try the MSMtool?
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691/amp/
Click to expand...
Click to collapse
Zed Kay said:
You can just use the drivers which are provided in the msm archive.
Click to expand...
Click to collapse
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

csmooth2001 said:
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
What do you see in device manager while the phone is connected?
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
csmooth2001 said:
I'll try that
NOPE!!!
pop window states
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Click to expand...
Click to collapse
L2 drivers>qcser64>view signature>view certificate>install certificate>next>next>finish then reboot

my phone is GM1915
which is tmobile (even though i bought it directly from OnePlus)
so i will search for downloads for that
**on a mission**

Msmtool is what you need to use. You will recover it for sure

csmooth2001 said:
my phone is GM1915
which is tmobile (even though i bought it directly from OnePlus)
so i will search for downloads for that
**on a mission**
Click to expand...
Click to collapse
currently trying --> https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947

Pixel bricked qusb_bulk

Hello XDA
After 2 years of usage my pixel died, last time alive it was android 10, turned off in my pocket and never returned, just turned out black screen and connecting as qusb_bulk with PC
Holding power button with/or volume buttons doesn't make any difference, no reaction
Any ideas how to fix this?

It looks like your phone is in some kind of download mode. qusb_bulk, qusb definitely means Qualcomm USB but the bulk thing doesn't mean anything to me. Maybe stuck in fastboot on EDL mode.

Dumbass370 said:
Hello XDA
After 2 years of usage my pixel died, last time alive it was android 10, turned off in my pocket and never returned, just turned out black screen and connecting as qusb_bulk with PC
Holding power button with/or volume buttons doesn't make any difference, no reaction
Any ideas how to fix this?
Click to expand...
Click to collapse
You are probably screwed while the system ran out of battery when auto installing a system update. You are now in edl mode.
You can try disconnect and reconnect battery and see if other state acheived.

You can try to flash the boot, recovery and system.img through adb using EDL like "adb edl flash system C:\path\to\your\system.img" Same for the recovery and boot except replace system in the aforementioned command and put recovery or boot along with the path to them

Also, forgot to mention that after flashing the system, boot and recovery.imgs run "adb edl reboot recovery" If that doesn't get you in recovery try getting in it using key combos. After getting into recovery flash an OTA image from Google and you're good to go.

↑good that is What I want to say

jjgvv said:
disconnect and reconnect battery
Click to expand...
Click to collapse
Tried it, with and without battery plugged in, pc sees phone as qusb_bulk still

muhammad42620 said:
through adb
Click to expand...
Click to collapse
I'd already do it, but adb can't recognize the phone, adb drivers not installing

Dumbass370 said:
I'd already do it, but adb can't recognize the phone, adb drivers not installing
Click to expand...
Click to collapse
Did you find out the reason of the issue ?

Andri_ju said:
Did you find out the reason of the issue ?
Click to expand...
Click to collapse
Nope.

Hello all, my google pixel1 32gb bricked after a SW update and it is going into EDL (emergency download mode) , can someone help me with .mbn file that I can flash with QPST tool? adb or fastboot is not recognizing the device, its always goes to EDL mode.
Thanks