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.
Related
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
Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!
Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app
I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!
I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob
I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?
If they have parts on hand if not either a swap out or a sendoff
Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.
Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)
Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.
Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!
Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone
After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything
sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
sumasage said:
My mom's pixel 2 xl all of a sudden wont boot. It said cant find valid operation system. The device will not start. She said it might have updated overnight or something like that. I tried to download the factory image from google to restore the OS but it wont flash without bootloader being unlock. It odd that the phone was working and now it doesnt have an OS.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Can you get to stock recovery for a factory reset?
It doesn't even let me get to recover. Picking recovery from the bootloader screen just make the phone restart like it try to go to recovery but then it come back to the same screen saying it can't find valid operating system.
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
trim81 said:
Same happend to me on my first unit when I relocated the bootloader.
Unit resetted and then can no longer find an operating system..
Only option was to call Google and RMA it. I've seen it happen to others on the web as well
Click to expand...
Click to collapse
What did you say Google? Did you tell them it happened while re-locking boot loader? I am on same boat....I tried to relock bootloader and getting Can't find valid operating system
I rma the unit as well.
sumasage said:
I rma the unit as well.
Click to expand...
Click to collapse
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
ram4ufriends said:
Did they accept the RMA? Was the issue after an update or did you try to flash the update using adb or fastboot?
Click to expand...
Click to collapse
Tell them exactly that. It no longer boots
As soon as I said there was no valid os the rep proceeded to rma. Seem like it a know issue so they didn't bother to transfer me to tech support.
Not sure if you want to try any of these solutions before you RMA, but here's another thread on the same "No OS ....." with several options, might be worth a try?
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
megernic said:
I ran into the same issue, however I found a solution, perhaps universal perhaps not.
When I enter fastboot mode, my phone shows (until I release the power/vol buttons) the "Start" option that is part of the boot mode. After releasing, I get the "no rom detected." So I used the script at the top of https://forum.xda-developers.com/pi...l-deuces-bootloop-recovery-flashing-t3704761. I used the script by running it WHILE pressing the Power/Vol keys.
This worked for me.
Note: I let go of power/vol after starting script.
Click to expand...
Click to collapse
Did you check or uncheck OEM unlocking in Developer Options before doing this?
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Larzzzz82 said:
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Click to expand...
Click to collapse
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
simplepinoi177 said:
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
Click to expand...
Click to collapse
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
helpless_user said:
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
Click to expand...
Click to collapse
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
In fastboot you can boot to a recovery.img; fastboot boot twrp.img
Download TWRP .img here.
(that recovery menu allows adb mode also).
Here you can(re)flash zip/image etc.
Format /data to ensure it is not encrypted.
For example, flash the extracted images of the OTA images from Google.
simplepinoi177 said:
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
Click to expand...
Click to collapse
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Not able to figure out the exact fix
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
@OP, I am still stuck with the exact same issue. How did you exactly fix it? After running the solution given, I'm back at the infinite logo screen again.
Edit: It worked, thank you so much! This is a life saver.
simplepinoi177 said:
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Click to expand...
Click to collapse
Hi i have the same issue with different device lenovo tab m10 tbx605L and i cant boot the recovery.img it throws me this error.Can u give me any ideas?
helpless_user said:
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Click to expand...
Click to collapse
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
EDIT: Quoted the wrong poster. My reply is an answer to the quoted poster instead of the poster who revived a dead thread with a question for a totally different device.
Strephon Alkhalikoi said:
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
Click to expand...
Click to collapse
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
safaan0313 said:
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
Click to expand...
Click to collapse
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Strephon Alkhalikoi said:
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Click to expand...
Click to collapse
Hmm well thanks for your indirect F**k off
safaan0313 said:
Hmm well thanks for your indirect F**k off
Click to expand...
Click to collapse
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Strephon Alkhalikoi said:
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Click to expand...
Click to collapse
Right I knew that.I am sorry.I was so damn angry at my own mistake.I AM S O R R Y.But off the record I just repaired my tab
LE2125 Installed but when TWRP loads none of the Dialog works, its locked up.
weeems said:
LE2125 Installed but when TWRP loads none of the Dialog works, its locked up.
Click to expand...
Click to collapse
How did you install twrp and is it 3.6.0
MrSteelX said:
How did you install twrp and is it 3.6.0
Click to expand...
Click to collapse
I used fastboot flash and it is 3.6.0 yes
weeems said:
I used fastboot flash and it is 3.6.0 yes
Click to expand...
Click to collapse
Wrong installation method
weeems said:
I used fastboot flash and it is 3.6.0 yes
Click to expand...
Click to collapse
You have to use fastboot boot twrp. Now you must install stock kernel and start over.
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
HellsBells7 said:
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
Click to expand...
Click to collapse
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
MrSteelX said:
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
Click to expand...
Click to collapse
Can you point me to a guide to doing so? I'm afraid I don't know, first time I've ever screwed up this bad. Not even sure where to get files or anything of that nature, Or how to get them onto the phone via fastboot (seems to be the only way to interact)
EDIT: Will this help me?
HellsBells7 said:
This seems similar to something that has happened to me. I purchased this phone with the intent of flashing Lineage-MircoG on it. TWRP-3.6.0_11-0-lemonadep.img has been installed, and was working on the phone. I was in the process of doing factory wipes so that I could flash LOS and for some reason, the touch screen stopped working. I can interact with the power button but can't swipe to unlock. I can't seem to find any button combination that will reboot the device either. I'm not sure what I did wrong, but I could really use a break down of how to fix it. Thank you in advance.
EDIT: Was able to get to fastboot by holding down power, volume up, and volume down at same time. Still unable to interact with touch, however. Computer seems to recognize a device is plugged in but Internal Storage is completely empty, and thus far my attempts to drag the LineageOS image to the device have been unsuccessful.
Click to expand...
Click to collapse
Install stock rom and boot it. Touch will be back then temp boot twrp and install LOS. After installing then you do format data.
HellsBells7 said:
Can you point me to a guide to doing so? I'm afraid I don't know, first time I've ever screwed up this bad. Not even sure where to get files or anything of that nature, Or how to get them onto the phone via fastboot (seems to be the only way to interact)
EDIT: Will this help me?
Click to expand...
Click to collapse
Yes
OK, thanks for being patient with me. I have the program downloaded to my computer but I don't seem to be able to get my phone into the prescribed EDL mode. Fastboot, yes, but not EDL. The fastboot command from my terminal window isn't working, and obviously I'm too far gone for adb at this point.
Is there a combination of hardware keys that will force EDL? Or perhaps an easier way that I'm missing altogether?
Again, thank you for helping me. I don't remember having this much trouble with the 6T.
From fastboot. Temp boot twrp and have it boot to edl. If no touch, can you plug in a mouse. If all fails, with phone off hold vol up and down together and plug in USB cable
I got it back on to stock! Thanks for everyone's help.