Related
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Have you tried to reinstall the motorola driver?
Yes, when I first "lost" RSD support and since the current "Failed to boot 2" message.
It has the flash interface when I plug it in, but the motorola software dosent see it, same with RSD. just like nothing is plugged in.
Why not put it into fastboot mode when it reboots and then flash a different file?
phobos512 said:
Why not put it into fastboot mode when it reboots and then flash a different file?
Click to expand...
Click to collapse
It won't boot into any other mode, upon putting the battery in, it shows the dual core logo for about 1.5-2 seconds that pops up the "Failed to boot 2" message and starting RSD mode.
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Phalanx7621 said:
Judging by your first post u mentioned that u never unlocked your boot loader, unless I'm reading this wrong. These ROMS weren't meant to be flashed with the Bootstrapped version of CWM (The one that requires u to be plugged in to AC power) so not sure if that sheds any light on the subject or not. Again, if I read your post wrong, I apologize.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ya, from what I can tell its Motorola locking me out for using an modified rom. But I think that I should be able to return to a stock firmware using RSD lite or the Motorola software restore from thier site, but neither see my phone connected. This leads me to belive that somewhere in the process the RSD protocol got messed up. Now I really don't know much, just enough to be dangerous. So if theres anyone that can tell me if I'm even looking the right direction.
And if I am right is there anything I could possibly do?
gjRabbit said:
Alright here goes
So my question is, what options do i have? I can't access any recovery options (Fastboot, android recovery, etc) and my RSD lite wont connect.
Short Story
Every time i try to boot my Atrix (after trying to update CherryPi), I get the Failed to boot 2, Starting RSD mode. Unfortunately, when I plug my phone into a computer RSD doesn't see it. It's like its not even phased.
Long Story
Okay, so I got my atrix not too long ago. Got my phone rooted at proceeded to use gingerblur. Then shortly there after, I attempted to upgrade to the Gingerbread OTA update, which got me stuck in a boot loop. (Now I'm a little confused, I don't think that I have unlocked my phone at all. I don't ever recall "unlocked" being on the boot screen at all). From this point I don't think RSD was working. I spent about a week trying to get it to work. Then I was able to fastboot flash the stock img files for gingerbread to my phone. So now I had a working gingerbread atrix. I sat stock for a little while, figgured out how to root via fastboot (again, no rsd support at this point). After I was rooted I installed CherryPi 0.3 via CWM. It worked great, a couple of days later I went to do the CherryPi 0.X > 0.5 and it flashed with CWM "successfully" got to the AT&T logo on bootup and then crashed and has been giving me the failed to boot 2.
I hope i've given you guys enough info. If any of you super hackers live in San Diego, I'd be more then willing to bring my phone over for you to figure out. So I just really need to know what my options are. If I take it back to AT&T will they likely give me a new one? (I'm good at playing dumb). I traded my phone originally so I don't know what kind of warranty is in place. Can I contact Motorola and get a new handset? Just looking for suggestions.
Thanks guys
Click to expand...
Click to collapse
Hey man, I have the same problem with you.. have you some progress for that..
I find some infor from forum that this kind of hard brick can be solved by using the developping cable to reflash the sbk file, this method is pending at the SBK file is unavailable which is not released out by MOtorola.. I find a one of my friend who is working in MOTO (Tianjing, CHINA) to see my device, I hope he can help me to unbrick my phone.. when i have good news, I'll update it.
I have the MetroPCS lgms769, I tried unlocking the bootloader but I guess I messed up some how. My screen had the touch screen problem, so I tried flashing again but now I'm stuck on security error. No matter what I do, I cannot get fastboot drivers to install for my phone. I've tried several times. It just sits there at waiting for omap44xx device. I've done the steps right to the T, My computer makes the sound as something connected then disconnected, then connected again and then once again disconnected. I've watched under device manager but I see nothing coming up, even when I do view all devices. I've booted into S/W upgrade mode but my phone is not detected. I can't boot to anything, it just goes to security error, shuts off, and boots showing my battery charging. I've installed all drivers through the LG website that goes with my phone. When my phone was working, I connected the usb and switched to every mode for it to install drivers. I'm on Windows 8 64 bit. Could someone please help me?
kseunder84 said:
I have the MetroPCS lgms769, I tried unlocking the bootloader but I guess I messed up some how. My screen had the touch screen problem, so I tried flashing again but now I'm stuck on security error. No matter what I do, I cannot get fastboot drivers to install for my phone. I've tried several times. It just sits there at waiting for omap44xx device. I've done the steps right to the T, My computer makes the sound as something connected then disconnected, then connected again and then once again disconnected. I've watched under device manager but I see nothing coming up, even when I do view all devices. I've booted into S/W upgrade mode but my phone is not detected. I can't boot to anything, it just goes to security error, shuts off, and boots showing my battery charging. I've installed all drivers through the LG website that goes with my phone. When my phone was working, I connected the usb and switched to every mode for it to install drivers. I'm on Windows 8 64 bit. Could someone please help me?
Click to expand...
Click to collapse
Funny you should mention this. I too have the same problem!! I spent all night to no avail! I managed to get clockwork to install, flash the backwards touch problem fix, but then when I attempted to install a Pacman 4.3 rom the phone rebooted to the Security Error Lg logo!! I can't flash any KDZ now because at 15% it loses a connection! I tried the Fastboot method and ADB just would not detect my phone! Pulling the battery out and having the phone connected to usb makes the device manager go nuts! Omap device pops in and out and wont stop! Thankfully I have the Tmobile premium handset protection package, so Ill get a replacement p769bk but OMG people don't try to unlock the boot loader on this device! Its not worth the risk and complexity/trouble!! Stick to root access and be happy! Wait and pray someone smart enough can figure out how to unlock the boot loader easily and with minimal risk! Before I messed with my phone I was on the OTA update v20F. I flashed to the V20B 760 KDZ and used the hex edited bin file that goes with it. Just don't do it! Its not worth the backwards menu/logo/touch headaches! Be warned!
I wound up taking it back to metropcs and I'm getting a new one in 3-5 days, they didn't charge me since the guy said it was a software problem and I was still within the 30 days
kseunder84 said:
I wound up taking it back to metropcs and I'm getting a new one in 3-5 days, they didn't charge me since the guy said it was a software problem and I was still within the 30 days
Click to expand...
Click to collapse
Good deal. Like I said before to anyone who reads this post:
Head my warning or you'll probably end up like the both of us!.
I really like this phone but damn! Why does LG have to lock the boot loader..? I miss having Cyanogen Mod. I mean my old P999 G2x wasn't this hard to get CWM/Root on it!
Somebody save the day! Find the key to a simple boot loader unlock! (V20F) This phone deserves it!
Hey you posted in the wrong place, anyways fastboot probably didn't work because you are on Windows 8.
If you try again, use this http://forum.xda-developers.com/showpost.php?p=45102887&postcount=1
This is the official program to restore from security error & other problems.
Sent from my LG-P769 using xda app-developers app
Thanks for trying to help but I tried to use that app and it still failed to detect my phone. I don't think I'll try it again. We need a new one click wonder app before I'll attempt this again. Also I don't think I like having a backwards LG logo stuck on my phone, ( I did not know that was going to stay there) yet alone some strange image mirror bug with the lock screen. It corrected itself if you hit the power button and wake it but if you reboot the phone it comes back.
Sent from my Nexus 7 using xda app-developers app
SovereignKnight said:
Thanks for trying to help but I tried to use that app and it still failed to detect my phone. I don't think I'll try it again. We need a new one click wonder app before I'll attempt this again. Also I don't think I like having a backwards LG logo stuck on my phone, ( I did not know that was going to stay there) yet alone some strange image mirror bug with the lock screen. It corrected itself if you hit the power button and wake it but if you reboot the phone it comes back.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You can fix that with the proper u-boot.
Sent from my LG-P769 using XDA Premium 4 mobile app
Device:
New Verizon VS985 with 12c rom. Phone was in working order prior to brick.
How I got into brick:
1. Rooted using ADB push the UPDATE-SuperSU-v2.46.zip (it was successful as I gained root after reboot)
2. Tried to install twrp using this post, which I failed to realize it was meant for 23b and not 12c. This is where I suspected I messed up.
http://forum.xda-developers.com/showpost.php?p=59309598&postcount=190
I did not put the img file on my phone, but leave it on my computer in the ADB folder. I then did the first two command lines:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
and noticed the computer says Device Was Out of Space. I thought the first two commands did not go through, and I stopped without doing the rest of the commands. I think it rebooted ok after this before I did step 3.
3. I then unlocked bands 3 & 7 using this method:
http://forum.xda-developers.com/verizon-lg-g3/general/unlocked-lte-bands-vs985-t2909150
It goes like what the instruction says. However after the reboot, my phone went into brick.
Symptoms:
1. Screen does not turn on. No LED light. No LG Startup logo. No red Verizon logo. Nothing at all on screen when pressing the power button.
2. When I hold the volume up while plugging in USB cable (to computer), it vibrates once like it goes to download mode or battery is being charged. The screen is off so I cannot tell which mode it is in.
3. While in this state, the computer does detect the 4 USB devices. However, it only would load the drivers for the first two, and the last two would keep searching but never loaded.
4. I do have the important LGE Mobile in Device Manager under Ports, and I was able to change it to COM41 for the official LGFlashTool for the .TOT and .dll Unroot/Unbrick method.
5. On the LGFlashTool, the box 1 became yellow and said READY. However, when I unplugged the USB cable and plugged it back, after the "Waiting for Connection.", when it tried to do the actual flash, it would fail. See the attached picture.
6. I then uninstalled LGFlashTool and tried the KDZ Method (with 10b KDZ rom), the LGFlashTool2014 will recognize the phone and show the correct COM, but when the actual flashing happen, it will fail. One time it said external server is not available. The other times, it fail for other reasons. (I forgot to capture the screen last night, but will do tonight.) Basically it won't flash.
Any suggestions?
acefr said:
Device:
New Verizon VS985 with 12c rom. Phone was in working order prior to brick.
How I got into brick:
1. Rooted using ADB push the UPDATE-SuperSU-v2.46.zip (it was successful as I gained root after reboot)
2. Tried to install twrp using this post, which I failed to realize it was meant for 23b and not 12c. This is where I suspected I messed up.
http://forum.xda-developers.com/showpost.php?p=59309598&postcount=190
I did not put the img file on my phone, but leave it on my computer in the ADB folder. I then did the first two command lines:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
and noticed the computer says Device Was Out of Space. I thought the first two commands did not go through, and I stopped without doing the rest of the commands. I think it rebooted ok after this before I did step 3.
3. I then unlocked bands 3 & 7 using this method:
http://forum.xda-developers.com/verizon-lg-g3/general/unlocked-lte-bands-vs985-t2909150
It goes like what the instruction says. However after the reboot, my phone went into brick.
Symptoms:
1. Screen does not turn on. No LED light. No LG Startup logo. No red Verizon logo. Nothing at all on screen when pressing the power button.
2. When I hold the volume up while plugging in USB cable (to computer), it vibrates once like it goes to download mode or battery is being charged. The screen is off so I cannot tell which mode it is in.
3. While in this state, the computer does detect the 4 USB devices. However, it only would load the drivers for the first two, and the last two would keep searching but never loaded.
4. I do have the important LGE Mobile in Device Manager under Ports, and I was able to change it to COM41 for the official LGFlashTool for the .TOT and .dll Unroot/Unbrick method.
5. On the LGFlashTool, the box 1 became yellow and said READY. However, when I unplugged the USB cable and plugged it back, after the "Waiting for Connection.", when it tried to do the actual flash, it would fail. See the attached picture.
6. I then uninstalled LGFlashTool and tried the KDZ Method (with 10b KDZ rom), the LGFlashTool2014 will recognize the phone and show the correct COM, but when the actual flashing happen, it will fail. One time it said external server is not available. The other times, it fail for other reasons. (I forgot to capture the screen last night, but will do tonight.) Basically it won't flash.
Any suggestions?
Click to expand...
Click to collapse
not sure if i can be of assistance, i was more dumbfounded by some of what you wrote, i had to reply.
just to be clear,
you were not previously rooted,
pushed the su zip that can only be flashed from custom recovery,
how did you install the zip with no twrp and no root?
then rebooted and had root?
anyways,
then dd the aboot,
the out of space is normal, the first code zeroes out the partition, the second line flashes the new code.
moving on,
you basically flashed the same aboot you already had on being on 12b,
the twrp you flashed is fine, it works on all versions, so thats not the issue.
--not trying to sound mean with my replies above, just some of what you said is theoretically impossible.
so, up to this point, assuming you got root somehow, nothing you did is wrong or would cause the problem you now have. (aside from the rooting)
i need to go look into this link you posted about the bands.
just out of curiosity, why were you using my post (now deleted) to try and put twrp on? its for L not kk, and its actually good you stopped when you did or you would have had other serious issues after flashing the L boot onto a kk stock rom.
anyways, again, not trying to sound mean, this is mostly unbelievable..
---------- Post added at 07:10 PM ---------- Previous post was at 06:47 PM ----------
so, i looked at the other thread and still dont see any issues. until you answer my questions, i cant speculate as to the cause.
only suggestion i could make,
remove the battery, sim card, and sdcard.
hold the vol down and power, and put the battery back in, and see if anything happens.
bweN diorD said:
not sure if i can be of assistance, i was more dumbfounded by some of what you wrote, i had to reply.
just to be clear,
you were not previously rooted,
pushed the su zip that can only be flashed from custom recovery,
how did you install the zip with no twrp and no root?
then rebooted and had root?
anyways,
then dd the aboot,
the out of space is normal, the first code zeroes out the partition, the second line flashes the new code.
moving on,
you basically flashed the same aboot you already had on being on 12b,
the twrp you flashed is fine, it works on all versions, so thats not the issue.
--not trying to sound mean with my replies above, just some of what you said is theoretically impossible.
so, up to this point, assuming you got root somehow, nothing you did is wrong or would cause the problem you now have. (aside from the rooting)
i need to go look into this link you posted about the bands.
just out of curiosity, why were you using my post (now deleted) to try and put twrp on? its for L not kk, and its actually good you stopped when you did or you would have had other serious issues after flashing the L boot onto a kk stock rom.
anyways, again, not trying to sound mean, this is mostly unbelievable..
Click to expand...
Click to collapse
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
I will try the volume down+power tonight and report back. Again thanks for your input. The rooting method is a suspect too, as it says G2 in the posting. I was directed there from a G3 posting.
acefr said:
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
Click to expand...
Click to collapse
ok, that makes way more sense. you were indeed rooted and were pushing the su zip to flash in twrp i assume.
so anyways,
ohhh wait a minute, i just re read what you wrote. did you flash the first 2 img's from my post? 4 lines of code?
bweN diorD said:
ok, that makes way more sense. you were indeed rooted and were pushing the su zip to flash in twrp i assume.
so anyways,
ohhh wait a minute, i just re read what you wrote. did you flash the first 2 img's from my post? 4 lines of code?
Click to expand...
Click to collapse
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
acefr said:
Not a problem. I understand the more detail I give, the higher chance there is a solution. I appreciate your effort in trying to solve it.
1. the phone was originally in factory new state. No custom recovery, no root, stock 12c rom.
2. I used the following method to root, and it appeared ok as the phone was able to reboot and granted SU when I did step 2. It was late night and my mind was not clear when I did step 2. I wonder why I didn't see the Lollipop in the title.
http://forum.xda-developers.com/android/help/lg-tribute-development-t2953342/page38#376
I will try the volume down+power tonight and report back. Again thanks for your input. The rooting method is a suspect too, as it says G2 in the posting. I was directed there from a G3 posting.
Click to expand...
Click to collapse
install both of these drivers then try the tot flash tool again.
https://www.mediafire.com/?q1blsp6151rcmf9
https://www.mediafire.com/?x22q33votbv086d
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
acefr said:
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
Click to expand...
Click to collapse
no, the rooting is fine, i used that the other day, i thought for a second i misunderstood and you dd the boot too. but no, thats good.
---------- Post added at 07:36 PM ---------- Previous post was at 07:32 PM ----------
acefr said:
Yes, I gained root before trying to install twrp. I stopped after the first 2 lines of code, and didn't execute the last 2. I am sure I didn't load the img as I didn't even put it on the phone. The rooting file says G2 instead of G3. Would that be the issue?
Click to expand...
Click to collapse
btw, did you try this i suggested earlier?
remove the battery, sim card, and sdcard.
hold the vol down and power, and put the battery back in, and see if anything happens
Click to expand...
Click to collapse
bweN diorD said:
install both of these drivers then try the tot flash tool again.
---------- Post added at 07:32 PM ---------- Previous post was at 07:30 PM ----------
no, the rooting is fine, i used that the other day, i thought for a second i misunderstood and you dd the boot too. but no, thats good.
Click to expand...
Click to collapse
Thanks. Will give it a try tonight. The phone is at home. I will vol down and power first. If not working, then TOT flash.
These installation programs are for the USB drivers for the phone, right?
acefr said:
Thanks. Will give it a try tonight. The phone is at home. I will vol down and power first. If not working, then TOT flash.
These installation programs are for the USB drivers for the phone, right?
Click to expand...
Click to collapse
yes, one is the latest lg driver, and the other is an alternate lg driver. i always install both to avoid connection issues.
Actually
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
---------- Post added at 11:56 PM ---------- Previous post was at 11:47 PM ----------
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
***Edit**** I just tried the suggestion of removing everything and vol down and power. shorter vibration than usual but still nothing.
soateufel said:
I understand exactly where he's coming from because i was rooted on stock lollipop and also got the message about insufficient storage and what i did was i went to the google play store look for the kitkat sd fix it don't matter just fine and it said the patch was applied so i thought everything was fine i was also on stock recovery because how to flash the custom recovery just confused the hell outta me. So what i ended up doing was trying to backup titanium and i use the imei backup because i just had the issue where i got the boot signature verify screen and i called verizon and got a replacement sent out to me. Here is the problem now, after i did all that, i had gotten worried because my battery was dying but here's where i get confused my phone will not turn on a tray the KDZ method and it tells me the phone does not have enough battery life the only time i will see any image on my phone is when the battery is out and i plug the phone into my computer so what i'm thinking is the battery is just shot... which is highly possible and unfortunately verizon does not have any to send me so i ordered one of amazon and hopefully it'll be here on the 16th and if that's the case that means we have all those days to figure out if this is a brick which i pray to god it better not because i didn't have my phone on last week because of the boot signature verify and then i have the refurbished one all of 3 days before this crap happened. I do feel a vibrate when i plug the phone in with the battery and my phone is recognized somewhat by my computer it only loads the com port and modem. But like i said every time i try to use the android recovery tool that came with the verizon software it tells me my battery is too low i also should mention that i tried the tot method and it failed as well. One other thing i'm going to mention is that i also tried reading the information with the kdz method and it said imei null and pid null just don't worry about it i was like um ya thats not good.
Click to expand...
Click to collapse
when you zero out a partition using the dd method through terminal or adb, it is absolutely normal to say out of space or whatever.
any sd fix you applied was unnecessary and possibly caused the problem you have.
yes, the imie being 000000 is not good, but i dont believe it will keep you from using stock recovery tools, and is very fixable.
okay. so im gonna try the tot method. I installed both drivers and plugged in my phone and the phone driver just installed so ill let you know what happens.
bweN diorD said:
when you zero out a partition using the dd method through terminal or adb, it is absolutely normal to say out of space or whatever.
any sd fix you applied was unnecessary and possibly caused the problem you have.
yes, the imie being 000000 is not good, but i dont believe it will keep you from using stock recovery tools, and is very fixable.
Click to expand...
Click to collapse
ya no dice... trying to kdz right now with the most recent drivers.
bweN diorD said:
yes, one is the latest lg driver, and the other is an alternate lg driver. i always install both to avoid connection issues.
Click to expand...
Click to collapse
"vol down and power" did nothing. The phone screen is still black and it vibrated for a short period. I then proceed to use another computer with USB2.0 port. Installed your two sets of drivers. Plugged in the the phone, computer found three USB device, loaded first and third drivers, the middle one driver failed to load. It is a Phone Modem. Then use the TOT flash, same thing, failed right before the flash started. However, this time I noticed there is an error message saying "Model Information Check Failed". See the attached pictures.
Maybe when I unlocked band 3 and 7, the Verizon Hidden Menu somehow changed permission of the NV value?
acefr said:
"vol down and power" did nothing. The phone screen is still black and it vibrated for a short period. I then proceed to use another computer with USB2.0 port. Installed your two sets of drivers. Plugged in the the phone, computer found three USB device, loaded first and third drivers, the middle one driver failed to load. It is a Phone Modem. Then use the TOT flash, same thing, failed right before the flash started. However, this time I noticed there is an error message saying "Model Information Check Failed". See the attached pictures.
Maybe when I unlocked band 3 and 7, the Verizon Hidden Menu somehow changed permission of the NV value?
Click to expand...
Click to collapse
Tbh, I don't know what else to tell you to try, sorry.
I Have the same problem except
When I turn on the phone normally I get the lg logo then the notification light blinks I can seem to get the drivers working like recovery mode and download but the download mode is not working right it says dowload mode then goes to a black screen I get it showing it in device manager in Windows 8.1 but its not lg driver it starts with a Q can't think of it right now it under ports I can't seem to flash anything when it boots I get the Security boot error and then after the lg logo nothing happens except the notification lights up and blinks I was upgrading from 10B to 12B then my phone rebooted and can't boot into the system any help please I need this phone working
Same issue here!! Just vibrates, black screen, no boot
asdecker said:
Same issue here!! Just vibrates, black screen, no boot
Click to expand...
Click to collapse
Did you get into the brick by enabling band 3 and 7? Or what did you do prior to bricking it? Maybe we can figure out what is causing this together.
mine happened when i used lucky patcher to odex my system apps to make more space
Mine was when I ran the scripts to fix download mode. I'm stuck for sure. Can't get it to do anything
asdecker said:
Mine was when I ran the scripts to fix download mode. I'm stuck for sure. Can't get it to do anything
Click to expand...
Click to collapse
When you and soateufel tried the TOT flash, which step did you encounter issue? Did you get the same Model Information Check Failed warning like in my picture at post #13?
My fiancees Sprint LG G3 LS 990 out of nowhere yesterday got a green screen of death, no rooting, completely stock, had the phone since dec 2014 with no issues til now. Now it is stuck in a boot loop. I've tried going into recovery mode, it says recovery mode loading then turns off right back to boot loop. I tried going into download mode but just shows the LG startup logo then turns off boot loop. I have everything to flash it to stock if I can get it into download mode but unfortunately, it won't go into download mode. I've read all over these forums and tried everything i could including holding vol down while boot looping til it shuts off then attempting to go into download mode, but when i do that the phone becomes unresponsive and wont turn on in recovery, download, or into the boot loop, and i have to take the battery out to get it to do anything. I saw about shorting the phone but thats far above my pay grade so if anyone has any advice I would greatly appreciate it. If nothing else if anyone has any suggestions as to what we can do at the sprint store, we're willing to buy a new phone but she still is making payments on this phone until dec and it would really suck to have to pay to cancel that and then buy a new phone when it was completely stock. thanks!
edit: yesterday right after it green screened and went into boot loop we were able to go into recovery, restore to factory settings, and the phone worked for a few hours then green screened again.
edit 2: i think later today i will attempt to short the pins and hopefully succeed with that method.
Green screen damn i never heard of that one tell us what ever worked incase we run into that same problem mean while i will do some research on my part to try to get u together.
---------- Post added at 01:00 AM ---------- Previous post was at 12:39 AM ----------
Go to this link https://youtu.be/My_fPd704Es this guy was having the exact same issue but with a different LG i have used the 2014 flash tool a couple weeks ago to fix a problem with my lg g2 and can confirm that it works because the lg support tool from the lg site just kept telling me that i already had the latest software installed on my phone with no supoort but when i used the 2014 flash tool to flash my kdz it worked perfectly. And if u look under that video theres a thousand other videos of others fixing it using the same method. Hope it works for u.
---------- Post added at 01:05 AM ---------- Previous post was at 01:00 AM ----------
By the way MAKE SURE U GET THE CORRECT KDZ FOR YOUR PHONE MODEL AND CARRIER I CAN'T STRESS THAT ENOUGH SO DONT DOWNLOAD THE ONE ON THE VIDEO UNLESS U FIND A VIDEO WITH YOUR EXACT CARRIER AND MODEL. For example i have a lg g3 ls990 zvc so i would ONLY download the LG G3 LS990 ZVC because that ZVC ranges from like ZV4 ZV8 ZVA ZVB and using one of those will cause a boot loop im warning you now.
So, I'm im at a loss here... I haven't done anything to my phone today other than turn on the Webserver at Boot function in Adaway, which I'm guessing is the culprit here... but based on my inability to fix that, which I've fixed Xposed issues before, I'm not confident.
so I'm bootlooping on LG screen primarily, phone was working fine next minute it was off and wouldn't turn on. Took battery out, etc... thought it was the batteries at first, charged both fully, continued troubleshooting. Rebooted a few times it'd boot, show my unlocked Bootloader screen, continue as if going to TMO screen, back to LG screen.
So I tried to boot into TWRP via Factory Reset method. I follow the prompts and then the screen locks, randomly the bootloader unlocked dialogue reappears.
Computer previously recognized device via ADB, now it does not, even with updated drives and ADB/Fastboot. Had the device install itself a few times when plugged in, did not help.
I was able to boot into Fastboot one time, while in there I thought maybe it's an issue with TWRP, so I reflashed TWRP 3.0.1 through fastboot and ran fastboot with the twrp image command... screen locked and nothing happened.
I'm not sure what to do at this point without Fastboot being accessible through computer or regularly through manual method. TWRP is pretty much,... man I don't even know where TWRP is at this point it hasn't made a single appearance in this troubleshooting session.
Any ideas I'm missing?
LGv10
Lollipop 5.1.1, Rooted, Xposed v85 TWRP 3.0.1
If you can get fastboot working again try to just boot twrp rather than flashing it
fastboot boot nameofrecovery.img
Other than that try using lgUP to flash rooted MM if you can get pc to recognize phone
Sent from my LG-H901 using XDA-Developers mobile app
demkantor said:
If you can get fastboot working again try to just boot twrp rather than flashing it
fastboot boot nameofrecovery.img
Other than that try using lgUP to flash rooted MM if you can get pc to recognize phone
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
hey bud - thank you for responding. I actually by the grace of god, just got my phone to boot into fastboot mode again. It wouldn't even turn on since I wrote this post so I've just been browsing for alternatives. Literally on the LgUp page as we speak thinking that's going to have to be the route I take even if I lose all my data... at least I won't have a brick. I ended up using a method I've been trying all day, it's weird how it's hit or miss on when it works... held volume down and plugged in USB, not sure why it's working randomly even tried other computers, ports, cables... anyway thanks !
demkantor said:
If you can get fastboot working again try to just boot twrp rather than flashing it
fastboot boot nameofrecovery.img
Other than that try using lgUP to flash rooted MM if you can get pc to recognize phone
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
I Knew i was going to leave something out, if I flash rooted MM, couldn't that make things worse if I'm on TWRP for LP. I'll read the instructions on the up page, but at first glance I didn't see them talking about specific recoveries like on the eliminator thread..
You can follow toungkick's method and flash the .tot and kdz to get rooted mm, this will include the proper recovery
Choice is yours on the method but this way is smooth and rooted MM is great on this phone
But yeah, data will be wiped,
If you manage to make it into recovery you can try and dirty flash current ROM on top (no wipe) and see if that fixes things first so you don't loose any data
Sent from my LG-H901 using XDA-Developers mobile app
demkantor said:
You can follow toungkick's method and flash the .tot and kdz to get rooted mm, this will include the proper recovery
Choice is yours on the method but this way is smooth and rooted MM is great on this phone
But yeah, data will be wiped,
If you manage to make it into recovery you can try and dirty flash current ROM on top (no wipe) and see if that fixes things first so you don't loose any data
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm honestly losing my mind over this one, I've gotten into Fastboot several times but never long enough to flash much of anything. LGUP won't recognize device and the method to get it to recognize the device by removing the battery isn't work. So I tried manually flashing images in Fastboot and also tried Nexus Root Toolkit as a last ditch effort.
The further I've gotten is flashing TWRP again, and reflashing a boot image...
Believe it or not I just booted into TWRP, it wasn't easy at all but the phone finally went through following the factory data reset method... I was in there for maybe 7 seconds and then screen went black and phone powered off.
I'm getting to the point where, since it fully booted once, booted into fastboot, booted into TWRP, I'm not convinced this isn't hardware related? But I'm not an expert there.
The only way, literally that I can get it into Fastboot is to take the battery out entirely, hit power a few times to drain it, hold volume down insert cable... the screen comes on with the battery indicator but it flashes a red question mark and I simultaneously throw the battery in while holding down volume... and fastboot boots right up ... I only have a few minutes each time and even though things are successfully clashing (I also erased the cache) nothings working.
I was in TWRP long enought o know that it appears all my data is still in there, was hoping to get to Xposed to delete... maybe I'll look into the xposed uninstall zip and see if that helps but really.... wondering if my batteries got screwed up somehow with these new cables I'm using. never read anything quite like this one
Closing loop here. Phone bricked for sure. Got replacment on warranty. Back up and running rooted MM tho with jun method.
klark1kent said:
Closing loop here. Phone bricked for sure. Got replacment on warranty. Back up and running rooted MM tho with jun method.
Click to expand...
Click to collapse
What happened to the original phone?
Phone died on me, and now I'm stuck on the LG logo. Not actually fully booting.
dinggus said:
What happened to the original phone?
Phone died on me, and now I'm stuck on the LG logo. Not actually fully booting.
Click to expand...
Click to collapse
I was never able to get it to boot. Even tried flashing through lgup and it would never make it through.. I took it to tmobile and got it replaced through warranty. Cost 5 bucks. You can manually boot into fastboot or download mode and flash images if your phone will stay on long enough
Im afraid my phone did the same thing. Ive done all of what you mentioned. I guess i have no other choice but to go to T-Mobile and exchange it. You say it only costed you 5 bucks? How is that..? I thought after you void its warranty ... U'd pretty much be stuck wid ****.???
lokz831 said:
Im afraid my phone did the same thing. Ive done all of what you mentioned. I guess i have no other choice but to go to T-Mobile and exchange it. You say it only costed you 5 bucks? How is that..? I thought after you void its warranty ... U'd pretty much be stuck wid ****.???
Click to expand...
Click to collapse
I found this page (https://guidebelajar.blogspot.com/2015/12/guide-to-flash-bricked-bootloop-lg-v10.html?m=1) and am currently in the process of 'refurbishing' via LGUP.
I was able to get into download mode using the following method
"Now turn your LG V10 H900 (AT&T), H901 (T-MOBILE), VS990 (VERIZON) phone off, then click continuously on the up volume and connect your phone to your PC, "
lokz831 said:
Im afraid my phone did the same thing. Ive done all of what you mentioned. I guess i have no other choice but to go to T-Mobile and exchange it. You say it only costed you 5 bucks? How is that..? I thought after you void its warranty ... U'd pretty much be stuck wid ****.???
Click to expand...
Click to collapse
Man I'm sorry I must have notifications off... It was covered though the manufacturer warranty so they only charged me 5
Sent from my LG-H901 using XDA Labs
Explains this... Glad I wasn't crazy but damn LG
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/
Sent from my LG-H901 using XDA Labs