i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
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?
So I was having so many issues with my rooted phone crashing on jasmineRom 7.0 I thought maybe an OTA update had made it through and started downloading. No matter what I was doing the screen would turn blue and then restart. Sometimes it would crash blue again during reboot, and sometimes it would crash and then show the green demigod crash screen. So I researched flashing the .tot files to go back to stock. KDZ I didn't care for because it still showed the phone as modified software, and I wanted full stock so I could use the extended warranty with Verizon if need be. I eventually got the .tot method to work and everything was hunky dory, and showing stock. I upgraded all the way to marshmallow and decided I love every bit of it, but I couldn't figure out how to get my contacts and stuff off titanium backup without root. So I figured, "well roots not the problem if an OTA tried to download it just means I missed a setting or something". So I rooted again. No issues, I reinstalled JasmineRom 9.1 this time. Eventually it started crashing again, although this time I followed absolutely every guide I could find on disabling OTA. So I thought, "Great it's Jasmine" and I really wanted Marshmallow anyway so I followed xdabbeb's guide for getting the 35b bootstack on my phone, worked great no issues, and then I installed xdabbeb's firmware, combined with Edor's debloating zips. Everything was working great! I had no issues, I backed up just my apps, and some data, and reinstalled others and everything was great and working fine, and the phone was still official, no OTA's getting through. That was almost a full week ago. Yesterday I woke up and the phone wouldn't turn on. I took the battery out and put it back in and the phone came on, but then crashed with the blue screen again. So I thought great I guess I'll put it back to stock and use the warranty. By this time though I was having trouble getting it to load past the LG screen. I finally got it into TWRP and was able to wipe everything (except SD card) and then I stuck it in download mode and went to install the .tot files. Weeeeelllll, long story short, it crashed during download mode install with the LG Flash Tool. So now the phone gets stuck in download mode everytime I pull the battery and power it on. And crashes again every time I go to install anything. KDZ doesn't work, the flash tool says it can't communicate with the phone, because it crashes. And LG Flash Tool for the .tot files seems to crash everything it loads the modem, or consistently crashes on LAF:bin_user_mode. So I have no idea. At the moment it just looks like my phone is all funky defective, and Verizon may take it back and give me a new one so I'm going to try that. HOWEVER! If anyone has any ideas on what the issue is or what else can be done, I still want to hear it. Feel free to post
Also I've tried updated drivers for the computer, I've tried rolling back drivers, I've tried different KDZ files, I've tried the LGUP8974.dll fix where you flash that in flash tools and then flash the vs985 dll, which is what I had to do to get it back to stock the first time. I've tried everything I could find online except anything to do with fast boot and shorting the pins. Which I haven't tried because I can still access download mode it just seems to be stuck in download mode. Those methods from what I understand are for hard bricking, and for people who's phones don't turn on at all. Although if Verizon won't help I may try one of the laf recovery methods.
Thanks!