Related
Hey guys, I've updated to wm6 and sometimes after my p3300 started to either black out or get into a irresponsive mode where the screen is just lightly on. No buttons replies! Once its happens the only solution is to do a soft reset and then pass to phase 2, try to restart it. That bad boy gets stuck directly at the loading process and its maybe - with luck- that it will go through the os loading after 10 tries and soft resets. The phone can work then from five minutes to ten hours and will get stuck again. What is Happening???!!! Also I don't think its the battery cause it does the same thing even with full battery. Last detail, I just passed the warranty limit and its too late to send it back. What can I do??
Did you updated with the official Rom?
Try to flash it again.
Or just try it out a cooked WM6.1 ROM. I recomend Artemis touch Vanilla 4.02.
Cheers
You tried a hard-reset?
babar_almighty said:
Hey guys, I've updated to wm6 and sometimes after my p3300 started to either black out or get into a irresponsive mode where the screen is just lightly on. No buttons replies! Once its happens the only solution is to do a soft reset and then pass to phase 2, try to restart it. That bad boy gets stuck directly at the loading process and its maybe - with luck- that it will go through the os loading after 10 tries and soft resets. The phone can work then from five minutes to ten hours and will get stuck again. What is Happening???!!! Also I don't think its the battery cause it does the same thing even with full battery. Last detail, I just passed the warranty limit and its too late to send it back. What can I do??
Click to expand...
Click to collapse
did u run a uspl first?
jahrami said:
did u run a uspl first?
Click to expand...
Click to collapse
If he upgraded it, then he didn't need it or it was the original WM6 ROM.
The problem was after upgrade!
Flash it again or do a hard reset!
Cheers
Thanks for the help. Yeah I installed the touch Vanilla 4.02 cooked WM6.1 ROM. And I believe the uspl was in the file. As far as I remember I ran it but had no feedback whether it worked or no...
Would a hard reset get the bad boy back to wm5 or reboot with wm6.1?
I *should* reset/default to factory settings for whatever ROM was last successfully flashed to the device. You will lose any installed programs/data so so a PIM backup/ActiveSync before hand if required.
Hi everyone!
Using tools found in Buzzdev's site, I tried to change the splashscreen on my Uni, but something failed. I tried it 3-4 times with correct images (480x640 bitmap 24bit converted in rsb) but after telling me that the update is made, it makes a soft reset and the image that appears is completely messed up!
Also, before making this thing, it remained in the blank initial screen for 1-2 seconds, now it stays there for 15 seconds!!! Everytime I make a SR I fear that it's bricked!!!
Any help is very appreciated...
Auzman said:
Hi everyone!
Using tools found in Buzzdev's site, I tried to change the splashscreen on my Uni, but something failed. I tried it 3-4 times with correct images (480x640 bitmap 24bit converted in rsb) but after telling me that the update is made, it makes a soft reset and the image that appears is completely messed up!
Also, before making this thing, it remained in the blank initial screen for 1-2 seconds, now it stays there for 15 seconds!!! Everytime I make a SR I fear that it's bricked!!!
Any help is very appreciated...
Click to expand...
Click to collapse
Please use the SEARCH button: http://forum.xda-developers.com/showthread.php?t=252720&highlight=splash+screen
have you voted?
Good luck,
Take a look over here:
http://forum.xda-developers.com/showthread.php?t=399403&highlight=bootscreen
I read everything in those 3ds but nothing helped me.
I tried 2 more times to change the splashscreen and I obtained another messed up image, but now the blank screen has a normal behavior: it appears for 2 seconds.
Even if I haven't received error messages I tried to install rapi.cab and SdkCerts.cab, but nothing changed. Trying to install htc_certs it says that it has to unistall the previous customization tools. Have I to continue uninstalling?
Another question: I didn't entered in bootloader mode, was I supposed to?
In edit:
@orb3000: oh yeah, I voted long time ago for our great Uni!
I add another thing: when Uni boots the image is totally messed up, but when I try to flash another image the backup is correct!
I tried to install htc_certs, but nothing changed, except that now it takes more time to boot...
Ok, here are the news:
I found this post that took me to this one.
According to Tomal's instructions, I tried to remove the first 28 byte from the .rsb header, but no program could open it, due to missing header.
I tried to change the initial offset from the batch file (without editing the .rsb file) but nothing changed, same messed up image on boot.
So question is: what am I supposed to do now? Install a rom with a different splashscreen, edit qhat I want and then revert to Tomal's rom? Seems too long to do!
Auzman said:
Ok, here are the news:
I found this post that took me to this one.
According to Tomal's instructions, I tried to remove the first 28 byte from the .rsb header, but no program could open it, due to missing header.
I tried to change the initial offset from the batch file (without editing the .rsb file) but nothing changed, same messed up image on boot.
So question is: what am I supposed to do now? Install a rom with a different splashscreen, edit qhat I want and then revert to Tomal's rom? Seems too long to do!
Click to expand...
Click to collapse
As far as I know you don´t have to reflash a ROM to have a new splash screen.
When I change mine just made a hard reset and voila! my new splash was there with the same ROM I was using
Good luck,
Nope.
That didn't work for me...
Any other idea?
Ok, half fixed everything.
I tried to flash my Uni with a Rom without flash disk and with a new splash screen. I used this one.
Obviously, flashing went wrong and my uni was stuck in the boot screen with a brand new splash screen! Now, I got a new splash screen with a bricked Uni...
Uff...
So I tried to enter boot loader. It did. Tried to install Tomal's 8.5, but again I obtained a bricked Uni.
I used mtty to format DOC and everything worked.
Then I installed again Tomal's 8.2 and my Uni is now working again.
But formatting DOC erased also splash screen!
So I don't have a splash screen at all.
Now, looking back I suppose that next time my ego will try to tell me that a wonderful brand new splash screen would bring my Uni to another level of power, I'll take one finger of mine and close it in the first door I find... That would solve everything.
Auzman said:
Ok, half fixed everything.
I tried to flash my Uni with a Rom without flash disk and with a new splash screen. I used this one.
Obviously, flashing went wrong and my uni was stuck in the boot screen with a brand new splash screen! Now, I got a new splash screen with a bricked Uni...
Uff...
So I tried to enter boot loader. It did. Tried to install Tomal's 8.5, but again I obtained a bricked Uni.
I used mtty to format DOC and everything worked.
Then I installed again Tomal's 8.2 and my Uni is now working again.
But formatting DOC erased also splash screen!
So I don't have a splash screen at all.
Now, looking back I suppose that next time my ego will try to tell me that a wonderful brand new splash screen would bring my Uni to another level of power, I'll take one finger of mine and close it in the first door I find... That would solve everything.
Click to expand...
Click to collapse
OK, send me your splash screen.
I'll prepare it for you.
tomal said:
OK, send me your splash screen.
I'll prepare it for you.
Click to expand...
Click to collapse
Tomal, you're great!
My idea was to use the splashscreen attached, but I was also wondering what is necessary to do for install it into a nk.nbf file.
You said that the header (the first 28 byte) has to be removed, then the .rsb file has to be inserted on the address 0x3f00000, but this is the (absolute?) address on the Uni memory, I don't know how it is managed on the .nbf file...
So, if I convert to .bin (or something like it) the .nbf file and with an hex editor I insert on the correct address the image everything should be fine?
My next question is: how the upgrade utility decides to update or not the splashscreen? Seems that something other has to be changed...
That's one of my screens, it's ready for flashing as you can see here:
http://forum.xda-developers.com/showthread.php?t=399403&highlight=bootscreen
Win_XP said:
That's one of my screens, it's ready for flashing as you can see here:
http://forum.xda-developers.com/showthread.php?t=399403&highlight=bootscreen
Click to expand...
Click to collapse
Infact I took it from yours!
But, as specified in the other posts, with Tomal's rom seems impossible to use the standard procedure...
Perhaps the only way is to insert the splash screen directly in the rom and flash everything at once.
Auzman said:
Infact I took it from yours!
But, as specified in the other posts, with Tomal's rom seems impossible to use the standard procedure...
Perhaps the only way is to insert the splash screen directly in the rom and flash everything at once.
Click to expand...
Click to collapse
ok, here it is.
Connect the device in activesync and run splash.exe
cheers
Nope, doesn't work. I have the same wonderful fully black splash screen...
Tomal, there's no problem, it's good as it is, don't go crazy for it!
And thank you again for your great support!
Auzman said:
Nope, doesn't work. I have the same wonderful fully black splash screen...
Tomal, there's no problem, it's good as it is, don't go crazy for it!
And thank you again for your great support!
Click to expand...
Click to collapse
Nope, don't be upset. I have another way. But you need to consider a HR, so do a backup before start.
Attached you'll find the splash and flashing tools. nk.nbf only contains the splash so your rom will be untouched.
Burn the splash in the regular way...
Once again, nothing good...
I used your last method, flashed the splashscreen, only soft-reset the device, the splashscreen appeared correctly, but it didn't boot.
So, I flashed your 8.5 standard (the special one has rltoday, but I don't like it so much...) and correctly finished the procedure. Once again, device didn't boot.
Used mty, format DOC, flashed again and now it works... Without splashscreen!
So, according to me the only way to restore a splashscreen on my device is to flash another rom which doesn't use flashdisk, change bootscreen and flash back to yours (for me is the best).
Too hard for me: flashing device contains a little danger every time you do it. It's time to leave my Uni with a rom for more than 3 days!!!
Tomal, once again, thank you for your support!!!!!!
Hi everyone,
I've been trying to cook a WM6.5 in Portuguese (I used some files rom WM6.1PTG and I translated some others) with Visual Diamond Kitchen and in the cooking part all went well, I have the .ndh file generated and without errors.
Then I flash the Diamond and after the flashing is concluded the diamond makes itself a reboot and stops after the first boot screen with TouchDiamond and the red information about the versions.
I tried to do a hard restart, soft, remove and out again the batery without success.
Does anybody have the same problem?
I'll appreciate help.
Best Regards,
Armaia
Do you removed "FWUPDATE"?
pspeter said:
Do you removed "FWUPDATE"?
Click to expand...
Click to collapse
that FWUPDATE troubled me a lot!!!!
No, I didn't. Do you think that could be the problem? I,m going to try.
Thanks
Try to change the rom . Pull out the stylus , Press the reset button and hold the VOLUME DOWN and the right down button . After connect to pc
Hi,
I removed the FWDATE but the problem occurs in the same way.
AM
Armaia said:
Hi,
I removed the FWDATE but the problem occurs in the same way.
AM
Click to expand...
Click to collapse
Try to restore first your original shipped rom and then reflash your own rom.
Hi All,
I have the same problem, I flashed MightygroovyROM, after first boot, it stops, there is only "Touch Diamond" on the screen. I tried hard reset but doesnt work. Since activesync connection couldnt establish, I couldnt do anything.
Anyone know another technique to connect without activesync ? or is there any other way to go back old rom any flaeshing a new rom ?
Best regards
Kag
Armaia said:
Hi everyone,
I've been trying to cook a WM6.5 in Portuguese (I used some files rom WM6.1PTG and I translated some others) with Visual Diamond Kitchen and in the cooking part all went well, I have the .ndh file generated and without errors.
Then I flash the Diamond and after the flashing is concluded the diamond makes itself a reboot and stops after the first boot screen with TouchDiamond and the red information about the versions.
I tried to do a hard restart, soft, remove and out again the batery without success.
Does anybody have the same problem?
I'll appreciate help.
Best Regards,
Armaia
Click to expand...
Click to collapse
Okay, I was just changing the startup screen on my Samsung SCH-i760 (WM 6.1) from the animated Verizon splash screen to a new one I just made, and now my phone freezes as soon as it loads to that screen on startup. I have tried soft resetting 3+ times. I can't start the device at all, so there's no way for me to get on to change it back, if thats the problem. What should I do!? I need my phone! Somebody Help Please!!!
This is what I did. I made the file using GIMP. Saved it as a gif, named as "VerizonStartUpAni.gif". I put it in My Documents on my phone, and then moved it to "WINDOWS" with Commander. Then yeah, I copied it over it bad move. After that I soft reset my phone and it seemed fine, until it got to my new startup screen. It just stays there. I left it alone for over 5 minutes and it was still stuck there.
What should I do!? I need my phone! Somebody Help Please!!!
My new startup screen is attached blow. Maybe someone could tell me what I did wrong with it? Feel free to use it if you want!
Thanks in advance!
Hannah4Evr
My new startup screen is attached blow. Maybe someone could tell me what I did wrong with it? Feel free to use it if you want!
You just need to apply Hardreset. But it will erase all your data to default.
http://ars.samsung.com/customer/usa...D=557&PROD_SUB_ID=561&PROD_ID=833&AT_ID=91422
That's what I ended up doing I didn't have anything backed up either... Thanks for the reply!
Hi guys,
Can anyone help me here ?
When I try to start up my Phone, it always loads the bootloader ...
I tried running reflashing a rom and task29, but no help there :s
Does anyone have an idea what to try ?
Tnx
Nick
Some people with the same problem said that their batterie was broken. Can you try another batterie?
I'll give it a try
Will let you know ...
Lennyz1988 said:
Some people with the same problem said that their batterie was broken. Can you try another batterie?
Click to expand...
Click to collapse
Nope, doesnt help.
Tried with a friend's battery, and have the same result.
Also tried using his phone with my battery and worked perfectly.
Any other ideas?
Trickass said:
Nope, doesnt help.
Tried with a friend's battery, and have the same result.
Also tried using his phone with my battery and worked perfectly.
Any other ideas?
Click to expand...
Click to collapse
Just to ask: You're not (accidentally) holding down the volume key when you press the power key (or reset) to turn on, are you? That puts it into bootloader.
MCbrian said:
Just to ask: You're not (accidentally) holding down the volume key when you press the power key (or reset) to turn on, are you? That puts it into bootloader.
Click to expand...
Click to collapse
No, I'm not doing that
I thought maybe it got stuck though, something like that :s but when I do press it, I hear a pretty clear "click", so I guess it's not broken at all...
Also, I noticed that when I try to reflash a ROM, the "current image" (or whatever it's called) is blank ...
(I mean the thing that sais the version number of the currently installed rom)
Okay, sounds dumb I know, but did you flash a new rom after flashing Task29?
It is used to wipe the OS out completely BUT you then have to re-install a new OS...
Just thought I'd ask.....
Same issues.
Same issues on my touch pro 2.
The only solution i find in order to make it boot is with mtty on a Windows xp pc with no activesync.
Perform a
set 14 0
task 8
then the phone boot on the os but on the next reset stay in bootloader !
ultramag69 said:
Okay, sounds dumb I know, but did you flash a new rom after flashing Task29?
It is used to wipe the OS out completely BUT you then have to re-install a new OS...
Just thought I'd ask.....
Click to expand...
Click to collapse
Lol yeah I know that
Thanks anyway
Frederic.james said:
Same issues on my touch pro 2.
The only solution i find in order to make it boot is with mtty on a Windows xp pc with no activesync.
Perform a
set 14 0
task 8
then the phone boot on the os but on the next reset stay in bootloader !
Click to expand...
Click to collapse
Hm, I'll see if I can find a Windows XP pc somewhere and try ... MTTY doesn't seem to work with Win7 x64
Trickass said:
Lol yeah I know that
Thanks anyway
Hm, I'll see if I can find a Windows XP pc somewhere and try ... MTTY doesn't seem to work with Win7 x64
Click to expand...
Click to collapse
Hummm i have see somwhere a howto for mtty on W7... but i'm a little lazy i have choose to do this on a old windows xp
But this command are just temporary i'm searching for something more stable !
Some news from my Rhodium Stuck in bootloader
I have try to Hardspl it (Olinex 0.85)
The good news is i have manage to do it, the bad news is after that even the
set 14 0
don't manage to make it boot.
After a while searching, (thanks wiki of another phone) i have find those command :
password BsaD5SeoA
set 14 0 # Maybe it's usless now but in fact i don't know
set 1 0
task 8
And now i'm back to my start....
I tried using the MTTY commands, and when I did it the first time, the phone booted and performed its "first run setup" thing.
After rebooting though, it went back to the tricolor screen, and I can't get past it anymore, even with the same MTTY commands ...
Any other ideas ? :/
mtty, a lot of post on the internet...
hi,
I think we are a the same point !
I have find a way to start a boot with the HTC screen but the phone tel me that a txt file is missing on the sd card ???!!!???
with mtty :
boot
yes it's quite simple why i haven't think of that befor i don't know... but that didn't solve my problem at all.
I have send a mail to HTC in order to have a diferent point of view but all they said to me is doing a hard reset (who didn't do anything...)
I will post the avancement of my test but i feel a little stuck.
Note : After searchin on the internet, the set 14 0 tel to the phone to boot on the os after a flash (sometime the phone don't reconize the end of flash)
the set 16 0 (or set 16 1) disable (or enable) the RUUNBH tag on boot loader.
More Infos...
I have find a post on a other forum whos said that a defective battery could result to an unstable beaviour of the phone.
I have let it without battery for a day and, today it has directly boot on the OS.
I have ordered a battery on ebay and waiting for it maybe the solution ?
Frederic.james said:
I have find a post on a other forum whos said that a defective battery could result to an unstable beaviour of the phone.
I have let it without battery for a day and, today it has directly boot on the OS.
I have ordered a battery on ebay and waiting for it maybe the solution ?
Click to expand...
Click to collapse
Oke, I will try to take out the battery tomorrow as well ... Although, I tried using a different battery and it didn't help ...
Right now, I managed to boot using mtty set 14 0 > task 8, which seems to work
(sometimes, I need to do the task 8 twice in a row ...)
So as of now, I managed to flash a stock rom onto the phone, and only have to try and reset hardspl back to stock as well.
Waranty here I come ...
lol mine is out of waranty, and it's the solution i ve find everywhere !
did you try hard reset by holding the call and hang up button together when you power up the phone.
last time I remove a program and tha cause me to boot ot a black screen after teh bootloader. Hard reset fix the issue as it return teh phone to the sotck setting of the rom.
PUTALE said:
did you try hard reset by holding the call and hang up button together when you power up the phone.
last time I remove a program and tha cause me to boot ot a black screen after teh bootloader. Hard reset fix the issue as it return teh phone to the sotck setting of the rom.
Click to expand...
Click to collapse
yes, i've try it (HTC has send me the same advise) and... same issue !
In order to done the hard reset (who didn't execute when the phone is to boot in bootloader) i have do a set 14 0 and reset with power and holding the two call hang and power.
But thanks for the advise !
Frederic.james said:
lol mine is out of waranty, and it's the solution i ve find everywhere !
Click to expand...
Click to collapse
Out of warranty ?
How old is it then ?
Mine is just under 1 year old, so I'm lucky I guess ... and I hope
Trickass said:
Out of warranty ?
How old is it then ?
Mine is just under 1 year old, so I'm lucky I guess ... and I hope
Click to expand...
Click to collapse
Hum it's the phone of a firend who give it to me... and he has buy it on e-bay.... for the waranty sound difficult to retreive a bill and... I will search till i find something to do