Database Info

[RESOLVED] changing baseband/unknown baseband/broken audio in calls

These steps are mainly directed at how to use the KDZ program to switch your baseband/fixing unknown baseband.
*I have heard this works on Windows Vista/7 but I personally have only been able to accomplish it through Windows XP*; VMWare running XP and XP Mode also work but make sure the USB is consistently being connected to the XP environment (don't jack around outside it) or the process will hang & require you to start over!*
1. You do NOT need to have stock recovery installed for this to work, it will require you to reflash CWM after though - How to NvFlash CWM Recovery
2. If you are not on a stock ROM prior to doing this your phone will get stuck in a boot loop of the stock T-Mobile animation when the process is finished; until you reflash CWM Recovery and restore a backup
Notes:
[While on a custom ROM and Recovery]
I have had the kdz method hang after the baseband flash but before installing the stock ROM & Recovery, leaving everything but the baseband unchanged; this could happen for you but I recommend making an Nandroid still if you care about losing your current data; similar log of how it will appear if this happens: Baseband flash hangup
[Modem causing process to hang]
The process may hang due to the LG Modem driver, disabling and re-enabling it should fix this (Start --> Run --> devmgmt.msc --> Modems --> LGE Android Platform USB Modem --> Disable/Enable)
Needed files:
T-Mobile G2x Android USB Driver - drivers so your computer recognizes phone
V11H_00.kdz | Mirror 1 - data for the June 05 2011 baseband (WIND MOBILE)
V21E_00.kdz | Mirror 1 | Mirror 2 - data for the July 15 2011 baseband
V21Y_00.kdz | Mirror 1 | Mirror 2 - data for the March 11 2012 baseband
KDZ_FW_UPD_EN - software to install the baseband
APX Drivers & NVFlash - driver and software to flash Clockwork Recovery on your phone again
P999 V10F Nandroid - Nandroid of stock 2.2.2/V10F ROM
P999 V21E Nandroid | Mirror 1 | Mirror 2 - Nandroid of the stock 2.3.3/V21E ROM
P999 V21Y Nandroid | Mirror 1 | Mirror 2 - Nandroid of the stock 2.3.4/V21Y ROM
LGMobile Support Tool - Checks if the LG ROM/Baseband is outdated
Call audio fix for V21E Baseband | Mirror 1 - Fix the audio issue during a call with the V21E baseband on a custom ROM
Call audio fix for V21Y Baseband | Mirror 1 - Fix the audio issue during a call with the V21Y baseband on a custom ROM (So you can still be on CM9 nightlies thanks to owain94)
If you're trying to update from the V21E/July 2011 baseband to the V21Y/March 2012 baseband you should only need the LGMobile Support Tool and be on a stock 2.3.3 ROM to get the new baseband.
Download whichever file(s) you need from above; if you've been crack flashing with your computer already you should only need the KDZ program & the V21E/V21Y baseband file
Install the G2X driver onto your computer
Extract the KDZ_FW_UPD_EN archive and right click the "msxml.msi" file and select Install
Next keep your finger held on the Volume Down button of your phone and connect the USB cable to the phone and computer and wait until your phone displays "S/W Upgrade; if your computer says it detected a device it needs a driver for extract the APX/NvFlash zip and navigate the computer to the APX folder for the driver"
Open the "KDZ_FW_UPD.exe" file and click the folder icon to locate the KDZ file
After you have navigated to the KDZ file select it and push "Launch software update"
The log will instantly show:
Code:
15:54:41 : Launching SW update
15:54:41 : Unpacking KDZ
*The program will hang for a minute or two while it is unpacking the file don't worry!*
After you will see some information similar to this:
Code:
15:54:51 : KDZ file extraced
15:55:08 : Files were extracted.
15:55:08 : LGMobileDL Load.
15:55:08 : Port = 4
15:55:08 : Connecting to phone
15:55:20 : Check Phone mode = 1
The program will pause again for a minute and then this will display:
Code:
15:55:57 : Phone type check.......
15:55:57 : LGMobileDL.DLL Loading....
15:55:57 : _SetAuthMark Fail
15:55:57 : AuthMark°¡ Á¤È®È÷ Phone¿¡ Write µÇÁö ¾Ê¾Ò½À´Ï´Ù!
15:55:57 : _SetAuthMark Fail
15:55:57 : LoadCDMAPhoneData() Error
15:55:57 : _DetachDLL Call
15:55:57 : _DetachDLL Call End
15:55:57 : Param : Path = C:\Documents and Settings\All Users\Application Data\LGMOBILEAX\Phone\V21E.wdb
15:55:57 : Param : moduleDir =
15:55:57 : Param : waitTime = 33000
15:55:57 : Param : UsbHighSpeed = 0
15:55:57 : Param : PhoneMode = 1
15:55:57 : Param : BinVersion = V21E_00
15:55:57 : Param : AuthMark = 0
15:55:57 : Call fn_StartUpgrade
Last you will hear your USB disconnect/reconnect multiple times while seeing this spammed; this will keep going until the value of "lParam = 100"
Code:
15:56:07 : CDMA: wParam = 2006, lParam = 0
15:56:07 : Model Dll Msg Not Found(2006, 0)
Once the program has reached 100 your phone will reboot displaying the LG Logo and after a few moments it will boot up running the chosen baseband.

About to do this (http://support.lgforum.com/lg/topics/t_mobile_g2x_update_for_sound_quality) to my phone, to update the baseband and in the name of science.
I'll let you know how it goes.
And then, I'll be flashing over RC3 because as per (http://forum.xda-developers.com/showthread.php?t=1679892) it works with the new baseband.
Wait about an hour or two and I'll have something posted.

Maybe...
http://forum.xda-developers.com/showthread.php?t=1287321
or...
http://forum.xda-developers.com/showthread.php?t=1619932

E: 5 Hours later I got it, back on July baseband and phones working, so happy ROFL

xBkKx said:
E: 5 Hours later I got it, back on July baseband and phones working, so happy ROFL
Click to expand...
Click to collapse
Yay! I use a VM of XP too...so much easier
Sent from my LG-P999 using Tapatalk 2

Gotta love XDA's finest. You guys make it hard to actually brick a phone. In the end there will always be a way out of a brick so long as we have XDA developers supporting the device I'm stuck at the S/W Upgrade screen from a failed baseband update using the LG tool and I'm trying this method now. My IParam is scrolling so I'm sure it's doing the job.
Booted and everything's great. It's unfortunate that I restored to a stock ROM and used the LG Tool which failed miserably before using this method instead. I thought this method took more work and look at that, for being hard-headed I ended up having to do more work than I would have had I just done it this way from the beginning.

Lucky me - my "new" replacement phone showed up and I went to work getting it all setup; rooted, ROM loaded, apps and settings - went to make a phone call and experienced what I am assuming to be "the "chirping" sound during a call" cited for the V21Y March 11, 2012 baseband. My settings verified the culprit baseband in question.
I am currently running through TGA_Gunnman's "NANDROID Restore Stock FR 2.22 V10f / GB 2.33 V21e and 2.34 V21y" tutorial to get back to stock and then unroot to follow this one. I am assuming I will need to use the "V21Y_00.kdz - data for the March 11 2012 baseband" but I'm bit unclear on how the "V21Y-BB.Fix.zip" plays into your instructions.
Any assistance would be greatly appreciated. - THX!

That bb fix zip is what owain made, just flash that to fix the chirping noise if you have it, it's so you can be on the new baseband and also a custom ROM
Sent from my LG-P999

That sounds good - I am running into trouble with the update however. I get all the way down through a bunch of the IParams till it hits this one -CDMA: wParam = 2010, IParam = 3035
Model Dll Msg Not Found(2010, 3035)​where it just hangs indefinitely. Tried it a few times and have a log saved if that would be of any help. I'm using an actual Windows XP machine (not a VM).
Thoughts?
Edit: Why do I get the sinking feeling I could have just flashed the BB fix to begin with? * sigh *

Is the USB connection staying connected? It disconnected around that on me sometimes and I had to retry, you could also try going into device manager and finding the LG Modem and disabling and re enabling it really quick (if the process hanged at a specific area during the Param spamming session longer than a minute it basically timed out, at least for me)
You said you were on the March baseband so why are you flashing it again? You need to V21E if you're switching. V21E July 15 2011/ V21Y March 11 2012 are the basebands.
You probably did just need to flash the bb fix zip that's why I mainly mentioned that :/ been at work so I'm sorry I haven't been able to be more clear
Sent from my LG-P999

Yeah - I ran the LG tool just to confirm my suspicions... guess I should have done that first. I did quite a bit of searching on the issue before deciding to nuke but didn't find the info spelled out for me (I'm still a rather "step by step" n00b, unfortunately)
It all works out though - The Eaglesblood ROM I was/am using updated since the version I installed Tuesday. It not only included the fix but a sweet install interface that did a lot of the leg work for me! - I am up and running great now! I used Titanium Backup Pro so the setup process wasn't quite so laborious.
Thanks for the help - and responses from work

When I'm doing this to get from 2.3.3 to 2.3.4 for the y21y BB the kdz update will get to the part where it says
15:56:07 : CDMA: wParam = 2006, lParam = 0
15:56:07 : Model Dll Msg Not Found(2006, 0)
But a few seconds later it will give me a runtime error.
Edit:
To be exact this is the full error.
Runtime Error!
Program: ...gs\administrator\desktop\stuff\kdz fw upd\kdz_fw_upd.exe
abnormal program termination
Edit2:
Decided to run VMware and windows xp on my desktop to see if it was just my laptop and lo behold it was something with my laptop.
It is currently installing and will come back to this if anything goes wrong or have in opinions.

Works fine for me. I just downgrade it to July baseband.
USB cable -> make sure you use the original cable from LG.
1st time flashing -> use Nokia cable -> failed -> stuck at Iparam=40++. (CWM is not removed). After reboot. The Phone Shows BB as July and bluetooth for car is working again. (So eventhough its stuck, the BB is already showing as July)
2nd time flashing -> use original LG cable -> works fine until Iparam=100. (CWM is removed when the program completed).
Thanks

I kept getting "mod uptestex mfc has stopped working" with vista. I needed to use VMware to run XP and then I was finally able to get it to downgrade to July 2011. Also once it gets to 100 you need to just unplug the phone because it will continue to bootloop until you install CWM and flash a rom or restore a nandroid. If you are doing this to get Bluetooth working in CM7.2 you will need to reflash 7.2 over your current 7.2 or you will have no call audio.

I am trying to flash v21y using the KDZ_FW_UPD tool
I am getting the error phone not found?
[R&D Test Tools Log File]
04:33:24 : Launching SW update
04:33:24 : Unpacking KDZ
04:33:35 : KDZ file extraced
04:33:38 : Files were extracted.
04:33:38 : LGMobileDL Load.
04:33:52 : Port = 0
04:34:06 : Connecting to phone
04:34:32 : PHONE WAS NOT FOUND!
04:34:34 : ===FINISHED===

vincy24 said:
I am trying to flash v21y using the KDZ_FW_UPD tool
I am getting the error phone not found?
Click to expand...
Click to collapse
In Device Manager under Modems make sure LGE Mobile USB Modem is enabled it will appear in there when the phone is connected and in the S/W Upgrade screen.
I tried this again on a fresh install of XP on my VMWare and it went fine..the KDZ Program should have "Type: CDMA" and "PhoneMode: DIAG" (should be default) as the options also, in case you messed with it.

solution here
http://forum.xda-developers.com/showthread.php?t=1619932
really works with unknown baseband

Dumb enough to get in trouble, smart enough to not make it worse
So, thought I was slick, I'm not, I'm a noob. Tmobile G2x in North America (Dallas, to be exact.) Was running 2.3.4 stock.
Downloaded & installed EAGLESBLOOD™ ICS AOSP [4.0.4]. Unfortunately, despite some thought of "was there a warning about this? I think I saw something somewhere" I did flash the baseband radio during the install.
Phone runs fine now, just have the dreaded click/thump noise and limited data. Can't make calls
Searched and found this thread. Looks like the cure but I'm unclear:
- Do I have to go back to stock (and if so, is there any concensus on which method to follow. I've seen several different threads)
- If I follow this thread, which files do I download/install? When I pull up "About Phone" I have baseband version M6600A-SCAUTNZ-2.0.9720T 1 [Mar 11 2012]
I'm sorry for my ignorance but I thought I'd ask before I install something and only make my problems worse.
Thanks,
Jeff

crosjn said:
So, thought I was slick, I'm not, I'm a noob. Tmobile G2x in North America (Dallas, to be exact.) Was running 2.3.4 stock.
Downloaded & installed EAGLESBLOOD™ ICS AOSP [4.0.4]. Unfortunately, despite some thought of "was there a warning about this? I think I saw something somewhere" I did flash the baseband radio during the install.
Phone runs fine now, just have the dreaded click/thump noise and limited data. Can't make calls
Searched and found this thread. Looks like the cure but I'm unclear:
- Do I have to go back to stock (and if so, is there any concensus on which method to follow. I've seen several different threads)
- If I follow this thread, which files do I download/install? When I pull up "About Phone" I have baseband version M6600A-SCAUTNZ-2.0.9720T 1 [Mar 11 2012]
I'm sorry for my ignorance but I thought I'd ask before I install something and only make my problems worse.
Thanks,
Jeff
Click to expand...
Click to collapse
Flash the rom again and when it gives you the option for baseband, click the 21y option. That'll fix the calling issue.
Sent from my LG-P999 using xda app-developers app

So awesome
Thanks, phone running muy bueno now. And who knew it was that easy to repair!
Many many thanks

P506 LG THRIVE Complete Emergency/Unbrick/revert to stock v11h/root & cwm

LG THRIVE EMERGENCY MODE/BRICK FIX/REVERT TO STOCK v11H Firmware/How to root after unbrick & revert/install CWM
***I want to make a few things completely clear:
1. THIS IS FOR THE LG THRIVE (P506GO) ONLY.
2. I AM NOT RESPONSIBLE FOR FURTHER BRICKING OF YOUR DEVICE (however I have not had any issues and I have done this many times)
3. I do not know where I found this procedure originally, however I have seen it posted around the web a few times. So I cannot actually give credit to anyone because I do not know who i got it from or who came up with it originally, So I apologize.
4. I did not make any of the files.
5. I did this because I am sure there are other people that have spent hours, upon hours, upon hours trying to figure this out, and my wife drives me nuts and I figure other spouces have been driven nuts, so here you go. If you like it, use it, if you dont, then dont.
This procedure will work for ANY LG THRIVE THAT STILL COMES UP IN EMERGENCY MODE, If your phone shows up as a QCUSB_DLOAD or something to that effect in device manager this will not work, This will also work for anyone wanting to fully revert back to stock 2.2.2 v11H. This is also safe to the effect it will not mess up your NV partition (there is another unbrick guide that you run the risk of screwing up your NV and then you wont have cell service after the unbrick).
That being said on with how to do it!
Download these files first
CUSTOM KDZ v11h
LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1.exe
LG_KDZ_FW-Update_OfflineFix
Unbrick Solution
1. If your phone is plugged in to the comp, unplug it. Remove the back off the phone and remove battery, do not worry it will be fine. Now set it to the side, we don't need it just yet.
2. Install the LG UNITED MOBILE DRIVER from the file you downloaded.
3. WE ARE NOT INSTALLING ANYTHING ON THIS NEXT STEP THIS IS MERELY TO HELP US ELIMINATE A PROBLEM. If your phone automatically boots into emergency mode then go ahead and plug it in (for those stuck in bootloop or just wanting to revert press and hold back + Volume up and then plug in the usb) and let the drivers install. Once that is done go to Device Manager (Start->run-> type devmgmt.msc and press enter.) expand the modems section and disable (DO NOT UNINSTALL) the LGE USB MODEM (See pic below). It will ask you to restart your computer, DONT.
{
"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"
}
4. Disconnect the phone from the computer.
5. Extract the contents of the LG_KDZ_FW-Update_OfflineFix to it's own folder.
6. open the folder to which you extracted those files then open the KDZ_FW_UPD_EN folder
7. XP Users: just double click the KDZ_FW_UPD.exe/Vista,7,8 users right click and run as administrator.
8. Set Type to 3GQCT and PhoneMode to Emergency (others tell you to set it to diag, dont.)
9. Click the little folder with the curved arrow above it to the right of the KDZ file and select the custom_lg_thrive.kdz file you downloaded earlier. Leave the program open.
10 EVERYONE MUST DO THIS STEP EXACTLY WHETHER YOU BOOT AUTOMATICALY INTO EMERGENCY OR NOT! Plug your battery back in, then press and hold the back button + Volume Up + Power. Release ONLY POWER once the thrive starts and then release back and volume up once your in emergency.
11. NOW PLUG YOUR PHONE BACK INTO THE USB!
12. Hit Launch Software update. If it says phone isnt found, first verify the LGE MODEM driver in device manager is still disabled, if it is disconnect phone and then plug it back in without rebooting and hit start upgrade again, it should work this time. IF THE WINDOW FREEZES DO NOT PANIC IF IT GIVES YOU A MESSAGE SAYING ITS FROZEN CLICK WAIT on VISTA/7/8 (on xp it should just revert back, once it does youll see in the dialog box it is flashing let it continue until it says it is complete (Your phone will reboot and you will be at the battery charging screen)
13. WE ARE NOT DONE JUST YET! Now we have to do a Factory(Hard) Reset SO with the device off press and hold the home + volume up + power. release all three once the device boots, let it do its thing. when the device reboots, it will seem to take forever. but it will finally get to the Android setup screen.
Walaa You are back to v11H stock firmware.
How to root after unbrick/revert to stock
1. After you setup your thrive go to settings->Applications and check unknown sources
2. in the same menu click on development and check all three settings in there.
3. Make it easy on yourself and just use the phone browser to come to this thread even easier here is a bit.ly link: http://bit.ly/14EbsSF
4. from your phone browser download the gingerbreak attachment.
5. Install it after its downloaded (if given the unknown sources dialog box refer to step 1
6. Hit Root Device, and let it do its thing, after it reboots, it will be rooted.
Install CWM
1. After rooting via the steps above, open up the play store.
2. In search type Rom Manager and install the Rom Manager from Clockworkmod
3. Open up rom manager and it should prompt you to install Clockworkmod Recovery. Click continue OR click the Flash Recovery button, it will search for your device, but it will pop up for the P500 (old Baseband) SELECT THAT ONE! then click normal install.
4. once it says it is successful go ahead and reboot into recovery via the menu in Rom Manager (allow superuser permissions), to verify that clockworkmod is installed. IT WILL HAVE MESSED UP COLORS, and may come up in the dialog box that an error occurred, THAT IS EXPECTED AND IS OKAY. Use the volume keys to navigate, power to select, and the back key to go back.
There, from this point you should be able to do whatever you want to your thrive that you want. I hope this helps.

Nice work. I have confirmed this method works very well on my thrive.
Thanks for your great work..

yoohath said:
Nice work. I have confirmed this method works very well on my thrive.
Thanks for your great work..
Click to expand...
Click to collapse
Thank you for posting this. I almost threw out the phone because none of the other suggestions seemed to work.
This worked for me, but some critical steps were not mentioned in the post.
My phone was automatically booting into emergency mode. After installing the LG UNITED MOBILE DRIVER, just plugging in the phone (in emergency mode) was not enough. It did not load the drivers, and nothing showed up under modems in Device manager. There seems to be different types of emergency modes. I had to do Back + Volume up + Power and then plug it in to get the phone drivers to install. Once it showed up, I disabled the LG modem.
I also had to install the "msxml.msi" program that you had in the same KDZ_FW_UPD_EN diretcory. Without this, the program was crashing with some error messages (sorry, I didn't write them down).
I also had to run "Windows Enabler.exe" in the same directory. I am not sure what this does, but without it, the program was crashing.
Once I got past all that, at first I thought the program froze because nothing was happening and windows complained that it was "Unresponsive". It took a couple of minutes for some log messages to show up. Once it got going it took about 5 minutes to complete.
Then the first boot took a very long time, around 5 minutes. It seemed stuck on the startup screen, but eventually it took me to the phone initializations etc.. and then it worked fine after that.

This works!!! Period. Surprised the hell outta me!!! I have two P506 that have been stuck in Emergency Mode for a couple years. I've tried countless combinations and KDZ's. It took less than 5 minutes to flash the KDZ per phone. Factory reset, and BAM!!! After about 3 minutes or so was welcomed by the Setup Wizard.
@aestivalisakito
Please add the extra things that were mentioned above by @asarangan to the OP. These are actually critical. I'm running Windows 7 64 bit Pro and KDZ Updater kept crashing without them. I enabled Windows Enabler and installed the XML 4 parser. Drivers were previously installed. Tried again and VOILA!!!!
Thanks again

asarangan said:
Thank you for posting this. I almost threw out the phone because none of the other suggestions seemed to work.
This worked for me, but some critical steps were not mentioned in the post.
My phone was automatically booting into emergency mode. After installing the LG UNITED MOBILE DRIVER, just plugging in the phone (in emergency mode) was not enough. It did not load the drivers, and nothing showed up under modems in Device manager. There seems to be different types of emergency modes. I had to do Back + Volume up + Power and then plug it in to get the phone drivers to install. Once it showed up, I disabled the LG modem.
I also had to install the "msxml.msi" program that you had in the same KDZ_FW_UPD_EN diretcory. Without this, the program was crashing with some error messages (sorry, I didn't write them down).
I also had to run "Windows Enabler.exe" in the same directory. I am not sure what this does, but without it, the program was crashing.
Once I got past all that, at first I thought the program froze because nothing was happening and windows complained that it was "Unresponsive". It took a couple of minutes for some log messages to show up. Once it got going it took about 5 minutes to complete.
Then the first boot took a very long time, around 5 minutes. It seemed stuck on the startup screen, but eventually it took me to the phone initializations etc.. and then it worked fine after that.
Click to expand...
Click to collapse
My pleasure I really want Thrive user (small polulation apart from P500) to have fully use this phone. Now I try to flash 4.4.2 Kitkat and battery drained was like froyo unless SElinus was disable from P505 kernel.

Hey nice thread !! Thanks.
I have a P500, and tried a lot of stuffs with KDZ and LGMDP,
your method is close to all of them with some more details,
that for ex :
10 EVERYONE MUST DO THIS STEP EXACTLY WHETHER YOU BOOT AUTOMATICALY INTO EMERGENCY OR NOT! Plug your battery back in, then press and hold the back button + Volume Up + Power. Release ONLY POWER once the thrive starts and then release back and volume up once your in emergency.
Click to expand...
Click to collapse
I'll try it !! I just think the step by step method is the same with my P500 ...
I, until now, got strange errors with KDZ ("Error upgrade - WPARAM : 100 - LPARAM : 4008") and LGMDP (Error AMSS writing),
have you already encoutered them ??
I'll try it tonight on my P500, with the good Drivers and stock Rom for the P500.
If you think you can help me or has another idea, look at my thread !
http://forum.xda-developers.com/showthread.php?p=49390595
Thanks.
Bestrau.

[23:14:54:328] : =============================================
[23:14:54:328] : Log is started on 13.01.2014, at 23:14:54:328,
executable: C:\***\LG_KDZ_FW-Update_OfflineFix\KDZ_FW_UPD_EN\UpTestEX_mod2_marwin.exe (ProcID: 0x00000b98),
compile time : Dec 8 2010 09:19:37
[23:14:54:328] : Version :
[23:14:54:359] : Get Usb Port
[23:14:54:359] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM5)
[23:14:54:359] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[23:14:54:359] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM5
[23:14:54:359] : Port = COM5
[23:14:54:390] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:54:406] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:54:421] : UNKNOWN : Req(12) -> Rsp(13)
[23:14:54:421] : >> DIAG_STATUS_F FAILED
[23:14:54:437] : >>Get Model Name [DIAG_VERNO_F]
[23:14:54:453] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:468] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:484] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:500] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:515] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:531] : BAD CONN MODE : Req(0) -> Rsp(3)
[23:14:54:531] : FAIL (No Phone)
[23:14:54:531] : GetModelName() Operation Failed Check Diag CMD
[23:14:54:531] : EMERGENCY Booting Mode
[23:14:54:531] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[23:14:54:546] : BS/P500/7D1\Tom\LOCALS~1\Temp\DZ42.tmp
[23:14:54:546] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - P500
[23:14:54:562] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:54:562] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:54:578] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:54:578] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:54:593] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[23:14:54:593] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[23:14:54:593] : NV Write Fail : NV ITEM 9028(9028)
[23:14:54:703] : >> GET DLOAD COMM MODE
[23:14:54:718] : [GetCommMode] Communication mode : 2
[23:14:54:734] : Pre Nand Download
[23:14:54:734] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[23:14:54:734] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[23:14:54:750] : [COM5] >>NandFlashInitWithFile(PARTITION TBL)
[23:14:54:750] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[23:14:54:875] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_TO_SDRAM 3
[23:14:54:875] : [COM0] ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_AMSS 15
[23:14:54:875] : [COM5] >>NandFlashInitWithFile(AMSS MODEM HEADER)
[23:14:54:890] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT AMSS MODEM HEADER
[23:14:54:906] : [COM0] >>Dl_AsyncWrite()
[23:14:54:906] : >> AMSS FLASHING ...
[23:14:54:906] : ¸Þ½ÃÁö º¸³¿ ProgreassiveBar Init wParam TYPE_WPARAM_PROGRESSIVE_POS=5 lParam(pos)=0 nResult=0
[23:14:54:906] : Sending Pkt Seq : 0
[23:14:54:906] : Sending Pkt Seq : 1
[23:14:54:906] : Sending Pkt Seq : 2
[23:14:54:906] : Sending Pkt Seq : 3
[23:14:54:906] : Sending Pkt Seq : 4
[23:14:54:906] : Sending Pkt Seq : 5
[23:14:54:906] : Sending Pkt Seq : 6
[23:14:54:906] : Sending Pkt Seq : 7
[23:14:54:906] : Sending Pkt Seq : 8
[23:14:54:906] : Sending Pkt Seq : 9
[23:14:54:921] : Dl_AsyncWrite - ErrNo(45), Addr(0x00004800), NandErrNo(0x04)
[23:14:54:921] : [COM0] ERROR Dl_AsyncWrite() TYPE_LPARAM_UPGRADE_ERROR_WRITE_TO_FLASH
[23:14:54:921] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[23:14:54:921] : Close Port<<
[23:14:54:921] : TYPE_WPARAM_UPGRADE_ERROR
[23:14:54:921] : ¸Þ½ÃÁö º¸³¿ - TYPE_WPARAM_UPGRADE_ERROR Error Code = 4008
[23:14:54:937] : Log finished
Click to expand...
Click to collapse
It unfortunately didn't work for me ...
Any ideas of what the problem could be ?

