For those familiar with it, what do you know about DREADIAG.nbh?
The image I have is locked to a CID. I have a US phone and the image's CID does not match. So, this diag image is either for UK phones or is internal to HTC to keep the general public from using it. I had to use a goldcard image to load the diag on my retail G1.
Every time the diag tries something with my radio it hangs and I have to press end to cancel that part of the test. The diag must use the radio firmware currently flashed to the device ad the diag image is only about 321k and the radio image is much larger (~8967k zipped).
I will try not to pollute this thread with details of the problem I'm having but I think it's due to an issue with some G1's and firmware < RC33, perhaps the radio. My phone hangs on boot (I'll add a link to my other thread).
Some other things I'm wondering about this image:
-Various use of RUU (Rom Update Utility) from HTC to manipulate the phone.
-Is there away to get a fastboot interface with it? That could lead to an alternate rooting method.
I will followup with a link to DREADIAG.nbh and the version # of what I have, and the service manual which contains some info about it. If you're going to experiment with it don't mess around with the tty interface you can connect to or you mar brick your phone (see http://forum.xda-developers.com/showthread.php?t=487945 ).
Thanks,
HDN
A search for the searvice manual:
http://www.google.com/search?hl=en&q=+HTC+Dream+SM+(A04).pdf&btnG=Search&meta=
My G1's problem:
http://forum.xda-developers.com/showthread.php?t=510327
However, I can no longer find a link to DREADIAG.nbh. If anyone has a link can you post it?
Thanks.
where did you get the download for the DREADIAG.nbh? there is a link in the how to root your phone thread that links you to the .nbh of RC29 and you just have to rename it to DREAIMG.nbh
usually there is no difference between the diag and the img, but out of curiousity how long did you let it "hang" before you canceled the process. cancelling a .nbh flash can be very dangerous ESPECIALLY if you have not already attained root
tubaking182 said:
where did you get the download for the DREADIAG.nbh? there is a link in the how to root your phone thread that links you to the .nbh of RC29 and you just have to rename it to DREAIMG.nbh
Click to expand...
Click to collapse
I know that. DREAIMG.nbh and DREADIAG.nbh are different things. You don't flash your phone with the contents of the diag image, it runs more like a live boot and has diagnostic utilities.
but out of curiousity how long did you let it "hang" before you canceled the process. cancelling a .nbh flash can be very dangerous ESPECIALLY if you have not already attained root
Click to expand...
Click to collapse
I didn't cancel anything. Read linked thread.
i think there is this image:
http://www.megaupload.com/?d=7NRX7H40
Related
Hi all, this is my first post. Must admid i`m new to win mobile, but after owning a nokia n96 i had to abandon nokia.
My phone is an htc touch hd, it is running orange custom firmware (well, win 6.1 with orange rubbish all over it), i`ve been trying to remove this and came accross the cooked roms and this is where i have got a problem. I have downloaded duttys 2.1 extreme and have been trying to install it. When it start it the phone and pc stay at 0% and after a few minutes i get an error code "[262] UPDATE ERROR, when i click view document it open word and i have this http://forum.xda-developers.com/showthread.php?t=435110 , I have went to this page and tried putting the 2 zip files in the 2.1 extreme folder and loading the update from them but am still having the same problem.
I just wondering is anybody knows what i can do to get this updated? Also is this the best rom available? i looked at the 2.2 but it seemed full of bugs.
Thanks in advance
...........bump
have you hardspl'd the device
What is a hardspl'd? is this the hard reset button? I haven`t anyway
cheers
hhmmmm
well your half way there anyway. but remember the warranty may be voided, orange never really check but if your the cautious type id not continue
READ THIS
What is HSPL
* Hard-SPL a.k.a. HSPL is required if you want to flash any ROM other than the one intended for your device by your device's carrier (which can be a mobile phone operator or HTC themselves). Thus to avoid getting the "ERROR [294] : Invalid Vender ID" message whilst falshing
* Why do you need Hard-SPL: the stock (shipped) SPL that comes with your device will only accept NBH files signed by HTC. (This signature is a standard RSA signature, with 2048-bit long strong encryption.) Without worrying about the technical details - this means that if you change even one byte in the NBH file, it will break the signature and it will not flash via the stock SPL. This is not a checksum, it is a much stronger protection, and you cannot bruteforce bytes to fit the signature.
now we know what HSPL is you need to read this wiki page HERE
more info and help HERE
then you can do on the flash remember you nee yto put the roms NBH file into the sale folder as the custom RUU
Cheers for this mate, Its a good job im off work tomorrow, Gonna give it a go now. I`ll let you know how i get on. Can you remommend any roms?
Thanks for your help
jayjay8585 said:
hhmmmm
well your half way there anyway. but remember the warranty may be voided, orange never really check but if your the cautious type id not continue
READ THIS
What is HSPL
* Hard-SPL a.k.a. HSPL is required if you want to flash any ROM other than the one intended for your device by your device's carrier (which can be a mobile phone operator or HTC themselves). Thus to avoid getting the "ERROR [294] : Invalid Vender ID" message whilst falshing
* Why do you need Hard-SPL: the stock (shipped) SPL that comes with your device will only accept NBH files signed by HTC. (This signature is a standard RSA signature, with 2048-bit long strong encryption.) Without worrying about the technical details - this means that if you change even one byte in the NBH file, it will break the signature and it will not flash via the stock SPL. This is not a checksum, it is a much stronger protection, and you cannot bruteforce bytes to fit the signature.
now we know what HSPL is you need to read this wiki page HERE
more info and help HERE
then you can do on the flash remember you nee yto put the roms NBH file into the sale folder as the custom RUU
Click to expand...
Click to collapse
Jayjay, your a star, thanks a million!!!! its hardspl`d now and its currently 15% through the installation. I went with this one Davideuck_V-2_HP_Topaz, don`t know if this is my best choice but at least its easily changed now! thanks
well im using duttys, but that just personal choice
ROMs are personal choice
you pick whats best for your knees so i hear lol
Good day.
first I will explain what I did...
I rooted my magic and flash the t-mobile myTouch 3G's rom without any problem. But what I want is to install Taiwan's rom. So I downloaded the RUU released by HTC taiwan and run it. The result of this action was failed during checkin the module ID. and it cause my phone stuck in RUU USB screen. I cannot enter neither fastboot nor adb. What i found out is I have a chance to recover my pone if i reflash the docomo's rom. So I need some help in looking the sappImg.zip or sappImg.nbh for Japan docomo ht-03A. Is there anyone who know where to get the file? Please help me...
Thank you.
is there a RUU for the image you need ? if yes , just run it and it should work, having a goldcard will bypass the ID peroblem to flash the Taiwan ROM. just put it in and restart then run RUU again.
When you run a ruu it will make a directory inside your temp (%temp%) and a zip file normally called rom.zip is there , rename it to sappimg.zip and you have got the file you want!
shwan_3 said:
is there a RUU for the image you need ? if yes , just run it and it should work, having a goldcard will bypass the ID peroblem to flash the Taiwan ROM. just put it in and restart then run RUU again.
When you run a ruu it will make a directory inside your temp (%temp%) and a zip file normally called rom.zip is there , rename it to sappimg.zip and you have got the file you want!
Click to expand...
Click to collapse
Shwan_3, Thank you fo the reply.
I am also looking for the RUU for Japan Docomo HT-03A. But unfortunately, as of now, nothing found.
I tried to create a gold card. But not success... can I used the old card of the other people? or it should come from my unit?
Thanks.
toks725 said:
Shwan_3, Thank you fo the reply.
I am also looking for the RUU for Japan Docomo HT-03A. But unfortunately, as of now, nothing found.
I tried to create a gold card. But not success... can I used the old card of the other people? or it should come from my unit?
Thanks.
Click to expand...
Click to collapse
you can use an old card.
read the entire thread http://forum.xda-developers.com/showthread.php?p=4577777
I'm also looking for Docomo's sappimg.nbh or correct SPL for docomo ht-03a.
Does anyone can make nbh file????
Dude forget it. Just make a gold card - 10 minutes is all it takes and flash to official taiwan rom which is by far the best rom at the moment. Cooked roms don't come even close to its speed and stability.
SAPPHIRE EVT1 32B SHIP S-ON 0
HBOOT-1.53.02000 (SAPP40000)
CPLD-10
RADIO-3.22.26.04
I need the sappimg.nbh for this device as well, because now it's dead.. anyone has it??
This method is what I used to unlock my 1.6 Docomo HT-03A. Please don't hold me responsible for any issues you have. I typed this up really quickly as a reference for other NOOBS like myself so that you don't have to scour the board. I don't know where you got your unlock code from, but if you have one, you may follow these steps to get your device unlocked.
* - Note: If you are running Docomo's Donut ROM (1.6) then when you insert your non-Docomo sim, you will NOT BE PROMPTED to enter your NCK (network unlock PIN). These steps are necessary to get back to 1.5 so that you can get the unlock PIN entry prompt.
Before this process your FASTBOOT screen should look like this:
SAPPHIRE EVT1 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP20000)
CPLD-10
RADIO-2.22.19.261
May 27 2009,19:06:41
1. Install Android SDK. On windows it's just a folder. From the TOOLS folder, copy Adb.exe, AdbWinApi.dll, and fastboot.exe to C:\windows\system32\. Next rename the SDK folder to something convenient and place it at C:\XXX where XXX is por... where XXX is whatever your SDK folder is called.
2. Make sure ADB is installed correctly. Once you think it is, open a command prompt and type:
adb devices
You should get something under "List of devices attached". If not, your drivers are not correctly installed.
3. Using a Micro SD make a Goldcard. I used the video here.
3.5. Download and install any 32B rom your heart desires, and copy it to the root of your SD card (your goldcard); this will be used later.
4. Fix your Perfect SPL. The docomo SPL is HBOOT-1.33.0006 (SAPP20000). Go ahead and follow Amon_RA's steps here.
Use the Engineers SPL on that page (ROM v2.53.707.2 (Engineerings SPL v1.33.2010) - MD5 : F9674D19BE5F949D0D9DC99714D210E3).
5. Boot the phone normally, and if you have a non-Docomo sim to insert AND you have your unlock code, you may now enter it the the device will be unlocked forever, yay!
6. Turn off the device and check your FASTBOOT (BACK+END) screen; it should look like this:
SAPPHIRE EVT1 32B ENG S-OFF H
HBOOT-1.33.2005 (SAPP20000)
CPLD-10
RADIO-3.22.20.17
Apr 20 2009,15:30:43
Note that the device is rev EVT1 32B ENG S-OFF H: a 32B model with board rev. EVT1, ENG = engineering version SPL, S-OFF = security off (simlock off?), and H for HTC.
Note that Amon_Ra's G-type recovery images WILL NOT work at this point.
This H and the radio below are for 32A devices, which leads us to step 7.
7. Revert to 32B radio and G recovery. Steps found here under the section "Revert to 32B Radio and ROM". The radio can be found here.
Code:
fastboot flash radio radio.img
Press menu to POWER OFF. Then re-enter FASTBOOT (BACK+END) and check that the radio has been reverted.
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.2.0G.img
*** - Note that instead of recovery-RAv1.2.0G.img, you may use the newer recovery-RA-sapphire-v1.6.2G.img instead.
8. Press MENU to POWER OFF. Hold HOME+END to boot into recovery mode.
9. Install update from zip inside recovery mode.
10. Reboot or allow the device to reboot and enjoy your device.
edit: My FASTBOOT screen still has SAPPHIRE EVT1 32B ENG S-OFF H instead of SAPPHIRE EVT1 32B ENG S-OFF G. I wonder if I can just change my SPL back to the original Docomo ship one or if there is some ENG SPL S-OFF G available somewhere?
Credit goes to Amon_RA and all others who contributed in his work. This thread is just a quick guide for others in my situation.
I was able to get the device up and running smoothly after a little bit of a eureka moment from reading this post.
I've been trying to fix my SPL for a while now. I have a Docomo phone, same fastboot info as yours.
Every time I try to update with a sappimg.zip/nbh, i get a
Model ID Incorrect!
Update Fail!
message. This is both before -and- after I created a goldcard, no change whatsoever.
I've tried making the goldcard in winXP with HxD, in Ubuntu with 'dd', checked my CID about 4 times, and used 5-6 different sappimg's, both zip and nbh, including the one you listed in your instructions.
I've used a few different SD cards, including Kingston, SanDisk, and Toshiba, and all of them read just fine on my PC after the goldcard creation.
I've just about racked my brain for any solution. Every answer I've seen to my error message is "make a goldcard". Every answer for "my goldcard isn't working" is "make it again and make sure you can read it with your PC".
So, basically, I've got about 30 tabs open in 4 FireFox windows, lots of threads, all with the same info, most linking back to each other across 4 forums.
Really, all I'm asking is this: What could I have missed? It seems simple enough, honestly, but it's just not working. Any ideas?
Geobot said:
I've been trying to fix my SPL for a while now. I have a Docomo phone, same fastboot info as yours.
Every time I try to update with a sappimg.zip/nbh, i get a
Model ID Incorrect!
Update Fail!
message. This is both before -and- after I created a goldcard, no change whatsoever.
I've tried making the goldcard in winXP with HxD, in Ubuntu with 'dd', checked my CID about 4 times, and used 5-6 different sappimg's, both zip and nbh, including the one you listed in your instructions.
I've used a few different SD cards, including Kingston, SanDisk, and Toshiba, and all of them read just fine on my PC after the goldcard creation.
I've just about racked my brain for any solution. Every answer I've seen to my error message is "make a goldcard". Every answer for "my goldcard isn't working" is "make it again and make sure you can read it with your PC".
So, basically, I've got about 30 tabs open in 4 FireFox windows, lots of threads, all with the same info, most linking back to each other across 4 forums.
Really, all I'm asking is this: What could I have missed? It seems simple enough, honestly, but it's just not working. Any ideas?
Click to expand...
Click to collapse
Your either applying the goldcard.img to the logical drive rather then Physical...
Not formattng the card to FAt first...
You cant use the same CID for different sd cards
Rename the Sappimg to SAPPIMG.zip
Well, it seems I'm an idiot after all. Thank you crypysmoker, I had my list of CIDs going to the wrong cards. Updated just fine once I sorted that out. Thanks for the reply ^^
Geobot said:
Well, it seems I'm an idiot after all. Thank you crypysmoker, I had my list of CIDs going to the wrong cards. Updated just fine once I sorted that out. Thanks for the reply ^^
Click to expand...
Click to collapse
lol.. When I first rooted the Fender Mytouch i had your same problem because i had never made a gold card. i kept putting it on the logical drive.... then I kept using the same CID for 4 different cards. Then once i found out what I was doing, It was all back to the first card I used lol
Glad I could help
Hi,
I'm attempting to Interop Unlock my HTC HD7.
I've just run a restore in Zune, but it appears that the earliest restore gives me:
OS version: 7.10.7720.68
Firmware revision number: 2250.21.51002.728
Hardware revision number: 0002
Radio software version: 5.71.09.02a_22.51.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 5.10.2250.0(132968)
Chip SOC version: 2.2.5.0
I understand that if I have a Firmware revision number of 5xxxx, I cannot run the Interop Unlock as seen in this thread.
From what I see, it is possible for me to download a Stock ROM, in my case, this, and run that to downgrade my Firmware revision number.
I would just like to clarify before I start this process. Is the above information correct, and to run the Stock ROM, do I simply enter Bootloader Mode, start the .exe as downloaded from the thread, and let it run (seems too simple to me)?
Also, should I manage to get Interop Unlock working on a Firmware revision number of 4xxxx, would the Interop Unlock stick once I update the phone (is normal Zune update even possible after that)?
Thanks.
Be very careful. Since you have bootloader 5.xx
Pretty sure downgrading like that will brick your device. You have to use a y-cable. Last I heard, ive had my hd7 unlocked for a while not sure of newer ways.
Look for the downgrading spl thread in hd7 development. I think that's where it is.
After downgrade spl. I would just install hard-spl and flash a custom rom. Easier.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Thanks for the reply. Didn't know about the Bootloader thing, fortunately I didn't go ahead with it yet.
I was under the impression that if the ROM is the official ROM for my region (SEA, Singapore, 728), I wouldn't require any modifications to the SPL.
I don't want to mess with the SPL or the bootloader though, I've bricked enough devices (not WP7) to have a phobia of such things. Guess I'll have to wait for a breakthrough in unlocking, unless someone has any other methods.
If you want to be absolutely safe, GoldCard (which what @reeg420 meant when mentioning Y-cable) is the most reliable method.
However, I *think* you can actually downgrade to an older stock ROM just fine even with SPL 5.x. It just won't downgrade the SPL itself the way it normally would. You can't use RSPL on SPL 4.x or higher, which is why being able to downgrade the SPL is sometimes important (people who want to use custom ROMs need RSPL).
I suggest you do a bit more searching before deciding. I have not tried messing with SPL 5.x at all; I briefly had 4.x on my phone and promptly downgraded it to 3.1 again.
Thanks. I decided to go ahead with it, but got an error: "ERROR 226 (Flash Write - FLASH write error happened. Please check your PDA Phone)", which rebooted my phone. Phone appears to be okay though, not bricked.
Looks like I'll probably need to use a GoldCard?
Edit: So it appears that the earliest ROM that allows me to HSPL is this, which has the Bootloader 1.54.2250.0(112696). Could someone check my following steps and verify that I'm correct?
1. Get Y-Cable, USB Gender Changer, MicroSD+Card Reader
2. Get GoldCard Tool
3. Get GoldCard IMG, from this thread? "My custom goldcard.img"
4. Format MicroSD to FAT32
5. Place RUU_signed.nbh extracted from the aforementioned ROM with Bootloader 1.54.2250.0(112696), renamed to SCHUIMG.nbh
6. Run GoldCard Tool, ignore CID box, use GoldCard IMG, Patch MMC
7. Connect GoldCard, Y-Cable, phone, etc, etc, etc, patch phone
8. Get DFT's WP7FG3 from this thread
9. Install HSPL (or should I get RSPL? What is the difference?)
10. Find ROM of my choice (what do you recommend?)
11. Run selected ROM's ROMUpdateUtility.exe, flash device to new Custom ROM
Q1: What happens if the GoldCard process fails?
Q2: Is there any cons as to having an outdated Bootloader?
Q3: Am I able to upgrade my device with Official ROMs in the future after performing this, or must I simply use Custom ROMs from here?
Q4: Will having a Custom ROM affect my connectivity with my network?
ReignOfComputer said:
Thanks. I decided to go ahead with it, but got an error: "ERROR 226 (Flash Write - FLASH write error happened. Please check your PDA Phone)", which rebooted my phone. Phone appears to be okay though, not bricked.
Looks like I'll probably need to use a GoldCard?
Edit: So it appears that the earliest ROM that allows me to HSPL is this, which has the Bootloader 1.54.2250.0(112696). Could someone check my following steps and verify that I'm correct?
1. Get Y-Cable, USB Gender Changer, MicroSD+Card Reader
2. Get GoldCard Tool
3. Get GoldCard IMG, from this thread? "My custom goldcard.img"
4. Format MicroSD to FAT32
5. Place RUU_signed.nbh extracted from the aforementioned ROM with Bootloader 1.54.2250.0(112696), renamed to SCHUIMG.nbh
6. Run GoldCard Tool, ignore CID box, use GoldCard IMG, Patch MMC
7. Connect GoldCard, Y-Cable, phone, etc, etc, etc, patch phone
8. Get DFT's WP7FG3 from this thread
9. Install HSPL (or should I get RSPL? What is the difference?)
10. Find ROM of my choice (what do you recommend?)
11. Run selected ROM's ROMUpdateUtility.exe, flash device to new Custom ROM
Q1: What happens if the GoldCard process fails?
Q2: Is there any cons as to having an outdated Bootloader?
Q3: Am I able to upgrade my device with Official ROMs in the future after performing this, or must I simply use Custom ROMs from here?
Q4: Will having a Custom ROM affect my connectivity with my network?
Click to expand...
Click to collapse
Answer for Q1: it will definitely brick your device
Answer for Q2: no cons that may disturb you
Answer for Q3: yes, you're able to upgrade your device with official roms
Answer for Q4: no, as i use custom rom on my device, no connectivity problems
Wow, the GoldCard step looks incredibly daunting then. Guess I'll give this a shot. Will have to wait for the stuff to arrive from Amazon though, which will probably be a while given my location.
Thanks everyone for your input
with new windows phone recovery-tool 2.0.3+: http://go.microsoft.com/fwlink/?LinkID=525569
it downloads the RUU nbh and the UEFI nbh to the following path:
C:\ProgramData\HTC\Packages\Products\0P6B1400-T-MOB010
named like:
RUU_signed_2061.30.15001.531.nbh
UEFI_signed_2061.30.15001.531.nbh
i grabbed the download links with fiddler for people without the device:
Code:
https://softwarerepo.blob.core.windows.net/softwarerepo/80c33a50-3c4b-448b-9981-e5cd74d32236/UEFI_signed.nbh
https://softwarerepo.blob.core.windows.net/softwarerepo/80c33a50-3c4b-448b-9981-e5cd74d32236/RUU_signed.nbh
mainos partition is decrypted on-device during flashing (device model specific encryption).
the same also works for other variants of the htc one w8 like verizon and at&t.
would be cool if someone could post those rom url's too.
there is no tool to decrypt the mainos partition sadly but i hope someone skilled creates it.
Will it be possible to flash the T-mobile RUU on a Verizon phone? I need to get rid of the lock on the 4G channels on the verizon version.
in theory, modelid check on device will make it fail.
HD2Owner said:
in theory, modelid check on device will make it fail.
Click to expand...
Click to collapse
Any way to change model id with regestry hack? Maybe the same hack that allowed non-Lumia devices to install wp 10 technical preview?
that is not the same. it would have no effect in this case.
modelID is checked by bootloader before flashing. it aborts at 1% with error.
what you want is a signaturecheck/mid/cid unlocked bootloader. and you're not alone.
even if you reverse-engineer the bootloader and patch it, you need a way to get it on the device.
both things are incredibly difficult with wp8 nowadays because of the security measurements.
the previous work i did on wm/wp7 custom roms is not possible for wp8 until that happens.
The recovery tool does not work with the Verizon version of this phone (at least when i tested it the day the build came out). I had to use the leaked rom to flash back to Windows 8.1 on my Verizon Windows M8
I do have the Verizon .nbh's lying somewhere, will look for it when I get home