Hi!
On any S4 mini (GT-I9195) which has the OLD bootloader without Knox is it possible to backup bootloader partition and restore it to any other S4 mini which has the NEW bootloader?
I mean usind the dd command like this:
Code:
dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1.mbn.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl2.mbn.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl3.mbn.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/aboot.mbn.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/rpm.mbn.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/tz.mbn.img
And the restore to device with Knox again with dd command, like for example:
Code:
dd if=/sdcard/aboot.mbn.img of=/dev/block/mmcblk0p5
Should the above work or it will brick the phone?
Update #01:
My friend has S4 mini with older bootloader (no Knox) and successfully executed the backup commands above (where if=/dev/... ).
Now I have all those files but I'm not sure whether the restore commands will work and the device "survives".
Attached there is a package of files -> old bootloader
Update #02:
Recevied another old bootloader package from another friend with I9195. Attached.
Can anybody with MJ7 firmware try the reverse DD commands?
Risky operation, device can be bricked!
I think... think... think... my opinion:
Look. If I read something about PIT Magic :
PIT files contain the Partition Information Table (PIT) for Samsung Android phones. Different firmware versions may require different partition layouts so the necessary PIT file 'tells' Odin how to set up the phone partitions correctly for the specified firmware to be installed.
The PIT file contains all the relevant information for each required partition such as Partition Name, Flash File Name, Block Size, Block Count etc. and also contains some unknown properties that maybe identifiers or flags of some sort.
What see Odin on Pit file? Many data about files that it must flash like block size, block count, attribute, etc.
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 5 -------------------------------->> Partition Number.
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 132.864
Block Count: 4.096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash FileName: aboot.mbn
I don't agree that command dd on terminal emulator can make the same like Odin. We must include some parameters like BS, Count, Attrib, and more in my opinion.
See example for extract a Pit file.
I attach a cmd to extract the pit file 16 GB from the phone, a out.pit made by this cmd and the pit file extracted by PIT Magic. All from i9195.
Then I Quote You : Risky operation, device can be bricked!
Hey guys! I am in deep trouble (or so I think). I just came back from my Winter vacation but sadly I left my Note 3 behind at my brother's house. I won't be getting it back anytime soon (literally) so I'm back to using the Galaxy S3 as my main phone. Though I wasn't using the S3 as my main phone, I still kept it up to date with the new things (Gummy 4.4.2 with the newest CWM and Ktoonsez (12.20.13 release)).
My problem relies here when I decided to flash a new ROM and tried entering my recovery and got slapped with an Android with a loading bar. It quickly rebooted my phone back and I thought, "CWM is notorious when it comes to issues" and so I went on and flashed TWRP 2.6.3.1 through GooManager. I rebooted into recovery and got slapped again but this time, it was telling me this: "Running OpenRecoveryScript... Installing Zip" follow by an "E:" error. These were the E: errors I was getting:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.
I've tried reinstalling the recovery numerous amount of times just to be presented with the same error.
My instincts tells me to Odin back to full stock so it would repartition the recovery but my curiousity asks me, "What if you can't go into the recovery to factory reset in order to boot into the Android firmware?" That would only mean I would be stuck with a phone that hangs in the Samsung logo screen.
I've also discovered that my root cache folder (Cache Partition or so I think) is completely empty (apparently, that's where the recovery folder is suppose to be and such) but for some odd reason, my phone is fully functional (apps, texts, phone calls, etc..) with the exception of entering Recovery Mode.
What should I do before making any kind of moves (my phone is fully functional with the exception of entering recovery mode)?
Recovery Partition is completely different partition from Cache. What you should be doing is flash TWRP with the help of ODIN.
Perseus71 said:
Recovery Partition is completely different partition from Cache. What you should be doing is flash TWRP with the help of ODIN.
Click to expand...
Click to collapse
Thank you for taking the time to read and respond to my question
I'll try doing that and see if it'll work. I've tried installing TWRP through Terminal Emulator and used the this command to push the recovery into the mmcblk0p18 (recovery partition):
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Sadly it didn't work but I will try using your method and see where it'll go.
With Samsung Phones, There is a utility called ODIN that takes out all the hassles of ADB push to the correct partition. There are plenty of Video tutorial on usage of Odin. Here's the main thread.
Perseus71 said:
With Samsung Phones, There is a utility called ODIN that takes out all the hassles of ADB push to the correct partition. There are plenty of Video tutorial on usage of Odin. Here's the main thread.
Click to expand...
Click to collapse
It didn't work. One thing I've noticed is that the CWM logo (Samsung logo with the CM alien) pops up before TWRP which makes me thing CWM has something to do with it.
This is the Odin process when I tried to Odin the recovery:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I also used this file to install the recovery:
openrecovery-twrp-2.6.3.1-d2tmo.tar
I took a screenshot of the partitions using diskinfo. Do you see anything wrong with any of the partitions?
That Alien indicates a successful flash of TWRP Recovery. With the latest versions of TWRP, they are including the CM Guy with Glasses logo. See if you can boot into recovery.
Perseus71 said:
That Alien indicates a successful flash of TWRP Recovery. With the latest versions of TWRP, they are including the CM Guy with Glasses logo. See if you can boot into recovery.
Click to expand...
Click to collapse
It still gives me these two errors before rebooting me back into Andriod:
E: TWFunc: : Copy_Log -- Can't open destination log
E: Unable to open '/cache/recovery/.version'.
Sounds like something wonky with Partition table. You may want to Odin back to stock. Make sure to use Android 4.1.2 version UVDMD5.
DO NOT FLASH UVUEMJC Stock firmware.
Perseus71 said:
Sounds like something wonky with Partition table. You may want to Odin back to stock. Make sure to use Android 4.1.2 version UVDMD5.
DO NOT FLASH UVUEMJC Stock firmware.
Click to expand...
Click to collapse
Are you sure it's safe to Odin back to stock despite the fact I can't enter recovery mode? My plan was to Odin stock but sometimes in order to boot into android, you must go into recovery mode and do a factory reset. It's the reason why I ask if it's safe to Odin back to stock (root or no root?).
By the way, thank you again for taking your time out to help me
Your fears are valid. Here's 2 things you need to know.
1. When you use ODIN to flash stock firmware, The .TAR files have both bootloader AND Stock recovery in addition to modem, kernel and rom. So it is going to overwrite anything and everything no matter what.
2. If you really feel strongly, you can do a Factory reset using Settings > Backup and Restore > factory reset in current state.
By the way, you are welcome, That's what we are here for.
Perseus71 said:
Your fears are valid. Here's 2 things you need to know.
1. When you use ODIN to flash stock firmware, The .TAR files have both bootloader AND Stock recovery in addition to modem, kernel and rom. So it is going to overwrite anything and everything no matter what.
2. If you really feel strongly, you can do a Factory reset using Settings > Backup and Restore > factory reset in current state.
By the way, you are welcome, That's what we are here for.
Click to expand...
Click to collapse
For some odd reason, when I press 'Erase Everything', it doesn't do anything. Maybe it's because I'm using a 4.4.2 nightly from Gummy. Is there another way to factory reset besides entering Recovery and Factory Reset from phone?
There does not seem to be any reliable method. There is one method involving ADB. But that too boots the phone into recovery.
Another thing. If you flash stock via odin, Don't just boot afterwards. Instead boot directly into stock recovery using the 3 button combo. (Vol UP + Home + Power)
Perseus71 said:
There does not seem to be any reliable method. There is one method involving ADB. But that too boots the phone into recovery.
Another thing. If you flash stock via odin, Don't just boot afterwards. Instead boot directly into stock recovery using the 3 button combo. (Vol UP + Home + Power)
Click to expand...
Click to collapse
In other words, I should uncheck A.Reboot (Auto Reboot) when I Odin back to Stock?
You got it.
Perseus71 said:
You got it.
Click to expand...
Click to collapse
Does it matter whether or not I use pre-root Stock firmware? Should I also use TriangleAway to reset the Binary Count?
Noobiologist said:
Does it matter whether or not I use pre-root Stock firmware? Should I also use TriangleAway to reset the Binary Count?
Click to expand...
Click to collapse
No it does not matter. Its personal preference really. Since you are likely to flash custom rom once all this is sorted, you can go either way. Triangle Away is necessary only when you intend to stick with stock firmware alone or intend to send in for Warranty exchange.
Another thing I remembered. When your stock flash is done and everything is fine, you will want to take a backup of your EFS partition AKA NV Data.
Install Terminal emulator from Play Store. Then in the Terminal enter following command.
su
reboot nvbackup
Click to expand...
Click to collapse
It helps if you happen to loose your IMEI in future at some point.
Perseus71 said:
No it does not matter. Its personal preference really. Since you are likely to flash custom rom once all this is sorted, you can go either way. Triangle Away is necessary only when you intend to stick with stock firmware alone or intend to send in for Warranty exchange.
Another thing I remembered. When your stock flash is done and everything is fine, you will want to take a backup of your EFS partition AKA NV Data.
Install Terminal emulator from Play Store. Then in the Terminal enter following command.
It helps if you happen to loose your IMEI in future at some point.
Click to expand...
Click to collapse
Thank you for the input! I believe I have a backup of my EFS partition in my SD Card (had it there since SGS3 was still running ICS) but I will do it again once I Odin the phone. What I'm really starting to believe is the PIT is probably messed up. What I need to confirm this is someone who has a SGS3 (T-Mobile 16GB) to download and run diskinfo from the Play Store and check the total size of the Cache Partition (mmcblk0p17) and/or download and run Terminal Emulator with these command prompts:
PHP:
su
cat /proc/partitions
This is what I got when I used the commands:
PHP:
[email protected]:/ $ su
[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 32 15558144 mmcblk1
179 33 15557120 mmcblk1p1
254 0 2110 dm-0
I could use this as a way to see if my PIT matches with a fully functional SGS3 (T-Mobile 16GB).
I actually do have that phone as my DD. Your MMCBLK0P17 values from partitions file do match mine. I didn't check others but I am sure they will match.
I use SlimKat for a Rom so my Diskinfo values will vary.
Perseus71 said:
I actually do have that phone as my DD. Your MMCBLK0P17 values from partitions file do match mine. I didn't check others but I am sure they will match.
I use SlimKat for a Rom so my Diskinfo values will vary.
Click to expand...
Click to collapse
That's a good thing! That means my PIT (theoretically) is fine. The reason why I asked for the diskinfo is to check the total space of the Cache Partition (Mine shows 826MB of total space). My ultimate theory is of course whether the firmware would actually do something about my Cache Partition (since it seems like the only reason my recovery isn't working is due to the fact it's not retrieving the information that's supposibly should be in the Cache Partition (E: TWFunc: : Copy_Log -- Can't open destination log and E: Unable to open '/cache/recovery/.version')).
It seems to me that the Cache Partition isn't writing the necessary files from the recovery image hence the fear of not being able to enter Stock Recovery to Format Data resulting in a boot-loop.
If you have a root file explorer, could you check the /Cache found in your root to see if you have any content there or something like a recovery folder in it?
Thanks
I need the official tmob noteII jb 4.3.1 kernel in tar or zip can anyone give me a link please
or latest official kernel
(Assuming you're running under Windows.)
Download the complete stock ROM from sammobile or the like. You could also get the boot.img from a repacked zip here, but YMMV.
Extract boot.img from the .tar.md5 file with a compression utility that handles tar archives, 7-Zip works well for this. (The error message about the end of the file is normal, that's because the MD5 hash isn't part of a normal tar archive.)
Get cygwin, namely its tar.exe command. With boot.img in your Cygwin home directory, from the Cygwin shell run:
tar -H ustar -cf youroutputfilename.tar boot.img
As an aside, my Windows-based setup to make Odin-flashable images is fancier than that. I've added the Cygwin binaries to my PATH environment variable (jury is still out on whether that's a good idea overall, but it works for a number of tricks) and I've created a script named tarodin.cmd in that directory which contains the following command:
tar -H ustar -cf %1 sboot.bin tz.img md5.img efs.img m9kefs1.bin m9kefs2.bin m9kefs3.bin param.bin boot.img recovery.img system.img modem.bin tombstones.img cache.img hidden.img userdata.img
The missing files just cause an error to show but the file itself works perfectly. I haven't bothered adding the MD5 hash, but it could be done.
The other way is to take a working t0lte kernel zip and substitute the boot.img in it then flash through recovery.
Good luck,
Darkshado
Got Kernel working
Darkshado said:
(Assuming you're running under Windows.)
Download the complete stock ROM from sammobile or the like. You could also get the boot.img from a repacked zip here, but YMMV.
Extract boot.img from the .tar.md5 file with a compression utility that handles tar archives, 7-Zip works well for this. (The error message about the end of the file is normal, that's because the MD5 hash isn't part of a normal tar archive.)
Get cygwin, namely its tar.exe command. With boot.img in your Cygwin home directory, from the Cygwin shell run:
tar -H ustar -cf youroutputfilename.tar boot.img
As an aside, my Windows-based setup to make Odin-flashable images is fancier than that. I've added the Cygwin binaries to my PATH environment variable (jury is still out on whether that's a good idea overall, but it works for a number of tricks) and I've created a script named tarodin.cmd in that directory which contains the following command:
tar -H ustar -cf %1 sboot.bin tz.img md5.img efs.img m9kefs1.bin m9kefs2.bin m9kefs3.bin param.bin boot.img recovery.img system.img modem.bin tombstones.img cache.img hidden.img userdata.img
The missing files just cause an error to show but the file itself works perfectly. I haven't bothered adding the MD5 hash, but it could be done.
The other way is to take a working t0lte kernel zip and substitute the boot.img in it then flash through recovery.
Good luck,
Darkshado
Click to expand...
Click to collapse
Thanks bud used the Kernel and subbed it in zip that did the trick God Bless
My T-Mobile S4 was having WIFI / LTE connectivity issues on Rogers so having successfully flashed ROM's before I started going through different jfltetmo ROM's but at some point flashed the wrong ROM. The last working ROM on my phone was CyanogenMod cm-11-20140217-NIGHTLY-jfltetmo.zip coupled with openrecovery-twrp-2.8.1.0-jfltetmo.tar but now my phone can only enter download mode and that too only when connected to a USB cable. If I turn my phone ON or try to enter Recovery mode it goes into a vibrate loop (no logo displayed) - does this make my phone soft bricked? Here is the screen output for my phone when in Download mode:
ODIN MODE
PRODUCT NAME: SGH-M919
CUSTOM BINARY DOWNLOAD: Yes (80 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Things I have tried so far:
-followed AndroidRootz Unroot / Unbrick Galaxy S4 tutorial step by step
-connect using Kies 3 with Samsung USB drivers v1.5.45.0 but Kies won't detect my phone
-flashed M919 stock Kitkat 4.4.2 (M919UVUFNB4_M919TMBFNB4_TMB.zip) using ODIN v3.10, v3.09, v3.07, and v1.85 which fails with ODIN showing:
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and phone screen showing:
START [224, 1448]
SECURE CHECK FAIL: aboot
-flashed TWRP v2.8.1.0 ODIN tar which resulted in ODIN showing a PASS but there still was no Recovery Mode
-flashed TWRP v2.8.1.0 recovery img and CWM v6.0.4.3 recovery img to RECOVERY partition using Heimdall v1.4.0 which were both successful but there was still no Recovery Mode
I also extracted my device's PIT file using Heimdall (my-PIT.zip) then compared it with a stock PIT (JFLTE_USA_TMO_16G_PIT.zip) I had found somewhere online. It seems I have slightly corrupted my partition so I tried the following fixes:
-ODIN flash just the stock PIT (JFLTE_USA_TMO_16G.pit inside JFLTE_USA_TMO_16G_PIT.zip) which fails with ODIN showing:
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and phone screen showing:
START [224, 1448]
SECURE CHECK FAIL: PIT
Do I need to explicitly fix my PIT partition first?
-If yes, is there a way to use ODIN, Heimdall, or some other tool to fix my PIT?
-if no, am I missing some step or using wrong firmware/tools?
Is there anything else I can do to get my phone back up and running? I am guessing I just need to be able to get into Recovery and the rest should be straight forward.
Any help to fix this issue would be greatly appreciated, thanks in advance
You said the last working rom, but you failed to mention the last thing you flashed before the issue....And that was?.....
ShinySide said:
You said the last working rom, but you failed to mention the last thing you flashed before the issue....And that was?.....
Click to expand...
Click to collapse
I can't remember now which ROM caused the issues - it was either a Samsung S3 or S4 ROM.
shaqto said:
I can't remember now which ROM caused the issues - it was either a Samsung S3 or S4 ROM.
Click to expand...
Click to collapse
If you flashed an s3 rom or firmware, you're most likely screwed.
Best bet find a pit file for m919 that isn't your pit file.
ShinySide said:
If you flashed an s3 rom or firmware, you're most likely screwed.
Best bet find a pit file for m919 that isn't your pit file.
Click to expand...
Click to collapse
I did find and flash a S4 ROM which I attached in my original thread
shaqto said:
I did find and flash a S4 ROM which I attached in my original thread
Click to expand...
Click to collapse
Yeah just noticed it.
Quick look thru it, you fcuked your boot Partition. At least if not more stuff. Didn't really compare side by side. Just what stood out to me.
Here's what it should be.
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10146376
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
here's yours
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 146176
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
notice the Identifier on the correct one is 20. dev/block/mmcblk0p20 is the boot.img Partition for us. You flashed a boot.img to the tz Partition.
Your most likely only hope is jtag.
But there's one more thing.... we're obviously not getting the full story. This wasn't a s3 or s4 rom you flashed. Because your identifier 8 aka /dev/block/mmcblk0p8 isn't even the boot Partition for the s3. mmcblk0p8 on the s3 is the cache.img.ext4 Partition.
ShinySide said:
Yeah just noticed it.
Quick look thru it, you fcuked your boot Partition. At least if not more stuff. Didn't really compare side by side. Just what stood out to me.
Here's what it should be.
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 10146376
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
here's yours
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 146176
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
notice the Identifier on the correct one is 20. dev/block/mmcblk0p20 is the boot.img Partition for us. You flashed a boot.img to the tz Partition.
Your most likely only hope is jtag.
But there's one more thing.... we're obviously not getting the full story. This wasn't a s3 or s4 rom you flashed. Because your identifier 8 aka /dev/block/mmcblk0p8 isn't even the boot Partition for the s3. mmcblk0p8 on the s3 is the cache.img.ext4 Partition.
Click to expand...
Click to collapse
Correct, the BOOT partition is messed up now which is why I was trying to fix the PIT (or at least I thought I was) by flashing the stock PIT file in ODIN with re-partition checked.. Is "partition block size/offset" the memory address for the start of a given partition? I guess the better question is, is there any way to replace the partition mappings using a modified PIT or any other method? Also I was curious, what is the "Partition Block Count"?
What if we approach this problem a different way - rather than changing the partition mapping to have BOOT entry point to the correct BOOT partition location, can we not just update the incorrect BOOT partition location with the actual BOOT img? ie. flash boot.img onto the device using my existing PIT file via Heimdall
You are also correct the S3 PIT file also does not match my PIT file - actually I did a search on Google for PIT file and I don't think any device has a PIT file identical to the PIT structure currently on my phone. I know it's stupid of me not being able to remember which ROM caused my phone to be in this state but it's also because I downloaded several M919 ROM's and immediately deleted the bad ROM after thinking I will never need it again. Anyways thanks again for helping out.
I've scoured the internet for hours trying to figure what I'm doing wrong with no luck.
I've recently flashed my N910T with _mone's developer build of lineageos. But it's not doing well with the old modem that I was using when i was back on CM12. So I've attempted to flash the modem using heimdall. I've tried both the EPK2 and EPG2 modems. Both times, heimdall throws an error back at me that says this:
ERROR: Failed to confirm end of file transfer sequence!
I've tried a couple different heimdall git repos (Benjamin Dobell's and a couple forks) just in case someone had fixed a bug in heimdall.
But is there something I've got wrong? Any idea why this is happening. I'm at a total loss. Any help would be hugely appreciated. My
Code:
> sudo ~/gitClones/karabijavadHeimdall/Heimdall/heimdall/heimdall flash --MODEM modem.bin --APNHLOS NON-HLOS.bin
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file data received, read 'empty' packet...
PIT file data receive completed, send kRequestEndTransfer...
PIT file download successful.
Uploading MODEM
100%
MODEM upload successful
Uploading APNHLOS
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: APNHLOS upload failed!
Ending session...
ERROR: Failed to receive session end confirmation!
Releasing device interface...