Hi everyone, I'm an idiot. - Mogul, XV6800 ROM Development

First I'd like to truly apologize if this question has been answered before (which I am afraid it may have been).
But today I flashed my Verizon XV6800 with a 6.5 beta5 rom.
Well, after it installed, um, well it won't load basically. After the "Windows Mobile 6.5" screen pops up, a white screen comes up. I don't exactly know how to fix it and reflash it or anything, because my phone isn't detected.
Is there some way to reset the ROM? Like, holding down buttons while it's loading?
I'm truly sorry if this has been answered before, and greatly appreciate the help.

Flash a GPS radio and then hard reset. Followed by a battery pull for a few minutes.
How to get into bootloader is power camera and reset button at the same time. I usually press power and camera at the same time, then press reset button for a sec and let go of them all.

First off, thanks for the reply. Also, I am from Pittsburgh, PA. Cool coincidence. Well, a little north.
Now that I'm at the boot screen, it was able to update again. I know you probably get this question often so thank you for taking the time.
I'm afraid to reinstall that 6.5 mobile beta I tried before. (I'm going back to 6.1 right now). Is there a good 6.5 you recommend? I'm going to try the search feature here, but was interested in what you think was best.

ThomasX said:
First off, thanks for the reply. Also, I am from Pittsburgh, PA. Cool coincidence. Well, a little north.
Now that I'm at the boot screen, it was able to update again. I know you probably get this question often so thank you for taking the time.
I'm afraid to reinstall that 6.5 mobile beta I tried before. (I'm going back to 6.1 right now). Is there a good 6.5 you recommend? I'm going to try the search feature here, but was interested in what you think was best.
Click to expand...
Click to collapse
Once your bootloader is unlocked and you have a GPS radio you can try as many as you like. I guess I would stay away from Beta ROMs. Other than that I dont have a recommendation.

Related

Front Buttons INOP?!?

I have searched this and could not come up with any fixes, but here goes.
On my 8525 most of my front buttons would quite working (Send, End, OK, Start Menu, and Both Top Menu select buttons) on every Cingular 2.06 Rom. This would be a daily thing that could be fixed by a soft reset. Then I upgraded to XDA Live 2.0 everything worked great for a while when all of a sudden all of the front buttons stopped working, all of them except the dpad. I did a soft reset and even a hard reset, and every time it would still not be working. I freaked out the only thing I could think to do is to downgrade to the original Rom 1.34 that was on it when I received it so I could try to send it in for warranty. After the downgrade all the buttons have been working now.
So in my mind I am thinking this is a software issue rather than a hardware problem. But if that is the case what would cause this? Is there any kind of fix?
I really want to put WM6 back on my device, but not at the cost of my hardware buttons.
Any help or advice would be greatly appreciated.
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Never heard of this problem before. There is a fix for the 8525 keyboard in the XDA Live extras, but I'm almost certain it doesn't affect the front buttons.
I'd almost say that its a problem physically with a broken/barely connected button membrane or something similar.. and the action of you moving the phone to reset it/pressing the button is enough to connect it again.
If you're sure its working 100% now, try flashing XDA Live again and seeing if it kills it again!
Philux-X said:
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Click to expand...
Click to collapse
Just a couple ideas. First, what 3rd party apps have you installed after upgrading and have you changed anything in the "softkey" program? Also, when you said you did a hard reset, was it a real hard reset, or just a power down? Some people at first get the two mixed up.
Also, the radio and bl wouldn't have anything to do with a problem like this.
Like TAURUSBulba said, I would think that it HAS to do with some cab/registry or executable you install that is common to all the ROMS that makes it do this. I would suggest you check out your installed applications and research what might create this problem.
The Rest was an actual "hard reset" with nothing else installed on phone except for system files (fresh system). I did not think the BL or Radio would have anything to do with it, I just wanted to be sure. I will try to re-upgrade to XDA Live 2.0 again when I can find some extra time. I will post results if anything changes or I continue to keep having this problem.
I appreciate your feedback.
Thank You

Why is my Jamin stuck on Gullum's Boot screen?

