Hi all,
I unlocked the extended rom on my p3300 and had the same problem a few people had with the device wiping the erom after a hard-reset.
I've managed to re-flash the extended rom with version 1.12.405.101 as linked to on the wiki and it works. A hard-reset sets up my device with tomtom and everything else working as it should.
However, if I then do another hard-reset again, it just does the standard windows set-up but doesn't do the additional extended rom set-up. To get it to work, I have to re-flash the device each time and only the first hard-reset works as it should. It seems to be wiping my extended rom!
Can anyone please help?
I've fixed it. You need to make each file 'read-only' in winimage and it stops the artemis deleting it's own erom files when it is first ran!
everything was fine, no problems with the phone at all, than I installed Duttys 4.1 rom and ever since the camera doesnt work. I got the camera to work once since then by un-ticking the camera tab from the Touch flow, soft resetting, then ticking the tab again but now thats not even working. I have installed 2 diferent roms since then and it still doesnt work. also the photo album doesnt work from that tab anymore but does in the program list where as the camera doesnt work at all.
Any help would be great
Have the same problem myself and have yet to find an answer
I found a guy that used advanced config to change one of the camera settings but I tried it and it didnt work
When you flashed the ROM, did you put the phone into boot loader manually, or did the installation software do it?
the installation software did it
dB Zac said:
I found a guy that used advanced config to change one of the camera settings but I tried it and it didnt work
Click to expand...
Click to collapse
I tried that myself and it worked for a while (a couple days) then the camera stopped working again. That trick has not worked since that first time. I have changed roms a couple of times and still nothing.
dB Zac said:
the installation software did it
Click to expand...
Click to collapse
Same here. Also I did accidentally install a rom with the wrong spl and had to hard spl after installing the rom. I think I went from 1.14 to 1.56 or something like that. I had a green tint to the screen until I did the hard spl. I have installed many roms since then and have not had a problem. I did not have a camera issue before this but the camera did work for quite a while after the spl issue. Hopefully this makes sense what I am saying.
so you are saying your camera was fixed after you "re- hard SPL'd" your phone?
dB Zac said:
so you are saying your camera was fixed after you "re- hard SPL'd" your phone?
Click to expand...
Click to collapse
No, I have an unlocked telstra phone and I had flashed my rom a couple times without needing to hard SPL my phone and never had a problem with flashing roms or the camera. It was only after I flashed to a rom that needed the phone to be Hard SPL'd and I didn't properly Hard SPL my phone before flashing the rom. I got the wierd "green tint" to my screen and realized that i had incorrectly Hard SPL'd. I quickly realized my mistake and then did it correctly and then the newer rom worked fine. It was a couple weeks later that the camera stopped working. I can't remember if I was on the same rom or not from when I Hard SpL'd my phone.
Sorry if this is hard to follow.
My thought is, did my upgrade without properly Hard SPL'ing my phone damage the camera or is it something else. Again, I have since properly Hard SPL'd my phone and flashed many roms since without a problem except the non-working camera.
well I don't know but I hard SPL'd my phone the day I got it with the 1.56 HSPL and I have used may roms on this phone. The rom I installed when this happended was duttys WM6.1 rom
dB Zac said:
so you are saying your camera was fixed after you "re- hard SPL'd" your phone?
Click to expand...
Click to collapse
I was trying to revert to an older Hard SPL 1.14 and install an older rom to see if that did the trick. Anyway, in my haste I screwed up and installed the older Hard SPL 1.14 and forgot to add in the older Rom so I ended up with the green screen of death. I couldn't get it to connect via activesync and put it in bootloader mode and re-Hard SPL'd it to 1.56 and the green screen was gone. I was about to go back to the Hard SPL 1.14 with one of Duty's older pre 1.56 Roms but thought I would check on the camera again one last time.
Now the camera works. Again, this is not the first time I have gotten the camera to work and I have no idea how long it is going to last but it is working and I am not going to mess with it anymore right now. I will leave the Hard SPL 1.56 and Miri's WM6.5 Rom that I have on the phone alone and see how it goes.
I know this is not a complete answer and I don't know if just re-Hard SPL'ng will work but it is worth a shot. Again, I downgraded first 1.14, screwed up the phone the went back to 1.56 and the camera started working again. At least I know that it is probably not a hardware issue as I have no where to send it back to for repair. All is well in Wisconsin for the time being.
Well two things:
1st can you just tell me exactly what you did, step by step. If I understand you correctly, I have already tried this but there may be a step or 2 that I missed. please include the roms you went from and two also
2nd, just called HTC and they said my the #'s my phone still has some warranty left and they will honor it in the states (I will reflash to tesla rom and the stock SPL before I send it)
Thank you for keeping me up to date on what you have done to get yours working. If your camera fails again, just call the # on the US HTC customer service site.
x5-rwk said:
I was trying to revert to an older Hard SPL 1.14 and install an older rom to see if that did the trick. Anyway, in my haste I screwed up and installed the older Hard SPL 1.14 and forgot to add in the older Rom so I ended up with the green screen of death. I couldn't get it to connect via activesync and put it in bootloader mode and re-Hard SPL'd it to 1.56 and the green screen was gone. I was about to go back to the Hard SPL 1.14 with one of Duty's older pre 1.56 Roms but thought I would check on the camera again one last time.
Now the camera works. Again, this is not the first time I have gotten the camera to work and I have no idea how long it is going to last but it is working and I am not going to mess with it anymore right now. I will leave the Hard SPL 1.56 and Miri's WM6.5 Rom that I have on the phone alone and see how it goes.
I know this is not a complete answer and I don't know if just re-Hard SPL'ng will work but it is worth a shot. Again, I downgraded first 1.14, screwed up the phone the went back to 1.56 and the camera started working again. At least I know that it is probably not a hardware issue as I have no where to send it back to for repair. All is well in Wisconsin for the time being.
Click to expand...
Click to collapse
hello there ,
1.14 radio is the problem ,
try to flash new one which is 1.16 in same form
http://forum.xda-developers.com/showthread.php?t=529031
or try to get into 6.1 and then Hard Rest with out Upgrade to dutty ,
seems problem in driver...
best regards
I havent had 1.14 on my phone since the day after I got it...
I am not very good at step by step instructions but you have obviously done a lot of flashing already, I will keep it short. Again, this started out as a botched attempt to downgrade my Rom to an older WM 6.1 Rom using the old 1.14 Hard SPL. You might not want to do this as it will temporarily screw up your phone. If you do, here are the steps I took. Really not too involved. Please read all steps first.
1. I synced my phone and downloaded the older 1.14 Hard SPL and flashed it.
link
2. That screwed up my phone "Aweful Greenscreen effect" and was not able use activesync anymore for flashing. I then put the phone into bootloader mode by powering off the phone. Hold in top power button until it asks if you want to power down. Yes. Then when you power up hold the volume down key and the power button at the same time. Make sure your USB cable it still plugged in. Your phone should now be in bootloader mode.
3. I downloaded the most current Hard SPL 1.56 and ran the HSPL Wrapper Blackstone 156OliNex
4. After that the Green Screen problem was gone and when I checked my camera it worked. I took a couple of photos and no problem. I opened it first with the WM Camera Program button then with the Manilla tab. When I used the Manilla tab it had to map the camera/videocamera button as we as find the photo album. After that it has showed up in Manilla normally every time I go back to it. Again, we will see how long this takes.
Thanks for the info on possibly being able to return the device for warranty reasons to HTC.
Hopefully this helps and my links work.
if you don't mind me asking, what dutty rom did you install because this all started for me when I insalled duttys 4.1 WM6.1 rom
Update
When I said I took the phone all the way back to stock, it wasnt 100% true. I loaded a stock HTC rom not a telstra rom.
with that being said, today I got the RMA # from HTC to have the phone repaired so I downloaded the newest updated Telstra Rom and loaded it onto the phone.By the way, My phone did not have the newest Telstra rom on it ever! When the phone was done, I started to prepair to load the newest stock SPL to go along with the rom when I notice the camera works..... What the hell?!?! I try loading a custom rom on it (miris 6.5 rom), camera still works! Hard reset the phone, camera still works. I don't know what this means but my phone is back on line with all features!
Thanks for everyones help and input
Keep your eye on it. It is almost like it slowly looses the connection to the camera and then has a hard time remaking the connection once it is lost. Then you have to do something drastic to get it back. I wouldn't mind so much if it only happened every three or four months but so far I have not been able to keep the camera going past two weeks without loosing it again. Keep me posted if yours goes out again.
Well that didn't take long. Camera is dead again. Going back to WM 6.1 and SPL 1.14 to see if that makes a difference. "unable to initialize" then camera and album disappears from TF3D.
What I ended up doing ( and I did it more then once cuz I tried to load a wm6.5 rom on it) was as fallows
starting with many different wm 6.5 roms, radio: 1.13.25.24 and HSPL 1.56
step 1: I flashed the newest telstra rom (Telstra_WWE_1.59.841.6_Radio_52.64.25.34_1.14.25.24)+
step 2: hard reset
step 3: flashed this custom 6.1 rom (gave up on trying to find a 6.5 rom that worked), L26 ultimate V3.55
step 4: hard reset
step 5: synced to my PC
step 6: loaded all my cabs (soft resetting after every 2 or 3)
Now Miris 6.5 V26 came close to working but when I would sync via PC or Microsoft My Phone it the camera bug would come back.
I am at about 18 hours without the bug. I have soft reset, changed the battery, synced the phone to my PC, called, received calls and text so far...
I have the phone for almost an year without having any problems at all.
Approximately 1 month ago i installed a theme (from this forum) and it worked perfectly untill i decided to change it with another one (also taken from the this forum).After the restart the main screen froze and the touch flo was not active.I could only scroll the menu and acces it.
Also, i could't change the wallpaper.
After this, i tried a hard reset and apparently everything came back to normal EXCEPT: the internet connection didn't work at all no matter the settings i've made and from time to time a "dont send" error popped up. The error was : AudioManager_eng.exe.
After this, i updated my rom (from the htc official website) and had another hard reset and still NOTHING.
In fact i noticed other errors as well.When i tried to acces the mussic tab - audioManager_eng.exe error appeared, when i open wm another wm error appeared.
PS: i also had the storage card formated hopping to solve the audiomanager_eng.exe error (no result)
What should i do now? I feel like i tried everything ...
PS2: i am sorry for the possible mistakes
english is not my mother tongue. Also please try explainig a sollution in simple terms so i can understand step by step what i am supposed to do
thanks
please help....
Have you tried a hard reset to restore everything to default? Or removing theme which started all problems? When you flashed a new rom you may have added more problems, especially if you didn't follow this guide. Depending on what rom you flashed your SPL may not match causing incompatibilities. Does the screen look distorted when you start/boot up phone? Does this discolourization go away when you press power on/off? If so you have a mismatching SPL. Read and follow the dummies guide to see if this fixes some of your issues.
I didnt flash the rom.I had an upgrade .This one: http://www.htc.com/europe/SupportDownload.aspx?p_id=179&cat=2&dl_id=533
And YES, i also had not one hard reset but 4 or so.Can that harm the phone?
Hello,
my friend's /he dodn't speak english/ Leo have problem. The notifications of WM automatically pops up. It start slowly and as time goes on it pops up more frequently and faster. It is impossible to work on it. He tried to flash custom ROM again, but any change.
He tried to remove the screen protector but no luck.
He wearing his Leo in his pocket , but there are any physical changes on the Leo
ANY IDEA?
try going back to the stock (provider) rom.using custom roms can leave old files after flashing which can cause problems.
if that doesn't help try using mtty to format the phone and then flash a new rom.
okey, i tell him, but i can't believe to this because i use the same rom. this problem started after 2 weeks of using the rom.
but thank you very much and i will translate this to him.
hope it will help
okey. he tried to reflash the shipped rom but no luck. tried few hard reset and no luck. today he gonna try myty.
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
I would relock and the re-unlock your hspl and see what happens. That is indeed a weird problem (that you can't send your phone in for).
Good luck
TheWizzard2203 said:
Hi guys
I'm a NRG rom user, com5 build and suddenly I'm experiencing the wierdest problem, which I can't solve by myself. Let me explain what happened.
I flashed the latest rom but also went back a couple of versions. I always flash with the flash util which has the task29 feature build in. What happens is that when I flash a rom, all goes well, the complete process including the XDA_UC auto install process. After that everything is okay and everything works. But when I restart the phone all processes are starting to fail loading. Strange thing is that when I remove the storage card and reboot the phone everything is back to normal again. But as soon as I boot the phone with the storage card in everythings fails. I even had white screens of death when booting with a storage card mounted. I also tried dutty's latest rom and mirri's latest, all have the same problem. This problem appeared all of a sudden, all the cabs etc worked like a charm before, so the problem doesn't lie in the cabs or the files autoinstalled during the xda_uc.
A weird solution to this problem is to flash the latest dutch official stock 1.66 rom which is available for the hd2. With that one everything works, also after a reboot. So I can't use a custom rom anymore. Could this be due to a hardware problem? And if so, how can I explain this to HTC if I want to try to send it to them for repair?
Ow and of course I tried it with several other microsd card, all having the same error, so it's not a sd card issue.
Click to expand...
Click to collapse
sounds like a defective phone!!!!
Yeah, that was my idea too. I tried relocking and reunlocking it with HSPL, but that doesn't matter.
But the problem is, how do I explain this to HTC if I want to send the phone to them for repair? I can't tell them that the problem only occurs when I install a custom made rom.
Pfff okay, I found the solution. It wasn't a hardwareproblem after all. I went through a terribly long trial and error procedure but finally pinned the problem down to only one cabfile, named HD2MemTweak found in the registry tips and tricks section of the general forum of the HD2.
I'd installed the lastest official 3.14 rom and installed all the cabs I was used to. But noticed, after several reinstalls, that when I installed that specific cab and rebooted the phone, everything went wrong. So I installed it without that cabfile and allw as working fine again. Then reinstalled HSPLv3 and installed the latest NRG Cookie Classic rom, which works fine again.
So that was the problem indeed. But one thing is strange of course, is that the mentioned cabfile used to work and suddenly stopped working. Could this maybe have something to do with the fact that the latest roms were build on the new 3.14 official rom? Who knows.....