@shinobisoft...feels good to have two bricks turn to gold again?
Sent from my LG-P500

Thank you so much for this!! I looked everywhere and tried multiple KDZ files with various computers and settings, but only this worked! Time to get CWM and Kitkat running on this thing. >

Hey guys I will add the aforementioned items to the original post. Sorry I have been away on deployment and have not been able to attend to this or any of my other threads. I'll get back on it
Website signature

[Q] P500 - Emergency mode - KDZ and LGMDP errors

Hi everybody,
I’m at a point where I need to get some help…
My story:
I hard bricked my P500 one year ago … I had CM7 on it, and I installed CM10, but had no network,
so I upgraded the baseband, unfortunately it froze in the middle of the upgrade, I took the battery out, and it was the end …
BOUM … No fast boot, no emergency mode anymore … nothing … dead … Impossible to switch it on …
I bought a new one, which is working under CM7. No problem.
(So if it helps to fix the old hard bricked one I have a working P500 under CM7)
I just got the idea to fix the dead one! Because it’s fun, but I’m stuck and need some help.
JTAG reset:
Since it was hard bricked, the only possibility was a JTag reset. I found a nice guy doing it close to my place and it worked!
The phone has been recognized without any problem, the full dump worked without any mistakes, and finally the bootloader has been restored with a RiffBox.
(See attached picture) The phone can now reach the emergency mode again.
Flash original firmware on P500 with KDZ - not successful:
http://forum.xda-developers.com/showthread.php?t=875881
The drivers from LG are installed, I disabled the LG modems,
my computers (xp) sees the phone without any problems.
I tried to flash the original firmware on it with KDZ, which I’m used to do
but this time I get every time an error
"Error upgrade
WPARAM : 100
LPARAM : 4008"
(Logfile attached)
Flash stock rom with LGMDP – not successful:
http://forum.xda-developers.com/showthread.php?t=1324105
Same here, the P500 is recognized by LGMDP,
it seems the IMEI number is not active,
and everytime I flashed a rom, I got an error:
“Error! AMSS writing” (See attached picture)
Flash a custom recovery (CWM) from LGMDP – not successful
http://forum.xda-developers.com/showthread.php?t=1318750
I also tried to flash CWM, LGMDP seems to have installed it, I got a “Download complete” message,
but I cant access the recovery mode. Vol Down +Home + Power On just brings me back to the yellow emergency screen.
I of course checked everywhere online … I have seen sometimes the same errors as mine but no solutions ….
Do, one of you, have a solution? Or know the errors I’m encountering?
Or do you have another way tp get out of the emergency mode?
Thank you for reading and helping me in any way …
Bestrau.

