Hi All,
i rooted my phone using what i thought was the right img file, but i can only assume it was the wrong file as i can now do nothing, i can boot into the Moto symbol, i can get to the droid with the warning triangle and into the fastboot section but i can no longer detect it when connected to the usb...
can anyone suggest a fix or am i screwed ??
thanks for any help
Try reflashing it with my tool, using unbrick feature, maybe you need fastboot drivers, just download it from sdk
Sent from my awesome ICS Xoom with xda Premium HD
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
TheWhiteDragon said:
cheers xxlordxx
ill give that a go, which drivers do i need to install for the fastboot ?
i downloaded the google usb driver package via the SDK last time, but it seems they are not firing up when i connect the tab.
Click to expand...
Click to collapse
If you can boot, you are not bricked - just start over with the root process using the correct image.
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
tried doing the same using the different modes.
on Pad
Starting RSD Protocol Support
Same result on LAIOT
Recovery -
Same result.
this has all been done on a windows 7 laptop,
i have a linux laptop, will i get any more success using that with the google driver ?
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
TheWhiteDragon said:
just had a brain wave, checked device manager - i have an unknown device detected.. thats where the sodding thing has been hiding...
any ideas what drivers i need to get the dam thing detected correectly ?
just going to try using the default google ones from the SDK.
Click to expand...
Click to collapse
Try a diff USB cable - download drivers from MOTOROLA website get this file - MotoHelper_2.1.32_Driver_5.4.0.exe
Okay here we go....
first thing let your xoom stuck on M logo.
Then hold power+volume up.
while power up press volume down to get firstboot.(make sure your PC and xoom know each other.)
You will see some text firstboot bla bla bla on left, top of screen.
Second thing open window cmd.exe
then type ...
cd /AndroidSDK/tools (where ever your adb.exe is located)
fastboot flash boot boot.img (the right boot image)
fastboot flash system system.img
fastboot erase cache
fastboot reboot
wait for reboot. You should see splash screen and you smile on your face.
TheWhiteDragon said:
hey guys,
i have downloaded LAIOT but im not sure its detecting the pad, currently im getting
Searching For Device
List Of Devices
(Nothing listed)
on the pad
Starting Fastboot Protocol Support
Click to expand...
Click to collapse
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
thanks Mjamocha
ill give it ago tomorrow, sorry been flat out at work.
ill also try xxlords again on another machine just incase its the drivers on the laptop which are the problem.
XxLordxX said:
I need to fix it then...
Sent from my awesome ICS Xoom with xda Premium HD
Click to expand...
Click to collapse
sorry guys i have been flat out at work, SCCM deployment is taking a while to learn & play with.
but im back now and hopefully unbuggering my phone
i am going to redo all the bits you guys suggested on my PC rather than Craptop.
hopefully ill have more joy, ill let ya know how i get on 8)
What about using RDS?
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
TheWhiteDragon said:
woot im back
Thanks guys, just needed a fresh machine to do it on, think the craptop was a bit confused with the drivers.
Click to expand...
Click to collapse
Glad you got it going!
Had a similar problem where I had a boot loop and adb didn't recognise my device, but I could still put it into fastboot or recovery with power + vol down.
What I did was boot the Xoom so that it was stuck at the Moto logo, connected to the PC and queued up the fastboot command (fastboot flash boot boot.img) so the command window said "Waiting for device...", then reset the Xoom and manually put it into fastboot again at which point it picked up the queued command and started flashing.
Related
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
You don't need to boot in recovery, boot in bootloader only.
polobunny said:
You don't need to boot in recovery, boot in bootloader only.
Click to expand...
Click to collapse
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
bahagiga said:
I think I might have confused the terms bootloader and recovery mode, what I meant was I press the vol up button and the power button at the same time which then opens the bootloader I guess? anyways, still the same issue for me.
Click to expand...
Click to collapse
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
http://junefabrics.com/android/
polobunny said:
Yes that's the bootloader.
Have you installed the ADB drivers? You don't need only the adb and fastboot executable, but also the drivers.
Under Windows, you can install the PDANet software which makes driver installation a breeze on most cases.
link
Click to expand...
Click to collapse
Hmm, on the third step where it says "installing pdanet to your phone" it just like freeze and on my phone in the bottom it says "FASTBOOT STATUS - FAILInvalid Command"
what should I do??
bahagiga said:
Hi,
I have a Nexus S model GT-I9023 which is broken and now Im trying to recover some photos. I searched for a whole lot of guides and I think Im doing it right but can't get it to work.
I acidentally dropped it into a bucket of water, I let it dry and the next day it worked and on for about a week. Then it suddenly stopped working and I couldn't boot my phone, it wouldn't go pass the startup text "Google" and the lock icon.
I have the android SDK installed including the Google USB drivers. I added the PATH to tools and platform-tools. In the terminal i type "cd C:\Program Files\Android\android-sdk\tools" and hit enter and afterwards type "adb devices". It starts the daemon up etc. but does not list any device.
Note: since I cannot boot up the phone and enable usb debuggin I boot the phone up in recovery mode which I think should work and is the same as enabling USB debuggin, if Im not wrong.
I suspect that maybe it's because of the recovery mode or because some drivers. I don't think my computer recognize the devices regularly but Im not sure what it really is.
Any help would be appreciated
Click to expand...
Click to collapse
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Bkadleck said:
Can you boot into "recovery" and mount the sd from there?
Sent from my Nexus S 4G using xda premium
---------- Post added at 04:54 PM ---------- Previous post was at 04:50 PM ----------
If you can get to bootloader you should be able to get into recovery. And from there you should be able to mount your sd.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I tried but I dont think I can, when I try it just goes into that 'bootup screen, with the Google text and lock icon'. :/ Not sure what to do
Im still stuck and havent been able to get around this, any helpful information is appreciated. Thanks in advance
Hey guys, Im still stuck with this issue. Anyone who has some tips on what to do or has an idea of what it could be? I just formatted my PC yesterday Windows 7 32bit and everything should be up to date.
Kind regards,
baha
If there's anyone out there I would greatly appreciate your help! I have some pictures that are very valuable to me (pictures of my dog) and would really love to see if I could recover them.
I cannot start up my phone the "normal" way, I can only start up the Fastboot mode. I have the Samsung phone drivers installed along with the Google USB drivers. I have attached a picture that shows that there should be no problems with the drivers. I have tried to use the google usb drivers specifically but still the same. I have also attached a picture of the command prompt and as you can see nothing really happens. I have tried different tutorials and all kinds of ways trying to make it work but I have no clue what the problem is since I am not getting any other error message.
Any help is appreciated, please!
I typed fastboot devices in the cmd prompt and it actually listed a device serial number which matches then one stated on my phone in the fastbootmode. Any idea what to do or what this means?
I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.
greatanomaly said:
I've searched the whole sight and tried a bunch of so called fixes and still when i plug in my atrix 2 in boot mode (only it boot mode it does this) all i hear is instead of the dehdo that lets u know its connected i hear duhduhduh and RSD doesnt detect my device... im trying to fxz to 2.3.5 then ota upto ICS then root but i cant do any of these because of this please help.
Click to expand...
Click to collapse
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.
1BadWolf said:
First and foremost, this belongs in the q&a section. Is your phone an MB865, an ME865, is it AT&T branded? Have you tried uninstalling then reinstalling the Motorola drivers on your PC? Tried a different USB port and/or another PC? Can you give a little more information? Awesome sound effects, by the way.lol
Sent from this thing.
Click to expand...
Click to collapse
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...
greatanomaly said:
thank u lol but im sure u can imagnine the sound an...
AT&T
MB865
and i do believe i said ive tried nearly everything that is listed on this site well other sites to...
I dont need special files for my special model phone or the fact that its at&t but if that information helps u make it connect to my pc like it does when its not in fastboot then there ya go and btw to the Q/A section they can move it...
Click to expand...
Click to collapse
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.
stuck on boot logo
1BadWolf said:
Yeah, I was kidding. This site can be too serious at times. I know you said you tried everything, but a lot of people say that and it isn't always true, especially when they ask questions on the same day they became a member. I wasn't trying to offend you or insinuate anything. I asked if you had an AT&T branded phone because I was curious as to why you wanted to flash to 2.3.5 then ota to 2.3.6 then ota again to 4.0.4 instead of using this:
http://forum.xda-developers.com/showthread.php?t=1961310
to go straight to 4.0.4?
So your PC isn't detecting your phone, but ONLY when in fastboot mode, correct? Is the phone detecting the PC? By that I mean, on my phone when I boot into fastboot mode, at first it says:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Connect USB
Data Cable
Then when I connect it to the PC it changes to:
AP Fastboot Flash Mode (S)
0A.72
Battery OK
OK to Program
Transfer Mode:
USB Connected
Are you at least getting that?
Sent from this thing.
Click to expand...
Click to collapse
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Gr8mobiPro said:
no sir ny fone is not showing this
it still says
Connect Usb
data cable
i stuck while i was on jbleak 4.1.2 and through SD card i flashed CM 10.1
once it worked but now it stucked on the boot logo ... it appears and gone ... and then shows black screen.
even in recovery when i tried to reinstall same zip file of CM10.1 it failed on signature verification.
please help me sir help me..!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Chill man..nothing to worry about..please install motorola drivers..it should work.
its still not working
nishant203 said:
Chill man..nothing to worry about..please install motorola drivers..it should work.
Click to expand...
Click to collapse
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:
Use Virtual PC
I still have the same issue. I have installed Windows 7 on VM Ware workstation i.e virtual desktop and then followed the below steps :-
-Reboot your Virtual PC
-Install Motorola drivers.
-Reboot your computer
-Install RSD Lite
-Reboot your computer
-Boot your phone into Fastboot mode
-Connect your phone to your computer using a high-quality (preferably OEM) cable.
-Let your PC install any necessary drivers. When it finishes it should tell you that the device "Fastboot Edison S" is ready for use.
-Turn your phone off, disconnect the cable
-Reboot your computer
-Boot your phone back into Fastboot mode
-Wait a couple seconds then connect your phone to your computer
-Wait a couple more seconds, then look at the bottom text that's displayed on your phone. It should say
This means that your phone is connected to your computer.
-Open up RSD Lite
-Wait a couple seconds. At the top of the list should be your phone (under model it should say "Fastboot Edison S")
-If you've done all this and everything has worked out for you, flash the fxz! Make sure to follow the instructions in the noob thread as specifically as possible
Gr8mobiPro said:
wot motorola driver ..?? i have installed moto device manager and it is not showing any thing connected.. because it remain in boot mode..:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
This seems to be happening more lately. it IS a driver issue of some sort, that is for sure. I would just use one of the scripts, or moto-fastboot manually. they do the same thing as rsd but through command line either with your own typing, or a .bat script.
This may also work better in linux, so you can try downloading a live cd/usb of ubuntu and seeing if it is recognized. no need for drives with linux, just download one of the scripts that includes the moto-fastboot utility. Let me know if you need more help.
same issue
i am having the same issue with my at&t atrix 2. it is soft bricked due to an upgrade from gb to jbleak. ap fastboot flash mode (s) oa.65 battery ok ok to program connect usb data cable same message i have installed different motorola usb driver versions. i have also soldered the 4 pin to the 1 red+5v factory usb cable
https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNE6DkvEZi41YPAYKVPqH_AlA4f4cQ
but still my pc says unable to recognize usb device. i dnt what to do any more. im in mexico and purchasing a new phone is very expensive i need help is there something any one can do i am sure my device is not completely bricked i just cant get the mofokin pc to recognize the mofokin phone in fastboot
I have tried MILLIONS of method that I can found on Google.
The problem : -
1) My fastboot can't communication with the PC. (Tried all the uninstall - install - uninstall - blah blah blah)
2) Recovery current is 3e stock.
3) Stuck in the custom rom loading screen.
How to :-
1) How to flash back stock using 3e?
2) RSDLite can't work, what else can I do?
I'm despo now and my phone is bricked for a week.
Thanks for anyone who can help or solve it.
Please HELP me ~!!!!
3mperium said:
I have tried MILLIONS of method that I can found on Google.
The problem : -
1) My fastboot can't communication with the PC. (Tried all the uninstall - install - uninstall - blah blah blah)
2) Recovery current is 3e stock.
3) Stuck in the custom rom loading screen.
How to :-
1) How to flash back stock using 3e?
2) RSDLite can't work, what else can I do?
I'm despo now and my phone is bricked for a week.
Thanks for anyone who can help or solve it.
Please HELP me ~!!!!
Click to expand...
Click to collapse
See here
Sent from my MB865 using xda premium
3mperium said:
I have tried MILLIONS of method that I can found on Google.
The problem : -
1) My fastboot can't communication with the PC. (Tried all the uninstall - install - uninstall - blah blah blah)
2) Recovery current is 3e stock.
3) Stuck in the custom rom loading screen.
How to :-
1) How to flash back stock using 3e?
2) RSDLite can't work, what else can I do?
I'm despo now and my phone is bricked for a week.
Thanks for anyone who can help or solve it.
Please HELP me ~!!!!
Click to expand...
Click to collapse
This is very easy if you have an att phone. If not you will NEED to get the correct FXZ for you phone and download what I am about to link here, then put the correct FXZ for YOUR phone in the same location as in the download, and run the batch file, while your phone is in fastboot, as simple as that. If you do this RSDlite is not needed.
Link to the post with the scripts:
http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Again as it is, that is ONLY for AT&T phone, and you MUST get the proper FXZ for your phone, if it is not an AT&T phone, and put the FXZ in the same directory as the rest of the files with the script.
jimbridgman said:
This is very easy if you have an att phone. If not you will NEED to get the correct FXZ for you phone and download what I am about to link here, then put the correct FXZ for YOUR phone in the same location as in the download, and run the batch file, while your phone is in fastboot, as simple as that. If you do this RSDlite is not needed.
Link to the post with the scripts:
http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Again as it is, that is ONLY for AT&T phone, and you MUST get the proper FXZ for your phone, if it is not an AT&T phone, and put the FXZ in the same directory as the rest of the files with the script.
Click to expand...
Click to collapse
My phone is Asia Retail. Not AT&T.
Thanks for helping.
Please help... My pc cant detect fastboot.
Ths script and the EXTRACTED ota file all put in same folder?
THanksssss
3mperium said:
Please help... My pc cant detect fastboot.
Ths script and the EXTRACTED ota file all put in same folder?
THanksssss
Click to expand...
Click to collapse
1. Make sure your phone is fully charged (you can't fxz below 30%)
2. Install the correct driver and boot your phone to AP Fastboot
3. You don't have to extract the fxz file. just put them to C:/ as a whole
I recommend you read the instruction again
Obviously you have to get fastboot working. that should just be a drive issue, but you can try a new cable/ usb port/ computer. What rom did you have? you should be able to get into its recovery and flash again.
lkrasner said:
Obviously you have to get fastboot working. that should just be a drive issue, but you can try a new cable/ usb port/ computer. What rom did you have? you should be able to get into its recovery and flash again.
Click to expand...
Click to collapse
I'm on Paranoid Rom. The recovery is wiped for no reason and my current recovery is 3e ( with the vol up + vol down to make it shown). I tried 3 different cables, 1 lappy and 1 pc. It just can't recognize my fastboot.
3mperium said:
I'm on Paranoid Rom. The recovery is wiped for no reason and my current recovery is 3e ( with the vol up + vol down to make it shown). I tried 3 different cables, 1 lappy and 1 pc. It just can't recognize my fastboot.
Click to expand...
Click to collapse
Hmmmm.. what does the phone say when it is in fastboot mode and plugged in? Does it say "connect a usb cable" or whatever it is, or "USB connected- ready to program" (or whatever, you get the idea)
3mperium said:
I'm on Paranoid Rom. The recovery is wiped for no reason and my current recovery is 3e ( with the vol up + vol down to make it shown). I tried 3 different cables, 1 lappy and 1 pc. It just can't recognize my fastboot.
Click to expand...
Click to collapse
I was stuck in this same situation just last week, fastboot not being recognized and all. What operating systems do you have? I tried 4 (windows xp 32 and 64bit, windows 7 32bit and windows 8 64bit), and only xp would work a few times. So maybe you can try a friend's computer with xp or anything else. Which drivers are you using? because it worked for me with Motohelper, but not the latest drivers. Either way, keep trying different usb ports especially with the Motorola cable. Let me know if anything works, good luck! :thumbup:
Sent from the Ace's MB865 using xda app-developers app
lkrasner said:
Hmmmm.. what does the phone say when it is in fastboot mode and plugged in? Does it say "connect a usb cable" or whatever it is, or "USB connected- ready to program" (or whatever, you get the idea)
Click to expand...
Click to collapse
Ya... Connect USB, data cable... I tried all my lappy + pc usb port... Non of them are working...
Aceofzeroz said:
I was stuck in this same situation just last week, fastboot not being recognized and all. What operating systems do you have? I tried 4 (windows xp 32 and 64bit, windows 7 32bit and windows 8 64bit), and only xp would work a few times. So maybe you can try a friend's computer with xp or anything else. Which drivers are you using? because it worked for me with Motohelper, but not the latest drivers. Either way, keep trying different usb ports especially with the Motorola cable. Let me know if anything works, good luck! :thumbup:
Sent from the Ace's MB865 using xda app-developers app
Click to expand...
Click to collapse
I read about other threads that said motohelper would help... I tried end user driver, motohelper, end user driver+motohelper, older version driver etccccccccc.... Only thing is hard for me to look after is the motorola ori cable... Motorola is just so imba... :good:
3mperium said:
I read about other threads that said motohelper would help... I tried end user driver, motohelper, end user driver+motohelper, older version driver etccccccccc.... Only thing is hard for me to look after is the motorola ori cable... Motorola is just so imba... :good:
Click to expand...
Click to collapse
I see, that may be why it's so hard to get fastboot to work. :/ The A2 seems to only like working with the Motorola oem cable for many people, especially with AP fastboot. Well try what you can to keep the battery charged, and try what you can.
Sent from the Ace's MB865 using xda app-developers app
I would try using Linux. if you don't want to install it, you should just be able to use a live cd of ubuntu or something. it aught to work right off the bat, no drivers needed. you will ahve to use manual fastboot commands though, no fxz (so you will need to install moto-fastboot)
Anyone know where I can locate the APX drivers for the Tf700?
I've scoured Google and the only reference I could find linked to a file that was removed.
vexille said:
Anyone know where I can locate the APX drivers for the Tf700?
I've scoured Google and the only reference I could find linked to a file that was removed.
Click to expand...
Click to collapse
Check this post:
http://forum.xda-developers.com/showthread.php?t=2263822
LetMeKnow said:
Check this post:
http://forum.xda-developers.com/showthread.php?t=2263822
Click to expand...
Click to collapse
Tried those - didn't work.
vexille said:
Tried those - didn't work.
Click to expand...
Click to collapse
What is exactly "didn't work"? You can't install on your OS or your OS still can not recognize your device...
What OS are you running? I just want to know more information...
I couldn't get the universal drivers to work on win 8.1 either - even starting it in test mode. Yest to find apx drivers that work with it
LetMeKnow said:
What is exactly "didn't work"? You can't install on your OS or your OS still can not recognize your device...
What OS are you running? I just want to know more information...
Click to expand...
Click to collapse
Win 7 64.
Device originally detected as APX but with yellow !. Then Windows installed it as "unknown device".
Uninstalled that from Device Manager and rebooted. Connected tablet and get "unknown device" again.
When I try to update driver to those in link it says "best driver already installed"
Just tried those drivers on my notebook (fresh install of Win 7 64). Same thing - Unknown Device.
Think I have to face the fact that my tablet is bricked
vexille said:
Just tried those drivers on my notebook (fresh install of Win 7 64). Same thing - Unknown Device.
Think I have to face the fact that my tablet is bricked
Click to expand...
Click to collapse
Why is it bricked? Can you boot into your bootloader? What is exactly you want to do to your device? Maybe, someone can help you if you can tell us more details about your device. Your bootloader version, ROM, kernel, stock firmware, and your current state of your problems...
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
sbdags said:
I couldn't get the universal drivers to work on win 8.1 either - even starting it in test mode. Yest to find apx drivers that work with it
Click to expand...
Click to collapse
I took your advices a while back not to upgrade my system to Win8 so I am still running Win7, hahaha....:silly::victory:
LetMeKnow said:
Why is it bricked? Can you boot into your bootloader? What is exactly you want to do to your device? Maybe, someone can help you if you can tell us more details about your device. Your bootloader version, ROM, kernel, stock firmware, and your current state of your problems...
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I took your advices a while back not to upgrade my system to Win8 so I am still running Win7, hahaha....:silly::victory:
Click to expand...
Click to collapse
I attempted to update my CM10 ROM to CM11. Went through the process of upgrading CWM via Clockwork ROM Manager but I suspect that it didn;t work.
Booted into CWM, did a factory reset and Dalvik Wipe. Then attempted to install the CM11 ROM. It failed (can;t remember th exact error).
After that I could restart into the recovery menu (3 icons) - but the next time I tried to restart I ended up where I am now.
Endless loop of the Asus logo with the "device is unlocked" mice type - that's the only screen I get.
I can get into APX mode (I think) but when I connect the tablet to a PC it's not recognized.
Can Asus do a factory repair? I know I'll get cahrged for it but at this point I have a near mint tablet, the keyboard and very expensive leather case that's just junk if not.
vexille said:
I attempted to update my CM10 ROM to CM11. Went through the process of upgrading CWM via Clockwork ROM Manager but I suspect that it didn;t work.
Booted into CWM, did a factory reset and Dalvik Wipe. Then attempted to install the CM11 ROM. It failed (can;t remember th exact error).
After that I could restart into the recovery menu (3 icons) - but the next time I tried to restart I ended up where I am now.
Endless loop of the Asus logo with the "device is unlocked" mice type - that's the only screen I get.
I can get into APX mode (I think) but when I connect the tablet to a PC it's not recognized.
Can Asus do a factory repair? I know I'll get cahrged for it but at this point I have a near mint tablet, the keyboard and very expensive leather case that's just junk if not.
Click to expand...
Click to collapse
I think that I know why your PC did not recognize your device... Do you know how to use ADB? What is happening when you enter "adb devices" in your adb prompt? Does your Asus screen have a spinning circle under Asus logo? I guessed that you are stuck at the bootloader screen and waiting for your OS to start so there is no spinning circle...
Please answer those questions above and maybe some experts can help you out... Good luck...
LetMeKnow said:
I think that I know why your PC did not recognize your device... Do you know how to use ADB? What is happening when you enter "adb devices" in your adb prompt? Does your Asus screen have a spinning circle under Asus logo? I guessed that you are stuck at the bootloader screen and waiting for your OS to start so there is no spinning circle...
Please answer those questions above and maybe some experts can help you out... Good luck...
Click to expand...
Click to collapse
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
vexille said:
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
Click to expand...
Click to collapse
Oh well, you can not boot into your bootloader and can not get adb running. I hope that someone or experts can jump in and give you some good advices... Maybe, _that, sbdags, lj50036, and berndblb are actively helping users around here... good luck...:fingers-crossed:
vexille said:
No spinning logo.
adb devices =
* daemon not running. starting it on port 5037 *
* daemon started successfully *
List of devices attached
Then command line
Click to expand...
Click to collapse
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
berndblb said:
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
Click to expand...
Click to collapse
Thanks!
I'll give these a try tonight.
I see a bunch on eBay for under $250 so I imagine it would be cheaper to just ditch this one if I can't get it working as opposed to sending it back to Asus for repair.
vexille said:
Thanks!
I'll give these a try tonight.
I see a bunch on eBay for under $250 so I imagine it would be cheaper to just ditch this one if I can't get it working as opposed to sending it back to Asus for repair.
Click to expand...
Click to collapse
I believe Asus charges $300+ for replacing the board, so yes, you're probably better off buying it on ebay.
Just don't ditch the old one too far - you may need the parts. Or you can sell them
berndblb said:
I believe Asus charges $300+ for replacing the board, so yes, you're probably better off buying it on ebay.
Just don't ditch the old one too far - you may need the parts. Or you can sell them
Click to expand...
Click to collapse
Well struck out on all accounts (I had left it plugged in at the Asus logo last night).
Appreciate all the help but I think it's eBay time for whatever I can get and sell the mobile dock and fancy leather case.
Then to decide what brand to get next....
berndblb said:
Did you have adb and/or fastboot working prior to this? Meaning, are you sure you have the necessary drivers installed?
Although, I'm afraid neither would help. You probably would not get an ADB connection since you can't boot Android nor boot into recovery or access via fastboot.....
The APX drivers would not help you unless you generated your device specific nvflash blobs prior to this disaster. Without them APX is useless to you.
But before you turn it into a paper weight I would make each and every desperate attempt to revive it I could think of.
For example:
Holding Power + Volume Down for 30 seconds or longer
Volume down + reset pin hole on the side of the tablet
If you have ADB drivers installed: Connect the tablet to PC, type: adb reboot-bootloader and reboot it - hoping that you get a second or two where ADB would connect during the next boot (very slim chance but what the heck...)
Connect the tablet to the wall wart, let it boot to the Asus logo and leave it there. Overnight for 8 hours or so (I have seen this working twice actually - although the situation was somewhat different...)
Beyond that it's prayers, voodoo or replacing the mainboard - sorry.
Click to expand...
Click to collapse
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
LetMeKnow said:
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
Click to expand...
Click to collapse
I've tried every suggestion and cannot get past the "device is unlocked" mice type and static Asus logo.
When using adb it doesn't find any devices. I'll be putting it up eBay tomorrow for whatever I can get.
Looking at the new Samsung Galaxy 8.4 Pro as a replacement.
LetMeKnow said:
Hi berndblb,
How are you these days? If vexille can get adb going, he/she could try to push the Asus firmware to the staging partition using dd command and hope for it to reinstall the bootloader....
@vexille
If you somehow can get into the fastboot mode, you may want to keep your device in that mode until you can successfully flash the new bootloader on your device. Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Hi LMK - you can't win'em all...
I'm good - just returned from a family visit to Germany. Fighting the jetlag - groan. And having to go back to serious work Friday - big groan.
So what did you replace the 700 with - if anything? I get you're snatching it away from your nephew once in a while to do some testing? What kind of a uncle are you? You are probably ruining all his game scores! LOL
berndblb said:
Hi LMK - you can't win'em all...
I'm good - just returned from a family visit to Germany. Fighting the jetlag - groan. And having to go back to serious work Friday - big groan.
So what did you replace the 700 with - if anything? I get you're snatching it away from your nephew once in a while to do some testing? What kind of a uncle are you? You are probably ruining all his game scores! LOL
Click to expand...
Click to collapse
I hope that you had a great time with your family... I am still looking and have not decide it yet.. I always backup my stuff before messing with the device. Plus, my nephew has a few hour of playing on the tablet per day any way.. So I can take it any time that I want, hehe....:laugh: I also have a higher authority as an uncle...:silly:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
osamarchie2000 said:
Hello everyone,
I have done something utterly stupid with my Nexus 5, I wiped the internal storage and lost my roms, I really wasnt thinking.
I have tried looking at options like adb sideload but cant find a decent tutorial
Could I just get a micro usb to usb adapter and install a rom off that?
Would anyone be able to point me in the right direction with adb sideload?
Other problems are I can't get on the android SDK because the CMD box only flashes up.
Does the adb sideload option in TWRP actually do anything if you wait for it? Its been waiting for about 1 hour now and nothings happening.
Please guys any help is appreciated
Click to expand...
Click to collapse
Why don't you flash the factory image using fastboot?
The Cmd box you are referring to happens because you need to navigate to that directory using Cmd and run it from there. You cannot just click it.
Thanks but I cant get the SDK to work at all. Im still looking into it but at the moment it wont work
Please somebody help me with the SDK, I dont know what else to do.
I cant open the SDK manager and I cant open it through eclipse either.
Someone else must have had this problem before
Click the link in my signature and then "adb and fastboot. What is it?"
This will help you configure adb properly. It also helps you learn commands. Like adb push.
adb sideload is the same as push but you type sideload instead.
FYI as much as people round here say it, there is no such thing as a soft brick. Its brick or not brick.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Show down and don't panic. Your device is easily fixed. Hold the power button for 20 seconds. This will shut down the phone. Then press and hold the vol down then press the power button. That'll bring your into the bootloader.
Sent from my Nexus 5 using XDA Free mobile app
osamarchie2000 said:
Switched off my phone and now I cant get it into recovery mode. Only the google logo which just stays there for ages
What do I do now?
Click to expand...
Click to collapse
Power + volume down button brings you in the bootloader, from there go into recovery (navigate with volume buttons and select with power button)
In recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=2559200.
Or flash the factory image in the bootloader. (that should work because you need to unlock your bootloader in fastboot)
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yeah that will work too. Water damage is never good for a phone even if it stil works after that. But that's another story
osamarchie2000 said:
Thanks guys,
It wasnt working because water damage had interfered with the volume buttons previously.
I have a micro usb to usb adapter now.
Can i put a rom on a USB drive and install that way?
Thanks guys
Click to expand...
Click to collapse
Yes you can. You'll have to "tell" twrp where to find the rom zip.
Sent from my Nexus 5 using XDA Free mobile app
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
osamarchie2000 said:
Only problem now is I cant get the SDK to work for my life. Ive spent 5 hours trying to fix my phone already today, I have the JDK installed. I open the eclipse thingy and when i try to open the SDK with eclipse it wont work either. Please somebody help with this
Click to expand...
Click to collapse
You don't need the SDK. You're not developing here
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
TWRP cant find any of the files on my USB-OTG
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Did you read my thread that I told you to read?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
osamarchie2000 said:
with the CMD, it gives me my device and its serial number and says recovery for
C:\adb devices
but for C:\fastboot devices
I get nothing.
Any ideas please?
Click to expand...
Click to collapse
Here's a hint, read rootSU's sticky rollup and look for the 15 second fastboot adb installer.
Sent from my Nexus 5 using XDA Free mobile app
Very sorry, Ive just re-read what Im looking for
Appologies
thankyou all, phone is well and good and im on CM11.
Thanks guys, anyone who helped is the best