Hey guys,
Does anyone know how we can get the rollback number on our devices? I was reading this thread here:
http://forum.xda-developers.com/g4/...wngrade-g4-t3197675/post62748057#post62748057
I guess you need to know your rollback number to do a KDZ becasue there is a chance of a hard brick. I tried the numbers highlighted below but it didn't work for Verizon. Anyone know how we could get this information?
waylo said:
This was not written anywhere specifically on the LG G4 forums that I could find. But every flash-addict needs to be warned. It is something you want to know before you continue tinkering.
Several users (myself included) have made the unfortunate mistake of attempting to downgrade their bootstack (for various reasons) to a former version.
DO NOT DO THIS (at least for the USA T-Mobile H811 version, and possibly other USA versions, per @autoprime)! It will result in a hard brick! Specifically, this results in the "Qualcomm QDLoader HS-USB port ( 9008 )" error. Connecting your phone to a PC will pop up with this active connection, but nothing else. There is no download mode. There is no publicly available fix as of yet.
This WILL happen both through KDZ restore as well as flashing bootstack .zips.
Yes, an official KDZ image can BRICK your USA phone, if you try to rollback.
This is in stark contrast to other manufacturers (i.e. Samsung), where the attempt to flash an older bootloader/modem/radio will simply fail, but your phone is not bricked.
I have conferred with @autoprime, who confirmed that with each OTA firmware release (on T-Mobile it was 10H, and now 10N), the version # increments. Flashing a lower version # will result in brick.
I have searched far and wide for a DIY fix. Without the proper firmwares in the right format, as well as the right flashing software, your phone is done and must be sent in for LG repair.
To check what antiroll-back version you are on, input this sequence in the dialer (T-Mobile and ATT) and scroll down:
*#*#244773825625#*#*
Flashing a bootstack version less than this # (through KDZ or zip) will brick the phone. You are free to flash anything equal or higher than the version listed.
Click to expand...
Click to collapse
sefirosu0522 said:
Hey guys,
Does anyone know how we can get the rollback number on our devices? I was reading this thread here:
http://forum.xda-developers.com/g4/...wngrade-g4-t3197675/post62748057#post62748057
I guess you need to know your rollback number to do a KDZ becasue there is a chance of a hard brick. I tried the numbers highlighted below but it didn't work for Verizon. Anyone know how we could get this information?
Click to expand...
Click to collapse
If you are still on the original software version 10b, then you have v0. If you took the OTA (or flashed the KDZ) to 11a, then you have v1.
We have a new OTA out now, 12a. I'm not sure what version that one is, but I'm willing to bet it is v2, and you will not be able to rollback if you install it.
laurasaurisrex said:
If you are still on the original software version 10b, then you have v0. If you took the OTA (or flashed the KDZ) to 11a, then you have v1.
We have a new OTA out now, 12a. I'm not sure what version that one is, but I'm willing to bet it is v2, and you will not be able to rollback if you install it.
Click to expand...
Click to collapse
Yeah right now I'm stuck with 11A and I'm not sure what I should do. Even though my phone sucks the way it runs, I'm gonna hang in there and wait a couple weeks. See what comes out of 12A.
Well I don't believe there is a way to check or there is a known way of finding it yet. Apparently there is an APK app that reads it. Perhaps we can rip it from another rom and access the APK via the same method we do for accessing the Themes (using a launcher to do custom shortcuts).
The inability to KDZ back to original software is ridiculous. Just like 12A and the broken notifications. How stupid is it to force broken updates yet make it impossible to go back to previous backup/software. I am half tempted to just take the 12A update and force Verizon to give me another phone just to emphasize my dislike for their method of locking the system down.
Okay, a brief history.
I have an h818p, bought here in the Philippines. I wanted MM and it was taking a while to roll out here so I used the LGUP method and flashed a Russian 20c kdz into my phone. It ran okay but had some trouble with data connections.
I finally had some time to see if I can fix it so I decided to run the 20D euro into the phone and got some error so I ended up doing a factory reset. My data works perfectly now and everything is up, the only problem I have is that every single time I boot my phone I get this error.
I tried looking as to its meaning and I think it has something to do with the wrong kernel being in my phone or something like that.
Now if anyone can please help me, find a solution. I originally wanted to flash a kdz from the Philippines but the only one I could find was 10l. Now that the errors been popping up I cant get my LGUP to read my phone properly (it wont even let me set a kdz, its asking me to find a .tot file)
Now Im wondering if I can use the LG Flash Tool to flash the 10l philippine version and if this will help. I dont want to experiment anymore only to brick my phone.
: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
but I figured it wouldn't hurt to ask around.
I picked up this phone cheaply off Ebay and after a few months the lack of root was really starting to tick me off as I really don't like feeling like a guest on my own device. When I first looked into rooting the device I'd found it was essentially impossible with my particular model of G4 for various reasons, despite that my frustration lead me to blindly following one of the first results I got when googling "LG G4 H810 root guide" which ended with catastrophic results.
The step I followed which killed my phone involved me rolling back the firmware to an older version using LGUP. Now, I knew that the firmware installed on the device had antirollback 3, and the firmware that I was flashing my device with had antirollback 2 and attempting to flash the device could lead to bricking... I don't know why I did it, but I did, I suppose I just had a hard time believing that official firmware installed with official software could break the device permanently.
After I installed the older firmware the device's screen turned off and it hasn't turned back on since. Entering recovery and download mode worked before, but after the attempted rollback the key combos used to get into those modes get no response from the device whatsoever. The only sign of life is that is appears as "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" under Linux when plugged in to USB.
I was recommended this method of unbricking on reddit: https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946 However that method seems to require KDZ file which matches my device which unfortunately I can't find anywhere.
I suppose I could try the above method but with a KDZ file for a different model of G4, but that seems like a rather poor idea. I suppose the device already isn't working, not like it can get any worse than that, right?
Any other unbricking methods out there? Anyone out there got a KDZ file for the H810? Am I stupid or something? (Well, I already know the answer to that one.)
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