Related
Hey everyone. I figured id make an official thread,although a thread a few down is very similar but still quite different.
I attempted to re-lock my XOOM wifi and I got the error.
-only able to get into RSD mode 2 or Fastboot protocol
-pc will not recognize through adb or RSD 5.0
-tried various command and no luck
-Screen wont turn off unless battery dies.
- reinstalled sdk, drivers etc.
I might of missed a few details, but ive been all around the forums and have yet to see a solution for this other than send it to Motorola. Ha just curious to whether anyone could shed a little more light on this situation. Not being able to RSD or adb seems like a bad situation, even if we did have that darn sbf id still be stuck! Thanks guys!
Sent from my DROIDX using Tapatalk
Try to get the xoom back into fastboot by rebooting (vol up + power) and then immediately holding vol down + power until the fastboot screen comes up. From there try pushing system and boot .img's through fastboot. Then you should be able to reunlock from the fastboot command on your pc. There is no way that I know of to re-lock a wifi only xoom as of yet.
Yeah, my bootloader screen says that im "Starting Fastboot protocol service" but I get no response from my PC. I've never had problems with adb recognizing my xoom before this. Its like the drivers arent even compatible with the device anymore?? For craps i attempted to send some commands through adb even though it didnt recognize the device, and had no luck. ADB simply replies "waiting for device" for all of them.
try reloading your moto drivers
Make sure you aren't using a front panel port. I had thus problem for ages, XOOM is a power hog. As for the LNX failure its the result of relocking with an invalid image, don't do it.
Sent from my HTC Desire using Tapatalk
Yeah, i spent days trying to figure that one out with the front ports vs. the back ports with my droid. I could never get it to remount in RSD when flashing a .sbf.
Thanks for the heads up though. Im not sure what made me think that it would be ok. My failure to do some research always lands me in pretty much the same spot! Here.
I reloaded all the drivers ect and have been unable to get anything. My droid works great, but no xoom.
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Xezuka said:
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Click to expand...
Click to collapse
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
This is the same of my problem:
http://forum.xda-developers.com/showthread.php?t=1052762
tritran18518 said:
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
Click to expand...
Click to collapse
Sorry I guess I didn't mean to set it to Debug from the Xoom, but as in to remove it and boot into Fastboot. Then plug it back in and allow Windows to install the drivers.
I had a hard time getting it to work, but after uninstalling and reinstalling the drivers, it recognized it and allowed me to flash the SBF.
Correct me if I'm wrong here! It's what worked for me. My Xoom went down like this and I resurrected it this way. Been working flawlessly on Tiamat 1.3.1 ever since.
Sorry guys, but the condition I'm in is becoming popular lately. I'm able to get the XOOM wi/fi to show "starting fastboot protocol" but absolutley no recognition on the pc. RSD or ADB. Therefore all commands sent from the ADB simply respond with "waiting for device" and unable to flash any images onto the device. Its in a real brick mode. At least for the time being with the lack of software communication on the pc and no .sbf yet. I sent the device into motorola for repair. They said the repair would be under the warranty and free of cost. I was honest as well, telling the repp I had unlocked the device and attempted to re-lock. Thanks for all the suggestions and input guys.
follow up?
hello i am curious what happened with your returned brick? did moto replace it?
I ask because i have the exact same issue and have gone through all the suggestions.
same error, cannot get into fastboot, no adb, no RSD, nothing. tried the various vol power button combos etc. no recognition on PC at all. yes i re-installed drivers etc etc etc... i have been reading...
it seems only option is to wait on SBF or return?
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
OK well its good to know I am totally screwed!!! thanks for the reply...
I told the rep on the phone what I did but I don't think he had any clue what I was talking about... he asked to me to reboot with vol up, then try to boot into fastboot, but didn't once say fastboot, just said vol down, then said he would send me a shipping box.
Get it today!!
I am in this situation after trying to re-lock in order to install the 3.1 update. I tried re-installing and updating the Moto drivers, rebooting etc but I can't get my PC to recognise the device in fastboot or RSD. I am on a stock Canadian ROM (but unlocked obviously).
I have sent an email to Motorola and been honest with them. Will see what they say.
That's the thing - moto provides all the tools to relock for US ONLY! There is no official way for canadians, which makes no sense. So us canadians can unlock no problem, but cannot relock, yet US units can? Strange to me...
chaz03 said:
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
Click to expand...
Click to collapse
Try rsdlite 4.9 or earlier it should see it then.
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
footboydog said:
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
crushsuitandtie said:
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
Click to expand...
Click to collapse
I have just tried this and still no luck. Fastboot just sits there with the "waiting for device" message and the Xoom just boots with the "Starting RSD mode 2" message. I also tried your suggestion with rebooting into fastboot mode by holding the vol down button and that doesn't work either.
BTW I don't have a custom boot.img. I am on a stock ROM but I just had the bootloader unlocked.
Incidentally I have tried RSD lite 4.8, 4.9 and 5.0 now and none work.
Hi,
today I woke up and my Nexus S was off. I turned it on and it just stucks while showing the google logo..
I tried pulling the battery, turning on.. still stucks!
so I tried do boot in Fastboot, ok.
Installed the SDK, the USB Drivers. The Nexus was recognized as "Android ADB Interface", ok.
Tried to list the device by "adb device", but I only said: list of devices attached. No device!
Then I tried "fastboot device". There it is! Trying "adb device" again, no device. mh.
So I tried to unlock the phone by typing "fastboot oem unlock".
I get the message on my phone, check "YES" and execute by pressing POWER, but no success. The phones stucks again. The cmd just says "...".
I spend 30min by watching on the cmd and the Nexus S, but no result.
What can I do?
Nexus S, locked Bootloader, 2.3.3, 2 days old
*push..*..
Can you get into the bootloader on the device? (Power and Volume Up)
Has it been rooted, and do you have CWM installed?
I can enter the the bootloader. Firmware is stock, unrooted!
I think the main problem is, that usb debug is not enabled in the device. Thats the reason why adb doesnt recognize it. But fastboot does ...
You can only use adb when the phone is booted up. Fastboot is for when the phone is in the bootloader.
Try going into recovery and doing a factory reset?
I don't know which phone you have, I'm on NS4G, got phone unlocked using GSM codes, so erased everything - a mess. When I got to backup using 2 finger method, there was nothing to reboot to
I went to Samsung site - found program called Samsung Simple DL for my phone, downloaded, executed and ran - back to stock. Kept it unlocked, but was back up and running.
I was paniced, so this might help
hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again
any ideas please?? or am i completely out of luck?
When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.
As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436
What we're your steps exactly? Did you relock your bootloader
a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Does anybody else have some more ideas?
Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?
kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.
Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you
Hello Xda community, I open this thread after two days of reading and trying different ways to solve my problem.
My Nexus 5 runs Android 5.1.1 which I got OTA, I've never Rooted, installed any ROMS or done anything that might violate the system or the warranty.:angel:
Few days ago I downloaded some crappy program to my PC called Wondershare Dr.Fone (BURN IN HELL !!!) that was suppose to recover my deleted photoes from the Nexus, during the process of syncing etc.. it asked me to open developer settings and turn ON debugging mode.. which I did... and after about 30-40 minutes of "working" I realized it FROZE
The program didn't have any "Abort" button, and it was already late, so I just disconnected my Nexus, and after a moment it restarted and went into Bootloop
First I waited about an hour to realize it was infinite, then I tried going into Recovery Mode and deleting Cache Partition then restarting... it also didn't help, whenever I tried to turn it off, it was just turning on again, showing the Google Logo and then bashing those infinite Spinning Google Ballz in my face (I can turn off the phone using the Bootloader which works just fine, but it doesn't helps with the bootloop)...
The next whole day I was trying to at least recover my photos and videos, hoping that I can use the ADB to Pull the Camera folder out... I tried to install maaaany Google USB drivers following the steps of dozen tutorials, downloaded the SDK Manager and tried to install them thru Google server, and even Installed Naked Drivers with Windows 8.1 Signature Check Disabled... and tried it on 3 different PCs (win 8.1 and 7) the result was the same: Nexus 5 remained invisible until I Clicked in recovery mode "ADB Sideload.." in which case my Nexus 5 appeared in Device manager under Other Devices section (which let me install the drivers) otherwise it was invisible for my PCs...
The problem: whenever I was lunching the ADB from it's folder and typing "adb devices" I saw some sort of serial number, and "Sideload" next to it (while in other tutorials people have the word "Device" instead) and every command such as "adb usb" or "adb pull /sdcard/" or "adb pull /Camera/" result in "Error: closed" :crying:
In despair I tried to Factory reset my Nexus, and after about an hour of wiping, it allowed me to reboot which ended up in another infinite Bootloop....
I don't know what to do now, I don't live in the States and don't have warranty, I feel it's really unfair how after preserving my Nexus and it's Stock OS for so long... some Dr.fone bull**** broke it...
Please help me save my Nexus
Yea well... I knew nobody would give a crap in here... >.>
iJutsu said:
Yea well... I knew nobody would give a crap in here... >.>
Click to expand...
Click to collapse
[sarcasm]Way to stay positive.[/sarcasm]
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
davehasninjas said:
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
Click to expand...
Click to collapse
Factory reset didn't give any results, just destroyed any hope of recovering the photos I had onboard...
The system did detect my device for some time only when I activated the "ADB Sideload.." in the Recovery mode, but it wasn't same as in most guides and tutorials I've seen... When I typed the command "adb devices" it showed "4bd...serial.. Sideload", while according to tutorials it should be detected as "4bd.... Device"... Also I think the phone should get detected even without pushing the "Adb Sideload"... but the main problem is that every command results in "Error: Closed" so I can Pull or Push or Sideload anything since it's always same error"... which made me think perhaps the drivers aren't Okey, but I tried every Nexus 5/Google driver I could find, and I really doubt it's the drivers fault.
As I said the device remains invisible both in Device Manager and in Devices and Printers, until I click the Adb Sideload on the Nexus...
Factory Reset didn't work even tho I've never did any root or install Stock ROM or Kernel or anything of that sort, makes me wonder if that Dr.Fone crap app actually bricked my phone...
Thanks for trying to help
beekay201 said:
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
Click to expand...
Click to collapse
Aw... that's what I suspected... But activating the ADB sideload is the only way to make my Nexus 5 visible when I type "adb devices".... Does the fact that my PC can see it during ADB Sideload means that the Drivers are installed correctly? what may be the problem then? uff..
Have u tried this
Since you dont mind losing your data, I guess u already did a factory reset, I seriously suggest trying this guide. Read carefully. It worked perfectly for me which was in bootloop after 5.1.1 update.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632