Related
Hey all,
I have a CWM backup of my current rom and have backups of apps and data but am stuck at a bootloop.
As I have read countless articles, it seems my error is because I have a locked bootloader(not actually sure). Though, I only tried to flash
clockcycle's wiped v20d cwm backup file. It failed part way saying it couldn't write to /system.
Since then, I haven't been able to fully enter CWM. just see the red triangle with the droid guy on his back.
I have read Cmahendra's unbricking guide but it doesn't work as I have installed JB and even the tips to unplug, wait 10s and reopen the program to flash again it still won't work. Still stops at 15% saying error connecting to the phone.
There is a similar thread which had this exact problem which said to
use the online method to recover your phone since I had already installed JB. I edited the hosts file to remove the fake offline server and opened up the b2CAppsetup.exe, clicked on customer support,
entered my model LGP769BK and my S/N and it began to start the process and 'analyze' then crashed and said "updating is not possible any longer due to a fatal error while the LG mobile phone software Update"
I've tried to search this out myself and not waste any space but I'm at loss here. If anyone has any help, it would be much appreciated
as I don't have a phone while this is not working.
I've tried all the ways to to hard reset, master reset and still I get the droid guy on his back. I can get to S/w mode like all the other posts say to do but none of those fixes seem to work for me. Am I missing something?
Do I have any options here? I have kind of read that I should just unlock the bootloader but I don't think that applies in my case as I can't turn on my phone fully.
edit: for the online method(LG support tool), it basically cancels when it goes to the 'downloading' phase --> this is what I've seen as most of the answers but doesn't work
Upon further reading,
many seemed to need to replace their u-boot and x-loader
I did so and installed fastboot using Lelus' script here:
http://forum.xda-developers.com/showpost.php?p=41768774&postcount=1
I used option 6 which allowed me to flash the u-boot and x-loader from p760(works with my 769 and others as it says in the options) for JB
I'm not sure if I needed this as I don't have an unlocked bootloader.
I'm not sure of commands in fastboot but I ran
fastboot devices and it showed something
I also ran: fastboot flash recovery recovery.img
and I put one of my cwm backups in the "yours" folder
After I activate fastboot, it brings me to the C:\fastboot\yours folder
I assume this is for me to put my intended files in but I'm unsure if I should use my cwm backup or something else?
After it flashed the recovery img, I sent a fastboot reboot command
but it still went back to the droid lying down with a red triangle.
As some of you may see, I'm not too great with this but I feel like I'm close. Does anybody have an idea of what I should be doing?
should I flash an update.zip?
I don't know many commands but hopefully this gets me going in the right direction.
PLEASE HELP ME!!!!
I guess your cmw restore formatted your system but couldnt load the new system
the recovery you run with a locked bootloader uses a technique called 2nd init which i think is somewhere stored in the system partition. so when the recovery formatted the system, it lost itself too.
I've had a similar problem. the way out would be booting into the SW upgrade mode--switch off the device, remove the battery, remove the usb cable. press the volume up button and connect the phone to the computer. wait for a couple of seconds and then insert the battery.
you should be in the SW upgrade mode
now use the B2C client. if it gives an option to upgrade, use that otherwise, go to the customer support menu and press recovery phone
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
shockah486 said:
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
Click to expand...
Click to collapse
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Tablechair said:
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
Click to expand...
Click to collapse
Thanks.I'll try this. if I have the ICS bootloader, does that mean I'll have to flash the V10G kdz? or can i do the v20d kdz
dhruvbatra205 said:
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Click to expand...
Click to collapse
I have the updated kdz fw upd .zip from the unbrick and root thread as well as downloaded a new, official B2C client but they all still hang at the download part during phone recovery.
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
shockah486 said:
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
Click to expand...
Click to collapse
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
Not yet. having problems flashing a kdz again. I've tried the 2 different software modes, as well as setting emerg and diag but still getting stuck at 15% again.
Do i have to replace my uboot and xloader with the ICS ones every time I want to use the offline flash method?
edit: yup, after replacing with ICS loaders again i'm able to flash using software upgrade. will update on whether I can restore cwm
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Help.
shockah486 said:
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Click to expand...
Click to collapse
Although I might be late, I have the same problem and the same phone and I really need help. I have a soft bricked phone lg optimus l9 and I had the same problems that you had exactly... Which is weird exept I don't have Clock Work Mod or anything ... If you get this I would really appreciate some help. Thanks
yup me too
I finally got software upgrade to work with my lg p769 that was security error cuz i still haven't unlocked the bootloader, if i knew what a good job lg and T-Mobile did in locking it i would have waited and got a g3 that my buddy rooted in like 5 min and unlocked the boot....
What worked for me is this LG FLASH TOOL 2014 THREAD ON XDA
http://forum.xda-developers.com/showthread.php?t=2797190
flashed both the 20H and 20D successfully i uninstalled everything lg in the control panel first though.
Hope this works for you cuz i was struggling on and off for a month to get this far lol
the 2014 tool ultimately worked for me too, once I fixed a couple things. I had rooted and forgotten to unlock, so it was at Security Error, and it would also disconnect at 15% .. in the 2014 tool, I had to install all the updates even though I'm in windows 7 or it would keep doing it. All good now.
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Liger878 said:
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Click to expand...
Click to collapse
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
shockah486 said:
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
Click to expand...
Click to collapse
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Hopefully you find the thread that states the exact steps bc that is off the top of my head and over a year ago by memory . GL bud
Liger878 said:
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Click to expand...
Click to collapse
Hey, I have been trying it with the fastboot but it keeps timing out and not allowing me to finish. One thing I should let you know is that, ever since I had put the device in fastboot, I am not able to get back the S/W upgrade mode. Dont know if that will help in seeing what my problem is or if you want me to explain everything from the beginning again, I am more than happy to.
Have you followed the steps that I linked to in the first 3 posts of this thread?
Follow the steps to flash the ICS bootloaders in fastboot and then you can do the fastboot trick for getting the software to recognize your device.
Right now your phone has the JB boot loader on it and is thus not recognized by the software.
recap:
step 1: flash the ICS bootloaders in fastboot (look at the linked thread in post 2)
step 2: use the software in emerg or diag mode but sitll follow the same steps as the tutorial. I think my earlier posts should explain precisely.
if you dont flash the ICS bootloaders, it won't be recognized by the KDZ installer
did the dumb unlock boot loader for the lg optimus l9 769 and now my phones all screwed up i did everything just like it said
now ive been seaching everywhere and cant find what i need i want to go back to the way it was when i first got it and the lg kdz flash thing doesnt work and it keeps telling me my battery is low when its not i need everything the bin file for tmobile usa and the kdz i cant get links to anything. my phone touch screen is all screwed up and i cant install cwm it wont let me i need help bad.. idk what to do any more. also got no 4g
andrew09 said:
did the dumb unlock boot loader for the lg optimus l9 769 and now my phones all screwed up i did everything just like it said
now ive been seaching everywhere and cant find what i need i want to go back to the way it was when i first got it and the lg kdz flash thing doesnt work and it keeps telling me my battery is low when its not i need everything the bin file for tmobile usa and the kdz i cant get links to anything. my phone touch screen is all screwed up and i cant install cwm it wont let me i need help bad.. idk what to do any more. also got no 4g
Click to expand...
Click to collapse
You have to let your battery drain some to get the offline flash working. The best thing to do is get back into the bootloader (fastboot) and install the omap4430 driver.
Issue the same command you used to unlock
adb reboot oem-unlock
Look for lelus fastboot thread.
Flash the non touch cwm for p769. You can find everything you need in carloswii5 thread on unlocking bootloader. Look at my post in that thread. And look for lelus touch screen fix. While you are at it, flash a custom ROM.
My desesperation may have been my reaper.
I tried flashing a kdz file vb20 to my l9. I was trying to unlock bootloader, based on the main threads at the General forum (unlocking bootloader for noobs). I only worked with the written instructions, and the phone didn't show the recovery installer that was on SD (forgot to install, I guess?). I freaked out and thought that a boot to recovery could fix. WRONG. It made the recovery to the v20b file. Everything is mirrored,
PS, please me nice on me. I know I didn't prep as well as I thought I did, so just want advice
EDIT:
Never mind. Dodged a bullet. After a while, the screen came up when it was unlocked. Took a while, but I was able to use the same method to flash v20f, am now updating to v20h. WAAAYYYY too close a call!!!
Another edit: think I'm gonna have to give it up. I flashed the most updated version, but the keyboard and screen behave too erratically.
So I messed up pretty badly. I recently bought an HTC One M8 for the ATT network that was previously rooted. I noticed it was on 4.4.2 and wouldn't upgrade to 5.0 so of course I tried to remove root. I went into TWRP recovery (which I know is why it wouldn't update because I didn't have stock recovery. For the life of my I couldn't get ADB to recognize my device to flash it.) I went over to "wipe" did the advanced wipe and ticked all the available options. Now, upon rebooting I noticed that I deleted the entire OS. After trying and trying I couldn't get it to boot past the HTC screen. Finally I figured out how to flash a rom using the information here "http://forum.xda-developers.com/showthread.php?t=2736694". After flashing the rom, it was still stuck at the HTC screen when trying to boot. I found some information about extracting the boot.img and flashing it using "fastboot flash boot boot.img"
Now this sort of fixed my problem. After turning the phone on, it stays stuck on the HTC screen until the screen times out. When pressing the power button to wake it up it goes into the setup page and from there to the home screen of the phone. There are apps missing, and no home or return keys on the bottom of the screen. So if I go into settings, I'm stuck there unless I power off the phone, turn it back on, let the screen time out, and wake it up.
Any one have any suggestions? As you could tell I'm not very experienced and would have never bothered with this stuff if the phone weren't already rooted when I bought it. I'd be very happy to buy someone a coffee if they can help me out
nikicollazo said:
So I messed up pretty badly. I recently bought an HTC One M8 for the ATT network that was previously rooted. I noticed it was on 4.4.2 and wouldn't upgrade to 5.0 so of course I tried to remove root. I went into TWRP recovery (which I know is why it wouldn't update because I didn't have stock recovery. For the life of my I couldn't get ADB to recognize my device to flash it.) I went over to "wipe" did the advanced wipe and ticked all the available options. Now, upon rebooting I noticed that I deleted the entire OS. After trying and trying I couldn't get it to boot past the HTC screen. Finally I figured out how to flash a rom using the information here "http://forum.xda-developers.com/showthread.php?t=2736694". After flashing the rom, it was still stuck at the HTC screen when trying to boot. I found some information about extracting the boot.img and flashing it using "fastboot flash boot boot.img"
Now this sort of fixed my problem. After turning the phone on, it stays stuck on the HTC screen until the screen times out. When pressing the power button to wake it up it goes into the setup page and from there to the home screen of the phone. There are apps missing, and no home or return keys on the bottom of the screen. So if I go into settings, I'm stuck there unless I power off the phone, turn it back on, let the screen time out, and wake it up.
Any one have any suggestions? As you could tell I'm not very experienced and would have never bothered with this stuff if the phone weren't already rooted when I bought it. I'd be very happy to buy someone a coffee if they can help me out
Click to expand...
Click to collapse
Best advice would be to just run the AT&T stock RUU. It will return your phone back to 100% stock, from there you can decide if you want to root, use a custom recovery, and install a ROM. But an RUU will be your best bet as its quick, simple, and risk free. You can download the AT&T RUU in the link I posted which will be the latest 5.0.2 Lollipop firmware, its a simple .exe file so all you have to do is connect your phone to your computer and double click the file you downloaded (RUU), it will handle the rest. http://www.htc.com/us/support/htc-one-m8-att/news/
Good luck!
root lollipop
CavyS said:
Best advice would be to just run the AT&T stock RUU. It will return your phone back to 100% stock, from there you can decide if you want to root, use a custom recovery, and install a ROM. But an RUU will be your best bet as its quick, simple, and risk free. You can download the AT&T RUU in the link I posted which will be the latest 5.0.2 Lollipop firmware, its a simple .exe file so all you have to do is connect your phone to your computer and double click the file you downloaded (RUU), it will handle the rest. http://www.htc.com/us/support/htc-one-m8-att/news/
Good luck!
Click to expand...
Click to collapse
Hi There --- Can someone help me out? I'm trying to find the correct procedure for updating the At&t M8 on lollipop......
I'm not sure if towelroot will temp root on lollipop --- based on what i've read it wont....
Any help is appreciated....i've searched but can't seem to find anything about rooting lolli on the at&t m8....
biswasd said:
Hi There --- Can someone help me out? I'm trying to find the correct procedure for updating the At&t M8 on lollipop......
I'm not sure if towelroot will temp root on lollipop --- based on what i've read it wont....
Any help is appreciated....i've searched but can't seem to find anything about rooting lolli on the at&t m8....
Click to expand...
Click to collapse
This isn't really related to the OP, so I'm not sure why you posted it to this thread.
I'm confused by the second sentence in your first line. Are you trying to update or trying to root?
Towelroot won't work if the bootloader is locked, that is the whole point of a locked bootloader.
You need to unlock the bootloader. At that point, you can root by a variety of methods. I think towelroot will work (as long as its intended for Lollipop), but you can also just flash a custom recovery and then flash a current version SuperSU (the most common method).
I got an LG G3 that came packaged with 35B (5.1.1), and nothing seemed to be working to get TWRP installed. I couldn't use LG Flash Tools to downgrade using the "TOT" method, because it'd stop with an "no ks version" error. I finally found something that works, and I'm now running AICP (nice ROM) with TWRP installed!
The trick is to follow these instructions (make sure you use VS985 components for our Verizon LG G3s, not D855):
http://forum.xda-developers.com/lg-g3/help/help-secure-boot-error-trying-to-boot-t3054977
Overwrite aboot.img (12B version) & recovery (TWRP image) using dd commands via an adb shell, after rooting with KingRoot, while Android is running. I then used adb commands to reboot into recovery, and volia! I was in! I had AICP on my internal card, and the 12b bootstack, which I flashed in that order.
After seeing AICP successfully boot, I went back and flashed the 35B bootstack. Success!
Stock images (aboot 12B etc.): http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Bootstacks: http://forum.xda-developers.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279
KingRoot: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Great news for you and others. Thanks for sharing!
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
fast69mopar said:
Well, i tried to follow this step by step and I ended up with a black screen after reboot. My G3 would power up, blue and green led's would flash like normal, I could hear the sounds being made by pressing the power button and touching the screen just like everything went as planned except for a black screen. My PC still recognized my device when Android was running and it was still detected when I entered download mode. I could see the device driver installation window popup on my PC and I could see my G3 in my Device Manager as well. I am a little unsure about what went wrong but I am doing my research to see if I can solve this problem. The good thing about the whole situation, I was able to use LG FLashTools 2014 to KDZ back to 35B which is what I was running at the beginning of this process. The software flash just finished and so did "Android is starting" so I will set this thing back up and try again once I find out what went wrong and why I received the black screen afterwards. If anyone can provide any input as to what my have happened or if there was something I missed I would appreciate it.
Click to expand...
Click to collapse
Weird... this is what I did (nothing more):
1) Pick a ROM I wanted to use. I went with AICP nightly for VS985 (MM 6.0.1). Put that ROM zip to be flashed by TWRP on your internal memory.
2) Put the 12B bootstack on internal memory.
3) Put the 12B aboot.img & latest TWRP img on internal memory.
4) Root with KingRoot
5) Open up an "adb shell" and use "su" to get a root shell.
6) Use dd commands (like in the original post's link) to zero, flash aboot & the recovery image to their proper partitions.
7) Use "adb reboot recovery" to boot into TWRP
8) Factory reset
9) Flash ROM (AICP etc.)
10) Flash 12B bootstack (not 100% sure needed, but whatever)
11) Wipe cache/dalvik (not 100% sure needed, but whatever)
12) Reboot & profit!
After seeing successful boot, I did go back into TWRP & flash the 35B bootstack, just to have the latest stuff that still does work.
I *did* have one oddity where my screen went black, but NOTHING was responsive (not even the LED). Phone just appeared completely dead -- no response to anything. I pulled the battery, and it booted up fine. Hasn't happened again...
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
fast69mopar said:
It was weird indeed. I flashed the 35B KDZ to return to stock after the screen went black. I was already on the stock 35B OTA that I received back in October. I was already rooted with Kingroot and had already removed Kingroot with SuperUser in its place. Was that something that was different between us maybe? Were you on the stock 35B, unrooted, before you started the process? Like I said, I was already rooted. Don't know if it makes a difference or not. Since I was able to flash back to stock after the mishap I will be trying it again here shortly when I get back in from of my Laptop. I am fully stock right now and my software status is official. I will do the process over again starting with a fresh template. I'll edit my post with an update after I'm finished. Thanks for the response and for the guide.
Click to expand...
Click to collapse
I was on a "fresh", unrooted flash of the 35B KDZ after some previous failed attempts to get TWRP installed. Then, I started my steps listed above. I didn't swap out KingRoot to SuperSU (since I knew it'd just be overwritten when AICP gets installed). Just needed root to flash aboot & recovery.
What command did you run to flash the twrp img, in the other link with the commands of says he used flashify but you used terminal to flash yours. Thanks.
It works.
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
jimtom1948 said:
New here, also with VS985 35b. LG Flash tool kept giving me failed previous flash on every attempt to downgrade to 10b. Saw this and using the same aboot.img and bootstack.zip that you used, I used terminal emulator to update and it worked first time. I just had to remember to use VS985 components including twrp. Everything is now running, and am so thankful. My first G3, previously rooting and playing with Samsung S4. Again, thank you for your incredible work.
Click to expand...
Click to collapse
You mind giving m the exact commands you used and the order you did everything in? Got a little confused going from thread to thread to get everything downloaded. Think I read too much.lol confused myself
Evohog
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
jimtom1948 said:
1) Started on this site and downloaded:
Stock image (aboot.img 12b)
bootstack (12b) down the page in downloads.
This is important because the instruction page is for D855 and you need VS985 aboot and bootstack. This was what initially confused me.
2) I then went to the page that says follow these instructions.
Here I downloaded oversharpening fix flashable zip and a twrp recovery for VS985.
You will want to substitute VS985 aboot and bootstack for the D855 in his writeup.
3) I followed the rest of his tutorial, very carefully typing the commands into terminal emulator. (I haven't got my linux machine ready for adb yet.
4. Shut down the phone. rebooted into recovery (You can use flashify settings to reboot into recovery, or the buttons on back of the phone after shutdown.
5. It worked, I was in twrp. Flashed the oversharpening and the 12b bootstack.
Hope this helps.
Click to expand...
Click to collapse
One last question, where in the commands it says "block/name/a boot" so I enter vs985 where it says name or do I enter name. I'm so rusty,it's been a couple years since I've even rooted anything. Thanks again for the hand holding.
Evohog
If you are talking about the commands that you type into the terminal emulator, you enter them just as they are written, except for what is in quotes. Don't change them. Good Luck.
Hey guys, Tried this and now im hard bricked. Could anyone give me a hand? I have everything posted here.
http://forum.xda-developers.com/verizon-lg-g3/help/kdz-restore-t3315170/post65328929#post65328929
johnny567
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
jimtom1948 said:
I was successful twice with this method. The third time, it bricked so hard I couldn't even get into download mode. After a ton of reading, I found a recommendation in
verizon-lg-g3/general/restore-verizon-to-stock-t2827878/page24 no. 236 by jhtrades 1 at the bottom of his recommendation (ALT METHOD #2).
http://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928. I followed along starting with step 6, no wire, and somehow got the phone back to a version of verizon with a problem in the bootloader. At least, I was able to get into download mode and did a KDZ to 10b. After that everything was back on track.
I am not absolutely sure if this will work for you, or exactly sure what I did, but it's the best I can come up with. All I remember at the time, was it seemed complicated. Good luck and hope you get it back and working.
Click to expand...
Click to collapse
It doesnt seem to be working for me. It is pulling up as the Qualcomm 9008 and i have tried with and without wire. It keeps failing and I end up with the error "No response from the device. Check PMIC first and if still boot problem replace AP." I noticed that I have a vs985k. Do you think that could contribute to the failure?