Related
Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
TannyBhoy said:
Severe panic!!
I rooted my Desire which was running 2.2 Froyo on the O2 UK network using unrevoked and it worked fine without any issues. Custom recovery by ClockworkMod.
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Big mistake! My handset then rebooted and got to the O2 splash screen. It wont move from there. Pulled battery out and tried again. Same. I assume i havent bricked the device and it is just stuck in a boot loop?
Since then i have removed all my user data from the SD card and 'cleared storage'. Tried installing an miui rom and again 'installation aborted'.
Can anyone clarify why this is happening and point me in the right direction?
I am a noob and would appreciate any help on this.
Click to expand...
Click to collapse
Try to bring you phone to stock.
Download RUU .
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
OriginalThinking said:
Can the RUU be flashed in clockwork mod recovery or does it have to go through HTC Sync?
If it cannot be flashed in Clockwork Mod, I presume he has to
Connect phone via USB to PC,
boot into Fastboot as you mentioned
run HTC Sync
and then run the Ruu.exe file (does HTC Sync recognise this filetype and then do it's thing?)
And that's it? (Just that it seems too simple!)
Click to expand...
Click to collapse
You might need a goldcard. Try without one for now.
Right I'll let him know to give that a go. If it doesn't work I might pick your brains around the goldcard option.
Massive thanks so far for your advice!
Dude thanks for that. Im going to give that a bash and let you know how i get on!
Much appreciated!
Haven't tried this but it's worth giving it a shot. http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
Or this: http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
TannyBhoy said:
The next day I then decided i needed to turn S-off so found a guide and tried installing unrevoked forever from a zip on the root of the SD and i got 'installation aborted error 42'. Tried again the next day but before i got started i decided to give myself re-assurance that i wouldnt lose anything on the device so i entered recovery and chose restore.
Click to expand...
Click to collapse
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
So if you hit back-up and your phone stuck in the boot loop it is normal. This is a problem because of the root and the fact that making a nandroid back-up will mess something in the NAND. But restoring the back-up you just made should resolve all the problems. I had the same issue and by only restoring the back-up I've just made got me working back, and still had the ROOT.
I don't think you need to run a RUU just for this.
UsManyDead said:
Hello. I think you wanted to say you chose back-up, otherwise you couldn't have chosen the restore option since you don't have any restore points.
Click to expand...
Click to collapse
I should have made clearer sorry. After i rooted successfully i entered recovery and hit backup option and it told me it had created a backup successfully. I had been using the phone as normal for another day before deciding to s-off and at that point i thought to 'test' my backup to make sure it had done it so i chose restore thinking anything i have downloaded on the phone since the back up will disappear and was expecting the restore to bring my phone back to the settings i had the previous day but the restore failed and thats when it got stuck in the boot loop.
Mine did the same thing except, instead of trying to s-off it just decided at one point that it felt like it, literally, I wasnt even using it at the time it was just charging. I did downloaded the stock ruu, it was linked earlier. Put it in fastboot, run the ruu and boom, however i did it on my goldcard, so make one if it doesnt work without it. Good luck.
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
paul.c said:
Try to bring you phone to stock.
Turn your phone on in fastboot (hold back button and press power - when your phone is off).
You have to have HTC Sync installed.
Run the exe file.
After that repeat the rooting and s-off-ing procedure.
Click to expand...
Click to collapse
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
TannyBhoy said:
BACK IN BUSINESS!! Dude you are the man! The RUU didnt install as it was a different boot version so from the site you suggested i used the Froyo version and its now working! Many thanks.
P.s. What's the easiest way to s-off? Also whats the correct way to create a complete back up restore point and then actually restore to that point without getting to this stage again?
Click to expand...
Click to collapse
Easiest way to s-off is alpharev:
http://alpharev.nl
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
MatDrOiD said:
Same here. But everything is working fine.
So put phone in usb debug mode and "only charge" mode, start abd, connect phone via usb to pc and type
Code:
adb devices
. If your desire's serial number is shown, everything is fine.
Click to expand...
Click to collapse
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
To start adb issue: "adb start-server" command without the quotes
To stop it: "adb kill-server"
Here is the complete list: http://developer.android.com/guide/developing/tools/adb.html
TannyBhoy said:
***NEW ISSUE***
Since i have my phone back to it's original state and have lost root access. The idea is to root again via Unrevoked, which requires me to update the Android 1.0 driver (in device manager under other devices) to the Android Bootloader Interface. However, DM now does not say 'other devices - Android 1.0' and instead it says 'Android Devices - MY HTC'. So i decided to completely uninstall HTC Sync and all it's drivers and then rebooted PC, reinstalled SYNC and then uninstalled again but this time leaving the drivers in. Rebooted again and repeated the process but it still recognises the device as 'MY HTC' instead of 'Android 1.0'.
Could it be that this is fine, it's just the new way since i am using the updated version of HTC sync now? Or is this going to cause an issue? I am now playing it a lot safer to avoid anymore issues and quite happy to try something you may suggest...
Click to expand...
Click to collapse
Thanks for the suggestions surrounding ADB but i guess im too much of a noob for that part, it seems massively complicated, im sure it doesnt to you guys. Isnt there an easier way? Or considering my above quote, can i just assume that its all working fine and go ahead with the root or should it really need to have 'Android 1.0' in device manager?
Im pretty certain this all happened becuase the first time i rooted i had followed instructions and uninstalled HTC Sync (not the drivers) which had been on my system since i got the phone lat year. Since i had to reinstall to flash the RUU im certain its an updated version of HTC Sync thats causing this issue. But is it really an issue?
TannyBhoy said:
Hey man thanks for the advice. If yours is working fine, ive no reason not to try it!
As i am a noob, can you clarify "start abd" ??
Also, type code "adb devices", where to type?
Click to expand...
Click to collapse
Here you have a nice guide about adb:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
This should answer all your questions.
Hello all:
I have a Galaxy Nexus CDMA version, that I have successfully unlocked but cannot root. When I type fastboot devices I get my phone serial number. When I type adb devices I get nothing. I looked everywhere and have tried everything that I know to do. From what I read I don't even need adb devices if I use the superboot method. I tried that, but any time I try anything it tells me that it is "downloading..._" and never leaves that, or it says something like failed (too many links). Does any body know what I can do or what I am doing wrong?
Thanks in advance.
I kept on typing the same command fastboot boot boot.superboot.img over and over again... it finally took one of the times I typed it. I hope it helps somebody. Also, it just stayed at the google screen and never passed it. I let it go for about 15 minutes, then pulled the battery and rebooted. I had root upon reboot. Hope this helps somebody.
The super boot root method is for 4.01. On 4.02 phone gets stuck at google logo,but it does work. The devs need to fix that.
Also as for your adb command, ADB only works when your phone is on and booted up in android. Adb does NOT work in fastboot.
Sent from my Galaxy Nexus
Yes. That is what I heard. Thanks
Sent from my Galaxy Nexus using XDA App
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Zepius said:
i hate to ask this question... but...
when you scrolled to yes, did you press the power button to accept the selection?
Click to expand...
Click to collapse
I wish the solution were that easy (though if I were that stupid....yikes). I did hit the power button and cannot scroll to No. The device is really just stuck there. My cmd prompt is just hanging (...) too. I suppose it could be that the communication is only going one way (computer to phone) but somehow isn't going phone-to-computer. I've tried different drivers/cords/USB ports, but (right now) don't have another computer that I can play around on.
I may give it one last driver reinstall try, but it's looking like Odin is the way to go?
molgator24 said:
My soft brick Verizon gnex is giving me a bit of trouble. It was stock, locked, and all those other things that you all probably frown upon, but worked fine for me and I had not reason to change this. It got stuck in a boot loop and a hard reset and wipe didn't do anything. I found efrant's guide and got everything set up. fastboot devices results in a correct read of my device and I can run fastboot reboot-bootloader, which I did as a check to make sure computer to phone commands were working fine.
The problem is that when I run fastboot oem unlock, I get the unlock bootloader?, can scroll to "Yes" and then my phone gets stuck there...indefinitely. I've let it go for up to two hours and don't get anywhere. If I terminate with a battery pull/ unplug, I get a "too many links" error. Running wug's toolkit does the same thing. Rebooting into fastboot works, but the phone is still locked. If I select "No" on the unlock screen, I get the Google splash forever. Any suggestions?
Click to expand...
Click to collapse
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
herecomesmaggi said:
I aint a grave digger , I can see the post date but Have you found Solution yet ?? I am myself stuck there ?
Click to expand...
Click to collapse
No dice. Samsung offered to let me send it back, but I never got around to it. If you send yours in and/or figure it out, let me know and I may turn my current paperweight into something usable. Best of luck, and sorry I don't have more to offer!
OK thanks for clearing that out. I have tried everything, it seems that memory is corrupted and that's why bootloader can't format it and is stuck at unlocking... I will update if I found anything.
Avoid Spells!!! "Auto correct : ON"
When I boot up my tablet, I get nonstop error messages telling me things have stopped working. I tried getting help from someone else on a different site, and this is what they told me to say: I flashed the GROUPER lollipop ROM onto a FLO. Someone please help me!!! It's a totally clean tablet. no files on it except android.
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions: https://developers.google.com/android/nexus/images
Only thing I don't know is whether or not you'll have to repartition the internal flash.
I'm a dummy.
nhizzat said:
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions:
Only thing I don't know is whether or not you'll have to repartition the internal flash.
Click to expand...
Click to collapse
i don't understand how to do all that though I'm not good with command prompts... and nexus root tool kit has done me no good. Could you dumb down the instructions for me?
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
It is almost impossible to hard brick this device, even if you flash the wrong ROM on this device..
Download this utility and it will bring your Nexus back to life....
http://www.wugfresh.com/nrt/
Giving up
nhizzat said:
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
Click to expand...
Click to collapse
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
So that means you will sell it to me for $20?
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
I tried NRTK
madbat99 said:
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
Click to expand...
Click to collapse
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Make sure fastboots working first. Put the tablet in bootloader mode by shutting it off then holding power and volume down (or up I forget, you want the screen that says start at the top and has device info at the bottom left.)
Connect to computer then go into the platform-tools folder in the SDK folder, hold shift and right click over the window>open command prompt here.
Type fastboot devices and hit enter. Does it show a serial number or does it show nothing? (waiting for device or something like that) If nothing you should uninstall all drivers for the tablet in device manager and install the google usb driver from the sdk manager in the sdk you installed.
Once you see the serial number you're almost done. If your bootloader is locked type fastboot oem unlock
Now from the factory image copy the image-razor.zip, bootloader.img and flash-all.bat to the platform-tools folder.
Double click flash-all.bat
That's it.
I think that it will be beneficial for you to look into using virtual machines (VM's). It allows you to run different operating systems directly from your computer.
The second half to this equation is learning to use Linux (Ubuntu is my choice). Since Android is built from Linux, you don't need special drivers to recognize your devices.
Another option to run Ubuntu is to create a Virtual Hard Drive on your PC, and install Ubuntu onto it (YouTube it, and follow the directions carefully).
Lastly, you can always get a flash drive that is 8gb or greater (16gb or 32gb is recommended), and install Ubuntu onto it was well. It will move little slower than your PC, but your issues will be solved and manageable.
Why am I advocating for Ubuntu? Because it works. PM me if your are interested in learning more, but don't expect me to do all of the work. You need to educate yourself a bit to actually follow my instructions.
____________________________
Please remember to:
Check Q & A forums before asking!
Search forum for similar post before creating!
Hit "thanks" to everyone who may have helped you (it costs nothing)!
Read the OP!!!!
Boucherwayne78 said:
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Click to expand...
Click to collapse
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
^Yeah like my last post, those are perfectly fine instructions. If that don't work, stuck at "erasing user data" or something you're ****ed. Most likely.Try a different cord/usb 2.0/computer
Tried a few things. Got any other ideas?
Zaphodspeaks said:
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
Click to expand...
Click to collapse
Thank you for your reply. Do you have any suggestions though for my situation? My bootloader was unlocked. I did try locking it then unlocking it several times though. I've tried two seperate stock ROMs, different usb cables, different usb ports, and it now tells me that fastboot is not working. even a link is greatly appreciated. I think it is a driver problem. My tablet does boot into the OS though. I can use the ui for about 10 seconds, then a notification pops up mid-screen: "unfortunately, the process android.process.acore has stopped." Please, even a link is greatly appreciated. I've tried just about everything to get these drivers working, and to get this tablet working. I will continue to research as well. Wish me luck!
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
azsgolf said:
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
Click to expand...
Click to collapse
Got any ideas on Fastboot.exe stopping working when the flash process begins? it fails sending bootloader and then fastboot.exe fails. It says on the screen when i close the error message it's booting into bootloader, but the tablet never restarts. it stays on bootloader(where i had it in the first place.) It should turn off the screen and go back into bootloader. Please, any feedback is appreciated.
Have you tried selecting the option of hardbrick on the tool?
Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot
http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.
peltus said:
http://forum.xda-developers.com/nexus-5x/general/tutorial-flash-factory-images-unroot-t3231627
Follow this guide to the letter. You probably haven't installed your fastboot drivers correctly.
Note: if your phone was working correctly and started bootlooping on its own, you might be one of the unlucky users who has a defective motherboard. If it continues bootlooping after flashing stock image RMA the phone.
Click to expand...
Click to collapse
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Edit: I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?
Light_Ben said:
Hi, thanks a lot for your answer.
I'm stuck at oem unlock. The command prompt tells me
FAILED (remote: oem unlock is not allowed)
And on the internet, they say to unlock it in the dev options... but I can't access to my phone. Am I stuck?
Click to expand...
Click to collapse
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.
peltus said:
Pretty much, yes probably. As i said if it started bootlooping running completely stock you probably can't do much about it by flashing anyway.
It's a common fault on the n5x that started popping up recently.
Click to expand...
Click to collapse
I tried to skip this and I succeeded in these conclusions: abd works but then I get an error when I try to abd sideload: footer is wrong, aborted.
Then I tried fastboot but fastboot doesn't recognize my device. What to do?
OK I did a lot of research and I think I'm stuck.
fastboot recognized my device, I had to connect the phone on USB 2 instead of USB 3 port.
ADB shows an error on the phone, and fastboot says OEM is forbidden. And because OEM can be activated only from the phone... I'm doomed I suppose.
LG said my warranty expired. And anyway, I would have to pay for shipping and all.
:'(
Thanks for everything. If you find anything, answer here.
I think someone has already started a thread on unbricking bootloader locked phones. You might search for that.
But to me, it just sounds like the hardware has gone belly up just as many others. You might search for that problem also.
Thank you, I contacted the author of the topic!
Just in case for people, here is the topic: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 ([REQ] Need help. Unbrick phones with locked bootloader, oem unlock disabled)
Light_Ben said:
Hi everyone,
I'm really sorry, I really tried everything and I tried to look for an answer but it's very hard for me to understand.
My phone "died". I am not sure it's because of a firmware update or not, but now it's on an infinite bootloop.
I can access to recovery mode and download mode, I downloaded the factory image for Android 7 on the official website but then, I don't know how to continue. I open the file flash-all.bat, but in the command prompt it doesn't recognize it. I suppose I missed a step. Should I open the file from another software?
Please help...
Thanks a lot
Click to expand...
Click to collapse
just sent it to lg ...I iam paying 130 euros for new bootlader because mine stucked on bootloop but I can acces the recovery mode and I tried to flash stock but nothing if you never locked the bootloader try to sent it to lg and say to them you never unlock the bootloader ....sorry for my bad engilsh
I have a big problem and I did not find any solution at xda.
I flashed a custom rom and now after entering pin my phone bootloops. I am not able to enter recovery or download mode.
It feels like the phone is ignoring volume up and volume down buttons. I also tried to press the buttons directly on the motherboard. I cannot immagine that the buttons are broken. Has anybody an advice or me?