Downgrading from 4.00.10 TMO to 3.17.xx - please help! - MDA, XDA, 1010 Software Upgrading

Hello all, first post here.
I upgraded my T-Mobile to 4.00.10 'internal test only' Tmobile rom.
I am getting a replacement phone from TMobile and I need to send this one back (Has a bad screen, warranty replacement).
Problem is, the one I am returning has the 4.00.10 ROM loaded... Do you think that the T-Mobile folks will care? I dont want to 'get in trouble'...
or charged for the replacement...
So, here is the question... Should I try to downgrade the ROM and the Radio Stack to its original before I return it?
How will I do that, I haven't seen anyone that has dont this yet, in a consistent way.
Also, is the Radio Stack upgrade included in the NK.NBF file in the RUUxx.exe from T-Mobile?
Thanks in advance for any help you can give!
J

You should definitely put the phone back into the "saleable" condition in which you purchased it. Get an extra sd card, a card reader, or the new xdatools posted here and flash the ROM back to the original Tmobile ROM you bought it with. If you didn't back up your ROM prior to flashing, which unfortunately is typical, you can download it here somewhere, flash it, and no one should be the wiser. By the way, why are you returning it?

I am returning the phone because the screen is messed up... It seem that the protective cover has separated from the 'screen', it is loose, so when you use your stylus, you have to really press down hard before it registers... also, it is extremely inaccurate when using the stylus even after numerous re-alignments.
Is there any way to reflash using SD Card if you dont have an SDCard reader? Can I copy the required files via ActiveSync to the SDCard while it is in the phone, then do a reset to bootloader to reflash via SDCArd?
If so, what files are needed on the sd card?
Another question along the same line... is there a special format for the files used to re-flash rom from the SD card (i.e. directory structure, file is a specific memory space, etc.) that is required when flashing using the BootLoader method?
I think that I can get an SD Card reader, but I am not sure yet...
Also, do you think that I can leave the Radio Stack at 6.24 instead of the orig 6.18?
Thanks, all.
J

Related

how to reprogram via the SD card?

Ok I tried looking through the forum, and read a bunch of stuff, but no one actually says HOW to do this.
I put on 4.00.16 and want to go back to the AT&T ROM, and I know you have to do it via the SD card. I've downloaded the XDAtools, but still have no idea how to do it.
I figured it out 10 minutes after posting my last message. hehe
Hi! I am tempted to also down load 4.00.16. Why are you going back to AT&T ROM? Did you find 4.00.16 had problems?
I had problems with the thing locking up sometimes while using 4.00.16
chocodough,
Thanks! I may decide to give it a try. But, before I do.... May I ask how you did the SD reprogram?

How to fix failure during upgrading ROM