Hey guys,
I successfully put Gullum's V5 Touch ROM on my Jamin and I have been using it since it came out which is a few weeks I think. Today I went to reset it and it's just stuck at Gullum's grey themed Prophet Touch the boot screen.
Does anyone know why that would happen after using it no problem for a while? Can I get any of the info on it back as I didn't syncronize it for a week. I'm guessing a Hard reset will do the job but now I don't trust the ROM if it just randomly locks up.
why didnt you flash to v6 instead?make sure you do step 1 first then proceed to doing step2.gullum is one of the best.beta testers rules!
rovert said:
Hey guys,
I successfully put Gullum's V5 Touch ROM on my Jamin and I have been using it since it came out which is a few weeks I think. Today I went to reset it and it's just stuck at Gullum's grey themed Prophet Touch the boot screen.
Does anyone know why that would happen after using it no problem for a while? Can I get any of the info on it back as I didn't syncronize it for a week. I'm guessing a Hard reset will do the job but now I don't trust the ROM if it just randomly locks up.
Click to expand...
Click to collapse
My advice: look an search a bit more before you start a new thread. There is one (very heavy) allready about this topic. There's even an tips and tricks Wiki-page that makes notice of this problem.
My personal solution: don't restart with the cube active.
It's difficult to search threads that have pages and pages of information. My eyes can only take so much scrolling. And even using the right combination of words to search for is the next thing to be successful at. Anyways I don't want to argue with you as I have been trying to keep up with information as some of you more 'experience' have learned and retained.
I always downgrade before I upgrade and I have done it many times as ROMs just keep coming out by the week!
I'm just wondering if there is anyway to get my Pocket PC back up and running to at least get an excel spreadsheet that is in internal memory. If not then I will suck it up and hard boot it. I'm just confused why a soft reset lead to a full boot screen freeze after countless soft resets before.
We don't going to argue my friend.. it was just a friendly advice!
But did you find the thread that deals with this problem? http://forum.xda-developers.com/showthread.php?t=320689 It realy tells a lot about problems and solutions experienced by other pp.
As about your wish to backup from the bootscreen (if I understand you correctly) I really don't know, never heard nor red about it.
But I did read that someone managed to start up again by removing his SD card, perhaps worth trying.

FallingAngel12 6.1

Im upping it right now to my folder on the ppcgeeks ftp. r4 of my rom, and sorry that it took so long guys. Its still a work in progress, and i am nowhere near completion of it.
FYI: I just tried loading your ROM but my 6800 keeps freezing at the Windows Mobile Version 6.1, the screen that says "Tap the screen to setup your ...."
I loaded a previous ROM and it works fine.
pete9976 said:
FYI: I just tried loading your ROM but my 6800 keeps freezing at the Windows Mobile Version 6.1, the screen that says "Tap the screen to setup your ...."
I loaded a previous ROM and it works fine.
Click to expand...
Click to collapse
Ditto.
Tried soft and hard resets as well as running unlock util.
mugsy77 said:
Ditto.
Tried soft and hard resets as well as running unlock util.
Click to expand...
Click to collapse
weird. like i said on ppcgeeks, i didnt have a problem, try flashing it again, and then hard reset.
I just pulled the battery because i was having the same problem and it now works no problem.
Pulling the battery worked, thanks!
No problem...happy that for once I helped out instead of always being helped.
Per Angel, he's going to look at a memory leak issue that was just discovered. You may choose to wait until he gets that squared away until updating. Angel, is it just a matter of soft resetting daily to prevent a memory leak?
mugsy77 said:
Per Angel, he's going to look at a memory leak issue that was just discovered. You may choose to wait until he gets that squared away until updating. Angel, is it just a matter of soft resetting daily to prevent a memory leak?
Click to expand...
Click to collapse
yeah, thats what i have had to do, wake up and soft reset. from what i have heard it is a problem with 6.1 right now, and i guess thats what we get with beta software. I recommend that you use dcd's right now until i get this all figured out. i will prolly post a cab pack for all my software that i use on the roms.

