After spending 2 days and trying and trying I finally got the solution. The smartphone in the sticker under the battery has model number "h901" but I think that for one reason or other it's "h900" that's why we will treat it like "h900" and I will tell you how to flash even if model is different. Make sure you have vs990 motherboard model(it will take you 5 minutes remove the screws and verify). First of all download:
Firmware: https://lg-firmwares.com/downloads-file/3862/WEB_H90021w_00_0921.kdz.
LGUP: http://oceanhost.eu/dl959drhehp3/LGUPV10.rar.htm
Uppercut(you will need this if you have problems opening LGUP: https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Software to extract "dz" file from "kdz" file(this will allow you install any firmware on different model number): https://dl.xda-developers.com/3/1/3....zip?key=uWmelyLw3rVRER88X_xl3A&ts=1548509744
Steps:
1) if you have the smartphone in qualcomm mode then follow this guide until step 6: https://forum.xda-developers.com/verizon-lg-v10/help/lg-vs990-unbrick-via-qfil-t3739299
2) Open WindowsLgFirmwareExtract software, on "kdz file" section click "open" and look for WEB_H90021w_00_0921.kdz file you downloaded, check h90021w00.dz file and click "extract KDZ file" wait for the process(you will find the file if you click again "open", just cut it and paste it on desktop)
3)Now you should be in download mode, open Uppercut and then it will open automatically LGUP.
Check UPGRADE and in file path select dz file you pasted in desktop. Wait process end you should have booted your LG V10!
Marshamallow firmware has bugs. Fingerprint for example doesn't work. But this is the only way you can boot up you phone.
If you want to thanks me and you speak spanish or italian you can check my videos on youtube about smartphones:
https://www.youtube.com/channel/UCv3x_-ozakd_80ZS7jdv18A?view_as=subscriber
Some of them are subbed in eglish.
Thank you!
I will to try
NO! DONT!
This fw is disaster! This will bring many problems to the phone and there's no way out yet unless (as claimed) you pay $150.
Please check AT&T V10 forum, you'll see many thread about this H90021w. Better find another way to fix your phone.
ardian1899 said:
NO! DONT!
This fw is disaster! This will bring many problems to the phone and there's no way out yet unless (as claimed) you pay $150.
Please check AT&T V10 forum, you'll see many thread about this H90021w. Better find another way to fix your phone.
Click to expand...
Click to collapse
Sure, but if you want switch on your phone from bricked and you can't pay or you don't want pay $150 it's a good solution. How can you make a disaster switching on a bricked phone? From what I saw, there is no solution asaid pay money, so if people don't use and don't want to pay money this can be a good solution to unbrick it, for example myself. Am I wrong?
Argenis_jbc said:
Sure, but if you want switch on your phone from bricked and you can't pay or you don't want pay $150 it's a good solution. How can you make a disaster switching on a bricked phone? From what I saw, there is no solution asaid pay money, so if people don't use and don't want to pay money this can be a good solution to unbrick it, for example myself. Am I wrong?
Click to expand...
Click to collapse
Still wrong, sorry.
There's another way to unbrick the phone.
Just find a patched LGup and ask for help to any H901 user to dump their partitions (not included modemst1, modemst2, fsb, cache, and userdata). You'll have your phone running again, assuming the ARB didn't mod the board yet.
Still, your good intention is appreciated.
ardian1899 said:
Still wrong, sorry.
There's another way to unbrick the phone.
Just find a patched LGup and ask for help to any H901 user to dump their partitions (not included modemst1, modemst2, fsb, cache, and userdata). You'll have your phone running again, assuming the ARB didn't mod the board yet.
Still, your good intention is appreciated.
Click to expand...
Click to collapse
Thank you but if you have the solution, why didn't you publish it?
EDIT: the phone I unbricked was already updated to marshamallow
Argenis_jbc said:
Thank you but if you have the solution, why didn't you publish it?
Click to expand...
Click to collapse
I just really found this LGup patched things a few days ago albeit it's already around for sometimes in here XDA. Usually I'm using a Medusa Pro box flashing to revive the phone and I think it's not really applicable for many..
I havent really use this LGup patched but from what I read, we can restore partitions using it..
Ah I just realize if it's not possible to restore using LGup patched if the phone is bricked, because it needs a download mode. Instead we can restore partitions using Qfil. The mbn and xml file can be found in here XDA.
---------- Post added at 04:12 AM ---------- Previous post was at 04:10 AM ----------
Argenis_jbc said:
Thank you but if you have the solution, why didn't you publish it?
EDIT: the phone I unbricked was already updated to marshamallow
Click to expand...
Click to collapse
Yes, marshmallow and there's no way back from there.
The only solution I can think of is to find a H90021z or H90022b user which kind enough to share his/her phone's partitions. If you can find one, I can provide the XML and MBN file.
ardian1899 said:
I just really found this LGup patched things a few days ago albeit it's already around for sometimes in here XDA. Usually I'm using a Medusa Pro box flashing to revive the phone and I think it's not really applicable for many..
I havent really use this LGup patched but from what I read, we can restore partitions using it..
Ah I just realize if it's not possible to restore using LGup patched if the phone is bricked, because it needs a download mode. Instead we can restore partitions using Qfil. The mbn and xml file can be found in here XDA.
---------- Post added at 04:12 AM ---------- Previous post was at 04:10 AM ----------
Yes, marshmallow and there's no way back from there.
The only solution I can think of is to find a H90021z or H90022b user which kind enough to share his/her phone's partitions. If you can find one, I can provide the XML and MBN file.
Click to expand...
Click to collapse
Step 1 is useful to revive phone into Download mode man, from Qualcomm mode to Download mode.
Argenis_jbc said:
Step 1 is useful to revive phone into Download mode man, from Qualcomm mode to Download mode.
Click to expand...
Click to collapse
One very important thing.
Once you boot using that firmware, H90021w, the board will be modified.. it's fuse or anything like that will be modified and there's no way to revert back even to the original firmware which was working on the board.
I did an experiment, at one point I have 2 H900 boards. Both are booting fine. On one phone it's 5.1, on another phone it's H90021w with all it issues. I swap the EMMC from 5.1 phone to H90021w, it's not booting no matter how many time I try. Then I put the EMMC back to the 5.1 board, it's booting perfectly. Mind you, I didn't put the EMMC of H90021w board to the other board as it will ruin it.
So ARB is a hardware state, not just software. And you can't going back due to this.
Hi greeting from Malaysia, 1st for all I'm sorry for my bad english.
Recently I managed to unbrick my LG V10, originally it was H901 T-Mobile, android 5.1.
1. I use QFIL to unbrick the phone. Use the files (H90021w Unbrick-Qfil.zip) designed for H900 (download somewhere from xda, I already forgot the link because too many try & error. It took me 5 days to figure out on how to unbrick my phone).
2. Then I use WindowsLGFirmwareExtract-1.2.5.0-Release to extract the kdz file to dz.
3. After that rename the .dz file to .tot . Use WinHex to edit the file, search word H900 and change to H901 because LG UP detected my device as H901. Save & change back the file from .dot to .dz
4. Lastly use LG UP, choose upgrade... done! LG V10 is back to life.
As mention before, due to vs990 motherboard, you will accouter some minor issue like finger print, cannot uninstall apps (but you can hide it by using ADB command).
After upgrade to Marshmallow, the performance seem better. Previously there are some lag. No issue with camera, in fact the performance is better (snap faster). Now I use LG V10 as my secondary phone & for content creation. I love the camera, you can't find the features from any latest mid range smartphone.
*Don't give up.
Regards,
Afif
QuickZero said:
Hi greeting from Malaysia, 1st for all I'm sorry for my bad english.
Recently I managed to unbrick my LG V10, originally it was H901 T-Mobile, android 5.1.
1. I use QFIL to unbrick the phone. Use the files (H90021w Unbrick-Qfil.zip) designed for H900 (download somewhere from xda, I already forgot the link because too many try & error. It took me 5 days to figure out on how to unbrick my phone).
2. Then I use WindowsLGFirmwareExtract-1.2.5.0-Release to extract the kdz file to dz.
3. After that rename the .dz file to .tot . Use WinHex to edit the file, search word H900 and change to H901 because LG UP detected my device as H901. Save & change back the file from .dot to .dz
4. Lastly use LG UP, choose upgrade... done! LG V10 is back to life.
As mention before, due to vs990 motherboard, you will accouter some minor issue like finger print, cannot uninstall apps (but you can hide it by using ADB command).
After upgrade to Marshmallow, the performance seem better. Previously there are some lag. No issue with camera, in fact the performance is better (snap faster). Now I use LG V10 as my secondary phone & for content creation. I love the camera, you can't find the features from any latest mid range smartphone.
*Don't give up.
Regards,
Afif
Click to expand...
Click to collapse
Bravo!, what WinHex version have you used?
I use Win Hex 19.6.
I think any version can be use.
QuickZero said:
3. After that rename the .dz file to .tot . Use WinHex to edit the file, search word H900 and change to H901 ......
Click to expand...
Click to collapse
Hi, I'm in this part. But I have a question when LGH90021W appears, should I also change it to LGH90121W?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now I get this:
joranto said:
Hi, I'm in this part. But I have a question when LGH90021W appears, should I also change it to LGH90121W?
Click to expand...
Click to collapse
No need. Just change the 1st one.
---------- Post added at 03:30 PM ---------- Previous post was at 03:22 PM ----------
joranto said:
Now I get this:
Click to expand...
Click to collapse
Your QFIL folder should contain:
1. aboot.bin
2. boot.bin
3. gpt_backup0.bin
4. gpt_main0.bin
5. grow.bin
6. hyp.bin
7. laf.bin
8. patch0.xml
9. pmic.bin
10. prog_emmc_firehose_8992_lite_lge1
11. rawprogram0.xml
12. rpm.bin
13. sbl1.bin
14. sdi.bin
15. tz.bin
*the name may be different base on the "patch0.xml"
Total folder size: 76.7MB
QuickZero said:
No need. Just change the 1st one.
---------- Post added at 03:30 PM ---------- Previous post was at 03:22 PM ----------
Your QFIL folder should contain:
1. aboot.bin
2. boot.bin
3. gpt_backup0.bin
4. gpt_main0.bin
5. grow.bin
6. hyp.bin
7. laf.bin
8. patch0.xml
9. pmic.bin
10. prog_emmc_firehose_8992_lite_lge1
11. rawprogram0.xml
12. rpm.bin
13. sbl1.bin
14. sdi.bin
15. tz.bin
*the name may be different base on the "patch0.xml"
Total folder size: 76.7MB
Click to expand...
Click to collapse
Yes,....
What am I doing wrong?
joranto said:
What am I doing wrong?
Click to expand...
Click to collapse
Did you selected xml files? Did you verified phone model number?
Argenis_jbc said:
Did you selected xml files? Did you verified phone model number?
Click to expand...
Click to collapse
Yes, LG V10 H901 with VS990 motherboard
joranto said:
Yes, LG V10 H901 with VS990 motherboard
Click to expand...
Click to collapse
Have you tried another port? Write me a private message to help you
Hi guys, it worked with the suggestion to change port, there the images
---------- Post added at 09:54 PM ---------- Previous post was at 09:52 PM ----------
But I have stayed here. What do I do now?
Related
[CENTER]Common Questions and Problems KDZ Method:
1.Network connection error is NORMAL, move the window over and you'll see its actually most likely flashing
2.If your getting errors when doing the kdz method and running a custom rom that could be the problem and you'll need to use the TOT method.
3. Getting connection errors? Check under device manager to make sure you see LG something related under communication ports (Windows 8/10 ports might be hidden)
Make sure your using a USB 2.0 port!! USB 3.0 will NOT work.
Common Questions and Problems TOT Method:
If having an issue try and choose Board_ID on the TOT/DLL selection screen.
Make sure you've set your COM port to COM41
If device does not start flashing besure you unplug and replug the device
Make sure your using a USB 2.0 port!! USB 3.0 will NOT work.[/CENTER]
Here are all the current KDZ files for flashing Your G2 Back to Stock, I have updated the Link below with the AT&T, T-Mobile, Verizon,Sprint, and Korean, Asia, Pretty much of all them now!. READ!!! The first Guide Below is to Return To STOCK For ALL Varrients!! EXCEPT for the AT&T Please read below for the steps to return to stock on AT&T
NOTICE! - IF you download fails or does not download all the way USE A DOWNLOAD MANAGER!, Files that are usually over 1GB browsers have issues downloading them espseically if you have a slow connection.
First Off Not Responsible if you flash the wrong one!!!!
Please Check to make sure you don`t flash a 16GB firmware on an 32GB device. Please check the file names if they have an "16GB" in the File Name
THIS Guide Below for All Versions EXCEPT the AT&T Version (For AT&T & Sprint Scroll Down more)
How to flash ROM KDZ Method
First off I`d like to THANK @quangnhut123 for making a new way & easy way to flash the KDZ Method!!
The Files are Hosted on my server for fast speeds! Most if not all NEEDED KDZ files are on my Server
1). Download all The Files Below!
1) Firmware Files - HERE!
Or Here LGKDZ.com for your exact match KDZ for your model
2) Download LG Drivers - LG Drivers Here - 10.9 Mb
2.1)Verizon Drivers (Verizon Only)LG_VZW_United_v2.11.1.exe - 7.8 Mb
3) Download LG Flash Tool 2014 tool and extract - LG_Flash_Tool_2014.zip - 3.1 Mb
4) Enter to Download Mode and plug USB into your PC
5) Run LGFlashTool2014.exe and do as following pictures :
(If you cannot run LGFlashTool2014.exe, please install Visual C++ Runtime Library) - Download HERE
Normal Flash: Flash ROM without losing any data. Only use this when you need to fix system error. Beware of boot loop when flashing ROM that differ from current ROM on your phone or MOD ROM.
CSE Flash: Choose this option when you need a fresh format. All data will be gone. It's suitable for upgrading or downgrading ROM or simply use this when you need to back to Stock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No need to choose desired language, it automatically change to English as a default setting.
Wait until 100% to complete !
REMEMBER if you get Bootlooping after flashing perform a factory hard reset!
Instructions Here: https://support.t-mobile.com/docs/DOC-7590
_______________________________________________________________________________________________________________________________
2015 (updated with pictures) TOT Method!
RETURN TO STOCK TOT METHOD!, AT&T, T-Mobile, Sprint, Verizon, & a The few International TOT`s that are available
How to Flash YouTube Video:
1.Download Everything!
1.1)Download Both Stock Image & DLL File – Download Here
1.2)Download LG FlashTools V1.8 - Setup_LGFlashTool_1.8.1.1023.exe - 9.3 Mb
1.3)Download Drivers (Any LG Phone) - Here (Verizon Only) – Here
1.4)Megalock DLL File - Megalock.dll Download
(Hint) If your getting wrong dll/Wrong model error after having to start to flash and it fails use this DLL file instead of your model DLL file: LGUP_8974.dll - 1.4 Mb
This error means you where running a rom not meant for or built on a different model#.
Install:
2.Install LG Drviers
3.Install Flashtool (Don’t run it yet)
4.Extract the TOT file from the Zip
5.Copy MegaLock.dll file to C:\LG\LGFlashtool (This might be a hidden folder so enable "hidden folders". Replace the old MegaLock.dll file)
6.Power off your Device & or pull battery (G3),(G Pro),(G Flex)
7.Press and hold the Vol UP Key and plug in the USB cable to your phone you should now see “Firmware Update/Download Mode” and be in Download mode.
8.Open up Device Manger on your PC
8.1)Click on ports and double click LGEModem
8.2)Go to Port Settings Tab and click Advanced
8.3)Change COM Port to COM41 and click Okay.
8.4)After this you may need to rereboot your phone back into download mode.
9.Run LG Flashtool as Administrator
10.Select Manual Mode at the top
11.Click The DLL Box and choose the DLL file from Above meant for your device
12.Click the S/W box and select the firmware file with the .tot extension, Then Click OK when done.
13.Now Click the Yellow Arrow Button at the top left, The Firmware install will be triggered
14.You may need to unplug/replug phone before Firmware install will start (If it does nothing after clicking the yellow button
15. Should take anywhere between 4-8 Minutes, When its done your phone should reboot
Do NOT Close the FlashTool Window during firmware update.
99% of the time FlashTool will FAIL after 85% anything after 85% is just your phone rebooting so your safe
_____________________________________________________________________________________________________________________________
Remember if you have bootloop or stuck on LG Logo after flashing make sure you FACTORY RESET!
Extra Important Info:
To Fix ANY Driver issues make sure you reboot your computer after removing and then reinstall again, Also try different USB ports or USB cable or try another PC.
Also try this for any driver issues: http://forum.xda-developers.com/showpost.php?p=53313255&postcount=5400
To Fix "Knock On" from not working - Thanks too - @wassk "If ur phone is d802 then open ur dialer type there 3845#*802# when hidden menu opens check for settings....press settings and inside u have Update Touch Firmware...press that and wait for 10-15 seconds....then close this and try again ur screen...maybe will help"
BEFORE POSTING IN THIS THREAD. DON`T POST ANY LINKS TO the LG-FIRMWARE site as most of there links are not even working, and also make you see an AD for 5 seconds to make money off of you for a dead link they are not even hosting they are just thieving off LG`s Servers and making money on it. Anyone That posts a link to it will be reported to the Mods or asked to remove. Thank You.!
____________________________________________________________________________________________________________________________________________________
My Links are ALWAYS hosted on MY servers for NO Downtime! If My site does NOT have what your looking for PM me or post what you want and I will try and get it for you
Feel Free to buy me a Beer if you feel I have helped you Thank you!
Thank you so much!
Donations: @avinash Rajkumar, @penone1130, @nilesd
LGUP Method:Flashes both KDZ & TOT files:
Thanks to @shakeyabooti for LGUP!
Download LGUP from HERE
Install the file with the DLL name in them first and then LGUP_Install_Ver_1_14_3 Then copy the folder "common" to C:\Program Files (x86)\LG Electronics\LGUP\model (this should resolve unknown error)
Make sure you have downloaded the required KDZ file MM or LP
Open LGUP on your computer "make sure your phone is plugged in"
ARE YOU HAVING TROUBLE WITH LGUP NOT SEEING YOUR MOBILE?
Try this....... take the back off your mobile so you can get at the battery. Connect your mobile via USB. Start LGUP, if it does not see your phone DO NOT DISCONNECT, DO NOT RESTART OR TURN OFF LGUP. Take out the battery and then put it back in.......let the phone restart on its own. LGUP should now see it.
LG Drivers: in First post
TO DO A FULL WIPE AND INSTALL MM - Open the LGUP on your computer. FILE PATH point it towards the MM KDZ.
IMPORTANT!!!!!!! shut down LGUP!
Now open LGUP again - you will notice that the MM KDZ will still be showing in the FILE PATH section. Select REFURBISH and make sure BIN file is ticked. Press Start. Make cup of tea and be patient
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a FULL wipe, tick BIN file. Press Start. Make cup of tea and be patient
Video Guide: (Thanks to @KiaTheKing
https://www.youtube.com/watch?v=iPKcuYwDoxY
--------------------------------------------------------------------------------------------------------------------------------------------------
Thanks very much!
Verizon stock firmware looks like it's available here:
Mod Edit: Ad referral and ad redirect links are not allowed. Link removed.
Sent from my Galaxy Nexus using Tapatalk 4
That site does not even work
hyelton said:
That site does not even work
Click to expand...
Click to collapse
Strange, it was working when I posted. I should have downloaded and hosted the firmware.
Its all up again ::
Country: United States
Carrier: T-mobile
Model: LGD801BK, Firmware Revision: D80110c_00
Download:http://csmgdl.lgmobile.com/swdata/WDLSW/LGD801BK/ATMOBK/D80110c_00/D80110C_00.kdz [Size: 1.8GB]
Notes, The new LG G2 Firmware in .kdz format can not be converted into .BIN/FLS format with the LG Extract tools for the time being.
Carrier: Verizon Wireless
Model: LG VS890 Firmware Revision: VS98010B_13
Download: VS98010B_13.S10B_13
Carrier: AT & T
Model: LG VS890 Firmware Revision: V10d_00
Download: LGD800AT-01-10C-210-410-AUG-13-2013 :good:
I have now Updated the link above which now has the T-Mobile and Verizon Versions :
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/
hoping the ATT version gets posted soon, there was a link but the DL is broken =/
djkinetic said:
hoping the ATT version gets posted soon, there was a link but the DL is broken =/
Click to expand...
Click to collapse
Guys , do you know about a CWM Recovery , is it available for F320K ?
the att files are zip files will this method still work the same?
clippy83 said:
the att files are zip files will this method still work the same?
Click to expand...
Click to collapse
Huh? There is No AT&T Download for the G2 Yet.
hyelton said:
Huh? There is No AT&T Download for the G2 Yet.
Click to expand...
Click to collapse
can someone with a AT&T G2 go to http://g2-lg.com/lg-g2-stock-rom-firmware/ and give the admin a IMEI code? Looks like that is all he needs to get it for us. See the comments
joshuadjohnson22 said:
can someone with a AT&T G2 go to http://g2-lg.com/lg-g2-stock-rom-firmware/ and give the admin a IMEI code? Looks like that is all he needs to get it for us. See the comments
Click to expand...
Click to collapse
I'll try, one second.
Does he have an email address I can send it to him at? Not sure how to contact him.
Nevermind, they can be found here or here.
Thanks, Uploading it on my server now for backup!
This flash file will need to be flashed a different way than this guide though.
hyelton said:
Thanks, Uploading it on my server now for backup!
This flash file will need to be flashed a different way than this guide though.
Click to expand...
Click to collapse
How would I go about doing this on att ..I mistakenly blanked out the carrier field on build.prop
Sent from my GT-I9505G using Tapatalk 4
djkinetic said:
How would I go about doing this on att ..I mistakenly blanked out the carrier field on build.prop
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
Follow this Guide Exactly EXCEPT Download and use the ZIP file and DLL file from the storagecow link on the first post and choose AT&T
http://forum.xda-developers.com/showthread.php?t=2302660
hyelton said:
Follow this Guide Exactly EXCEPT Download and use the ZIP file and DLL file from the storagecow link on the first post and choose AT&T
http://forum.xda-developers.com/showthread.php?t=2302660
Click to expand...
Click to collapse
I'll give it a try and hope it works lol
Sent from my GT-I9505G using Tapatalk 4
Ok so i couldnt get LG Flash tool to work properly on my desktop, I was about to take a trip to the store, but I decided let me try on my laptop, and it worked!! It just finished restoring and is now booted up...lesson learned, and good to know we have a way that works to get back to stock.
I know others have looked as well but can anyone *please* dump the rom of their AT&T 4.2.2 stock image for the good of all us AT&T S4 Zoom owners who are stuck in a logo reboot loop or have other problems that require a restore? There are currently no images available on any of the usual places (Samsung firmware, updates etc.)
Thanks very very much in advance!
If you not found any stock rom for C105A At&t... & Your Phone is In Boot loop Stuck on Samsung Logo... Then Just Flash C105A Mexico C105AUBUAND1, 4.2.2 System And Cache Separately in Odin...
This will not work because the AT&T variant of the phone is bootloader locked. You are not able to flash firmware variants unless they are for the AT&T version of the phone. Hence why so many people need a firmware image for AT&T. If anyone has or can make a DD.Image it would help a lot of people.
moomoo said:
This will not work because the AT&T variant of the phone is bootloader locked. You are not able to flash firmware variants unless they are for the AT&T version of the phone. Hence why so many people need a firmware image for AT&T. If anyone has or can make a DD.Image it would help a lot of people.
Click to expand...
Click to collapse
i am try this Method personally.. Every Thing working Fine
Download SM-C105A Mexico (Telcel) Android 4.2.2 firmware, from SamMobile,
Extract Whole Firmware Select only System Image & Cache file & Make it odin flashable Tar. using (tar-Tool_Odin3-v3.07_by_mkh.mourad)
Flash System & Then Cache In Odin Ap.. Thats It..
Try Only If Your Phone Is Soft Brick or In Boot loop State... Thanks
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53644
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53643
I'd like to help. I've extracted system.img and cache.img from an AT&T sm-c105a (4.2.2). Unfortunately I didn't read the above instructions very well and placed them both in an odin flashable tar.md5 file. I guess if you want to follow the above proceedure you will need to flash them separately. On the other hand, if you have a brick already anyway, you could just try it out. Any problems with the file post here. Mediafire was being dodgy and I wouldn't be surprised if it was damaged. Anyway here is the link, or as close a facsimile as my noobness will allow: http www mediafire com /download /xbdxb8gun1niwg9 /sm_c105a.zip
So, I assume from the deafening silence that this did not work? I'm not surprised since a dd of a mounted partion (system) can't be a good idea. I have been experimenting with Adebar which is also supposed to make a system backup. Doesn't seem to fully support the phone, or, doesn't create the full backup. I'm open to other ideas....
More files
Boot and recovery images, plus pit file all from stock sm-c105a AT&T JB 4.2.2. www . mediafire . com/ download/ 3df255lt8unnh24/ Boot_Recovery.tar.gz
Faisalkhan.007 said:
i am try this Method personally.. Every Thing working Fine But 3G Is Not Working..
Download SM-C105A Mexico (Telcel) Android 4.2.2 firmware, from SamMobile,
Extract Whole Firmware Select only System Image & Cache file & Make it odin flashable Tar. using (tar-Tool_Odin3-v3.07_by_mkh.mourad)
Flash System & Then Cache In Odin Ap.. Thats It..
Try Only If Your Phone Is Soft Brick or In Boot loop State... Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Don t work to me.
Here are a cache and system image from the AT&T variant of the phone. @awwar can you be more specific. You are in a boot loop? No recovery?? Device recognized by Odin/Heimdall??? I am VERY interested in providing a way to unbrick our phones but am unwilling to brick my only device. If you want to try something post here and I will provide what support I can.
My CM-C105A is in Kies recovery mod mode. I can flash only system and cash tar files. Kies show error when i am traing to recover my phone.
Have you tried the pit file? Sometimes that might help?? Also, I have a boot.img download further up the page. If your bootloader is bad you could get similar symptoms? Kies doesn't like my boot/recovery images? Can you post the specific error? Thanks for replying. c_p
capt_planit said:
Here are a cache and system image from the AT&T variant of the phone. @awwar can you be more specific. You are in a boot loop? No recovery?? Device recognized by Odin/Heimdall??? I am VERY interested in providing a way to unbrick our phones but am unwilling to brick my only device. If you want to try something post here and I will provide what support I can.
Click to expand...
Click to collapse
have you pit -file to AT&T firmware?
awwar said:
have you pit -file to AT&T firmware?
Click to expand...
Click to collapse
@awwar Here are recovery and boot images and pit file from AT&T version of phone Build # JDQ39.C105AUCUAMJ2. Kies may not be able to restore if you have a damaged bootloader source. But, on a plus note, "I haven't run into anyone yet who couldn't undo soft brick from Odin" source
capt_planit said:
@awwar Here are recovery and boot images and pit file from AT&T version of phone Build # JDQ39.C105AUCUAMJ2. Kies may not be able to restore if you have a damaged bootloader source. But, on a plus note, "I haven't run into anyone yet who couldn't undo soft brick from Odin" source
Click to expand...
Click to collapse
Nothing changed, I flashed whith this firmwares but error. This firmware is too large.
@awwar Ok man, thanks for testing. I hope your skills extend further than the average windows user. You have to extract the files and then repackage them for odin as tar.md5. I think you can do it in windows but I can only talk you through it if you are using linux. I am not sure which image to flash first but Faisalkhan.007 in the first page suggests doing it one file/partition at a time. I would flash my recovery and on reboot try using volume up and home to get to the newly flashed recovery. I think you are getting file too large because you've got more than one file in your flash package. Restore the pit file as a last attempt after trying to flash each partition. I'd love to figure out how to pass you the bootloader only but I've got another project ahead of this. Did you look at some of those links? Try this (search for download mode on the page) if you are having trouble getting to download mode. And this is for osX but might help too. The errors you are getting don't sound like the one I get. I upload an entire file then fail at 100% for an unknown reason. The Heimdall guys say that is due to the locked bootloader. TLDR: Split files, flash singly, reboot and try stuff in between. c_p
Well I Really Don't Know , But Its Working For Me,
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53644
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53643
awwar said:
Nothing changed, I flashed whith this firmwares but error. This firmware is too large.
Click to expand...
Click to collapse
Okay Wait I Am Gonna Upload Flash able Tar System & Cache files On Cloud When its Done, i will send You Link, :good:
awwar said:
Don t work to me.
Click to expand...
Click to collapse
https://mega.nz/#F!SFhCnIIb!D7QIX-Xmkd8aZBfU_-2PIg
Try It
I have *three (3)* SM-C105A S4 Zoom Camera phones by Samsun and enjoy them. I have upgraded firmware on 2 so that I can use Remote ... uh, is it Viewfinder? And it works. Not to the point. What I *lost* was compatibility with *ooooooold* Photo Elements. Which, at age 57 I like to use and don't want to relearn. I run it on a virtual XP. What makes this post relevant is that *third* S4. It *hasn't* upgraded. Cracked screen, disused, but I crammed.. well, a bit of fibrous matter...OK , a ciggy-butt, in the battery door, with a rubber-band, to hold a fresh battery in place, ... and it's booting now. So, please give me a month to extract the firmware, yes it is AT&T and also upload Photo Elements, firmware from old and upgraded, to continue the discussions, or not, and to try cloning the two to restore my ability to post process nudies shot with my camera phones. And other pics. I wrote an AI MathCAD program to postprocess nudies (it's fine art fer heaven's sake) that actually simualted the artist's brush strokes. More on all this in I hope a month.
DGoncz
---------- Post added at 01:39 PM ---------- Previous post was at 01:22 PM ----------
No, back when, I must have applied, not the most recent upgrade, but the intermediate of the three versions.....and all hope is lost. Photos from the oldest S4 I have do *not* open in Photo Elements. None of my cameras produce photos that open in Photo Elements any longer...but they did. I opened an older photo just now.
Dang these upgrades. The message says the JPG file is missing a segment. Phooey.
I have a business account with Samsung and will open a support ticket.
I will not pursue the hack angle for now.
Samsung may help me.
Cheers,
DGoncz
DGoncz said:
I have *three (3)* SM-C105A S4 Zoom Camera phones by Samsun and enjoy them. I have upgraded firmware on 2 so that I can use Remote ... uh, is it Viewfinder? And it works. Not to the point. What I *lost* was compatibility with *ooooooold* Photo Elements. Which, at age 57 I like to use and don't want to relearn. I run it on a virtual XP. What makes this post relevant is that *third* S4. It *hasn't* upgraded. Cracked screen, disused, but I crammed.. well, a bit of fibrous matter...OK , a ciggy-butt, in the battery door, with a rubber-band, to hold a fresh battery in place, ... and it's booting now. So, please give me a month to extract the firmware, yes it is AT&T and also upload Photo Elements, firmware from old and upgraded, to continue the discussions, or not, and to try cloning the two to restore my ability to post process nudies shot with my camera phones. And other pics. I wrote an AI MathCAD program to postprocess nudies (it's fine art fer heaven's sake) that actually simualted the artist's brush strokes. More on all this in I hope a month.
DGoncz
Click to expand...
Click to collapse
@DGoncz You could do that, or, you could just do a complete wipe/reset. Should be 4.2.2 after that. You may also be able to use a hex editor to set the start of the jpeg file to whatever your proggie wants to see. Good luck c_p
Any chance someone with an H931 can use LGUP to do a firmware dump? I'm specifically interested in the modem and system partitions (for unlocking band 30 and maybe enabling AT&T WiFi calling), but it might also be possible to do a full flash to the H931 from a bootloader unlocked US998 (depending on firmware signatures).
I'm still on Nougat, but Oreo will probably also work (and I'll eventually want Oreo anyways), so either would be awesome.
To dump the firmware, use the LGUP from this thread (https://forum.xda-developers.com/showthread.php?t=3738917), and use the patched DLL and EXE from this thread (https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23 and use LGUP+V30DLL_PATCHED.zip), and just use the DUMP function. Definitely skip userdata though (I don't want your data, and it's encrypted anyways).
Thanks!
Anybody have an AT&T H931 and can help me out?
Cross flashing the modem to get band 30 seems like a definite possibility, so I'd really appreciate it. ?️
gwillmer said:
Any chance someone with an H931 can use LGUP to do a firmware dump? I'm specifically interested in the modem and system partitions (for unlocking band 30 and maybe enabling AT&T WiFi calling), but it might also be possible to do a full flash to the H931 from a bootloader unlocked US998 (depending on firmware signatures).
I'm still on Nougat, but Oreo will probably also work (and I'll eventually want Oreo anyways), so either would be awesome.
To dump the firmware, use the LGUP from this thread (https://forum.xda-developers.com/showthread.php?t=3738917), and use the patched DLL and EXE from this thread (https://forum.xda-developers.com/showpost.php?p=75272845&postcount=23 and use LGUP+V30DLL_PATCHED.zip), and just use the DUMP function. Definitely skip userdata though (I don't want your data, and it's encrypted anyways).
Thanks!
Click to expand...
Click to collapse
I have a H931, do you still need the dump?
banziitox24 said:
I have a H931, do you still need the dump?
Click to expand...
Click to collapse
Yes! Oreo would be awesome if you have it.
gwillmer said:
Yes! Oreo would be awesome if you have it.
Click to expand...
Click to collapse
don't have Oreo, only have 7.1.2, do you think you can help me make these files flashable, either DZ or KDZ. Can't seem to find anything to do that
Nougat is definitely still useful for me, so I'd really appreciate you uploading that. Using the modem might be questionable across versions, but the wifi calling config in /system would be great.
I'm pretty sure only the bootloader-unlocked models (US998/H930) would have any way to flash this kind of partition dump (using dd from recovery), because they aren't the kdz or dz format that LGUP seems expect. I haven't really looked into how to write those file formats either, but I'm not optimistic about my skills there.
However, I was just thinking about one possible upgrade path to Oreo for the H931s that aren't on AT&T's network: if we get the FOTA upgrade file. Looking at my /fota dump, I think it'd be on the cache partition after downloading/before upgrading, and I bet it'd be in the format LGUP wants for the "FOTA UPGRADE" option, meaning it could be used with a stock H931. Are you on AT&T?
gwillmer said:
Nougat is definitely still useful for me, so I'd really appreciate you uploading that. Using the modem might be questionable across versions, but the wifi calling config in /system would be great.
I'm pretty sure only the bootloader-unlocked models (US998/H930) would have any way to flash this kind of partition dump (using dd from recovery), because they aren't the kdz or dz format that LGUP seems expect. I haven't really looked into how to write those file formats either, but I'm not optimistic about my skills there.
However, I was just thinking about one possible upgrade path to Oreo for the H931s that aren't on AT&T's network: if we get the FOTA upgrade file. Looking at my /fota dump, I think it'd be on the cache partition after downloading/before upgrading, and I bet it'd be in the format LGUP wants for the "FOTA UPGRADE" option, meaning it could be used with a stock H931. Are you on AT&T?
Click to expand...
Click to collapse
No I'm not with AT&T I just need these files converted in a way that I could use them to flash into another phone, I'm uploading files now I'll send you a PM when i have them uploaded, also how you plan to flash modem or the files that you need from this dump because that might help me a little
banziitox24 said:
No I'm not with AT&T I just need these files converted in a way that I could use them to flash into another phone, I'm uploading files now I'll send you a PM when i have them uploaded, also how you plan to flash modem or the files that you need from this dump because that might help me a little
Click to expand...
Click to collapse
With the disclaimer that I haven't tested this yet, here's my plan. Before flashing anything, I'm going to open up the modem in a hex editor to check if the secure boot RSA certificate matches the one from mine (it seems the US998, AS998, VS996, and LS998 have the same one, while the H932 does not). If it doesn't, then I can't flash the modem, because then it won't boot.
I should be able to flash /system though, because I have an unlocked bootloader (which disables the signature check). I don't actually want most of AT&T's bloatware though, so I'm going to open the system image in 7zip, and extract what I need.
As far as how I would actually flash, I'm going to use the dd command after booting TWRP (using either adb shell, or TWRP's built in terminal). dd is a tool for doing low level disk and file copying, and it can be really dangerous (I've seen it called "disk destroyer" lol). The command will be something like:
Code:
dd if=/external_sd/modem.img of=/dev/block/platform/soc/1DA4000.UFSHC/by-name/modem
Unfortunately, this has to be done from a custom recovery, because the stock recovery doesn't have a terminal or the dd command, and you won't be able access anything under /dev/block when booted without root. Trying to write an image to a live file system is not a good idea, and even if you could, it would check the signature on boot and have problems.
This PDF explains secure boot, though I think it's a little different for the file system images (like /system).
https://www.qualcomm.com/media/docu...d-image-authentication-technical-overview.pdf
This post by @runningnak3d explains which images are signed (for both regular and bootloader unlocked). https://forum.xda-developers.com/showpost.php?p=76319892&postcount=34
Thanks again!
gwillmer said:
With the disclaimer that I haven't tested this yet, here's my plan. Before flashing anything, I'm going to open up the modem in a hex editor to check if the secure boot RSA certificate matches the one from mine (it seems the US998, AS998, VS996, and LS998 have the same one, while the H932 does not). If it doesn't, then I can't flash the modem, because then it won't boot.
I should be able to flash /system though, because I have an unlocked bootloader (which disables the signature check). I don't actually want most of AT&T's bloatware though, so I'm going to open the system image in 7zip, and extract what I need.
As far as how I would actually flash, I'm going to use the dd command after booting TWRP (using either adb shell, or TWRP's built in terminal). dd is a tool for doing low level disk and file copying, and it can be really dangerous (I've seen it called "disk destroyer" lol). The command will be something like:
Code:
dd if=/external_sd/modem.img of=/dev/block/platform/soc/1DA4000.UFSHC/by-name/modem
Unfortunately, this has to be done from a custom recovery, because the stock recovery doesn't have a terminal or the dd command, and you won't be able access anything under /dev/block when booted without root. Trying to write an image to a live file system is not a good idea, and even if you could, it would check the signature on boot and have problems.
This PDF explains secure boot, though I think it's a little different for the file system images (like /system).
https://www.qualcomm.com/media/docu...d-image-authentication-technical-overview.pdf
This post by @runningnak3d explains which images are signed (for both regular and bootloader unlocked). https://forum.xda-developers.com/showpost.php?p=76319892&postcount=34
Thanks again!
Click to expand...
Click to collapse
Yeah I figured you where either going to zip it and flash it via TWRP or even via Fastboot, here's a link for the dumped ROM.
https://www.mediafire.com/download/zp558y5y5qms3i7
Please don't make mirrors or redistribute my link without my consent.
Thank you
Sent from my SM-N950U using Tapatalk
It will be interesting to see if you can get any of this to work. I'd like to get WiFi calling and band 30 support on my unlocked US998 on AT&T. I recently just updated mine to Oreo. So if anyone can dump Oreo I can try that.
I have Oreo and the H931.
Do you still need this done and if so, will I be taking any risks by doing this?
I meant to report back what happened with Nougat, but life got a little crazy. Using the Nougat modem didn't seem to unlock band 30, but I didn't get to test much further because it also made my fingerprint reader not work (flashing back to my US998 modem fixed it). No issues booting though!
Sulgor84 said:
I have Oreo and the H931.
Do you still need this done and if so, will I be taking any risks by doing this?
Click to expand...
Click to collapse
Yes please! I think the Oreo modem won't cause the same problem with the fingerprint reader, and I'm much more optimistic about getting wifi calling to work using the Oreo system dump. And no, it won't harm your phone (you aren't writing anything to the phone, only reading). Thank you so much!
Sulgor84 said:
I have Oreo and the H931.
Do you still need this done and if so, will I be taking any risks by doing this?
Click to expand...
Click to collapse
Any chance you were able to do this, it would be very useful to have this around given the cross flashing/bootloader unlock. Unfortunately there are no KDZ/TOT's for the ATT variant like there are for other models.
Thanks
Anybody with the H931 and Oreo able to help us out? It'd be very much appreciated!
gwillmer said:
Anybody with the H931 and Oreo able to help us out? It'd be very much appreciated!
Click to expand...
Click to collapse
I have two V30's that I can access, both H931 Oreo. One is still stock entirely, bootloader still locked and running the ATT OTA oreo update. The other is mine, converted to a US998 running a custom rom rooted. Would you like me to dump the stock phone? I'd be very interested in seeing band 30 support on a custom rom possibly, and wifi calling would be a bonus.
Phoked said:
I have two V30's that I can access, both H931 Oreo. One is still stock entirely, bootloader still locked and running the ATT OTA oreo update. The other is mine, converted to a US998 running a custom rom rooted. Would you like me to dump the stock phone? I'd be very interested in seeing band 30 support on a custom rom possibly, and wifi calling would be a bonus.
Click to expand...
Click to collapse
Yeah, that would be awesome. Backup boot and modem also if you can. At&t has no kdz like sprint. It would be nice for at&t users to have a stock flashable zip also.
Phoked said:
I have two V30's that I can access, both H931 Oreo. One is still stock entirely, bootloader still locked and running the ATT OTA oreo update. The other is mine, converted to a US998 running a custom rom rooted. Would you like me to dump the stock phone? I'd be very interested in seeing band 30 support on a custom rom possibly, and wifi calling would be a bonus.
Click to expand...
Click to collapse
Yes! Not only is there potentially band 30 and wifi calling, but as of right now, there's no way to bring an H931 back to stock Oreo after doing any crossflashing. Modem and system definitely are most important, but it might not be a bad idea to dump everything except userdata (so that a crossflashed H931 can be completely returned to stock in case of warranty issues, etc).
Thanks!
gwillmer said:
Yes! Not only is there potentially band 30 and wifi calling, but as of right now, there's no way to bring an H931 back to stock Oreo after doing any crossflashing. Modem and system definitely are most important, but it might not be a bad idea to dump everything except userdata (so that a crossflashed H931 can be completely returned to stock in case of warranty issues, etc).
Thanks!
Click to expand...
Click to collapse
I'll be glad to help development in any kind of way.
Didn't know there was so many partitions haha. Dumping all partitions except userdata with patched LGUP as I type this. Is there any uploading site you would prefer me to use? I haven't uploaded large files for public use before.
---------- Post added at 09:16 AM ---------- Previous post was at 09:05 AM ----------
Hmm, I unfortunately ran into an error towards the end of the dump
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this dump still valid or should I try something else? All the files I got from it are sitting at 8.42gb so far.
Edit: Just tried again. Watched the progress from 0-100% this time and it his the error once at 100%. Produced the same error and dump files are the same size as before. 74 files in total. There are 3 modem files, the first one at 110mb, the rest at 2mb. The system file is at 6.58gb. Let me know if these files are still of use despite the error and I will upload to the site of your choice.
Phoked said:
I'll be glad to help development in any kind of way.
Didn't know there was so many partitions haha. Dumping all partitions except userdata with patched LGUP as I type this. Is there any uploading site you would prefer me to use? I haven't uploaded large files for public use before.
---------- Post added at 09:16 AM ---------- Previous post was at 09:05 AM ----------
Hmm, I unfortunately ran into an error towards the end of the dump
Is this dump still valid or should I try something else? All the files I got from it are sitting at 8.42gb so far.
Edit: Just tried again. Watched the progress from 0-100% this time and it his the error once at 100%. Produced the same error and dump files are the same size as before. 74 files in total. There are 3 modem files, the first one at 110mb, the rest at 2mb. The system file is at 6.58gb. Let me know if these files are still of use despite the error and I will upload to the site of your choice.
Click to expand...
Click to collapse
The size sounds about right. The last file it dumped might be corrupted, but it's odd that it did the same thing twice. It does say timeout, so maybe the phone just stops sending data when it's done? Either way, all the other files should be fine.
banziitox24 used mediafire and that worked pretty well. Also, putting them all in an zip or rar would cut down on the file size and save you some time.
Thanks again!
Glad to help, uploading compressed rar (2.54gb) to mediafire right now. If there's a way to fix the error I was seeing and you at some point need the file that perhaps got corrupted, let me know and I will be happy to try again. Also, I noticed a file popped up after LGUP finished the dump, titled "LG_358164080144563_20180619092912.xml", is this of any use too?
---------- Post added at 10:46 AM ---------- Previous post was at 10:05 AM ----------
http://www.mediafire.com/file/jy11ghyhh5iddz3/H93120d.rar/file
Hope this helps. Would be exciting to see these carrier limited functions come back for those rooted, especially if my V30 dump contributed to so haha. Feel free to ask me if there's anything else I can help with.
Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge. It changed me from AU to HKG for reasons unknown to me.
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Wibble Wobble said:
Hi all,
First some details:
LG930DS
secure startup enabled
H930DS30s_00_OPEN_HK_DS_OP_0902.kdz installed via LG Bridge.
It changed me from AU to HKG for reasons unknown to me.
Click to expand...
Click to collapse
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Wibble Wobble said:
rooted with TWRP and Magisk 20.1 installed
I'm having issues with VoLTE not working (actually no longer in settings of the hidden menu) since installing Pie and I want to rule out the HKG variant as the cause. To do this I will install H930DS30c_00_OPEN_AU_DS_OP_0902.kdz instead. I have downloaded this kdz but now I'm not sure if I can install it without having to wipe and re-do all the Magisk and TWRP (and setting up all my files and apps again). After reading the guides none seem to answer this question quite right as they are mostly aimed and either US, EU, or India with their TWRP flashable roms like this one https://forum.xda-developers.com/lg-v30/development/us998-lg-v30-us998-us99830a000704-kdz-t3952256
Can someone with a better idea of how this works let me know the best option for me to switch over to the AU variant.
Click to expand...
Click to collapse
We haven't always had TWRP-flashable zips. Only thanks to generous, talented devs do we have the collection of TWRP flashable zips for US998, H931, H933, VS996, LS998, T-mobile H932, H930, India H930DS. That's only 8 of at least 20 variants and I'm not even counting all the different regional variants of H930DS...
So you will have to do what we all did before TWRP-flashable zips, and what we will have to do again when some of our TWRP flashable zip devs move onto other phones.
Method #1 -- Works some of the time on Oreo, not yet tried on Pie
This worked for many people in Oreo -- but some still had to reinstall TWRP, reformat data, reinstall the root files. Never could figure out the difference between success and not. Then we got TWRP-flashable zips and the issue became moot.
1) Make backup in TWRP AND make backup of all apps in Titanium Backup.
2) Flash new KDZ via Pie-compatible Dev Patched LGUP in Partition DL mode, but omit the Recovery partitions. Do NOT select "all partitions". This will let you keep TWRP.
3) Boot into TWRP via fastboot commands from your computer, just like when you first installed TWRP using the WTF instructions. (Best not to use the stupid hardware button dance.) Once in TWRP, then choose Reboot to Recovery (from within TWRP) to get the actual internal phone TWRP, instead of the PC TWRP.
4) Flash the Pie-compatible three root files (Magisk, encryption disabler, root check disabler, Magisk again). See attachments on this post to download those files.
5) Restore all Data from within TWRP. Do not choose any other categories.
6) Wipe all Caches.
7) Reboot
Restoring all TWRP data may or may not overcome the fact that you have re-flashed encrypted stock Pie on your phone. IF it does work, then after rebooting the phone if anything is still wonky, use Titanium Backup to restore all apps and data (this is in addition to the TWRP data restore you did).
Good luck.
Method #2 -- Works all the time, but yeah you have set up your phone again
1) Flash new KDZ via Pie-compatible Dev Patched LGUP in REFURBISH mode.
2) Your phone is now on the region KDZ you desire and you still have unlocked bootloader. You will need to reinstall TWRP, and then flash the three root files (Magisk, encryption disabler, root check disabler, Magisk again). This includes the step where you reformat all data with a "YES".
See instructions here:
REINSTALL TWRP on PIE stock KDZ with ALREADY-UNLOCKED BOOTLOADER
THAT POST ASSUMES YOU HAVE PREVIOUSLY UNLOCKED BOOTLOADER, AND THAT YOU HAVE NOW UPGRADED TO STOCK PIE KDZ. YOU HAVE UNLOCKED BOOTLOADER and are STILL on firmware which has FASTBOOT FLASH COMMANDS.
___________
Dev Patched LGUP
Dev Patched LGUP vs regular LGUP is necessary when cross flashing across regions or other variants. You will need this for either of the two methods above.
Here's how to flash with LGUP:
UPGRADING LG V30/V30+/V30S TO PIE KDZ FIRMWARE WITH LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open Dev Patched LGUP and flash PIE KDZ either via PARTITION DL MODE (but omit Recovery Partitions for your purpose in this thread) for Method #1 or via REFURBISH for Method #2.
Use the attached patched LGUP in this post. If you get a ".dll error" you either didn't install correctly or are using the wrong version of Dev Patched LGUP. Read the installation instructions carefully. Some people have used OTHER versions of LGUP before and ignore the installation instructions -- they think they know how to install and they do NOT --- then complain about .dll error, which is their fault.
* NOTE: YOU CAN NOT USE LGUP "UPGRADE" MODE IF YOU HAVE TWRP CUSTOM RECOVERY. LGUP "Upgrade" is like a manual OTA and is only for pure stock (but you can have unlocked bootloader).
3) IF your bootloader is unlocked, it will remain unlocked after flashing KDZ.
_________________
HOW TO INSTALL DEV PATCHED LGUP
0. UNINSTALL any prior LGUP version. Seriously. Go to Programs folder and delete the LGUP folder if you must.
1. DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
2. Extract LGUP_DualMode.zip to a folder on your PC.
3. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
4. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode. < READ THAT AGAIN.
5. Launch LGUP using the desktop shortcut. NOT from folder icon!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
I don't care what anyone else tells you. If you listen to them, let them help you recover from messing up your phone.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
It's all fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again.
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
ChazzMatt said:
LG Bridge will look for the KDZ intended for your IMEI, not the firmware you have on the phone right now. Was your phone imported from Hong Kong (China)? Or did you buy from Australian carrier or Australia LG authorized retailer? Did you buy the phone new or used? Have you updated it before using LG Bridge?
Any H930DS can be flashed to run any other H930DS firmware. Best guess is somehow the phone was originally Hong Kong variant and someone flashed it to Australian firmware. When you went to look for update via LG Bridge, then it updated to that region Pie meant for that IMEI.
Unless you have used LG Bridge successfully before and you are sure it is Australian IMEI H930DS?
Click to expand...
Click to collapse
Ahh thank you for explaining this. I imported mine from Hong Kong. As far as I know it was never sold new in AU.
I'm about to rush off to work for the day so I will have to try this when I get home tonight and let you know how it goes. Thank you so much for the detailed and fast response! This is much more than I was hoping for!
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Wibble Wobble said:
One last question. Do I need to disable secure startup or does the encryption work with the method #1?
Click to expand...
Click to collapse
Yes, I would do that.
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Wibble Wobble said:
As far as I know it was never sold new in AU.
Click to expand...
Click to collapse
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
ChazzMatt said:
I don't know the Australian market, but we have an Australian XDA moderator who has or had Australia H930DS. Since there is Australia H930DS firmware, I assume it was sold new back in 2017/2018 by some carrier or by LG authorized retailer.
He has Vodafone in his profile. @Redline.
Click to expand...
Click to collapse
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Redline said:
This is correct. I bought one BNIB from an eBay seller, a H930DS and it was only a couple weeks old from the factory. Came pre-loaded with AU firmware and I updated it to the latest. Before going the LineageOS route.
Click to expand...
Click to collapse
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Wibble Wobble said:
Interesting to know. I bought mine back in 2017 but I couldn't find it in AU and read somewhere that imports were going to be the only option. To bad for me.
I know little of what IMEI's do. Is there any issues related to regional OS versions and the IMEI of a device? Is the hardware otherwise the same?
Click to expand...
Click to collapse
I could kind of answer is the question of if the hardware is otherwise the same, the rest might be a question for ChazzMatt.
AFAIK the modem on my H930DS was the same as other similar models, similar to the V20 you can flash a KDZ from another region if you wanted to (to for example, get less bloat or better coverage on a band you rely on for service). I remember on my V20 the region that had Claro-carrier firmware came with the least bloat out of the box vs other regions, but we also had KDZ Writer with the V20 that allowed us to flash specific parts of the KDZ *in* TWRP on the device itself, so you could have, say, Claro firmware with the AU modem.
As for what IMEIs do, they're similar to the MAC address on a piece of networking gear; it's a globally-unique identifier specific to your device, you can put it into IMEI lookup websites to get information about manufacture date, model etc.
If you have a carrier-model phone, they can also block your IMEI on their network if it is stolen and then attempted to be re-used.
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Wibble Wobble said:
I've had to opt with #2 as the encryption was a problem as you suspected. I'm puzzled though... while I was setting up for USB debugging I noticed that I had VoLTE in the drop down menu, however, calls still reverted back to 3G. I didn't pay much attention to it as I had to do a format in the steps to follow. Now that I'm back up and running I no longer have VoLTE in the drop down menu? It's the only icon missing. Calls still revert to 3G again. I'm on the boost network which uses Telstra and this phone is listed as compatible for VoLTE with them. I know that it worked in Oreo too.
Click to expand...
Click to collapse
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
ChazzMatt said:
Hmmm.... Sorry, I don't know. But you are back on Australian firmware.
If you wish, you can use the same procedure to downgrade back to Australian Oreo to see if you can get VoLTE back.
H930DS20f_00_OPEN_AU_DS_OP_0408.kdz
https://lg-firmwares.com/downloads-file/19586/H930DS20f_00_OPEN_AU_DS_OP_0408
Click to expand...
Click to collapse
Out of frustration I started doing random things just to test there effect, much of it being in the hidden menu where I discovered VoLTE settings. Nothing was working until... I force stopped the carrier service and made a phone call. Presto! VoLTE now appears (though not listed under any setting in mobile networks, or in the drop down menu) and my calls say HD call. Finally to confirm 4G remains active and still works during a call!
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?