Related
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
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
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 this morning i got a notification on my phone about updating android version. In my half asleep state, i click sure, update, and rolled over to go back to sleep. i checked on it in a couple minutes and saw that it just booted into twrp and sat there because i have a custom recovery installed it can't do its normal processes. I reboot the phone, only instead of booting up like normal, it goes to the lg screen as usual and then straight into twrp. my first action was to reflash what i was using before, wich was H830_20A_DeOdexed by lordodin912. it flashed fine, but still didn't boot. then i thought maybe it got further into the update then i thought and i need a 20c rom, so i tried flashing 20c+kernel also by lordodin912. Still nothing. So sine then i have tried flashing a few things both 20a and 20c and none of them seem to be changing my situation as soon as it boots its just goes straight back into twrp.
Anyone have any ideas? this is just getting really frustrating, i would love to know what i messed up and how i can fix it.
edit* TheRealJDTram posted a solution, if anyone has the same problem
TheRealJDTram said:
And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.
Click to expand...
Click to collapse
konchar said:
So this morning i got a notification on my phone about updating android version. In my half asleep state, i click sure, update, and rolled over to go back to sleep. i checked on it in a couple minutes and saw that it just booted into twrp and sat there because i have a custom recovery installed it can't do its normal processes. I reboot the phone, only instead of booting up like normal, it goes to the lg screen as usual and then straight into twrp. my first action was to reflash what i was using before, wich was H830_20A_DeOdexed by lordodin912. it flashed fine, but still didn't boot. then i thought maybe it got further into the update then i thought and i need a 20c rom, so i tried flashing 20c+kernel also by lordodin912. Still nothing. So sine then i have tried flashing a few things both 20a and 20c and none of them seem to be changing my situation as soon as it boots its just goes straight back into twrp.
Anyone have any ideas? this is just getting really frustrating, i would love to know what i messed up and how i can fix it.
Click to expand...
Click to collapse
i am have the same situation ....quite worry about it.
kugcsq said:
i am have the same situation ....quite worry about it.
Click to expand...
Click to collapse
Same here as well. I've reverted back to using my PRIV until we can figure this out.
Wouldn't lgup help?
Sent from my LG-H830 using XDA-Developers Legacy app
And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.
TheRealJDTram said:
Same here as well. I've reverted back to using my PRIV until we can figure this out.
Click to expand...
Click to collapse
PRIV?
konchar said:
PRIV?
Click to expand...
Click to collapse
BlackBerry PRIV. My previous phone.
TheRealJDTram said:
And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.
Click to expand...
Click to collapse
thanks for your help, where do i run these? i used minimal_adb_fastboot before for adb commands, but it is telling me that dd is not recognized as a command. im using that im using the commands in the wrong place, can you elaborate on how to input it?
konchar said:
thanks for your help, where do i run these? i used minimal_adb_fastboot before for adb commands, but it is telling me that dd is not recognized as a command. im using that im using the commands in the wrong place, can you elaborate on how to input it?
Click to expand...
Click to collapse
With your phone booted into twrp, connect to computer, run ADB devices. Verify that your device is detected. If it is, run "ADB shell". You'll be brought to a Linux prompt. Mine had some odd characters at the prompt, looked corrupt, but it worked anyways. Paste the two commands that are listed into that prompt one at a time and pressing enter after each. It should execute them on your phone. If you can't get that to work and you feel you could type the commands out using the on screen keyboard, you can select advanced in TWRP and launch Terminal.
TheRealJDTram said:
With your phone booted into twrp, connect to computer, run ADB devices. Verify that your device is detected. If it is, run "ADB shell". You'll be brought to a Linux prompt. Mine had some odd characters at the prompt, looked corrupt, but it worked anyways. Paste the two commands that are listed into that prompt one at a time and pressing enter after each. It should execute them on your phone. If you can't get that to work and you feel you could type the commands out using the on screen keyboard, you can select advanced in TWRP and launch Terminal.
Click to expand...
Click to collapse
you are awesome. that did the trick. bootlooped a few times, and then went on to setting up android. thanks alot for your help.
konchar said:
you are awesome. that did the trick. bootlooped a few times, and then went on to setting up android. thanks alot for your help.
Click to expand...
Click to collapse
No problem. I had the issue as well and just started trying everything I could find on here.
TheRealJDTram said:
And I'm back! I wish I'd seen this before I wiped my phone, it may have wiped it anyways, not sure. But it fixed it for sure.
https://forum.xda-developers.com/showpost.php?p=70334660&postcount=17
Run the 2 commands in this post via ADB shell.
Click to expand...
Click to collapse
i wish i could see this early. i spent a whole night to fix it.
Finally i use this way:
Here is how you should do it:
1. Download LG bridge on your computer.
2. Switch off your Device, pull out your battery.
3. Attach your USB Cable from desktop to mobile
4. Hold volume up button, and put your battery while holding it. It should switch on itself if the USB is attached and you are holding volume up before putting in battery.
5. Once its on Bootloader, flash firmware recovery from LG Bridge.
Please help! I too was stuck in the TWRP, tried those two commands but now I'm getting red triangle and "Device Corrup, Cannot boot" error.
Tried to firmware repair with LG Bridge (entered Download Mode) but it cannot find any phone, even if it shows up on my PC as a serial LG COM port.
LG G5 H850 - Unlocked BL - was running Fullmics v1.5
Same happened to me, except I didn't get a prompt. I was playing chess and it said something about shutting down to update.
The commands worked.
If you have TWRP you can go Advanced > Terminal and just type it in there. !!!Make sure you double-triple check the spelling, typos will effff your shhht up!!!
Same exact thing happened to me, stuck looping back into TWRP. Used UPPERCUT to start LGUP (phone was being ID'd as an h1 instead of h830). Went from broken 20c to the 20a kdz file. Of course, lost everything on the internal storage and root and TWRP but just ran the easyrecowvery auto script and regained TWRP. Flashed 20c back on top and the NSS5.5 kernel package and am finally back where I was before the whole debacle. I'll wait and see if Autoprime preps a tested flashable version, maybe try again then.
BTW, I think the 20a deodex by lordodin912 is partial; it requires the complete 20a to be flashed first as a backbone. I don't think it's bootable by itself.
OnePlus 8 [WINDOWS PC] here;
Trying to convert to global using a flash-all technique where it boots into fastbootd in the middle of installation.
(https://forum.xda-developers.com/t/guide-convert-to-global-wip.4105885/)
It's supposed to detect the device and immediately resume the installation, but what happens is my phone is in the fastbootd menu with the 3 language selection whilst my terminal is stuck on "<waiting for any device...>"
If I reboot into recovery, nothing happens. If I reboot into normal fastboot, I get error messages such as "Command not found" and "Cannot flash to critical partitions!" Both of these result in me having to MSM.
Would this work any better if I ran it on a linux os? If not, what's the problem?
VRtualVortex said:
OnePlus 8 [WINDOWS PC] here;
Trying to convert to global using a flash-all technique where it boots into fastbootd in the middle of installation.
(https://forum.xda-developers.com/t/guide-convert-to-global-wip.4105885/)
It's supposed to detect the device and immediately resume the installation, but what happens is my phone is in the fastbootd menu with the 3 language selection whilst my terminal is stuck on "<waiting for any device...>"
If I reboot into recovery, nothing happens. If I reboot into normal fastboot, I get error messages such as "Command not found" and "Cannot flash to critical partitions!" Both of these result in me having to MSM.
Would this work any better if I ran it on a linux os? If not, what's the problem?
Click to expand...
Click to collapse
The problem is that you are trying to intervene in the process. Once you flash all you don't touch your phone until the welcome screen. Be patient and let it work it's magic. Should take about five minutes or so. Happy modding!
Nathan.7118391 said:
The problem is that you are trying to intervene in the process. Once you flash all you don't touch your phone until the welcome screen. Be patient and let it work it's magic. Should take about five minutes or so. Happy modding!
Click to expand...
Click to collapse
I've also tried without touching anything. The problem is that after it reboots into fastbootd, nothing happens, no matter how long I wait. It's stuck on "<waiting for any device...>"
VRtualVortex said:
I've also tried without touching anything. The problem is that after it reboots into fastbootd, nothing happens, no matter how long I wait. It's stuck on "<waiting for any device...>"
Click to expand...
Click to collapse
Hmmmm... Very strange. I would suggest do the pieces over again. MSM back to TMO then take the OTA to current-unlock bootloader finally upgrade to global. My phone did the same thing. I place in bootloader where you have the start on the top then it boots to the 3 languages screen where it finishes the install. Now it did take a minute or so to start again but it finishes for me. I've done it several times. In fact, I just did it again around mid December. How this helps.
Still nothing. I've waited 10 or so minutes.
Nathan.7118391 said:
Hmmmm... Very strange. I would suggest do the pieces over again. MSM back to TMO then take the OTA to current-unlock bootloader finally upgrade to global. My phone did the same thing. I place in bootloader where you have the start on the top then it boots to the 3 languages screen where it finishes the install. Now it did take a minute or so to start again but it finishes for me. I've done it several times. In fact, I just did it again around mid December. How this helps.
Click to expand...
Click to collapse
See above.
VRtualVortex said:
See above.
Click to expand...
Click to collapse
Ok last try here.
1. Use a different global file.
2. Use the orange usb cord that came with your phone.
3. Try a different usb plug in your computer or use another computer.
If that doesn't work then I suggest you check the troubleshooting info on the forum where you got the ROM.
You ever get it working past the fastbootd screen?
Is it as simple as just leaving it alone??
Same issue, and the only time it finished it went into crash dump mode.
Anyone found a solution to this? I have been struggling for hours.
I have done MSM 10.5.7 with flashall to 10.5.11, and MSM 10.5.22 with flashall to 10.5.12. It's always the same issue - reboot to fastboot and stuck there, the bat window just stuck at <waiting for any device>.
Please help
This must be due to drivers, try on a different PC.
lethalfriend said:
This must be due to drivers, try on a different PC.
Click to expand...
Click to collapse
Did you have to install other drivers than the one comes with the phone?
I am late to the table here, but the solution is to unplug the USB connection from your computer then plug it back in.
The script is waiting for the device to report itself back up, but there is some driver issue in Windoze that causes the device restart to not be detected. When you unplug/replug, the usb interface gets reset and everything happens.