How much did JTAG cost ?
Sent from my GT-I9082 using Tapatalk

Hey akiratoriyama, I read your posts, sorry for your hard bricked ...
It happened to me too, I found a guy in Germany he does it for 18 euro and you have to pay for the shipping.

no signal (baseband fix) : http://forum.xda-developers.com/showthread.php?t=2616412
restore your original rom here: http://forum.xda-developers.com/showthread.php?t=2559363
hit like if i helped..

Same error as usual ...
voltaire23 said:
no signal (baseband fix) : http://forum.xda-developers.com/showthread.php?t=2616412
restore your original rom here: http://forum.xda-developers.com/showthread.php?t=2559363
hit like if i helped..
Click to expand...
Click to collapse
Hi Voltaire,
your proposition is just the same as all the others I tried !
I gave it a try,
but got the same error ...
[11:02:44:461] : =============================================
[11:02:44:461] : Log is started on 19.01.2014, at 11:02:44:461,
executable: C:\Prerequisite\KDZ Updater\KDZ_FW_UPD.exe (ProcID: 0x00000ab0),
compile time : Dec 8 2010 09:19:37
[11:02:44:461] : Version :
[11:02:44:633] : Get Usb Port
[11:02:44:633] : rsi.strFriendlyName=LGE Android Platform USB Serial Port (COM5)
[11:02:44:633] : FriendlyNameList[iii].szFriendlyName=LGE Android Platform USB Serial Port
[11:02:44:633] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 1 - COM5
[11:02:44:633] : Port = COM5
[11:02:44:648] : UNKNOWN : Req(12) -> Rsp(13)
[11:02:44:664] : UNKNOWN : Req(12) -> Rsp(13)
[11:02:44:679] : UNKNOWN : Req(12) -> Rsp(13)
[11:02:44:679] : >> DIAG_STATUS_F FAILED
[11:02:44:695] : >>Get Model Name [DIAG_VERNO_F]
[11:02:44:711] : BAD CONN MODE : Req(0) -> Rsp(3)
[11:02:44:726] : BAD CONN MODE : Req(0) -> Rsp(3)
[11:02:44:742] : BAD CONN MODE : Req(0) -> Rsp(3)
[11:02:44:789] : BAD CONN MODE : Req(0) -> Rsp(3)
[11:02:44:804] : BAD CONN MODE : Req(0) -> Rsp(3)
[11:02:44:820] : BAD CONN MODE : Req(0) -> Rsp(3)
[11:02:44:820] : FAIL (No Phone)
[11:02:44:820] : GetModelName() Operation Failed Check Diag CMD
[11:02:44:820] : EMERGENCY Booting Mode
[11:02:44:820] : >>Get Model Name in Emergency Mode [DLOAD_VERREQ_F]
[11:02:44:836] : BS/P500/7D1\LOCALS~1\Temp\DZ10.tmp
[11:02:44:836] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 0 - P500
[11:02:44:851] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[11:02:44:851] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[11:02:44:867] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[11:02:44:867] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[11:02:44:883] : DLOAD_NAK_F reason_msb = 3, reason_lsb = 3
[11:02:44:883] : [ DLOAD ERROR ] : NAK_INVALID_LEN
[11:02:44:883] : NV Write Fail : NV ITEM 9028(9028)
[11:02:44:992] : >> GET DLOAD COMM MODE
[11:02:45:008] : [GetCommMode] Communication mode : 2
[11:02:45:008] : Pre Nand Download
[11:02:45:008] : >>Set Trusted Mode [DLOAD_NAND_SEC_MODE] sec_mode = 1 (1=trusted 0=NonTrusted)
[11:02:45:008] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - TRUSTED MODE
[11:02:45:023] : [COM5] >>NandFlashInitWithFile(PARTITION TBL)
[11:02:45:023] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT PARTITION TBL
[11:02:45:148] : ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_TO_SDRAM 3
[11:02:45:148] : [COM0] ¸Þ½ÃÁö º¸³¿ TYPE_WPARAM_WRITE_AMSS 15
[11:02:45:148] : [COM5] >>NandFlashInitWithFile(AMSS MODEM HEADER)
[11:02:45:148] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - INIT AMSS MODEM HEADER
[11:02:45:164] : [COM0] >>Dl_AsyncWrite()
[11:02:45:164] : >> AMSS FLASHING ...
[11:02:45:164] : ¸Þ½ÃÁö º¸³¿ ProgreassiveBar Init wParam TYPE_WPARAM_PROGRESSIVE_POS=5 lParam(pos)=0 nResult=0
[11:02:45:164] : Sending Pkt Seq : 0
[11:02:45:164] : Sending Pkt Seq : 1
[11:02:45:164] : Sending Pkt Seq : 2
[11:02:45:164] : Sending Pkt Seq : 3
[11:02:45:164] : Sending Pkt Seq : 4
[11:02:45:164] : Sending Pkt Seq : 5
[11:02:45:164] : Sending Pkt Seq : 6
[11:02:45:164] : Sending Pkt Seq : 7
[11:02:45:164] : Sending Pkt Seq : 8
[11:02:45:164] : Sending Pkt Seq : 9
[11:02:45:179] : Dl_AsyncWrite - ErrNo(45), Addr(0x00004800), NandErrNo(0x04)
[11:02:45:179] : [COM0] ERROR Dl_AsyncWrite() TYPE_LPARAM_UPGRADE_ERROR_WRITE_TO_FLASH
[11:02:45:211] : WM_COPYDATA ¸Þ½ÃÁö º¸³¿ 3 - Close Port
[11:02:45:211] : Close Port<<
[11:02:45:211] : TYPE_WPARAM_UPGRADE_ERROR
[11:02:45:226] : Log finished
Click to expand...
Click to collapse
Any ideas ?

