Related
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.
RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
So I tried using the wugfresh toolkit last nigh to root since from what I've read all the nexus devices use the same method to unlock the bootloader and such. This was likely a mistake. After figuring out I had to change the device to PtP I managed to get to the unlock bootloader screen on the device, at which point it became unresponsive. I turned it off completely, and at that point it wouldn't boot at all, it would just sit on the nexus logo forever. I also couldn't fastboot, holding down the power, volume up and volume down buttons seemed to do nothing. So I let it run down last night in hopes of starting on a fresh charge. Now the device doesn't seem to want to charge at all. I plugged it into both my computer and wall charger through the usual usb cable, and the screen isn't showing any indication of charging. All I saw was the notification light blinking in short bursts after initially plugging it in, and now not even that is happening.
Ideas?
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you wipe system, what exactly are you expecting to reboot into???
je
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
destructobob said:
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
Click to expand...
Click to collapse
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
I like toolkits, seriously, but they hardly ever work. I usually have to drop to a shell prompt and run the commands manually anyway.
Sent from Nexus 7 XHD using XDA Premium HD
destructobob said:
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
Click to expand...
Click to collapse
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
hadisious said:
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
Click to expand...
Click to collapse
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
phonic said:
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
Click to expand...
Click to collapse
So I'm able to get into the bootloader, but its not responding to the command line entries. My computer brings a popup anytime the nexus tries to do a regular boot, where it just sits at the logo. The popup explains that the device is unrecognized. I've uninstalled any devices that resemble the nexus in device manager, and have tried repeatedly to update the driver manually by pointing it to the usb driver folder within the sdk. Doing that simply says windows is unable to locate the correct driver. So I think my device is where it needs to be, I just can't connect to it from the command line at the moment.
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
alicarbovader said:
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
Click to expand...
Click to collapse
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Honestly I had completely forgot that the initial unlocking does the factory reset. I got caught up in booting up the device and installing a few apps to try it out, to the point that I completely blanked on the reset haha.
I tried a bunch of different roms and verions on my gnexus and old N7, jumping between CM and PA mostly, and I got used to just having a backup ready and not worrying about a data wipe. I've mostly stuck with PA because the pie controls are fantastic on both devices and I've come to get used to the added screen space. I'm perfectly fine with the stock experience outside of pie controls, but I do love customizing my device and the custom roms allow for so much freedom in that regard.
destructobob said:
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
Click to expand...
Click to collapse
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
shengovind said:
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
Click to expand...
Click to collapse
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
destructobob said:
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
Click to expand...
Click to collapse
:good::good::good:
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Yes but you should've waited for a suitable toolkit.
alicarbovader said:
Yes but you should've waited for a suitable toolkit.
Click to expand...
Click to collapse
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
phonic said:
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
Click to expand...
Click to collapse
ok, not a toolkit.. I give you that, but was the stock experience too intimidating...?
personally, i'd nuked htc sense when i got thoroughly bored with its great buttery ui. i like the aosp experience, rooted or not.
and i didn't know that we don:t need toolkits fpr nexus devices, cuz i've never happened to own one.
Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.
Kooky_Lukey said:
Hey guys,
So, the other day i was just playing a game and then all of a sudden i get a ton of lines up and down the screen and i could see parts of the screen but not the whole screen and it became really slow to respond. I tried to reboot but it is just black with some grey lines.
I am running CM 10.1 and did everything in hashcode's forum to get there.
When i plug the kindle into my computer i can still see and access all of the internal storage and everything and i can still reach the TWRP bootloader screen but i just cant see anything.
I attached a picture of what it looks like in TWRP bootloader. I did not drop the Kindle or anything like that this all literally happened while i was holding it and playing a game.
Any help is greatly appreciated and I have no idea what else to do.
Click to expand...
Click to collapse
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.
Thepooch said:
Do a full wipe data,cache,dalvik and system reflash Rom cleanly then see if upon boot the problem persists. Otherwise I would say it`s some kind of hardware issue.
Click to expand...
Click to collapse
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks
Kooky_Lukey said:
Am i able to do this through a command prompt? I looked for some but i couldn't find any commands that were directly for a Kindle to do this on, only ones that were for like the nexus or different tablets. Thanks
Click to expand...
Click to collapse
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?
Thepooch said:
So your saying this is the boot screen not TWRP you need to access recovery if not wipe in fastboot
Code:
fastboot -i 0x1949 erase cache
Code:
fastboot -i 0x1949 erase userdata
at the userdata part it could hang just let it sit for ten minutes or so side note this will wipe your sdcard so all backups and rom files will be gone. So best you transfer all you wish to keep to your pc. This is not a promise your issue will be gone but it would be my approach if you cannot get into recovery. First try to access recovery by holding volume up button on first splash at boot continue to hold till it enters recovery. Now if that is the bootloader and not CM10 boot screen something more is amiss but I highly doubt you have magiclly broken your bootloader playing a game.
Edit: Also I would gather that you have completely powered the device off then on again?
Click to expand...
Click to collapse
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.
Kooky_Lukey said:
Sorry for the confusion, yes i have powered off and on again and yes i can get into recovery. The picture that i took was when i was in recovery. You can kind of make out the TWRP logo in the top left corner and the blue lines on top of "install" and things like that. However, the screen looks like this so i cant make out the buttons that i need to press which is why i was asking if i could do all of these things in a command prompt because recovery isnt doing anything for me right now.
If this clears things up and there are different lines of code i should run then i will wait but if its the same then i will run them when you respond. Thanks.
Click to expand...
Click to collapse
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.
Thepooch said:
when you let the device try to boot are all the animations normal or does this distortion persist through all? if it persists this has got to be some kind of major hardware malfunction. If your boot animations look normal but you only see this take place when in recovery then I suggest getting into fastboot and reflashing TWRP. You can still try the wipes in fastboot that I recommended at this point I do not believe there is any harm in doing so. If none of what I suggested helps you might have one toasted Kindle so maybe instruction will take place for you to prepare to return it to Amazon we will cross that road when we come to it.
Click to expand...
Click to collapse
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.
Kooky_Lukey said:
No this distortion persists throughout everything, no matter where i go or what i do its like that.
I just also tried the two lines and i still get the same thing so if you could point me in the direction of getting everything worked out to send back to amazon that would be greatly appreciated thank you.
Click to expand...
Click to collapse
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.
Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thepooch said:
Sure no problem when I get home I will write something up for you or we can restore it to return together either way. If this graphical issue persists across all partitions of the device it's completely logical that it is a serious hardware malfunction.
Click to expand...
Click to collapse
Thank you so much you do not know how much I appreciate it. If anything youre writing has anything to do with java i would love to help but if not then i wouldnt be of much help
stunts513 said:
Not exactly sure how it hooks up, but could it possibly be a loose cable to the LCD screen?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I wouldn`t even bother opening it let Amazon do their job. Case openers, case damage it would be pretty hard to pin the issue on them if you were to open the device.
Actually because of the present condition of the device I would go this route http://forum.xda-developers.com/showthread.php?t=2096888 . Just pick the latest version of the 8.9 to restore to you should also be prompted with an option to wipe cache and data please do so. All the partitions will be restored to stock and the device will be ready for return. Say nothing about modifying the device just leave those details out. If you want help catch me online and we will set something up. Some of this does depend on the state of your warranty. Be courteous with customer service and brief as to what caused the issue you simply just found it that way Good luck.
Good point, wasn't really thinking about "what if the problem wasn't that".
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Psicovirus said:
Hello friends, im writing because today I screwed my nexus 5x downgrading from oreo to nougat because the phone was getting too hot and I was worried that it would have the famous bootlop.
I don't know what happened, but when I tried to enter the recovery after flashing it, following instructions, the recovery now have a flashing "no command" logo and force entering the bootloader mode Its impossible because the vol down key is damaged. Now everytime I restart the phone it goes straight to recovery mode.
Can I do something? this is the so called bootloop? there's another way to enter bootloader mode?
Thanks for answering
Click to expand...
Click to collapse
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hold Volume and Power Up while in the stock recovery aka "no command" screen. You should fully enter stock recovery now. You F you can boot up, then you can issue this command "adb reboot bootloader" while in Android and connected to a computer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Psicovirus said:
Thank you for answering friend.
When I do the combo vol up and power, it just reboots to the bugging recovery.
If i try to start up in any way, it will go straight to recovery.
I just managed to enter a "download mode" but i don't know if that coul be useful.
Click to expand...
Click to collapse
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Nicktheprofessor said:
Connect it to your computer and try to do adb reboot bootloader from the "no command" screen.
Click to expand...
Click to collapse
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Psicovirus said:
Hey friend.
In recovery mode, the pc doesn´t recognize the phone at all, so I cannot reboot to bootloader.
Thanks for answering.
Click to expand...
Click to collapse
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Nicktheprofessor said:
Something has gone seriously wrong here, you can't even use the LGUP tool to recover from whatever happened there I suspect. I think your best bet would be to open it up (unless it's under warranty) and short the vol down button to get into bootloader mode.
Click to expand...
Click to collapse
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Psicovirus said:
I just used LGUP tool and phone is in Google logo for too long, shutted it off so it can cool down (LGUP relocks bootloader?)
Thanks for the suggestion!!
Edit: Now the phone is stuck at google logo, should i wait for it to boot or assume it is damaged?
Click to expand...
Click to collapse
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Nicktheprofessor said:
Is it recognized at all by the computer? I really know nothing about Windows and how this works on Windows so perhaps someone else who does can help you.
If you have access to Linux, is it present in /dev/block?
Click to expand...
Click to collapse
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Psicovirus said:
No, it can't be recognized by my pc, but i can still get to download mode, i think the problem it that the tot file that is available, is from an earlier version from android an it doesn't include several partitions, so the bootloader (now locked) doesn't let it start up, i think the solution is try to get to recovery or bootloader and sideload an recent OTA file, but i don't know if i can because i can't get to recovery.
There's any way in which i can get to install a more recent image via download mode?
Any suggestion is welcome, thanks to you all.
Click to expand...
Click to collapse
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Nicktheprofessor said:
Well you can't sideload anything without getting into recovery and it doesn't sound to me that you used a correct file if it has fewer partitions.
There are probably .tot files floating around if you search this N5X forum, or you might be able to find one here: http://www.lgbbs.com.cn/forum-109-1.html
Best of luck.
Click to expand...
Click to collapse
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Psicovirus said:
Sorry for the inconvenience, but i've installed the only tot file that there is around. I have been reading and here in the forum, people says that "This TOT file only contains GPT partition table, boot, recovery, system, modem", and we need to flash a full factory image so the rest of the partitions are in the same page. do you think that with LGUP's option "Upgrade FOTA" i can achieve this?
Many thanks in advance.
Click to expand...
Click to collapse
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Nicktheprofessor said:
What that tells you is that you now have a GPT that is correct and you can now fastboot flash a correct image BUT it has replaced your recovery which should allow you to enter recovery properly.
From there you can sideload a full OTA image that will restore the other partitions.
Oh an don't worry, if I stop responding I'm trying to find something and if I cannot help you further I'll just tell you that.
Click to expand...
Click to collapse
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Edit2: Seems like i screwed up stalling stock recovery on top of twrp, sahme on me. How can i short the volume down button?
Psicovirus said:
I didn't quite catch that, what I should do now? my phone still doesn't want to enter recovery mode, and bootloader is out of the picture for now because the broken button.
Should i try to flash the OTA via the "FOTA UPGRADE" option from LGUP?.
Im grateful that you are taking the time to answering me.
Edit: Tried to install the OTA via LGUP and gives error, so is a no.
Click to expand...
Click to collapse
Reboot to recovery, use adb to sideload the OTA.
Reply to edit2: open it up, find the leads on the circuit board that go up to the vol down circuit breaker, use two needles and insert them into the solder where the breaker connects and while crossing the needles so they connect push power.
OR, fix the broken breaker, most of the time it's just a broken off brass dome that needs realigning, you'll need to fixate it which is just a needle's head worth of superglue on one side and a soldering on the other side (reflowing by heating the dome with a soldering iron usually works).
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Nicktheprofessor said:
Reboot to recovery, use adb to sideload the OTA.
Your problem was that your recovery was shot, it should now be restored since that partition along with the GPT (the partition table) has been rewritten when you flashed the TOT file.
If you still cannot enter recovery or use adb reboot bootloader from whatever stage you can get into you'll have to open it up and short out the leads to vol down to get it into bootloader but even then you're probably SOL since it sounds like your emmc isn't working correctly. That is a hardware error though so depending on where you live that might buy you another two years of warranty.
Click to expand...
Click to collapse
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Psicovirus said:
Friend, what is SOL? how do you know it is a emmc error if it was me that damaged the software? I cannot enter recovery, so ill try the short, any recommendation tha you can give me about that?
Click to expand...
Click to collapse
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Nicktheprofessor said:
SOL=Sh*t Out of Luck.
You flashed a tot file that rewrite the partition table (GPT) as well as installed a recovery partition and the stock recovery (whatever version it was should work fine). That it didn't tells me that something is awry with your emmc.
See my edit of my previous post, shorting it out is a piece of cake, fixing the breaker is a bit more work but if you have a soldering iron and super glue as well as a steady hand and good eye sight you'll be able to fix it.
Don't go nuts with the superglue though, as I said, a needles head worth is plenty. You'll know what I'm talking about regarding the brass dome (sometimes it's copper and sometimes it's zink, zink doesn't work with the superglue so you'll have to use special glue for that) when you see it, it's like a little dome resting on top of the leads, pushing it down shorts them out.
I'd do the needle thing first though, just to see if it works at all, no need fixing the button if the emmc is dead.
Click to expand...
Click to collapse
Im trying to do that, i already have the phone open, sewing needles will do?
Psicovirus said:
Im trying to do that, i already have the phone open, sewing needles will do?
Click to expand...
Click to collapse
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Nicktheprofessor said:
Anything with a sharp point made of metal will do, as long as you can penetrate the solder with the tip and get a lead it will work.
All you need is to short it out for a few seconds while you use the power button to enter bootloader.
My guess is that you won't be able to enter the bootloader mode either though. The bootloader is read from a partition on the emmc.
I really hope you do prove me wrong on this though, that would be awesome.
Click to expand...
Click to collapse
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Psicovirus said:
I tried that and didn't work, but maybe im doing something wrong, the sadness hit me hard and I rather try again when im more clear headed.
I still fail to see how the emmc is failing, should have entered recovery mode more easily? Flashing software somehow made it more prone to fail?
Many thanks, friend, you've been really helpful.
Click to expand...
Click to collapse
You can use a q tip and some acetone to clear eventual lacquer from the solder points but the thing is, it's probably the emmc that is shot.
Your emmc obviously doesn't accept what the recovery the LGUP wrote to it. If it did, you'd be flashing the OTA right now. Why? I have no idea, I'd need to take the phone to the lab to examine what caused the degradation and even then I probably couldn't tell you much more about the actual cause.
And don't worry about it, your case is interesting and not easy to solve by simply doing a search, you weren't an arse about anything either and that is unusual and welcome.