Back to the WM - Tilt, TyTN II, MDA Vario III Android Development

I have a question. If i turn i my kaiser Usb teatchering then in Windows have i device - Windows Mobile-based Internet Sharing Device, but is it yellow exclamation mark and is information in device properties is can't start device.
I can use mtty and flash my device?

The only way to flash is switching device to boot mode (4 colored screen) i'm sorry.

I can't use mtty to "brick" my PDA? Is it in "Radio from Hell"

arekmelerski said:
I can't use mtty to "brick" my PDA? Is it in "Radio from Hell"
Click to expand...
Click to collapse
Why would you want to brick your phone? ( a brick is a phone which does not function, and is said to be as useful as a brick).
And mtty has very limited uses on Kaiser hardware, the only way to flash is from bootloader, either SD method or USB method work fine this way, (usually).
Radio from hell refers to a specific radio version, which is no longer available for download, at least not on XDA-Devs.

I will not flash in my kaiser "Radio from hell". I will use method with mtty - she is in thread with "RFH"

Related

Request from a Linux user - Flashing without MS Windows

HI everybody
Like other people on this forum, i'm a linux user
I'm working under Ubuntu Hardy Heron. It's impossible to run any RUU under this system using WINE ( Software than give the possibility to run windows apps under linux ) because it need an active sync connection witch also don't work.
So my request is the following: Can we have a ROM Update utility for our cheer Penguin ?
Big thanks to all developers that works so hard for our community
you and me both: i'm on Linux Mint 5, though
i don't think it's a problem of the people on here: i say it's microsoft's refusing to release drivers for activesync...
There have been attempts made, but i don't know if any of them are going to work with these newer devices... Try googling SynCE...
Hello penguin's friend
SynCE is hard to configure...
But the question is not about synchro, but for ROM updating.
Okay Microsoft is radin... But for upgrading we only need an USB connection for data transfer through the hard SPL.
Activesync is only necessary to retrieve informations from the PDA during an update procedure ( Rom version for example ).
But the flashing procedure doesn't require it ! the prove: when we lunch this procedure the active sync connection stops and the SPL appears on the PDA's screen.
Here is my idea to make it possible under Linux : Run manually SPL on the PDA, and start flashing directly (with USB connection only).
In fact, we only need a ROM Update Utility that pass-through device information retrieving step ( is it really important? ). May be it can works.
All of this could run with wine. But I still think that a native linux RUU is the best way to explore.
There still exist a linux RUU update program (I don't remeber where, but if you make a search into this forum you can find it).
The matter is another one...our diamond don't use the common way to establish a connection with the laptoop ( /ttyUSB0) and so, till now, it's impossible to update...we have to find a workaround for this issues...
I don't understand...
It's the SPL that give necessary connection (usb/serial). Is the problem from it ?
Exactly
Take a look: http://forum.xda-developers.com/showthread.php?t=410302
By searching, i found a solution by flashing from a SD card with a special SPL.
Its solution was developed for ARTHEMIS PDA here : http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Do you think this SPL could work on our diamond ( we don't have SD Card but internal storage ).
I'm afraid to try it. My be it can crash my device permanently ...
GriFolle said:
Exactly
Take a look: http://forum.xda-developers.com/showthread.php?t=410302
Click to expand...
Click to collapse
GREAT ! i go take a look
Sers,
for Linux, HTC Flasher from the link in previous post is what you need.
It's working well for much HTC devices but Diamond still got some connection issues. It doesn't get attached to any serial port in SPL Mode, so flashing via Linux seems impossible.
Even flashing throught Virtualbox doesn't work because it's impossible to attach the device to the VM.
Maybe you're gonna find a solution, let's hope.
regards
demacus
dominique2222 said:
By searching, i found a solution by flashing from a SD card with a special SPL.
Its solution was developed for ARTHEMIS PDA here : http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Do you think this SPL could work on our diamond ( we don't have SD Card but internal storage ).
I'm afraid to try it. My be it can crash my device permanently ...
Click to expand...
Click to collapse
There you're wrong.
Take a look here: http://wiki.xda-developers.com/
In this thread a guy manage to flash Diamond via USB.
OK I have the solution !
It's very simple and don't need any computer!
BE CAREFUL BEFORE STARTING TO HAVE GOOD BATTERY !!!
Install Olinex hard SPL
Connect your PDA to linux in USB Disk mode
Simply copy your .nbh file into internal memory in root folder. rename it to DIAMIMG.NBH
Reset your device with pressing volume down and right key.
You will enter in Olinex SPL flash mode. Wait two seconds and it will ask you if you want to flash from DIAMIMG.nbh !!!
Thanks everybody for your help.
I think this solution is the more simple !
Congrats! Nice find!
This will make things much easyer for many ppl!
regards
demacus
it's much faster than trought async... always used this trick, the only thing to REALLY pay attention to have at least 40/50% of battery
All Right !
Is the file still there afterwards?
Nice find.
Possible to choose from more files?
dominique2222 said:
OK I have the solution !
It's very simple and don't need any computer!
BE CAREFUL BEFORE STARTING TO HAVE GOOD BATTERY !!!
Install Olinex hard SPL
Connect your PDA to linux in USB Disk mode
Simply copy your .nbh file into internal memory in root folder. rename it to DIAMIMG.NBH
Reset your device with pressing volume down and right key.
You will enter in Olinex SPL flash mode. Wait two seconds and it will ask you if you want to flash from DIAMIMG.nbh !!!
Thanks everybody for your help.
I think this solution is the more simple !
Click to expand...
Click to collapse
Thumbs up for you mate! super find, and saves us from messing with external USB hubs ....
Riel said:
Is the file still there afterwards?
Nice find.
Possible to choose from more files?
Click to expand...
Click to collapse
Well.....The file need that specific name.
You CAN transfer other files and name them, but you wont get a "menu" for choosing.
Just turn to your friend, and use his computer that runs Windows.
luzok said:
Just turn to your friend, and use his computer that runs Windows.
Click to expand...
Click to collapse
If prefer working under Linux Sorry Mr Bill !
Penguin 4 ever !!! YeaaaH !!!!

[GUIDE]How to Flash Your Vogue (CDMA Only!!!!)

Hi all!!
Ever since I got my Sprint Vogue, I have spent God only knows how many hours looking for and gathering information regarding this phone (flashing instructions, unlocking, SuperCID, etc). There are a few sites that have fairly comprehensive guides as to how to do this, but there are very few posts in the Vogue Section here at XDA-Developers.
Having said that, I figured I would create my own "How to Flash Your Vogue"-Thread. This is a multi-step process and I cannot emphasize the importance of following every step down to the "T", that is unless you are looking for a silicone-skinned brick...
Who is this guide for?
*Anyone with a CDMA version of the Touch. [highlight]That means no GSM[/highlight]
*Noobs and Seniors alike.
*People who have trouble flashing their devices.
*Anyone looking for links to more information.
*Curious people in general.
*Anyone willing to get rid of the nasty stock rom and looking for a newer and cleaner OS (notice that I never said more stable, so do not blame me afterwards ).
[highlight]Please keep in mind that there is always a chance of bricking your device with these procedures. I will not be in any way, shape, or form responsible if you damage your device while doing this.[/highlight]
Got your coffee? Alright, let's do this.
Step 1. Preparing the device
As with every phone, you have to make sure that you have the following things done before flashing:
* Battery charged at least 50%.
* All the necessary programs (see next post).
* Instructions handy.
Make sure that you back up all your information (contacts, e-mails, files).... essentially, anything that you would like to keep post-flashing. You can do this via Active Sync/Mobile Device Center or via third party software (PIM Backup is really good)...
You will have to reinstall every last piece of software in your device as it will be hard reset. Some programs may work if installed in a SD card directly, but a lot of them write things to the registry and copy files to the device, which they require to run. Long story short, keep all your cabs and exe files in a safe place so you can restore later if needed.
Step 2. Unlocking the Device (HardSPL)
Unlocking the device is done so that you can flash custom roms in your devices. The unlocker that you are about to download and use was provided by "ImCoKeMaN" at PPCGeeks. If you are interested in the full thread, please click here.
If you have read the above link, you will see two versions of the HardSPL (0.40 and 2.31). Simply use 2.31 as it works fine with most devices.
[highlight]To use this under Windows XP,[/highlight]
1. Connect your device to your computer and make sure it is synced with ActiveSync.
2. Download and extract the contents of the zip file, which is an exe. Let it run to completion. You will be prompted to disconnect and reconnect your device at one point in the process. Do it... don't worry
3. It will look like it is flashing a rom via a RUU. Do not disconnect the device after it is done!!!!!
4. Once it is done flashing, you will see a prompt that says that it will run exitbl. DO NOT DISCONNECT YOUR DEVICE. At this point, open ActiveSync, go to File>Connection Settings> Uncheck "Allow USB Connections". Continue following the on screen instructions and let it finish.
5. Go to bootloader once more to verify that it worked. You should see 2.31 CoKe MFG.
[highlight]To use this under Windows Vista/7 x64 (thanks jitajt),[/highlight]
jitajt said:
connect your device to WMDC (it's not necessary to set up device, just connect without setting up device)
then right click on the 2.31 unlocker and run as administrator
follow the directions, you will get an error about sleep.exe not being compatible with x64 but just hit ok and continue, (you will get about 10 of them)
then just keep following the directions in the command prompt and it will put your phone into bootloader then you have to disconnect and reconnect when it tells you to. and it will flash your phone and reset it. then your done you can close the command prompt and disconnect your phone.
I did it just like above and I have not had any problems.
Do this at your own risk as I am not responsible for your phone
Click to expand...
Click to collapse
Step 3. Flashing your Roms
The time has finally arrived. You sat down patiently through the unlocker and you are now ready to take the leap of faith into what you believe will bring your device to a new level of usefulness (also known as getting rid of that nasty, bloated, stock rom )
The process is relatively simple:
1. Download the RUU package from this post. I am only posting this because some cooks only post the rom nbh files rather than the whole package.
2. Go into the threads and look for whichever rom you prefer. Look at my signature to learn which one I am using. NFSFan (my current one) is by far the best one I have tried so far. You can download it from here
3. Put your device in bootloader mode and connect the device to the computer. [highlight]Once in bootloader, activesync will NOT see the device. If the RUU gives a connection error, try to run it with the devices in regular mode (with ActiveSync connected)[/highlight]
4. Open the Romupdateutility.exe and follow the steps.
5. Once it is done flashing the rom, disconnect it from the computer and hard reset it. To do this, simply hold "Send" + "End Call" +Stylus in the reset hole for about 3 seconds. It will prompt you to erase all the data and restore to factory defaults. Press "Enter", which is the center button in the directional pad. Once it is done, press "Send" to reboot.
Congratulations, you just flashed your first rom for Vogue
Step 4. SuperCID
This step can be skipped if you are not thinking of doing anything as far as your radio (such as flashing radios other than the ones intended for Vogue). This is also used to do other things such as modifying certain important things on your device such as the NV files, which is information that will not be discussed here. However, if you are interested in finding out more, simply google it, there is a ton of information out there.
Anyways, back to SuperCID... here is the procedure (thanks to hpnasik at mobile-files.com for the post)
1. Download the following special rom . This is an Alltel rom with radio 3.37. This was specially prepared to be able to reduce the Security Level of the device to level zero.
2. Download mtty since you will need it. Do not worry if you do not how to use it. You will have a step by step in this guide.
3. Flash the Alltel rom from above.
Now comes the fun part...
4. Disable USB in Connection Settings of Active Sync
5. Boot The Phone holding power button and camera button to enter bootloader.
6. Phone Will Display Serial in Bottom
7. Connect Phone to PC
8. Phone should Display USB instead of Serial in Bottom
9. start mtty.exe
10. Select All Default and Connect to USB in drop down box and Shoot the Following Commands (All Commands are case Sensitive)
11. run command rtask a : After this Command Phone will not Display any thing
12. run command echo_on : even though nothing is shown to screen
13. run command readCID : in Sprint it will display SPCS_001
14. run command writeCID 00000000 : Set CID Value to 00000000 replaces SPCS_001 in Sprint (This make PPC Radio Security Level to Zero)
15. run command readCID : This will Display the Update CID as 00000000
16. run Command retuoR : This will return to Original Boot Loader State
Congratulations, you just SuperCIDed your device. Original thread with the instructions can be found here if you are interested.
Step 5. Flashing your radio.
Now that your device has been SuperCIDed, you will have the opportunity to flash radios that have been ported to this device (ie. there is a version of the 3.42.40 radio for the Titan, which has been ported to the Vogue). There are two ways of doing this:
Way 1: Do it by flashing via RUU (same as with flashing a rom)
Way 2: Flash via microSD card. Simply put whichever radio that you wish to flash in the root of a 2GB or less microSD card formatted to fat32. Rename the radio to VOGUIMG.NBH and put your device in bootloader. The flashing will start by itself.
Way 3 (I know I said two ways...): There are a few stock roms that come with new radios. One of them can be downloaded directly from HTC and it is for the Sprint Touch. This one comes with Radio 3.42.30
The other one is for Bell Mobility and this one comes with Radio 3.42.50.
Why am I giving "Way 3" if the other two options seem much easier?? I have run into the problem where my device would not let me flash other radios than the one that I had. SD card method did not work and the RUU started out fine but quits at 8% rebooting my phone and displaying Error 328 in the RUU on the PC. Anyway, here are the links...
Sprint rom with radio 3.42.30
Bell rom with radio 3.42.50
Verizon Stock Rom
All Shipped Roms (All Carriers) - Thanks conflipper!
All Above Radios zipped
The newer radios perform a little better and give out better GPS signal (faster locks)....
Hang on a sec... did you just say GPS?!?!? But my Vogue does not have a GPS.... It does, just read a little further and be happy
Step 6. Enabling GPS, Returning to Stock, and Carrier Cabs
As I said before, there is a GPS hidden on your device. Now, if you are like me and went straight to the specs of the phone to confirm, you will probably try to call BS on this. Long story short, there are a few custom roms which have this "tweak" already implemented (like the one I am using from NFSFan). If you require some more info, I will post it later...
[highlight]Location must be on or else your GPS will not work. To activate it, go to Settings>Personal>Phone and change the Location setting to ON instead of 911 (thanks for pointing it out, th3lolz)[/highlight]
[highlight]For Verizon Users[/highlight]
br125 said:
For those of you with the official mr1 update from verizon that cannot get their gps working:
My xv6900 came with the official update and I got it working, it involves downgrading to a NON-GPS radio, then back to a gps radio...
go here: http://forum.xda-developers.com/showthread.php?t=533639
now the instructions are going to imply that you must load the unlocker before each flash... bs don't worry about that
1. flash the .40 unlocker
2. flash the non-gps rom (reset before customization)
3. flash the 2.31 unlocker
4. flash the vzw rom (reset before customization)
5. flash any custom rom or android rom
that's it, time consuming, but it works
*ignore the multiple flashing instructions, its completely unnecessary, I've never flashed more than once with no problem ever....
I also suggest keeping the vzw radio, but do as you will, I like the 3.37.38 radio.. ain't broke don't fix it
lastly, just make sure you RESET BEFORE THE CUSTOMIZATIONS RUN...... that is what locks your gps.
good luck!
ps. the verizon radio rom that is in that post is for the "leaked" 3.37.37 radio, I reccomend using the official update from verizon here for the 3.37.38 radio rom instead:
http://www.pcdphones.com/phone_downloads.aspx?bid=95&cid=1&mid=302&carrier=Verizon Wireless
RESET BEFORE CUSTOMIZATIONS
Click to expand...
Click to collapse
[highlight]How to Relock you phone[/highlight]
If, for whatever reason you need to return your phone for repair/replacement, you will need to relock it. To relock your phone, simply run the unlocker 0.40 and flash the stock rom of your carrier.
ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
[highlight]Carrier Cabs[/highlight]
Thanks to Codybear for gathering all of the cabs with settings for various carriers. But since the link went down, here is another one courtesy of LMiller1708
https://sites.google.com/site/vogueroms/vogue-files
This information was only gathered by me and I take no credit whatsoever other than trying to put it in a one stop thread. Thanks to the following people
Shadowmite
ImCoKeMaN
mindfrost
NFSFAN
Codybear
joshkoss
and a bunch of people that were involved in developing all this...
Thread sticky'd as requested
Peace,
Josh
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
dwigginstm said:
ok so im a noob n all at this but for some reason when i go to start the Vogue unlocker it tells me to connect my phone, when its already connected. Ive tried everything my even switched to an xp from vista but still no luck. Please help
Click to expand...
Click to collapse
How exciting!! My first victi...erh patient
Did you put the device in bootloader mode? If you did and it is connected to the PC, you should see USB on the screen of your device. Also, do you have ActiveSync on your XP machine? You will need it for the drivers on this step. Changing USB ports sometimes help as well. And one last thing, do not use a USB hub, go directly through the USB ports in your computer. Good luck!
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
yes i have activesync set up with the phone and pc, but when i put the phone in bootloader mode and connect it the pc recognizes it but not activesync. is there another program i can unlock the phone with?
dwigginstm said:
yes i have activesync installed xp, and yes it changes from serial to usb in bootloader mode. But once i connect it to the pc while in bootloader mode my computer recognizes just activesync doesnt, only when its on and not in bootloader mode will activesync recognize it...
Click to expand...
Click to collapse
Do not worry about ActiveSync. While you are in bootloader, the device is not running WM, which is why your computer only sees it as a USB device. This is perfectly fine. ActiveSync will not recognize it.
Please, follow the instructions in my post for unlocking. Read it thoroughly and try to understand it, else you will end up bricking your device.
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
dwigginstm said:
ok but when i begin the unlocking exe it tell me to connect the device to activesync, althought the only way activesync will notice it is if i take it out of bootmode. your help is appriciated
Click to expand...
Click to collapse
that is a message in the RUU. do not pay attention to it. good luck...
so i finally got the unlocker to start and it begins the ten minute process and stops then show a 262 error code ive done this over and over again
Let's go from the top. I just saw the message that you were talking about. The unlocker does ask for ActiveSync as you pointed out and it is asking you to connect the device to the computer. Then it asks for you to press any key when that is done. So, try that and you should see the word "initializing" with a dotted line getting longer for about 20 seconds. Do that.
The RUU will start up afterwards. The prompt will tell you that it is going to flash a new SPL, and if I am not mistaken that is where you are getting stuck.
Just out of curiosity, which version of the Vogue do you have? (Alltel, Bell, Verizon, Sprint, US Cellular)?
no internet
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
terrancextc said:
i just flashes my cell for the first time in with sprint NFSFAN's WM6.5 1.00 FINAL ROM worked great but for some reason my internet doesnt work i downloaded NFSFAN Sprint Provisioning but i dont know how to use it. It has a cople files SPRINT~1.000 and 000DUMMY and setup.xls
thanks in advance
Click to expand...
Click to collapse
You downloaded a cab. Simply put it in your SD card and run it by tapping on it. Don't unzip it...
Unlocker is not 64 bit compatible... grrr....

HardSPL + MTTY, an almost bricked HTC Diamond!

I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
blanktruth said:
Ok, first of all I did not think that it was this dangerous to use MTTY!.
I followed everything and came to these lines
---------------------
Cmd>task 8
Cmd>
---------------------
But after Cmd>task 8 my device restarted immediately before the second line Cmd> appears and I panicked and disconnected my device and pushed the wrong buttons while "Touch Diamond" logo was on the screen.
Now, nothing happens. I can not start from the beginning because I can not start the bootloader by pushing Vol Down and the small red reset button...
Is there anything else left for me to try? Or should I throw my HTC to garbage?
Click to expand...
Click to collapse
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?
i have the same probnlem!! with my diam300
my bootloader show not Diam300 64m but only 64M on the first position in 3color mode... plz help
Connect the Diamond and run the customruu.exe from your desktop, this should work.
how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....
blanktruth said:
I really need some help!
I was following the the post The DEFINITIVE MTTY Thread!! REVISED 02-11-09 and I made a mistake as follows;
Now, I do not know how, but I brought my HTC to bootloader mode and now I can see it via MTTY. But I mistakenly formatted the Internal Storage while I was trying to bring my HTC to bootloader.
Is there any way to upload the DIAMIMG.nbh file to Internal Storage? Or should I follow a different way to save my HTC Diamond?
Click to expand...
Click to collapse
The only thing to do now is to flash back a stock ROM or use a custom ROM with the RUU.
Solved!...
Dom1n8tr1x said:
First of, your device is supposed to soft-reset after the "task 8" command and you should have been holding down the "Volume Down" and "Back Buttons" to begin flashing your new ROM. The whole idea of using MTTY is to format your Main Storage and flash a new ROM. Therefor you should have loaded the ROM that you wanted to flash onto your Internal Storage.
Click to expand...
Click to collapse
Thank you for your reply.
Actually I had uploaded the ROM to my internal storage, but during trying to bring my phone to bootloader mode, I formatted the internal storage...
Anyway, what I did now is, first I opened the USB Connection feature from ActiveSync, and then used CustomRUU.exe to Flash the ROM...
Everything is solved now...
Thank you very much all...
ilijan said:
how to connect if i used mtty... its clear everything what i have on device storage and in bootloader canot start stock or developed rom...
if i want start hard spl its say invalid model it....[/QUOT
bootloader is all you need to revive the phone
connect it to usb in bootloader mode and just install an oficial diamond rom from an windows xp pc.
it's easy
Click to expand...
Click to collapse
plz write here step by step guide how you solved
How it was solved...
ilijan said:
plz write here step by step guide how you solved
Click to expand...
Click to collapse
Actually the most crucial part was to bringing phone to boot loader mode. And I think I managed that by pushing the Volume Down and Back (the arrow pointing left) buttons immediately after restarting my phone. And I had to do this after taking out the battery and putting it back after 5 sec.
When I pushed these buttons at the start up the phone tried to install the ROM from my internal storage, but as I explained I had deleted it by mistake. Therefore it could not find the ROM. I disconnected my phone from my PC and the screen started to say something like Retrying USB connection or waiting for USB connection, something like that.
I restarted my PC in Digitally Signed feature disabled by pressing F8 during start-up. Reconnected my phone to PC (the screen of the phone was still blinking as waiting or retrying usb connection). And voila the phone screen changed to boot loader mode...
The rest was easy. I opened the USB connection feature from ActiveSync and used CustomRUU.exe with a ROM to flash my phone...
That is all...
1. plug phone in to computer in bootloader
2. run customruu or stock from rom update on computer
3. wait for rom to flash to device
4.???
5.profit
but my booloader dont show model ID: DIAM300 64M what i had befor
and show me only: 64M
and any flash error with invalid model id, i canot flash, rom, stock rom, or hardspl...
understand me.. im not totaly noob... i used mtty X times... but now have this probles
can somebody help me?
my diamond dont have model id...
before i had in bootloader mode DIAM300 64M model id, but now i havent got... its show only 64M,
every rom flash stopped at 1% cose model id error,
every hard spl falsh finished 100% but after flash when device restart write model id error...
i cant do anithing... can somebody help me?
For everyone facing problems after flashing his/her device, take a look at the link in my sig.
There you can find a guide to restore your diamond.
you dont understand me..
i canto flash any rom any hard spl becous my diamond dont have device ID...
in bootloader dont show DIAM300 64M but only 64M
after all flash say error mobile ID...
i try mtty, hard reseted, soft... and nothing
after start its show me only first stock screan, the red text on the right bottom sight dont start: 1.17.25.14
2.100000
geny d2x
its maybe wrong but i forgot what waz here...
how can change device model ID? form 64M back to my stock DIAM300 64M?
Try another version of Hard-SPL, some people report that 1.40 not fully works.
I suggest you try 1.94 Olinex.
my diamond is death... if somebody know how can heal it... plz write me...
my device ID is missing... so i cant flash any rom, any hard spl, any radio...
try this? http://forum.xda-developers.com/showthread.php?t=409425&highlight=invalid+model+id
im not sure but i dont think one can brick his/her phone after hard spl, thats the reason of hard spl in the first place that u dont brick it. boot loader is always present
Guide
if you are using Windows XP try the following steps:
Connect your device to your PC
In Active Sync > connection settings > check Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.
Guide
if you are using Windows XP try the following steps:
Connect your device to your PCIn Active Sync > connection settings > check
Allow USB connections (which you have un-checked while doing MTTY)
Find a ROM with CustomRUU.exe / diamond wrapper
Now enter into bootloader mode(forget about the device ID)
Go to customRUU.exe and run it
Follow the ROM installation steps
This will help you installing your new ROM.
I had a similar problem and i resolved it by follwoing the above steps.

WLAN ERROR NOW FIXED!!! Thanks to gruptnt

Thanks to gruptnt over at this thread: http://forum.xda-developers.com/showthread.php?t=490681
WLAN IS NOW FIXED!!!!!! Flash without worry anymore.
my wifi work great again
That is perfect solution !!!
thank !!!
complimenti....
penso proprio che questo tread sia
sticky
eng: sticky for ever
binht611 said:
my wifi work great again
That is perfect solution !!!
thank !!!
Click to expand...
Click to collapse
I also have the same problem... i visit the above post but the post is very big... can you please tell me what steps you follow....
Thank you.... i also have trinity and after this error my trinity hangs frequently.....
These two posts should help:
http://forum.xda-developers.com/showpost.php?p=5313622&postcount=340
http://forum.xda-developers.com/showpost.php?p=5314726&postcount=345
WLAN IS NOW FIXED!!!!!! Flash without worry anymore.[/QUOTE]
Dear Supersport....
thanks for update...
but after the complete procedure (all report was ok), the phone dont restart.
i can see the rom number...etc etc, but remain the htc logo on the black screen.
How can resolve this ?
Thanks a lot for your help.
Vito95
vito95 said:
Dear Supersport....
thanks for update...
but after the complete procedure (all report was ok), the phone dont restart.
i can see the rom number...etc etc, but remain the htc logo on the black screen.
How can resolve this ?
Thanks a lot for your help.
Vito95
Click to expand...
Click to collapse
Have you tried to flash another ROM to the phone and see if that gets it going again?
First of all thanks to you SuperSport and GRUPTNT for this
But for me, unfortunately, it doesn't works, i'm unable, when running Mtty116, to get the USB connection. I got Vista and i think it's the problem.
If somebody got an idea about it...
kabtv said:
First of all thanks to you SuperSport and GRUPTNT for this
But for me, unfortunately, it doesn't works, i'm unable, when running Mtty116, to get the USB connection. I got Vista and i think it's the problem.
If somebody got an idea about it...
Click to expand...
Click to collapse
yes, confirmed, you must XP
SuperSport said:
Have you tried to flash another ROM to the phone and see if that gets it going again?
Click to expand...
Click to collapse
Hi, after some hours the phone is restarted.
Now the only problem is that in comm manger application, Wlan dont work.
remain in off state (red botton).
can you help me?
regards
narshorn said:
yes, confirmed, you must XP
Click to expand...
Click to collapse
Please see this update.
Now, you can run MTTY in Windows Vista and Windows 7. I've made a Video Tutorial Showing how. It's Step 2b on this page:
http://forum.xda-developers.com/showpost.php?p=5314726&postcount=345
my god, you worked late yesterday on this...
thanks for this and everything else, but again, i think that nothing is going to be easy for me...first, if i disconnect USB from mobile center, it's not in the computer management anymore...so i can't change the driver...next if i reconnect the USB connection, i can find it in the device manager but i can't change the driver because:
On my Vista home premium(32 bits operating system) : ''The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for 32-bit systems.
and on my Win7(X64 Home Premium): it's the same message except for X64
BTW, it's not the first time that i tried to flash EOM from your signature and i can't go all the way to the process...don't know why, it did stop before the end...but i got the splash screen
kabtv said:
my god, you worked late yesterday on this...
thanks for this and everything else, but again, i think that nothing is going to be easy for me...first, if i disconnect USB from mobile center, it's not in the computer management anymore...so i can't change the driver...next if i reconnect the USB connection, i can find it in the device manager but i can't change the driver because:
On my Vista home premium(32 bits operating system) : ''The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for 32-bit systems.
and on my Win7(X64 Home Premium): it's the same message except for X64
BTW, it's not the first time that i tried to flash EOM from your signature and i can't go all the way to the process...don't know why, it did stop before the end...but i got the splash screen
Click to expand...
Click to collapse
Ok, I think I forgot to mention one step. Before you disconnect WMDC, be sure your phone is in Bootloader Tri-Color Screen Mode. (Also, before flashing any ROM, be sure to be in Bootloader Tri-Color Screen Mode. [Power/Camera/Reset]) Your Computer will Still be able to see the Phone in Device Manager after WMDC is Disabled.
I don't believe this will work on 64bit Windows. I tried and stopped after a couple failures.
I'm sorry your WLAN is not working still. That's not good and we will do our best to get you back to WiFi.
Looking at the Video again this morning, it does appear to go sort of fast. Hit Pause when needed to read the text pop-ups.
Next thing is I believe you may be selecting the wrong option when you browse for the driver. Be sure you are selecting the option: "Let me pick from a list of device drivers on my computer". If you get a warning that the driver is not the correct driver, BUT you have the option to go ahead with the installation, go ahead and install it. It's a Windows XP Driver, so Win7 will not suggest installing it. But when it's all over, you will be removing it again and reinstalling the Win7 Driver.
SuperSport said:
Ok, I think I forgot to mention one step. Before you disconnect WMDC, be sure your phone is in Bootloader Tri-Color Screen Mode. (Also, before flashing any ROM, be sure to be in Bootloader Tri-Color Screen Mode. [Power/Camera/Reset]) Your Computer will Still be able to see the Phone in Device Manager after WMDC is Disabled.
Click to expand...
Click to collapse
That was it...i succeed to install the driver and WIFi works again
SuperSport said:
I'm sorry your WLAN is not working still. That's not good and we will do our best to get you back to WiFi.
Click to expand...
Click to collapse
don't be, you do so much for the community here
Thanks again...
kabtv said:
That was it...i succeed to install the driver and WIFi works again
don't be, you do so much for the community here
Thanks again...
Click to expand...
Click to collapse
That was FAST , good work! Happy to hear it worked for you.
Also, be sure to delete the XP driver from Device Manager, and re-scan the system to install the original driver. And then, re-activate your USB Connection in WMDC.
kabtv said:
my god, you worked late yesterday on this...
BTW, it's not the first time that i tried to flash EOM from your signature and i can't go all the way to the process...don't know why, it did stop before the end...but i got the 3G Asia splash screen
Click to expand...
Click to collapse
did you experience that...?
kabtv said:
did you experience that...?
Click to expand...
Click to collapse
Did you use SSPL_TRIN.exe to enter Bootloader Mode before flashing? I think that is necessary for a full flash of OEM.
SuperSport said:
Did you use SSPL_TRIN.exe to enter Bootloader Mode before flashing? I think that is necessary for a full flash of OEM.
Click to expand...
Click to collapse
i used the sd card method...
kabtv said:
i used the sd card method...
Click to expand...
Click to collapse
You would still need to use SSPL_TRIN.exe to put the phone into a special Bootloader Mode because the OEM ROMs overwrite the HardSPL on your phone. This special mode allows that to happen.
Copy SSPL_TRIN.exe & your TRINIMG.nbh to your phone's SD Card Root. From your phone's File Explorer program, browse to your SD Card and tap SSPL_TRIN.exe to run it. If asked, go ahead and say "Yes". This will enter a special Bootloader from which you can flash the OEM's.
Only use this method to flash Back to OEM ROMs and NOT for Normal Flashing. You want to use the HardSPL's Bootloader to flash Cooked ROMs to protect your phone.
Download SSPL_TRIN.exe
And, remember, after flashing an OEM ROM, be sure to flash a HardSPL back on your phone BEFORE Flashing Custom ROMs again.
Sorry everyone for getting off topic. kabtv, if you need more help with this, PM me, I'd be happy to help.
SuperSport said:
You would still need to use SSPL_TRIN.exe to put the phone into a special Bootloader Mode because the OEM ROMs overwrite the HardSPL on your phone. This special mode allows that to happen.
Copy SSPL_TRIN.exe & your TRINIMG.nbh to your phone's SD Card Root. From your phone's File Explorer program, browse to your SD Card and tap SSPL_TRIN.exe to run it. If asked, go ahead and say "Yes". This will enter a special Bootloader from which you can flash the OEM's.
Only use this method to flash Back to OEM ROMs and NOT for Normal Flashing. You want to use the HardSPL's Bootloader to flash Cooked ROMs to protect your phone.
Download SSPL_TRIN.exe
And, remember, after flashing an OEM ROM, be sure to flash a HardSPL back on your phone BEFORE Flashing Custom ROMs again.
Sorry everyone for getting off topic. kabtv, if you need more help with this, PM me, I'd be happy to help.
Click to expand...
Click to collapse
Hi,
I have moved to hd, so I didn't come to this forum since then...
I will try to explain a little better the HSPL and official roms.
First, there are several HSPL for trinity. The best one is olipro 1.30, so this th eone we want to get into the trinity.
First the theory, in a .nbh file we have several parts: ipl,radio,spl,splash,os,extrom In an official rom contains all parts, a custom ROM normaly nowdays contains os only. Whith older kitchens contains splash+os
The HSPL of olipro is protected so it is not overwrited by the roms. So it is safer, and you can't get a brick if you don't flash the ipl part.
The SPL is the tricolor program, so when flashing you should view the spl that you have in the trinity.
Whith the customruu of the trinity there is a file called enterbootloader.exe which is transmited to the pda and executed to display the spl. This file is SSPL_TRIN.exe renamed.
Ok, so this are the scenarios:
1) you launch the romupdate whith as/wmdc connected:
Enterbootloader is transmited and executed -> Special SPL 1.07
So when flashing you will flash every part of the nbh (all for oficial, os for custom)
2) you enter manually in boot loader
The SPL in your device -> olipro 1.30
So when flashing you will flash only (ipl,splash,os,ext)
The safer method is to put manually the bootloader mode and flash. You can have the HSPL whith an offical ROM whithout worries. Though there is an exception: you want to update the radio.
If you want to update the radio use method one so you run the other SPL.

Only Bootloader available - no boot possible- HELP!!

Hi, I have a big Problem with my Diamond
I can't boot the Diamond, only in bootloader
Does anybody has an idea how to change the SPL or the ROM ?
Or is there a possibilty to get Jumpspl on my device (i can't access windows)
Thank You for your help, I really appreciate it.
Hi,
I have sort of the same problem, except I have a US DIAM110. If you have found the original stock ROM for your device, try that. It has to work; JumpSPL only works from Windows.
~codeslicer
try using mtty it work for me- diamond 100
and try another usb in ur pc and flash olinex 1.93 again
Flash via RUU, hrad reset, if still in bootloader, Mtty task 8
......
Thank You!!!
bummer
have you tried using a custom RUU to install your stock rom?
extract the stock rom from official RUU and use the custom RUUs that can be found here.
one more thing, you might want to grab the old drivers for mobile device sync and make sure the old drivers are loaded. vista and w7 usually rollback the drivers.
might not work, but worth a shot eh...
hey i had the same problem i tried evrything and it didnt work just like you so i went to htc service center and the flashed my rom back to the box rom check out if there is an htc service centre near you.
Thank You....!!!
Try, with mtty:
Code:
Task 29
Task 8
then remove the device, enter bootloader, and try flashing. Maybe, post to us the output of
Code:
info 0
info 1
info 2
... info 8
etc up to info 10 I think
You can also try pmming Olipro or cmonex, or try looking around on how to do a CID unlock (imei-check or something like that does it, but it's been reverse engineered by now).
Finally, if you're about ready to give up, you can run "task 2A" which FORMATS EVERYTHING. You could be left with a brick. But there's a chance your SPL will be saved and whatever's causing the problem to be removed. Again, I don't recommend it; it's a very powerful command.
Best of luck.
~codeslicer
Thanks codeslicer...
Thanks......
Have the same Problem
i`m also from germany:
Diam300
SPL-193 OliNex
There seems to be a problem with the HSPL?
i tried to flash another H-SPL, but it jups from 0% direktly to 100% and restarts?!
There seems to be a problem?!
codeslicer said:
Try, with mtty:
Code:
Task 29
Task 8
Finally, if you're about ready to give up, you can run "task 2A" which FORMATS EVERYTHING. You could be left with a brick. But there's a chance your SPL will be saved and whatever's causing the problem to be removed. Again, I don't recommend it; it's a very powerful command.
Best of luck.
~codeslicer
Click to expand...
Click to collapse
excuse me...what does it mean "FORMATS EVERYTHING"???
after "task 2A" the first thing to do will be flashin hardspl and then a ROM ???
ok, it is possible to flash roms and radios... but it is impossible to flash any spl!
so whats wrong?
/edit: is it possible to flash SPL on another way? in some "do whatever it says"-way?
the fact that i previously installed XANDROID has nothing to do with the problem,does it?
Bumpt to Top.
Noone an idea?
Can anybody do a checksum with mtty, who has also olinex 1.93 an post the result? i want to check SPL etc. CRC Checksum.
THX!
Still the question: what does the Task 2a on the diamond!?
ok, those who are currios: task 2a doesn´t work neither.... :-/
Lord,
Hard-SPL is protected, which is why it is called "Hard". It is written in "hard" on the memory to prevent it from accidentally being erased. Therefore the memory where Hard-SPL itself resides is protected so a bad flash won't brick your device.
In order to modify the bootloader (in your case it's Hard-SPL at the moment), you have to use Soft-SPL, which "softly" remains in the memory, but is not actually "written" in the memory. To do that, you get something called Jump-SPL. Find it, and execute the .bat program when your device is connected via ActiveSync. Accept the prompt on your device, and the screen will turn black. Now flash the new SPL (bootloader) that you want to install. If you mess up here you can brick your device, but installation is fast.
~codeslicer
Also, when you use mtty, you cannot copy and paste. The program only works when you TYPE it in. So do be careful with Task 2A and do not resort to these tactics unless your device has been fully bricked.
~codeslicer

Categories

Resources