I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.
Seif said:
I have a siemens sx56 with AT&T. I was trying to upgrade the ROM version to unlock it. Using XDA developer software and during this process, somehow the connection between the computer and the phone stopped (active Sync). Now the phone is not responding and the screen still displaying the upgrading process. I tried to reconnect but the Active sync does not recognize the devise. I read in this forum that you can solve this problem by using SD card with a good ROM version. Here is what I did. I copied the NK.nbf to the SD card using my computer SD read/write slot. I inserted the SD card in the phone and did the boot loader mode. What I got is "Wallaby boot loader v5.22 GSM OK" that set. Does the phone will automatically ask to press action to start flashing or I have to press a certain key. I tryed all the keys but they give me different tests that they work fine. So far I am not able to find the key that will install the the cooked rom. After that, when I tried to use the SD card in the computer, it did not recognize the card and ask me to format the SD card. I tried the fat and the fat 32 format and download NK.nb1 and/or NK.nbf and again I got the samething. Do I need to down load the ROM file using the XDAtool or just copying the file from the computer to sd directory will do it. I would really appreciate it if someone points out the best way of handling this problem (i.e. get the phone to work with the appropriate ROM and unlocking it) thanks.
Click to expand...
Click to collapse
Bro, you shouldn't change the Sd fat you erased what's written on it anyway your unit is still on the safe side and you can bring it to normal.
First of all downgrade your bootloader to 5.15 >>>
goto this http://forum.xda-developers.com/viewtopic.php?t=3274
Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards
rafia said:
Hi,
I also have exactly the same problem with my Siemens SX56 as those of Seif's. My Wallaby's boot loader version is 5.22. Ramram said that the first thing to do is to downgrage bootloader. But I couldn't understand how to downgrade the bootloader because I do not have a copy of old bootloader. Should I use 'OSImageTools' or 'XDArit' to write backed up CE image to SD card?
Seif, how did you solve your problem?
Best Regards
Click to expand...
Click to collapse
You need XDArit to write the rom to your SD read the past post on how to copy rom to your SD which is the safest way of installing the rom into the device, by using XDAtools press on FIX BROKEN BOOTLOADER this will downgrade you bootloader to 5.15 don't forget to connect your unit to the cradle when you want to downgrade.
I recommend 1rst of all to make a quick search in threads to be totaly ready for this
this would help :
http://forum.xda-developers.com/viewtopic.php?t=6581&highlight=downgrade+bootloader
http://forum.xda-developers.com/viewtopic.php?t=2068&highlight=downgrade+bootloader
Good Luck now.
Update : How to fix failure during upgrading ROM
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Good Luck and special thanks to Biso for his help.
Re: Update : How to fix failure during upgrading ROM
Seif said:
The problem was solved. Here is what I did. I copied the NK.nbf file to the SD card using the XDAtools. It seems that the XDAtools uses special format for the bootloader that well recognize the ROM file on the SD card. Rafia your bootloader (v5.22) is fine you do not need to downgrade it.
You should follow this procedure:
1. Install ActiveSync that comes with the device.
2. download XDAtools from this site and install it in your computer.
3. Cook the ROM ( or get it by extracting the zip file from the XDA developers special edition ROM.)
4. Use the XDAtools to copy the cooked NK.nbf file from your computer to the directory of the SD card
5. Insert the SD card in the dead device and go to the bootloader mode (soft reset while pressing power key). Make sure it has more than 80% battery before starting.
6. If it is still working and the bootloader ver. is older than 6.22, it will ask you to press action to start flasing.
7. Once finished, remove the SD card and hard reset, wait 60 sec and hard reset again.
Click to expand...
Click to collapse
Thanks a MILLION for this info. I'm in the same boat, with bootloader 5.22. One question though, when I'm in bootloader mode, which option do I choose from the menu to transfer the ROM to my device from the SD card? Will there be something automatically coming up? Or will I use one of the options listed below:
1. CE ROM TO SD
2. BOOT TO SD
3. CE + BOOT TO SD
4. GSM ROM TO SD
5. CE + GSM TO SD
By the way, so I never do anything to ruin my device again, can someone please explain what each option does?? I really don't have a clue.
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!
Linger1974 said:
Rudegar said:
as you can read from the menu you type in all these options are to the SD card
and they are to backup i suppose
rom upgrading should start automatic when a sd card with valid rom is in the sdport
and you are in the bootloader
maybe it ask you i forget but it's not something you have to find browsing
the menu's
Click to expand...
Click to collapse
Thanks for answering my question. Now I simply need to find a really good ROM to use to load back onto my device. What I would like to do is end up with Windows Mobile 2003, but the device is locked at the moment.
Can someone recommend a ROM for me to load onto the device so that I can then unlock it and THEN upgrade to 2003? Or is there a 2003 ROM out there that will also unlock? Originally, I ended up in this predicament by upgrading to the 2003 upgrade from Rogers AT&T, but that locked the device on me. I then tried to use a cooked 2003 ROM, and that's where I am now, without a useable device.
Thanks for all replies!
Click to expand...
Click to collapse
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck[/quote]
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?
Linger1974 said:
First of all get the "Special Edition Rom" to your device Unlock it then cook any other Rom you prefer
Special Edition Rom at http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
Good luck
Click to expand...
Click to collapse
Thanks, Ramram. I'm sure I'll have more success this time, but it's just odd that I went from a 2002 ROM, which was unlocked, to the Rogers 2003 ROM, and the phone was locked after that.
I guess I should stay away from that Rogers ROM then?[/quote]
Why to worry about the Rogers Rom you know now a way to unlock your phone.
I assume the Rogers rom is based like the At&t rom which it has the sound clipping bug , so I'd rather say that you could cook a T-mobile rom 4.01.16 WM2003 and try it it does not have the sound clipping bug..

