Related
OK, so i went and flashed an old backup. Now i can't enter recovery or download mode at all. Can someone help me out? My phone doesn't go passed the SGS4G boot screen. It just stays there. Left it on for three hours and nothing. The only PC i have access to does not have internet. I am typing this on my backup Nokia X2.
Your going to need to download Odin 1.85 and then download any 2.3 and above up to 2.3.6 firmware. I highly recommend also downloading Dr honks kj 1 kernel for it comes with voodoo lag fix and clock work mod recovery.but u must read alot to find what you need because u could possibly ruin your phone permanently!!! Good luck and like I said you must read... it will be your best bet towards reviving your phone and keeping it operational.
I know that and all but no matter what i do. I cannot enter download mode at all. I can't even enter recovery. The only buttons i can press are the only 3 hardware keys. My soft-keys don't work.
When u can use your computer again.set up Odin then plug your USB cable in then before you connect your phone make sure you take the battery out leave the backing off your phone.then plug your USB to your phone be sure to hold vol. Up and down simultaneously then keep volume up down held down and put your battery in, that should put your phone in download option it should also warn you that placing a custom rom or firmware could pose a problem to your phone then I believe the option to put your phone in download mode is volume up once u push up with the volume key you should immediately be put in Andy's download mode.that's really the other alternative that has worked for me always. I certainly hope u get your phone running again bro otherwise you may have to send your phone to warranty replacement that's if its still valid 4 u or if u pay for insurance on your phone, I saw your posts and know your familiar with several how to's and such so like u said good luck to you homez.
Sent from my SGH-T959V using xda premium
Please use the Q&A Forum for questions Thanks
Moving to Q&A
pwner5889 said:
I know that and all but no matter what i do. I cannot enter download mode at all. I can't even enter recovery. The only buttons i can press are the only 3 hardware keys. My soft-keys don't work.
Click to expand...
Click to collapse
Ever have any luck?
this should have the info you need http://forum.xda-developers.com/showthread.php?t=1001759
pwner5889 said:
I know that and all but no matter what i do. I cannot enter download mode at all. I can't even enter recovery. The only buttons i can press are the only 3 hardware keys. My soft-keys don't work.
Click to expand...
Click to collapse
Download mode is holding the 2 volume key and plug in the USB port is that what u tried?
iCrazyNoob said:
Download mode is holding the 2 volume key and plug in the USB port is that what u tried?
Click to expand...
Click to collapse
Yes. I tried that. Nothing happened at all. Made sure the battery was pulled before i plugged the usb cable in. I held down the volume keys while putting the battery back in. Nothing happened. Drivers were installed and everything.
pwner5889 said:
Yes. I tried that. Nothing happened at all. Made sure the battery was pulled before i plugged the usb cable in. I held down the volume keys while putting the battery back in. Nothing happened. Drivers were installed and everything.
Click to expand...
Click to collapse
Your other option is to download the Android Software Development Kit (SDK) & install it. It contains 'adb' which will allow you to reboot the phone into download or recovery mode.
Go to http://developer.android.com/sdk/index.html, download and install the SDK. You only need to install the Tools part, not all of the other parts.
Once done, open a command prompt, cd to the platform-tools directory where the SDK installed, and issue the command:
adb reboot download
That should get you there.
stephen_w said:
Your other option is to download the Android Software Development Kit (SDK) & install it. It contains 'adb' which will allow you to reboot the phone into download or recovery mode.
Go to http://developer.android.com/sdk/index.html, download and install the SDK. You only need to install the Tools part, not all of the other parts.
Once done, open a command prompt, cd to the platform-tools directory where the SDK installed, and issue the command:
adb reboot download
That should get you there.
Click to expand...
Click to collapse
OK, ill try it when i can get access to a PC with internet access.
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:
THIS GUIDE WAS MADE WITH CWM Installed.
This post is to try and combine all the resources i used and found in one simple guide. I really hope this can get sticked so it doesnt get lost.
So after i flashed Hells-Core kernel for the N4 on My N5 i sorta screwed up my Nexus to the point that it wouldnt boot. Not even into bootloader. So unable to find anything on google i came to XDA for help. Well while waiting for a response on here my GF (who has No android knowledge about an average user.) took to google and found what i was looking for without even really Trying. The nexus 5 has a SECOND bootloader option that Alot of users dont know about. To access that second bootloader and fix the BSOD here are the steps you follow.
I AM NOT HELD RESPONSIBLE SHOULD YOU FULLY BRICK YOUR DEVICE BY DOING THESE STEPS!
1.) Plug your device into your PC or laptop (NOT required BUT it does make it easier to do the steps.)
2.) If your device is powered on but again you cant see anything hold Down+power till you hear your device eject from your Computer.
3.) As soon as you hear it eject press and hold Down+up+power. You are now in the secondary bootloader
Now for the Fun and Dangerous stuff.
1.) Open CMD prompt and direct yourself to your ADB location
2.) Type adb devices. If your device shows up here skip the next step.
2a.) If your device DOESNT show up navigate to the recovery option and load recovery. Once your in recovery proceed to the next step.
3.) in CMD prompt type adb shell. if you see # your good. if not type SU
4.) once you have root access in adb shell enter the following command: dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6" and hit enter you should see something like this
dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6"
1024+0 records in
1024+0 records out
524288 bytes (512.0KB) copied, 0.136945 seconds, 3.7MB/s
Click to expand...
Click to collapse
5.) after all that is done you are good to go. Reboot your device and pat yourself on the back seeing as your Soft-Bricked device and bootloader is now fixed and in working order again.
Again We at WolfRoms© are Not responsible for ANY damage that results from these steps.
Thanks*
Andriy2 and his post with the partition command:
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
cargobr151 for the partition list:
http://forum.xda-developers.com/google-nexus-5/general/info-partition-list-nexus-5-t2517503
And lastly grim489 for helping me out on another post i had.
Guide written by Wolf
Founder and one man dev team of WolfRoms©
Thanks for the guide. You are the second guy who saved his phone thanks to the secondary bl.
Tapatalk-kal küldve az én Nexus 5-el
Yeah, you're the 2nd person I've seen fixing his bootloader. Kudos man!
Even I think that this guide should be in the stickies
Thanks everyone. We shall see if it becomes a sticky. But hey if you could just hit the Thanks button id appreciate it
Shameless bump. Trying to get this as a sticky
wolfirotisha said:
Shameless bump. Trying to get this as a sticky
Click to expand...
Click to collapse
Have you reported it that to mods?
Tapatalk-kal küldve az én Nexus 5-el
This reminds me about SuperCID11111111 on HTC phones.
an extra warning. Do not edit mmcblk..... files by any means or will have a totally murdered phone.
I have one question.
3.) As soon as you hear it eject press and hold Down+up+power. You are now in the secondary bootloader
Click to expand...
Click to collapse
At this phone your screen is on? What do you see? Or the phone's screen remains black during the process?
bitdomo said:
I have one question.
At this phone your screen is on? What do you see? Or the phone's screen remains black during the process?
Click to expand...
Click to collapse
During that step, your phone is still bricked and screen should be off. (if the screen is on, then this guide might not be needed for your device)
It should light up after "Now for the Fun and Dangerous stuff" step ( 4&5 )
GUGUITOMTG4 said:
During that step, your phone is still bricked and screen should be off. (if the screen is on, then this guide might not be needed for your device)
It should light up after "Now for the Fun and Dangerous stuff" step ( 4&5 )
Click to expand...
Click to collapse
I found out the screen turn ons
2.) If your device is powered on but again you cant see anything hold Down+power till you hear your device eject from your Computer.
3.) As soon as you hear it eject press and hold Down+up+power. You are now in the secondary bootloader
Click to expand...
Click to collapse
Otherwise how we could navigate to the recovery?
2a.) If your device DOESNT show up navigate to the recovery option and load recovery. Once your in recovery proceed to the next step
Click to expand...
Click to collapse
So we see the normal fastboot screen right?
bitdomo said:
I found out the screen turn ons
Otherwise how we could navigate to the recovery?
So we see the normal fastboot screen right?
Click to expand...
Click to collapse
If you screen turns on, you could solve your issue in another manner. what happened to your phone that brought you here?
To navigate to recovery, given that the phone is on the alternate bootloader, just would need to press 2 times either vol- or vol+ and press power.
like we do normally.
GUGUITOMTG4 said:
If you screen turns on, you could solve your issue in another manner. what happened to your phone that brought you here?
To navigate to recovery, given that the phone is on the alternate bootloader, just would need to press 2 times either vol- or vol+ and press power.
like we do normally.
Click to expand...
Click to collapse
My phone is fine. I am just curious.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
I found out the screen turn ons
Otherwise how we could navigate to the recovery?
So we see the normal fastboot screen right?
Click to expand...
Click to collapse
i can get into recovery but i have no zip on interal so im stuck. pc wont see device so i can transfer a rom over to the phone
I flashed trinity kernel for the n4 onto my n5, 3 times in a row accidentally! after it not booting 3 times, I realized my mistake. I went ahead and flashed the n5 trinity kernel after, and to my surprise it booted, with everything normal. no issues after. I assumed it would've changed my partitions, but it did not.
Georgiazen said:
i can get into recovery but i have no zip on interal so im stuck. pc wont see device so i can transfer a rom over to the phone
Click to expand...
Click to collapse
Reboot to recovery.
Connect your phone to the PC
Download usb drivers http://forum.xda-developers.com/showthread.php?t=2386956
Open device manager and update the driver for AOSP on Hammerhead device.
If you are running windows 8 or 8.1 then you have turn off the driver signature enforcement to install the driver.
Install this http://forum.xda-developers.com/showthread.php?t=2588979 skip the driver installation.
Create a new folder on the root of your C drive and name it to flash
Download a rom zip.
Rename the zip to flash.zip make sure you will not rename it to flash.zip.zip then copy it to the C:\flash folder
In recovery enable adb sideload. If you are using TWRP then it is in the ADVANCED menu.
Open CMD window and type these commands:
cd C:\flash
adb sideload flash.zip
Georgiazen said:
i can get into recovery but i have no zip on interal so im stuck. pc wont see device so i can transfer a rom over to the phone
Click to expand...
Click to collapse
well, you'll need to find and install a working driver for your pc, so adb can see your device(while in recovery). after that, it'll take 2 minutes to adb push to your device and flash.
bitdomo said:
Reboot to recovery.
Connect your phone to the PC
Download usb drivers http://forum.xda-developers.com/showthread.php?t=2386956
Open device manager and update the driver for AOSP on Hammerhead device.
If you are running windows 8 or 8.1 then you have turn off the driver signature enforcement to install the driver.
Install this http://forum.xda-developers.com/showthread.php?t=2588979 skip the driver installation.
Create a new folder on the root of your C drive and name it to flash
Download a rom zip.
Rename the zip to flash.zip make sure you will not rename it to flash.zip.zip then copy it to the C:\flash folder
In recovery enable adb sideload. If you are using TWRP then it is in the ADVANCED menu.
Open CMD window and type these commands:
cd C:\flash
adb sideload flash.zip
Click to expand...
Click to collapse
ok but it doesnt say asop it says android device and mtp
Georgiazen said:
ok but it doesnt say asop it says android device and mtp
Click to expand...
Click to collapse
Then update that, maybe the name depends on the version of windows you are using and thr version of the recovery.
this what i see 1. android phone - composite adb devive
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
now it says google nexus adb interface
Georgiazen said:
this what i see 1. android phone - composite adb devive
---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------
now it says google nexus adb interface
Click to expand...
Click to collapse
:good:
Hi guys. Looks like I deleted the Fire UI. Now, I dont get pop up messages. I dont have the notification bar or the soft keys. And now that the pop up boxes wont pop up, I cant authorize the tablet. Which means I cant do any modding to it, to fix it. Just dont know what to do at this point. Any ideas would be greatly appreciated.
Xpun3414 said:
Hi guys. Looks like I deleted the Fire UI. Now, I dont get pop up messages. I dont have the notification bar or the soft keys. And now that the pop up boxes wont pop up, I cant authorize the tablet. Which means I cant do any modding to it, to fix it. Just dont know what to do at this point. Any ideas would be greatly appreciated.
Click to expand...
Click to collapse
HD 8 or 10? Get a copy, untampered SystemUI.apk from the same device, or as close to it. Must be from an Amazon tablet. Boot to recovery and adb sideload it.
DragonFire1024 said:
HD 8 or 10? Get a copy, untampered SystemUI.apk from the same device, or as close to it. Must be from an Amazon tablet. Boot to recovery and adb sideload it.
Click to expand...
Click to collapse
I have the new HD 10 7th Gen 10". Cant do the ADB thing at all. Since I cant authorize it. Even in recovery mode.
Xpun3414 said:
I have the new HD 10 7th Gen 10". Cant do the ADB thing at all. Since I cant authorize it. Even in recovery mode.
Click to expand...
Click to collapse
in recovery shouldn't matter. You can only adb sideload Amazon signed software in recovery. I will give you a copy of mine as soon as I have access to it.
DragonFire1024 said:
in recovery shouldn't matter. You can only adb sideload Amazon signed software in recovery. I will give you a copy of mine as soon as I have access to it.
Click to expand...
Click to collapse
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Xpun3414 said:
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Click to expand...
Click to collapse
If you can't boot to recovery at all, you might be perma bricked.
Sent from my Moto E4 using XDA Labs
Xpun3414 said:
ADB wont work, since I cant authorize the tablet.& in recovery mode the pc & ADB wont even see the tablet
Click to expand...
Click to collapse
So, to make sure we're all talking the same thing:
Can you boot into recovery mode? (To boot into recovery mode: When the tablet's off, press and hold the power and volume up button. The volume up button is the one closer to the power button. Once the Amazon logo pops up, release the power button but keep holding the volume up button. Eventually, it should boot to a text-only page.)
If you can boot into recovery mode, are you seeing the recovery menu? It should offer you a text-based menu, with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Assuming you can boot into the recovery menu, connect the device to your computer. Select "apply update from ADB," using the volume buttons to maneuver and the power button to select.
It should say: Now sent the package you want to apply to the device with "adb sideload <filename>"...
With the device connected to your computer, go to where your adb software is; type: adb devices . . . does that list the device? (AFAIK, the recovery menu should allow ADB even if you don't have ADB enabled in the system proper; I'm not 100% certain of that, but it's a pretty useless recovery menu if it doesn’t . . .)
If it does list with the adb devices command, then it should be ready to sideload. At this point, you'll need an update file to sideload (which will wipe your system and should convert it to a factory-restored tablet). That's beyond the scope of this troubleshooting, but there are other guides online. However, make sure you choose the same sideloading package as your operating system version. (For example, my tablet has 5.5.0.0, so I sideload update-kindle-40.5.9.1_user_591450020.bin)
To be honest, if you're tech-savvy, then it's quite probable you've already done all this, and apologies for spelling it all out . . . but, reading what you're saying, I'm having a hard time even envisioning what you're getting stuck on.
GamerOfRassilon said:
So, to make sure we're all talking the same thing:
Can you boot into recovery mode? (To boot into recovery mode: When the tablet's off, press and hold the power and volume up button. The volume up button is the one closer to the power button. Once the Amazon logo pops up, release the power button but keep holding the volume up button. Eventually, it should boot to a text-only page.)
If you can boot into recovery mode, are you seeing the recovery menu? It should offer you a text-based menu, with options:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Assuming you can boot into the recovery menu, connect the device to your computer. Select "apply update from ADB," using the volume buttons to maneuver and the power button to select.
It should say: Now sent the package you want to apply to the device with "adb sideload <filename>"...
With the device connected to your computer, go to where your adb software is; type: adb devices . . . does that list the device? (AFAIK, the recovery menu should allow ADB even if you don't have ADB enabled in the system proper; I'm not 100% certain of that, but it's a pretty useless recovery menu if it doesn’t . . .)
If it does list with the adb devices command, then it should be ready to sideload. At this point, you'll need an update file to sideload (which will wipe your system and should convert it to a factory-restored tablet). That's beyond the scope of this troubleshooting, but there are other guides online. However, make sure you choose the same sideloading package as your operating system version. (For example, my tablet has 5.5.0.0, so I sideload update-kindle-40.5.9.1_user_591450020.bin)
To be honest, if you're tech-savvy, then it's quite probable you've already done all this, and apologies for spelling it all out . . . but, reading what you're saying, I'm having a hard time even envisioning what you're getting stuck on.
Click to expand...
Click to collapse
ok heres the thing.
A) when in android, ADB see the device. But I cant authorize ADB on the tablet, due to no pop up box & no notification bar.
B) I can boot into recovery (yes I can see it) but,when in recovery. the pc/ADB doesnt see the tablet at all. so sideloading doesnt work.
C) I would think being in recovery mode, you wouldnt need to authorize ADB. Im thinkin', maybe because I cant authorize it in Android, I cant do anything in recovery. IE: sideload.
Heres what I get when the tablet is in recovery mode..
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Xpun3414 said:
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Click to expand...
Click to collapse
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Xpun3414 said:
ok heres the thing.
A) when in android, ADB see the device. But I cant authorize ADB on the tablet, due to no pop up box & no notification bar.
B) I can boot into recovery (yes I can see it) but,when in recovery. the pc/ADB doesnt see the tablet at all. so sideloading doesnt work.
C) I would think being in recovery mode, you wouldnt need to authorize ADB. Im thinkin', maybe because I cant authorize it in Android, I cant do anything in recovery. IE: sideload.
Heres what I get when the tablet is in recovery mode..
Click to expand...
Click to collapse
Xpun3414 said:
Ok today, while in recovery mode, I plugged in the tablet & I got this.....
Click to expand...
Click to collapse
GamerOfRassilon said:
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Click to expand...
Click to collapse
Sideloading in recovery does not require ADB authorization !!! All you need to do is to get the correct drivers loaded, to make sure that your PC can see your Fire. Recovery is for restoring things, if it needed ADB authorization, it would defeat its purpose.
Get USBDeView, and see which devices it shows when the Fire is in recovery, and plugged into a PC USB port. Then try to locate correct drivers. You may want to delete any driver related to this Fire in USBDeView, then plug it back in, make windows try to get the driver for it again.
GamerOfRassilon said:
Yeah, that's all a poser.
At this point, about the only other advice I can offer is to try a different USB port (on your computer), and/or a different USB cable. And if all THAT fails, try a different COMPUTER with different usb cables. (I had some strange errors with getting my Kindle to be recognized by the computer, until I switched to a different port . . . and I've had a problem with the device not charging at all depending on which cable I'm using.)
And if that doesn't yield anything different . . . I'm out of ideas, I'm afraid.
Click to expand...
Click to collapse
I can't believe I didn't think about that. Totally sliped my mind.
Anyway. Used a different usb cable & a different pc and BAM ! Flawless recovery. Thank you for your help.
-------------
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!