[Help!!] How to Unbrick Metro PCs LG K7 LGMS330!!

Search This thread

juggalodrew

Member
Jan 4, 2013
23
2
Welland
so i have a k7 and its working unlocked but no matter what i or my phone provider can get mms to work with out having to switch back n forth from mms to internet so i tried the lgup tool flashed the stock rom but it kills my phone every time im lucky to have got 5 motherboards for my phone but anyone tell me what i might be doing wrong it either gets stuck at metro pcs screen or wont turn back on i have gone through 2 boards already once i rooted with kingo root installed super su did its updates and reboot bam stuck metro pcs screen the second i flashed stock rom with lgup it said all went well but phone would not turn on any ideas
 

XannyGvd

New member
Jun 19, 2017
4
0
I have no pc to unbrick my metro pcs lg k7

Can someone please help me unbrick my metro PS LG K7 ?! I have no PC to unbrick any help will be much appreciated !!!
 

gportillo

Member
Sep 13, 2015
6
0
help

i have a lg ms330 metroPCS , try to flash with the wrong version and hard brick, no response only appears on pc qualcomm hs 9008

the correct version firmware is ms33010h

but researching, i found two scripts in phyton how part of solution for unbrick, for to generate the rawprogram0.xml, path0. according to firmware of device for flashing with qfil, but i discover that i have to generate the program_firehose_8909.mbn for write on eMMC i tired with others firehose program, but wihtout done process

im researching how to generate the firehose file....

sorry for my bad english..

best regards.
 

nikonsevast

Member
Dec 3, 2010
6
0
k7 isnt recognized

i know its old phone but my pall brought it from usa , its k7 k330tn tmobile version. And off course its locked on tmobile. I try to unlock the phone but no luck. Actually i did manage to unlock bootloader ,adb shell,root it and also managed to install metro pcs software on it with custom recovery. after that i try to update recovery and kingo root ,and thats was a mistake , cause phone is now in botloop state and none of unbricking ways doesnt work. LG UP want recognize (unkown model), uppercut didnt help also,flash tool had some issues, xda realese of flash tool says s fail to load etc... Only tool which find some info about phone is lg mobile support tool , but i can not do anything with that. So please HELP ? but i think i try almost everything.
 

gportillo

Member
Sep 13, 2015
6
0
i know its old phone but my pall brought it from usa , its k7 k330tn tmobile version. And off course its locked on tmobile. I try to unlock the phone but no luck. Actually i did manage to unlock bootloader ,adb shell,root it and also managed to install metro pcs software on it with custom recovery. after that i try to update recovery and kingo root ,and thats was a mistake , cause phone is now in botloop state and none of unbricking ways doesnt work. LG UP want recognize (unkown model), uppercut didnt help also,flash tool had some issues, xda realese of flash tool says s fail to load etc... Only tool which find some info about phone is lg mobile support tool , but i can not do anything with that. So please HELP ? but i think i try almost everything.





hi, your problem is more easy to solve, you can to verify the firmware version that installed when you put the phone in download mode and appears the screen and the firmware version don't try flash another version different on appears in the download mode, or kill your phone... if need more help, post it

Best Regards.
 

nikonsevast

Member
Dec 3, 2010
6
0
hi, your problem is more easy to solve, you can to verify the firmware version that installed when you put the phone in download mode and appears the screen and the firmware version don't try flash another version different on appears in the download mode, or kill your phone... if need more help, post it

Best Regards.

well , its to late...its dead..actually i solved problem with right LG UP tool , for ms330,and was recognized but after that i made a mistake and flashed via upgrade instead of refurbish..cause i didnt have .tot file so i checked upgrade with .kdz. Everything went fine until reboot. Now its 9008 old way. and cant get qfil to work ."sahara fail". anyway thanks for offering help. sorry for bad english ,

best regards
 
Dec 18, 2017
28
7
well , its to late...its dead..actually i solved problem with right LG UP tool , for ms330,and was recognized but after that i made a mistake and flashed via upgrade instead of refurbish..cause i didnt have .tot file so i checked upgrade with .kdz. Everything went fine until reboot. Now its 9008 old way. and cant get qfil to work ."sahara fail". anyway thanks for offering help. sorry for bad english ,

best regards

If you're on Windows OS (I'm using Windows 10 for example): Try this, at least (I ran into a similar issue)!
  • Uninstall all related programs (LG UP included).
  • Uninstall all previously used drivers (Device Manager and/or "Apps & Features"); Hotkey: Windows key + X; Then press M or F

