Related
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
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Did you have all the drivers?
Can you get to bootloader?
pert_S said:
Did you have all the drivers?
Click to expand...
Click to collapse
Up to my knowledge, no driver is required on a mac.
pert_S said:
Can you get to bootloader?
Click to expand...
Click to collapse
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
sylar12 said:
Up to my knowledge, no driver is required on a mac.
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
Click to expand...
Click to collapse
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
pert_S said:
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Click to expand...
Click to collapse
Yep. No response so far, but the problem appears a few hours ago only.
I'm pretty sure my bootloader is corrupted. But does that prevent the device to power on?
Any other idea?
sylar12 said:
Any other idea?
Click to expand...
Click to collapse
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
abaaaabbbb63 said:
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
Click to expand...
Click to collapse
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
sylar12 said:
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Click to expand...
Click to collapse
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
sylar12 said:
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
Click to expand...
Click to collapse
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
gee2012 said:
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
Click to expand...
Click to collapse
This is not "directly" required on mac. And the fastboot binay has been recognized by the shell, since the unlocking procedure started (my phone asked me if it was ok for unlocking the bootloader).
abaaaabbbb63 said:
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Click to expand...
Click to collapse
I already tried this: nothing happens... I guess the phone is really bricked.
eddie_gordo said:
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
Click to expand...
Click to collapse
It should be the same, yes. Fastboot is very easy to use usually, it's the first time I have such a problem. And I have no idea why the unlocking has got wrong. 2 solutions imho:
- a phone harware problem which only reveals during the unlocking process;
- a fastboot problem/mac related problem.
Just trying to figure out which one is the correct answer.
El Daddy said:
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
Click to expand...
Click to collapse
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
I think you got really unlucky. Possibly a bad cable or USB port but some connection got lost while you were flashing. RMA is your best option right now. Sorry bro
abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their phone.
Click to expand...
Click to collapse
Yessssss, I did it!
...
:crying:
abaaaabbbb63 said:
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't they will).
Click to expand...
Click to collapse
You'll be fine on the rma. Been there done that on another device
sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
Click to expand...
Click to collapse
Maybe the XDA award for the1st N5 bricker is a new Nexus 5 32GB
abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
Sorry to disappointed you but I was the first one. Last week I bricked mine
Update: Solved.
Summary of issue: two identical devices side-by-side, s-off by Firewater works fine on one and won't work on the other. This rules out a lot of possible issues and so this was not an "I don't know how to use firewater's s-off method" post.
Solution: Factory reset FOUR TIMES. On the fourth factory reset, things worked.
Lesson learned: (After you make sure you're actually doing everything right and with the right files) you might actually have to give this many tries.
Cheers.
Thanks @pjim @Dodge DeBoulet @wtoj34
Hey everybody, Recognized Contributor here, usually the one who’s glad to help everybody else, and I’m totally… at a loss. Thanks X 10 for ANY help. I’m looking forward to contributing and modding on the Verizon M8 soon!
Issue: Two identical CDMA M8 devices, both on my Verizon account. Literally the same activation, using the same usb port, usb cable, computer and human:
Device #1: temproot using WeakSauce.apk; s-off using Firewater; installed the CWM recovery for our device; made a nandroid; flashed iB4STiD’s SkyFall ROM. ALL GOOD 100%.
Device #2: temproot using WeakSauce.apk; …. Firewater’s s-off will not do its thing with device #2. It goes only this far:
Code:
Do you understand the implications of these warnings? (Yes/No)
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
…………………………………
……………………………….
……….. (indefinitely until I disconnect; I've waited 30 minutes just to be sure)
So it STOPS BEFORE the “preparing… the first bottle is open…chugging… ” part.
But… it ran five minutes before. Device #1 is good to go. Device #2? I’ve tried the hold power for 60 seconds thing, used different usb cables, different ports (hey, maybe something broke in the 30 seconds between devices?), redownloaded everything, matched MD5 checksums anyway, hard reboot via adb, repeat, start over like ten times…
For the love of God, can anyone think of what I can be doing wrong?
So funny...........
erikalin said:
Hey everybody, Recognized Contributor here, usually the one who’s glad to help everybody else, and I’m totally… at a loss. Thanks X 10 for ANY help. I’m looking forward to contributing and modding on the Verizon M8 soon!
Issue: Two identical CDMA M8 devices, both on my Verizon account. Literally the same activation, using the same usb port, usb cable, computer and human:
Device #1: temproot using WeakSauce.apk; s-off using Firewater; installed the CWM recovery for our device; made a nandroid; flashed iB4STiD’s SkyFall ROM. ALL GOOD 100%.
Device #2: temproot using WeakSauce.apk; …. Firewater’s s-off will not do its thing with device #2. It goes only this far:
Code:
Do you understand the implications of these warnings? (Yes/No)
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
…………………………………
……………………………….
……….. (indefinitely until I disconnect; I've waited 30 minutes just to be sure)
So it STOPS BEFORE the “preparing… the first bottle is open…chugging… ” part.
But… it ran five minutes before. Device #1 is good to go. Device #2? I’ve tried the hold power for 60 seconds thing, used different usb cables, different ports (hey, maybe something broke in the 30 seconds between devices?), redownloaded everything, matched MD5 checksums anyway, hard reboot via adb, repeat, start over like ten times…
For the love of God, can anyone think of what I can be doing wrong?
Click to expand...
Click to collapse
As an auto technician, when someone says my car wont start my first question is, is there any gas in it? The first thing I would look for is the root. I have literally had weaksauce take up to 3 minutes to get root. If in the excitement you start adb and get firewater running before you get root, it cant write to the system and would get stopped,probably around where you are getting stopped. Make sure root is working before you even plug in the cable. Do something simple like start a root app and grant it before you start. As I read through these forums forums I've seen that this device is not consistent in it's behavior. One will not be the same as the other. Could even be internal, might consider an exchange. Usb ports fail all the time.
Hi. Thanks for taking the time. Yes, I'm waiting for root. Adb wouldn't be able to access root if, well, it didn't have access to root. (Not being sarcastic, just check-listing in my head.) I also have my laptop set to make a noise when it has root access. USB port is fine. Ugh. :/ I'm not sure I can come up with any reason to exchange. Thanks for trying. Cheers.
Sent from my SPH-L710 using Tapatalk
erikalin said:
Hi. Thanks for taking the time. Yes, I'm waiting for root. Adb wouldn't be able to access root if, well, it didn't have access to root. (Not being sarcastic, just check-listing in my head.) I also have my laptop set to make a noise when it has root access. USB port is fine. Ugh. :/ I'm not sure I can come up with any reason to exchange. Thanks for trying. Cheers.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I'm assuming you don't have any additional security measures enabled, such as a pattern or password lock (disabling that stuff is in most of the how-to's I've seen). Have you attempted a factory reset/do-over from scratch?
Try some of these I picked up from other forums. Have you tried factory resetting the device? Have you tried re installing adb on your computer? Have you tried removing the firewater file from your phone, and re download it on the pc? Does the firewater file have a (1) next to it? Have you tried uninstalling weak sauce and super su and do adb reboot on your pc then re root? Are you using the same account on your pc as your other phone?
Sent from my HTC6525LVW using Tapatalk
Dodge DeBoulet said:
I'm assuming you don't have any additional security measures enabled, such as a pattern or password lock (disabling that stuff is in most of the how-to's I've seen). Have you attempted a factory reset/do-over from scratch?
Click to expand...
Click to collapse
Hi. Thanks for taking the time to try to help me out. Yes, no security/lock stuff. Have tried factory reset and do-over from scratch at least twice, no joy.
wtoj34 said:
Have you tried factory resetting the device? Have you tried re installing adb on your computer? Have you tried removing the firewater file from your phone, and re download it on the pc? Does the firewater file have a (1) next to it? Have you tried uninstalling weak sauce and super su and do adb reboot on your pc then re root? Are you using the same account on your pc as your other phone?
Click to expand...
Click to collapse
Appreciate you taking the time. No need to reinstall adb stuff on my computer (I use the Android SDK for a lot of things; it's fine). Accounts on PC don't matter. Just "thinking out loud" here. I think I've done every combination of your other ideas too. Thanks again for sharing the ideas though...
There's either something I can't think of trying OR there's some odd little thing wrong inside the second device, and I can't think of any legit reason to bring it back for replacement because it otherwise acts fine. Ah well. People have bigger problems, lol. Cheers.
Update: Solved. See OP.
erikalin said:
Update: Solved.
Summary of issue: two identical devices side-by-side, s-off by Firewater works fine on one and won't work on the other.
Solution: Factory reset FOUR TIMES. On the fourth factory reset, things worked.
Lesson learned: You might actually have to give this many tries.
Cheers.
Thanks @pjim @Dodge DeBoulet @wtoj34
Click to expand...
Click to collapse
Wow, never would have guessed that repeated FRs would do the trick. Was that 4 in a row after your previous attempts, or 4 total throughout the entire S-OFF ordeal?
My own experience was entirely uneventful; the only bit of panic I've experienced with this remarkable phone was well after the root/S-OFF activity, during the installation of GSAM Battery Monitor. Installation of the root companion package required a reboot, and nothing appeared to happen after the confirmation button was pressed. When I manually rebooted, I got what seemed to be a "White Screen 'o Death," with no response from the usual reboot key combo. At some point the display went dark and I was sure it was bricked. I eventually tried the 60 second power button press, though, and it booted normally. Incidentally, GSAM appeared to be successfully installed as well.
USB 2.0 vs 3.0
I also haven't had any good luck with the firewater s off...mine hangs right after I say "Yes" then my phone diaconnects from adb and I have to start the process over again.
I've tried over 30 times, but I think it's been on usb 3.0 ports. I'm going to try on 2.0 and if that doesn't work...factory reset time...
Good Evening all,
I am coming here after trying for well over 4 hours to fix this issue, I'll go into as much detail as possible here:
Stock Android 5.1.1
Had the phone since launch day
No warranty
So, yesterday afternoon I was trying to take a picture of this lock I came across.. however, when I opened the camera app it was unable to connect. meh, I've had this issue before! It is usually fixed by retrying, or making sure I don't have the flashlight on through the drag-down bar. The Flashlight icon was on, despite my flashlight not actually being enabled. I clicked to turn it off, and then it switched it on. Weird! I clicked it again, and the phone realised it was actually off and kept the icon as off.
I then went to use the Camera again to no avail. So, I quite simply turned the phone off and attempted to switch it on again. This is where the fun starts - I am then met with the Google balls spinning, and spinning, and spinning, and spinning. This has happened once before, and that was when I first installed Android 5.0 - it took a good 20 minutes before it booted up, so I decided to leave it for a while. Fast forward two hours, it is still going. Yep, it's not booting. I again switched it off and back on, in the hope it would miraculously fix itself - it didn't. I decided to leave it going overnight, in the hope that something was just really, really broken and required a lot of work to fix - no, still nothing. Just the annoying balls flying around.
So tonight I connected the device up to my PC, booted into recovery and attempted to install the latest device image (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701). Now, I am running Windows 8.1, getting the official nexus drivers to work or to even get the device into fastboot is a massive chore - and took me a while. Once I finally got it going (and to note, it has always been that bad!) I hit the "flash-all.bat" file and away it went.
It then got to the point where it needed to reboot into the bootloader, it was at this point that Windows reported the device malfunctioned (with code 43), Device Manager reported the following: device descriptor request failed - I had to keep unplugging and replugging the device to get the bat file to continue, and it got to the end (without any visible problems within the commandline) and rebooted my device.
Now, I am back to these damn balls.
Can anyone offer any assistance with this? Have I bricked my device? I don't care about my data, I just need my device for work!
Thanks,
Jake
jake.Hall30 said:
Good Evening all,
I am coming here after trying for well over 4 hours to fix this issue, I'll go into as much detail as possible here:
Stock Android 5.1.1
Had the phone since launch day
No warranty
So, yesterday afternoon I was trying to take a picture of this lock I came across.. however, when I opened the camera app it was unable to connect. meh, I've had this issue before! It is usually fixed by retrying, or making sure I don't have the flashlight on through the drag-down bar. The Flashlight icon was on, despite my flashlight not actually being enabled. I clicked to turn it off, and then it switched it on. Weird! I clicked it again, and the phone realised it was actually off and kept the icon as off.
I then went to use the Camera again to no avail. So, I quite simply turned the phone off and attempted to switch it on again. This is where the fun starts - I am then met with the Google balls spinning, and spinning, and spinning, and spinning. This has happened once before, and that was when I first installed Android 5.0 - it took a good 20 minutes before it booted up, so I decided to leave it for a while. Fast forward two hours, it is still going. Yep, it's not booting. I again switched it off and back on, in the hope it would miraculously fix itself - it didn't. I decided to leave it going overnight, in the hope that something was just really, really broken and required a lot of work to fix - no, still nothing. Just the annoying balls flying around.
So tonight I connected the device up to my PC, booted into recovery and attempted to install the latest device image (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701). Now, I am running Windows 8.1, getting the official nexus drivers to work or to even get the device into fastboot is a massive chore - and took me a while. Once I finally got it going (and to note, it has always been that bad!) I hit the "flash-all.bat" file and away it went.
It then got to the point where it needed to reboot into the bootloader, it was at this point that Windows reported the device malfunctioned (with code 43), Device Manager reported the following: device descriptor request failed - I had to keep unplugging and replugging the device to get the bat file to continue, and it got to the end (without any visible problems within the commandline) and rebooted my device.
Now, I am back to these damn balls.
Can anyone offer any assistance with this? Have I bricked my device? I don't care about my data, I just need my device for work!
Thanks,
Jake
Click to expand...
Click to collapse
You did not bricked your device, it bricked itself. Take a look at this.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
bitdomo said:
You did not bricked your device, it bricked itself. Take a look at this.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
Thanks for that, however, I am completely unable to use Recovery. I boot into it, and Windows flat out refuses to anything but complain:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Like I say, always had issues with adb on this machine. The device is recognized as an Android Fastboot Device when Windows does decide to play fair. Any ideas as to what I can do next? I am on Windows 8.1
I'm guessing it's pointless keeping the balls spinning?
Make sure you're using a USB 2.0 port... for some reason, USB 3.0 has problems with adb/fastboot sometimes.
jake.Hall30 said:
Thanks for that, however, I am completely unable to use Recovery. I boot into it, and Windows flat out refuses to anything but complain:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Like I say, always had issues with adb on this machine. The device is recognized as an Android Fastboot Device when Windows does decide to play fair. Any ideas as to what I can do next? I am on Windows 8.1
I'm guessing it's pointless keeping the balls spinning?
Click to expand...
Click to collapse
Try other usb ports and usb cables or even other PC
hey guys, thank you for the response!
Telyx said:
Make sure you're using a USB 2.0 port... for some reason, USB 3.0 has problems with adb/fastboot sometimes.
Click to expand...
Click to collapse
USB 2.0 is doing the same. Recovery just flat out does not work, Windows always reports the device malfunctions
bitdomo said:
Try other usb ports and usb cables or even other PC
Click to expand...
Click to collapse
I have tried different ports and cables, I am wondering - is it worth dual booting Windows 7 and having a bash there?
jake.Hall30 said:
hey guys, thank you for the response!
USB 2.0 is doing the same. Recovery just flat out does not work, Windows always reports the device malfunctions
I have tried different ports and cables, I am wondering - is it worth dual booting Windows 7 and having a bash there?
Click to expand...
Click to collapse
I would try if I were you
bitdomo said:
I would try if I were you
Click to expand...
Click to collapse
Windows 7 was a bust, as was a different computer. Windows reports the exact same error when trying to boot into recovery, thus preventing me from firing off any adb commands. I can use all fastboot commands, as the bootloader works fine.
Next steps? I really can't afford a new phone right now (plus I want to wait to see what google come up with this year!)
jake.Hall30 said:
Windows 7 was a bust, as was a different computer. Windows reports the exact same error when trying to boot into recovery, thus preventing me from firing off any adb commands. I can use all fastboot commands, as the bootloader works fine.
Next steps? I really can't afford a new phone right now (plus I want to wait to see what google come up with this year!)
Click to expand...
Click to collapse
Turn off the driver signature enforcement and use the naked usb drivers 0.73 for the recovery device.
If you type naked usb drivers 0.73 in google it will be the first link to its post on xda where you find the download link
bitdomo said:
Turn off the driver signature enforcement and use the naked usb drivers 0.73 for the recovery device.
If you type naked usb drivers 0.73 in google it will be the first link to its post on xda where you find the download link
Click to expand...
Click to collapse
I've actually managed to get into recovery and successfully use adb. I followed the instructions within the post you added, and I am now in a constant reboot cycle wherein it keeps going back to recovery, saying /data can't be mounted then rebooting before I can see what's going on.
Progress!
EDIT: Dude, i absolutely love you! Thank you so so much, just having someone to talk to about it has helped!
For anyone who comes across this looking for an answer, what I have done is install TWRP (custom recovery), used the adb commands found here: http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 to fix the persistent partition, I then had a different boot loop, so I reinstalled the rom and voila! She's back!
Just a question: how did this happen, out of the blue, in the first place? is this something I did?
Thank you to the xda team, you guys are great
jake.Hall30 said:
I've actually managed to get into recovery and successfully use adb. I followed the instructions within the post you added, and I am now in a constant reboot cycle wherein it keeps going back to recovery, saying /data can't be mounted then rebooting before I can see what's going on.
Progress!
Click to expand...
Click to collapse
Restart your device to recovery again.
You can also try the fastboot boot <<whateverfilename>>.img instead of flastboot flash recovery <<whateverfilename>>.img
So for the last three months I've been using my rooted phone with the Pixel Experience ROM, and today I decided to switch back to the stock rom. I first tried to uninstall Magisk, but when I checked the app it was already uninstalled, which I think was a bit strange. Then I downloaded the global 14.0.1 MIUI and tried to flash it via recovery mode using adb, and it failed at the end of the flashing process. So I went to try to install it using fastboot, but after using the command fastboot devices, my phone was not listed. Then I went to the recovery mode again (I was using orange fox when doing so) and tried to reboot into fastboot mode. Doing so didn't change anything when using the command to list the devices, but MiFlash had it listed, so I tried using it. I selected the rom, and selected the "clean and lock" IIRC, it started to flash and said it finished without any errors, however my phone showed some errors that I can't remember now. I tried to reboot the phone, and it went back to recovery mode, so I tried to flash it again. In this time, I tried to stop the flashing process by removing the usb because I thought I should look for the errors first, and then I remembered that I shouldn't do it (I have a very bad short term memory), so I tried to put the usb back and flashing it again. This time the Miflash showed an error, and I realized I was using the flash command while in recovery mode, not fastboot (I accidentaly pressed "adb" in the recovery), so I tried to reboot my phone to change it and it turned off. There's no more battery charging screen, fastboot or recovery. After a lot of research, I found out that my phone is in ETL mode, it shows in the device manager on my pc and also shows in the miflash as "COM3" or "COM4".
Can someone please help me? I tried so many things so far, and I still don't want to send it to repair
If you selected clean and lock and it finished, that means you locked your bootloader, and with locked bootloader, you can't flash anything. And you also yanked usb out of your phone in the middle of flashing process? My bet, you screwed up partition or two, and now your phone is in EDL, my man... Just take it to a service centre, before it's completely destoryed
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
seiguisage said:
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
Click to expand...
Click to collapse
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
So probably It really is just a paperweight now
seiguisage said:
So probably It really is just a paperweight now
Click to expand...
Click to collapse
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
Click to expand...
Click to collapse
Since my gf gave me her old Mi 9 I think I'll make this a new hobby lol
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
What are you talking about. if he has access to EDL mode he can fix everything. Even if your UFS was completely wiped and had no partitions. EDL is a completely separate thing. However you can't reflash the software using EDL because only service centers have the authorisation to do that (some people have that access too, and you can reflash your phone if you pay them). Another way to do it is open the phone up, and short some pins to get access to unauthorised EDL.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it.
Click to expand...
Click to collapse
Yeah, mouth-to-usb always helps.