Develop Bugs

iPAQ 2750 bootloader can start but cannot connect via mtty or recover by HPRUU

While start up at bootloader mode, the display showing "USB is connected".
After press the calendar key, showing "USB"
1) start up mtty with \\.\WCEUSBSH001 only got a blank screen ...
2) Using the HPRUU.exe to recover, the program can successful grab some info from my PPC, but when I press "update" , the ppc shutdown immediately and that program told me update/is successful while the progress bar only stay at 0%. Nth happen. And I check the log, I got the "Client_FlashOS ERROR : Device Open Error".
***** Client_BL_MODE Start
wcemgr is killed : 0
wcescomm is killed : 0
INPUT RUU model_id : hp iPAQ hx2(1,4,CHT
Size of : 16
INPUT RUU language_id : CHT
* device open : device OK
Check the value: 0
BL_MODE Checking Success -4
* device open : device OK
Check the value: 0
BL_MODE Checking Success -3
BL_MODE Checking Success -2
* device open : device OK
Check the value: 0
BL_MODE Checking Success -1
* device open : device OK
Check the value: 0
BL_MODE Checking Success
CLIENT_API int Client_FlashOS Start
***** Thread_Client_FlashOS Start, hx2000_1.10.00_CHT.nbf, 2600
* device open : device opened already
Client_FlashOS ERROR : Device Open Error
***** Client_Shutdown Start
* device open : device opened already
***** Client_Shutdown End
Have anyone got this happen before, and my battery is getting less and less after many time or tries and failed ...

Try killing RAPI.
Also, MTTY needs full port access, so disable any Firewall Software, & McCafee products are notorious for causing issues as well.
Are you using an XP or Vista machine?
BTW, you will only get a blank screen. try hitting the enter key twice. Then you should get a prompt: cmd>
I suggest trying an "cmd>info 8" command first to see if there are bad blocks causing problems.

Hi Gsleon3,
what is mean by killing RAPI?
I am using Windows XP SP2.

pcfool said:
While start up at bootloader mode, the display showing "USB is connected".
After press the calendar key, showing "USB"
2) Using the HPRUU.exe to recover, the program can successful grab some info from my PPC, but when I press "update" , the ppc shutdown immediately and that program told me update/is successful while the progress bar only stay at 0%. Nth happen. And I check the log, I got the "Client_FlashOS ERROR : Device Open Error".
***** Client_BL_MODE Start
wcemgr is killed : 0
wcescomm is killed : 0
INPUT RUU model_id : hp iPAQ hx2(1,4,CHT
Size of : 16
INPUT RUU language_id : CHT
* device open : device OK
Check the value: 0
BL_MODE Checking Success -4
* device open : device OK
Check the value: 0
BL_MODE Checking Success -3
BL_MODE Checking Success -2
* device open : device OK
Check the value: 0
BL_MODE Checking Success -1
* device open : device OK
Check the value: 0
BL_MODE Checking Success
CLIENT_API int Client_FlashOS Start
***** Thread_Client_FlashOS Start, hx2000_1.10.00_CHT.nbf, 2600
* device open : device opened already
Client_FlashOS ERROR : Device Open Error
***** Client_Shutdown Start
* device open : device opened already
***** Client_Shutdown End
Have anyone got this happen before, and my battery is getting less and less after many time or tries and failed ...
Click to expand...
Click to collapse
Did you connect the AC adapter throughout ?? You MUST !!

Yes, I did.

Help me out!!!!!!

I have Htc Universal o2 exe
It was good whe i was using Windows mobile5
Before few days back i have installed new rom to it that is luca16thebig [Diamond Edition] to it but dont know that its only for G3 users mine is G4 after that it was stuck in splash screen then i went in bootloader mode nd try to reset radio by this method
STEP 1
- First disable ActiveSync (File>>> Connection Settings>>> Allow USB Connections. Untick this box)
- Put your Universal into Bootloader mode (Hold down the Power button & Backlight button while performing a soft reset).
- Connect your Universal to your PC via the USB cable.
- Open mtty (I won't bother adding it as an attachment here, it's already been posted on the first page of this thread)
- Close all unessential software including antivirus and others, to ensure you have the maximum amount of RAM available to avoid problems.
- In the "Port" drop down menu select USB (If USB is not available you haven't connected properly. I couldn't get a connection at all when using Windows 7 X64, just stick with XP when flashing your device, there's much less hassle):
STEP 2
- After opening mtty type the following command. Type it directly into the window, do not copy and paste.
Code:
task 28 55aa
Then press ENTER.
If the following text appears then you've done it right:
Code:
Wait ..
DOCInfoTableinitHW +
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2C70000
All Size: 0x7770000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
USB>
If this is not the text you get, then start again from the beginning.
STEP 3
Providing that you've completed STEP 2 successfully, continue by typing the following commands into mtty one by one, making sure to hit enter after each one.
Code:
set 14 0
set 14 1
set 14 2
set 14 3
set 14 4
set 14 5
set 14 6
set 14 7
set 14 8
set 14 9
set 14 10
STEP 4
After you have enter all of the commands outlined in STEP 3, continue by entering the final command in mtty.
Code:
task 0
or
Code:
task 7
(I wasn't sure which one to choose, or even if a choice was implied, so I first entered task 7, then hard reset my Uni, put it into bootloader mode again, and repeated steps 1-4, this time entering task 0)
Your Uni's screen should have gone completely blank after that last command. If it has then:
- Close mtty.
- Unplug you Uni from the USB.
- Put it in bootloader mode again.
- Plug the USB cable back in.
STEP 5
Start mtty again and connect to your Uni via USB (as described in STEP 1).
Enter the command:
Code:
shmsg 11
It should report the following information:
Code:
USB> shmsg 11
String format is invalid!
Syntax error!
(The Syntax error! line didn't appear when I performed this procedure)
If you do not get this result, start again from the beginning.
STEP 6
Enter the following command:
Code:
rtask 0
mtty should report the following:
Code:
USB> rtask 0
Radio reset.
USB>
If this was the result you received then unplug your Uni from the USB cable, perform a hard reset (not in the original instructions, but that's what I did), then enter Bootloader mode again.
STEP 7
- Find and download a WM5.0 ROM, remove ms_.nbf and Radio_.nbf, so you're just left with nk.nbf (I used the KDSkamal_Ultimate_Ed ROM, which can be found through Google), and flash it to your device.
- Your Uni may get suck in Bootloader mode after flashing the WM5 ROM. Simply use the ExitBootloader tool.
- At this stage you're Universal should be functioning with a half decent WM5 ROM. Now you can proceed to flash another ROM of your choice in the usual manner. I would heartily suggest Tomal's WM6.5 ROM that can be found here on Xda-Developers, you won't be disappointed! :-D
but also i am unable to install new rom to plz help me out i am using windows 7 os ....
thanks in advance nd sorry for my bad english plz help me out....

And when i am using mitty utility for that i am getting this info for that
task 28 55aa
Wait..
DOCInfoTableinitHW+
Binary0 Size: 0x100000
FAT0 Size: 0x4000000
FAT1 Size: 0xA00000
FAT2 Size: 0x2900000
All Size: 0x7400000
FAT0_ADDR=0x100000,FAT1_ADDR=0x4100000,FAT2_ADDR=0x4B00000
USB>

Dude, i would PM luca and ask him....
As his Diamond ROM although looks good, seems to have lots of problems

What we have tried and where to go from here

Ok, so we haven't had quite as much luck yet as we would have liked, but I think as we continue to try out different approaches we will have some luck. I think it might be beneficial for us to have a an overview of what has been tried and what has been attempted thus far. So here is a list of things people have tried (please feel free to add anything that I may have left out or accidentally overlooked).
Registry Edit to access Zune storage
I believe this was the first approach that people took to gaining access to the KIN, and this link provides a great walkthrough.​
Bitpim
This is a pretty good overview of what has been attempted through Bitpim. Recently some have even tried using some other software, namely CDMA Workshop, (Look at the last post of the page.) I would suggest that we also try a couple more:
RevSkills
UniCDMA​
Nvidia Tegra Flash
I forgot this when I first posted.​
OpenZDK
This was another potential since much of the hardware, namely the processor is the same on both the kin and zune.​
Looking for clues in the log files
To put it simply in the hidden menu there is an option to have system log s emailed to you. I tried reading through some and noticed some of the events and files that the KIN uses, but have not had any luck yet.​
FTP
This link is the same as the link for the Log Files above.​
Export/Import in hidden Menu
Once again, the linked used here is the same one for Log Files and FTP.​
Please add anything that I may have left out, either different approaches or links to helpful information. I haven't had a chance to tinker with RevSkills too much yet, but it looks real promising.

Ah, we mods like these threads. Keep it up. Stickied.

The hidden import feature becomes active if you create a contact while using
qpst. It imports but I don't know where it put that info.
Interesting to note is that None of my phone entered contacts show up in qpst.
It is like that directory is mapped to some other place.
I was able to create directories and added txt files using qpst that remain even after power cycling the phone. I haven't found any of this using the phone yet.

I am getting the same results as you when I use the EFS manager and service programming. I can create files and make changes and they last after reboot.
I find it odd that when I export contacts from the hidden menu the file is visible in windows explorer if I have edited the registry as noted in the first post. I find this odd because everything else that is visible on the device using this method is related to the Zune, i.e. photos, music, and videos.

I have started looking back at some of the log files that I had the phone email me through the hidden menu and I have found some AT commands for the phone along with some other information. Here is a little bit of one file that I just started sorting through. The formatting isn't perfect because the log files have a lot of unreadable characters, but I have bolded files and commands. I also left everything in the case (upper and lower) as I found it in the file. The name of this file is:
MICROSOFT-PMX-DEBUGSTRINGPROVIDER-CHANNEL.02.clg
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_PRE_UPDATE
MPM_BB_USB_DRIVER_LOAD_UPDATE_EVENT, dwWaitTime: -1
MPM_Util:USB Client 1 has been Loaded
MPM_Util:USB Client 2 has been !UnLoaded!
CDMA Radio Updeate: Text stored version : v0.4.727
CDMA Radio Update:Registry Key version: v0.4.727
CDMA Radio Update: Current Modem version: v0.4.727
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_PRE_UPDATE
MPM_MainsSmThread
MPM_BB_UPDATE_REQ_EVENT - No modem update is needed
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_END_RSTISR_REQ_EVENT, dwWaitTime: -1
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_END_RSTISR_REQ_EVENT MODEM RESET ISR Init Completed.
MPM_MainsSmThread
MPM_BB_STATE_NORMAL_ON_POST_UPDATE
MPM_POWER_ON_REQ_EVENT, dwWaitTime: -1
RILNDIS: GetPacketInterface Initialize = c117d634
Shutdown = c117c4e4
RILDrv : i : Accumulated response (1) : <cr><lf>
IOPTMODE: 6 <cr><lf>
RILDrv : i : Sending cmd: ATV0E0X3 <cr>
RILDrv : t : LoadEriData : Opening file
\RoamingIndicator\eri.bin
RILDrv : i : Accumulated response (1) : ATV0E0X3 <cr> 0 <cr>
RILDrv : t : LoadEriData:
\RoamingIndicator\eri.bin not exist. Err 0x00000002
RILDrv : i : Sending cmd:
AT+cstt=0, 1, 75, 85, 95, 100 <cr>
RILDrv : t : LoadEriData: Opening file
\Windows\eri.bin
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv : i : Sending cmd :
AT+CSTT=1,1,18,22,26,30 <cr>
PMIC Boot cookie: rb7262h
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv : i : Sending cmd :
AT+CSQT=1<cr>
RILDrv : i : Accumulated response (1) : 0 <cr>
RILDrv:i: Sending cmd:
AT+GMI; +GMM; +GMR; +CKEYPAD?25<cr>
RILDrv:i: Accumulated response: +CKEYPAD:25
RILDrv:i: Accumulated response (2): equesting :
IUSBON, USBST, New PLMST, timestamp, 10, 2,2944 <cr><lf>
RILDrv:i:Accumulated response(1): +IQMIREADY <cr><lf>
+IUSBON<cr><lf>+IECHO: Requesting:IUSBON, USBST,
New PLMST, timestamp, 10, 2, 2944 <cr><lf>
RILDrv:i: ParseNotificationOEM: +IQMIREADY: SetEvent for QMI Init
RILDrv:i: Accumulated response(1): +IUSBON<cr><lf> +IECHO:
Requesting: IUSBON, USBST, New PLMST, timestamp, 10, 2, 2944<cr><lf>
RILDrv:i: Accumulated response(1): +IECHO:
Requesting: IUSBON, USBST, New PLMST, timestamp, 10, 2, 2944<cr><lf>
RilDrv:arseGetEquipmentInfo Modem Version: 727

I found out one more thing, if you use the s+l+power comination when the phone is powered off and connected to the computer another USB device is found. I just found this thanks to conflipper's early work We will have to come up with some sort of driver for this now.
Here is the name of the device and the hardware IDs
Microsoft Pink Bootstrap
USB\VID_045E&PID_2345&REV_0000
USB\VID_045E&PID_2345

I also just found this hardware id when having the computer turned off and plugged into the pc. When I hold down u+s+b+power Windows finds another device with the following name and hardware IDs (According to what I have found online this VID is Nvidia.) So this might be where we can use the tegra chipset stuff.
APX
USB\VID_0955&PID_7416&REV_0103
USB\VID_0955&PID_7416

Thought I would also add that my phone is currently unusable, but on the positive side, I wouldn't found those other two usb hardware IDs if this hadn't happened. Sidenote, I was using QPST Configuration program, and I right clicked on the my phone in the active phones tab. I then clicked on "Configure service to port mapping..." and added one property (unforturnately, I can no longer go back to the window because the program doesn't recognize my phone now). At this point, my phone rebooted and is now stuck trying to boot up.
I don't think it is completely bricked, but I fear that until we pull a rom it is probably useless because it is stuck in a constant cycle trying to reboot. The only way to stop this is to remove the battery. I have since tried using the various key combinations provided by conflipper and have found that the bootstrapper combination (s+l+power) would probably work if we had a rom. I then tried the hard reset combination (c+b+power) which initially looks like it might work but then it gets stuck in the cycle of rebooting.
I am going to continue working on it, hoping that somehow now that I might have some extra sort of access to hardware, but I am afraid my contributions may be limited until we are able to pull a rom.

Sorry to hear that. There has to be a way of getting it out of the loop.

RevSkills Hardware Log.
Diag Port Supported Command List.
7E - TRS FRM MSG supported.
5A - CHECK AKEY supported.
59 - EFS CMD supported.
58 - GET IS95B supported.
57 - SET MAX SUP CH supported.
56 - SUP WALSH CODES supported.
55 - FER INFO supported.
51 - GET FEATURES supported.
49 - READ PRL supported.
47 - UNKNOWN unknown response:
45 - GET CDMA RSSI unknown response:
44 - CHANGE SERIAL MODE unknown response:
43 - GET PARAMETER unknown response:
42 - UNKNOWN unknown response:
40 - SET PILOTS unknown response:
3F - GET STATE unknown response:
3E - UNKNOWN unknown response:
3D - CONF SLEEP unknown response:
3C - GET PACKET SEQNO unknown response:
22 - DISPLAY EMU supported.
04 - PEEK DWORD supported.
03 - PEEK WORD supported.
02 - PEEK BYTE supported.
01 - Show ESN supported.
00 - Version Info supported.
Click to expand...
Click to collapse
(the phone rebooted many times while doing this test, hence the unknown responses).
I tested more of the options provided by the free version of Revskills and it was kind of funny to see how the keyboard emulator worked, but only for numbers.
After all the reboots and so, i got some hex descriptions for errors in a new folder, called Err. Uploaded a new screenshot from that folder contents.
Easy CDMA just lets you browse the filesystem we already know.... not so much fun.
Little update.
You seem to be able to enter the recovery mode holding the U S B + power option but, as i tried right now, also using "Volume -" + power as stated for other tegra devices. Can't check if that loads ok on the computer, as i dont have the usb cable here right now.

OOPS I made a mistake. I am not seeing anything using windows 7 using u+S+B and power up. Should I disable zune, change registry for zune back to normal etc??

You shouldn't have to because the device has a different hardware id, so the drivers installed for the zune portion aren't applicable. Try turning your phone off, plugging in the usb cable and then using the key combinations. If the new hardware message box doesn't appear, you should still see an unkown device in device manager.
Also you have to hold the u+s+b+power for a few seconds before it will be recognized. When I have done this the screen stays blank on my phone and the only way I know it is working is through Windows.

Using Windows 7 OS. I had to uninstall the zune driver located in portable devices in the device manager then it found new APX device and i was able to point to the NVIDIA driver. Tried ruining the phone (Flashing android to it) as in another thread but it also got stuck on the flashing prompt. Restarted phone normally and the windows found another device and loaded the zune drivers back.
Incidently, holding the volume down and power on does the same as the U+S+B+Power and is easier on the fingers.
Thanks and keep up the great work.

I again may have spoken to soon. I cannot duplicate the above scenario anymore.
I also can no longer transfer pictures taken with my phone on to my pc. I can add pictures to the phone from pc and back but not the ones taken with the camera. Originally I could with zune software. The folders for uploaded pictures are different then the ones taken with the phone. I really think that I screwed something in the phone up by playing with qpst and others.

I'm not sure about what you did there, but in my testing & curiosity purposes trials, i wasnt able to alter the device (do a write to memory), so i doubt that qpst or the others did it for you.
Also, according to coinflipper notes, the kin has several layers, including the SBL that is the one operating with the os directly (the "Ms Pink bootstrap" device), not the recovery mode, which basically put us handling a modem....
I'm trying some things, but no results yet... gonna take some time....

I have changed the USB password and added contacts (somewhere) while writing to the device using qpst. I changed the password to 000001. Is this a different part of memory I am fooling with?
Thanks

I am not sure. I have no previous experience with any phone deving nor Qualcomm tools. Just pointed what coinflipper said.
I said "basically a modem", cause you got diag(nostics) mode within a com port, and some users (in other posts) showed logs with AT commands.
I'm working with some tools to connect to the device, but using the driver we all got (zune software). Not promising anything, just peeking around some tests.
@mcdietz
Here I pasted a public output of the linux command "lsusb -vv" (ultraverbose) where Kin (factory default settings) values are.
http://pastebin.com/rZscb9wz
Is useful for usb access to the kin. Use at will.

I have been testing usb connections to the kin devices (the ones we used in this forum) and i checked this:
Kin mode (normal Zune mode):
- Using MTP protocol:
-- You can browse files/folders/track related to Zune values using the lib-mtp tools in the system you like.
-- You can format the device (zune related folders) & delete zune files using the lib-mtp tools.
-- You can't download files from the device using the lib-mtp tools (kin doesn't allow you to)
-- You can't upload files to the device using the lib-mtp tools (kin doesn't allow you to)
- Using raw USB:
-- You can Write & Read values to the device (Kin VID 0x045e, PID 0x0641). Protocol allowed: MTP
Click to expand...
Click to collapse
Of course, Zune software does use this mode and is allowed to write to the filesystem. But that's because before doing so, it uses MTP protocol values to send and receive crypto values based on JANUS from Microsoft (Microsoft DRM for Mobile Devices) and after crypto relationships, the usb commands enable the "Connected" window at the Kin.
Capturing and replaying this values over usb does not work (ever) and does not work for the kin (had to try), so no go-go from here. Also, we cannot know if it would be able (dreaming after bypassing the DRM) to go outside the pictures/music/etc folders.
On the other hand, MTP tools reports that our little friend is able to reproduce the following files:
Firmware file
MediaCard
Abstract Playlist file
Abstract Album file
JPEG file
Microsoft Windows Media Video
MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
MPEG-4 Part 14 Container Format (Audio Emphasis)
Microsoft Advanced Systems Format
Microsoft Windows Media Audio
ISO MPEG-1 Audio Layer 3
Click to expand...
Click to collapse
Where firmware is strange and good but the question is... how to upload the firmwares files (you can get zune firmwares from the net) to the zune software on the device (and run them)?.
It's more interesting when you notice that firmwares contain "Zboot.bin" which is "Tegra device bootloader" but, sadly, doesnt work with nvflash because of what I said below. Those updates are WinCE updates too...
APX mode (nvidia "flashing" mode), with or without Nvidia driver.
- Using nvflash
-- You can't start flashing due to writing to usb error
-- Following attemps block the nvflash and device access.
- Using raw USB:
-- You can't Write or Read values to the device (APX VID 0x0955, PID 0x7416). Protocol allowed: None
Click to expand...
Click to collapse
This matches the post where coinflipper told us that you cannot dump the rom image.
Microsoft Pink Bootstrap (No driver):
- Using raw USB:
-- You can Write & Read values to the device (Kin VID 0x045e, PID 0x2345). Protocol allowed: Unknown
-- Phone answers "01" to all the write requests i did (from "00" to "FF").
Click to expand...
Click to collapse

markspace. com/kin/
Here's some software that was developed for it, but I'm guessing it is only client end?
I'm not allowed to link, so assemble the spaces yourself please

The link for the download (direct) , being for Mac(only) is:
http://www.markspace.com/kin/download.php
But you must register to get an activation code from the main page (posted by shlhu). It will need internet access to activate the software during installation and reboot after it.
Requires Itunes (for audio sync), Iphoto (for image, also have started it once), and Quicktime (for video).
I tested it with a fresh installed Snow Leopard and i can say that it works. I dunno how it does (without zune installed), but it works.
Unfortunately, i wasnt able to analyze the usb transmission there, so i cant compare with the windows one. If it can skip the JANUS drm, then we may have a chance. If it is the same process as windows... we are done... lol.

Nvidia Shield TV PRO 2015 brick to update 8.0 -> 8.0.1

Hello
I have a shield tv 2015 with nvidia experience 8.1 (android 9) - last October 2, I upgraded to 8.0.1, installed and when it was to restart, turned off and did not turn on.
Turns on the 2 sec green light and turns it off and the disc works (it seems to be in standby).
I opened a ticket (on nvidia) but it is being useless because the procedures that give me do not work.
I found that underneath is a snap-in cover. so i turned off the hard drive it always turns on the green light but i can't get into fastboot / recovery mode.
At the moment when I connect the usb cable to the pc I have an APX device. does anyone know anything about APX?
Thanks help me please i´m a nood

Your only bet is to get help from nvidia costumer support since it's not a pro version.
Apx mode = your device is bricked.

Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.

parfuar said:
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
Click to expand...
Click to collapse
You can try what has been done in this thread https://forum.xda-developers.com/shield-tv/general/bricked-shield-tv-pro-2015-version-t3841024
Or something like this https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195

Hi,
One question.
My original hard drive
Info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=ST500LM000-1EJ162, FwRev=SM16, SerialNo=W763XDYH
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Reserved: ATA/ATAPI-4,5,6,7
* signifies the current active mode
-------------------------------------------------------------------------------------------------------------------------------------
fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb22c3a15
my new hard drive
info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=HGST HTS545050A7E380, FwRev=GG2OACD0, SerialNo=TE85113R0Y5TPK
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: mode=0x01 (1) WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7
* signifies the current active mode
----------------------------------------------------------------------------------------------------------------------
--->> fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x4ca778fd
Hard drives are the same, I should with the tutorial, be able to get the shield to work without major problems.
what is wrong?
commands used:
dd if=start.bin of=/dev/sdX bs=4M
dd if=end_976574630.bin of=/dev/sdX seek=976574630
with these files:
https://forum.xda-developers.com/sho...2&postcount=23

My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far

First time it bricked was updating to 8.0, after recovery it was able to get the updates up to 8.0, when i did the 8.0.1 update i also got the same error as those above where turns on then off and does not even wake the display.

HellToupee_nz said:
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
Click to expand...
Click to collapse
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.

parfuar said:
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
Click to expand...
Click to collapse
In my case, I have the fastboot. but this is difficult because we don't have active developer mode.

Yes, i had done a factory reset also, u can get stuck at the spinning android logo forever without that i find. For the end part of the disk i used my own from my disks image, i've just done it all again and updated back to 7.2.3 stopped there and copied my widevine key off my orginal image so got L1 support and going to make backup of its current state.

parfuar You don't use "sdX" you change the "X" to the letter your drive is from fdisk -l , looks like you need to use "sda", after after you write the two bin files reboot directly into bootloader and select boot recovery kernel which will bring up t wrp recovery and you need to perform a factory reset wipe then reboot and Android should boot up and you will have Nvidia experience 3.3 and you have to do a couple updates to get up to 8.0 just make sure you turn off automatic updates cuz mine automatically updated to 8.0.1 and crashed my hard drive a second time. I used my original hard drive

also posting here that my 2015 500gb gets bricked with 8.0.1. hdd swapped out for crucial mx500. i think the guy here said it happened on his stock 500 sshd?

OK... This is how I got it to work.
Using "DD for Windows"... since I don't have a Linux PC (tested working perfectly on Windows 10 x64)
Download link:
http://www.chrysocome.net/downloads/dd-0.6beta3.zip
Unzip the "dd.exe" file and copy it to:
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps
This gives you the ability to use DD system wide.
Use the beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Connect your drive. I highly suggest using a Desktop PC because it is much faster than a USB to Sata cable.
If you don't have any open Sata slots, just disconnect your CD-rom drive temporarily and use the connectors.
Now:
1) Put the "start.bin" file in the root directory of drive C (example C:\start.bin)
2) Open a command prompt as Administrator and change directory to C: (command: cd C:\ )
3) Type command dd --list to determine the correct disk you want to write to.
4) Use command dd if=start.bin of=\\?\Device\HarddiskX\Partition0 --progress
whereas X is the drive number you determined earlier with the dd --list command
(replace the X with the drive number you want to write to)
5) Watch the write progress and stop the process at about 6GB (around byte 6,500,000,000)
(you can actually see the write counter running)
There is no need to write the "end file". Shut down the PC once finished and remove the drive.
6) Install the drive back into your Shield Pro and start. The green NVIDIA logo should show up soon.
Wait for about 10 minutes and if nothing happens unplug the Shield and do a restart.
Now wait patiently.... it will eventually boot past the green logo and the Android colors.
Now let your Shield self-update to whatever version you desire. It starts with version 3.0
That's it! You just successfully de-bricked your Shield Pro
Enjoy!

