My first attempt to upgrade to AP4 did not succeed unfortunately (SPL to 3.50 upgrade went OK though), my power light stayed green and the display wouldn't come on.
So I took the Athena into bootloader and re-flashed back to AP3.
All seemed fine, the "Tap the screen to set up your device" screen appeared, I set it up and let the customization program run.
Unfortunately after the automatic reset at the end of the customization program, the device returned to the "Tap the screen to set up your device" and the customization program started again...
I tried interrupting the customization by soft resetting before it started executing itself, soft resetted during customization, let customization finish again (and again), but the device seems to be in an endless loop....
Any suggestions/help?
Thanks a lot in advance!
this happen because the spl and the kernel, AKA nk.exe, do not match. not sure what to do except try the new ap3 the cmonex posted **not sure if you tried that**
try the 3.0 cmonex posted and enjoy.
solved!
Thanks irus & Pawel062 (and cmonex!), that did the trick!
Probably not a bad idea to advise anybody who needs downgrading from AP4 to AP3 to use that rom. Download it from http://htc-hackers.com/uploads/ap3newspl.zip
See cmonex' thread at http://forum.xda-developers.com/showthread.php?t=386604
***great Information!***
HEY ALL,
I WAS ALSO HAVING SOME ISSUES VERY SIMILAR TO THESE WHILE TRYING TO "DOWNGRADE" TO ANY ROM FROM AP 4.0. THIS IS GREAT INFO AS I BUILD MY OWN ROMS CONSTANTLY, SO I WAS A BIT WORRIED WHEN I COULDNT SWITCH AFTER TRYING AP 4.O, BUT THANKS TO CMONEX, IRUS, & PAWEL062, WE CAN DOWNGRADE A BIT EASIER!
THANKS AGAIN!
M E G
I downloaded the http://htc-hackers.com/uploads/ap3newspl.zip
can anyone tell me the steps
note i'm stuck into the bootloader
mgozamy said:
I downloaded the http://htc-hackers.com/uploads/ap3newspl.zip
can anyone tell me the steps
note i'm stuck into the bootloader
Click to expand...
Click to collapse
just flash it with normal RUU
I have this problem of the "looping" with the customizations. My problem is that I can't get the device to a state where it is "talking" to activesync and from what I see, I need that to push this ap3spl new file.
When you say "just flash it with normal RUU" can you tell me what that means please? (sorry, noob here...) I've spent hours on the forums, wiki etc and I'm a bit lost.
I'm "trying" to get AP4 w/WM6.1 onto the device.
Purchased unlocked (new) and used on AT&T for 6 months.
Went to update the radio to 1.57 and used the unlocker first. (took out SIM/SD first of course).
Got past step one and then got a black screen on reboot...
I got AP3 to load but now I get this fun looping.. Setup device, load customizations, reboot, and start over.
Sounds like this file in this thread is my fix to at least get AP3 working but not sure how to apply. Can I do it from the bootloader?
thanks in advance for putting up with me
Oh yeah:
My current state:
ATHE100
IPL - v2.02
ATHE100 MFG
SPL -v3.50 OliNex
Eureka!
Ok, I'm not a COMPLETE noob.. (close). I'm up and running. AP3 (new spl) loaded, then loaded AP4. Woo Hoo!
No GPS
Well, I guess I'm "Almost" back up and running.
Since step three never got kicked off, it looks like my GPS rom/radio never was rewritten back to the device.
Any help on how to get just the GPS portion back?
Endless loop after flashing AP4
I have a similar problem. My Dopod U1000 was running WM6 and I upgraded to
radio version 1.58.00 no problem. After flashing AP4 I am in a cycle where my initial boot screen has black and white lines at the top and black at the bottom
Then get the Windows Mobile 6.1 screen and after automatic customizing the
PDA resets itself. I have tried to flash the AP3newspl file but it cant communicate successfully with the synced PDA. Any help?
Johnatara said:
I have a similar problem. My Dopod U1000 was running WM6 and I upgraded to
radio version 1.58.00 no problem. After flashing AP4 I am in a cycle where my initial boot screen has black and white lines at the top and black at the bottom
Then get the Windows Mobile 6.1 screen and after automatic customizing the
PDA resets itself. I have tried to flash the AP3newspl file but it cant communicate successfully with the synced PDA. Any help?
Click to expand...
Click to collapse
get into bootloader by pressing camera+reset and check your spl
you can flash a rom from here
also read this
http://forum.xda-developers.com/showthread.php?t=429013
Thanks lakeman. I reinstalled WM6 ROM from the boot loader.
My IPL v1.00 and SPL v1.20. Olipro and Radio 1.58
I have transferred enblerapi.cab to PDA and run it each time but when I flash
AP4 ROM or AP3newspl ROM I get an endless loop and my SPL stays v1.20
I cant seem to get a flash of SPL3.5 which I suspect is the problem.
Am I missing something?
Il download non funziona.
Hi, I’m from a group of peoples whom works in an environment which camera is prohibited. I had tested my Prophet flashing from WM5 to WM6.0, WM6.1 Prophet Shadow 2.0 TE Rom is running smooth and very stable in my Prophet.
Thank-you very much Cloudyfa for your wonderful Rom
As to use my Prophet G3 in my working environment, I had dismantled the camera and test booting up my ppc. During boot up, it hanged at this htc display, done a hard reset and re-boot, it still hanged at this display and it sight like the booting program is searching for something.
Decided to flash back to WM5 NVID and Goodd…. It boot up to WM5 and try clicking on the camera icon, it’s not functioning. Tested it’ functions and connect to GPS every thing works smooth and steady, but not as fast as WM6 Rom and no launcher etc…..
Re-flashed to WM6.0 and WM6.1 Rom, always hanged when boot up in one way or the others . Flashed back to Prophet Shadow 2.0 TE Rom and reboot, it still stuck at the htc isplay page. If look at the booting up window carefully, it show IPL 2.20, SPL 2.20.0000, GSM 02.19.21 & OS 5.2.20.21
To my understanding of the flashing process, the Prophet Shadow 2.0 TE Rom had already flashed in my prophet and rebooted my itself, but hanged at htc display because the process is looking for the camera hardware which I had dismantle out and that why is go round & round until it hanged.
Please correct me, if I’m wrong. Thank-you.
For troubleshooting, can any body provide me a tool (program) and guide me into the nk.nbf file to remove the camera execution file from loading? And with this tool, I can also use it to flash future Rom and enjoy flashing new roms.
Maybe new threads will be form for those who like to have Prophet without camera.
Rewards, I will buy you beer, ha…ha…ha…
Prophet G3 w/o camera
IPL : 2.20
SPL : 2.20.0000
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
Prophet G4 c/w camera
IPL : 2.15
SPL : 2.20.0001
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
glim59 said:
Hi, I’m from a group of peoples whom works in an environment which camera is prohibited. I had tested my Prophet flashing from WM5 to WM6.0, WM6.1 Prophet Shadow 2.0 TE Rom is running smooth and very stable in my Prophet.
Thank-you very much Cloudyfa for your wonderful Rom
As to use my Prophet G3 in my working environment, I had dismantled the camera and test booting up my ppc. During boot up, it hanged at this htc display, done a hard reset and re-boot, it still hanged at this display and it sight like the booting program is searching for something.
Decided to flash back to WM5 NVID and Goodd…. It boot up to WM5 and try clicking on the camera icon, it’s not functioning. Tested it’ functions and connect to GPS every thing works smooth and steady, but not as fast as WM6 Rom and no launcher etc…..
Re-flashed to WM6.0 and WM6.1 Rom, always hanged when boot up in one way or the others . Flashed back to Prophet Shadow 2.0 TE Rom and reboot, it still stuck at the htc isplay page. If look at the booting up window carefully, it show IPL 2.20, SPL 2.20.0000, GSM 02.19.21 & OS 5.2.20.21
To my understanding of the flashing process, the Prophet Shadow 2.0 TE Rom had already flashed in my prophet and rebooted my itself, but hanged at htc display because the process is looking for the camera hardware which I had dismantle out and that why is go round & round until it hanged.
Please correct me, if I’m wrong. Thank-you.
For troubleshooting, can any body provide me a tool (program) and guide me into the nk.nbf file to remove the camera execution file from loading? And with this tool, I can also use it to flash future Rom and enjoy flashing new roms.
Maybe new threads will be form for those who like to have Prophet without camera.
Rewards, I will buy you beer, ha…ha…ha…
Prophet G3 w/o camera
IPL : 2.20
SPL : 2.20.0000
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
Prophet G4 c/w camera
IPL : 2.15
SPL : 2.20.0001
GSM : 2.19.21
OS : 5.2.20.21
Flashed Rom : Transformer 1.1, Shadow 2.0 TE
Click to expand...
Click to collapse
Hey...... did you ever try the simple step.....
remove the sim card?
just brain storming......
Yes, try every methods that i had learn from this thread, from 31/06/08 until now, out of solutions then ask of help
Regards
glim59 said:
Yes, try every methods that i had learn from this thread, from 31/06/08 until now, out of solutions then ask of help
Regards
Click to expand...
Click to collapse
if your prophet still can flash........
did you try intertek's micro V3 rom?
he had removed the default camera (except the camera.dll)
give it a try....... ^^
I removed the camera recently too (G4). Didn't boot either. This has nothing to do with the software, it seems like its in the mobile's firmware (bios).
Instead of removing the camera module, remove the lens! Dead simple. on the sides of the camera lens module there are 4 small metal leaves to prise up. The lens module comes out together with the spring that is underneath it. All you are left with is a cmos. You could possibly put the lens back in later, with a fiddle.... Its now totally useless to take photos with and the security people at your company can see that the camera has no lens when they look through the camera hole at the back of the mobile, which means you'll be OK if they stop you and look at the mobile. So you can't get sacked or carted of the premises.
I work at most of the major car companies in germany, so I have the same problem
Hi, Jellyme
did you try flashing with new rom? did it boot up?
I will download and flashing intertek's micro V3 rom tonight after work
thkx
No, I didn't try a new rom.
I don't think a new rom will work, as my Prophet hung at the HTC Logo, before the OS even started booting. My guess its a Boot ROM thing: It checks for a reponse from the camera chip.
However, I hope you have luck with a new ROM! However, I wouldn't want to be stuck on a particular ROM.... some of them here are just a little too buggy to live with.
jellyme said:
No, I didn't try a new rom.
I don't think a new rom will work, as my Prophet hung at the HTC Logo, before the OS even started booting. My guess its a Boot ROM thing: It checks for a reponse from the camera chip.
However, I hope you have luck with a new ROM! However, I wouldn't want to be stuck on a particular ROM.... some of them here are just a little too buggy to live with.
Click to expand...
Click to collapse
Go for Korand's 3.2 ( wm6.1) stable fast and bug free, its a clean rom with basic features.. ^^
edit: Should be Korand 3.1 ...
> Go for Korand's 3.2 ( wm6.1) stable fast and bug free,
> its a clean rom with basic features..
There are no bug free 6.1 for me. However, most are pretty damn close! It always depends on which functions you need. For some, the 6.1 are bug free, for my particular usage (business) they are good enough, but not bug free. I'm happy with the 6.1 that I use, with the camera lens removed...
The BIOS needs to be told to ignore the camera at startup. Anyone with an idea how to do this?
jellyme said:
> Go for Korand's 3.2 ( wm6.1) stable fast and bug free,
> its a clean rom with basic features..
There are no bug free 6.1 for me. However, most are pretty damn close! It always depends on which functions you need. For some, the 6.1 are bug free, for my particular usage (business) they are good enough, but not bug free. I'm happy with the 6.1 that I use, with the camera lens removed...
The BIOS needs to be told to ignore the camera at startup. Anyone with an idea how to do this?
Click to expand...
Click to collapse
Umm... Does the ROM not boot up at all without a camera (do different - WM5 - ROMs do the same)?
I had tried a few of WM6.0 &WM6.1 without camera, ever intertek's micro V3 rom which removed the default camera (except the camera.dll) advised by dioxda2, It hanged for half a hour at the Front booting display showing IPL..SPL... and showing the ROM version.
As for WM5.0 NVID rom w/o camera no problem flashing and when activate the camera, display flipped and remain normal without having the camera display page.
Thank-you Jellyme for your method, just flashed with camera w/o len last night, but need to flashed 3 times before it able to boot up to Shadow 2.0 TE and it slight unstable when activation of some programs. I will monitor it for a few days.
As for me, re-moving the len from the camera is still no good enough, cause work involve with Military Security. I'm putting my two arms and limbs high up the air , ha..... ha..... ha.....
At the same time, I had also e-mail to HTC service centre to check whether they have any device or dummy camera connector to plunge back on the main board. No reply yet.
Regards
Would completely removing the camera drivers work? Or maybe put some tape over the lens
completely removing the camera, it will boot up to HTC display and then hanged for shadow 2.0T. For the other, stuck Front booting display showing IPL..SPL... and showing the ROM version.
Not adviseable to put some tape over the lens, Security check do not want to see camera in the camera window, ever len is out and still have to place a piece of thick Black paper on the camera receiver to complete cover the shadow of the camera image, in which the camera is still active.
Military security would not clear this conditions of the Prophet or camera phones.
It may be possible to cook a ROM with no camera drivers at all... That way, it wouldn't work at all...
> It may be possible to cook a ROM with no camera drivers at all...
> That way, it wouldn't work at all...
Thats what we want. Actually I think the Camera drivers have only to be removed from the registry... in case references to them are found there. Then the camera drivers should be removed.. or a dummy camera driver written that just has the required interfaces and returns OK at every call, if removing the camera drivers doesn't work.
Maybe getting the driver from a WM phone without a camera or from WM 5.0?
jellyme said:
> It may be possible to cook a ROM with no camera drivers at all...
> That way, it wouldn't work at all...
Thats what we want. Actually I think the Camera drivers have only to be removed from the registry... in case references to them are found there. Then the camera drivers should be removed.. or a dummy camera driver written that just has the required interfaces and returns OK at every call, if removing the camera drivers doesn't work.
Maybe getting the driver from a WM phone without a camera or from WM 5.0?
Click to expand...
Click to collapse
I think devices without the camera won't have the drivers at all... I can re cook a WM5 ROM now with no camera drivers/no camera exes etc...
Hi, my guys over here are buying new camera phone like iphone, Samsung i780, Nokia E51i........etc to dismantle the camera or cameras.
Their phone still work without camera.
FYI only
regards
glim59 said:
Hi, my guys over here are buying new camera phone like iphone, Samsung i780, Nokia E51i........etc to dismantle the camera or cameras.
Their phone still work without camera.
FYI only
regards
Click to expand...
Click to collapse
It might just be WM, or even just the Prophet...
It might just be WM, or even just the Prophet...
Click to expand...
Click to collapse
Samsung i780 is using WM 6.0 rom............ FYI
glim59 said:
Samsung i780 is using WM 6.0 rom............ FYI
Click to expand...
Click to collapse
Then it's our Prophets
hi all, hope someone can help, been reading threads for days and this is about my fifth xda so i'm no newb.
it's an i-mate jamin i got for my father, ipl/spl 2.13.0001 (G4) bought second hand from ebay, seems to work fine running wm5 os 2.13 but won't send text messages, didn't think much of it since i was planning to upgrade to wm6.1, unfortunately NO KNOWN METHOD WORKS.
Here's what i've tried:
Two different windows xp computers, two different cables, re-install activesync, hard reset, multiple connection retries.
PDAViet temp step 1 from OS and Bootload, most common error is [264], tried NVID wm5, tried official IPL 2.20.0001 upgrade and official i-mate ROM, tried jump/soft/hard SPL, all go to white bootload screen but no further, sometimes the green LED will flash as a radio signal on this white screen but usually nothing.
It seems very much to me like the bootloader is not responding, can someone please tell me when you put the phone in the bootloader and plug the usb cable in, after it has said USB, if you then unplug the cable should the USB text dissapear? because on mine it remains..
when running hardspl.bat the only error on the script is;
cerun: program could not execute (0), after trying to run jumpspl, altho it DOES go into the white screen and just sit there, yes i've tried pressing the camera button.
I'm fresh out of ideas here! help please!
when i run Prophet_G4_IPL_v2.20.0001.exe after a hard reset (sticks on bootloader and give [264]) but before that it says upgrade from 1.2.0.0 to 2.20.
That first number doesn't seem right? is it possible the previous owner flashed a G4 ipl onto a G3 device? and how would I tell?
Hi. I have searched the forums, but haven't found the answer I have been looking for, so sorry if this is a repeat.
I am working under Windows 7, installed VMWare and XP Pro on it, and easily installed Hard-SPL and Cracings 6.5. When I went to upgrade the Radio, I was sure to download one without SPL and IPL. I tried to upgrade, but it hung at 2% for at least 5 hours. (I knew it was bad in 2 minutes actually, but decided to wait). Now it will turn on, but to the tri-color boot screen. Tried hard reset (although I didn't really expect it to work). Is there anything that I can do? It shows when I connect it to usb, both on the phone and on the computer.
It is FAR out from under warranty, so thats out, but if there is anything I could try, I would be much obliged for pointers. Thanks a lot!
-Jotek
You need to make the update with RUU 2.5.2
( http://forum.xda-developers.com/showthread.php?t=314952 ).
Try it, if even that does not work (for me it works only with wizard_love ROM
( http://forum.xda-developers.com/show...293480&page=21 loca's post), but not with other cooked ROM's) then you can try WST wizard service tool
( http://forum.xda-developers.com/showthread.php?t=329170 ) to unpack the nbf and load only the OS ROM.
Thanks for the info.
I will try it later this weekend when i get time! (moving to new apt.... sigh... can't feed the addiction)
-jotek
If Tri Colour Screen WST needs to boot into WM OS surely???
How can you use WST if only on bootloader. Please explain as I have similar issues...
Dilbert
I had exactly the same experience as you: Hard-SPL followed by Cracing and then the tri-color screen. This thread helped me revive my G4.
http://forum.xda-developers.com/showthread.php?t=442126
Hey I am having the same problem but with my G3 att 8125. I flashed to 2.26 which I always do before installing any rom then installed X2A Haseebs Iphone Killer and it stalled at 57% for over an hour so I unplugged it and hard-reset it. I have installed this rom about twice and it works fine. Now my phone starts up and goes straight to the Tri-colored bootscreen. When I plug the phone in it displays that it is connected via USB but the computer doesnt recognize it. IPL 2.26, SPL 2.26 as displayed on the screen. PLEASE HELP!
Hi all, I've got the exact same problem as Quadzilla has - any help would be much appreciated!
Hi everyone.
I tried to upgrade my i-mate Jamin to WM 6.5 using this file.
I think I did everything right (I checked the G4 and HardSPL in the beginning of installation and I'm sure my MB is G4).
Everything was going perfect and the installation advanced without any problems, but at the end my Jamin was stuck in the three color screen, showing only the following words:
IPL: 2.13.001
SPL: 2.13.001
I tried to hold the Comm Manager and Soft Reset buttons as this topic recommends, but the phone gets back to the 3 color screen again, and no success...
I tried to pull out and reinsert the battery, also no success...
Please help me, this is my friend's phone! I AM SO NERVOUS and I may kill somebody!
Is there anything I can do to get rid of the 3 color screen?
mahi58 said:
Hi everyone.
I tried to upgrade my i-mate Jamin to WM 6.5 using this file.
I think I did everything right (I checked the G4 and HardSPL in the beginning of installation and I'm sure my MB is G4).
Everything was going perfect and the installation advanced without any problems, but at the end my Jamin was stuck in the three color screen, showing only the following words:
IPL: 2.13.001
SPL: 2.13.001
I tried to hold the Comm Manager and Soft Reset buttons as this topic recommends, but the phone gets back to the 3 color screen again, and no success...
I tried to pull out and reinsert the battery, also no success...
Please help me, this is my friend's phone! I AM SO NERVOUS and I may kill somebody!
Is there anything I can do to get rid of the 3 color screen?
Click to expand...
Click to collapse
Please don't panic! If you see when connect the phone to the computer and USB message on the bottom of prophet screen update is posible. So try to put original WM5 on the phone. Read dioxda2 post for more. For sure you don't hardspl your phone before flashing....
Thanks
bikertibi said:
Please don't panic! If you see when connect the phone to the computer and USB message on the bottom of prophet screen update is posible. So try to put original WM5 on the phone. Read dioxda2 post for more. For sure you don't hardspl your phone before flashing....
Click to expand...
Click to collapse
Thank you very much, my problem solved using the WM5 flashing process.
I thought it's impossible to get the phone connected to PC because activesync wasn't establishing a connection to the phone, but obviously I was wrong.
After flashing WM5, I performed a HSPL on the phone, and then used the file again, and the phone was upgraded to WM 6.5 with no problem.
I previously had downloaded your 6.5 ROM from a crappy forum, which was only including a download link and some useless info, and since I was a newbie myself D), I didn't even know that I should have performed a HSPL before upgrading the OS.