Hello!
It seems like I am one of the few people to have a RS987 variant of the V10. I love everything about this phone, but it's killing me not having root access. I've avoided making a topic dedicated to this variant by posting in other threads and PMing people, but I've gotten nowhere.
I'm unable to unlock the bootloader like the T-Mobile variant even though I have to ability to enable "OEM Unlock" in the dev settings, and I've attempted to flash the Verizon VS990 5.1.1 KDZ to my phone in hopes I could root it after flashing it but it failed.
I'm willing to donate $40 to anybody that can provide a root method for RS987 variant of the V10.
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
SoulAce1290 said:
Check this out.
http://forum.xda-developers.com/lg-...d-lollipop-kdz-10c-lg-servers-t3332348/page15
First post last link.
Click to expand...
Click to collapse
This just the KDZ for stock 5.1.1, which I provided
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
https://mega.nz/#!8k1UyCyC!Z2NIKvNOEkXBiElMLrXkv0RyPKhCN2q0KvlI1OH6ImY
this DZ file with
https://mega.nz/#!xgMgBIQD!VHtXeIlzpPydKRICtGfBUjXvtdN-KNtqX6U9bu3bY8Y
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Succeeded in flashing out.dz ... but
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
WillyPillow said:
I should have posted this earlier but I was kind of busy IRL...
Anyway, it should be noted that I DO NOT have an RS987, therefore THIS HAS NOT BEEN TESTED! The usual disclaimers about voiding your warrenty, bricking your device, killing your cat ...etc applys.
Basically, flash
LINK REMOVED
this DZ file with
LINK REMOVED
this DLL in LGUP.
I did not modify anything except /system, so theoretically you should be able to flash back the stock KDZ in download mode even if you experience bootloops.
Click to expand...
Click to collapse
joatamonk said:
I succeeded in flashing the provided out.dz with LGUP, however, the phone would stall at initial LG logo, and wouldn't make the startup sound or animation.
Flashing back to the stock image for the RS987 worked fine, however. Even the carrier settings stayed.
A this point I can't verify if the bootloader is locked or not, I can't get into fastboot, just LG Download mode. Of course I'd be able to easily enable fastboot if I had root by writing zero's to the LAF partition. Ugh catch 22.
I also tried flashing the VS990 image for verizon pre-rooted system... no luck, LGUP refuses since it's not the same model number. I have a pre-rooted system.img file that I created using the extracted system.img from the stock .kdz. But I have not way to re-pack it into a .kdz or .dz file. Of course, I don't know if my rooted system image would work, since I can't test it.
Love the phone, but I'm so sick of Androids being locked down so tight.
Click to expand...
Click to collapse
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Pre-rooted system.img file for RS987 LG V10
WillyPillow said:
Sorry about that. Too bad I don't have an RS987 to debug the issues. How about you send me your img file and I'll try to pack it for you?
I don't think the bootloader is unlocked for the variants except H960A and the T-Mo one. Also, you can view the bootloader status under the hidden menu.
Click to expand...
Click to collapse
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
@joatamonk
I just remembered what the problem is. I forgot a critical step in making the DZ
Unfortunately, I'm a bit busy recently, and I might not be able to fix this until next week. Sorry to keep you waiting.
joatamonk said:
WillyPillow, thank you for the offer to attempt to repack this system.img file into a .DZ file that'd be flashable to the LG V10 RS987...
I've PM'd you a link to a Google Drive with the rooted system.img
One file is system.rar and has a rooted system.img file that works with the RS987 LG V10.
The other file is RS98711a_02_0309.rar which is where I extracted the stock system.img file from. It was a multi-part system.bin file which I extracted and merged with "WindowsLGFirmwareExtractor".
I used the imgrooter script that worked for rooting my LG G4 phone which also had the same version of Lollipop 5.1.1. With LG G4 I was able to flash the file from download mode by opening a shell prompt with the phone using Send_Command.exe ... I was able to get Send_Command.exe to work with the LG V10, by first unlocking the mode by beginning to flash a .KDZ file and then unplugging the USB cable at the 9% progress mark. At this point I had a shell prompt with the phone. HOWEVER, I had extremely limited commands available. I could list files/folders, and run CAT on any file I wanted, but the command for dd or chmod or chown would all crash my shell prompt with the error "Hello I am LAF nice to meet you." At that point all commands with the phone would cease and go back to displaying "FAIL" for any command. (Really strange. I wish LAF would give me DD command from that shell prompt and I'd tell it where to put my system.img file!)
So, good luck re-packing this system.img back into a .DZ file I can flash.
I'm sure myself and other RS987 owners who frequent this forum would love a pre-rooted flashable system image.
Thanks in advance for your efforts.
Click to expand...
Click to collapse
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
No luck
WillyPillow said:
Sorry about the (extremely) late reply.
Here's the updated DZ:
https://mega.nz/#!VkFlGCRK!tNegI52h6aPNYU98pQ6RISmlr53ok57XHZvjIQZR4xM
Hope it works!
Click to expand...
Click to collapse
I thank you greatly for your efforts, however this .dz file didn't work. It got farther than the last one you had made. After flashing it with LG UP 1.14 the phone would reboot, show the android guy (the one with a spinning gear in it's belly), that screen would stay for about 5 seconds, phone would restart again, and then get stuck on the initial LG power up screen, it never played the startup sound or showed the animated LG logo.
RS987 must be a little different than the Verizon version? Perhaps it only loads signed kernels, or signed images or something?
Is this .dz file made from the pre-rooted image I had uploaded? Is there software that can be used to pack .DZ files from the .img file? So that I can try different methods of rooting system.img and flashing that to the phone?
The good news is the phone works fine after I flashed the stock RS98712a file back to the phone.
Thank you again for your efforts, they're appreciated.
Joata
Subscribed
Related
Hey guys, ive searched the whole day now and have a serious problem with my LG G2 D802 variant..
I tried to flash Paranoid Android 4.0 with TWRP and there was a never ending boot animation, after that I tried to do a factory reset with the LG Flash tool wich stops at 49%.
Now I'm trying to unbrick it with this tutorial but I can't find the .tot file for the D802.
http://optimusforums.com/threads/guide-complete-guide-to-unbrick-your-soft-bricked-g2-f320.9232/
The thing is, I have extracted the .kdz and it outputs a .dz and a .dll when I'm trying to start the flash progress, there is a popup wich says "Failed PriviousLoad()... :/
Could someone please help me out?
Sidenote: I have access to TWRP but sideload wont work(?) adb lists no devices....
i look for it allso
i look for it allso
i have d802 International but without Recovery,and cannot access to fastboot
only TOT will help me.
Please!!! help us...
I think this will help!
dagotal said:
i look for it allso
i have d802 International but without Recovery,and cannot access to fastboot
only TOT will help me.
Please!!! help us...
Click to expand...
Click to collapse
hi i have LG G2 D802 16gb
last week i flashed kitkat rom, but since most of G2 specific apps are lost, i didnot like it and i want to get back to stock.
i get "stuck at %49 error", "page error", "wparam error", ("whatever you call error") all the time while trying to flash d802 stock rom with "R&D tool", i tried on Win8, WinXP..
I changed the USB com port to 4, to 41.. nothing Worked!!!
and at last!..
I ve found a solution...
here it is...
i found the python script, called "KDZFileTools.py" written by someone (called thecubed) in this forum.
thanks him alot!!! and here is the link;
http://forum.xda-developers.com/showthread.php?t=2483250
to make python script file run in Windows go to http://www.python.org and download python 2.7 (NOT 3.x) and install it..
then put .py script file, .kdz file into "c:\python27\" folder (this folder is created default when you install python)
and in command promt type;
python KDZFileTools.py -f D80210B_00.kdz -x
this commands extracts the required .DLL file from .KDZ file, to "c:\python27\kdzextracted" folder, the extracted.dz file is NOT necessary for this tutorial.
and i found a tot file from this link, http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
the one with date: SEP. 7, 2013
i used these two files (DLL i extracted from kdz and tot file) with LG Flashtool v.1.5, you can find it here:
http://forum.xda-developers.com/showthread.php?t=2475045
if you fallow the steps explained here,
http://forum.xda-developers.com/showthread.php?t=2475045
with the DLL (extracted from your phones .KDZ file)
and
.tot file given above
YOU WILL GET STOCK ROM BACK!! i did these and get mine back!!
warning that I'm not responsible for you messing with your phone
hope this helps..
please inform me if you succeed.
.tot file for D80210e_EUR_XX
Are any of .tot files from link above compatible with phone running stock d80210e_eur_xx, so 32Gb version? Or can I just use the one which is for 32Gb version (using .dll from d80210e_eur_xx.kdz and .tot from d80210b_sea_xx) and then use .kdz method with d80210e_eur_xx.kdz to get my carriers official ROM? Thank you in advance!
Worked perfectly
tanerf82_ said:
hi i have LG G2 D802 16gb
last week i flashed kitkat rom, but since most of G2 specific apps are lost, i didnot like it and i want to get back to stock.
i get "stuck at %49 error", "page error", "wparam error", ("whatever you call error") all the time while trying to flash d802 stock rom with "R&D tool", i tried on Win8, WinXP..
I changed the USB com port to 4, to 41.. nothing Worked!!!
and at last!..
I ve found a solution...
here it is...
i found the python script, called "KDZFileTools.py" written by someone (called thecubed) in this forum.
thanks him alot!!! and here is the link;
http://forum.xda-developers.com/showthread.php?t=2483250
to make python script file run in Windows go to http://www.python.org and download python 2.7 (NOT 3.x) and install it..
then put .py script file, .kdz file into "c:\python27\" folder (this folder is created default when you install python)
and in command promt type;
python KDZFileTools.py -f D80210B_00.kdz -x
this commands extracts the required .DLL file from .KDZ file, to "c:\python27\kdzextracted" folder, the extracted.dz file is NOT necessary for this tutorial.
and i found a tot file from this link, http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
the one with date: SEP. 7, 2013
i used these two files (DLL i extracted from kdz and tot file) with LG Flashtool v.1.5, you can find it here:
http://forum.xda-developers.com/showthread.php?t=2475045
if you fallow the steps explained here,
http://forum.xda-developers.com/showthread.php?t=2475045
with the DLL (extracted from your phones .KDZ file)
and
.tot file given above
YOU WILL GET STOCK ROM BACK!! i did these and get mine back!!
warning that I'm not responsible for you messing with your phone
hope this helps..
please inform me if you succeed.
Click to expand...
Click to collapse
Thanks man, I had some problems with the LG UpTestEX software, and your method worked perfectly !
I made a successful downgrade with a D802 (4.4.2 Vodaphone to 4.2.2 JDQ39B) :victory:
When all else failed... this worked.
With correct dll and tot files... this worked a treat.
Thanks for all the work guys
tanerf82_ said:
hi i have LG G2 D802 16gb
last week i flashed kitkat rom, but since most of G2 specific apps are lost, i didnot like it and i want to get back to stock.
i get "stuck at %49 error", "page error", "wparam error", ("whatever you call error") all the time while trying to flash d802 stock rom with "R&D tool", i tried on Win8, WinXP..
I changed the USB com port to 4, to 41.. nothing Worked!!!
and at last!..
I ve found a solution...
here it is...
i found the python script, called "KDZFileTools.py" written by someone (called thecubed) in this forum.
thanks him alot!!! and here is the link;
http://forum.xda-developers.com/showthread.php?t=2483250
to make python script file run in Windows go to http://www.python.org and download python 2.7 (NOT 3.x) and install it..
then put .py script file, .kdz file into "c:\python27" folder (this folder is created default when you install python)
and in command promt type;
python KDZFileTools.py -f D80210B_00.kdz -x
this commands extracts the required .DLL file from .KDZ file, to "c:\python27\kdzextracted" folder, the extracted.dz file is NOT necessary for this tutorial.
and i found a tot file from this link, http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
the one with date: SEP. 7, 2013
i used these two files (DLL i extracted from kdz and tot file) with LG Flashtool v.1.5, you can find it here:
http://forum.xda-developers.com/showthread.php?t=2475045
if you fallow the steps explained here,
http://forum.xda-developers.com/showthread.php?t=2475045
with the DLL (extracted from your phones .KDZ file)
and
.tot file given above
YOU WILL GET STOCK ROM BACK!! i did these and get mine back!!
warning that I'm not responsible for you messing with your phone
hope this helps..
please inform me if you succeed.
Click to expand...
Click to collapse
Thank you for this great tutorial, I have a query though. The TOT files provided in the link, are they generic? I have the same phone but the 32gb variant. Can i extract the DLL and then flash the 32gb TOT on tmy LG G2 D802 International variant?
bidsar.k said:
Thank you for this great tutorial, I have a query though. The TOT files provided in the link, are they generic? I have the same phone but the 32gb variant. Can i extract the DLL and then flash the 32gb TOT on tmy LG G2 D802 International variant?
Click to expand...
Click to collapse
It was a "bit" long time ago I dont remember exactly what the issue really was. But i think "memory variant" wouldnot be important for dll.. give it a try, it should work..
tanerf82_ said:
It was a "bit" long time ago I dont remember exactly what the issue really was. But i think "memory variant" wouldnot be important for dll.. give it a try, it should work..
Click to expand...
Click to collapse
Thanks for the reply. So should i extract the DLL from the stock KDZ and the flash the 32gb TOT from that link? Are you sure it won't mess things up more?
I badly want to fix this issue or else i would have to pay a hefty amount to my friend. I just want to be sure i dont render it completely dead.
By the way, are those TOTs carrier specific?
After installing a KK beta build rom I noticed my cell service was disabled so I checked the settings/status and everything showed up
as unknown including imei. Here's the full process I went through until finally fixing/restoring service on my phone.
NOTE: all of this was possible because I still had two very important files called modemst1.img and modemst2.img
these are what hold the important info about the phone including imei and such. Luckily @autoprime has a script in ioroot that'll backup
these files if you're on JB but if you're on KK you have to MANUALLY back them up. With that being said if you don't have these files
then this guide isn't for you.
So the first thing I tried (after restoring my nandroid backup which I found out didnt backup those modemst files) was take the two modemst files from my ioroot folder on my computer and putting them on the internal storage of the phone in a folder called EFS_Backup. I renamed the two files to efs1.img and efs2.img (if you don't have the option to show the files extension in the name enabled then you would just type in efs1 and efs2 or else the filename would end up efs1.img.img etc.) After that I put the phone into recovery (twrp) and plugged the usb cable. Then I ran cmd as administrator and typed these commands:
adb shell
su
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
It said that it copied them however I checked the folder with root browser and it still showed the empty modemst files (my backup ones were 3mb). So I tried the commands while the phone was booted up I granted root access and it said it copied again but still nothing. Around this time I got into a bootloop and was getting stuck so I flashed a KK baseband which helped me at first. At this point @dr87 gave me a flashable efs zip file to use which I'm going to attach to this post. To use it you have to drag your two modemst backups into it name then efs1 and efs2 then flash the zip in recovery.
Like the other steps though that didnt seem to replace the modemst files and I was stuck without service. I then got a bootloop again and tried flashing my nandroid backup with the KK baseband but this time it wouldn't work so I went back to the KK beta build so I could boot up again. I tried running the dd commands again this time with the efs files on the root directory on the internal storage of the phone. The command I used for that was this:
dd if=/sdcard/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
I got the same results as before. However another member said something about running the dd commands in stock recovery so I decided to do a zvc tot and try running the dd commands in the stock recovery. I downloaded the zvc tot from here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
I extracted the tot from the zip file and put it on my desktop and then I followed the sprint version of this guide:
http://forum.xda-developers.com/showthread.php?t=2432476
Scroll down to the part where it says RETURN TO STOCK TOT Method! AT&T & Sprint Verzion & The Few International TOTs I have available
Follow those instructions there however after step number 10 where you set your G2's port to COM 41 turn off and unplug your phone then after 13 where you click the yellow arrow in LG Flash Tool put your G2 back into download mode and the Flash Tool will then connect to your device and start the process. Once that was finished I went through the setup and was about to reboot to get to stock recovery when I noticed something.......MY CELL SERVICE WAS BACK!!!! Apparently with the custom roms replacing the modemst files didn't stick but after moving to stock zvc it seemed to replace it and I'm now back up and running. If you have any questions let me know and I'll get back to you as soon as I can. Wish you all the best.
P.S. I would like to give a very big thanks to @GizmoKaca he really helped me alot through this whole process.
OfficialPerson said:
After installing a KK beta build rom I noticed my cell service was disabled so I checked the settings/status and everything showed up
as unknown including imei. Here's the full process I went through until finally fixing/restoring service on my phone.
NOTE: all of this was possible because I still had two very important files called modemst1.img and modemst2.img
these are what hold the important info about the phone including imei and such. Luckily @autoprime has a script in ioroot that'll backup
these files if you're on JB but if you're on KK you have to MANUALLY back them up. With that being said if you don't have these files
then this guide isn't for you.
So the first thing I tried (after restoring my nandroid backup which I found out didnt backup those modemst files) was take the two modemst files from my ioroot folder on my computer and putting them on the internal storage of the phone in a folder called EFS_Backup. I renamed the two files to efs1.img and efs2.img (if you don't have the option to show the files extension in the name enabled then you would just type in efs1 and efs2 or else the filename would end up efs1.img.img etc.) After that I put the phone into recovery (twrp) and plugged the usb cable. Then I ran cmd as administrator and typed these commands:
adb shell
su
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
It said that it copied them however I checked the folder with root browser and it still showed the empty modemst files (my backup ones were 3mb). So I tried the commands while the phone was booted up I granted root access and it said it copied again but still nothing. Around this time I got into a bootloop and was getting stuck so I flashed a KK baseband which helped me at first. At this point @dr87 gave me a flashable efs zip file to use which I'm going to attach to this post. To use it you have to drag your two modemst backups into it name then efs1 and efs2 then flash the zip in recovery.
Like the other steps though that didnt seem to replace the modemst files and I was stuck without service. I then got a bootloop again and tried flashing my nandroid backup with the KK baseband but this time it wouldn't work so I went back to the KK beta build so I could boot up again. I tried running the dd commands again this time with the efs files on the root directory on the internal storage of the phone. The command I used for that was this:
dd if=/sdcard/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
I got the same results as before. However another member said something about running the dd commands in stock recovery so I decided to do a zvc tot and try running the dd commands in the stock recovery. I downloaded the zvc tot from here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
I extracted the tot from the zip file and put it on my desktop and then I followed the sprint version of this guide:
http://forum.xda-developers.com/showthread.php?t=2432476
Scroll down to the part where it says RETURN TO STOCK TOT Method! AT&T & Sprint Verzion & The Few International TOTs I have available
Follow those instructions there however after step number 10 where you set your G2's port to COM 41 turn off and unplug your phone then after 13 where you click the yellow arrow in LG Flash Tool put your G2 back into download mode and the Flash Tool will then connect to your device and start the process. Once that was finished I went through the setup and was about to reboot to get to stock recovery when I noticed something.......MY CELL SERVICE WAS BACK!!!! Apparently with the custom roms replacing the modemst files didn't stick but after moving to stock zvc it seemed to replace it and I'm now back up and running. If you have any questions let me know and I'll get back to you as soon as I can. Wish you all the best.
P.S. I would like to give a very big thanks to @GizmoKaca he really helped me alot through this whole process.
Click to expand...
Click to collapse
I have exactly the same issue and can't do anything. Phone boots up fine but no cell or data. I don't have those 2 files...is it something I can download? I really need help. I'm so frustrated, especially because it's my FRIEND's phone. Help me, please!
See this: http://forum.xda-developers.com/spr...nal-please-t2814919/post54122384#post54122384
THANK YOU!!!!
im sorry, but those files are unique to each phone, each one is different. It is not something you can download. Best thing to try is tot back to 100% stock, then hope he has insurance on the phone and take it to a repair center, once they determine it cant be fixed, they will order a replacement (or give you one), if he doesnt have insurance, hope its under warranty and do a RMA to LG
LoveistheGroove said:
I have exactly the same issue and can't do anything. Phone boots up fine but no cell or data. I don't have those 2 files...is it something I can download? I really need help. I'm so frustrated, especially because it's my FRIEND's phone. Help me, please!
See this: http://forum.xda-developers.com/spr...nal-please-t2814919/post54122384#post54122384
THANK YOU!!!!
Click to expand...
Click to collapse
I'm sorry to hear about your predicament. When you rooted your phone did you use ioroot? What version were you on when you rooted i.e. Jelly Bean, Kit Kat, etc.?
OfficialPerson said:
I'm sorry to hear about your predicament. When you rooted your phone did you use ioroot? What version were you on when you rooted i.e. Jelly Bean, Kit Kat, etc.?
Click to expand...
Click to collapse
I was on KK. Used AutoRec for TWRP.
LoveistheGroove said:
I was on KK. Used AutoRec for TWRP.
Click to expand...
Click to collapse
Autorec and twrp are different then ioroot which is rooting. But since you were on KK then I'm pretty
sure when you rooted it didn't automatically backup your EFS files. When you go into settings to where
it say PRL, IMEI, MEID, etc. does it say unknown for all of them? Or do some of they have numbers and
stuff?
OfficialPerson said:
Autorec and twrp are different then ioroot which is rooting. But since you were on KK then I'm pretty
sure when you rooted it didn't automatically backup your EFS files. When you go into settings to where
it say PRL, IMEI, MEID, etc. does it say unknown for all of them? Or do some of they have numbers and
stuff?
Click to expand...
Click to collapse
I used iroot and all of those are blank or unknown
Is it really that easy to permanently ruin a phone? Wow.
I'm sure it is, I just can't believe it's impossible to fix.
LoveistheGroove said:
I used iroot and all of those are blank or unknown
Is it really that easy to permanently ruin a phone? Wow.
I'm sure it is, I just can't believe it's impossible to fix.
Click to expand...
Click to collapse
Hmm ok and yeah things can go down south very easily which is why they put
warnings all the time but people (including myself) usually take them lightly lol.
However it may not be permanently ruined I read a post a couple days ago about
someone taking the optimus g and writing the prl imei and other info himself with
certain programs. He mentioned ways to get those numbers for your specific phone
I'm not exactly sure if it'll work but it may be your only option at this point. I'm going
to see if I can find the post again and put the link here. This is a pretty advanced
process though I've never done it myself so don't really know that much about it.
If anything though are you insured?
OfficialPerson said:
Hmm ok and yeah things can go down south very easily which is why they put
warnings all the time but people (including myself) usually take them lightly lol.
However it may not be permanently ruined I read a post a couple days ago about
someone taking the optimus g and writing the prl imei and other info himself with
certain programs. He mentioned ways to get those numbers for your specific phone
I'm not exactly sure if it'll work but it may be your only option at this point. I'm going
to see if I can find the post again and put the link here. This is a pretty advanced
process though I've never done it myself so don't really know that much about it.
If anything though are you insured?
Click to expand...
Click to collapse
Thank you and please do if you can. I know the codes to program them. I just don't have them.
I have insurance. Last effort though.
Please share if you can!
Billy
LoveistheGroove said:
Thank you and please do if you can. I know the codes to program them. I just don't have them.
I have insurance. Last effort though.
Please share if you can!
Billy
Click to expand...
Click to collapse
Here's the post the section I was referring to is repairing EFS.
http://forum.xda-developers.com/showthread.php?t=2161498
OfficialPerson said:
After installing a KK beta build rom I noticed my cell service was disabled so I checked the settings/status and everything showed up
as unknown including imei. Here's the full process I went through until finally fixing/restoring service on my phone.
NOTE: all of this was possible because I still had two very important files called modemst1.img and modemst2.img
these are what hold the important info about the phone including imei and such. Luckily @autoprime has a script in ioroot that'll backup
these files if you're on JB but if you're on KK you have to MANUALLY back them up. With that being said if you don't have these files
then this guide isn't for you.
So the first thing I tried (after restoring my nandroid backup which I found out didnt backup those modemst files) was take the two modemst files from my ioroot folder on my computer and putting them on the internal storage of the phone in a folder called EFS_Backup. I renamed the two files to efs1.img and efs2.img (if you don't have the option to show the files extension in the name enabled then you would just type in efs1 and efs2 or else the filename would end up efs1.img.img etc.) After that I put the phone into recovery (twrp) and plugged the usb cable. Then I ran cmd as administrator and typed these commands:
adb shell
su
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
It said that it copied them however I checked the folder with root browser and it still showed the empty modemst files (my backup ones were 3mb). So I tried the commands while the phone was booted up I granted root access and it said it copied again but still nothing. Around this time I got into a bootloop and was getting stuck so I flashed a KK baseband which helped me at first. At this point @dr87 gave me a flashable efs zip file to use which I'm going to attach to this post. To use it you have to drag your two modemst backups into it name then efs1 and efs2 then flash the zip in recovery.
Like the other steps though that didnt seem to replace the modemst files and I was stuck without service. I then got a bootloop again and tried flashing my nandroid backup with the KK baseband but this time it wouldn't work so I went back to the KK beta build so I could boot up again. I tried running the dd commands again this time with the efs files on the root directory on the internal storage of the phone. The command I used for that was this:
dd if=/sdcard/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
I got the same results as before. However another member said something about running the dd commands in stock recovery so I decided to do a zvc tot and try running the dd commands in the stock recovery. I downloaded the zvc tot from here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
I extracted the tot from the zip file and put it on my desktop and then I followed the sprint version of this guide:
http://forum.xda-developers.com/showthread.php?t=2432476
Scroll down to the part where it says RETURN TO STOCK TOT Method! AT&T & Sprint Verzion & The Few International TOTs I have available
Follow those instructions there however after step number 10 where you set your G2's port to COM 41 turn off and unplug your phone then after 13 where you click the yellow arrow in LG Flash Tool put your G2 back into download mode and the Flash Tool will then connect to your device and start the process. Once that was finished I went through the setup and was about to reboot to get to stock recovery when I noticed something.......MY CELL SERVICE WAS BACK!!!! Apparently with the custom roms replacing the modemst files didn't stick but after moving to stock zvc it seemed to replace it and I'm now back up and running. If you have any questions let me know and I'll get back to you as soon as I can. Wish you all the best.
P.S. I would like to give a very big thanks to @GizmoKaca he really helped me alot through this whole process.
Click to expand...
Click to collapse
__________________________________________________________________________________________________________________
I think I have great news. I looked in my ioroot folder and found both of the files (3 MB each) that are modemst1.img and modemst2.img.
I created a folder on the Internal called EFS_Backup, and I copied and pasted those two files into the new folder, renaming them efs1 and efs2. They renamed and stuck in the folder just fine, but running the ADB commands didn't work. So I used the flashable EFS zip in TWRP and it said FAILED.
I'm thinking since I have these 2 files I should be able to fix this, right???? But...the thing that's driving me nuts is that LG Flash Tool, no matter what version, will NOT work on my device anymore. Not with either of my PC's.
Does anyone have a suggestion for what to do now that I found those modem files in my ioroot folder?
I feel like this is the closest I have gotten and now I'm stuck. LG Flash Tools never worked on Windows 8. The OLDER versions worked fine with .tot files BEFORE all of this happened, in Windows 7. Now even Windows 7 won't work to use LG Flash Tools, after I created this mess.
Can anyone PLEASE help me take these 2 files and get them to fix my EFS? I really don't know what I'm doing, clearly, or I would have backed up my EFS first. Problem here is probably same everywhere...I've always done this, never bothered with Nandroid or EFS backups, but also never had the issue of only having an internal memory on an Android device. Stupid mistake.
I would greatly appreciate any help that can be offered. I have one more day and I can still take this phone back...IF I can fix it. Thank you in advance!
PS: I Have my ESN, MEID HEX, MEID DEC, IMEI, ICCID AND IMSI - ALL POPULATED WITH NUMBERS IN SETTINGS. WHAT IS "UNKNOWN" IS MY PHONE NUMBER AND MY PRL.
I have the LG v10 from T-Mobile. I bought the phone a few weeks ago and it had Marshmallow installed. Somehow I managed to install TWRP/SuperSU, but then had issues and flashed the official/stock MM image with LGUP. Afterwards I discovered that MM for this device is not currently rootable, and TWRP cant be flashed via fastboot because MM blocks it. So I returned the device to T-Mo store, lied and said it force-upgrade to MM and had began freezing up. They did an in-store trade for an identical model that had 5.1.1 Lollipop.
The device is currently still in factory condition in every way, with the exceptions that I unlocked the bootloader via fastboot and installed TWRP. Nothing else is modified yet and no custom ROMs have been flashed.
I recently became aware that there is no stock LP image for the T-Mo v10, only MM images are available. After all the issues I've had, I'm now paranoid and want to have a complete dump of the phone's entire contents (partitions, bootloader, system, etc) that is in KDZ or TOT format, and can be reflashed with the standard tools available. Since there is nothing official then I would have to do this myself. This would be useful in the event that I run into lots of issues and need to do a emergency stock restore.
I found a thread by XDA user @tungkick, in which he created a modified dump of the device while it was running LP. However, because it was unofficial and he didn't disclose this upfront, his thread was shut down. His file bricked multiple MM users. I assume it would work if one was still on LP and hadn't upgraded to MM. Not to mention that I cant seem to find his file anywhere. So I figure the safest way is to do this myself. I would be willing to make this file available to the community when finished, with full disclosure that it is unofficial. But the problem is, I don't know how.
I know that the Linux dd command can be used to dump images of various things, and I have read that this can be done on PC by connecting to the device via ADB or fastboot. This would hopefully result in an image file that contained the contents of all the device's partitions.
But another issue would be converting it to KDZ or TOT. And it would have to be done in such a way that it would be flashable with the standard tools.
Can someone please give me a technical understanding of the tools and knowledge I would need to undertake this? Would it be too complicated for someone like myself that has little Android/Linux experience (but is generally competent with computers/technology)?
Thanks for any advice!
Noone can help me with this?
To the mods/admins: I think maybe I posted this in an area where it is unlikely to get any useful answers. Can someone move the thread to the Help& Troubleshooting area of the general LG v10 forum (not here in the T-Mobile subforum)? Thanks!
I think it's just that if that could. have been done someone would have done it already. Even tungkick didn't make one for tmobile for some reason. I think because he made his root injected files from official lg files and lg has not released a kdz or tot for tmobile LP.
Just my observation... I could be wrong.
Sent from my pretty nifty brand new LG V10
@ planetbeen: I don't see why it wouldn't be possible. Linux's dd program can dump almost any connected device that it can see. But then it needs to be converted into a standard TOT/KDZ that can be flashed with any standard software. Which is why I want to create an unofficial backup of the entire phone before modifying it further, so I can do an emergency restore if necessary. I just need the right instructions from people who have the technical expertise.
I had trouble with my old LG v10, I had used LG's LGUP program to flash it to Marshmallow from my PC, only to realize that it couldn't be rooted or have a custom recovery. And I also discovered that I couldn't downgrade to Lollipop. So I returned the phone to the store and exchanged it for an identical model that still had LP. I just told them it had auto-upgraded to MM and started crashing. They exchanged, no questions. Before this I had various issues, like GPS crashing randomly when turning it on, Bluetooth also doing the same thing, and the Settings app also crashed sometimes when accessing the Security menu. I had flashed multiple ROMs, but stock-based and CM/AOSP-based, but kept running into issues, oftentimes the same ones. So I figured that something in the phone had become corrupt and figured that flashing stock MM would fix everything. Big mistake. I'll never let this phone upgrade again until MM is solidly hacked, which from what I've read may be a long time away. I paid enough for this phone and I really value hackability. I'm not the average Joe that just uses my phone for Facebook, etc. To me, if a phone cant be hacked, then buying/owning it is a waste of time/money. Same thing with every computer/electronics device I've ever owned.
Thanks again!
It looks like I'm going to have problems getting answers from knowledgable people, so instead of waiting, I'm going to take a little initiative and at least try to do the dump with dd. I found a post by @tungkick that says to enable USB debugging and make a backup file via dd with the 'adb shell' and 'su' commands. Is the following syntax correct?
dd if=/dev/block/mmcblk0 of=/sdcard/H901.bin bs=1024 count=6291456
Do I run these commands from a PC via command line while connected via USB? Or directly on the device in a terminal emulator? Or do I need to run the command while in fastboot/bootloader mode, while Android is powered down?
Thanks again!
Stock use tool extract kdz then choose file dz (use lgup)
remember can not flash if phone update 6.0
Never downgrade because phone brick now.
version 5.1.1
https://drive.google.com/file/d/0B_Hol5T47S-bQkJVemgzMDV0Nzg/view?usp=sharing
@ tungkick: Thanks for the info. I had used the dd command to dump my phone to external SD before, but the file was 6GB! I was unable to use Tool KDZ Extract to extract the *.dz from the *.kdz file you provided. I was able to flash your KDZ with LGUP, but it boots me into TWRP recovery near the end.
Do you mind if I publicly distribute a mirror copy of your file on my Dropbox, so that it will be available to others that need the stock LP firmware for this device?
Thanks again!
I just wanted to say that flashing your KDZ has possibly screwed up my device permanently. Your image has TWRP, not the stock recovery, and is pre-rooted with SuperSU. Normally this would be good but...............
Near the end of LGUP, the device boots into TWRP. System and MicroSD are mounted, but nothing else (data, cache, dalvik, etc). I was able to obtain a stock recovery *.img, then copied it over to my MicroSD while in recovery. Then I flashed it, booted the phone into stock recovery, and performed a factory reset. Afterwards I booted into system, and all looked good, until it got to the "Checking connection" screen, then a lot of apps started force-closing repeatedly. Because of this I can't get to the Home screen, and no amount of factory reset is working. It just keeps happening over and over again.
How to get out of this mess, anyone?
Help please!!!
Still looking for a solution and would really appreciate any help!
My theory is that the /cache and /data partitions somehow got corrupted during the flash. So I tried booting into FastBoot mode and issueing the commands:
fastboot erase cache
fastboot format cache
fastboot erase userdata
fastboot format userdata
It just says something something along the lines of "remote: cant format/erase in an unlocked state". If I relock the bootloader, it says that it cant erase/format in a locked state.
TWRP still cant read those partitions (they won't mount and cant be mounted), and the apps still start force-closing almost immediately after rebooting into system, before I can complete the setup, preventing me from getting to the home screen.
@ tungkick: Is there any possibility we can arrange a TeamViewer meeting to fix this?
Thanks!
The pdf's that give instructions on rooting/twrp etc have already been updated to 20j (at least "step 3" has. I'm on stock 20e and all I want to do at the moment is add twrp so I can make a "vanilla" backup to restore to. Where can I find the tot file for 20e twrp?
Also, can anyone point to a file that has the 20e boot but has removed the corruption nag?
I prefer to stay with 20e for now and not jump to 20j.
famewolf said:
The pdf's that give instructions on rooting/twrp etc have already been updated to 20j (at least "step 3" has. I'm on stock 20e and all I want to do at the moment is add twrp so I can make a "vanilla" backup to restore to. Where can I find the tot file for 20e twrp?
Also, can anyone point to a file that has the 20e boot but has removed the corruption nag?
I prefer to stay with 20e for now and not jump to 20j.
Click to expand...
Click to collapse
Hello famwolf,
You should post this where you downloaded the pdf files from. Now with that said, you are fortunate that I am the person who wrote those pdf files so I do have the old links to the 20e files:
20e .KDZ file:
H90120e_00_0316.kdz
20e .TOT File:
LGH901AT-00-V20e-TMO-US-MAR-16-2016-ARB01+0.rar
The only way to get rid of the annoying "corrupt file message" is to re-lock the boot loader by running the following command while in fastboot mode: fastboot oem lock
If you still have the old pdf file with the old links, why can't you just use that one? The links to all of the files still work. I'm curious as to why you do not want to upgrade to the 20j version. So far it is solid and it fixed the nasty GPS issue along with giving better battery life. Just in case you do not have a copy of the old pdf file, I have attached it to this post.
jun19inf said:
Hello famwolf,
You should post this where you downloaded the pdf files from. Now with that said, you are fortunate that I am the person who wrote those pdf files so I do have the old links to the 20e files:
20e .KDZ file:
H90120e_00_0316.kdz
20e .TOT File:
LGH901AT-00-V20e-TMO-US-MAR-16-2016-ARB01+0.rar
The only way to get rid of the annoying "corrupt file message" is to re-lock the boot loader by running the following command while in fastboot mode: fastboot oem lock
If you still have the old pdf file with the old links, why can't you just use that one? The links to all of the files still work. I'm curious as to why you do not want to upgrade to the 20j version. So far it is solid and it fixed the nasty GPS issue along with giving better battery life.
Click to expand...
Click to collapse
I greatly appreciate your time! I just recently purchased a refurb V10 and it came with 6.0 20e. The only copy of the pdf's I had at the time of my post were the ones in your thread which point to 20j for the step 3. I've since acquired a copy of the 20e documents from a friend who also has a V10 and has had it much longer than me. My goal is to make a twrp backup and then root it...make another backup etc...labelled and offloaded to my freenas server for safe keeping.
As to relocking the bootloader I have a couple of questions.
1) Does relocking the bootloader reset the phone back to factory the same as unlocking does?
2) Will I have to unlock every time I want to upgrade TWRP (and deal with it resetting everything again)?
I read somewhere here on the v10 forum (I've been reading up for 2 weeks in advance) that there is a modified boot which gets rid of the corruption nag but have no idea where I saw it mentioned.
If it improves the battery life then perhaps I need to reconsider using 20j. One reason I hesitated is because I don't see it showing up as an offered update via OTA on my currently "factory" V10.
famewolf said:
I greatly appreciate your time! I just recently purchased a refurb V10 and it came with 6.0 20e. The only copy of the pdf's I had at the time of my post were the ones in your thread which point to 20j for the step 3. I've since acquired a copy of the 20e documents from a friend who also has a V10 and has had it much longer than me. My goal is to make a twrp backup and then root it...make another backup etc...labelled and offloaded to my freenas server for safe keeping.
As to relocking the bootloader I have a couple of questions.
1) Does relocking the bootloader reset the phone back to factory the same as unlocking does?
2) Will I have to unlock every time I want to upgrade TWRP (and deal with it resetting everything again)?
I read somewhere here on the v10 forum (I've been reading up for 2 weeks in advance) that there is a modified boot which gets rid of the corruption nag but have no idea where I saw it mentioned.
If it improves the battery life then perhaps I need to reconsider using 20j.
Click to expand...
Click to collapse
Hello again famewolf,
Re-locking the boot loader does reset the phone and you will have to unlock it everytime to flash any rom stock or custom. I don't believe I've read anything about having a modified image that gets rid of the nagging corrupt message but I'll dig around and see what I can find. As to the battery life, it has greatly improved (for me at least). There were situations where for no reason the phone would get hot and drain the battery now it does not happen. Not to mention that the update fixes that nasty quad root exploit so that's another thing to think about right there. Either way, glad I could help.
General question here. I just got the phone today and am on 20e. It won't let me update to 20j even though I see it available because I assume A. I'm not charged to 100 percent and B. I'm using a metro pcs SIM instead of T-Mobile.......so can I just follow the instructions to root for 20j......will they upgrade me to 20j through the root process basically?
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
bennylava said:
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
Click to expand...
Click to collapse
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
eduardvi995 said:
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
Click to expand...
Click to collapse
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't get that LG program, LGup, to flash 7.0 to the phone. It gives me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
bennylava said:
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't that LG program, LGup, to flash 7.0 to the phone. It give me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
Click to expand...
Click to collapse
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
eduardvi995 said:
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
Click to expand...
Click to collapse
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
bennylava said:
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
Click to expand...
Click to collapse
Its seems you were lucky enough. I checked your rom build and compared it with the only rom on your phone that can be rolled back. It totally matchs the anti-rollback v01 firmware 8.0, so you still can roll-back to Nougat if you try the firmware version H83020c, wich you can download over here:
Fastboot-Flashable rom:
Codefire - Listing of H83020c
KDZ Format rom:
http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=FWAAZHZF92MNARE76685PNJ/H83020o_00_0205.kdz
Its seems the first one it's Fastboot-Flashable, so you should know what to do next if the KDZ Rom doesn't work. However, check this website and compare the rom build yourself, just to be clear about it:
Download T-mobile LG G5 H830 Stock kdz firmware H83030C
Download T-mobile LG G5 H830 Stock kdz firmware H83030C -
www.mylgphones.com
The first link has 3 flashable roms there. including KDZ and fastboot format. Make sure to try them all if one doesnt work
If both methods are useless to roll back to Nougat, dont hesitate to tell me. There's still a workaround available.
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
bennylava said:
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
Click to expand...
Click to collapse
It needs to be in firmware update mode only if you are flashing a kdz rom through Lg official flashtool. If you are going to flash through fastboot, you have to make sure your PC recognizes your device sending "fastboot devices". The fastboot flashable room is right in the first link (.zip file, 1,6 GB size file)
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
bennylava said:
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
Click to expand...
Click to collapse
That should be it. Download it and check it has all partitions (boot, system, recovery, etc...)
You are probably gonna have to flash each partition manually (for example, if you are flashing system, you should write "fastboot flash system system.img" and so on)
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
{
"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"
}
bennylava said:
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
Click to expand...
Click to collapse
You don't have to write "fastboot flash" 28 times. You can just write "fastboot flash all". But I'd rather flashing manually.
Ignore the META-INF folder. You can't flash any file inside there. You should only flash every file ending in "xx. Img* such as boot.img or. system.img.
This zip contains that folder because it was meant to be flashed through recovery, but if you try to do that, the recovery will not do it, or it will cancel installation, as there is a line that checks your actual fingerprint to avoid Rolling back.
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
bennylava said:
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
Click to expand...
Click to collapse
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
I've bought two H830's and got both to TWRP/LOS ROM no problem. Regardless of your current official build on your phone, you can rollback to version 30c and dirtycow from there to get TWRP. You can get necessary tools/info from here.
0. (If you havn't already...) Enable OEM unlock in settings and unlock bootloader/fastboot
1. Use LGUP tool to clean flash an official 30c version (H83030c_00_0813.kdz) build to your LG H830
2. Dirtycow exploit to get TWRP
3. Use TWRP to install
Let me know how it shakes out
Also an important note, you CANNOT flash directly the recovery via fastboot to get TWRP, only the H850 can do that, NOT the H830. That's something important no one ever brings up. You must use the dirtycow exploit.
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
eduardvi995 said:
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
Click to expand...
Click to collapse
So just put the zip file on my external SD card, and then tell flashboot to...? Or somehow use only the phone itself to flash the rom? Sorry I'm afraid I'm having trouble following along as I've never done this before.
But as per your instructions, the rom (the whole zip file) is now on the external storage SD Card.
Or did you mean to extract the zip file to a folder, and put that on the SD card? My next question would be thus:
What is the exact command to begin flashing, once I have everything in it's proper place? I did a little experiment where I tried to flash one of the files individually. The Linux terminal gave me the following error:
[[email protected] Desktop]$ cd bootloader
[[email protected] bootloader]$ fastboot flash aboot.img
unknown partition 'aboot.img'
fastboot: error: cannot determine image filename for 'aboot.img'
[[email protected] bootloader]$
As you can see, the bootloader folder is on the desktop, with many .img files inside it. Just as the pic in post #11 shows. Inside the bootloader folder is a .img file called "aboot.img". And for some reason fastboot "cannot determine the image filename for aboot.img"
DrowningInFreedom said:
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
Click to expand...
Click to collapse
Thank you for the reply! I've got two questions for you:
1. Do you have a link to the version of LG UP that you'd recommend using? It seems that there are many links out there in the wild, and some of them are to old versions. I'm not sure exactly which one I should use.
2. How exactly do you use Uppercut with LG Up? I got Uppercut, but it didn't seem to do anything when I double clicked on it. It just sat there. Is it like some kind of addon or modification to LG up? Or is it supposed to open as it's own program. Thanks!
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
DrowningInFreedom said:
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
Click to expand...
Click to collapse
Here's what happened when I tried to flash the right 80320a file (Nougat):
Any idea why it would say that?