@Everybody with the exact problem described by the author...
Do you guys have your bootloader unlocked, like with "fastboot oem unlock"?
Well, I do. And I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
Do you guys have your bootloader unlocked, like with "fastboot oem unlock"?
Well, I do. And I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
Last edited:
Needing that program
I'm in need of that forbidden program as well. Can you
PM me?
I'm in need of that forbidden program as well. Can you
PM me?
I don't really understand how you bricked it. I rooted with king root no problem, then downloaded and installed busybox. Granted I haven't found a recovery yet so I refuse to boot into stock recovery just in case. After a restart I still have root, never had to deal with a bootloader or anything. Is our bootloader unlocked?
Sent from my LGMS330 using XDA-Developers mobile app
Sent from my LGMS330 using XDA-Developers mobile app
Got my MS330 fixed.... I downloaded the tot but found out it was corrupted somehow, but these guys fixed it for me using TeamViewer:
Check last few posts if you still need/wanna fix.
http://xdaforums.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678/page26
Last edited:
No, I have to upload the repaired MS330.rar that the guy who helped me zipped up to MEGA sometime today.
The rar contains a repaired tot I think.
He told me he will build me a rooted firmware with it after I upload it.
Could you also pm the program and/or the .DLL to me also...im in desperate need of an unbrick method
It was a system dump...not really sure what he did exactly...I think he dumped my system, then used part of the tot I downloaded from here to get me unbricked.
---------- Post added at 03:19 AM ---------- Previous post was at 03:16 AM ----------
I have the dlls he used, but I promised not to give them out.
---------- Post added at 03:19 AM ---------- Previous post was at 03:16 AM ----------
I have the dlls he used, but I promised not to give them out.
Undo Kingroot damage on LG K7
This procedure is to for fixing issues after Rooting the phone with Kingroot and the device becomes unstable but boots fine.
If you ran a factory reset thinking that was going to fix the issues and now you are stuck in the Setup Wizard Loop
try finishing the setup five times. The fifth time it will take you to the home screen.
If you bricked the phone completely and cannot get to the Home screen you will need to put your phone into Download Mode and use the LG flash tool to flash the .KDZ Rom file. At the moment this file is unavailable to get from LG support. So bricked all the way, just wait for the realase of the file.
!!For future reference, when ever you root android 5.0 and above within Android (Kingroot method), You have to Enable OEM Unlock from Developer options right away ALWAYS or else if you restart the phone it will get bricked due to oem security software blocking root permissions!!. Saying that lets continue.
Thanks to ledzepman71 for providing the .IMG file for Sytem Image. Link he provided. (Thanks again, you saved my phone)
Tools used:
ADB_Driver_Win8_X644.zip
ADB_Fastboot.zip
Start by:
- Enable developer options. (Tap Build Version ten times, etc)
- OEM Unlock should be Enabled or else you would not be on that screen (Bricked)
- Enable USB debugging
- Download ADB_Fastboot.zip and ADB_Driver_Win8_X644.zip (or find the one for your Win Version) and extract.
- Place the system image from ledzepman71 in the folder ADB_Fastboot.
- Run MAF32 as Administrator (From ADB_Fastboot)
- Type "adb reboot bootloader" (check the screen on your phone and allow the debug permision, run same command again after)
- Phone will restart to the Bootloader screen.
- At this point now install ADB Drivers. I am providing the ones for Windows 8.1 X64. Manually go to device manager and located the device named Android (with the yellow exclamation mark) and update Driver with the one provided in the folder "ADB Driver Win 8.1 X64"
- Now back on the computer type: "fastboot flash system system.img" (Proccess will take some time, 8 out 8 steps)
- finally run "fastboot oem lock"
- Now disconnect the phone and remove battery to power off phone, then put battery back in again.
- Boot your phone in to recovery like this:
Press and hold the Volume Down and the Power buttons simultaneously until the LG logo is displayed on your screen.
Then release and re-hold the Power button while still holding Volume Down.
Keep holding the buttons until the Recovery Mode menu appears.
- Now perform Factory Reset and done!
You need three links for this fix. I'm a new User for XDA, if you need the links to the files message me. I cannot post links yet because I'm a new user. Need to do 10 posts first.
This procedure is to for fixing issues after Rooting the phone with Kingroot and the device becomes unstable but boots fine.
If you ran a factory reset thinking that was going to fix the issues and now you are stuck in the Setup Wizard Loop
try finishing the setup five times. The fifth time it will take you to the home screen.
If you bricked the phone completely and cannot get to the Home screen you will need to put your phone into Download Mode and use the LG flash tool to flash the .KDZ Rom file. At the moment this file is unavailable to get from LG support. So bricked all the way, just wait for the realase of the file.
!!For future reference, when ever you root android 5.0 and above within Android (Kingroot method), You have to Enable OEM Unlock from Developer options right away ALWAYS or else if you restart the phone it will get bricked due to oem security software blocking root permissions!!. Saying that lets continue.
Thanks to ledzepman71 for providing the .IMG file for Sytem Image. Link he provided. (Thanks again, you saved my phone)
Tools used:
ADB_Driver_Win8_X644.zip
ADB_Fastboot.zip
Start by:
- Enable developer options. (Tap Build Version ten times, etc)
- OEM Unlock should be Enabled or else you would not be on that screen (Bricked)
- Enable USB debugging
- Download ADB_Fastboot.zip and ADB_Driver_Win8_X644.zip (or find the one for your Win Version) and extract.
- Place the system image from ledzepman71 in the folder ADB_Fastboot.
- Run MAF32 as Administrator (From ADB_Fastboot)
- Type "adb reboot bootloader" (check the screen on your phone and allow the debug permision, run same command again after)
- Phone will restart to the Bootloader screen.
- At this point now install ADB Drivers. I am providing the ones for Windows 8.1 X64. Manually go to device manager and located the device named Android (with the yellow exclamation mark) and update Driver with the one provided in the folder "ADB Driver Win 8.1 X64"
- Now back on the computer type: "fastboot flash system system.img" (Proccess will take some time, 8 out 8 steps)
- finally run "fastboot oem lock"
- Now disconnect the phone and remove battery to power off phone, then put battery back in again.
- Boot your phone in to recovery like this:
Press and hold the Volume Down and the Power buttons simultaneously until the LG logo is displayed on your screen.
Then release and re-hold the Power button while still holding Volume Down.
Keep holding the buttons until the Recovery Mode menu appears.
- Now perform Factory Reset and done!
You need three links for this fix. I'm a new User for XDA, if you need the links to the files message me. I cannot post links yet because I'm a new user. Need to do 10 posts first.
Last edited:
Anyone want a free Rooted Tribute 5 mobo with bad ESN?
Sent from my LGMS330 using XDA-Developers mobile app
Pm me I do please
Sent from my 5054N using XDA-Developers mobile app
---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------
Sent from my 5054N using XDA-Developers mobile app
Sent from my 5054N using XDA-Developers mobile app
---------- Post added at 03:16 AM ---------- Previous post was at 03:15 AM ----------
Meeeee please!!!
Sent from my 5054N using XDA-Developers mobile app
Last edited:
When does it say that while typing commands? In what mode?
Sent from my LGMS330 using XDA-Developers mobile app
sorry if this isnt the right place to post this but I cant find a main thread for the lg k7 on here
If anyone needs help with unbricking LG k330 message me
Sent from my LG-K330 using XDA-Developers mobile app
Sent from my LG-K330 using XDA-Developers mobile app
Top Liked Posts
-
There are no posts matching your filters.
-
3here you guys go I made stock tot https://drive.google.com/open?id=0By73pguuHS8mSTZJQVkwekVTanM3
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.1Here 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/67pywf2nlmgcdz47mu7q68dtypvt0dy31
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/mmcblk0p391
I am checking XDA every hour for update. That's how desperate I am right now after bricking 2 device
