Develop Bugs

XDA EXEC stuck at spalsh screen after flashing

Hai ,
I tried different flashes of WM6 , then i reverted back to wm5.
But then again i flashed it with wm6 rom.
It flashes it successfully but after hard reset , pressing 0 , it just stays at splash screen giving infos in red.
I am stuck at spalsh screen ... any ideas ?
Also tried uni_exitbootloader .. but still stucks at splash screen
Tried Refalshing it many times but same ..

babablacksheep said:
Hai ,
I tried different flashes of WM6 , then i reverted back to wm5.
But then again i flashed it with wm6 rom.
It flashes it successfully but after hard reset , pressing 0 , it just stays at splash screen giving infos in red.
I am stuck at spalsh screen ... any ideas ?
Also tried uni_exitbootloader .. but still stucks at splash screen
Tried Refalshing it many times but same ..
Click to expand...
Click to collapse
Try enter bootloader and re-flash WM6 Rom, if it still fails to boot, search the Universal forum for MTTY commands to reset partition tables. I suspect the partitions are corrupt.
Hope youre battery is not too low.
Cheers,
Beast

babablacksheep said:
Hai ,
I tried different flashes of WM6 , then i reverted back to wm5.
But then again i flashed it with wm6 rom.
It flashes it successfully but after hard reset , pressing 0 , it just stays at splash screen giving infos in red.
I am stuck at spalsh screen ... any ideas ?
Also tried uni_exitbootloader .. but still stucks at splash screen
Tried Refalshing it many times but same ..
Click to expand...
Click to collapse
Something like this happened to me when I first flashed my Universal, I tried something in the Wiki (Cannot remember?) That told me to use that usb port from now on for all flashing. After that it worked. I will search further to see if I can help...

