Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...
If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH
I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.
Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?
hey just got back the bootloader screen...
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?
Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....
Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.
Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.
Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?
What sort of error? Not found?
yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1
ran the program multiple times...still getting the COuntry ID error...
Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.
I was trying to flash the following ROM to my Magician, I did nothing and there was a sudden Reboot in my computer.
ftp://xda:[email protected]/Magician/Shipped_ROMS/CHT_11106_902_11100.zip
NOW, I don't have any backup .nb1 roms to flash back to my magician. I only have couple of .nbf files extracted from "CHT_11106_902_11100.zip
". AND I got a "cht10606_bigstorage.nb1" - "not sure if it's a complete rom.
The ROMUpgradeUt.exe was able to reach stage 3 of the flashing. If I start the magician now, I can see it stuck at the splash screen; that's it.
I WONDER if there is any extisting rom that I can ntrw.exe back and restore to the state I can apply ROMUpgradeUt.exe.
THANKS ALL
MARTIN :shock: :shock:
One more question
I first attempted to hack bigstorage by directly ntrw-write the cht10606_bigstorage.nb1 to my 1GB SD (I don't have small SD card).
But I can't get the "Serial V1.00" in the bootloader mode switch to "SD downloading", even I waited for more than hour an hour.
P.S. I can't verify if I successfully ntrw-write the .nb1 file, coz I see nothing inside my SD.
thanks everyone.
MARTIN
Not sure if big / Small discovery
I solved my own problem, after spending hours and hours on the bootloader screen with that "SD Download" Sections = 1 Not Allow Update screen :twisted:
I realized that Using a different bigstorage verison Rom from the original Version Rom to hack/flash into BigStorage CREATES the "Not Allow Update" screen.
It seems to be a limitation for flashing rom by bootloader, in which the flashing-rom has to be the same version the rom within the magician.
So, I THINK, it's not recommanded to flash ANY modified-bigstorage-rom to an existing rom, if u r sure about the verion difference. I think it's better to use Hex editor to do the hack.
Hope this post help many with the same problem.
MARTIN
When you're stuck in bootloader mode, MaUpgradeUt_noID.exe will help you. It's modified original which won't ask about language etc. and most importantly it can be run even in bootloader mode so you can flash it anyway.
I've tried installing the file using the bootloader method countless times now and every time I get a coloured screen with "Serial" at the bottom and some text up the top.
I've tried the card as it was when I got it, Tried it formatted FAT32 with windows, tried it formatted with Resco on the device, etc. It's definitely FAT32.
When I open any of the 3 .exe files from Palm in winzip or winrar there are two .nbh files (CHEEIMG.nbh and CHEEIMG_FW.nbh) one is ~263kb and one is ~85MB.
From everything I have read so far I ignore the correctly named small one (CHEEIMG.nbh) and copy the big one (CHEEIMG_FW.nbh) to the SD card - once thats done I rename it to CHEEIMG.nbh and I should be good to go - start the bootloader and it should work but it's just not happening.
Am I missing something? I just can't get it to work. I've tried the 3, vodafone and generic (ROW) files.
Any help would be greatly appreciated.
EDIT:
I'm currently running TREO750-1.15-ROW
Firmware: 1.27.3b.00
Cheers
As far as I understand all this you have to run Hard-SPL first, otherwise your device won't load "foreign" roms.
hmm ok I'll try that but since it's a ROW to ROW update I thought it's not a foreign ROM?
-MM- said:
As far as I understand all this you have to run Hard-SPL first, otherwise your device won't load "foreign" roms.
Click to expand...
Click to collapse
I think you can flash all official and leaked without Hard-SPL... It's needed for cooked roms.
surely I shouldn't need it for the bootloader method?
Anyone got any ideas that may help me upgrade?
Since the original link to this guide is buried in another thread, I've re-posted it here (and the guide in full) in order to help people that might've missed it. The latest version of the guide will always be available at http://www.karrderized.com/romguide/ however, and is a more printable version as well, so please check there too.
Installing the Hero ROM on your HTC Magic
Version 1.2 - 13 August 2009 - by KarrdeNZ
Disclaimer: I am not responsible if you brick your phone. This is only a guide. These instructions have worked for me, but there is no guarantee that they will for you as well. Follow this guide at your own risk.
Feel free to print off this guide if it makes things easier to follow. Please do not, however, steal this guide and claim it as your own. Updates to this guide will be posted here - http://www.karrderized.com/romguide/ - link, but don't steal. Thanks.
Things you'll need
Back up your settings
Installing the Android SDK
Determine your phone's version
Download the correct recovery ROM for your version
Download the correct Hero ROM for your version
Setting up the fastboot connection
Boot the recovery ROM
Back up your phone with Nandroid
Wipe your phone
Load your new ROM
Boot into your new ROM
Things to note
Acknowledgements
Changelog
1 . Things you'll need
A HTC Magic phone (obviously) running Cupcake (1.5) and with a SD card
A USB cable for your HTC Magic
A PC. These instructions assume you're running a Windows variant, though the same procedures can be performed on a Linux machine. Don't ask me about Macs. If you're running Windows, note whether you have a 32-bit or 64-bit OS, it becomes relevant later on.
The Android SDK - current release as of this writing is 1.5 Release 3, available here.
Recovery ROM - Which particular one you want to use will depend on your phone's version (I'll cover this later on).
A signed Hero ROM to install. Again, this is version dependent.
Got all that? Good.
2. Back up your settings
Now, before we start, back up. I'm of the opinion that you can never have too many backups. Take a copy of everything on your phone's SD card, make sure your contacts etc are synced, any apps you want that you can't easily get back from the Market are backed up, all that stuff.
Another thing you should note are the APN settings for your particular provider. These are in Settings, Wireless Controls, Mobile Networks, Access Point Names. You may have multiple APNs listed - go into each one and note down all the settings. You'll likely need to re-enter these manually once you've installed your new firmware.
Once you're satisfied you've got everything backed up, we can start setting up our environment.
3. Installing the Android SDK
Download the latest release of the Android SDK - here at the time of writing - for your relevant OS. I'll be using Windows from here on in. Extract the .ZIP file to somewhere convenient - I've got mine on my C: drive under C:\android-sdk-windows-1.5_r3. We need the SDK for the tools it provides in the tools subfolder, fastboot in particular, as well as the USB drivers for your phone.
4. Determine your phone's version
As of this writing, there are two distinct versions of the HTC Magic - PVT32A and PVT32B. The primary differences between these two versions is the amount of RAM (288MB on the 32A, 192MB on the 32B) and the radio (Qualcomm MSM7200a for the 32A, Qualcomm MSM7201a for the 32B). Generally, if your phone is HTC branded, it's a 32A, and if it's carrier branded (Google, Vodafone, etc) it's a 32B. Mine's a PVT32B from Vodafone NZ. But let's find out for sure what yours is.
Grab your phone and turn it off. Now, while holding the Back button down, power it back on. Your phone should now boot to a screen with a white background, some lines of text, and some skateboarding androids at the bottom. Welcome to fastboot.
The first few lines on the screen, in green, are what we're looking for. Mine reads as follows:
Code:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Yours will likely differ slightly. The number we're looking for is in that very first line - PVT 32B in my case. Make a note of this. The next item we're looking for is the second line, which indicates your SPL version. Some SPL versions do not allow ROM flashing, notably those of T-Mobile's myTouch3G variant of the HTC Magic. At this writing, HBOOT-1.33.0006 and HBOOT-1.33.0010 are the two known "perfect SPL" versions that do not allow flashing. If you have either of those versions, stop now. There is a complicated procedure you will need to follow first.
Otherwise, for now you can turn your phone back off (by pressing MENU).
5. Download the correct recovery ROM for your version
Head to this thread and download the recovery ROM for your particular phone version, as we determined in step 4. Save it in the tools subdirectory of the Android SDK (in my case, C:\android-sdk-windows-1.5_r3\tools).
6. Download the correct Hero ROM for your version
If you have a 32A, this thread should help you find a signed ROM (I'd suggest Fatality's Hero ROM): here
If you have a 32B like me, try Qteknology's Hero port here- the swap version is the fastest Hero ROM I've found so far. It does however require you to repartition your SD card in order to provide swap space to speed the ROM up - a guide for this is available from the linked forum post.
Note I have only tested the one I linked for the 32B as that's the version I have. Download whichever ROM you need to somewhere handy, and rename it to update.zip. Please note: if you have file extension display turned off (default in XP) then just rename the file to update instead - the .zip extension will already be set. Once you've done this, copy it to the root directory of your phone's SD card. You can do this using the standard USB connection system that the phone provides, or if you prefer using a card reader.
7. Setting up the fastboot connection
Start your phone in fastboot mode as we did in step 4 (hold down Back while turning the phone on). Once the fastboot screen is up on the phone, plug the phone into your computer with the USB cable.
At this stage, my computer asked for drivers for the phone - these are included with the Android SDK, in the usb_driver subdirectory. Users with 32-bit versions of Windows should use the drivers in the x86 subdirectory under that, and 64-bit versions should use those in the amd64 subdirectory. Once the drivers have installed, leave the phone attached to your PC - you're ready to proceed with booting the recovery ROM.
[Guide] Installing the Hero Rom on your HTC Magic - part 2
8. Boot the recovery ROM
We're going to use the Android SDK's fastboot utility in combination with fastboot mode on the phone to perform a one-off boot of the recovery ROM so that we can back up the existing setup, wipe the phone and then load the new ROM. At this stage, it would be wise to make sure you've synced contacts and backed up whatever you want to hold onto.
Open a command prompt window on your PC (Start, Run, cmd) and change to the tools subdirectory of where you installed the Android SDK, for example:
Code:
cd\android-sdk-windows-1.5_r3\tools
The prompt should change to indicate you're now in that directory. Now we make sure the phone is properly configured to communicate through fastboot. Type the following:
Code:
fastboot devices
If you see your device listed, we're about ready to go. Let's boot into the recovery ROM:
Code:
fastboot boot recovery-RAv1.2.0G.img
If the recovery ROM you downloaded is named differently, substitute it's name for recovery-RAv1.2.0G.img.
All going well, your phone should kick into the recovery ROM now - you'll come to a pretty green texted menu with the HTC logo in the background. This ROM is being loaded via the fastboot software and is NOT on your phone, just in it's memory. We have yet to make any modifications to your phone at all.
9. Back up your phone with Nandroid
Let's make one more backup to be safe. The recovery ROM we booted into provides us with Nandroid backup and restore, which we can use to backup the firmware and data currently on the phone to the SD card.
On your phone, use the trackball to scroll down to Nandroid v2.2 backup and click. This will start the backup process, and you'll see some yellow text start to appear at the bottom of the phone's screen. Once it's complete, you have a backup.
Use the trackball to select the Reboot system now option and click. It should load back into it's normal firmware. You can now mount the SD card as usual and copy the nandroid directory from the SD card to your computer. This is also a prime opportunity to back up your entire SD card.
10. Wipe your phone
WARNING: This is the absolute LAST point at which you can back out of this procedure. After this, it's all or nothing. Proceed at your own risk.
Boot your phone back into fastboot with USB attached (see step 4) and then load the recovery ROM again:
Code:
fastboot boot recovery-RAv1.2.0G.img
Use the trackball to move down to Wipe data/factory reset. This will erase all the data on your phone, ready for you to install the new ROM. Click. Congratulations, you have just wiped your phone! You are now ready to load your new ROM.
11. Load your new ROM
Still in the recovery ROM menu, scroll to Apply sdcard:update.zip. This process extracts the ROM from the update.zip file we placed on your SD card earlier and installs it onto your phone. It may take a little while so be patient. It'll tell you when it's done.
12. Boot into your new ROM
Select the Reboot system now option and click. Your phone will now restart with it's shiny new ROM! First boots can take a while, so bear with it. You'll probably see a new splash screen or two on startup, and eventually you'll get into your phone. You may or may not be prompted with a request about giving an app root access on your first boot - you can safely Always Allow this, as it's writing a swap file to your SD card in an effort to speed things up. You'll also need to go through the setup process on the phone again as if it were new, because for all intents and purposes it is. This includes setting up your Google account syncing, as well as the new Hero functionality such as your Facebook, Flickr and Twitter integration (if you so desire).
And from here on out, it's all up to you! Enjoy your new firmware, make it your own. There's some great new functionality in Hero over the standard Magic firmware.
13. Things to note
This firmware isn't perfect. I'm loving it and see myself using it from here on in, but there are some quirks. These may or may not be fixed with your particular versions of ROM, especially once this guide has aged a little, but I'll try and keep it up to date.
The main thing you'll likely notice (especially if you're using a 32B like me) is the slowness. There's a lot going on with this new ROM so lag is fairly common. The phone will speed up a bit once you've used it some more, so bear with it. Your initial setups and playing around will be slow because of initial caching and your non-typical use of the phone, but this should clear up. Various ROMs have tried for workarounds for this, for example Qteknology's Hero port uses a swap partition on your SD card to help speed things up. CompCache is also a popular method, but my own experience with CompCache hasn't been very successful.
There are also reports of SMS messages sometimes not arriving on the latest Qteknology ROM - I mostly didn't experience this until recently, but it seems to be an occasional issue. The ROM builders are working hard on the issues they come across so fingers crossed for resolution on this one.
14. Acknowledgements
This guide wouldn't exist without the xda-developers forum. The bits and pieces I gathered from thereabouts are what I used to run this procedure on my phone, and hence build this guide. The people there are much more experts at this than I am, so I defer to their wisdom.
I must also give props to Jesse of Radix's Gadget Blog. His instructions were incredibly helpful in getting my head around what exactly to do.
And also to papalazarou, whose forum thread prompted me to write this guide.
- KarrdeNZ
15. Changelog
Version 1.2 - 13 August 2009
Added Changelog
Updated links and references to ROMs to account for new versions
Changed ROM recommendations to Qtek for 32B based on personal experience
Removed references to now fixed bugs, added reference to SMS bug on Qtek's ROM
Added "perfect SPL" note
Version 1.1 - 29 July 2009
Added note about update.zip naming with regard to file extensions
Added SD card issue
Version 1.0
Initial release
First rate stuff mate, thanks very much. Now all I need is the new release of Jerp's ROM and I'll be embarking upon my first upgrade. Makes so much difference having everything you need in one coherent place. This post really should be stickied.
+1 for sticky.
Needs to be in one place, will cut down on 'how do i' and 'where can i find' threads
(note i said cut down, and not cut out lol)
This applies to all roms actually.
Great write-up! Thx for the effort, this will surely be handy in all other topics, where these questions are asked again and again (logically IMHO, as it isn't basic stuff for everyone).
Well done!
Now that is a quality tutorial cheers!
+1 sticky
I had posted these replies elsewhere before I realised you had posted the guide in it's own thread. I've run into a problem and it's really confusing me as to why it's not working
---------------------------------------------------------------------
KarrdeNZ, mate I followed your guide to the letter. I got all the way down to step 11 and then a problem occurred.
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
----------------------------------------------------------------------
Well I tried downloading the same file again. No luck this time either!
This is what it says when I click the install from sdcard button:
--install from sdcard...
Finding update package...
Opening update package...
E: Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Now I get that it's saying that it can't find the file but I really don't understand why? I mean the file is there, do I have to unzip the file onto my computer 1st and then put it on the sdcard?
I thought i just stuck the zipped file onto the root of the card making sure i renamed it 'update.zip'
Please help me out guys, thanks.
i did have the same issues, sorted it by:
Formatting the sd card (fat32)
Changing the permissions on the zip file
Moving files to the sdcard then sticking the sdcard into another computer to check that the files had been moved.
And it worked!
Roy_Drage said:
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
Click to expand...
Click to collapse
don't know if this is the exact same error, but i had a similar situation and it freaked me out, all you have to do (in my situation) is wait a few seconds or so. i think the phone is still in the process of mounting the SD card or initializing the card component. give it a few seconds (30 sec) and try the update again.
I formatted the card in the phone before I started, did u format yours in the actual computer itself?
Also how do I change the permissions on the zip file?
n1ck75 said:
i did have the same issues, sorted it by:
Formatting the sd card (fat32)
Changing the permissions on the zip file
Moving files to the sdcard then sticking the sdcard into another computer to check that the files had been moved.
And it worked!
Click to expand...
Click to collapse
this is 5 star
thanx works gr8
Excellent guide. All the other tutorials/guides/instructions totally went over my head. Yours was extremely clear and easy to understand. Two thumbs up!
Excellent
Thank you for an excellent guide.
KarrdeNZ said:
I must also give props to Jesse of Radix's Gadget Blog. His instructions were incredibly helpful in getting my head around what exactly to do.
- KarrdeNZ
Click to expand...
Click to collapse
Sweet.. I get a mention! Glad my guide helped you get started and now you're writing a guide too to help others - this is what a community is all about!!!!
KarradeNZ - you've made a great start to a guide here - but I really think this should all be in the XDA Wiki so everyone can contribute/update/maintain it. Then we just get one link stickied at the top and everyone goes there..
I just started to write up a skeleton of what I think should be in the 'Ultimate Guide to Sapphire Hacking' on the Wiki page at:
XDADeveloperWiki - HTC_Sapphire_Hacking
You want to help me improve it?
Heck.. if you want we can use your guide as a basis if you like - I just braindumped what _I_ think should be in it and I can immediately see stuff I've overlooked that's in your guide!
Feel free to take inspiration/snippets/whatever from my guide for it - just throw a link to it in there as well. I prefer to keep the guide itself separate but am happy to have it contributing to the wiki.
And there's only one A in my name.
When I apply sdcard:update.zip I get the following Error
E:cant open/sdcard/update.zip
(No such file or directory)
installation aborted
Please help and suggest what could be wrong ?
Just rename the file update mate.
Then try again.
Thanks Roy_Drage for the fast reply you sorted my .zip problem.
Also well done and thanks to KarrdeNZ for putting such a great guide together that even a noob like me could follow. My new Magic is now running Hero looks awesome !
bajax said:
Thanks Roy_Drage for the fast reply you sorted my .zip problem.
Also well done and thanks to KarrdeNZ for putting such a great guide together that even a noob like me could follow. My new Magic is now running Hero looks awesome !
Click to expand...
Click to collapse
BT works? (can you connect to a BT headset?)
Facebook integration works?
have you notice any issues?
Hello Friends.
My English is not very good but let me indicate the beginning'll try to explain.
I bought the device from last year's TR TURKCELL un rom convert was 6.5.
My job, I had to return 6.5 to 6.1 sees. I tried to go back a lot of things but I think the name of the error RUU_signed.nbh file with the name change CHEEIMG.nbh want to install after the following issue has occurred.
How do I do if I've stayed if the bootloader. Now red, green, blue and white colors on the screen there. When a screen comes up gray. when I press the camera, restart button does bootloder screen.
On Screen
Palm TR
IPL-0.20
Palm TR
SPL-0.24 0000
Writes...
USB and PC hardware in the device is visible. Can not connect to the bootloader in the Active SYNC.
I researched the Internet to the device I need to take the original rom. A lot like the original Treo750_Cingular_ROM called Treo750_2.23_ROW_WM6 ROM file I tried did not take. As enhancements on a PC via USB, but does not do installation DesktopUpdater. I tried with SD card, makes installation , BOOT Ok GSM gives OK, but gives FAİL Errors on OS install. At the end of the installation gives the error bar. I'm normal with FAT32 formatted SD was snow. SD card would install the original file 1.16RWE_CHEEIMG.nbh. camera, I would hold the restart button. to install the device, while 1% is automatically rebooted. I also want to install the self-RADIO reboot is 7%.
As far as I understand with; device when large files at 1% at small-sized files when closing at 7% has been reopened
devicereset, Hard-SPL, Treo750_OS5_2_19199WWE_STD, Original 1.16RWE.nbh, Treo750_2_23_ROW_DE_DesktopUpdater, completefixed, I tried almost everything, but the installation does not do..
I need this device too. I am electronics technician. Heard called JTAG recovery method.
Luckily the apology, that I am open for any ideas. but you'll help me. Tek Tek at a descriptive writer, you'll be happy. I trust you. As of this minute to thank every one, wish to express my respect and greetings
Based on your bootloader screen you have not successfully HardSPL'd your Treo. You need to do that first, and then flashing ROMs with the SD card is possible. You can't flash a ROM using the SD card without doing this.
You also can't downgrade a ROM using the regular installation packages because the install package will see the current ROM (if I understand you correctly, WM6.5) is a newer ROM than what you are trying to install. I think I remember seeing a post someplace where you can edit one of the files in the installer package to get it to work, but you would have to search to find it and even so, it's probably much more difficult to do than just doing the Hard SPL.