Bestrau said:
Hi Voltaire,
your proposition is just the same as all the others I tried !
I gave it a try,
but got the same error ...
Any ideas ?
Click to expand...
Click to collapse
Well.. thats weird..hmmm did you follow the steps EXACTLY as written??
remove sd card while performing that.. disable lg modem... hmm retry again.. patience..

voltaire23 said:
Well.. thats weird..hmmm did you follow the steps EXACTLY as written??
remove sd card while performing that.. disable lg modem... hmm retry again.. patience..
Click to expand...
Click to collapse
Yes I followed it exactly as written .... I tried a couple of times .... same results ...

Bestrau said:
Yes I followed it exactly as written .... I tried a couple of times .... same results ...
Click to expand...
Click to collapse
Is your Download Mode unlocked????

voltaire23 said:
Is your Download Mode unlocked????
Click to expand...
Click to collapse
The only thing I can do is : enter the Emergency Mode by pressing volume up button + back button together and then plug the usb cable.

Bestrau said:
The only thing I can do is : enter the Emergency Mode by pressing volume up button + back button together and then plug the usb cable.
Click to expand...
Click to collapse
Uhmm..sorry to say but all I can say is try to search in the threads because I know there are other ways besides KDZ.. And you know that KDZ is very lethal mostly on optimus one variants and others...hmm..dont loose hope man..good luck.. GODBLESS.