Okie Problem Solved.
I did this to get myself sigh if relief.
100% working
1. Take out the SD and SIM cards
2. Opened ActiveSync and go to file, connection setting and Un-check "Allow USB Connections". Then press Ok and close ActiveSync
3. Put in bootloader mode (Power + Light + reset) which brings up the "un-backlit" screen with "Serial" at the top and v0.XX at the bottom
4. Plug in USB cable DIRECTLY from PC to Jasjar (MAKE SURE NOT TO USE A USB HUB). You MIGHT then see a warning window complaining that an "Unsigned" device driver is being attempted to be installed. You will be prompted to either "STOP INSTALLATION" or "CONTINUE ANYWAY" - this warning can be safely ignored and so just click on "CONTINUE ANYWAY".
5. Open mtty utility / software
6. Select USB from the "Port" drop-down on the upper left corner of the dialog box and hit OK
7. Then another screen will come up. Hit enter and that will show "USB>"
8. Type "task 28 55aa" and hit enter. {type it manually/ don`t copy and paste commands}
9. use the "Original OEM ROM" that is made for your device and update with it (CE,Extended and Radio) Flash all
10. Hard Reset
Also if your device bootloader version is lower than "v 1.01" you should update that first (before installing the OEM ROM, but NOT before "Task 28 55aa").
After this is complete you may then use your device again.
NOTe : I find you must kill the wcescomm, wcesmgr and rapimgr exe's using task manager before you get the 'usb' option in mtty (kills activesync)

Please,
what to do when there's no USB port in mtty (only COM1 and COM2) ?????

babablacksheep
must say -Thank you!

vjj said:
Please,
what to do when there's no USB port in mtty (only COM1 and COM2) ?????
Click to expand...
Click to collapse
You must disable ActiveSync before connection
and put in bootloader mode (Power + Light + reset) BEFORE run MTTY
after USB must appear in drop-down menu
one more time thanked babablacksheep

Diamond not conecting

I want to upgrade rom on may diamond but when conect the phone to my conputer the phone it just starts to charge. The computer does not detect him and I have activated usb conection on the phone.
I am using a standard miniusb cable used also for canon fotcamera, Nokia N95, motorola V3 (v360 L6, L7 etc.)
I did instaled Activesync on my computer but still no result.

You did no say which Win OS you are using - If Vista then you do not need activesync (AS) but windows mobile device centre or any other Win OS Before Vista then AS is what you need. AS needs to be installed before you connect your phone to the PC.
Have you restarted your PC first before install - this also helps sometimes

Try this....
Start>Settings>Connections>USB to PC and here ....uncheck the box Enable advanced network functionality
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.

R3PUBL1K said:
You did no say which Win OS you are using - If Vista then you do not need activesync (AS) but windows mobile device centre or any other Win OS Before Vista then AS is what you need. AS needs to be installed before you connect your phone to the PC.
Have you restarted your PC first before install - this also helps sometimes
Click to expand...
Click to collapse
I am using Win XP SP2 and I have tried every thing that you said but nothing.

band27 said:
Try this....
Start>Settings>Connections>USB to PC and here ....uncheck the box Enable advanced network functionality
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
Click to expand...
Click to collapse
I did uncheck that box but without any results so now I will try internal method. But I'll have to send the file to the phone via bluetooth and see if it works.

band27 said:
Just a reminder to please use the Internal Method when flashing a new Rom or Radio. Do not rely on your PC as errors occur more frequently.
Click to expand...
Click to collapse
How much is it supose to take "Internal method"?
After pressing Vol_Down + Back button it showed the three color screen then it changed to a white screen with loading on it and it stays like that (after pressing Vol_Down + Back button I didn't press nothing else).

The Internal Method shouldn't take you any longer then 2 min. or so.
Once you have started the flashing to begin in the Grey menu....it will eventually say OK...OK
and yes
at this stage you soft reset and press vol down and centre round button.
Grey menu then gives you a choice to reset back to manufactures settings which is what you want (vol UP)......this should take an additions 2 min. if that.

band27 said:
The Internal Method shouldn't take you any longer then 2 min. or so.
Once you have started the flashing to begin in the Grey menu....it will eventually say OK...OK
and yes
at this stage you soft reset and press vol down and centre round button.
Grey menu then gives you a choice to reset back to manufactures settings which is what you want (vol UP)......this should take an additions 2 min. if that.
Click to expand...
Click to collapse
I have tried everything that you said and nothing.
The only diference is that now when I conect the cable to the phone it asks me witch mode to conect it (Activesync or storage), but the computer still doesn't see's it.

Tried another USB-cable?

chribruu said:
Tried another USB-cable?
Click to expand...
Click to collapse
I tried with 3 diferent cables.

Have you tried putting your device into bootload mode (soft reset & vol. down) and the connecting to your pc. The bottom of your coloured screen should switch from serial to usb....If this switches to USB then you are good to go with downloading what ever Rom using the RUU_
Keep me posted...

band27 said:
Have you tried putting your device into bootload mode (soft reset & vol. down) and the connecting to your pc. The bottom of your coloured screen should switch from serial to usb....If this switches to USB then you are good to go with downloading what ever Rom using the RUU_
Keep me posted...
Click to expand...
Click to collapse
It doesn't switch's to usb it only shows "serial". If I put it into bootmode while it is conected to USB it shows nothing, not "USB" or "Serial" it's blank.
I am begining to belive that there is a hardware problem in my phone.

Do you have .NET framework installed on your PC! if not, get it from http://www.microsoft.com/downloads/d...DisplayLang=en

Trying to flash Tilt 2

Hi all, I have a general problem that I'm hoping someone can help me fix.
I have a Tilt 2, I performed a hard reset back to the stock AT&T rom. I am following the Hard-SPL instructions, but am having difficulties. Here are the steps I have followed:
1) Installed enablerapinew.cab to device and soft reset
2) Am running Rhodium-HardSPL from my PC, while the device is connected via ActiveSync (also showed up in Mobile Device Center as connected on Win7)
3) I am using the Automatic flash button, and I get the first warning dialog just fine. I press Next
4) HardSPL has a list of instructions, saying to make sure that ActiveSync is still connected. This is the part that has the error. When I pressed Next from the previous dialog, the phone goes black, but ActiveSync disconnects from the PC. I have to perform a reset on the device to get it out of the black screen.
I have tried these methods on both a Windows 7 Machine and my Windows XP laptop. It seems that when the phone switches into the black screen, the PC is no longer seeing it as a phone device, so it automatically cancels out activesync.
Any suggestions?
Thanks!

how long are you giving it? When it runs this your phone will reset and go into bootloader mode, so its possible that your phone is just loading. Do any on screen errors pop up?

burtonsnow8 said:
how long are you giving it? When it runs this your phone will reset and go into bootloader mode, so its possible that your phone is just loading. Do any on screen errors pop up?
Click to expand...
Click to collapse
After the first dialog box, the phone goes black and then does nothing unless I use the reset button. I let it sit there for about 10 minutes, and all it did in windows was install a Qualcomm driver. Not sure why activesync cant see the phone once it goes off. I just tried booting the phone up into bootloader by itself and seeing if any drivers installed, but nothing did.

Just tried a different USB port also, same thing.
The drivers it installs into windows when the device goes black are a Qualcomm driver, and HTC USB Sync. Nothing happens after that

try running it while in bootloader.
shut down your phone, hold the volume down and end/power key while using the soft reset button. Once in bootloader make sure it shows you are connected via USB. Run the hardspl.

burtonsnow8 said:
try running it while in bootloader.
shut down your phone, hold the volume down and end/power key while using the soft reset button. Once in bootloader make sure it shows you are connected via USB. Run the hardspl.
Click to expand...
Click to collapse
That did the trick! Thanks buddy, much appreciated!!!

Major Flashing HELP!

I flashed my Diamond to many firmwares before but today after flashing it to Memo's WM 6.1 I cant seem to flash to anything else... I tried every single version of hard spl and its either connection error or nothing happens... i tried mitty but when i connect my phone to the USB, it still says serial not USB...
Im new to this, atm just generally confused... someone help?

It looks like you USB interface is broken or your cable is not OK.
Try some other cable if possible.
Otherwise, do you have a DIAMIMG.NBH file in the root of your storage? If yes, you can flash it directly from internal storage and then examine your USB.

iXiR said:
It looks like you USB interface is broken or your cable is not OK.
Click to expand...
Click to collapse
or maybe you just dont have drivers for usb bootloader installed ?

-
vicai said:
or maybe you just dont have drivers for usb bootloader installed ?
Click to expand...
Click to collapse
not sure what u mean... if i used the 2003 driver uploaded by the forum it doesn't show USB (just serial). but if i use the official version i get USB.
and just to confirm the flashing buttons are : hold down volume key, press back and reset?

-
ok sorry for the big fuzz, ignore my stupidity...
i was pressing the hang off button instead of the back key for the entire day XD
but still got a problem... the screen just says loading and i do have the DIAMIMG.NBH in my root...

megabeater said:
ok sorry for the big fuzz, ignore my stupidity...
i was pressing the hang off button instead of the back key for the entire day XD
but still got a problem... the screen just says loading and i do have the DIAMIMG.NBH in my root...
Click to expand...
Click to collapse
no need, pred vol down (no back key) when you get the usb in bootloader, start the cursomtruu.exe from the rom you have downloaded, next next next finish

My kaiser bricked?

I think my kaiser is bricked somehow. I left it sitting on my charger and came back and it was frozen and now when I turn it on nothing happens except the green light comes on. I can sometimes by messing around with the power plug and battery get it back into android but I cannot even bring up my bootloader anymore. I have no idea if its bricked or whats wrong with it.

Please define messing arround with power plug and battery . Did you try another battery? Battery contacts, miniusb contacts...worst case, something is burned inside. Camera+power+reset doesn't work?
Also, check what was your wife doing before you came back

lol she would never do anything to my phone. By playing with the power plug I mean just plugging it in and taking it out and what not. It's really hard to define it, I would just say ****ing with it lol.

I've come to the conclusion that the radio in my tilt died. Why must my phones always die from a dead radio =( android still works but I can't get into the bootloader anymore and I can't flash a new kernel or even reinstall. Will be nice to see how long this lasts lmao

Can you dump your kaiser to see what is left in our rom?
Follow this procedure to dump your kaiser:
First you have to install QPST (http://www.megaupload.com/?d=OW3ERRNB)
1. Turn on kaiser , now you enter the OEMSBL. You will see nothing on your phone!
2. Your computer will ask drivers for a device if you didn't installed the MotoQ drivers before. Point it to the extracted drivers!
3. If QPST is installed on your computer, disable the com port in the QPST Configurator.
4. Launch mtty and select your com port that is listed as Qualcomm Dignostic Interface 6000 (Comx) in the device manager.
5. Type "h" <Return>
6. if you got any output continue to 7 else pull out the battery, reinsert it and restart at 1
7. type "radata 90000000 1" : Your kaiser is now in loading mode.
8. Close mtty
9. launch the QPST configurator and add the comport and ENABLE it.
10. remove the usb cable of the phone, and reinsert it.
11. your phone must now be listed as Q/QCP-xxx (download)
12. Launch the "QPST Memory Debug" tool to dump smi.bin and ebi.bin
13. Click on browse to select the right com port
14. Click on "Get Regions"
15. Click on "saveto..." to save the files to a directory
16. Zip the files and send it to me.

massivekid said:
Can you dump your kaiser to see what is left in our rom?
Follow this procedure to dump your kaiser:
First you have to install QPST (http://www.megaupload.com/?d=OW3ERRNB)
1. Turn on kaiser , now you enter the OEMSBL. You will see nothing on your phone!
2. Your computer will ask drivers for a device if you didn't installed the MotoQ drivers before. Point it to the extracted drivers!
3. If QPST is installed on your computer, disable the com port in the QPST Configurator.
4. Launch mtty and select your com port that is listed as Qualcomm Dignostic Interface 6000 (Comx) in the device manager.
5. Type "h" <Return>
6. if you got any output continue to 7 else pull out the battery, reinsert it and restart at 1
7. type "radata 90000000 1" : Your kaiser is now in loading mode.
8. Close mtty
9. launch the QPST configurator and add the comport and ENABLE it.
10. remove the usb cable of the phone, and reinsert it.
11. your phone must now be listed as Q/QCP-xxx (download)
12. Launch the "QPST Memory Debug" tool to dump smi.bin and ebi.bin
13. Click on browse to select the right com port
14. Click on "Get Regions"
15. Click on "saveto..." to save the files to a directory
16. Zip the files and send it to me.
Click to expand...
Click to collapse
Would be nice if my kaiser was detecting still... It's weird. It's almost like it has no boot loader but yet it will still sorta boot android.

If the Green led comes on, you are in the OEMSBL. Does your computer asks for drivers when you connect your kaiser to your computer? Ifso, you need the MotoQ drivers (found in this forum) to connect your kaiser OEMSBL to your computer. Then you can use MTTY to talk with it. (if you type something you will not see any output. Only after presing enter/return.
If you need help, let me know.

I've used mtty before. The green led DOES come on but it does not detet at all on my computer. It is not asking for any drivers. When I plug it in nothing happens

then it goes further then the oemsbl.
If it boots Android, it must pass the SPL, so did you try to hold the camera button and then turn on your device? If the SPL tricolor shows, then you can flash. (in theory)

massivekid said:
then it goes further then the oemsbl.
If it boots Android, it must pass the SPL, so did you try to hold the camera button and then turn on your device? If the SPL tricolor shows, then you can flash. (in theory)
Click to expand...
Click to collapse
I've tried to get into the tricolor screen but it is not working with camera + Power and battery insert or on Camera+power+soft reset. I used to have an HTC screen I added display before the kernel loaded. Now the first thing I see is my loading screen for android around a minute or so later only when it's plugged into power.

That's strange. And what is happening when you press the green phone key and powerup? (OEMSBL boot) keep pressing the green button for 5 secs If the green led comes on. Then connect your phone to your computer. Does it appear in the windows device manager?

Does not detect in device manager at all, not even as an unknown device. It's as if nothing was plugged in

If it is not listed as a serial port device. (ports Com & LPT)
then it is not in the OEMSBL. Is your device Security unlocked? If not this can explain why it doesn't enter the OEMSBL with the green button.
Did you also try to put an upgrade file (KAISIMG.NBH) on your root of the SD card?
Maybe this will get launched when your device is turned on?

massivekid said:
If it is not listed as a serial port device. (ports Com & LPT)
then it is not in the OEMSBL. Is your device Security unlocked? If not this can explain why it doesn't enter the OEMSBL with the green button.
Did you also try to put an upgrade file (KAISIMG.NBH) on your root of the SD card?
Maybe this will get launched when your device is turned on?
Click to expand...
Click to collapse
I'll try that out as i've always flashed via usb. Also it is Security unlocked and it is SIM unlocked too.

Nope that did not do a thing. I took a WM rom nbh renamed it to KAISIMG and set it on the root of the SD and it did nothing.

Oh yes, you are right.
in order to load the KAISIMG.NBH, you have to enter the SPL.
hold Camera button and power on. wait 2 secs and unpress the camera button. Then wait for 1 minute, and press the power button again (Power button = start flashing, action key = cancel).

just tried that and still nothing out of my phone

massivekid, i have very similar problem, but my phone turned on.
I dont can turn on bootloader , i try very much metods and any working.
my phone always turn on Smart Mobility i can't change android kernel/back to the windows
few times i tun my pda on blinking yellow led, but computer no see the device

but it still boots into android?
then a jumpspl for android would cure it ;-)

Can you try this one?:
- Remove USB cable/cradle
- Remove battery and re-insert it
- Hold Camera and insert the USB cable.
What do you see now?
The reason why i ask this, is that you have told me that it boots android when you insert the power/usb cable and you see output after 1 min or so when booting android. This behaviour was added to android to let the battery charge...
So the poweron procedure difference from when you press the power button, or when you let the kaiser charge...