[Q] HTC Desire 816 single SIM EU version stuck in emergency download mode - how to fix?

I got a hard bricked HTC Desire 816 single SIM, EU version, Qualcomm MSM8928 Snapdragon 400 chipset
I know for sure it's a HTC single SIM phone, the rest I googled with the help of part numbers printed on various parts of the phone.
I can post the numbers if it helps to identify the phone
I guess it's an European model and not an import.
When I connect it to a PC I get a Qualcomm HS-USB QDLoader 9008 (Com4) port detected
I fully charged the battery on an external charger.
I have tried this guide: https://forum.xda-developers.com/t/guide-unbrick-htc-816w-a5_dug-from-hard-bricked-9008.3391110/ but the phone does nothing, when I press Vol- & Power button.
I see the phone in various SW like QFIL but I have no idea what firmware is the correct one.
I would like to read the whole phone content to identify which firmware I need - but how?
Or is there a other how identify the phone? Perhaps restore only the preloader, bootloader ... ?
Any advice how to proceed?
Thank you

Some progress ...
I need QPST or something similar, what is able to flash in emergency download mode - done
I need to download and extract probably suitable firmwares - done
I need a suitable programmer for the MSM8928 - probably done
But the firmwares are not in an usable format for the QPST Software Download.
How do I convert them to mbn or hex?

