• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root KDZ WParam: 100 LParam: 64, WParam: 100 LParam: 0

alpha125 said:
Yes, in download mode and emergency mode, but I don't know how to insall neither of those (cwm & twrp)through the computer.
Click to expand...
I believev there is a tot on how to do it in this forum maby exclusive 36 can help or another dev I'm not good at that part my self I'm trying to learn it better
 
AquaVolt said:
I was thinking of putting any custom rom on your sd card and then entering recovery, wiping /system and then flashing the rom. Unfortunately, you seem to be in stock recovery and not CWM recovery so that's not going to work.
Click to expand...
roadkill42 said:
make sure u are rooted again then will need to put cwm or twrp recovery using the PC method then try flashing a ROM after that hope I ant confusing u take ur time ok
Click to expand...

I've noticed that when i connect my phone to the computer and let it get to the charging screen (the screen with the blue battery) my computer makes the usb connection sound.
 
alpha125 said:
I've noticed that when i connect my phone to the computer and let it get to the charging screen (the screen with the blue battery) my computer makes the usb connection sound.
Click to expand...
Yeah its supposed to do that, even though it's bricked it still is able to charge. I was able to charge it when I bricked too, I would charge it overnight and worry about unbricking the next day :p. You should try using someone else's computer and see if that works. The only fix that I know of is using a different computer.
 
I have the exact same problem on my LG Optimus F6.

Seem to be going round in circles as well:

[R&D Test Tools Log File]

19:36:46 : Launching SW update
19:36:46 : Unpacking KDZ
19:37:36 : KDZ file extraced
19:37:43 : Files were extracted.
19:37:43 : LGMobileDL Load.
19:37:43 : Port = -1
19:37:43 : Connecting to phone
19:37:58 : Check Phone mode = 2
19:37:58 : Phone type check.......
19:37:59 : LGMobileDL.DLL Loading....
19:38:00 : _SetAuthMark Fail
19:38:00 : _SetAuthMark Ok : wAuthMark(65535)
19:38:00 : _DetachDLL Call
19:38:05 : _DetachDLL Call End
19:38:05 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\MS50010e_03_Develop.wdb
19:38:05 : Param : moduleDir =
19:38:05 : Param : waitTime = 0
19:38:05 : Param : UsbHighSpeed = 1
19:38:05 : Param : PhoneMode = 2
19:38:05 : Param : BinVersion = MS50010e_03
19:38:05 : Param : AuthMark = 65535
19:38:05 : Call fn_StartUpgrade
19:38:57 : 3GQCT : wParam = 100, lParam = 0
19:38:57 : Step : Upgrade Error error code = 0
19:38:57 : ResetStartInfo() Call
19:38:57 : _DetachDLL Call
19:39:02 : _DetachDLL Call End
19:39:02 : FreeLibrary Call
19:39:02 : FreeLibrary Call End
19:39:02 : ResetStartInfo() Call End
19:39:02 : 3GQCT : wParam = 100, lParam = 64
19:39:02 : Step : Upgrade Error error code = 64
19:39:02 : ResetStartInfo() Call
19:39:02 : ResetStartInfo() Call End
19:39:03 : ===FINISHED===

My phone is rooted via Towel Root and was using links to the SD Card for storage.

I first noticed a problem a couple of weeks ago when the phone was not booting, removed the ext_SD and then it booted fine. Put the ext_SD back in and all appeared to be good.

Now I just get the LG Logo and identical problems as you describe OP.... :(
 
Was anybody here able to find a solution for this error? If so, please share - there seem to be quite a few people with this problem (myself included!). Thanks for any help!
 
Can someone clear up a few basic questions for me? Is Recovery Mode (as opposed to Reset Mode) native to the F3 or is it only enabled when you install a recovery program like CWM or TWRP? If it is native what does it recover? I've got an MS659 and before it bricked I never thought to boot into Recovery Mode. Now that it is, well, it seems like it could have been useful...
 
That's what it seemed like from reading everyone's comments. If you don't root your phone, though, how would you know to install CWM or TWRP? It seems like everyone in the forum (except me) has CWM or TWRP installed. This explains, I guess, why it's just assumed that everyone can boot into Recovery Mode.
 
Another random question - do you guys always have your phone in USB debugging mode since that's the only way to access it if it crashes?
 
I wasn't able to do anything with the phone, so I gave up. The phone is still bricked and nothing that I've tried works. I hope you guys find the solution to the problem, if so please notify me! :)
 
For anyone getting an error when running the unbrick software, make sure you have at least 3GB free disk space on C: before you start the process. I was getting a param error (unfortunately I didn't write down which number) and discovered it was due to the fact that C: was running out of space. After freeing up space it went through fine.

Just something to try. It may not solve your problem.
 
I have used window 10 x64 every time to unbrick without issue. I loaded the kdz in the first slot, then plugged the phone in (in emergency mode, without root, without a custom recovery, without any living software or firmware on the phone except for the charging software and what was left of the stock recovery/emergency mode). I was able to factory reset a few times, which further exacerbated the situation. In fact, it had seemingly excorcised all life (whether good or bad) from my phone except for emergency mode and the ever pleasing, undeniably enjoyable for endless hour of viewing pleasure, battery charging graphic (I think its going to get it up this time, lol, keep pushing bro). Start with a freshly wiped phone, put the kdz file where you think it should go, have the program ready to flash the phone, don't attach the phone, but put it into emergency mode, then plug it into the computer (provided, of course, you have the proper drivers loaded) and see it that helps the flashing program do its job. Just my 2 cents
 
You must log in or register to reply here.
Back
Top Bottom