Hello,
I was using CM13 but then decided to downgrade to 4.4 EU stock. Here are steps I did:
1) http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
2) I flashed XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF
Everything went fast and smooth except one thing - screen is flickering after downgrade and after flashing stock ROM. I guess this is a bootloader issue that came with CM13. What to do with this?
[edit] I have checked my bootloader version:
adrian$ ./osx-fastboot getvar version-bootloader
version-bootloader: 4118
finished. total time: 0.001s
Click to expand...
Click to collapse
Hi,
Is this flickering disappear when you put your phone in stand by mode once and turn it on one more time?
If answer is yes,highly suggest you to leave it like it is... It's your bootloader, it's a highest version that's needed by 4.4.4.
Trying to downgrade your bootloader is almost surely a good way to brick it...
Thanks for your response.
Yes - they happens randomly - mostly after phone reboot then they goes away. By the way - my bootloader 41.18 seems to be the lowest version available and from what I read shouldn't cause flickering on 4.4
I discovered a forum pertaining to the G5 a few days ago for methods of rooting the device (http://forum.xda-developers.com/tmob...-h830-t3384526). To the best of my abilities, I believe I followed each step correctly. After I used the LGUP tool to install the file while the device was in download mode, it began boot-looping on the initial boot screen with an error message displaying "boot verification failed". I found a post on the same forum from someone who was experiencing the same error on their device. Tungkick posted a response that provided a solution to the issue; "IF Boot Verification Failed error > download stock full flash again>> enabable usb debugging + oem unlock> adb reboot bootloader> fastboot oem unlock> then up file tot add twrp again." I downloaded the stock file and used LGUP to flash it to the device.
I believe I made the mistake of selecting "upgrade" instead of "refurbish" before I initiated the flash. When the file finished installing, the screen on my device went black. Since then, I've been incapable of booting my phone up. When I connect it to my laptop, the Device Manager reads it as: "Qualcomm HS-USB QDLoader 9008". I researched some methods but wasn't successful in finding one that fixed my phone. Although, I could've found a site that provided a solution but I might've failed to follow the instructions properly. I assure you I gave my best effort to fix this issue myself, but I'm desperate to seek help from anyone at this point.
I would sincerely appreciate any feedback that would assist in resolving this issue. Here are the Web addresses:
(1) http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
(2) http://www.androidbrick.com/unbrick-...-qhsusb_dload/
(3) http://www.androidbrick.com/ultimate...oad_qpst_qfil/
Unfortunately your phone is done. None of those links work for the G5, or the G4 even.
If you purchased it from a retailer, send it to LG for a warranty replacement. Be 'mysterious' and ignorant about how it happened. Will take about 1.5 weeks to get it back. They just reflash the phone and you're as good as before. Or, show it to T-Mobile and they will send a refurbished replacement out, for either $5 or $20, depending on your phone insurance.
It's quite odd that this happened according to your description. From your profile, you have the H830, right? Do you know if you were on 10A or 10D?
From the beginning, did you select OEM unlock in Android developer settings, and then unlock the bootloader? If not, that will lead to that type of error you got. The instructions are all over the place and the tutorials are not always as complete as they should be.
I don't think refurbish vs upgrade makes a difference--one will wipe the /data, the other won't. If you have the right stock KDZ file, LGUP (you used LGUP, not LGFlash right?) will simply return you to stock so you can try again.
That error occurs if you try to flash an older firmware version OR flash a different model KDZ. Neither of those should occur with LGUP as it has safeguards.
waylo said:
Unfortunately your phone is done. None of those links work for the G5, or the G4 even.
If you purchased it from a retailer, send it to LG for a warranty replacement. Be 'mysterious' and ignorant about how it happened. Will take about 1.5 weeks to get it back. They just reflash the phone and you're as good as before. Or, show it to T-Mobile and they will send a refurbished replacement out, for either $5 or $20, depending on your phone insurance.
It's quite odd that this happened according to your description. From your profile, you have the H830, right? Do you know if you were on 10A or 10D?
From the beginning, did you select OEM unlock in Android developer settings, and then unlock the bootloader? If not, that will lead to that type of error you got. The instructions are all over the place and the tutorials are not always as complete as they should be.
I don't think refurbish vs upgrade makes a difference--one will wipe the /data, the other won't. If you have the right stock KDZ file, LGUP (you used LGUP, not LGFlash right?) will simply return you to stock so you can try again.
That error occurs if you try to flash an older firmware version OR flash a different model KDZ. Neither of those should occur with LGUP as it has safeguards.
Click to expand...
Click to collapse
Yeah, I was on 10D. OEM unlock and USB debugging were enabled; the bootloader was unlocked, as well. This is all a mystery to me, honestly. I've never experienced an issue like this before. I appreciate you taking the time to help
Hmm, weird scenario then, as it seems like everything went exactly the way it was supposed to. Good luck with the replacement, it's not that hard, just annoying.
If you're happy with the G5 you have, send it through LG. If you'd prefer to get it a tad sooner and don't mind playing the refurb lottery, go through T-Mobile.
waylo said:
Hmm, weird scenario then, as it seems like everything went exactly the way it was supposed to. Good luck with the replacement, it's not that hard, just annoying.
If you're happy with the G5 you have, send it through LG. If you'd prefer to get it a tad sooner and don't mind playing the refurb lottery, go through T-Mobile.
Click to expand...
Click to collapse
Thanks, man. Take care
If your bootloader was unlocked already then you should have twrp still, try booting into that with a button combo or thru adb terminal you'll need a file called no dm-verify zip witch you can find on the fourms, be sure to wipe your caches as well. I believe this is your problem is you may have forgot to flash this and that's why your not booting. And I would try to flash the 10d fluence ROM as well and follow his instructions on how to do so it may solve your boot loop and you won't have to wait for another phone.
I made a stupid mistake trying to flash a H850 build on H830 devices via TWRP.
I ended up with a dead device with 9008 driver communication only. Now, I've managed to get MSM8996 programmer file in order to flash bootloaders back to the device via QPST utility and all I'm missing is rawprogram0.xml file that contains the exact start_byte_hex values of each one of the bootloader files in order to be successfully downloaded to the phone.
I would highly appreciate some help from anyone with a rooted LG G5 to get the exact start_byte_hex of each one of the phone's partitions in order to build my own rawprogram0.xml file or alternatively just get the complete LG G5 rawprogram0.xml file from someone who already have his hands this file
I'll post here all revive steps and tools used once I'll have all files needed and get a successful revive results on my device.
Crossdead said:
If your bootloader was unlocked already then you should have twrp still, try booting into that with a button combo or thru adb terminal you'll need a file called no dm-verify zip witch you can find on the fourms, be sure to wipe your caches as well. I believe this is your problem is you may have forgot to flash this and that's why your not booting. And I would try to flash the 10d fluence ROM as well and follow his instructions on how to do so it may solve your boot loop and you won't have to wait for another phone.
Click to expand...
Click to collapse
Dude, I concur with your method entirely haha.
I wanted to root my phone and install a custom recovery simultaneously (idiotic decision, I guess). So I just waited until someone posted a forum with the files that were compatible for the G5's most recent update. Ironically, the files didn't install properly or something, so my phone went into a bootloop. The same developer who posted that forum with the root and recovery files, provided a solution to the issue. Which was, initially, flashing the stock files to the device, then proceed with installing the root/recovery files.
I then flashed the stock files to the device and simultaneously at completion, my phone powered off. Still, my phone is incapable of communicating with my laptop because something is wrong with the drivers on the LG and I've only been able to find outdated and ineffective solutions for it. Thank you for lending a hand though, man. If you have any alternatives, please let me know.
motman said:
I made a stupid mistake trying to flash a H850 build on H830 devices via TWRP.
I ended up with a dead device with 9008 driver communication only. Now, I've managed to get MSM8996 programmer file in order to flash bootloaders back to the device via QPST utility and all I'm missing is rawprogram0.xml file that contains the exact start_byte_hex values of each one of the bootloader files in order to be successfully downloaded to the phone.
I would highly appreciate some help from anyone with a rooted LG G5 to get the exact start_byte_hex of each one of the phone's partitions in order to build my own rawprogram0.xml file or alternatively just get the complete LG G5 rawprogram0.xml file from someone who already have his hands this file
I'll post here all revive steps and tools used once I'll have all files needed and get a successful revive results on my device.
Click to expand...
Click to collapse
Same here, man! I thought I was so close to fixing it but the QPST tool would always display an error indicating that there was an issue with the rawprogram0.xml file. I don't believe I used MSM8996 programmer file, though... Would you mind posting a link of the download, please? Thank you for posting.
Colbyfales_25 said:
Same here, man! I thought I was so close to fixing it but the QPST tool would always display an error indicating that there was an issue with the rawprogram0.xml file. I don't believe I used MSM8996 programmer file, though... Would you mind posting a link of the download, please? Thank you for posting.
Click to expand...
Click to collapse
Here you go, I guess that you will have to use the lite version
https://www.mediafire.com/?epv3qq83ag2vqar
motman said:
Here you go, I guess that you will have to use the lite version
https://www.mediafire.com/?epv3qq83ag2vqar
Click to expand...
Click to collapse
I found a way to create the required rawprogram0.xml and patch0.xml files from a working phone via Python script.
Python should be installed on your computer in order to run this tool. All we need is someone with a working phone who will be willing to run this tool and create the required files...
Tool:
https://www.mediafire.com/?jh2owbccrfj6rne
Script description:
http://forum.xda-developers.com/showthread.php?t=1884417&page=2
motman said:
I found a way to create the required rawprogram0.xml and patch0.xml files from a working phone via Python script.
Python should be installed on your computer in order to run this tool. All we need is someone with a working phone who will be willing to run this tool and create the required files...
Tool:
https://www.mediafire.com/?jh2owbccrfj6rne
Script description:
http://forum.xda-developers.com/showthread.php?t=1884417&page=2
Click to expand...
Click to collapse
I'm on it. I'll keep you apprised throughout the process.
Colbyfales_25 said:
I'm on it. I'll keep you apprised throughout the process.
Click to expand...
Click to collapse
Cool
Colbyfales_25 said:
I'm on it. I'll keep you apprised throughout the process.
Click to expand...
Click to collapse
Ever get a chance to make any progress with this?
SophiaNOTLoren said:
Ever get a chance to make any progress with this?
Click to expand...
Click to collapse
Unfortunately, no. I had access to Ubuntu's OS but wasn't successful finding another G5. Theoretically, using the Python rawprogram0.xml and patch0.xml scripts, along with an operable G5, It's plausible to recover the phone. I essentially just went into a retail store and told them that the phone had spontaneously shut-off and wouldn't reboot. They provided a replacement and that was the end of it.
So i got on of these but sprint model well g5
i have a full dump from before my phone bricked
but not through the script from lgups partition dump how can i push these back to mine or make a partition xml from my dump or even a sdcar debrick img? lol Im not picky any of these would suit me. lol Not askin to much
Colbyfales_25 said:
Unfortunately, no. I had access to Ubuntu's OS but wasn't successful finding another G5. Theoretically, using the Python rawprogram0.xml and patch0.xml scripts, along with an operable G5, It's plausible to recover the phone. I essentially just went into a retail store and told them that the phone had spontaneously shut-off and wouldn't reboot. They provided a replacement and that was the end of it.
Click to expand...
Click to collapse
Ah, that's a shame. I bought mine on eBay, and I'm on Metro not TMobile proper, so sadly that avenue's not much use for me.
for UFS Chip only can use Nuprog to rewrite full flash to chip direct or use cm2 dongle with Open memory tool plugin and can flash it in 9008 port
Device Found!
Initialize ...
Handshake passed!
BB_IDC_CPU : SnapDragon 820 [MSM8996]
ID_BLOCK_S : B861DCBB
ID_BLOCK_I : 009470E1
ID_BLOCK_E : 2A703DB9
ID_BLOCK_L : C4CF6F2386EC1D32B0AF58AB5E37F2A3
ID_BLOCK_L : 527BBE85A099E0CC4DA13129613BB67A
Pickup loader from firmware package
Loader Sent! Initializing ...
Running FireHose on BBID : MSM8996 , FLASH : UFS , mVER : 1
ExtInfo : 0x0000C000/0000C000/00001000/00001000/00001000
UFS Device : SAMSUNG KLUCG4J1CB-B0B1 0800
UFS SectSize : 0x1000
UFS LU0 Size : 0x00000007602F0000 : 29,50 GiB
--------------UFS Device Info--------------
UFS Total Active LU: 0x6
UFS wManufacturerID: 0x1ce
UFS Boot Partition Enabled: 0x1
UFS LU Write Protect: 0x0
UFS Boot LUN ID: = 0x0
UFS Memory Type: 0x0
UFS LU Total Blocks: 0x0
UFS Supported Memory Types: 0x800f
UFS LUN Enable Bitmask: 0x3f
UFS bConfigDescrLock: 0x0
Boot Ok!
Flash Chain : 74
Flashing now
Flashing : persist.img
Flashing : cache.img
Flashing : devcfg.mbn
Flashing : devcfg.mbn
Flashing : dynamic_nvbk.bin
Flashing : reserve1.bin
Flashing : reserve2.bin
Flashing : config.bin
Flashing : userdata.img
Flashing : gpt_main0.bin
Flashing : gpt_backup0.bin
Flashing : xbl.elf
Flashing : gpt_main1.bin
Flashing : gpt_backup1.bin
Flashing : xbl.elf
Flashing : gpt_main2.bin
Flashing : gpt_backup2.bin
Flashing : gpt_main3.bin
Flashing : gpt_backup3.bin
Flashing : rpm.mbn
Flashing : rpm.mbn
Flashing : tz.mbn
Flashing : tz.mbn
Flashing : hyp.mbn
Flashing : hyp.mbn
Flashing : sec.dat
Flashing : pmic.elf
Flashing : pmic.elf
Flashing : NON-HLOS.bin
Flashing : adspso.bin
Flashing : mdtp.img
Flashing : emmc_appsboot.mbn
Flashing : emmc_appsboot.mbn
Flashing : logo.bin
Flashing : boot.img
Flashing : boot_aging.img
Flashing : system.img
Flashing : recovery.img
Flashing : BTFM.bin
Flashing : keymaster.mbn
Flashing : keymaster.mbn
Flashing : cmnlib.mbn
Flashing : cmnlib.mbn
Flashing : cmnlib64.mbn
Flashing : cmnlib64.mbn
Flashing : apdp.mbn
Flashing : msadp.mbn
Flashing : gpt_main4.bin
Flashing : gpt_backup4.bin
Flashing : md5.img
Flashing : gpt_main5.bin
Flashing : gpt_backup5.bin
Click to expand...
Click to collapse
MA7MOD_GSM said:
for UFS Chip only can use Nuprog to rewrite full flash to chip direct or use cm2 dongle with Open memory tool plugin and can flash it in 9008 port
Click to expand...
Click to collapse
This is rather interesting. I have a working g5 (H830) and a bricked on stuck on qdloader mode.
Can you point me in the direction of reading the backup from the working one to resurrect the bricked phone?
Currently have access to Octoplus Jtag Pro box. I do have cm2 dongle as well.
Hit me up soon, i hope.
Best Regards
hiroprotagonist said:
This is rather interesting. I have a working g5 (H830) and a bricked on stuck on qdloader mode.
Can you point me in the direction of reading the backup from the working one to resurrect the bricked phone?
Currently have access to Octoplus Jtag Pro box. I do have cm2 dongle as well.
Hit me up soon, i hope.
Best Regards
Click to expand...
Click to collapse
Let’s start with cm2
MSM8996 & UFS & MemoryTool
-Connect Working H830 in edl mode by press down,up and connect usb setup Cm2 QLM driver
-Open Cm2QLM and chose Memory Tool
-Chose full files and Make read
-Connect dead H830 with memory tool and make restore readed files from first working h830
-Send Screen Shot
#MA7MOD_GSM
Hello i'm literally new here and im feeling pretty desesperated due to my dad Moto X XT1058 which i tried to fix a wifi problem, long story short: I made the huge mistake of downgrading(Android 5.1 to Android 4.4.4) and then installing an OTA update after that everytime the phone boots up it will boot in fastboot
This is what it says in order in red:
Downgraded security version
Update gpt_main version failed
failed to hab check for gpt_backup: 0x35]
CID Read Failure
Invalid CID status 0x69
CustomerID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
I tried RSDLite but it always gives error in step 2 and using while using command line (fastboot and mfastboot) it would give error saying "Access denied" Hope you guys can help me out and sorry for the bad english.
PC data:
OS: Windows 10 x64
RAM: 8GB DDR3
Graphic card: AMD Radeon R5 with 1gb of vram
Processor: Quad core AMD A8-6410 x4
Cheers!
StormTrooper_115 said:
Hello i'm literally new here and im feeling pretty desesperated due to my dad Moto X XT1058 which i tried to fix a wifi problem, long story short: I made the huge mistake of downgrading(Android 5.1 to Android 4.4.4) and then installing an OTA update after that everytime the phone boots up it will boot in fastboot
This is what it says in order in red:
Downgraded security version
Update gpt_main version failed
failed to hab check for gpt_backup: 0x35]
CID Read Failure
Invalid CID status 0x69
CustomerID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
I tried RSDLite but it always gives error in step 2 and using while using command line (fastboot and mfastboot) it would give error saying "Access denied" Hope you guys can help me out and sorry for the bad english.
PC data:
OS: Windows 10 x64
RAM: 8GB DDR3
Graphic card: AMD Radeon R5 with 1gb of vram
Processor: Quad core AMD A8-6410 x4
Cheers!
Click to expand...
Click to collapse
Greetings and welcome to assist. I think your issue is due to a locked bootloader, hopefully this thread here will help you recover your device
https://forum.xda-developers.com/showthread.php?t=2718031
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. I think your issue is due to a locked bootloader, hopefully this thread here will help you recover your device
https://forum.xda-developers.com/showthread.php?t=2718031
Good Luck
Sawdoctor
Click to expand...
Click to collapse
I flashed the firmware and now it works (it had to be the brazil one because i couldn't find the Mexico 5.1 ROM) now i can't connect to wifi everytime i try to turn it on it would turn off by itself neither i can turn on Bluetooth, when the phone was 4.4.4 i managed to make it work but then the OTA came and screwed everything:crying: already tried modifying the "Hosts" text file in /system/etc/ but it didn't worked.
Hope you can guide me throught this.
Edit: Thanks for the link!
StormTrooper_115 said:
I flashed the firmware and now it works (it had to be the brazil one because i couldn't find the Mexico 5.1 ROM) now i can't connect to wifi everytime i try to turn it on it would turn off by itself neither i can turn on Bluetooth, when the phone was 4.4.4 i managed to make it work but then the OTA came and screwed everything:crying: already tried modifying the "Hosts" text file in /system/etc/ but it didn't worked.
Hope you can guide me throught this.
Edit: Thanks for the link!
Click to expand...
Click to collapse
Unfortunately the bluetooth and wifi not turning on could be bootloader related, have you tried asking in the moto x forums ? They have the device so may be more help
sawdoctor said:
Unfortunately the bluetooth and wifi not turning on could be bootloader related, have you tried asking in the moto x forums ? They have the device so may be more help
Click to expand...
Click to collapse
I will try and ask them about this issue, i will comeback and report if there's any fix for this issue
Hi I hope you're fine. My Asus zenfone max fell in qualcom hs 9008 qloader. I struggled to release it by flashing the firmware open [firmware27] OPEN_ZC550KL_8916_V12.8.4.10_M3.1.25_20170228_V3.0.0.08. Everything went well after weeks of testing. Except that I lost both imei and the base band it marks "unkown". I tried to flash the raw firmware of asus to try to correct the problem, either with asus flash tool or with fastboot commands: flashall_AFT WW_ZC550KL_V13.8.26.15_M3.1.39_Phone-user.raw I still have the error "Failed! Raw do not exist! I tried all the raw available, I turn on 8916. I had to fall back on the firmware OTA UL-ASUS_Z010-WW-12.8.10.82-user from lolipop to marshmallow. I flashed them all via ota. The imei still does not come back. I tried to unlock the bootloader to be able to rewrite the imei via tutorials that require the root: failure. 8916_SIGNED_Android_M_UnlockTool_2016_0715 fails each time: "error that may be due to the network ..." it remains the option of the QCN file but I have not tried. How can I do to get the imei please? I had to look like crazy and having no issue I ask you humbly advice. Cordially. Sorry for my shabby English, I am a francophone.
Nas3 said:
Hi I hope you're fine. My Asus zenfone max fell in qualcom hs 9008 qloader. I struggled to release it by flashing the firmware open [firmware27] OPEN_ZC550KL_8916_V12.8.4.10_M3.1.25_20170228_V3.0.0.08. Everything went well after weeks of testing. Except that I lost both imei and the base band it marks "unkown". I tried to flash the raw firmware of asus to try to correct the problem, either with asus flash tool or with fastboot commands: flashall_AFT WW_ZC550KL_V13.8.26.15_M3.1.39_Phone-user.raw I still have the error "Failed! Raw do not exist! I tried all the raw available, I turn on 8916. I had to fall back on the firmware OTA UL-ASUS_Z010-WW-12.8.10.82-user from lolipop to marshmallow. I flashed them all via ota. The imei still does not come back. I tried to unlock the bootloader to be able to rewrite the imei via tutorials that require the root: failure. 8916_SIGNED_Android_M_UnlockTool_2016_0715 fails each time: "error that may be due to the network ..." it remains the option of the QCN file but I have not tried. How can I do to get the imei please? I had to look like crazy and having no issue I ask you humbly advice. Cordially. Sorry for my shabby English, I am a francophone.
Click to expand...
Click to collapse
Help
I'm a beginner at rooting and flashing and what not so after looking up and following (To my best efforts) guides on here and other sites as well, on flashing lineageOS on my phone and i may have read a step wrong and wiped my system data BEFORE i got the chance to make a twrp backup.. i've tried flashing the lineageOS rom anyways, and it must not have been the right version. I've searched probably 16 hours in the total in the past 3 days trying to find my stock firmware but cant seem to find it anywhere,
My info is:
product: htc_ocmdugl
version: 1.0
max-download-size: 1082400000
serialno: FA83K1E00528
slot-count: 0
current-slot:
imei: <Mod edit>
version-main: 2.15.709.1
boot-mode: download
version-baseband: 8998-200321-1905211056
version-bootloader: 1.0.0.0000
mid: 2Q4D10000
cid: HTC__621
Like i said, i cannot find my stock firmware and i'm not sure which, if any, custom firmwares would work or what version to download, i can still boot to twrp, my phone can only get to download mode, recovery mode and bootloader mode, other than that it's stuck in a bootloop,
If anyone has a firmware or knows what version of lineage i can use, please let me know, it's probably the most i've spent on a smartphone, and i just tried to make it my own and failed, at my own cost...
Any help or tips would be greatly appreciated!!!
I live in canada and paid for the phone through carrier so i'm not sure what applies to my phone, as in "United States, Europe, Asia" i see theres multiple versions but not sure where mine fits in...
@Chef_BOYRD I've removed the IMEI from your OP but feel free to re-insert it if you deem it necessary. Please be aware that it's clearly suggested not to publicly post the IMEI or to share it. It's not required for anything but your IMEI could easily misused, and I'm convinced you wouldn't enjoy that.
Regards
Your friendly neighbourhood watch.
Chef_BOYRD said:
Like i said, i cannot find my stock firmware
Click to expand...
Click to collapse
Stock firmware for Taiwan CID_621 you can find here
You can try LineageOS 16.0 GSI from AndyYan or other GSI firmware.