The firmwares are incomplete, it seems I need a complete mmcblk0 dump ...

It seems I'm out of luck.
I've tried different tools under Windows and Linux (to rule out Windows driver issues) but the result is the same.
I can download the prog_emmc_firehose_8928.mbn but that's it, the port stops responding after that.
I've also tried to boot two images (A5_DUG and A5_DWGL) from a SD Card and nothing, no sign of life.
I know need a A5_UL image but I thought the phone should show at least some sign of life but nothing :-(
The only sign of life is the port in EDL mode, when connected to a PC.
Is the phone dead or is there something else I could try?
I'm out of ideas ...

Some news.
I got some responses to SAHARA commands from the phone:
Attempting to switch device to mode: Command Mode
Device is awaiting client commands
Serial Number: AAA - BBB
Unknown ID 1: 0
Unknown ID 2: 0
MSM HW ID: 32993 - 000080E1
OEM Public Key Hash Hex:
========
Dumping Data For Command: 0x06 - Read Debug Data - 3904 Bytes
========
SBL SW Version: 0
========
Dumping Data For Command: 0x00 - NOP - 16 Bytes
========
Requesting mode switch from Command Mode (0x03) to Memory Debug (0x02)
Devices responded with an error: Invalid Command
Port Closed
Firehose programmer download:
/dev/ttyUSB1 USB VIDID=05c6:9008 Qualcomm CDMA Technologies MSM QHSUSB__BULK
Connected to /dev/ttyUSB1
Reading hello handshake
Device In Mode: Image Transfer Pending
Version: 2
Minimum Version: 1
Max Command Packet Size: 1024
Device requesting 80 bytes of image 0x0D - EHOSTDL
Sending image /prog_emmc_firehose_8928.mbn
Image /prog_emmc_firehose_8928.mbn successfully sent.
If there are no more images requested, you should send the done command.
Sending Done Command
Done Command Successfully Sent
No response from device
It seems that the prog_emmc_firehose_8928.mbn is not the correct one ...