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
I have a Verizon galaxy note II, and had been running AllianceROM.
AllianceROM seemed to be running pretty good until one day when my accelerometer stopped working. I thought it may be a software bug, so I tried to reflash the ROM. I got a bootloop, and tried again.
I tried to flash cyanogenmod 11 and still got a bootloop. Then I realized I didn't have a safe backup.
I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm.
In the end, I'm stuck with a note II that can't boot. When I try to turn it on, I see the galaxy note II logo, but then the screen goes black (not off, I have to pop the battery out before I can try again.) Power+home+volume up now brings me to android system recovery/manual mode, and power+home+volume down gets me to ODIN mode.
Any suggestions or help would be greatly appreciated. I really wasn't planning on getting a new phone at this point, so I hope it's not beyond fixing! Thanks in advance.
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
mattnmag said:
Ethan,
It sounds like you should be able to fix your device if you are careful. If you can boot into the stock recovery using power+ home + volume up buttons, then do a factory reset and wipe cache... that might fix your problem and let the device boot up normally.
You should also check out Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. His guide has links and detailed instructions on how to restore back to stock. (Hit the thanks button for him too... as he spent a lot of time making the guide).
Remember that 4.1.2 is the last build that allows us to unlock our bootloader, so don't restore the device to 4.3 or 4.4.2 unless you want to permanently lock your bootloader. Also, there's no current root method for our phones if they get updated to stock 4.4.2, so don't odin that unless you decide you don't want root and custom ROM'S anymore.
Good luck!
Click to expand...
Click to collapse
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Ethan.S said:
I just tried following that guide, installing the .pit file and the suggested stock firmware, but Odin reported "FAIL" instead of "PASS."
Now when I try to turn my phone on or go to stock recovery, I get the message "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Any hope left?
Click to expand...
Click to collapse
Yes, there's still hope to fix it if you can get the phone into download mode.
Here's some info to clarify before you try something else.... What firmware did you try to install when you used Droidstyle's guide? Also, in your initial post, you said "I attempted to flash some stock firmware through ODIN, since I couldn't get anything to work through cwm." What firmware did you flash at that point.... was it one of the Verizon stock firmwares? And what build number was it ( 4.1.2 VRAMC3 , 4.3 VRUEMJ9, 4.4.2 VRUFND7)?
I ask this because, if you flashed 4.3 or 4.4.2, then you can no longer restore back to 4.1.2....you would have to restore back to one of those newer versions (and those newer firmwares actually lock the bootloader and install Knox security features... so that's why I was suggesting not to use them--- unless you already did before you had placed your original post for help).
If you can't restore the phone through ODIN using Droidstyle's guide, then you might try the emergency firmware recovery feature that's available through the Samsung Kies program. You can find Kies at this link: http://www.samsung.com/us/kies/
**The KIES instructions say to use Kies version 2.6 for Firmware recovery back to 4.1.2, and use Kies version 3 for Firmware 4.3 and 4.4.2.
Here's a link to Kies 3 FAQ as well: ( http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00059191&fm_seq=81528 ). Scroll down under Basic Functions and look for the link to "How do I Perform an Emergency Firmware Recovery..." The process should be similar if you plan to use KIES 2.6 instead - (that's only if you're able to restore back to 4.1.2 and you never Odin flashed one of the newer 4.3+ firmwares) .
I hope you can get it fixed. If you're not sure of things, I would suggest researching more and asking more questions before going forward. There is risk that we all take whenever we start modifying our phones, and the more knowledge we can get, the better chances of recovering from errors when we mess something up. (I know I've made plenty of errors as I've tried to learn... I even bricked my Tranformer Prime tablet shortly after receiving it from EBay :banghead: ). If worst comes to worst, you might end up having to pay someone to do a Jtag repair to unbrick it.... but let's hope it doesn't come to that.
Also-- you could try Verizon's Software Upgrade/Repair Assistant found here: ( http://www.verizonwireless.com/support/devices/knowledge_base.html/80201/ ). I have no idea what the differences are between Verizon's software repair assistant and Kies.... **
(FlashKDZ/Root/Recovery/Hiddenmenu/troubleshooting) (noob2noob guide)
Okay, this is my first thread on XDA, the reason I'm making it is there is a lots of problems with progressing to lollipop. All of this is already mentioned in the forum, but this way it is much easier since it is all at one place. If I'm doing something wrong please warn me with explanation how to resolve the issue. If I'm posting in wrong forum section please move my thread where it is supposed to be.
1. Before doing anything check if your phone is ready to get updated:
1.1 Do you have a stock Kitkat rom or at least a rom that is kitkat based, since there can be a problem with partitioning if custom lollipop rom is installed
1.2 Create a backup. Don't be lazy LG backups will not help you since they can't go from kitkat to lollipop, don't try to do it from recovery because you will lose custom recovery. Copy your files from phone including extracted contacts, and back it up online with google or some other backup providers.
1.3 Check if you have a latest touch firmware, because you might have a problems after installing lollipop and it will be hard for you to check for updates since your touch might become useless.
1.3.1 To check it go to hidden service menu by typing 3845#*802# and go under HW Device Test, then Touch Test then touch firmware version and write everything down. After that go to touch firmware upgrade and after 15 seconds compare the touch firmware version values with those you written down.
1.4 In hidden Menu you can also go to wlan test then ota setting to check if it is disabled on your phone. After that check again if there is OTA updates for your phone, and also check if there is PC suite Update.
1.5 Check your phones version if it is D802, D800 or something else, and check which rom you have installed. You can do this in settings about phone or if you are happy about hidden menu found, go there and into settings then version info. This might not be interesting or fun to do, but it will save you the trouble if something goes wrong, because you will know what to ask.
1.6 Last but not the least, before starting to flash fill up your battery, i've read some posts that say there are problems with wrong capacity shown, and a lots of battery drain problems, and only solution till now is to have a full battery on start.
2. You will need LG FlashTool and of course installed drivers for your G2 on your PC.
All of that you can get in the thread by @quangnhut123 .
2.1 Just a bit of precautions, don't forget to always copy a kdz file in to Flashtool folder and then start a tool. All should look the same as in that thread, except you should always use CSE method because with this method you will install kdz from scratch, removing everything from the phone.
2.2 You should find the kdz file which suits for your phone on site . You can check for kdz by typing in imei in check new firmware section or find the one for yourself by searching the site. v30a is lollipop open while v30d is for branded G2's.
(I've read that this site is not allowed by Xda moderators, so if I can't post it please give me info on where should we download kdz's from).
2.3 I think it's all pure logic now but lets say it one more time. You have downloaded kdz file, and put it inside LG Flashtool folder. You should now start Flashtool and get your phone into Download mode. To do this you need to hold volume up button on turned off device and connect usb cable while holding volume up. Now just cse flash.
2/3 This is troubleshooting step, if you have a problem ask and i hope this great community will help you like they did to me, and ofc I will do my best to help.
3. Now we go to rooting.
Here is the thread by @avicohh which worked for my D802.
Just follow his step by step tut and you will have a rooted phone
3.1 The only issue that might happen here is you are stuck with # and adb waiting for your phone. To resolve this just go into download mode manually.
4. Okay rooting done, now let's go to custom recovery install
It's easy as installing an app from google play by @bender_007
4.1 After installing it open the app and follow the on-screen instructions. If it fails for the first time, try it few more times, it will eventually work. (OFC. I didn't install it with only one try).
4.2 To get into custom recovery hold volume down and power button till first LG sign shows up, then release both buttons and quickly press them again. It will ask you do you want to do factory reset, press yes and yes again, and it will get you to custom recovery if you installed it.
4.2.1 If you factory reset your phone that means you didn't install recovery correctly and you will lose your data, but again that should be no problem since you have that backup from the start.
Now optional steps:
5. Install system app remover to remove bloatware from your phone. You can do it manually but this way you will have those apps backed up.
6. Next suggestion is to install a few mods if you need them. In my case I had to have a Plug and pop, since it is lost from Lollipop and I loved that feature. Here is a thread on how to install that mod by @p_a_r_s_a7
//That's all, if you have any questions feel free to ask, since there is no dumb questions, but also try to read carefully before//
Thanks to:
@quangnhut123
@avicohh
@p_a_r_s_a7
@bender_007
A lot of others whose names i can't remember. If anyone else needs to be mentioned PM me and i will add you in this section.
I will add pictures and stuff if needed
Thanks, good all-in-one thread, + easiest methods. Ill recommend it‚to others
This forum is such a mess that a thread like this is like a fresh breath of air. Every advice given on other threads references something that you should already know how it's done, or you should already have done to your phone in the past and have a certain version of it, or non-working tools that are only around for a few months until an update makes them unusable.
No wonder that most of the first-page topics, including pinned ones, have the word "brick" in the title. This should signal the forum moderators that something is wrong around here.
My phone is stock international sim-free G2, never rooted or otherwise modified and yet no one was able to offer a coherent solution of how to update to Lollipop, until your post.
So, thanks for this thread.
Thank you, that is exactly why i made the thread. Every one of those threads has everything explained, but you need to search theough 150 pages to understand how something is done. That's why i wanted to make a thread with all explanations made in a single post and to make it noob friendly since the worst thing that happens in other threads is answer like use a search you have it somewhere.
Hi,
Thanks for the thread. It really helps noobs like me, but I still have a couple of questions...
I was running Paranoid Android L rom with root, twrp and kk bootloader on My D802.
I didn't see this thread before I decided to downgrade back to 4.2.2 stock rom, and now I don't really know what steps to take.(I have kernel version 3..4.0 and build number JDQ39B)
I haven't seen an OTA available, so I was thinking of flashing new Lollipop rom kdz file. But I've been seeing stuff about using LG PC suite to upgrade via OTA so i wasn't sure.
So my main question is that do I do an OTA upgrade on my current 4.2.2 stock rom or do I download an official Lollipop rom? Can you give me a brief idea of the steps to take?
Thanks
seyio said:
Hi,
Thanks for the thread. It really helps noobs like me, but I still have a couple of questions...
I was running Paranoid Android L rom with root, twrp and kk bootloader on My D802.
I didn't see this thread before I decided to downgrade back to 4.2.2 stock rom, and now I don't really know what steps to take.(I have kernel version 3..4.0 and build number JDQ39B)
I haven't seen an OTA available, so I was thinking of flashing new Lollipop rom kdz file. But I've been seeing stuff about using LG PC suite to upgrade via OTA so i wasn't sure.
So my main question is that do I do an OTA upgrade on my current 4.2.2 stock rom or do I download an official Lollipop rom? Can you give me a brief idea of the steps to take?
Thanks
Click to expand...
Click to collapse
Updating through pc suite or ota is the best way if it is available to you. Flashing kdz is the same thing but that is doing it manually while through pc auite nad ota is pretty much automatic. Anyways which ever way you decide to use be sure to fully charge your battery and factory reset acter the update. If you need anything else feel free to ask
[email protected]$o said:
Updating through pc suite or ota is the best way if it is available to you. Flashing kdz is the same thing but that is doing it manually while through pc auite nad ota is pretty much automatic. Anyways which ever way you decide to use be sure to fully charge your battery and factory reset acter the update. If you need anything else feel free to ask
Click to expand...
Click to collapse
Do I flash KK bootloader or root before I update through ota?
seyio said:
Do I flash KK bootloader or root before I update through ota?
Click to expand...
Click to collapse
No need to flash bootloader if you didnt flash it for paranoid android. And definitely no need to root since you can root after update.
Problems with flashing KDZ
I have downloaded Spain Lolipop KDZ file for LG G2 D802.
Have backed up everything usint TWRP> ( Presently on Optimus G3 rom v 1.4.1 with dorimanx kernel and TWRP )
I have copied the KDZ file to the flash tool. When i use CSE flash .. it takes me to the next page .. in which I click on Start which then opens up the LG Mobile support tool.
Then it shows detecting ur phone .. unpacking or extracting file .. after that shows software updating .. reaches 2 % and then shows error .. asks me to retry .
Do you know what I am doing wrong ? or the cause of this prob ?
http://i58.tinypic.com/15rk2eo.png
sankeerth24 said:
I have downloaded Spain Lolipop KDZ file for LG G2 D802.
Have backed up everything usint TWRP> ( Presently on Optimus G3 rom v 1.4.1 with dorimanx kernel and TWRP )
I have copied the KDZ file to the flash tool. When i use CSE flash .. it takes me to the next page .. in which I click on Start which then opens up the LG Mobile support tool.
Then it shows detecting ur phone .. unpacking or extracting file .. after that shows software updating .. reaches 2 % and then shows error .. asks me to retry .
Do you know what I am doing wrong ? or the cause of this prob ?
http://i58.tinypic.com/15rk2eo.png
Click to expand...
Click to collapse
Had the same problem when flashing kitkat kdz. Are you sure that you have pasted kdzfile inside flashtool. If that is not the problem try other kdz. That helped me
Where are you from and more specifically whhere your phone is from so i can maybe help you with finding right kdz. And btw i think you might have a problem when trying to restore that backup so if you still can backup your phone manually or on the cloud.
[email protected]$o said:
Had the same problem when flashing kitkat kdz. Are you sure that you have pasted kdzfile inside flashtool. If that is not the problem try other kdz. That helped me
Where are you from and more specifically whhere your phone is from so i can maybe help you with finding right kdz. And btw i think you might have a problem when trying to restore that backup so if you still can backup your phone manually or on the cloud.
Click to expand...
Click to collapse
I have restored the complete back up using TWRP .... Yes i have already pasted kdz in the same folder of flash tool...still no change .. now downloading D802 20H firmware to flash stock n den again try KDZ
I have seen that some guys who had the same problem resolved it with disconnecting from network
Sent from my LG-D802 using XDA Free mobile app
sankeerth24 said:
I have restored the complete back up using TWRP .... Yes i have already pasted kdz in the same folder of flash tool...still no change .. now downloading D802 20H firmware to flash stock n den again try KDZ
Click to expand...
Click to collapse
http://www.1x1a.com/fixlg-flash-tool-stuck-at-2.html
Or maybe try this. I havent tried it so i cant promise anything but if you want you can try. Hope it helps
[email protected]$o said:
No need to flash bootloader if you didnt flash it for paranoid android. And definitely no need to root since you can root after update.
Click to expand...
Click to collapse
Hi again..
OTA update to Lollipop has failed on my D802, LG PC Suite only upgraded me from Android 4.2.2 to 4.4.2, so can anyone help me out here?
Am I missing something for OTA update? If not, then which lollipop kdz can I download for my phone so that I can flash? I live in UK and i use a 3 UK sim if that helps
but also, In the process of trying to boot into my previously installed TWRP recovery, I discovered that i have been restored to stock recovery. I have rooted the phone, but just wanted to clarify: I flash custom recovery, then bootloader/kernel then lollipop kdz?
Thanks again
seyio said:
Hi again..
OTA update to Lollipop has failed on my D802, LG PC Suite only upgraded me from Android 4.2.2 to 4.4.2, so can anyone help me out here?
Am I missing something for OTA update? If not, then which lollipop kdz can I download for my phone so that I can flash? I live in UK and i use a 3 UK sim if that helps
but also, In the process of trying to boot into my previously installed TWRP recovery, I discovered that i have been restored to stock recovery. I have rooted the phone, but just wanted to clarify: I flash custom recovery, then bootloader/kernel then lollipop kdz?
Thanks again
Click to expand...
Click to collapse
I am not sure but i think that update for the uk didnt come out yet. so you can't update to lollipop yet via pc suite or ota. and you got it all wrong. first you flash lollipop kdz but you will have to try out few of them since official for uk didn't come out yet, after that you root, and then flash custom recovery.
and as previously you will be back to stock recovery after update. you have it all explained step by step in first post. i know it is a bit long but that is the best way, since i didn't want to write stuff like "you should know that" and so on. so just follow the first post and you will be happy, or wait for official uk update over the ota you will be happy too, and i guess it should come out in a month.
[email protected]$o said:
I am not sure but i think that update for the uk didnt come out yet. so you can't update to lollipop yet via pc suite or ota. and you got it all wrong. first you flash lollipop kdz but you will have to try out few of them since official for uk didn't come out yet, after that you root, and then flash custom recovery.
and as previously you will be back to stock recovery after update. you have it all explained step by step in first post. i know it is a bit long but that is the best way, since i didn't want to write stuff like "you should know that" and so on. so just follow the first post and you will be happy, or wait for official uk update over the ota you will be happy too, and i guess it should come out in a month.
Click to expand...
Click to collapse
Thanks for the quick reply.
I'll download all the lollipop kdz's and see which one of them works for me till the UK one comes out then I'll just do a normal flash over it.
But seriously, one month for the UK ota :crying: Right now, I don't even know which is worse: Google that takes forever to release updates with so many bugs, or Apple who generally release better stable updates but make older devices laggy...
Thanks again for all the help.
seyio said:
Thanks for the quick reply.
I'll download all the lollipop kdz's and see which one of them works for me till the UK one comes out then I'll just do a normal flash over it.
But seriously, one month for the UK ota :crying: Right now, I don't even know which is worse: Google that takes forever to release updates with so many bugs, or Apple who generally release better stable updates but make older devices laggy...
Thanks again for all the help.
Click to expand...
Click to collapse
its a good update, not that buggy, and be sure to fully charge your battery before the process. you should try europe open or something like that, but there is no german or uk release yet and some guys suspect it is slowed down because they found out bugs in other versions
After CSE Flashing my d802 with a 30a, it got stock on lg logo screen, then an android screen with "erasing" on bottom, then lg screen. I let it sit for 4 hrs but nothing happened. Im back to stock kitkat atm. A little help please.
fernievidal said:
After CSE Flashing my d802 with a 30a, it got stock on lg logo screen, then an android screen with "erasing" on bottom, then lg screen. I let it sit for 4 hrs but nothing happened. Im back to stock kitkat atm. A little help please.
Click to expand...
Click to collapse
Where from is your phone? Are you sure you flashed right kdz? Did lollipop even turn off? DidCSE flashing finished sucessfully? I would like to help you, but i cant if you dont explainme what is your problem. I am not some pro who faced every error on every phoneso please explain a bit more
And i suppose that erasing screen could have been factory reset on stock recovery
[email protected]$o said:
Where from is your phone? Are you sure you flashed right kdz? Did lollipop even turn off? DidCSE flashing finished sucessfully? I would like to help you, but i cant if you dont explainme what is your problem. I am not some pro who faced every error on every phoneso please explain a bit more
And i suppose that erasing screen could have been factory reset on stock recovery
Click to expand...
Click to collapse
I believe mine is an international version. Where it came from, well, I'm from the Philippines and I got my phone from a local telecom, Globe.
The flash tool said that it was successfully upgraded, but judging from the phone's behavior I think there's something wrong. My phone never started successfully, and I got stuck in the LG logo.
Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
mrbix said:
Hi All,
I have relented and admitted defeat. Wondered if someone would be kind enough to help me get my Z5C back to stock, actually I want it rooted but I’ll take a stock version right now, given how many hours I’ve thrown at this. I would consider myself a novice, but not a complete novice. I recently upgraded from Z1C, and the rooting process for that phone was pretty straight forward, however I have come unstuck trying to root my Z5C.
Using my desktop pc, I followed this guide perfectly until I got to “4. Root MM”:
http://forum.xda-developers.com/z5-compact/general/summary-tutorial-root-sony-xperia-z5-t3360515
At that point I chose “Alternative 3” and somewhere or somehow made a mistake possibly? I don’t know but my phone wouldn’t boot up.
Note: I managed to backup my DRM keys, I have a TA.img file saved to my pc.
I thought I had botched up the process and would start again by reflashing the Lollipop stock exploitable firmware, E5823_StoreFront_1299-6910_32.0.A.6.200_R2B. I used Flash Tools and connected my device in flash mode and flashed the ftf but the flashing process wouldn’t complete. It keeps hanging or getting stuck, I’ve left it for hours to complete and it never does, here’s a screenshot:
https://www.dropbox.com/s/yggshdri5r6x1br/Flash Tools.png?dl=0
I thought it was my fault so made sure I had all the drivers installed for, flashmode, flashboot, Z5C, by running “Flashtool-drivers.exe” in the drivers folder and rebooting my pc. I tried downloading Lollipop firmware again and creating the ftf file again. I tried flashing the ftf, again and again and it never gets past “modem.sin”.
I tried the whole flashtools-flash-ftf process again, but this time I used my laptop and got the exact same result. I actually tried multiple USB 2.0 ports on both my pc and laptop also, but had no luck.
Anyway I gave up on rooting MarshMallow and just focussed on getting my phone functional with an operating system.
I came cross this tutorial and managed to install CM13 just fine by flashing the kernel(boot.img) and then recovery(TWRP v3), wiping(dalvik, system, cache, data) and installing the CM13 zip file from within TWRP:
http://forum.xda-developers.com/z5-compact/development/rom-cyanogenmod-13-sony-xperia-z5c-t3339930
As I type my phone is working fine with CM13 but how do I get MarshMallow back on my phone? Is it something to do with Sony RIC and DM-Verity? Do I need to somehow restore my DRM keys first and then try reflashing the stock Lollipop? Any help with this would be greatly appreciated.
Thanks,
Bix
Click to expand...
Click to collapse
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
mrbix said:
Thanks very much. I've managed to flash my phone and am rooted on MM.
I tried re-installing the latest version of flashtools v9.22.3 and used "flashtool-drivers.exe" to install the flashboot and flashmode drivers and finally the Z5C drivers and it still didn't work, and read somewhere(sorry i can't find the link now) that someone had installed all the available drivers from that list . I did that and it worked? I'm sure I've fluked this but glad it's worked nonetheless.
Click to expand...
Click to collapse
correct driver installation was a bit difficult also for me. good to know you solved the problem
ninestarkoko said:
look here http://forum.xda-developers.com/z5-compact/help/flashtool-stuck-modem-sin-t3382757
Should be a bugged version of flashtool!
0.9.20.0 works fine for me, you can easily find it on google : "flashtool-0.9.20.0-windows.exe"
I would NOT use previous versions like 0.9.18 or 0.9.19 as suggested in the thread
If it does not solve, i could only tell you to follow another guide, and try again from zero:
please, follow the steps 1 and 2 in this guide http://forum.xda-developers.com/z5-...ck-root-xperia-z5-premium-sony-stock-t3335974
downloading latest ftf for your Z5Compact model (E5823 or E5803, look in settings -> phone info, are you sure you are flashing the correct ftf?).
before doing anything, obviously do a BACKUP
Click to expand...
Click to collapse
Thank you. I had the same issue as OP, Google found me this thread and using flashtool 0.9.20.0 worked.
Hey folks. I'm in need of some help, but need to provide some background info as it seems there might be a few ways to correct this.
Background
I had a recent bad Nandroid mess up a restore process which somehow led to me losing root. I was on XDABBEB's 47A stock rooted ROM for months, then went to try the 3.1.1 ROM recently. I found that I wanted to go back, then BOOM! Bad restore from my data NANDROID. Then I:
Got stuck in a boot loop.
Rebooted into recovery
Saw the LG Recovery
(Stupidly?) chose to wipe cache
Continued to boot from LG Recovery
Went immediately to TWRP
Wiped Data and caches
Rebooted
At this point, I got back into 47A, but obviously without any data. I soon found that, though SuperSU was installed, it wasn't working:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-rot - consult the relevant forums for your device!
Click to expand...
Click to collapse
At this point, I checked Root Checker app and, surely enough, it says I wasn't rooted.
I checked ADB and tried to su from the prompt ($) and
Code:
su: notfound
However, adb reboot recovery brings me to TWRP
I tried TOT'ing on my Windows 10 (x64) machine, but it wasn't working:
PID: FAIL
IMEI: Unknown
[23:59: 0] CrossDL [Unknown] to [VS985].SW ***The text on this line continues, but I can't read it***
00000064
Error: [23:59: 0] CrossDL [Unknown] to [VS985].
Click to expand...
Click to collapse
I'm lucky in that my phone is currently working fine. I'm on 47a with everything working fine ... just not rooted, which I would really like to be.
So, my question is, what should I do next? I know some options that I have, I just don't know what options I should try or in what order I should try them...I understand some of the jargon and background info, but I don't understand the true inner workings of rooting and therefore don't feel comfortable making these choices on my own.
So, to all of you people that are way more intelligent at this than I am...
Should I try restoring my rooted 49A backup from TWRP?
Should I try to flash SU binaries in TWRP?
Should I TOT from my work machine that is Windows 7?
Should I KDZ on Windows 10?
Thanks in advance for your collective help.
This inquiring mind wants to know!
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone. In that case, you must flash back to 10B via the TOT method. That way, you can then root with Stump and then install TWRP, flash the correct boot images, and then reflash XDEBs ROM.
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method. It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
iBolski said:
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone
Click to expand...
Click to collapse
Correct. xdebbeb's stock 47A on a non-K model
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method.
Click to expand...
Click to collapse
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
Click to expand...
Click to collapse
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
my.ads0 said:
Correct. xdebbeb's stock 47A on a non-K model
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
Click to expand...
Click to collapse
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
iBolski said:
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
Click to expand...
Click to collapse
I just want to make sure that you're aware that I am NOT on pure stock 47A. I'm on xdabbeb_stock_vs98547a.zip from here.
When I flashed back from his 3.1.1 ROM, I flashed to my backup of the above ROM, which had Root. The SYSTEM flash from my nandroid back to his version of 47A worked without incident, but the DATA flash of my nandroid failed, left me in a bootloop, after which I performed the actions outlined in my original post. That squarely left where I am now, with no root, but on his version of 47A (I never had the stock 47A on my device before) with TWRP as my recovery.
In the end, I'm game for trying different things, but ideally, I'd like to try the least invasive method (trying to flash SuperSU in TWRP?; trying to flash my xdabebb 3.1.1 version?) ) before trying any other method or going to the extreme method (TOT'ing). I just am trying to avoid TOT'ing since my phone IS working AND the fact that I would have to do that at work. It would suck to go from a working phone to a broken phone without being able to fix it without knowing that I tried all of the least invasive methods first. I just need guidance from people like you as to what will or won't work in my situation.
The reason for this post is that I wasn't sure that you were aware I wasn't on pure stock 47A, but on xdabebb's version, which maybe you had overlooked and offered me more options? If you were aware of that and everything above is irrelevant, then I'm cool with that. Just tell me so. I just didn't want that fact overlooked.
Thanks again for entertaining my inquisitiveness, iBolski.
Well, trying to install the SuperSU binary zip from TWRP didn't work. That got me flashing blue & red lights. I tried restoring my XDABEBB 49A 3.1.1 install and that didn't help either. Both TOT & KDZ methods are failing on my PC (Windows 10) with both not able to read the phone properly (can't see imei). I will maybe try to uninstall the drivers or just wait until Monday to try my windows 7 machine at work.
Oops.
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
my.ads0 said:
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
Click to expand...
Click to collapse
Awesome. I saw your earlier post about being on XDEBB but that didn't matter. You were at a point that flashing back to 10b was your best option to get back to XDEB. That's why I kept saying you needed to flash back to 10B if you wanted to get back on XDEBB because where you were at that point was messed up, so it was just best to flash to 10b clean.
Glad you got it all worked out!