Definitive instructions for ROM Backup/Update.

Sorry to ask this question which I know has been covered in so many other topics - but thats the problem - the topics are scattered and the answers are varied.
I have a Wizard derivative - an O2 XDA Mini S.
I have run the unlocking wizard and it is now unlocked.
I now want to
a. Backup the exisitng ROM
b. Backup the External ROM
c. Load an updated ROM.
I have tried the 'Unlock EXT ROM Wizard' - but still can't see the External ROM (in Total Commander for example) to back it up.
Can someone post a precise set of instructions for the step by step process for doing a. to c. above.
I am sure that others will find it useful as there still appears to be many posts from confused 'novices' to PPC (like me) who are trying various procedures on a hit and miss basis with varied success.
I just did the backup bit today.
Download aWizard 1.3b2
Run it, run the RAPI server using the 'e' command, wait till it starts, unlock the CID using 'u', then you can backup using the 'b' command, give it a name to backup to, and wait 15 or so minutes and it'll backup your GSM, OS, and Extended roms.
As for flashing, you can use the aWizard tool if you have the .nba rom files.
Or you can use one of the pre-packaged roms + flashers like the iMate one... but, that's where it gets a little perilous. AFAIK, the latest iMate rom will flash a locked Extended rom onto the device, which you can not edit any longer. So until someone figures out how to unlock the Extended rom, be careful.
My other idea would be to take the iMate full rom and break it up into the GSM, OS, and Extended roms. Once you do that, instead of using the pre-packaged flasher and rom, use aWizard to flash the GSM and OS roms and do the Extended part manually. Then you can keep an unlocked Extended rom (of your stock image) incase you ever want to revert to stock (since you backed up the stock GSM and OS roms in the first step).
Where is the aWizard 1.3b2. The unlocker I have is called lockiwizo2b and there is no u option.
Read the upgrading portion of the wizard forums, its all over the place there.
PS, be absolutely sure you want to upgrade, once you change, there is no going back, I did mine, I'd like to go back, but cannot.
jvanbrecht said:
Read the upgrading portion of the wizard forums, its all over the place there.
PS, be absolutely sure you want to upgrade, once you change, there is no going back, I did mine, I'd like to go back, but cannot.
Click to expand...
Click to collapse
Sure you can.
If you have an SD image you can go back to the T-Mobile original US load with no problem at all. You DID make an SD image of the ROM before you screwed around, right?
The SPL will not downgrade (you probably can do that by running the RUU for the "hacked-up" earlier Imate version with the 1.x SPL/IPL) but I've found no particular reason to.
I have verified that an SD image restore to the original T-Mo US firmware works from the Imate shipping RUU.
Genesis.
What is the best method for making the SD Image?
I would also like to know.
I would also like to know if the original Extended rom can be backed up after the iMate rom overwrites it.
pewe said:
Genesis.
What is the best method for making the SD Image?
Click to expand...
Click to collapse
You need:
1. A terminal program that can speak over the USB port. Terraterm has a patched version out which can do this.
2. A CID-unlocked device (it will NOT work if its not CID-unlocked!)
3. A SD card of 128MB or larger (buy a 128MB for just this purpose, as its a great backup device)
To use it:
1. Get into the tri-color screen (hold CAMERA, reset) and plug into the USB port.
2. Kill wcescomm.exe from Windows XP (this is the ActiveSync driver for the USB port)
3. Start your terminal porgram
4. Hit "return" to insure you have a command prompt.
5. Make sure your 128MB SD card is in the slot.
6. Type "r2sd all" and hit return.
The loader will dump the entire ROM (including extended ROM) to the SD card.
Note that this is NOT a file on a FAT filesystem - its a RAW data dump with a signature and checksum. As such you CANNOT read it onto your computer using a copy - you need a tool like "psdread" to read it from the card to a file on your PC.
If you use a NEW card, you can search for the end of valid data or do what I do and dump the entire 128MB (which is larger than the dump file for certain) and then just compress it - all the trailing zeros will compress to basically nothing.
Stick the card somewhere safe.
To RESTORE from the SD card, insert it with the power off in the Wizard, then power on while holding the CAMERA button. With the older ROMs the backlight will be OFF; with the new IMATE one it will be ON. It will tell you to press the VOICE key to load from the SD card. Do so, it verifies the integrity of the dump and loads it.
Note that the prompt only comes up for a few seconds and if you're using a 1.x release of firmware when you do this the backlight is OFF so its hard to see - but its there. Grab a flashlight if necessary.
Once you load something else on your unit from stock of course you can't go back unless you did this FIRST. This was the first thing I did when I got my MDA, so I have a copy of the T-Mobile "base software" on the SD card in case I pooch my device and need to go back to the OEM firmware.
Thanks Genesis. Very helpful guide.
I did another search on the forum using different search words and I found this post:
http://forum.xda-developers.com/viewtopic.php?t=37386&postdays=0&postorder=asc&start=0
and it looks like this is does the same thing - but without having to use other programmes like Terraterm.
Am I right?
Genesis3 said:
pewe said:
Genesis.
What is the best method for making the SD Image?
Click to expand...
Click to collapse
You need:
1. A terminal program that can speak over the USB port. Terraterm has a patched version out which can do this.
2. A CID-unlocked device (it will NOT work if its not CID-unlocked!)
3. A SD card of 128MB or larger (buy a 128MB for just this purpose, as its a great backup device)
To use it:
1. Get into the tri-color screen (hold CAMERA, reset) and plug into the USB port.
2. Kill wcescomm.exe from Windows XP (this is the ActiveSync driver for the USB port)
3. Start your terminal porgram
4. Hit "return" to insure you have a command prompt.
5. Make sure your 128MB SD card is in the slot.
6. Type "r2sd all" and hit return.
The loader will dump the entire ROM (including extended ROM) to the SD card.
Note that this is NOT a file on a FAT filesystem - its a RAW data dump with a signature and checksum. As such you CANNOT read it onto your computer using a copy - you need a tool like "psdread" to read it from the card to a file on your PC.
If you use a NEW card, you can search for the end of valid data or do what I do and dump the entire 128MB (which is larger than the dump file for certain) and then just compress it - all the trailing zeros will compress to basically nothing.
Stick the card somewhere safe.
To RESTORE from the SD card, insert it with the power off in the Wizard, then power on while holding the CAMERA button. With the older ROMs the backlight will be OFF; with the new IMATE one it will be ON. It will tell you to press the VOICE key to load from the SD card. Do so, it verifies the integrity of the dump and loads it.
Note that the prompt only comes up for a few seconds and if you're using a 1.x release of firmware when you do this the backlight is OFF so its hard to see - but its there. Grab a flashlight if necessary.
Once you load something else on your unit from stock of course you can't go back unless you did this FIRST. This was the first thing I did when I got my MDA, so I have a copy of the T-Mobile "base software" on the SD card in case I pooch my device and need to go back to the OEM firmware.
Click to expand...
Click to collapse
You, sir, are my new hero. You win 3 internets for this post.
Although, what would happen if I used my existing 512mb minisd card with apps already on it? Will it dump to a file and I can compress at that point? You mentioned it was non-readable on the card if I did that. I've already backed up the stock ROM using the aWizard tool, but if I used your method with a miniSD that had files already on it, would it blindly write to it, clobbering files, or write something to the card that was unreadable via a PC (basically not as a file on the filesystem), and if I put more stuff on the miniSD like apps or media, it'll overwrite the backup of the image?
If you do this to a card with data on it you will pooch all the data - it will scribble right on top of the FAT tables and destroy them.
Second, you won't know where the data you dumped ends. To be safe you should save 128MB of the card (from the front) to your file on the PC. This will result in a larger-than-necessary file, but that's ok.
You need tools like "psdread" and "psdwrite" to read and write the SD card in "raw" format - it is NOT a file that gets dumped, but just a RAW image of the ROM (with checksums)!
The only other "gotcha" is that depending on the EXACT configuration of the data you dump the SD card may refuse to reformat to its original capacity when you're doing doing this and/or refuse to reformat at all!
That's fixable by writing a block of zeros (e.g. 10kb or so worth) to the front of the card, which will clear what's confusing Windows (and the phone).
Genesis3 said:
If you do this to a card with data on it you will pooch all the data - it will scribble right on top of the FAT tables and destroy them.
Second, you won't know where the data you dumped ends. To be safe you should save 128MB of the card (from the front) to your file on the PC. This will result in a larger-than-necessary file, but that's ok.
You need tools like "psdread" and "psdwrite" to read and write the SD card in "raw" format - it is NOT a file that gets dumped, but just a RAW image of the ROM (with checksums)!
The only other "gotcha" is that depending on the EXACT configuration of the data you dump the SD card may refuse to reformat to its original capacity when you're doing doing this and/or refuse to reformat at all!
That's fixable by writing a block of zeros (e.g. 10kb or so worth) to the front of the card, which will clear what's confusing Windows (and the phone).
Click to expand...
Click to collapse
interesting. if I got a $10 128mb minisd, though, I wouldn't really care to use it in anything else other than this phone. I have a 512mb already for daily usage, so the 128mb would be for a backup incase I want to revert to the standard OOB rom from T-Mobile.
As long as the rom is written to the card and will read from if I choose to restore, I don't care if windows ever reads from the card again.
pewe said:
Thanks Genesis. Very helpful guide.
I did another search on the forum using different search words and I found this post:
http://forum.xda-developers.com/viewtopic.php?t=37386&postdays=0&postorder=asc&start=0
and it looks like this is does the same thing - but without having to use other programmes like Terraterm.
Am I right?
Click to expand...
Click to collapse
That's the tool I was talking about. This will dump the roms to a file on your PC that is readable. You can edit stuff, rewrite it back to the device, etc.
But what I haven't gotten a definitive answer on is whether you can flash the iMate extended rom and then overwrite it at a later date with the original t-mobile extended rom, since the iMate one is locked or something. Genesis' method involves using a miniSD to create a raw image of a newly booted phone, GSM/OS/Extended rom and all, which you can keep somewhere safe incase you ever want to revert. Apparently, even after flashing the iMate rom with the locked Extended rom, he was capable of re-flashing the device with the original rom from the miniSD.
This is exactly what I am looking for. I want to switch to the iMate rom, and know the order all the cabs in the extended rom need to be installed for it to work properly, but I was afraid I could never revert to the OOB experience. This fixes that, and I will be ordering a 128mb card tonight.
I downloaded Tera Term from http://hp.vector.co.jp/authors/VA002416/teraterm.html is this the right one? It only has COM ports as options to communicate.
Can someone please provide a link to a terminal program I can download which works over USB?
Hi,
I followed your instructions for making a backup of my ROM to an SD Card. I have a small problem, I don't have a card reader for my PC, is there any way to get the ROM image onto my PC via my Wizard? Also since the Wizard doesn't think the MiniSD card exists anymore, is there anyway to raw write those 0's to the card from the Wizard.. perhaps using terraterm? Or have I just killed my MiniSD card and I'm going to have to buy a reader for my PC ?
Thanks!
zan5hin said:
Can someone please provide a link to a terminal program I can download which works over USB?
Click to expand...
Click to collapse
download this one: http://arisme.free.fr/hacks/binaries/TeraTermPro_WinCE_USB.zip
its in the bin folder of the zip.
koniosis said:
Hi,
I followed your instructions for making a backup of my ROM to an SD Card. I have a small problem, I don't have a card reader for my PC, is there any way to get the ROM image onto my PC via my Wizard? Also since the Wizard doesn't think the MiniSD card exists anymore, is there anyway to raw write those 0's to the card from the Wizard.. perhaps using terraterm? Or have I just killed my MiniSD card and I'm going to have to buy a reader for my PC ?
Thanks!
Click to expand...
Click to collapse
You need a card reader in your PC (or a friend's PC) - I do not know of a way to write it directly in the MDA.
Genesis3 said:
You need a card reader in your PC (or a friend's PC) - I do not know of a way to write it directly in the MDA.
Click to expand...
Click to collapse
Ok thanks, I've got one from a friend now, so all good I was looking at http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloaderCommands to see if there were any bootloader commands for writing to sd card, but it appears you can only copy the ROM to the SD, besides, this is for a different phone anyway.
Ok I may have found something: http://wiki.xda-developers.com/index.php?pagename=XdaUtils/psdwrite.exe claims to be able to write raw to the SD card on a WinCE device... I'll investigate.
I'm currently reading the image raw from the MiniSD card using the command "psdread -1 0 0x0F140000 sd.img" using a 256MB MiniSD and it appears to be working, albit slowly. I'll keep you informed of whether I can succesfully recover my SD card using the writer after this read finishes.

wing usb broken, sd flash?

Hi guys,
My USB port will charge, but it doesn't seem to want to connect to a computer regardless of the cable or the OS/machine. The device manager won't even flinch. Not a huge deal, I sync to exchange over the air and I can bluetooth if necessary... but, I really want to upgrade my rom to the new tmobile 4.26 that came out recently. Has anyone had luck with the SD card flash? I formatted the card fat32 and put on the file as HERAIMG.nbh, but no luck, the bootloader just sits there whether I have the card in, or put it in in that screen. I see a quick "searching for SD card" before the bootloader goes, but nothing ever takes. Any ideas?
Thanks,
Ray
I had to rename the img to "heraimg.nbh" lower case for some reason. I am using a 1gb card formatted Fat32.
Also, your phone has to be HardSPL'ed. It SHOULD be all upper case, nailtoe's phone would be the exception. How big is your SD card?
It's 1GB. Am I out of luck without USB, or is there a non-usb hardspl technique? Now that I just asked that I'm going to search the forum to look, but ... meh. I think I'm gonna have to call t-mobile and get a replacement.
I need HardSPL even though I'm trying to go to a t-mobile rom?
if you're trying to flash back to the stock tmobile rom and you've extraced the .nbh from the RUU, you shouldnt need HardSPL to flash if you're not already HardSPL'd
ivanmmj said:
Also, your phone has to be HardSPL'ed. It SHOULD be all upper case, nailtoe's phone would be the exception. How big is your SD card?
Click to expand...
Click to collapse
I had no idea I was the exception. Not trying to counter your statement I know you are experienced enough to know what you are saying. But I tried and tried for days with capped and it refused to boot it. Ever since then I go lower case haven't tried it with caps since. Might have to try it proper next time I flash. Interesting how sometimes things do what they do though.

Help i cant remove hspl

Im sending my phone back to htc so I flashed back a standard rom. I thought this would remove hspl but it didnt now Im ****ting my pants. How do i get it off?
Did you flash stock rom via sd card? That is the only way that flashing a stock rom removes hspl. Otherwise the much simpler method is to rerun HSPL2 and select your original spl (ending in 0000) - assuming you can remember which spl you were on.
how do i flash the rom via sd?
elgrego4 said:
how do i flash the rom via sd?
Click to expand...
Click to collapse
Find nbh file of the rom you want, copy to root of sd card and rename it to LEOIMG.nbh, boot into bootloader and follow instructions. If it doesn't pick up the image, try reformatting sd card (preferably a small one ie 2gb) to FAT32 and retry.
Ive renamed the the file but bootloader does nothing, i only have a 16gb sd. I also put the whole rom on the card and selected it using file explorer and now the windows colour dots are just going around in a circle.
Did you copy just the .nbh file from the rom to your sd card and rename that and not the entire exe file? You also won't be able to flash via file explorer.
Seriously though if you can't flash via sd card (bigger sd cards don't alsways work - although my 16gb card does) just do the second and much easier option I gave you above, ie flash the rom via exe as you have done and then run HSPL2 and select your stock spl.
I cant do that cos now windows 7 wont install the bloody drivers lol. Im FUBAR'd
Be careful in your rom selection. This should ALWAYS be stressed when telling people how to do this. It's not simply a case of getting the one you want. You should always try to get the original rom your phone came with, or at a minimum one that the htc site recommends when you enter your country and phone serial. Flashing a bad rom via sd is pretty much the only way to brick your phone. This should not be forgotten or taken for granted.
That said, download the correct rom, rename to leoimg.nbh, stick it on the root of your sd card. Power off phone, insert sd card, hold volume down, press power.
(yeah I know clyde just typed the instructions, I just like them explained this way).
Sent from my HD2 NANDroid using XDA App
elgrego4 said:
Ive renamed the the file but bootloader does nothing, i only have a 16gb sd. I also put the whole rom on the card and selected it using file explorer and now the windows colour dots are just going around in a circle.
Click to expand...
Click to collapse
Have you double checked you card is Fat 32? I couldn't get a leoimg.nbh file recognised, until I found a similar post saying that it had to be Fat32. My card was in plain old fat...
MattOG said:
Be careful in your rom selection. This should ALWAYS be stressed when telling people how to do this. It's not simply a case of getting the one you want. You should always try to get the original rom your phone came with, or at a minimum one that the htc site recommends when you enter your country and phone serial. Flashing a bad rom via sd is pretty much the only way to brick your phone. This should not be forgotten or taken for granted.
That said, download the correct rom, rename to leoimg.nbh, stick it on the root of your sd card. Power off phone, insert sd card, hold volume down, press power.
(yeah I know clyde just typed the instructions, I just like them explained this way).
Sent from my HD2 NANDroid using XDA App
Click to expand...
Click to collapse
Good point m8, I assumed that as he had already flashed the rom via exe that he had the right one. (I know that's a dangerous assumption given the level of some of the users on this site as some shouldn't be authorised to use anything more technical than a tv remote - no offence elgrego4 ). Noted and I will include that important statement in future advice given
I've just seen from your signatrure elgrego4 that your rom is listed as LEO70 (ie WP7). Did you reformat your sd card after using WP7?
elgrego4 said:
Im sending my phone back to htc so I flashed back a standard rom. I thought this would remove hspl but it didnt now Im ****ting my pants. How do i get it off?
Click to expand...
Click to collapse
Turn the phone off..Then turn it on while holding volume down. This will take you to the bootloader menu( rainbow color). Plug the phone unto your PC then flash the original ROM that you downloaded from HTC site.No need to sync..Hope this will help.
Hey man if you want to remove HSPL you can just run the HSPL program from your pc with your phone connected in bootloader. It's the same procedure as installing HSPL, but now you must select SPL 2.08.000 instead of HSPL 2.08 while running the program.
I did it this way while I had to send my phone back and had no problems with it =)
You can check your SPL version in Bootloader.
yes it was fat 32, ive borrowed a 2gig so i will try that next
Its flashing with the 2gb card so fingers and everything else crossed
Keep us posted pls. I'm thinking also to bring back because of pixel error on the screen.
Sent from my HTC HD2 using XDA App
it says update success, do i just reboot it now?
rebooted, not bricked. Will check the bootloader in a minute
elgrego4 said:
it says update success, do i just reboot it now?
Click to expand...
Click to collapse
Yes........
SPL-3.03.000 is on now. Thanks for the help guy Knowing my luck htc wont find a fault
Pleasure m8, good luck.
Was 3.03 your original spl? If so I guess you do know it's a mission to get back to flash hspl once you get your phone back. You will first have to downgrade your rom to get to a lower version spl and then run hspl.

Categories

Resources