Bricking/Unbricking/Rebricking

Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Just for future reference...never has your phone been a brick. A bricked phone is just that...a brick, a paperweight, won't do anything at all. It can't be turned on, it can't boot, it can't be reflashed or fixed. It's obvious you're having a problem with something, but I constantly see people on a daily basis saying their phone is bricked when in actuality, very very few people have actually bricked phones.
Sorry, but I have no idea. You're apparently alone in facing this.
Have you tried reflashing to another third party or stock radio/ROM combination to help rule software or a bad flashing out as a cause?
mrfantastic said:
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Click to expand...
Click to collapse
What bootloader are you running? Maybe a bad install of the bootloader?
no, that's not a possibility, the bootloader isn't like a copy of Windows... besides, it's getting stuck on the windows mobile logo, that means its at the kernel.
my advice is to dump that ROM and flash something else.
Olipro said:
my advice is to dump that ROM and flash something else.
Click to expand...
Click to collapse
In case that is interpreted negatively, quite a few are using builds from my kitchen and he's been quite alone in reporting this.
Sorry, I just had to chime in to defend my work.
That said, if one is facing such problems the first avenue to problem solving is not to keep flashing the same radio/build of an OS ROM into perpetuity. Mix things up. Isolate.
I'm not saying i'm 100% positive on this one, but sounds like to me he's using some kind of software that is coded poorly, or something that is corrupting his kernel or the necessary files that boot the os. Sounds like the phone is getting hung up right when it's trying to execute these files at boot.
My advice to you, that is if you want to keep using key's rom, is to create a CLEAN rom, and don't install any software. Run it for a while clean and see if the problem goes away...if that's the case, you need to re-evaluate which software you use.
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
This is a very misleading title for this post. You can't unbrick a true 'brick' - unless it was a brick because you left the battery out.
A true 'brick' can't ever be turned on. It's a dead paperweight. So, there's no chance of unbricking it.
Flashed Keys rom to few phones....never had a problem !
I used olipro 2.40
Right now the phone is fine, it appears to happen randomly, Keys rom is great otherwise (no insult intended). What was meant by the problem with HTC home?
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
Click to expand...
Click to collapse
The windows mobile splash screen or the "silly green screen that says windows mobile" as you put it is not HTC Home. It is not HTC Home that is causing him to lock up at boot time.
To the OP, read my post, it's some piece of software that is causing your lockup. Guaranteed, if you make a clean rom (no software installed except the rom, with nothing cooked into it) I bet you see your problems go away. I then would install each piece of software one by one testing to see if you see the lockups after each one.
help
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
kaos29205 said:
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
Click to expand...
Click to collapse
Kaos,
You will find you get more answers by posting in the appropriate thread. This is not a WM6 thread so chances are that most ppl would ignore your post.
As you are probably on dcd 3.0.x, I have answered your question over there in the dcd 3.0.4 thread. http://forum.xda-developers.com/showpost.php?p=2177772&postcount=459
Apart from the fact that your are more likey to recieve an answer when posting in the correct thread, it will also help others with the same problem find the answer wheb they do a SEARCH.
Also another good place to find general information is in the titan wiki (see the sticky at the top of the titan upgrading section).
Lastly, you could try starting a new thread if you just cant seem to find the appropriate place to get your answer.

[Q] ''Tap here to launch HTC Sense''. Sense will not load!

Hi all,
As the title says, I can't get Sense to load. Any help/advice, preferably me not having to HR, would be much appreciated.
Here's a bit of background info: Yesterday afternoon I noticed my phone was running very low on battery power, I think it was down to 3%, fortunately I was at home so it wasn't a problem.
I plugged the phone into the wall charger and left it. About 4 hours later I went to unplug the phone expecting to find a fully charged up battery. However, the phone was turned off, I very rarely turn my phone off. Puzzlement followed for a second or two until I realised I hadn't switched the plug switch on. What a dummy!!!
Therefore, the phone had powered down through having no battery power. Sense has not loaded since. Would this cause Sense not to load??
I've had a prior problem with Sense not loading and I did a Hard Reset, I couldn't see what else I could do.
But I'm hoping someone quite a lot more knowledgeable than myself maybe knows a way round this without resorting to a HR.
Thanks for any help.
Anyone please?
If you still have the origional ROM running i would say bring it back to the shop from which you got it from and let them repair it
Otherwise i would say try to install HSPL and push another ROM to your phone so that will repair the fault. Installing ROMS wont take to long
wilwilwel said:
If you still have the origional ROM running i would say bring it back to the shop from which you got it from and let them repair it
Otherwise i would say try to install HSPL and push another ROM to your phone so that will repair the fault. Installing ROMS wont take to long
Click to expand...
Click to collapse
Thx for the reply.
Yes I'm still running original ROM although I updated the original 1.43 ROM to 1.72 via the HTC website. I don't yet feel brave enough to flash a custom ROM. Although this might be the right time to do it now. However, if there is anyone who may know a workaround for this without having to flash a custom ROM or hard reset, I would be very grateful.
Thx.
This is not a useful post but i had the same on mine, and had the same update line as you. Out of interest were you running GTX when the freeze happened?
Both times i had to done to me was on the GTX theme, atm not running it due to the effort of reinstalling everything after a HR, i feel your pain!
chris10230 said:
This is not a useful post but i had the same on mine, and had the same update line as you. Out of interest were you running GTX when the freeze happened?
Both times i had to done to me was on the GTX theme, atm not running it due to the effort of reinstalling everything after a HR, i feel your pain!
Click to expand...
Click to collapse
No GTX theme on my phone and the phone didn't actually freeze. As mentioned in my original post, the problem has come about. I think, due to the phone powering off through lack of battery power. This was due to me not switching the plug switch on after having put the phone on charge.
Thx for the suggestion anyway.
try this thread
forum.xda-developers.com/showthread.php?t=594275&highlight=unable+launch+htc+sense
conantroutman said:
try this thread
forum.xda-developers.com/showthread.php?t=594275&highlight=unable+launch+htc+sense
Click to expand...
Click to collapse
Thx for the link, I'll take a look and report back.
Cheers.
That happened to me couple days ago. Tried everything but nothing helped. Had to hard reset in the end.

Categories

Resources