Hello everyone.
Last week I got access to an old supposedly dead touchpad lying at my friends office. Had to fiddle with it for almost a day and a half to get it running as it was totally out of charge.
Tried all possible combinations of VolUp, VolDown, Home but it just would not start initially, even after leaving it for charging for whole night using the original charger.
Anyhow once it booted, to my surprise it had Android 2.3.3 preinstalled. The initialy few sec boot screen showed HP logo with few cmd lines mentioning topaz etc etc.
The few details in the back are as below...
Prototype - NfS
FB35UA-EVT
CPU - APQ80680(64M)Rev.2
So anyone around have been able to take a complete back of the original rom and then upgrade to CM9/Cm10?
I tried following the common steps for upgrading from WebOS to CMx but none works for obvious reasons.
I am currently trying to get help on how to install mboot and tenderlionCWM, hence any pointer would be of great help. FYI the terminal does not give SU access either.
Update 1 - Out of desperation, I ran the JC tool tpdebrick, well didn't went good, I believe.... the outcome is that the device does not show any activity on screen and under windows device manager it either shows Android or QHSUSB_DLOAD!!!
Hi, never heard of the hp touchpad coming with factory pre installed android, and j's debrick is i think only for something that is lifeless..
Anyway what I would suggest is this thread http://forum.xda-developers.com/showthread.php?t=1426244 paying particular attention to the first post on page 12. And with luck you will have a working TP.
PM if you want /need further assistance.
followed the give guid to restore to factory, however no positive results.
I got stuck on the first step itself as the PC shows the device as an Android device., Hence Novacom is unable to find the device.
The touchpad device property is as below.
Bus 002 Device 030: ID 18d1:d00d Google Inc.
I had to install the google usb drivers with tweaked inf as mentioned else where in the forums. The only difference was that the device id is different than the ones posted here.
I went ahead and tried placing the command
adb devices
but that too shows no device connected, even though the PC device manager shows it connect with drivers.
pls suggest possible wayouts
Android 2.3.3?, is there any pictures we can see? Pretty please.
Have you tried installing a camera launcher to see if the drivers are there?
Sent from my Nexus 7 using xda app-developers app
Well I wish I did a rom backup before moving forward, however as I had updated in my OP, Im in a brick situation right now, with no signs of life.
For last two days I am running tpdebrick by JC to revive it, but alas no positive signs for now.
P.S. For once when it did switch on, yes the stock camera was running, but the images were way below normal.
There were a select few Touchpads that accidentally shipped with Froyo 2.2 which was likely being used to test the hardware before WebOS was completed for it. But I've never heard of one shipping with GB, any CM7 ROMs for this were based on 2.3.7 IIRC.
sstar said:
Hi, never heard of the hp touchpad coming with factory pre installed android, and j's debrick is i think only for something that is lifeless..
Anyway what I would suggest is this thread http://forum.xda-developers.com/showthread.php?t=1426244 paying particular attention to the first post on page 12. And with luck you will have a working TP.
PM if you want /need further assistance.
Click to expand...
Click to collapse
I used the link above on a TP I bricked, did not work. What revived it was the TPdebrick following procedure
http://rootzwiki.com/topic/38786-tpdebrick-v004/
your tp might be valuable to developers. i would contact them and see if theres some system files on it they could use.
a very few prototype models had android installed on them, but they were never meant for the public. however a select few did manage to get out into the wild. this one you have is quite rare.
edit: never mind, i see you've bricked it. could have had some potential useful files on there
I'm guessing TP Debrick won't work for you because you're in Google Inc. mode already. A little modding of the tpdebrick script to skip the first steps would probably solve this problem.
I will attempt if no one beats me to it.
bonkers! I never realised that it was this a rare device . I had been careless handling this and overconfident in putting custom roms etc.
Anyway I spent the day last in running the tpdebrick004 again and again with different ways. Prior to that our fiddling with webdoctor, novaterm etc all failed.
The results are as below... for the honorary members here!
Test bed - Ubuntu live 12.04 32bit, with android-adb and fastboot installed and TPdebrick004
Scenario 1
1. Under Home+VolDown+Power mode
2. lsusb shows...
Code:
05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
3. Running tpdebrick004 aborts with the following
Code:
tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
Writing 1024 bytes to 0x2a000800; 162948 bytes left.
Writing 1024 bytes to 0x2a000c00; 161924 bytes left.
.
.
.
.
Writing 1024 bytes to 0x2a027400; 4228 bytes left.
Writing 1024 bytes to 0x2a027800; 3204 bytes left.
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
Uploading file 'tz.mbn'...
Writing 1024 bytes to 0x18000000; 97896 bytes left.
Response: ACK 0x18000000 (outstanding: 0)
Writing 1024 bytes to 0x18000400; 96872 bytes left.
Response: ACK 0x18000400 (outstanding: 0)
Writing 1024 bytes to 0x18000800; 95848 bytes left.
Response: ACK 0x18000800 (outstanding: 0)
.
.
.
Response: ACK 0x06410e00 (outstanding: 0)
Writing 1024 bytes to 0x06411200; 552 bytes left.
Response: ACK 0x06411200 (outstanding: 0)
Writing 552 bytes to 0x06411600; 0 bytes left.
Response: ACK 0x06411600 (outstanding: 0)
Sending CloseFlush...
Writing file mbr32.bin ...
Sending MAGIC...
Sending secureMode...
Sending openMulti ...
Uploading file 'mbr32.bin'...
Writing 512 bytes to 0x00000000; 0 bytes left.
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
fastboot mode not found
Aborted.
Nothing happens thereafter.
Scenario 2
4. After reading few tips in the tpdebrick discussion in rootzwiki, after getting the fastboot mode not found message I manually reset the TP into Home+VolUp+Power mode
5. lsusb in sperate terminal window shows
Code:
Bus 002 Device 030: ID 18d1:d00d Google Inc.
6. running tpdebrick again continues further after fastboot message..
Code:
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
Loading TPToolbox-Headless ...
sending 'bootmem' (13200 KB)...
OKAY [ 0.827s]
writing 'bootmem'...
OKAY [ 2.924s]
finished. total time: 3.751s
Waiting for netchip mode... (may take 3+ mins)
Waiting for ping check... (may take 1-2 mins)
Checking/updating known_hosts...
Copying A6 files...
a6_firmware.txt.00 100% 48KB 48.3KB/s 00:00
PmA6Updater 100% 13KB 13.4KB/s 00:00
Copying bootloader files...
bootie-topaz305.bin 100% 113KB 112.8KB/s 00:00
emmc_appsboot.mbn 100% 45KB 44.7KB/s 00:00
Checking A6 firmware...
processing file: /tmp/a6_firmware.txt.00
A6 device: /dev/a6_0
2.13.10 (0x020d000a)
fw file size: 49461
fw file mapped at: 0x401a3000
Firmware verification complete
Updating A6 firmware...
Write failed: Broken pipe
A6 firmware update failed.
Aborted.
It takes hell lot of a time after the Updating A6 firmware message... almost half hour or more...
And that is where I am stuck right now... Hope this is of some help in figuring out the next steps...
your device has different partitioning and no webos installed. the tpdebrick and the methods for installing the CM7/9/10 won't work for you.
when you have started messing with tpdebrick, webos doctor you have probably bricked the device for good and every valuable part of software that has been shipped with this prototype rom you had is lost.
maybe, though webdoctor was not able to connect, however how one would know that the partitioning was different. do excuse my lame Q
Because it didn't have web os.
desihu said:
bonkers! I never realised that it was this a rare device . I had been careless handling this and overconfident in putting custom roms etc.
Anyway I spent the day last in running the tpdebrick004 again and again with different ways. Prior to that our fiddling with webdoctor, novaterm etc all failed.
The results are as below... for the honorary members here!
Test bed - Ubuntu live 12.04 32bit, with android-adb and fastboot installed and TPdebrick004
Scenario 1
1. Under Home+VolDown+Power mode
2. lsusb shows...
Code:
05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
3. Running tpdebrick004 aborts with the following
Code:
tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
Writing 1024 bytes to 0x2a000800; 162948 bytes left.
Writing 1024 bytes to 0x2a000c00; 161924 bytes left.
.
.
.
.
Writing 1024 bytes to 0x2a027400; 4228 bytes left.
Writing 1024 bytes to 0x2a027800; 3204 bytes left.
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
Uploading file 'tz.mbn'...
Writing 1024 bytes to 0x18000000; 97896 bytes left.
Response: ACK 0x18000000 (outstanding: 0)
Writing 1024 bytes to 0x18000400; 96872 bytes left.
Response: ACK 0x18000400 (outstanding: 0)
Writing 1024 bytes to 0x18000800; 95848 bytes left.
Response: ACK 0x18000800 (outstanding: 0)
.
.
.
Response: ACK 0x06410e00 (outstanding: 0)
Writing 1024 bytes to 0x06411200; 552 bytes left.
Response: ACK 0x06411200 (outstanding: 0)
Writing 552 bytes to 0x06411600; 0 bytes left.
Response: ACK 0x06411600 (outstanding: 0)
Sending CloseFlush...
Writing file mbr32.bin ...
Sending MAGIC...
Sending secureMode...
Sending openMulti ...
Uploading file 'mbr32.bin'...
Writing 512 bytes to 0x00000000; 0 bytes left.
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
fastboot mode not found
Aborted.
Nothing happens thereafter.
Scenario 2
4. After reading few tips in the tpdebrick discussion in rootzwiki, after getting the fastboot mode not found message I manually reset the TP into Home+VolUp+Power mode
5. lsusb in sperate terminal window shows
Code:
Bus 002 Device 030: ID 18d1:d00d Google Inc.
6. running tpdebrick again continues further after fastboot message..
Code:
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
Loading TPToolbox-Headless ...
sending 'bootmem' (13200 KB)...
OKAY [ 0.827s]
writing 'bootmem'...
OKAY [ 2.924s]
finished. total time: 3.751s
Waiting for netchip mode... (may take 3+ mins)
Waiting for ping check... (may take 1-2 mins)
Checking/updating known_hosts...
Copying A6 files...
a6_firmware.txt.00 100% 48KB 48.3KB/s 00:00
PmA6Updater 100% 13KB 13.4KB/s 00:00
Copying bootloader files...
bootie-topaz305.bin 100% 113KB 112.8KB/s 00:00
emmc_appsboot.mbn 100% 45KB 44.7KB/s 00:00
Checking A6 firmware...
processing file: /tmp/a6_firmware.txt.00
A6 device: /dev/a6_0
2.13.10 (0x020d000a)
fw file size: 49461
fw file mapped at: 0x401a3000
Firmware verification complete
Updating A6 firmware...
Write failed: Broken pipe
A6 firmware update failed.
Aborted.
It takes hell lot of a time after the Updating A6 firmware message... almost half hour or more...
And that is where I am stuck right now... Hope this is of some help in figuring out the next steps...
Click to expand...
Click to collapse
I'm having the exact same issue on a 32GB 3G version of the Touchpad.
It always fails at the A6 flashing...
Redferne said:
I'm having the exact same issue on a 32GB 3G version of the Touchpad.
It always fails at the A6 flashing...
Click to expand...
Click to collapse
If you guys want to get these fixed, PM jcsullins and ask him to join you on IRC.
There are andriod 2.2.1 /2.3.3/2.3.4 os version for Touchpads in 2011(Never released).Andriod Version can flash back to webos. But need PalmWinDfuUtil/NovaDeviceInstaller/webos Tar files..etc
If use Tpdebrick 004 run to All Done. Will see flower type on the screen (The means into Revoery mode). Must use Nova Device Installer to flash the device.(Can not use doctor). But it will lost Wifi address and need to rewrite it....
Cannot get past Fastboot using TPDEBRICK 004
I posted the problem on RootzWiki, but essentially my 32GB 3G TP does not get past Fastboot:
Sending CloseFlush...
Done writing files.
Resetting device...
Requesting Reset...
Waiting for fastboot mode...
fastboot mode not found
Aborted.
Fastboot will work to communicate with the TP, but I don't know enough to troubleshoot the debrick scripts on my own.
lsusb reveals:
Bus 002 Device 015: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Is there anything that can be done manually via command line using fastboot? I'm not a Linux newbie, but i'm not a developer either.
So, I started digging because i'm curious...
in the tpdebrick script found the following:
devid_fastboot="18d1:d00d"
also found this:
echo "Reseting device..."
perl qdload.pl --lreset
echo "Waiting for fastboot mode..."
if ! `check_usbdevs 60 ${devid_fastboot}`
then
echo "fastboot mode not found"
echo "Aborted."
exit 1
fi
echo "Loading TPToolbox-Headless ..."
fastboot flash bootmem TPToolbox-Headless-v004
if [ $? -ne 0 ];
then
echo "TPToolbox-Headless load failed"
echo "Aborted."
exit 1
fi
So I sort of understand the script, but again i'm not a developer...
When I manually execute the perl command, I get the following result (is this a problem?):
[email protected]:~/Downloads/tpdebrick-v004# perl qdload.pl --lreset
Requesting Reset...
Invalid Response: 03 00 06
If the Invalid Response is correct, then it appears to be failing to execute the fastboot with the check_usbdevs devid.
Is there anyway to check the usbdevs and/or devid, and that these are correct?
Hello,
My Touchpad don't boot. I try several combi buttons, Vol+ Power Home, Home, etc...
It's recognized as "Qualcom QHSUSB_DLOAD" when I plugg it to a PC.
I try TPdebrick script and get the staus "Aborted":
Code:
[email protected]:~/Téléchargements/tpdebrick-v004$ script
Script started, file is typescript
[email protected]:~/Téléchargements/tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
...
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
MSG: Open multi failed, unknown error
ERROR: Open multi failed, unknown error
Invalid openMulti response.
Cannot write file tz.mbn
Aborted.
[email protected]:~/Téléchargements/tpdebrick-v004$ exit
exit
Script done, file is typescript
I try to search "QHSUSB_DLOAD" on internet but without success.
How can I solve this ?
Thanks.
Not trying to be the one to give you the bad news but there is no guaranteed fix when TPDebrick returns the Open Multi error.
Sent from my TouchPad using XDA Premium 4 mobile app
Yes, I know.
Maybe, there is a solution somewhere...I search, read a lot but not find.
I'm not optimistic a fix will ever come, but you never know.
Sent from my TouchPad using XDA Premium 4 mobile app
Plenty of folks on the tpdebrick thread have this issue, and as of yet there is no fix...
HP TOUCHPAD DEBRICK Linux Live CD
I have created an Ubuntu Live CD with all the necessary files to Debrick the Tablet from TP Debrick v005 by jcsullins.
If there is any Tablet that did not finished the flash process, run this Live CD and perform the Debrick again.
If you do not know the Tablet model do the following:
Flash using the 16 GB, then connect to charger. If the home LED does not come on after some time then.
Flash using the 32 GB, then connect to charger. If no LED light then
Flash using the 64 GB.
All process must finish in " ALL DONE "
Click HERE for the HP TOUCHPAD DEBRICK LIVE CD
For information about charging a Tablet after been store for 9 years go here:
https://forums.webosnation.com/hp-touchpad/332615-hp-touchpad-won-t-turn-brand-new-never-opened.html
Please, help! I have a total zte axon brick on my hands... Windows recognizes it only like qualcomm HS-USB QDloader 9008. I've tried Qfil programm and msm9894download tool, but have no success.
Qfil output such as:
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I'll appreciate any help in my situation!
P.S. Sorry if my english is not right, it's not my native language.
P.S.S As far, as I undestend after reading a lot of guides, I need one of files - MPRG8994.hex or MPRG8994.mbn. Can anyone know where I can get them?
saardukar said:
Please, help! I have a total zte axon brick on my hands... Windows recognizes it only like qualcomm HS-USB QDloader 9008. I've tried Qfil programm and msm9894download tool, but have no success.
Qfil output such as:
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
NOP: Fail Code: 10
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I'll appreciate any help in my situation!
P.S. Sorry if my english is not right, it's not my native language.
P.S.S As far, as I undestend after reading a lot of guides, I need one of files - MPRG8994.hex or MPRG8994.mbn. Can anyone know where I can get them?
Click to expand...
Click to collapse
Have you tried to go into recovery mode and install any rom from there?
Crazyhat said:
Have you tried to go into recovery mode and install any rom from there?
Click to expand...
Click to collapse
Recovery is not available. Nether fastboot or adb.
Hello!
I'm writed other question, OTG not working: https://forum.xda-developers.com/t/usb-otg-not-working.4297787/
After downgrade HUAWEI P20 PRO CLT-L09 C432 with official HiSuite (with proxy to old 8.1 firmware), flashing end = error. After power off, only blank screen. No recovery, no eRecovery, no power on.
After pressed power, the CPU started heating and still hand warm. USB not powered (no 5V out). (After attached USB cable, PC detected in fastboot mode (with/without accu) "Android Sooner Single ADB Interface". Test pins shorted (below flasher led), no reaction.
Bootloader locked, Multi-Tool or Miracle Box flasher/unbricker "stock service flash" downloaded to phone and failed (download to phone ok, CRC ok, no write permission).
Waiting for Phone...
Phone Found..
Read Info Skipped..
Writing Data : Please Wait
Writing Data : Please Wait
Max Write Size : 471859200 bytes
Uploading : crc
Size : 88 KB
Verifying.. ok
Writing : crc
FAILED (remote: Command not allowed)
Done..
Writing Data : Please Wait
Writing Data : Please Wait
Max Write Size : 471859200 bytes
Uploading : verlist
Size : 0 KB
Verifying.. ok
Writing : verlist
FAILED (remote: Command not allowed)
Done..
Writing Data : Please Wait
Hisuite not support this phone recovery. No other method to unbrick, only SD-update.
The phone not powered OTG = SD-update not working!
Test with powered USB hub?
Cable tested other type phone, good. Cable tested other working P20 Pro (not available menu to "reverse charge" = phone not supported OTG).
How to reflash firmware?
Thanks!
Ps.: Chat the Huawei service: No home recover method. 5-10 day in a service time and if mainboard change too big money. (Now changed LCD and need new battery + service fee... --> phone go to trash.) ...or other home servicing???
I have tried to mod my Nokia Lumia 930. My bootloader was already unlocked for side loading. Now I wanted to mod Astoria on it so that I can also use Android apps. However, Windows Phone Internals kept telling me that my phone is already unlocked. When starting the Mass Storage Mode and Enabled Toor Access, the message of the missing FFU appeared.
After trying to reflash, I entered the red bootloop and could no longer access the phone. The recovery tool also failed here.
When using the Thor2 tool manually, the following message appeared:
Bash:
PS C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool> .\thor2.exe -mode uefiflash -ffufile "..\..\..\Users\myUser\Downloads\windowsphone-deploy\Repository\RM-1045\RM1045_02540.00019.15234.50006_RETAIL_prod_signed_1012_02699D_000-DE.ffu"
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
............
programming operation failed!
327681 Error: Unable to send or receive message.
Operation took about 8.00 seconds. Average transfer speed was 2.65 MB/s.
THOR2_ERROR_UNABLE_TO_SEND_OR_RECEIVE_MESSAGE_DURING_SFFU_PROGRAMMING
The phone went off and since then it is not responding. Also not on the power button or the combo power button + volume down.
Full Log:
Spoiler
Bash:
PS C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool> .\thor2.exe -mode uefiflash -ffufile "..\..\..\Users\MyUser\Downloads\windowsphone-deploy\Repository\RM-1045\RM1045_02540.00019.15234.50006_RETAIL_prod_signed_1012_02699D_000-DE.ffu"
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe -mode uefiflash -ffufile ..\..\..\Users\MyUser\Downloads\windowsphone-deploy\Repository\RM-1045\RM1045_02540.00019.15234.50006_RETAIL_prod_signed_1012_02699D_000-DE.ffu
Process started Thu Dec 29 21:58:12 2022
Logging to file C:\Users\MyUser\AppData\Local\Temp\thor2_win_20221229215812_ThreadId-51424.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 2.34 Implementation version 2.59
Size of one transfer is 2363392
MMOS RAM support: 1
Size of buffer is 2359296
Number of eMMC sectors: 61071360
Platform ID of device: Nokia.MSM8974.P6180.2.2
Async protocol version: 01
Security info:
Platform secure boot enabled
Secure FFU enabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0015
Subblock ID 32
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file ..\..\..\Users\MyUser\Downloads\windowsphone-deploy\Repository\RM-1045\RM1045_02540.00019.15234.50006_RETAIL_prod_signed_1012_02699D_000-DE.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 2.34 Implementation Version 2.59
Unknown sub block detected. Skip...
DevicePlatformInfo: Nokia.MSM8974.P6180.2.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 15
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU sync version 2 supported.
Secure FFU async version 2 supported.
CRC header v. 1
CRC align bytes. 4
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 61071360
CID: Samsung, Size 29820 MB
Start charging...
Start charging... DONE. Status = 0
ConnSpeedEcho: Elapsed= 0.212000, EchoSpeed= 31.84, Transferred= 7077918 bytes
Get security Status...
Security Status:
Platform secure boot is enabled.
Secure eFUSE is enabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get RKH of the device...
RKH of the device is 800EEB508F7BBDF12A19262621FD837297A3B062FE2A7078C0F3167E57F21217
Get ISSW Version...
ISSW Version: 216
Mon Aug 11 15:16:52 EEST 2014;ISSW v0216; main; OS; DNE; KCI 1296; ASIC 8974;
Get system memory size...
Size of system mem: 2097152 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
Clearing the backup GPT...SKIPPED!
Successfully parsed FFU file. Header size: 0x000e0000, Payload size: 0x000000006f400000, Chunk size: 0x00020000, Header offset: 0x00000000, Payload offset: 0x00000000000e0000
RKH match between device and FFU file!
Option: Skip CRC32 check in use
Start sending header data...
Start sending payload data V2Sbl in async mode...
Percents: 0
Percents: 1
Exception during programming: 262160
Safe write descriptor index reached: false
Payload data transfer speed (16.88 MB/s) Elapsed time 1.33 sec
Payload data size 22.500305 MB
[IN] programSecureFfuFile. Closing ..\..\..\Users\MyUser\Downloads\windowsphone-deploy\Repository\RM-1045\RM1045_02540.00019.15234.50006_RETAIL_prod_signed_1012_02699D_000-DE.ffu
programming operation failed!
327681 Error: Unable to send or receive message.
Operation took about 8.00 seconds. Average transfer speed was 2.65 MB/s.
THOR2_ERROR_UNABLE_TO_SEND_OR_RECEIVE_MESSAGE_DURING_SFFU_PROGRAMMING
THOR2 1.8.2.18 exited with error code 262160 (0x40010)
This means your phone is hardbricked you should take it to the service center
Is der a solution without service center? Its out of support.
Huskynarr said:
Is der a solution without service center? Its out of support.
Click to expand...
Click to collapse
does jtag work?
Nope, doesnt work. Have send it now back to seller.