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.
Related
My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening; I've tried it on three PC's and none of them even see a device connected. It's not even a matter of drivers because when I'm in fastboot it's like nothing is connected at all.
I can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on. I can do anything I want in recovery or when the phone is up, but in fastboot I can't do anything.
Someone please help!!
By the way, ADB works perfectly but obviously fastboot does not because my PC thinks nothing is connected when fastboot is up on my phone and as I mentioned, my phone is completely unresponsive to anything that I do when I'm in fastboot. I can't use the "volume up/volume down" and tap the power button to get into downloading mode either because MY STUPID POWER BUTTON IS BROKEN!!!
Thank you again in advance....you will be my hero if you can help me with this!!!
forumsid987 said:
My power button is broken so I need to take my phone in to get it replaced. Following the instructions to get it unrooted/return to stock, I need my phone to be recognized in fastboot. It's not happening. I also can't use my volume buttons in fastboot, basicaly I can't do anything at all in fastboot...no volume buttons, no power button and it can't be recognized.
Volume buttons work when phone is turned on.
Someone please help!!
Click to expand...
Click to collapse
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
delete pls , my mistake sry
simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!
forumsid987 said:
I have tried that so much I think I'm going to break my phone.
I just need someway to return this phone to stock without expecting fastboot to work because it seems like it is unresponsive since the power button is not working. I know this sounds weird as heck but I have all the correct drivers installed but three different computers don't see any kind of usb device connected when the phone is in fastboot. I sincerely believe it's because while in fastboot my messed up powerbutton is screwing it up because it's thinking that the power button is held down the entire time.
If anyone has any ideas on how I can get back to stock please tell me. I have 100% access on my phone when it's in recovery because I can use the buttons at the bottom and I have 100% access when it's fully booted up but when it's in fastboot I can't do anything and no computer even sees a USB device connected to it.
Pleaseeee help!!
Click to expand...
Click to collapse
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.
simms22 said:
i believe that my phone thinks my power button is always pressed down too, but fastboot works here. my suggestion is that you try a different usb chord. i had an usb chord that i could charge with fine, but nothing else worked. i thought my nexus one was messed up until i tried another usb chord.
Click to expand...
Click to collapse
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!
forumsid987 said:
I tried 3 cords, I'm going crazy here! USB works perfect everywhere but both fastboot and recovery don't let me use my volume or power buttons...at least I can get by in recovery because of the capacitve buttons but I need fastboot to return to stock to get a new phone. I am so frustrated!!!!
Click to expand...
Click to collapse
have you tried pdanets website? http://junefabrics.com/android/
go there, download the free download and install it to youre computer. its tethering software. but thats not why you should try it. follow the on screen instructions after its installed and itll install the proper latest drivers for your phone. theres a chance your drivers might be out of date.
oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App
anyone have any other options/ideas for me?? It would be greatly appreciated
Find an Odin package. Put phone into download mode by installing battery, holding volume buttons while connected to USB.
Does anyone know if the 301k ohm resistor jig works for ns?
Sent from my Nexus S 4G using xda premium
ODIN doesn't work because of the gosh darn power button being broken.
I went kinda crazy and erased everything in recovery so now all the phone does is boot straight into fast boot. I deleted the boot.img recovery everything, hahahaha (I laugh but really I'm crying inside).
I need a fix ASAP, I'm officially out of a phone.
simms22 said:
tap or smack the back of the phone near the power button until the volume buttons let you scroll. thats what i do. at first it took me a long time, but now it takes me seconds.
Click to expand...
Click to collapse
Wow, this actually worked for me Thanks Simms!
I just got stuck in the same situation (http://forum.xda-developers.com/showpost.php?p=22884288&postcount=24) so I kept tapping the back of my phone (with the back cover off). Fastboot kept restarting at first, but then my volume keys started allowing me to change options. I selected recovery and nandroid restored my phone. Now all is well *wipes brow*
Funny thing is, my power button now works properly again (it hasn't been working for the past week)
forumsid987 said:
oh yeah. Used pdanet drivers and Google drivers. No luck with either. I can adb with both but like I said the deicer is not the issue it's that fastboot is totally unresponsive so it looks like nothing is connected to the pc
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!
kajik123 said:
have you found any solution? I have the exact same problem here: powerbutton stucks and no usb-recognition in fastboot (no luck with the tapping either) but no problem with adb in normal mode.
would be great to know if you found a way to deal with this. Thanks!
Click to expand...
Click to collapse
Same problem here.... going crazy since the power button just died on me. I think the device thinks the button is pressed all the time, which makes it a hw issue.. any help to retrieve data on phone would be great!
Having the same problem as the OP...
Pls can someone find us guys a solution.:crying:
Thanks
I had a broken power button and had the same problem. I just sent it back to Samsung with no ROM on it and they fixed the power button and put Gingerbread back on it even though I had voided my warranty by unlocking the bootloader ;')
MistaJae said:
Funny thing is, my power button now works properly again (it hasn't been working for the past week)
Click to expand...
Click to collapse
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app
caleb1783 said:
yeah. mine started workin again after installing jb... almost made me believe it was software problem
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Mine broke when I installed Jelly Bean. Something fishy is going on. Now I have the same issue as OP.
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Cronoadvan said:
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Click to expand...
Click to collapse
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
nlheiz said:
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Click to expand...
Click to collapse
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
tingtan said:
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
Click to expand...
Click to collapse
The screen does not light up at all, and USB is accessible after around 4 secs of long pressing power and hearing the click noise(camera?) which is not normal since no device boots so fast. This tablet never did anyway, taking from 20 to 30 secs.
After USB is available I can adb shell from windows but that's pretty much it, I don't know what to do afterwards.
Cronoadvan said:
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
Click to expand...
Click to collapse
Check your serial number. If its below B70 you got SBK1.
Goatshocker said:
Check your serial number. If its below B70 you got SBK1.
Click to expand...
Click to collapse
Yes it is, it's B50. Is that a bad thing?
Cronoadvan said:
Yes it is, it's B50. Is that a bad thing?
Click to expand...
Click to collapse
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
nlheiz said:
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
Click to expand...
Click to collapse
Thank you so much! That was my last resort and sadly was clueless on how to do that too!
Hopefully it's just some kind of weird software coma, but now even if it's a hardware problem there is still hope!
Thank you very much good Sir, may life repay you thrice as much
Your welcome......please read the apx and nvflash option really well. It is rather straightforward but you have to install the apx drivers correct and use power and volume + (together) to enter apx mode. Voor drivers maybe you can use this forum below:
http://forum.xda-developers.com/showthread.php?t=1185104
it had an option for installing apx drivers for win 7 64 bit.
Hope your screen will work again, and if not you can send it back without warrant loss...
good luck!!!!!
I hope I can save it but after 4 hours of trying and reading I can't seem to do it.
I was running an unlocked tf300 with cleanrom. I wanted to update to the newest version of cleanrom and have my tablet on that and ready for school for next term. I downloaded cleanrom on laptop and put it on my micro sd. Went and grabbed the tablet and tried using rom manager to install from sd and backup the os that was on it. Didn't work. So booted into the fastboot spot (vol down and power) and decided i should wipe data since i was there. Went over to that and pushed vol up (once). Let it sit for like 45 minutes and was still on the same screen. Thought to myself well it must be done. Shut off the tablet to restart it.
This is where the problem came up. Now i'm stuck on asus logo. The VD+P doesn't do anything but reboot into the asus logo. The VU+P will put it into a black screen and windows sees it as Asus transformer Prime APX interface. But adb can't see the device. Just device manager. typing fastboot -i 0x0b05 thing just says <waiting for device>
Every post i've read seems to tell people to just push VD+P but if i could do that and get to recovery i wouldn't be doing this. I can't put a blob file into the root sd of the tablet because I can't see the tablet.
Any help would be greatly appreciated.
Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
bigworm82 said:
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
Click to expand...
Click to collapse
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
tobdaryl said:
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
Click to expand...
Click to collapse
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
bigworm82 said:
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
Click to expand...
Click to collapse
Are you in fastboot mode or apx when you give the commands?
tobdaryl said:
Are you in fastboot mode or apx when you give the commands?
Click to expand...
Click to collapse
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
bigworm82 said:
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
Click to expand...
Click to collapse
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
tobdaryl said:
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
Click to expand...
Click to collapse
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
bigworm82 said:
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
Click to expand...
Click to collapse
apx or bootloader menu-recovery.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard) reset is located about 25mm or 1in below the sdcard
try this one.
tobdaryl said:
apx or bootloader menu-recovery.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
try this one.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
Click to expand...
Click to collapse
nope just back to asus logo
bigworm82 said:
nope just back to asus logo
Click to expand...
Click to collapse
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
tobdaryl said:
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
Click to expand...
Click to collapse
Device not found.
bigworm82 said:
Device not found.
Click to expand...
Click to collapse
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
tobdaryl said:
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
Click to expand...
Click to collapse
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
bigworm82 said:
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
Click to expand...
Click to collapse
I'm sorry, I did understand that from the beginning but the only things that can save you is get into that menu or recovery or your tab accepts a fastboot or adb command. That is the reason you keep getting pushed into that direction.
My best guesses are out. Sometimes redoing something you have already done twice works.
My experience and all I have read rom manager has issues on this tab. Also many who wiped data from the bootloader- recovery menu reach this same point when they reboot.
Some have recovered by just doing each thing again and again and suddenly something works.
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
bigworm82 said:
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
Click to expand...
Click to collapse
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
tobdaryl said:
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate the attempts though . I really didn't want to have to call them lol.
bigworm82 said:
I appreciate the attempts though . I really didn't want to have to call them lol.
Click to expand...
Click to collapse
If you explain you were having issues with your tab and used wipe data hoping to correct the problem. Now when you turn on it just stays on the asus logo maybe they will repair it without cost.
If you go into detail you probably won't get lucky.
OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US
If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.
Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.
Hold power button until phone turns off. Turn phone on while holding volume down.
tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.
lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again
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