Open olli991 opened 2 years ago
File Size Unknown on CP patching MST2_US_VW_PQ_P0253T.zip
File Size Unknown on CP patching MST2_US_VW_PQ_P0253T.zip
Added https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
File Size Unknown on patch swap and generate EL support.zip
File Size Unknown on patch swap and generate EL support.zip
Added https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Succesfully pached and activated mirrorlink , but after i pached CP i got boot looping and i have to do emergency update to restore the unit
( Below is picture at the finish of paching CP )
Succesfully pached and activated mirrorlink , but after i pached CP i got boot looping and i have to do emergency update to restore the unit ( Below is picture at the finish of paching CP )
Added sanity check to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
MST2_EU_SK_PQ_P0138T.zip Succesfully pached and activated mirrorlink , but after i pached CP i got boot looping and i have to do emergency update to restore the unit ( Below is picture at the finish of paching CP )
Added sanity check to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Installed this version of toolbox and same problem, after patch CP i get boot looping and i have to do emergency update
Below is screenshot of boot looping log with putty:
MST2_EU_SK_PQ_P0138T.zip Succesfully pached and activated mirrorlink , but after i pached CP i got boot looping and i have to do emergency update to restore the unit ( Below is picture at the finish of paching CP )
Added sanity check to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Installed this version of toolbox and same problem, after patch CP i get boot looping and i have to do emergency update Below is screenshot of boot looping log with putty:
Did you make a screenshot what happened at the patching time?
Hi, I'm publishing files dumped as in the instructions and I'm asking for help, because "standard" unit patching does not work :/
Thank you in advance for your help (: MST2_EU_VW_ZR_P0140T.zip
Dear All, tried to install toolbox but i am getting unknown file size detected when trying to cp off. unit runs MST2_EU_VW_ZR_P0131T
Hi, I'm publishing files dumped as in the instructions and I'm asking for help, because "standard" unit patching does not work :/
Thank you in advance for your help (: MST2_EU_VW_ZR_P0140T.zip
Someone badly patched your unit. Restore stock SWAP from stock 140 vesion by using Manual SW download option and then patch again.
Dear All, tried to install toolbox but i am getting unknown file size detected when trying to cp off. unit runs MST2_EU_VW_ZR_P0131T
[](url support.zip )
Added to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
MST2_EU_SK_PQ_P0138T.zip Succesfully pached and activated mirrorlink , but after i pached CP i got boot looping and i have to do emergency update to restore the unit ( Below is picture at the finish of paching CP )
Added sanity check to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Installed this version of toolbox and same problem, after patch CP i get boot looping and i have to do emergency update)
I beleive it is fixed in the https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip There was a typo in reset param. Fixed now.
Dear All, tried to install toolbox but i am getting unknown file size detected when trying to cp off. unit runs MST2_EU_VW_ZR_P0131T [](url support.zip )
Added to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
I did perfrom upgrade from MST2_EU_VW_ZR_P0131T to MST2_EU_VW_ZR_P0140T which worked just fine i then after thried to install toolbox which also looked fine When i tried to set CP off then the unit is in continious boot loop VW logo- bluemotion Logo off and again..... Any idea how i can restore unit?
Dear All, tried to install toolbox but i am getting unknown file size detected when trying to cp off. unit runs MST2_EU_VW_ZR_P0131T [](url support.zip )
Added to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
I did perfrom upgrade from MST2_EU_VW_ZR_P0131T to MST2_EU_VW_ZR_P0140T which worked just fine i then after thried to install toolbox which also looked fine When i tried to set CP off then the unit is in continious boot loop VW logo- bluemotion Logo off and again..... Any idea how i can restore unit?
Welcome to the club of owners of the 140T version, only I updated from the 138T version and already twice (even last night again) I restored the software according to the instructions (it only looks so hard, but it is really simple, you only need to buy a 3.3V encoder , even the VW dealer did not want to reinstall because the 138T and 140T software was issued with an error, this is what I heard at the VW dealer)
https://mibwiki.one/doc/technisat-pqzr-recovery-via-emergency-download-ssc0H3OtBI
Also after trying to patch CP, which as you can see in my and your example in these units, leads to loops, so in this topic I try to figure out how to straighten it all out with the creators of the TOOLBOX, today the sixth approach ...
Hi, I'm publishing files dumped as in the instructions and I'm asking for help, because "standard" unit patching does not work :/ Thank you in advance for your help (: MST2_EU_VW_ZR_P0140T.zip
Someone badly patched your unit. Restore stock SWAP from stock 140 vesion by using Manual SW download option and then patch again.
Thank you for the information, I also suspected something was wrong. I know that for you the statements "using Manual SW download option" are something banal, but I would like to ask for more detailed tips, i.e. whether restoring SW from MANUAL DOWNLOAD involves downloading pure software 140 / preparing the card and updating or restoring the default version of the system from the installed currently software?
MST2_EU_SK_PQ_P0138T.zip Succesfully pached and activated mirrorlink , but after i pached CP i got boot looping and i have to do emergency update to restore the unit ( Below is picture at the finish of paching CP )
Added sanity check to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Installed this version of toolbox and same problem, after patch CP i get boot looping and i have to do emergency update)
I beleive it is fixed in the https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip There was a typo in reset param. Fixed now.
In this TOOLBOX you fixed issue when after patching CP unit starts to loop over again? Can i also use it on 140T software?
Dear All, tried to install toolbox but i am getting unknown file size detected when trying to cp off. unit runs MST2_EU_VW_ZR_P0131T [](url support.zip )
Added to https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
I did perfrom upgrade from MST2_EU_VW_ZR_P0131T to MST2_EU_VW_ZR_P0140T which worked just fine i then after thried to install toolbox which also looked fine When i tried to set CP off then the unit is in continious boot loop VW logo- bluemotion Logo off and again..... Any idea how i can restore unit?
https://mibwiki.one/doc/technisat-pqzr-recovery-via-emergency-download-ssc0H3OtBI
As I assume that you got reboot loop after using the latest version we can admit that something wrong is happening after patching CP on 01xx units. But you can try to analyse yourself if you are interested: https://github.com/olli991/mib-std2-pq-zr-toolbox/blob/64b17f9317ab6a2a5ea661dc031fb6af5f9376d1/cpu/onlineservices/1/default/tsd/etc/persistence/esd/scripts/patch_cp.sh
Hello again, After the last CP patch attempt and fall into a boot loop, on your advice I got the system back to P0140T (emergency download), installed the newest TOOLBOX and made 2/3 patches (SWDL / SWAP) again. I'm attaching my new SUPPORT data dump and can I ask for a "look" of a specialist and for any advice what is the probability that after applying CP patch (3/3) I will have to recover the system through EMERGENCY DOWNLOAD? again (:
support-MST2_EU_VW_ZR_P0140T.zip
Thank You!
I thought that update 1.1.2 was dictated by my next attempt to patch CP for the third time, so first I updated the TOOLBOX, and then turned on CP patching for sure ... Unfortunately, it will probably have to be withdrawn because it did not fix CP patching in ALL 01xx firmware because the third time I restart my firmware (0140T) through emergency downoad ... Someone, help?
Hi, Unknow on CP and SWDL, SWAP is good. Thank MST2_US_VW_PQ_P0359T.zip
I thought that update 1.1.2 was dictated by my next attempt to patch CP for the third time, so first I updated the TOOLBOX, and then turned on CP patching for sure ... Unfortunately, it will probably have to be withdrawn because it did not fix CP patching in ALL 01xx firmware because the third time I restart my firmware (0140T) through emergency downoad ... Someone, help?
Added sanity checks for 1xx in https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip Now it should not create a bootloop situation anymore. Can you check it out please?
Hi, Unknow on CP and SWDL, SWAP is good. Thank MST2_US_VW_PQ_P0359T.zip s
Added in https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
I'm downloading and in 1-2h i'll try to do it on my fresh EMERGENCY DOWNLOAD firmware, again... We will see if I will have to do ED for the fourth time (: fingers cross...
Well, I tried... It's not too bad, but it hasn't happened yet ... I haven't done a reboot, so I don't know if it can also get into a loop after a failed attempt? What now? Help?
The update worked on swdl, but CP still failed. Here's the message I got
Well, I tried... It's not too bad, but it hasn't happened yet ... I haven't done a reboot, so I don't know if it can also get into a loop after a failed attempt? What now? Help?
Please install update and try again https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
j5startup_size=$(ls -l /net/J5/tsd/bin/system/startup_main | awk '{print $5}' 2>/dev/null)
they shouldn't be...
j5startup_size=$(ls -l /net/J5/tsd/bin/system/startup | awk '{print $5}' 2>/dev/null) ???
... also you should to try remove this fragment:
if [[ "$size" == "1852137" || "$size" == "1851273" || "$size" == "1850369" || "$size" == "1850393" ]]; then echo "else" >>/net/imx6/tsd/bin/system/startup_main echo " /tsd/bin/system/wd_procterm.sh 'tsd.mibstd2.main.root' J5e.MCP 0 "'"main.root crash"' >>/net/imx6/tsd/bin/system/startup_main fi
in my opinion this is the reason "bootloop" sw01 ... although I would like to see log.txt from putty
support dump blocked ([MST2_EU_VW_ZR_P0478T)
tanks
Well, I tried... It's not too bad, but it hasn't happened yet ... I haven't done a reboot, so I don't know if it can also get into a loop after a failed attempt? What now? Help?
Please install update and try again https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Unfortunately, this time also the message as below ...
support dump blocked ([MST2_EU_VW_ZR_P0478T)
tanks
What is on the previous screen?
Well, I tried... It's not too bad, but it hasn't happened yet ... I haven't done a reboot, so I don't know if it can also get into a loop after a failed attempt? What now? Help?
Please install update and try again https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Unfortunately, this time also the message as below ...
@to0nk Applied some changes https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
@yox2019 we need that else because on 1xx the startup looks like:
on -p 20 /tsd/bin/root/tsd.mibstd2.main.root -file=/tsd/etc/system/main.conf -reset=/net/imx6/tsd/var/root/reset.count.main
RET=$?
if [ $RET -eq 0 ] ; then
echo "main.root terminated -> calling shutdown script"
# source it to avoid spawning a new shell
. /tsd/bin/system/shutdown
echo "shutdown finished!"
elif [ $RET -eq 42 ] ; then
echo "MP42 set to low! -> Boot Stopped."
else
/tsd/bin/system/wd_procterm.sh 'tsd.mibstd2.main.root' J5e.MCP 0 "main.root crash"
fi
@Iprot ... I understand, only that this fragment is about "emergency" and actually in startup_main it is out of context, so it can cause problems but I might be wrong, if everything is ok then fine, if it is "bootloop" again try to delete it ... just your concept, my suggestion :)
... I mean this one: /tsd/bin/system/wd_procterm.sh 'tsd.mibstd2.main.root' J5e.MCP 0 "main.root crash"
I'm getting this on both my unit. The 1.1.1v works fine on my bench unit (SWaP,SWDL,CP works), but SWDL and CP doesn't work on my car unit for 1.1.1v. The latest master files (CP) doesn't work on any of the units, but SWaP and SWDL does. I've attach a picture of the error.
Both unit are MST2_US_VW_PQ one is a TechiSat and the other is a Preh
h
use this one: " Applied some changes https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip "
and show your outcome
support dump blocked ([MST2_EU_VW_ZR_P0478T)
tanks
What is on the previous screen?
here it is, in order .... I hope.....
Well, I tried... It's not too bad, but it hasn't happened yet ... I haven't done a reboot, so I don't know if it can also get into a loop after a failed attempt? What now? Help?
Please install update and try again https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
Unfortunately, this time also the message as below ...
@to0nk Applied some changes https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip
@yox2019 we need that else because on 1xx the startup looks like:
on -p 20 /tsd/bin/root/tsd.mibstd2.main.root -file=/tsd/etc/system/main.conf -reset=/net/imx6/tsd/var/root/reset.count.main RET=$? if [ $RET -eq 0 ] ; then echo "main.root terminated -> calling shutdown script" # source it to avoid spawning a new shell . /tsd/bin/system/shutdown echo "shutdown finished!" elif [ $RET -eq 42 ] ; then echo "MP42 set to low! -> Boot Stopped." else /tsd/bin/system/wd_procterm.sh 'tsd.mibstd2.main.root' J5e.MCP 0 "main.root crash" fi
Well, unfortunately ... For the fourth time I am starting the EMERGENCY DOWNLOAD ... Thanks for arranging the Friday evening (: but if someone had an idea that effectively patch CP on my unit, I will try to do it (:
@to0nk all fine but why didn't you include log.txt (during bootlop) which I asked for? ... if you want help, give something from yourself, not everyone has a unit with sw 01 ... that's why without logs it is difficult to diagnose the problem, although I gave some suggestions for the author
"Thanks for arranging the Friday evening (:" ...you know what ? you can always go to the dealer and remove the cp, respect someone's spare time
Hmmm ... You know, I did not think that your post was directed to me, the more so because there was no tag, from my post there were already two others and I thought that, as Iprot does, it marks the discussion addressed to me, between posts you can see three different threads ... Now I know that I have to use TOOLBOX from your post, because the last one downloaded was the one from Iprot.
So again ... I have a clean system already uploaded, now I have to apply the TOOLBOX to all 3 patches and then let you know? What period / activity do you need the putty log for? It's hard to keep up with the topic as there are no references to entries / people. Sry ...
P. S. "Thanks for arranging the Friday evening (:" that was a JOKE! I count with that I will have to restore the system, THATS WHY I DID IT ON FRIDAY EVENING, and not on the day when I use the car ... I suggest looking for a sense of humor ... did you not notice that by "experiments" on my MIB2 the project improvement / development is growing? . I don't know if it's an association of old bastards or pretentious nerds complaining about everything ... If you dont want to develop this project I can go to dealer, just inform me.
I don't know if it's an association of old bastards or pretentious nerds complaining about everything ... If you dont want to develop this project I can go to dealer, just inform me.
is it for me? ...listen my friend, if you really want to support this project, have an idea and send the logs, putty has the option to save the log.txt, I can't change the content of the script, but maybe the author will take into account my comments, so wait or if you know how to do it, do it yourself ... all that is needed is the putty log during bootloop from boot / reset
@to0nk ...please install it, then after applying "cp patch" and before restarting, connect the unit to putty, set log.txt and then restart the unit mib-std2-pq-zr-toolbox-test.zip
... the second "patch" folder contains the script I changed patch_cp.zip
------Edit Important!!!-------------
one more important thing before applying "cp_patch"
... after installing TOOLBOX activate "permanent console access" first ... then restart the unit and do what I wrote above please i.e. add a cp_patch and make logs.
... now, if the unit goes into "bootloop" again DO NOT USE EMERGENCY !!! ... just connect to putty press "ENTER" and copy and paste this command: mount -t qnx6 -o remount, rw /dev/hd0t177/ &&rm /tsd/bin/system/startup_main and press "ENTER" and restart the unit
... after that the unit will be like before "patching" cp :)
@zibroun your SD card is read only :)
use this one: " Applied some changes https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip "
and show your outcome
This one is good. Works on both my unit. Thanks
use this one: " Applied some changes https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip "
... abracadabra :)))) thanks for the notification, this version works for you at @to0nk not hmmm.... ... we are waiting for the log.txt from @to0nk
use this one: " Applied some changes https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip "
... abracadabra :)))) thanks for the notification, this version works for you at @to0nk not hmmm.... ... we are waiting for the log.txt from @to0nk
@yox2019 Because KamboSoup's unit is fw359.
@to0nk it will be much more easy and productive if you:
rm /net/imx6/tsd/bin/system/startup_main
then bootloop will stopBecause KamboSoup's unit is fw359.
@lprot I already have a "reel" in my head :))) ad.2 "rm /net/imx6/tsd/bin/system/startup_main" ...this command will not work, because the system must be read / write first also you do not need to enter the full path, because after activating the console you are already on imx6, so again:
mount -t qnx6 -o remount, rw /dev/hd0t177/ &&rm /tsd/bin/system/startup_main
@to0nk ...please install it, then after applying "cp patch" and before restarting, connect the unit to putty, set log.txt and then restart the unit mib-std2-pq-zr-toolbox-test.zip
... the second "patch" folder contains the script I changed patch_cp.zip
------Edit Important!!!-------------
one more important thing before applying "cp_patch"
... after installing TOOLBOX activate "permanent console access" first ... then restart the unit and do what I wrote above please i.e. add a cp_patch and make logs.
... now, if the unit goes into "bootloop" again DO NOT USE EMERGENCY !!! ... just connect to putty press "ENTER" and copy and paste this command: mount -t qnx6 -o remount, rw /dev/hd0t177/ &&rm /tsd/bin/system/startup_main and press "ENTER" and restart the unit
... after that the unit will be like before "patching" cp :)
Well, now we can experiment, only for your entry I have two things:
I have to install the TOOLBOX first from the link provided by you AND REPLACE "patch_cp" in it before applying the patch? Because I do not understand why you provided a link to the entire TOOLBOX, and then to only one file that you changed without adding it to the installation at the link provided by you?
You must forgive me for delay, but only after I "get rid of" the children I will start patching, the results will be published around 18:00 / 19:00
P.S. As I can see above, everyone pops up with their corrections, let me follow one because this way it gets confused whether I should use this or that command, I am one intermediate computer scientist and you are people sitting on the subject, so give a little breath (:
@to0nk no.... just install "mib-std2-pq-zr-toolbox-test.zip" from the link provided, scrypt is already changed there
... the second folder "patch_cp.zip" is only to compare what has been changed
... don't forget first: " 1.enable permanent console access in Toolbox Network menu" and in case of problems "bootloop" use this command please:
mount -t qnx6 -o remount, rw /dev/hd0t177/ &&rm /tsd/bin/system/startup_main
just copy this command from this post and paste it into putty terminal then hit "Enter" and restart unit
@zibroun your SD card is read only :)
I'm a fool ..... thanks a lot it worked !!!! I attach support files .... cp removed, swap no !!!! MST2_EU_VW_ZR_P0478T.zip tanks
@to0nk no.... just install "mib-std2-pq-zr-toolbox-test.zip" from the link provided, scrypt is already changed there
... the second folder "patch_cp.zip" is only to compare what has been changed
... don't forget first: " 1.enable permanent console access in Toolbox Network menu" and in case of problems "bootloop" use this command please:
mount -t qnx6 -o remount, rw /dev/hd0t177/ &&rm /tsd/bin/system/startup_main
just copy this command from this post and paste it into putty terminal then hit "Enter" and restart unit
Well, I managed to jump out a moment before the children's dinner, I did as you ordered, installation / activation of the console and CP patch ... And it entered the loop again, but I also got a recipe from you for this problem, but unfortunately I have to surprise you , after entering and confirming the code, I received a comment -> "there is no such directory" and the loop repeats ... Of course, I connect the log from the very beginning of putting putty on, please let me know if I should start an EMERGENCY DOWNLOAD, because tomorrow I have a trip with the children and i will not sing in the car without a radio (:
@to0nk ok did you applied only "cp" patch or "swap" and "swdl" as well ? ... sorry there was "typo" error in this command... this one is ok :
mount -t qnx6 -o remount, rw /dev/hd0t177 / &&rm /tsd/bin/system/startup_main
was missing "space" after: mount -t qnx6 -o remount, rw /dev/hd0t177...
put this command again please
Please place your support dumps in this issue.
This applies to:
How to make a support dump?![Screenshot](https://user-images.githubusercontent.com/55631413/158680592-9e2765ec-89e1-4418-9b0e-b669b4680bdb.png)
You can find it in the "Tools" screen below the patch scripts. You'll find the filedump in the new .../support folder in the dump section of the SD card. Please zip the whole "support" folder and upload it to this thread.