Quote:
Originally Posted by kippsoft
Hi guys...
After alot, alot of work and problems...
I am happy to announce to you that I found solution to your Alcatel OT-918(All)..
Pre-requisites:
SP Flash tool(I have attached it)
One Touch Upgrade from Alcatel site
The 3 Alcatel ROM files(Attached)
Fully charged phone.
Steps
Download the appropriate ROM file for your phone and extract it to a folder.
Download Alcatel One Touch Upgrade for your phone ...Click here for Alcatel OT-918 Upgrade Tool...
Download the SP Flash tool(Attached)
Install appropriate USB drivers for your phone..
Using SP Flash tool push the 3 files(Download) to the smart phone...click here is an example of how to download...
Ensure it is successful..
Remove phone's battery,re-insert.
Open the upgrade tool and follow its help file on how to upgrade.
Thanks
NOW MY PART
-------------------------------------------------------------------------------------------------------------------------------
PLEASE NOTE THAT MY PHONE IS OT-918D
I didn't even know what was the imei of the phone was or the phone model but used SP-FLASH tool with many different versions of scatter files untill I came across the one that was used for installing recovery on ot-918 from a different website.
I even got to the point that the phone wouldn't come on after trying different models of the 918, but luckily usb worked.
WHAT YOU NEED
SP_Flash_Tool
One Touch Upgrade from Alcatel site
Scatter Files in the zip file below.
FILES TO USE ON THE SP-FLASH TOOL:
MT6573_Android_scatter_2_3_5_OT_918.txt
AND TICK THIS FILES :
dsp_bl
preloader
pro_info
NOTE: sometimes you have to press and hold the center button for the phone to be detected in order to accomplish the above procedure. Just make sure you remove the battery each time you try..
Then open the Alcatel Upgrade tool , this time it won't tell you that your phone is already up-todate. then proceed with the upgrade.
NB:MAKE SURE YOU USE A LOWER ANDROID VERSION E.G 2.3.5 SCATTER FILE OR ELSE ALCATE UPGRADE WILL SAY PHONE ALREADY UP TO DATE.
This applies to even a phone that won't come on(Mine was dead and couldnt come on only charging, and after fixing it, I discover that I had spoiled the display fiber since the phone was not displaying anything.)
Unfortunately I had to do the whole thing from a dead screen after pulling it apart prior to unbricking it.
You can find your serial number and phone model in the Alcatel upgrade file called otus_log.txt
Incase mine was in C:\ONE TOUCH Upgrade S 2.8.0\otus_log
I think that this method might work on all Alcatel MT65xx Phones.
But now that the phone works I have to get a new display.
918 Is dual sim !
After puling apart my phone which I have always assumed to be single sim(This apparently caused alot of confusion as to which Rom to use), I realize a second Sim card slot right beneath the top slot although it's hidden and not accessible if you replace the chasis , so you guys might want to try a possible second simcard for you 918 phones, that I suppose is the reason why some guys could install dual sim roms and fail to access fast speed since it's using the secondary sim card, I haven't tested it since I have not acquired the screen yet.
every now and then while experimenting new roms one either brick his phone or loses all their secure files like nvram and etc
either way you have lost your imei which is the sole reason that you can use your sim
well if you find yourself in this situation and have a phone with a mediatek processor then don't worry i got you
so all you need is your firmware,sp flash tools,SN writer and of course drivers
so what you need to do is install your drivers (cdc is a tough one you can find other posts in xda itself for installing it)
then just for heck of it because you cant be sure that you have the same firmware as the one you downloaded use sp flash tools
to flash the firmware (use firmware upgrade option or format+download option i prefer the latter)after you are done flashing
open SN writer and go to settings and choose your ap_db and md1_db now the trick to this is if you have two apdb and md1db then you have to find out which one is the correct by trail and error if not,you lucky dawg if nothing else works turn on auto gen option
in identify and keep on trying till your phone gives up and trust me it will give up
p.s i am new at this so like go easy on me
p.s p.s i will upload some pictures in the near future
I have created boot recovery files based on Samsung's pdf titled "[14-96]_Boot_Recovery_Guide_Qualcomm_APQ8084_[includes_SM-N910F]__Rev_3.0"
These were done on a 32gb clas 10 microSD, they are imaged to a file via Norton Ghost portable (GHO file.
If your note doesn't boot, that might help. (No charging light, PC detects as QHUSB 9008 mode etc)
Download these GHO files and norton ghost portable.
Insert an empty microSD, Open norton ghost > Local>Image>to Disk the choose your microSD.
Your disk capacity might show up less, but don't worry, you can restore later on with Minitools (Check online on how to use).
I have also created an eMMC backup image of n910p running MM (PE2 build version)
It's a 2gb file, on unzipping with 7zip, around 4gb. (While creating, the output from adb shell is shown in the pick. Not sure if it's an error... is it supposed to be bigger? it was on a clean stock but rooted.. no user content)
Follow this guide http://www.droidsavvy.com/unbrick-qualcomm-mobiles/ to check it's in new 9008 mode.
Then my file might work for you.
All files are at https://mega.nz/#F!qRAGBZDY!_k24QWYaA0We2IQoAgE2Ng
Hi,
and Thanks
Well I have tried these Gho files but no joy. Ghost says file sizes are 19. After writing to the mirco SDCard there is no spaced used and 3 folders that are blank.
I am looking for these files below to recover to use QPST (QFIL) / MiFlash , maybe you can extract them from your device but I have no idea how to do it.
MPRG8084.hex
-8084_msimage.mbn
-rawprogram_32GB.xml
-patch0.xml
-Settings.xml
Thanks
dray_xclusive said:
Hi,
and Thanks
Well I have tried these Gho files but no joy. Ghost says file sizes are 19. After writing to the mirco SDCard there is no spaced used and 3 folders that are blank.
I am looking for these files below to recover to use QPST (QFIL) / MiFlash , maybe you can extract them from your device but I have no idea how to do it.
MPRG8084.hex
-8084_msimage.mbn
-rawprogram_32GB.xml
-patch0.xml
-Settings.xml
Thanks
Click to expand...
Click to collapse
And my phone its same
I hope to find way to solve it
i have also same issue does any one solve ?
an interesting read... curious, under what circumstances would this be more convenient / more practical than a simple odin flash?
is this supposed to recover hard bricks / bad bootloaders?
Took N910P back to Sprint.
I experienced my problem when I was using my secondary (not activated, clean esn) Sprint N910P as an MP3/MP4 player. After the last update which i don't know... it would not boot into the OS after the Sprint splash screen, so it would continue to do this constantly after removing the battery and rebooting even after optimizing apps screen. I researched and found XDAs forums with a lot of How tos, troubleshooting and workarounds. Long story short the Reactivation Lock was not disabled and even using the techniques supplied here I did not have any success.
I took it to the Sprint store and they deactivated my Primary LGV20 and activated the Note 4 so they could service it and then flash it to the current OS. They couldn't flash it and were going to have to send if off to replace the motherboard or replace the phone. The tech told me that this has been happening to Sprint Note 4 phones after an update and since it was a update error there will be not charge to me. Now I had insurance on the Note 4 for six years prior to upgrading to the LGV20, so they had to activate it to be able to service it. I will update their findings when i receive my phone in 7 to 10 days.
I pray this helps someone in my situation, as for me it is bittersweet. I didn't fix my phone but I found a new forum and I can tell everyone here is as passionate about what they do as I am!
- Jacob
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
FILES USED IN THIS POST>https://forum.xda-developers.com/g4/general/vs986-ls991-firehoseprogrammer-raw-t3670375
Having trouble?
gratefuldeaddougie said:
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder.
It appears as if some body else has stumbled upon this 4 months befor I did, back in May. Here is his Guide> http://forum.gsmdevelopers.com/showthread.php?t=28897&highlight=VS986+REPAIR
I understand the guide, but I'm confused on what you mean by "don't rename the laf.img file" because when I got the needed files from the kdz file, I got a laf.bin file but not a laf.img file. Do you mean rename the laf.bin to laf.img?
gratefuldeaddougie said:
FILES USED IN THIS POST>https://forum.xda-developers.com/g4/general/vs986-ls991-firehoseprogrammer-raw-t3670375
Click to expand...
Click to collapse
I need help with LS991ZVI
gratefuldeaddougie said:
This is my universal LG 90 minute method to virtually unbrick the most stubborn of bricks. This dilemma concerning the Verizon varient not getting any unbrick love has been making me ill. Let us, with the VS986_9008's, take the QDloader to the Mortal Combat ring And show it the "9008 Fatality". This takes about 90 minutes and sheds an unbelivable amount of light on a larger scale. I am starting this thread due some "lurkur guilt". I've been silently creeping around XDA since 2012. Not a single THANX button, post, comment, or even regerstering a user name. I have gathered all the things to revive this device here on XDA. So there is no need to go anywhere other than download mirrors provided by authentic XDA members. Well. First. Along over due shout out to the Devs whom I owe appreciation to, and they don't even know it yet. This is a long list. THE Greatest of THANX & PRAISES to GameTheory, PlayfulGod, Mazda, Steve Kondick, ChainFire, LaserWolf, roirrawdaor, RootJunky, Roark 13, and many more. Most importantly the main body of the Xda Developers that work painstakingly consistant on keeping these forums spam and malware free. Thank You for all the patience and for the most part, compassionate and keeping the sarcasm down to a minimal when dealing with noobs' questions at times when all any body ever wanted was a greater understanding of the Android OS. It displays a level of understanding and Professionalism that is so scarce in this technological revolution era. Never a noob joke. Very Cool. So very, very cool. I have never done this before so here goes........ One more thing be fore we start. I will not be providing download mirrors, links, or subsections of instructions on how to use these tools. I am leaving the greater portion of the learning curve to the reader. Big Tip: Search Plus is your greatest friend. Drum Roll Please.......................................................................................................................................................................You will need these 1) VS98627C_00_ARB02.kdz
2) VS98613B_00_ARB02.kdz 3) LGMobileDriver_WHQL_Ver_4.2.0.exe 4) QHUSB drivers (Qualcomm drivers) 5) QFIL (latest version) 6) WindowsLGFirmwareExtract (latest version) 7) LGUP and 8992_dll.msi (LGUP for G4) 8) LS991_ARB_02_RecoveryImage.zip (Yeah. I know it's for sprint. Just trust me.) This is done in stages so maybe a small break to stand up and stretch in between each phase is a protocol to follow. FOR SANITY. PHASE ONE: When all the needed files are chill'in on your desktop create a new file and name it "VS986 Firmware Recovery" extract the LS991 RecoveryImage to it. Now delete these laf, tz, pmic, rpm, hyp, sdi, sbl1. Using WindowsLGFirmwareExtract ; extract the VS98627C.kdz . We now take the VS98627C laf, tz, pmic, rpm, hyp, sdi, and sbl1 files and move them to our "VS986 Firmware Recovery" folder. Last but not least rename the file extensions of those from bin to mbn. But do not rename the laf.img file. Congrats. you just made a recovery image for the verizon varient of the G4. If you didn't Know how to use the kdz extraction tool. You do now. Isnt learning Android a Blast. PHASE ONE COMPLETE PHASE TWO: Like I said in the begining.. I am not giving Tuts on the use of tools or driver installs. - Iinstall the LG drivers / install the Qualcomm drivers / install LGUP and 8992_DLL.msi / Reboot PC / Go Pee PHASE THREE: Open up the back of your G4 but leave the board intact in the chassis. If you have never done this before then I suggest a youtube search to get you up to speed. With the phone open and your PC freshly booted, open up DEVICE MANAGER and force the G4 into QDLOADER 9008 mode using the test points. Again there are more than enough Threads on this topic. Open QFIL Double check the comm port number in device manager compared to comm port connection in QFIL. Make sure they are the same. IF QFIL does not recognize your connected phone than driver installation school should have held you back for that lesson. When you're all good up to this point....... Tick the "FLAT BUILD" box............. load "prog_emmc_firehose_8992_lite" found in the folder you created................. rawprogram0.xml and patch0.xml should load automatically. If they do not then load them manually. Click DOWNLOAD button. This should result in a successful flash of the laf image, except in the case where the device has the dreaded G4 hardware curse. If the logic board has no issues there should not be a problem. Upon success/pass of flash, disconnect the phone from the PC and put back together you device. PHASE 4::: This should be easy. Hold volume up. Plug into PC. Continue to hold volume rocker up untill FIRMWARE UPDATE screen displays. Use LGUP to flash the VS98627C.kdz and if you like downgrade to 13B for root and start all over. What do you mean to tell me you are not familiar with download mode? What in tar nations are you doing here? Did you try the SEARCH PLUS feature?
Click to expand...
Click to collapse
Hi!
I need to know if I can go back to the original fastboot mode of my lg vs986 because the flashed one is from the ls991, and that's a problem bacause when you plug the device to the pc staying in fastboot mode it won't be visible, I think is a driver problem that cause incompatibility, I've lost my imei after try with other tutorials and that's why I need to restore it, I need to entry on fastboot mode (done), I'm actually using "usu unlock" tutorial, It has unlocked fastboot mode but still being the ls991 one.
the other points are nicely explained but I AM little confused in one point in which you mentioned don't rename the files what is its mean please help me to understand that point.
Hello Guys
My friend ask me for get a Lineage OS to his H815 with Nougat. I agreed as I made few successful changes from stock to Lineage OS with Samsungs and older LGs (like L3 E400). But G4 is really more complicated, more than I expected . Firstly I wanted to unlock this phone with FWUL, so I download a VirtualBox emulated image with FWUL and after it boots I opened SALT program and it detects the phone. I made a basic backup and then I choosed Unlock G4 (UsU). After that some windows pop up. Last window was a pre-checking, when the bar gets to the end window closed and nothing more was happening. So after almost hour of waiting I just turned off the phone - I thought its all. After that while phone is booting I have those messages in the left top corner:
[820]-----------------------
[870]
[920] Secure boot error!
[970] Error code : 1009
[1020[ OFFICIAL !!
[1070]
[1120]-----------------------
Its booting, but only sometimes its normal boot, most starts are with bootloop, sometimes its start after 10 restarts, sometimes after 2nd restart, sometimes after plug in/plug out USB cable it starts boot normally (connecting cable only to phone, not to PC), sometimes only thing that helps is to take out the battery. I made full wipe to be sure that its not a software problem, but only thing I achived with that is fact that phone has a Nougat and now it have a Marshmallow. It is (was?) H815, but now model name is LGLS991 (?), it gets very long until it shows software version (V20g), IMEI is unknow, even when I type *#06# I get the null response.
I can get into recovery, can put phone into download mode. But i'm not able to do anything to get LOS or a least Nougat.
I've read many, many tutorials how to get G4 working properly after unsuccessful unlock, but nothing helps. What I've tried:
1. Flashing stock Nougat for H815 with LGUP, installed USB drivers, proper DLL, set com to 41, but when I trying to flash, after a 4% i get error: KDZ file is invalid. Downloaded few KDZ firmwares, dont belive that every single one is invalid, there is something wrong with LGUP or with settings, but I cant find what
2. Flashing with LG Flash Tool 2014: tried both normal flash and cse flash and always stoping in the same moment, with "Connection to server failed. Try again in a moment". Read many tutorials about this error, none was helpful in my case.
3. Flashing with LG Flash Tool v1.8.1.1023 and a TOT file, but after select of dll and tot file and press the yellow arrow I get an error: "Failed PreviousLoad()"
Tried all this methods on second computer but without a luck.
What else can I try to get this G4 working properly? Maybe try to install some rom from stock recovery? But which rom will be ok and dont get things worst?
If you need more info dont hesitate to ask. Would be very greatful for any advices .
you definitely didn't read enough... go to read again the UsU thread and as you've read the whole tutorial, you can also read the whole FAQ and the OP, because 90% of what you pointed out in your publication (which incidentally is in the wrong section) is explained there.
A quick advice: Don't try to flash any KDZ/TOT again.