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
Related
Hi, this situation is kind of strange and I hope it's just the battery and not the whole goddamn phone.
What I'm dealing with at the moment is:
The phone doesn't boot
When plugged onto charger or USB cable it boots but stuck at Google logo after a blink and stays there. Also, Home, Back and other buttons are lighten.
When "forcefully" put into fastboot mode, e.g. after plugging it onto USB and instantly pressing Vol Up + Power it stuck there as well, volume rocker no more response neither does the power button. Also, I notice there are no commands at the end like "USB int" etc we see normally.
Fastboot or ADB returns no device found
Please help. I personally believe it could be due to battery, what do you guys think?
Thank you.
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
ej8989 said:
As long as you can see the google logo, your device is not bricked. GIve more useful information; like your computer operating system, the last thing you did before this happened, etc.
Click to expand...
Click to collapse
Thanks. My OS is Windows 8.1 Update 1. The last thing was to install UPDATE-SuperSU to root so that I can install ROM Manager to update Recovery but the installation was aborted so I attempt to flash it via Fastboot with success. Then, wanted to install SlimKat but it couldn't let me mount USB storage so that I can put the .zip file. I, then stupidly click on install via ADB but didn't know how to go back so I pulled the battery and powered up; used ADP push command to transfer said the file, but again for some reason I had to pull the battery and since then I am in above position.
Sent from my XT1032 using Tapatalk
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Put the device in bootloader and plug it into the computer, be patient, my phone is rather slow to get detected sometimes.. (Up to 30 min.) Check your drivers on the computer, try rebooting the boot loader from just pressing the power button (while in boot loader mode)..
If all else fails, read up on Wugs NRTK page and about ODIN...
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
BaghiXDA said:
Hi, device doesn't go into bootloader without plugging it to computer (I've to press required buttons BEFORE plugging OTG cable). And when it boots in fastboot mode it doesn't let me press any button either. I kept it plugged in for sometime as well when it when it was at Google logo; will try to do the same while in fastboot mode too and let you know. As for drivers, same computer was used before when it was working and it detected just fine immediately (gave me a pain to find the right drivers though - PDANet was a life saver).
EDIT:
I should mention that I broke the OS before this happened by formatting /system folder and wiping other data from CWM recovery - I think, I also rebooted it without flashing the ROM as well.
Click to expand...
Click to collapse
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Setting.Out said:
I recently had to update my drivers on my computer.. after it did an update, my phone wasn't recognized..
Try Wugs Nexus Root Toolkit,.. use the options for "bricked".. do this from the bootloader screen (power/volume +)...
I don't have experience with ODIN, so you'll need to read that forum/threads...
Click to expand...
Click to collapse
The problem is, even the Toolkit doesn't recognize the device no matter what. Even the keys for ODIN don't work, aren't they Home+VOL+ and Power?
EDIT1:
Kept plugged in for little longer as suggested but it heats up (it's too hot here) so I plugged out. Going to be running it off of Linux and lets see how it goes. :fingers-crossed:
EDIT2:
Tried Adam's UnBrickable method on Linux and even that couldn't find device. But that was to be expected since Adam clearly mentioned in his post that this tool isn't for those who see anything on their screen.
Whelp! Currently I can only see I:\ drive in device manager and that's all under portable devices and that's all. I see the same even in BIOS boot options, it's listed as "Google".
Guess need to close this thread now.
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.
Hi everyone im stuck on the resurection of my device (moto g 2013 8GB updated to 5.1 with [5.1 GPE 1 click] from This forum.
I've tried everything or almost for now, cant get it out of that loop.
*Battery pulling.
*hard buttons combinations.
*fastboot and ADB. (not in fastboot mode so.. And as i did flash de 1click before the loop USB Dbgn isn't enabled)
*i think i've tried every toolkit on this forum.
*Raped google search for over a week trying every posible method-
*Only thing left is to take it to church for a blessing. but im not a believer D:
ADD: i've rooted with a "boot.img" from this forum i think it was a 2015 file.
before this i had not 1 issue with the phone. just unlockd the bootloader a few days ago and updated to 5.1 from 5.0.2 becouse of a wifi issue (unknow mac adress) i had to reboot it like 10 times until it appeared again (original mac adress from device, still wrote it down i have it somewhere.)
I think this would be my first post on this forum and it took me over a week to do it becouse this (asking you-comunity) is my last resource.
PS: i had it going betwen 5.0.2 and 5.1 like 4 times to try solving the wifi issue.. only thing it got me was the "line" on the screen like if it where a problem with vertical sync. (i think you are all very familiar with that issue after downgrading the kernel i think.)
the phone just turns it self on everytime. (everytime)
i was able to boot into recovery before the last flash touching the place were the hardware volume button goes (with a neddle) untill it didnt workd anymore and i send it to a store to repair the volume rockers. still no recovery or bootloader boot.
my pc (laptop with 7-32bit recognices it as xt1032. and the one with xp as MTP.)
I've installed every posible thing that i found to bring it back to life even the android sdk full every pkg from 5.0.2 to 5.1 and extras, Motorola drivers and ADB. tried online searching automated from windows and listing it from a folder with the google one. tried adding the hardware manualy and have every ADB thing that i found on device mng but everyone is wit a yellow triangle. (No USB Debuging enabled so why bother anymore.)
I think that's about it.
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
i m sorry for my english, isnt my native lang. And for making it over complicated.
i cant enter fastboot mode or give any order to the phone trough fastboot on a console.
I have installed a TWRP touch, just cant acces it. dont know if it is the hardware button (Vol -) or what.
so it dosnt show up on fastboot devices nor adb devices.
am i not understanding something ?
Thanks for replying and taking the time to help!
Enter fastboot mode by turning on phone while holding Volume Down.
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
dieguitwow1 said:
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
Click to expand...
Click to collapse
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
Click to expand...
Click to collapse
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
dieguitwow1 said:
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
Click to expand...
Click to collapse
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
lost101 said:
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
lost101 said:
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
Click to expand...
Click to collapse
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
dieguitwow1 said:
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
Click to expand...
Click to collapse
If you power phone off completely, then no commands are remembered. The button is broken.
lost101 said:
If you power phone off completely, then no commands are remembered. The button is broken.
Click to expand...
Click to collapse
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a niddle until it stoped working is there a fix for it? :fingers-crossed:
dieguitwow1 said:
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a needle until it stopped working is there a fix for it? :fingers-crossed:
Click to expand...
Click to collapse
Sorry, I can't help you with that. If you know someone good with a soldering iron, maybe they can fix it - otherwise, try another repair shop.
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
dieguitwow1 said:
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
Click to expand...
Click to collapse
adb reboot bootloader
lost101 said:
adb reboot bootloader
Click to expand...
Click to collapse
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
dieguitwow1 said:
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
Click to expand...
Click to collapse
Yes, USB Debugging would need to be enabled.
lost101 said:
Yes, USB Debugging would need to be enabled.
Click to expand...
Click to collapse
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
dieguitwow1 said:
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
Click to expand...
Click to collapse
I am not aware of any other options.
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
dieguitwow1 said:
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
Click to expand...
Click to collapse
What has changed? Did you get the vol button fixed?
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!
Device:
- Samsung Galaxy A12
- Rooted
- Magisk and Magisk Manager both updated
- Model sm-a127m
- Problem context: I could not find a recovery for my particular model and during the rooting process I somehow ended up not being able to access the recovery, after a long time I tried to install one from the TWRP Official App and this ended up happening.
Bafif said:
Device:
- Samsung Galaxy A12
- Rooted
- Magisk and Magisk Manager both updated
- Model sm-a127m
- Problem context: I could not find a recovery for my particular model and during the rooting process I somehow ended up not being able to access the recovery, after a long time I tried to install one from the TWRP Official App and this ended up happening.
Click to expand...
Click to collapse
Going back to stock by flashing latest via Odin is what I would do and then start from scratch.
You took TWRP for a125f didn't you?
They have very different hardware, but I think it will work to return to stock.
bmwdroid said:
Going back to stock by flashing latest via Odin is what I would do and then start from scratch.
You took TWRP for a125f didn't you?
They have very different hardware, but I think it will work to return to stock.
Click to expand...
Click to collapse
Instead I re-flashed twrp, this time a version supposedly for a127m unofficially and the phone ended up blinking on and off a totally black screen. Now it doesn't enter download mode or recovery mode and the computer doesn't recognize it. I'm pretty ****ed up.
Bafif said:
Instead I re-flashed twrp, this time a version supposedly for a127m unofficially and the phone ended up blinking on and off a totally black screen. Now it doesn't enter download mode or recovery mode and the computer doesn't recognize it. I'm pretty ****ed up.
Click to expand...
Click to collapse
Was it fully loaded before you started?
Is it possible that the battery is empty?
I'd leave for hours connected to the charger and test tomorrow again to get into download mode.
bmwdroid said:
Was it fully loaded before you started?
Is it possible that the battery is empty?
I'd leave for hours connected to the charger and test tomorrow again to get into download mode.
Click to expand...
Click to collapse
The battery is fine, it was loading almost the whole process because I flashed the last time from the PC and was at 70% before starting. The only thing it does since yesterday (it was not turned off at any time) is to flash between the screen turned on showing pure black color and the screen off.
If I press Volume Down Key and power key what it does is not to enter the Download Mode as before but show the Samsung A12 logo and then the warning of "unlocked bootloader" with the "Press Power Key to continue", then the same screen From Samsung A12 but with a warning of Custom Software and then begins to blink again.
I cannot turn it off or enter the recovery mode or enter the download mode. The battery is inaccessible to me although I could find a way to do it if it served something.
@Bafif one last idea:
did you enable USB debugging in dev options before?
Then adb commands might be working.
1 To test if adb can see it (device connected to PC) :
command <adb devices>
Perhaps necessary to enter twice.
If yes you'll see a notification on the screen.
2 Then you can <adb reboot bootloader> to enter download mode.
If you don't get the notification I'm probably not able to give any further hints.
bmwdroid said:
@Bafif one last idea:
did you enable USB debugging in dev options before?
Then adb commands might be working.
1 To test if adb can see it (device connected to PC) :
command <adb devices>
Perhaps necessary to enter twice.
If yes you'll see a notification on the screen.
2 Then you can <adb reboot bootloader> to enter download mode.
If you don't get the notification I'm probably not able to give any further hints.
Click to expand...
Click to collapse
No luck, I guess it's bricked
PS C:\> adb devices
List of devices attached
PS C:\> adb reboot bootloader
error: device not found
PS C:\>
Bafif said:
No luck, I guess it's bricked....
Click to expand...
Click to collapse
Sorry to read that.
Tried very long pressing power button (2 minutes or so) or other button combo like Vol up + down together plus power?
I don't own that device so can't test for you.
bmwdroid said:
Sorry to read that.
Tried very long pressing power button (2 minutes or so) or other button combo like Vol up + down together plus power?
I don't own that device so can't test for you.
Click to expand...
Click to collapse
I GOT IT . What I did was wait for the battery to run out totally and then keep the two volume buttons pressed and connected the cable with the phone off, that opened the download mode. I just had to wait two days for completely draining. Thanks for paying attention to me
Bafif said:
I GOT IT . What I did was wait for the battery to run out totally and then keep the two volume buttons pressed and connected the cable with the phone off, that opened the download mode. I just had to wait two days for completely draining. Thanks for paying attention to me
Click to expand...
Click to collapse
Glad to hear that.