I should try put the phone in Emergency Mode and start trying the KDZ with a Stock Gingerbread from different sources until it works...

voltaire23 said:
Uhmm..sorry to say but all I can say is try to search in the threads because I know there are other ways besides KDZ.. And you know that KDZ is very lethal mostly on optimus one variants and others...hmm..dont loose hope man..good luck.. GODBLESS.
Click to expand...
Click to collapse
Thank you ...
Too bad nobody has a solution for this "Upgrade Error: WParam: 100 LParam: 4008" on KDZ ...
And as I said in the original thread, I also tried with LGMDP, but I got everytime an "amss writing" error.

Bestrau said:
Thank you ...
Too bad nobody has a solution for this "Upgrade Error: WParam: 100 LParam: 4008" on KDZ ...
And as I said in the original thread, I also tried with LGMDP, but I got everytime an "amss writing" error.
Click to expand...
Click to collapse
No prob. well..you can always press my ""Thanks"" button..haha.

Same problem here((( Did everything but still on LG logo((

Make sure you have the correct KDZ file for your device and download my attachment.
I know for a fact that this KDZ Updater works as it is the exact one I used to restore 2 P506's back to life just a month or so ago. I did this on Windows 7 Professional 64 bit so it should also work for Windows XP.
Do all the usual KDZ stuff. Disable LG Modem in Device Manager, etc. Then follow the directions in the ReadMe.txt in the attached archive. Best of luck!

voltaire23 said:
No prob. well..you can always press my ""Thanks"" button..haha.
Click to expand...
Click to collapse
Your help is appreciated, but asking for people to press the "Thanks" button is defeating the purpose of the "Thanks" button. The "Thanks" meter has no effect on your account and standings here at XDA.

voltaire23 said:
No prob. well..you can always press my ""Thanks"" button..haha.
Click to expand...
Click to collapse
shinobisoft said:
Your help is appreciated, but asking for people to press the "Thanks" button is defeating the purpose of the "Thanks" button. The "Thanks" meter has no effect on your account and standings here at XDA.
Click to expand...
Click to collapse

Look man, it's upsetting to have the phone in Emergency Mode. August last year, my phone got stuck too, tried every program I could and never boot successfully. Took my phone to the store, they said they tried everything but they couldn't make it work. After a couple months with another device I decided to plug my LG P500 in to the computer and see if there was any new program available to flash. Strangely, my phone BOOTED in the stock rom and has been working flawlessly since. What I'm saying is, don't lose hope, this phone is amazing!

[Completed] [X620] - Black Screen,no boot only Red Light

Hello Guyzs, i'm totally newbie on Leeco Phone. My phone (Leeco Le X620) does not start anymore. I have only charge indicator that lights up (RED LIGHT). I try to follow this Topic : red-light-recovery-process
1 - Open FLASH TOOLS and chose DA_PL_HIGH (in my case that one worked, if doesn't for you choose DA_PL).
2 - Choose the MT6797_Android_scatter.txt
3 - Choose the Authentication file.
4 - Keep in DOWNLOAD ONLY
5 - Uncheck BOOT and RECOVERY. Keep the rest.
6 - Click DOWNLOAD.
7 - Phone needs to be OFF. Plug the phone (no volume up or down required). Let the process finish.
That will bring the phone to live again but it won't boot. Let's move forward.
8 - Press CTRL-ALT-V and chose OPTIONS>>WRITE MEMORY
9 - Choose the RECOVERY_STOCK_WORKS _AFTER_BRICK.img
10 - Write to address 0x8000.
11 - Phone OFF again, click WRITE and plug the phone (no volume up or down required).
After that another process
12 - Open FLASH TOOLS and chose DA_BR (PAY ATTENTION, THE FILE CHANGED).
13 - Choose the MT6797_Android_scatter.txt
14 - Choose the Authentication file.
15 - Keep in DOWNLOAD ONLY
16 - Uncheck BOOT and RECOVERY. Keep the rest. (AGAIN)
17 - Click DOWNLOAD.
18 - Phone needs to be OFF. Hold VOLUME UP and plug the phone. Let the process finish.
Now after all of these, you should be ready for the BOOT and RECOVERY.
19 - Open FLASH TOOLS and chose DA_BR (PAY ATTENTION TO THE FILE)
20 - Choose the MT6797_Android_scatter.txt
21 - Choose the Authentication file.
22 - Keep in DOWNLOAD ONLY
23 - CHECK ONLY BOOT
24 - Click DOWNLOAD.
25 - Phone needs to be OFF. Hold VOLUME UP and plug the phone. Let the process finish.
Repeat 19 to 25 for RECOVERY.
Click to expand...
Click to collapse
BUT:
DOWNLOAD :
secureboot\DA_PL_HIGH.bin
+
secureboot\MT6797_Android_scatter.txt
+
Only PRELOADER check
=
WORKS
after Write Memory :
ecovery_stock_works _after_brick.img
+
0x8000
=
WORKS
After DOWNLOAD :
secureboot\DA_BR.bin
+
secureboot\MT6797_Android_scatter.txt
+
Uncheck BOOT and RECOVERY. Keep the rest.
=
FAILED
ERROR MESSAGE :
BROM ERROR :STATUS_OPEN_FILE_ERR (0xC001000E)
Click to expand...
Click to collapse
I try with Mediatek SP Tool V5.1612, V5.1628, V5.1636 or .....Do you have an IDEA please ?
And last news,my PHONE is not recognized by SP Tool. Drivers Preloader Vcom don't appear but i used mediatek-Driver_Auto_Installer_v1.1236.00
I need help

Littleminx said:
Hello Guyzs, i'm totally newbie on Leeco Phone. My phone (Leeco Le X620) does not start anymore. I have only charge indicator that lights up (RED LIGHT). I try to follow this Topic : red-light-recovery-process
BUT:
DOWNLOAD :
secureboot\DA_PL_HIGH.bin
+
secureboot\MT6797_Android_scatter.txt
+
Only PRELOADER check
=
WORKS
after Write Memory :
ecovery_stock_works _after_brick.img
+
0x8000
=
WORKS
After DOWNLOAD :
secureboot\DA_BR.bin
+
secureboot\MT6797_Android_scatter.txt
+
Uncheck BOOT and RECOVERY. Keep the rest.
=
FAILED
ERROR MESSAGE :
I try with Mediatek SP Tool V5.1612, V5.1628, V5.1636 or .....Do you have an IDEA please ?
And last news,my PHONE is not recognized by SP Tool. Drivers Preloader Vcom don't appear but i used mediatek-Driver_Auto_Installer_v1.1236.00
I need help
Click to expand...
Click to collapse
Greetings and welcome to xda, it is difficult to help if your phone is not recognised. Where did you get the mod ? I have seen a little development for your device and a custom rom/recovery but they need fastboot
Good Luck
Sawdoctor

THX Sawdoctor
SURE
it is difficult to help if your phone is not recognised.
Click to expand...
Click to collapse
I have uninstalled and reinstalled PRELOADER Drivers several times but they are never used. Only the "MediaTek USB Port" driver appears and is used.
I think the phone is dead
Unless you know of another solution.

[Guide] Fix and Re-Locking Bootloader From Fake UBL

ULTIMATE GUIDE TO FIX ROM FROM FAKE UNLOCK BOOTLOADER​
Device: Redmi Note 5/Pro (Whyred)
Anti: 3 (required)
Initial Rom: Global/China with ARB v3
Method: Test Point
As we know that buying whyred from a distributor with a red box has a strange rom and also mi account that can't be binded. this is very troublesome when we want to unlock the bootloader..
This method is to really lock the Bootloader again, can bind Mi account and can be used for Unlock bootloader officially.
And finally, this method doesn't need to edit the script anymore, I upload patch scripts and loaders specifically for ROM 9.5.17 below.
It has been tested and the results are successful.
Let's start and DWYOR!
Step:
1. Download ROM 1 and ROM 2 below then extract.
2. Download the Patch then copy and replace it in ROM 1 which has been extracted (in the images folder).
3. Open back cover of the phone carefully and connect to the PC via Test Point (HS-USB QDLoader 9008)
4. Flash ROM 1 that has been patched with MiFlash (I use MiFlash 2017.4.25.0 and PC 64bit during flashing).
5. After success, close the miflash, unplug the cable, and turn it on. Wait a few moments until stuck in recovery mode (pict 1)
6. Connect Whyred to PC again via Test Point and Flash ROM 2 with MiFlash.
7. Wait for the first boot, after entering the system, check unlock status in developer mode and tadaaaa.. it's completely locked now... (pict 2)
8. Bind Mi account, continued unlock bootloader officially.
9. Done! ready to go to custom ROM
Note:
1. Patch is only used for ROM 1 (Global 9.5.17).
2. ROM 2 can use all China ROMs as long as still ARB v3.
Picture:
Pict 1
{
"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"
}
Pict 2
War Equipment:
ROM 1. (Global 9.5.17): LINK
ROM 2. (China 9.5.21): LINK
Patch: LINK
Just Hit THANKS Button for Supporting me..

Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.

poncespr said:
Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.
Click to expand...
Click to collapse
The same mistake is also available

poncespr said:
Any chance this guide can be updated for ARB4? At least the patch file?
Edit:
Nevermind, I see it cannot be done.
Click to expand...
Click to collapse
UtkuAblak said:
The same mistake is also available
Click to expand...
Click to collapse
sorry bro, currently only available for arb 3. refers to the difficulty of flashing if it has arb 4. coz the test point method in arb 4 must use an authorized account.
there is a guide to bypass this authorized account, but there are some reports that still fail.
this weirdness has been made xiaomi itself..

octodellin said:
sorry bro, currently only available for arb 3. refers to the difficulty of flashing if it has arb 4. coz the test point method in arb 4 must use an authorized account.
there is a guide to bypass this authorized account, but there are some reports that still fail.
this weirdness has been made xiaomi itself..
Click to expand...
Click to collapse
Stupid me that updated my RMN5Pro before reading these guides. Still is a great phone. Just wanted a taste of pie.

Mi phone deat
Sir, my nead mi authorized account please help me this my id 1813003637
---------- Post added at 05:50 PM ---------- Previous post was at 05:39 PM ----------
Sir my need mi authorized account please help me
This is my id 1813003637 sorry for my bad english

I have ARB3 device with fake ubl. I want to try this method, but I can not fully understand what we do with battery while short circuit the test points(5th step).
After writing 1st ROM, we connect the battery, then open device and stuck with recovery. After this (6th step), will I disconnect the battery again, while test point?

And another question;
while writing 1st or 2nd ROM which option we select with MiFlash Tool? "Clean_all" or "Clean_all and Lock" ?

How can I check for Fake UBL to be sure for 100% that I need this ?

netlogger said:
I have ARB3 device with fake ubl. I want to try this method, but I can not fully understand what we do with battery while short circuit the test points(5th step).
After writing 1st ROM, we connect the battery, then open device and stuck with recovery. After this (6th step), will I disconnect the battery again, while test point?
Click to expand...
Click to collapse
yes, like the first..
netlogger said:
And another question;
while writing 1st or 2nd ROM which option we select with MiFlash Tool? "Clean_all" or "Clean_all and Lock" ?
Click to expand...
Click to collapse
both can be used, coz basically our whyred is in locked bootloader.
but for sure, you can choose Clean_all and Lock
The4anoni said:
How can I check for Fake UBL to be sure for 100% that I need this ?
Click to expand...
Click to collapse
go to fastboot mode and run fastboot command:
Code:
fastboot getvar anti
if the displayed output is 3, is good. that means you can use this method.
if the displayed output is 4, you can not use this method.

octodellin said:
go to fastboot mode and run fastboot command:
Code:
fastboot getvar anti
if the displayed output is 3, is good. that means you can use this method.
if the displayed output is 4, you can not use this method.
Click to expand...
Click to collapse
I know how to check anti rollback... I want to check does my bootloader is fake unlocked or not

I copied the patch files to the ROM1 images folder.
I open miflash, selected the ROM1 folder.
I made the testpoint method, and I see driver 9008.
then clicked the refresh button then Flash button on miflash program. It writes "flashing".
Flashing process starts, but after that, it stucks while writing keymaster.mbn file. I waited over 20 minutes but nothing happened.
I tried another miflash from may 2018, but same situation.
I tried other USB ports, nothing changed.
I checked the log file. At begining it seems everything normal, but when it came to write keymaster.mbn file(this is the first file to flash)
The log file looks like this:
...
: Write file C:\RN5... ....\images\keymaster.mbn to partition[keymaster] sector 65536
: write file legnth 357392 to partition 65536
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
...
And gooes on like this for over 80000 lines. I closed the miflash.
I checked the phone, nothing happened, It opens normally, old rom still there...
what can be the situation?

The4anoni said:
I know how to check anti rollback... I want to check does my bootloader is fake unlocked or not
Click to expand...
Click to collapse
1. check in mi unlock status from developer mode
2. check from fastboot command: fastboot oem device-info
3. test to unlock bootloader
if you face unlocked in mi unlock status but in fastboot showing "Device unlocked: false" even more you can't bind account, thats mean you unlocked is fake.
netlogger said:
I copied the patch files to the ROM1 images folder.
I open miflash, selected the ROM1 folder.
I made the testpoint method, and I see driver 9008.
then clicked the refresh button then Flash button on miflash program. It writes "flashing".
Flashing process starts, but after that, it stucks while writing keymaster.mbn file. I waited over 20 minutes but nothing happened.
I tried another miflash from may 2018, but same situation.
I tried other USB ports, nothing changed.
I checked the log file. At begining it seems everything normal, but when it came to write keymaster.mbn file(this is the first file to flash)
The log file looks like this:
...
: Write file C:\RN5... ....\images\keymaster.mbn to partition[keymaster] sector 65536
: write file legnth 357392 to partition 65536
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
: WriteFile position 0, size 0
...
And gooes on like this for over 80000 lines. I closed the miflash.
I checked the phone, nothing happened, It opens normally, old rom still there...
what can be the situation?
Click to expand...
Click to collapse
1. make sure that you have extracted the patch. there are 3 files that must be replaced to the images folder in ROM 1 (Global 9.5.17)
2. use the miflash that I use
3. try to change clean all or clean all and lock, with flash_all.bat
hope it works for you ..

I allready tried that all of you wrote. But in windows command prompt mode, I tried to execute flash_all.bat with admin rights. It didn't work.
---------- Post added at 10:45 AM ---------- Previous post was at 10:42 AM ----------
I allready tried all. Nothing changes.
I tried to run flash_all.bat from command prompt with admin rights, but that does not work.

Bruh. Thanks a lot. This is the ONLY guide that has helped me fix my Note 5 Pro.
I was on global rom from the seller... I'm flashing a bunch of ARB 3 or lower MIUI roms... I accidently flashed with lock the bootloader...
That bricked my phone. No other roms would work. No china ones, no global. Tried so many patches until this guide which worked for me.
Thanks