Then follow the instructions on this thread (installing LG UP/drivers/downloading the proper firmware ROM file): https://forum.xda-developers.com/lg-k7/how-to/guide-factory-stock-flash-t3722424

You should be able to reflash the KDZ (ROM image) as many times as it takes (it should not affect your ability of accessing the download mode).

I hope this helps and I hope you read this post! I understand you only have 2 posts on this site.
 
  • Like
Reactions: nikonsevast

secor941

Member
Sep 14, 2017
13
1
How do I flash this into my device? What program? If you can't say it here DM me... Thank you


Sent from my iPad using Tapatalk

PM, not DM... DM already is an abbreviation for a cough suppressant!
Accessing the system partition requires root permission. I am not familiar with your particular device, but after accessing the recovery menu on your device, see if there is an option that would put the device into a mode that will allow you to access it with the Android Debug Bridge (adb) through a command prompt on a computer with the device connected to it with a usb data cable. I have recently learned of a couple different ways that can possibly root your device with the command line. First is by downloading a file called psneuter which can be found in this file, https://github.com/tmzt/g2root-kmod , If you're using Windows then you'll want to download this to your android sdk directory and then navigate to g2root-kmod/scotty2/psneuter/. Next you will need to copy those files to the platform-tools directory which is also where adb is at. After copying the files, open a command prompt from your platform-tools folder by placing your cursor in an empty blank space within this folder, hold shift key while right-clicking on the blank area. After you have opened a prompt, type adb usb and press enter, type adb devices, the prompt should list your device. Now you will want to enter, adb push psneuter /data/local/tmp , which will copy the file to your device. Now you will want to enter, adb shell, which is the command prompt of the device. Once you are in the adb shell enter, cd /data/local/tmp, followed by chmod 777 psneuter, and then, ./psneuter... You should see an output of :
adb kill-server
adb devices
adb shell
If the $ has not already switched to #, enter su or sudo su. Next you will want to extract the contents of your system.img file that you have obtained and the use adb push *.* to /system/. Now enter: mount -o remount,rw -t rfs /dev/block/st19/system followed by the exit command and the adb reboot. This should replace all of the system files with all new files and you should now be able to reboot your device and have it working like new again.

