Related
Hi, All. Ive followed XDA for a long time and love it. I love my verizon G-Pad but ever since the Lollipop update it has just been so slow and almost unsuable. Well ive got good news. Today i found a way to downgrade back to LG Official Kitkat 4.4.2.
Tool Used: LG Flash Tool 2014 - you can download from this thread
http://forum.xda-developers.com/showthread.php?t=2785089
I could only get this to work from LG's Download Mode (with tablet turned off, hold the Vol Up Key and plug in USB cord)
If you are running version 23A Lollipop you must downgrade to 22A first. Attempting to downgrade straight to 11A (Kitkat) will fail at 57% restore.
After downgrading to 22A, allow the device to fully boot then shutdown and return to download mode
Now push 11A firmware, everything should now go smoothly (at least it did for me)
Firmware Download and LG Flash Tool Bundled
https://mega.nz/#F!fgskmDSB!GANW9PaJ0dW3lvHCWBzscQ
Many Many thanks to the Devs of the LG Flash Tool for such a wonderful utility on LG Devices
tutorial?
How do I downgrade to 22a?
In the Firmware download link I've provided is the 22a and 11a firmwares. Follow the LG Flash Tool link for usage.
Sent from my LG-VS985 using Tapatalk
buddyjwilson said:
In the Firmware download link I've provided is the 22a and 11a firmwares. Follow the LG Flash Tool link for usage.
Sent from my LG-VS985 using Tapatalk
Click to expand...
Click to collapse
Hey man gotta question, my pad was on lollipop and only rooted with no real tweaks and I rebooted one day and it sticks at the Verizon logo. I can get to stock recovery where any selection goes to fastboot where any selection goes to a blank screen where I have to kill it. The couple others I've seen with this problem had success with the support tool / update recovery deal but mine says everything is up to date. I tried flashtool with a kdz and I get all the way to it supposed to send it but the tab download stays at 0% and nothing happens....I would rather have kk anyway would it be worth trying this , **** can't hurt the damn thing no worse lol tired of it sitting in my dresser where its been for months ...I really wonder wtf happened to it
EDIT...... OK I feel like a real dumbass lmao... Apparently the pc I was using had an Antivirus on it and apparently the flash tool doesn't play well with an Antivirus
OK has anyone found a twrp that will flash correctly on the vk700? The twrp floating around for gpad 10.1 only works on the v700 cuz its been bumped To work on the locked bootloader....
Sent from my VS986 using Tapatalk
Does anyone know if it works on v700 ?
good day
I wanted to downgrade the firmware lg pad 10.1 g (v700)
this issue http://forum.xda-developers.com/g-pad-10/general/g-pad-10-1-verizon-return-to-kitkat-t3226085
but now only comes on and QHSUSB_BULK
and locate the driver and remains QDLOADER 9800
as I remount firmware or where I get the files for this tablet TOT
carlosdjmix said:
good day
I wanted to downgrade the firmware lg pad 10.1 g (v700)
this issue http://forum.xda-developers.com/g-pad-10/general/g-pad-10-1-verizon-return-to-kitkat-t3226085
but now only comes on and QHSUSB_BULK
and locate the driver and remains QDLOADER 9800
as I remount firmware or where I get the files for this tablet TOT
Click to expand...
Click to collapse
Well this downgrade is for vk700 not v700 which is a big difference, I found that out by trying to get twrp to work on my vk700 when it's only for v700 which if you have the v700 your better off
Sent from my VS986 using Tapatalk
:crying:
My issues is quite complicated. Please be patient and read on.
Less than a week ago, I bought an LG G3 D855. It wasn't brand new and definitely out of warranty.
It was on the 4.4.2 Os version but I couldn't update it because I couldn't locate the UPDATE CENTER and after some research online, I found out it was because it was rooted. I couldn't find a Supersu application anywhere on the phone anyways but Root checker confirmed that it was rooted.
I downloaded the stock kitkat firmware in a .tot format and I tried flashing using LG Flash Tool for TOT but it failed because "Device version is different"
I checked the Imei online and it stated that the device is a Sprint LS990 but the details embedded in the phone all say it is D855
I checked online and found a couple of posts about this error and one user said he was able to fix it by flashing the actual Sprint .tot with the lg flash tool. I tried that but it didn't work. It still said "Device version is different. Check BIN or dll"
I checked online and found results pointing to a generic .dll file for G3s and I downloaded it but when I used it on the Flash tool, it resulted to an error "CrossDL blah blah"
So I found a Marshmallow kdz file. LGUP won't see my device model so I was able to flash it after editting the software in my build.prop to D85510n.
***I have always changed the port to COM41 in all the steps I used
The LG UP detected my model and it flashed to 100% but got stuck on a bootloop by loading the lg screen, freezing and restarting by it self. It never gets to the homescreen.
I downloaded lollipop kdz reflashed using LGUP in a form of downgrade and it got to 100% and got stuck at the lg screen while trying to reboot.
I redownloaded the stock kitkat rom and used the Lg flash tool but it failed. It said 'PID null IMEI Null"
I used LGUP to reflashed. It came to my understanding that the LGUP can flash both kdz and tot. So it flashed to 100% but got stuck at the lg screen and I have tried all I can but it is stuck. It can go into download tho. I don't know what to do about the IMEI. I don't know if the last flash retrieved it. I don't kniw what to do.
It no longer shows as LGE AndroidNet USB Serial
Please can anyone help me?
I just need my phone to work again. I was stubborn and now I regret it. I should have just stuck to kitkat. I'm so desperate to get my phone working that I wouldn't mind Android Froyo Os if it was ever possible.
PLEASE HELP!!!
I think you have to repair the IMEI...
maybe this can help
https://youtu.be/nwzgs1Cmr9k
Sent from my LG-D855 using XDA Free mobile app
I think that he forgot to hard reset after flashing the kdz.
i completly know what you should do:
1: force your phone into qualcomm 9008 mod.
2: use board diag unbrick instruction and it will boot on download mod. for unbrick you will need best kitkat tot for your G3 model.
3: flash best lollipop or kitkat tot to make your phone alive
and then flash it with any kdz you want(it should be for your G3 model)
my telegram ID : @Erfan_rv
pls help me
Apparently, it seems my bricked phone keeps disconnecting during flashing process. I dont think it the fault of the cable because I have used different ones and they all seem to work fine with other phones. I have tried a different computer and still the same results. it connects as qualcom 9008 but once I try to start flashing, it disconnects and interrupts the flashing process. my phone just shows a grey screen now when I power it up with the battery in. also, I was trying to upgrade from linear os to the latest linear os. I cant fine the tot out there so im using zv6 currently. could this also be the problem? thanks in advance
On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
Success -- Downgrade of MM to LP works with the downgrade firmware above , works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , it detected .134 and ..144 and .184 MM update packages and now also should detect .223 latest firmware if on ext SD if written like mentioned and shown in the video !
The above LP downgrade version is detected in .223 latest M firmware after a reboot.
Some pics
Seeing a lot of people bricking their devices downgrading to LP from M .
There is now no need for all these bricks when we can downgrade via M recovery to LP via ext sd card .
If you are on a stock rom MM bl and rooted TWRP ..you just need to flash stock boot.img and recovery for the MM build you are on . Reboot to stock M recovery. Follow above procedure.
If you are on M bl custom Rom and rooted TWRP but have no stock M back-up , flash back boot.img and recovery for.134 , sideload .134 stock. Then downgrade
That above applies to 551 Z00A .
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
audit13 said:
Yup, using the Asus files to downgrade from MM to LP bricked my brother's phone. I've tried a few methods with xFSTK to fix it but nothing has worked so far. Looks like the phone will be recycled Oh well, he seems pretty happy with his Samsung Note 3 for now
Click to expand...
Click to collapse
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
timbernot said:
Yup , even tho i can unbrick in xFSTK in less time it takes to downgrade (everytime success btw) -- pay attention to the video... on the edited files i show in file manager
Click to expand...
Click to collapse
Thanks, I'll give it another go when I have a chance.
audit13 said:
Thanks, I'll give it another go when I have a chance.
Click to expand...
Click to collapse
You need to have a working device to downgrade via SD :good:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
audit13 said:
Okay, I was able to restore stock MM to the phone which is what it has before it bricked. Problem now is that I can't verify the Google account I tried both of my google accounts without success. I'll have to find some other method.
Click to expand...
Click to collapse
But you was bricked a moment ago - no comprehendi ?:laugh:
If you used xFSTK you wouldnt need to downgrade , you would be in LP already.
If done on another device try later , maybe a reboot :good:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Now its time to party vid coming soon .
All the very best wishes to each and all
audit13 said:
I was bricked and was able to iFSTK to get into the bootloader. I then used the Asus Flash tool to flash an MM raw file to at least get the phone booted. I was happy until I was stuck at the set up screen with no way to verify the google account.
Click to expand...
Click to collapse
MM raw file Hey , please share here ?
If there even is a MM raw file that is
Flash 5.0 raw for 5.0 then you wont need to downgrade btw
And this is nothing to do with downgrading via SD card btw - off topic
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
audit13 said:
I believe I used the MM ww raw file from here: http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
Do you know what you are doing ?
Saying , posting ?
Do you have a zenfone ?
Let me know which one of my posts is confusing and I'll try to clarify.
On 551 Z00A or AD the official downgrade version of LP WW-52.20.40.196 firmware from any M stock firmware - via sd card
https://www.youtube.com/watch?v=_1T6SMJiUSg&feature=youtu.be
OP updated
Merry Xmas to all at XDA --Still seeing people looking to downgrade from M to LP even after posting this method above via ext SD card - WOW
So , my present to you is a video of the above process
Say NO to anymore bricks Say NO to ever having to use xFSTK downloader again
This makes our phones fully , changeable forwards and backwards via SD card (for good)
The process will go from .184 M to .196 LP on the 551 Z00AD or Z00A
If you Have MM bl custom rom - use giovix`s Modder tool to `return to stock option` flash boot.img - flash recovery option in Modder . Follow process.
Video Coming Soon ...........
Ps, i assume the process will be exactly the same for Z008 from the latest Stock M to LP but using the relevant downgrade version(whatever that is) from official ASUS site for Z008
I dont have a Z008 so if anyone wishes to attempt it and give me your results here , that would be great for others
pps, i decided to do the video due to either people dont trust this method or people are extremely shy about hitting the thanks button . Whichever -- help others
audit13 said:
Let me know which one of my posts is confusing and I'll try to clarify.
Click to expand...
Click to collapse
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
timbernot said:
Hi , I understand where you went wrong , you flash raw again in boot loader ,where it stays on ' RESULT=OK ' a couple of mins into flash in on screen cmds , you close flash tools . Force close it...restart flash tools .put all stuff in again ...then press vol+ once.
Leave connected to PC from first part flash all the way through closing flash tools and restarting flash ..do not touch fone apart from vol + before second flash.
Serial will be corrected and you will boot into system.
There is a vid of this exact process in my unbrick thread.
Enjoy
Ps , I never let the first flash finish , due to knowing above process to correct serial..
So if you run into probs , you may need to re flash in xfstk again.
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU! It worked.
This is what I did to cause the loss of serial #:
used the sd card method to downgrade from MM based on instructions from another forum (i.e. not XDA);
phone got stuck at the erasing portion of the process and stayed there for about 45 minutes so I powered off the phone;
used xFSTK to successfully flash the bootloader
successfully flashed MM raw file with Asus Flash Tool;
tried to downgrade to LP again and bricked again;
used SFSTK again but serial # was now abcde... in bootloader so I used Asus Flash Tool again. AFT never finished flashing a ROMand the phone was stuck on the bootloader screen with "Result: okay" so I just shut down the phone and left it off until I saw your post this morning.
Edit:
I set up the phone ran software update option from settings but the Android Version is 5.0? Also, when I boot into fastboot, I see the serial # as abcde... but I can get the proper serial # by pressing the volume up and down keys a few times. Lastly, my SD card is not seen in recovery but is seen in the ROM. When I boot to recovery from the bootloader, I see this:
Android system recovery <3e>
LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756_user
E:file path/tmp/last_install
E:file path /cache
E:file path /tmp
Finding update package
Opening update package
E: file path:/sdcard/MOFD_SDUPDATE.ZIP
E: failed to map file
SD installation aborted.
E: Installation failed with status 1
I'm not too worried as these things are cosmetic. The important thing is the phone now works
Just to clear things up.
You never bricked your device using the method in the OP regarding downgrading via sd card. So not to scare people off .
Mofd sdupdate method is for adb sideload using a cable.
In the video it shows how files must be written when downloaded for each stock firmware in file manager in the first few mins. To be recognised from ext sd
Lastly , 2.20 in firmware or raw = LP
4.21 = M which doesn't have a raw yet unless I missed it coming about
Hello,
I have followed the Canadian guide to rooting my LG G4 H81210N.
I was on MM when i opened my brand new LG G4, i successfully downgraded to 5.1 LP for my right carrier.
I have downloaded the rooted img file to flash via the LG ROOT kit, following the rooting guide.
When i reach go to flash my rooted img (4.2ish gb) it takes less than 5 minutes for it to return with the pound # sign to show its completed the flash. i type LEAVE, my phone reboots fine, and i open up a root checker and super su with no success of a root.
I have tried using my original carrier (wind) KDZ and rooted img file, with no successs.
I have tried using telus kdz and rooted img file with no success. (as all canadian variants are compatible as i've read.)
So i have no clue what i am doing wrong. the LG root kit i downloaded contains SUPERSU 2.46, should i download a newer version?
thanks again for your help.
Please somebody help me out !!! ill even let someone use TeamViewer to do it or watch from your end, i know im not doing anything wrong but i just cant figure out why its not working!!
when i go to flash the rooted img, it stays for about 3-4 minutes and gives me the # sign, i let it sit for another 20 min and then rebooted, still nothing. I even tried using an american rooted img file to brick my phone so i know atleast its flashing something, but i couldnt even get it bricked haha sounds stupid but i have been trying to root for 4 days today is the 5th day i am going crazy!!!!!!!!
Problem is likely in the rooted image you're installing ...
adoomie123 said:
Please somebody help me out !!! ill even let someone use TeamViewer to do it or watch from your end, i know im not doing anything wrong but i just cant figure out why its not working!!
when i go to flash the rooted img, it stays for about 3-4 minutes and gives me the # sign, i let it sit for another 20 min and then rebooted, still nothing. I even tried using an american rooted img file to brick my phone so i know atleast its flashing something, but i couldnt even get it bricked haha sounds stupid but i have been trying to root for 4 days today is the 5th day i am going crazy!!!!!!!!
Click to expand...
Click to collapse
Suggest you check out [Canadian Guide] - Complete Source for the LG G4 H812. Linux VM/Root/Tools&Files at: https://forum.xda-developers.com/g4/general/canadian-guide-complete-source-lg-g4-t3212449 and use one of the rooted images available there. It sounds to me that the image you've been using either isn't rooted or has been rooted incorrectly.
I notice you have not posted on that site so it should be a good source of info for you.
Good luck, S.
I have LG G8 Alexa variant. Model LM-G820QM.
I think ts on latest firmware "qm21e". Right now I live in India so the VoLTE is not working. I tried to cross-flash it to Open firmware but LGUP gave error "Cant change the device(AMZ_US > OPEN_US)".
I have three questions.
Can I cross flash Korean firmware ?
And if so, will i get VoLTE working ?
And my G8 has 2 cams while the Korean varient has 3 cams. Will my cams work with Korean firmware ?
Thank you.
Do you by any chance still have the OPEN_US Firmware?
I've been looking everywhere for it but I can't find it.
Download LG Firmware for LG G8 ThinQ LMG820QM Android 10 Q kdz stock BPT Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-roms.com
--------
| Firmware Update Android 10 Q kdz stock AMZ Rom
Download Android 10 Q KDZ stock firmware for download with direct link
lg-firmware.net
I think any of this 2 are OPEN. If not then reply me back I will deep search on google. I happend to found it somewhere but can't remember where exactly.
Thanks for your reply
Unfortunately, neither one worked.
I tried the first one, however the flash tool didn't work because (OPEN_US_>NAO_US)
The second one would not download at all. I don't think it would have worked anyway since my phone is not the Alexa version. It's factory unlocked, purchased from Best Buy.
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
I see, but I just want VoLTE to work. I don't mind using stock rom or custom rom too. So keeping that in mind what do you suggest? And also, Do you think that your solution " I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root! " could work for me too ? If so do let me know how did you figured that NAO_US was actually OPEN_US. Maybe I can find out one for AMZ_US.
On the box Model : G820QM
SKU : G820QM8 (QM8 stands for AMZ)
Thank you.
I'm really not sure how VoLTE works internally, so I couldn't tell you if using another firmware would actually work for you - but the way I found out one of the firmwares was actually OPEN_US was by extracting it using the KMZ extractor tool someone made. This is how I was able to reflash the partition on my phone that I screwed up on in the first place and created a brick with. Like I said, you could manually reflash all those partitions one-by-one in QFIL, but i don't recommend it as it may not even work and could potentially brick your device. It's really up to you in this case, if you'd like to try though:
Download the firmware you want to try, search for KZM extractor on Google, download QFIL and all of it's prerequisites, and finally the firehose.
Use the KZM extractor and place the firmware inside of it.
Once it is done extracting all the files, put your phone into download mode and open QFIL
NOTE: DO NOT FLASH THE PARTITIONS WITH 'OP' IN THEM! Your phone won't boot for sure!
From QFIL use the firehose file and manually, one by one, sort through the output files of the KZM extractor and find the partitions that match their name and flash them with the file.
Zero guarantees this will work, and you may end up with a brick for a phone at the end of the day, but if you're that desperate it just might work.
Hi there.
I am still looking for solutions for VoLTE to work. I googled a lot and came on this post " https://piunikaweb.com/2021/06/07/unlocked-lg-g8-thinq-now-supports-att-volte-after-april-update/ "
Mine is Amazon version "QM8". Yet I did received april update via OTA. But still no VoLTE. I can OEM unlock from devs. Can I flash AT&T "QM7" on Amazon "QM8" ?
What do you think of this please let me know.
Thank you
VoLTE seems to depend on files in the OP partition, so crossflashing other partitions but not OP will not get VoLTE to work. LGUP will not allow crossflashing.
See my experience to get working VoLTE and Wifi Calling: https://forum.xda-developers.com/t/lg-g8-volte-fix.4113291/post-85455109
You will need to be bootloader unlocked and rooted.
awgybop1 said:
Hey man, I was able to figure out my problem! Not only that, I discovered one of the NAO_US Firmwares was actually OPEN_US, and that worked for my phone. I am now back up and running, with an unlocked bootloader and Root!
I appreciate your help, and I want to help you if I can.
As for the cross-flashing, you can't do it via LGUP. The only possible way is to download the firehose for your phone and to use the Qualcomm Image Flash Loader(QIFL) tool. You can extract the firmware you want to flash, and load all the images into the QIFL partition manager. There is no guarantee your phone will boot from it, but you can try it. NOTE: Do NOT modify the OP partitions! This will cause your phone to throw an OPID mismatch error and it won't boot!
As for the cameras, you may be able to extract the current Camera APK from your phone and install that on the Korean firmware so that you are still able to use them. No guarantee this will work, and they might work fine with the Korean camera APK, but it's worth doing before you flash.
Click to expand...
Click to collapse
Pls how to extract kdz,mine get error bad header