If you wish to keep your device permanently rooted you will need to download busybox, su, and superuser.apk (https://forum.xda-developers.com/attachment.php?attachmentid=2634873&d=1395042343) to your platform-tools directory, then run the adb push command once more before rebooting your device to push the previously mentioned files to /system/bin using the same process as above using these files instead of psneuter and then run the adb shell again. Now make sure you have # and not $ then enter adb install Superuser.apk followed by chmod 4755 /system/bin/busybox and then chmod 4755 /system/bin/su. Now enter mount -o remount,ro -t rfs /dev/block/st19/system again followed by exit and reboot....
That seems like the easiest method to me, assuming it actually works that is.
 

stoag

Senior Member
Mar 2, 2017
91
13
Alcatel 1X
Moto G Stylus
Can someone with a working K7 please post the output of these commands in adb
Code:
ls -al /dev/block/platform/*/by-name
and
Code:
cat /proc/partitions
Thanks

c:\>adb shell ls -al /dev/block/platform
drwxr-xr-x root root 1970-01-03 02:11 7824900.sdhci
drwxr-xr-x root root 1970-01-03 02:11 7864900.sdhci

c:\>adb shell ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1970-01-03 02:11 DDR -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-03 02:11 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-03 02:11 abootbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-03 02:11 boot -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-03 02:11 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-03 02:11 config -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-03 02:11 devinfo -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-03 02:11 drm -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-03 02:11 eksst -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-03 02:11 encrypt -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-03 02:11 factory -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-03 02:11 fota -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-03 02:11 fsc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-03 02:11 fsg -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-03 02:11 grow -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-03 02:11 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-03 02:11 laf -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-03 02:11 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-03 02:11 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-03 02:11 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-03 02:11 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-03 02:11 mpt -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-03 02:11 persist -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-03 02:11 raw_resources -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-03 02:11 raw_resourcesbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-03 02:11 rct -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-03 02:11 recovery -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-03 02:11 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-03 02:11 rpmbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-03 02:11 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-03 02:11 sbl1bak -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-03 02:11 sec -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-03 02:11 sns -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-03 02:11 spare1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-03 02:11 spare2 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-03 02:11 ssd -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-03 02:11 system -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-03 02:11 tz -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-03 02:11 tzbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-03 02:11 userdata -> /dev/block/mmcblk0p39

c:\>adb shell ls -al /dev/block/platform/7864900.sdhci
drwxr-xr-x root root 1970-01-03 02:11 by-num
lrwxrwxrwx root root 1970-01-03 02:11 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 1970-01-03 02:11 mmcblk1p1 -> /dev/block/mmcblk1p1

c:\>adb shell ls -al /dev/block/platform/7864900.sdhci/by-num
lrwxrwxrwx root root 1970-01-03 02:11 p1 -> /dev/block/mmcblk1p1

c:\>adb shell cat /proc/partitions
major minor #blocks name

253 0 358028 zram0
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1536 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 512 mmcblk0p21
179 22 6656 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1536 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 6144 mmcblk0p28
179 29 6144 mmcblk0p29
179 30 10240 mmcblk0p30
179 31 8192 mmcblk0p31
259 0 16384 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 24576 mmcblk0p35
259 4 8192 mmcblk0p36
259 5 2465792 mmcblk0p37
259 6 204800 mmcblk0p38
259 7 4734976 mmcblk0p39
259 8 8175 mmcblk0p40
179 32 4096 mmcblk0rpmb
179 64 30748672 mmcblk1
179 65 30747648 mmcblk1p1

c:\>
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    I didn't use a DLL file, my program doesn't need it, you can try LGUP

    Sent from my SM-G935T using Tapatalk

    You may have given us a solution to unbricking the k7! but just as the rest I am having trouble without the DLL file. Can you pm the program that you used to flash your phone? Thanks.
    1
    Here is the system.img from the LGMS330 tot file.
    https://app.box.com/s/vtg4u46m0xj46amwjvvfrwrznpwjfjtp


    Here is the system.img from the LGK330 from my phone.
    https://app.box.com/s/67pywf2nlmgcdz47mu7q68dtypvt0dy3
    1
    If someone with at working k7 could run the commands on post 19 we would know for sure.
    Intuition tells me /dev/block/mmcblk0, but I'm not sure. step 2 for boost mobile says:
    When mine was working this was the block layout:
    major minor #blocks name

    253 0 359144 zram0
    179 0 7634944 mmcblk0
    179 1 65536 mmcblk0p1
    179 2 512 mmcblk0p2
    179 3 1024 mmcblk0p3
    179 4 512 mmcblk0p4
    179 5 2048 mmcblk0p5
    179 6 512 mmcblk0p6
    179 7 1024 mmcblk0p7
    179 8 512 mmcblk0p8
    179 9 2048 mmcblk0p9
    179 10 1536 mmcblk0p10
    179 11 1536 mmcblk0p11
    179 12 512 mmcblk0p12
    179 13 512 mmcblk0p13
    179 14 1536 mmcblk0p14
    179 15 512 mmcblk0p15
    179 16 512 mmcblk0p16
    179 17 512 mmcblk0p17
    179 18 512 mmcblk0p18
    179 19 512 mmcblk0p19
    179 20 1024 mmcblk0p20
    179 21 512 mmcblk0p21
    179 22 6656 mmcblk0p22
    179 23 6144 mmcblk0p23
    179 24 512 mmcblk0p24
    179 25 1536 mmcblk0p25
    179 26 1024 mmcblk0p26
    179 27 1024 mmcblk0p27
    179 28 6144 mmcblk0p28
    179 29 6144 mmcblk0p29
    179 30 10240 mmcblk0p30
    179 31 8192 mmcblk0p31
    259 0 16384 mmcblk0p32
    259 1 16384 mmcblk0p33
    259 2 16384 mmcblk0p34
    259 3 24576 mmcblk0p35
    259 4 8192 mmcblk0p36
    259 5 2584576 mmcblk0p37
    259 6 204800 mmcblk0p38
    259 7 4616192 mmcblk0p39
    259 8 8175 mmcblk0p40
    179 32 4096 mmcblk0rpmb
    If anyone has had success with the pair of LG_Root techniques on post 25, please say so.
    Mine won't get past step one and I am considering open a new thread to address my personal circumstance.

    I was able to pull the information from my wife's k7. I was able to get to step 11 but even with knowing the dev block it still fails at that step.
    lrwxrwxrwx root root 1970-01-11 21:26 DDR -> /dev/block/mmcblk0p13
    lrwxrwxrwx root root 1970-01-11 21:26 aboot -> /dev/block/mmcblk0p5
    lrwxrwxrwx root root 1970-01-11 21:26 abootbak -> /dev/block/mmcblk0p9
    lrwxrwxrwx root root 1970-01-11 21:26 boot -> /dev/block/mmcblk0p33
    lrwxrwxrwx root root 1970-01-11 21:26 cache -> /dev/block/mmcblk0p38
    lrwxrwxrwx root root 1970-01-11 21:26 config -> /dev/block/mmcblk0p21
    lrwxrwxrwx root root 1970-01-11 21:26 devinfo -> /dev/block/mmcblk0p20
    lrwxrwxrwx root root 1970-01-11 21:26 drm -> /dev/block/mmcblk0p28
    lrwxrwxrwx root root 1970-01-11 21:26 eksst -> /dev/block/mmcblk0p19
    lrwxrwxrwx root root 1970-01-11 21:26 encrypt -> /dev/block/mmcblk0p18
    lrwxrwxrwx root root 1970-01-11 21:26 factory -> /dev/block/mmcblk0p35
    lrwxrwxrwx root root 1970-01-11 21:26 fota -> /dev/block/mmcblk0p23
    lrwxrwxrwx root root 1970-01-11 21:26 fsc -> /dev/block/mmcblk0p15
    lrwxrwxrwx root root 1970-01-11 21:26 fsg -> /dev/block/mmcblk0p14
    lrwxrwxrwx root root 1970-01-11 21:26 grow -> /dev/block/mmcblk0p40
    lrwxrwxrwx root root 1970-01-11 21:26 keystore -> /dev/block/mmcblk0p17
    lrwxrwxrwx root root 1970-01-11 21:26 laf -> /dev/block/mmcblk0p32
    lrwxrwxrwx root root 1970-01-11 21:26 misc -> /dev/block/mmcblk0p30
    lrwxrwxrwx root root 1970-01-11 21:26 modem -> /dev/block/mmcblk0p1
    lrwxrwxrwx root root 1970-01-11 21:26 modemst1 -> /dev/block/mmcblk0p10
    lrwxrwxrwx root root 1970-01-11 21:26 modemst2 -> /dev/block/mmcblk0p11
    lrwxrwxrwx root root 1970-01-11 21:26 mpt -> /dev/block/mmcblk0p36
    lrwxrwxrwx root root 1970-01-11 21:26 persist -> /dev/block/mmcblk0p31
    lrwxrwxrwx root root 1970-01-11 21:26 raw_resources -> /dev/block/mmcblk0p26
    lrwxrwxrwx root root 1970-01-11 21:26 raw_resourcesbak -> /dev/block/mmcblk0p27
    lrwxrwxrwx root root 1970-01-11 21:26 rct -> /dev/block/mmcblk0p24
    lrwxrwxrwx root root 1970-01-11 21:26 recovery -> /dev/block/mmcblk0p34
    lrwxrwxrwx root root 1970-01-11 21:26 rpm -> /dev/block/mmcblk0p4
    lrwxrwxrwx root root 1970-01-11 21:26 rpmbak -> /dev/block/mmcblk0p8
    lrwxrwxrwx root root 1970-01-11 21:26 sbl1 -> /dev/block/mmcblk0p2
    lrwxrwxrwx root root 1970-01-11 21:26 sbl1bak -> /dev/block/mmcblk0p6
    lrwxrwxrwx root root 1970-01-11 21:26 sec -> /dev/block/mmcblk0p16
    lrwxrwxrwx root root 1970-01-11 21:26 sns -> /dev/block/mmcblk0p29
    lrwxrwxrwx root root 1970-01-11 21:26 spare1 -> /dev/block/mmcblk0p22
    lrwxrwxrwx root root 1970-01-11 21:26 spare2 -> /dev/block/mmcblk0p25
    lrwxrwxrwx root root 1970-01-11 21:26 ssd -> /dev/block/mmcblk0p12
    lrwxrwxrwx root root 1970-01-11 21:26 system -> /dev/block/mmcblk0p37
    lrwxrwxrwx root root 1970-01-11 21:26 tz -> /dev/block/mmcblk0p3
    lrwxrwxrwx root root 1970-01-11 21:26 tzbak -> /dev/block/mmcblk0p7
    lrwxrwxrwx root root 1970-01-11 21:26 userdata -> /dev/block/mmcblk0p39
    1
    I have been going nuts trying to figure this one out. Could you please PM me with the name of the program that will flash my K7. Thank you so much.

    I am checking XDA every hour for update. That's how desperate I am right now after bricking 2 device :(