Can someone explain the differences between the different parts of the phone system, what they do? I.e. kernel, firmware (is the kernel in the firmware), pda, phone, csc, modem, etc. Also what steps are generally needed to change each of them? With all the developments going on, it's hard to keep up with what's being changed and why. Any info would be helpful.
To avoid sounding like an ass ill say this. Stick around and use the search feature and read as much as you can and it will start to make sense. The answers to those questions would take some time to explain so if this all interests you like it did me start reading
Related
Greets,
I am running a tilt with stock AT&T roms, but with the bloatware avoided through the timely soft reset.
I am wondering ... can I replace the home screen if I don't flash to a cooked ROM? If so, how?
Thanks!
if by "home" you mean "today" screen, then yes. simply by adding any today screen plugin.
a few things for you to search for:
start|settings|personal|today|items
HTC Home
SPB plus
HTC Homeplug
there's a good start for you
Tried ... Failed ... Help?
Greets,
I attempted to install HTC Home on my stock AT&T Tilt. It did install (confirmed by the fact that when I saw no evidence of it running, I tried to reinstall, and it told me it was already installed).
This still leaves me with my same old screen (except now, the orientation icon changed to a battery with a question mark on it).
Once installed on a stock AT&T Tilt, how do I run HTC Home to replace my main screen?
Thanks!
Changing the Today Screen options is explained in the book that came with your phone called a manual.
jgermuga - Interesting (not to be confused with helpful) response.
Had the presence of mind to check to see if your prior posts were also obnoxious ... not surprisingly, many are. Needless to say, I will not be responding further to anything you might care to characteristically come back with.
Great having you here - you clearly bring a lot to the table.
Start -> Settings -> Today Screen
I guess it may be possible that jgermuga was a bit snide but I can't really blame him/her.
Check your manual, do a search, or try to make your question more understandable.
If you want to change your Today screen, try this link: http://www.microsoft.com/windowsmobile/articles/softwaretips/personalize.mspx
It may be one of the most basic things to do on the PDA. How did you find us anyway?????
No good ...
I respectfully disagree! I do my fair share of answering questions on forums and the usenet, as well as those that come to me via email. I have NEVER been insulting or snide with people who ask questions. If they ask, they are hoping to get an answer, and very little is as disheartenening as learning that someone has posted a reply, only to see that it wasn't a (useful) reply at all.
One can spend their brain cycles coming back with a clever snide statement which does not help at all (and feel morally superior for the wit) or one can be helpful and answer the question. Since this is a forum, and people search for responses, the snide answer only provides a dead end for everyone who may seek help in the future.
So to those who actually answered the question, thank you VERY much.
In my case here, the provided answers did not work, but perhaps I asked the wrong question. I will need to look into this further.
As much time as you have wasted writing long and pointless replies, you could've read your manual and had your question answered already. Trust me - sit down with your phone and your manual and a beer or two and go through every page. I have done that with every phone I have owned and I learned a LOT of interesting little details that I wouldn't have known otherwise.
Lidberg said:
Trust me - sit down with your phone and your manual and a beer or two and go through every page. I have done that with every phone I have owned and I learned a LOT of interesting little details that I wouldn't have known otherwise.
Click to expand...
Click to collapse
I agree. I've been using a PocketPC for over 5 years, and I still take the time to read over every manual. I always find a cool function for a button that I didn't know about, or something new about the OS that was changed, etc.
Not sure anyone will be able to help with this -- it's a weird set of circumstances. But maybe someone's got an idea.
I've got a Vogue that the camera button has stopped responding on. When I press it, it gives no resistance, like the button/spring has just fallen out or moved. I'd like to take it to the sprint techs and see if they can pop it open and make sure everything lines up again (this is, after all, the reason for keeping an equipment protection plan).
However, I'm not going to bring it in running Android, so I need to flash it back to stock. How to do that? Bring up bootloader mode by holding, you guessed it, the camera button (and volume down) at startup.
I know that the RUU application can trigger a reboot into bootloader mode from WinMo -- but I'm sure it has to be hooked up to activesync to do so, so that's not much use.
Is there some other way to get from Android to bootloader? Or... is there any other way to... sort of sideload a WinMo ROM from linux, without going through the bootloader mode? (I seriously doubt that part, but I'm grasping here.)
Or is there another way to get into the bootloader that I haven't thought of? I guess I should ask this in less specific vogue forums. Searching has provided me no clues.
Thanks for any ideas.
http://forum.xda-developers.com/showthread.php?t=708376
OK, so clearly my line about searching doing no good was premature. I'm a little embarrassed now. (I failed to search this particular forum, so I feel like a heel.)
Then again, that thread doesn't do me any good... it just confirms the bad.
Anyway, thanks. So that sounds like a pretty firm no. Ugh, stepping down from 5 buttons to 4 on this phone is not a pleasant proposition. Even with the camera button, it's pretty cramped.
The EnterBootloader.exe tool (which I assume is the same as BootLoader.cab in that thread) should be able to do it... unfortunately, I do not have the disassembly chops to figure out how to replicate its functionality.
makkonen said:
OK, so clearly my line about searching doing no good was premature. I'm a little embarrassed now. (I failed to search this particular forum, so I feel like a heel.)
Then again, that thread doesn't do me any good... it just confirms the bad.
Anyway, thanks. So that sounds like a pretty firm no. Ugh, stepping down from 5 buttons to 4 on this phone is not a pleasant proposition. Even with the camera button, it's pretty cramped.
The EnterBootloader.exe tool (which I assume is the same as BootLoader.cab in that thread) should be able to do it... unfortunately, I do not have the disassembly chops to figure out how to replicate its functionality.
Click to expand...
Click to collapse
hey, makk - can you open the case enough one time to get to bootloader, flash to winmo, then take it in? you don't need it to work forever, right? just enough to get it repaired? heck, even if you shorted it closed it might work.
Yeah, that's the option I'm considering now. Just need to pop the case open... which doesn't look like tons of fun. Anyone have any advice on that count? I actually have that tiny torx screwdriver, but that's about as far as I've gotten.
Edit: Searched and found a nice looking guide. See, I can search!
Edit2: Popped it open, jammed a paperclip into the camera button, got the bootloader up, back to WinMo, easy peasy. (OK, actually, horribly frightening. I hate ribbon cables.) Thanks, guys.
Though I no longer need it, building a linux EnterBootloader executable would be pretty nice -- especially since kernel updates are a pretty common occurrence -- it'd be nice to have a utility that'd grab the voguimg.nbh, put it on the sd card, and initiate the reboot all in one fell swoop. (...after doing some pretty thorough checks to make sure you're ready to go messing with your boot partition, of course.)
I took a look at the executable in ida, hoping that it might be simple enough for me to start to get a grasp of (that'd be very simple, for the record)... it was not. That program is the purest essence of confusion (at least to this assembly noob).
Anyway, if anyone has disassembling knowledge around here, and wants to give it a look, it might be pretty simple. (It also might be not simple -- I don't really have much way of knowing.) It's attached here.
makkonen said:
Though I no longer need it, building a linux EnterBootloader executable would be pretty nice -- especially since kernel updates are a pretty common occurrence -- it'd be nice to have a utility that'd grab the voguimg.nbh, put it on the sd card, and initiate the reboot all in one fell swoop. (...after doing some pretty thorough checks to make sure you're ready to go messing with your boot partition, of course.)
I took a look at the executable in ida, hoping that it might be simple enough for me to start to get a grasp of (that'd be very simple, for the record)... it was not. That program is the purest essence of confusion (at least to this assembly noob).
Anyway, if anyone has disassembling knowledge around here, and wants to give it a look, it might be pretty simple. (It also might be not simple -- I don't really have much way of knowing.) It's attached here.
Click to expand...
Click to collapse
COUGHdzoCOUGH
I don't think I'd want to go up on the roof and turn on the dzo-signal for something so trivial as this.
Hi, hi. I don't recall if this is my first post or not, but my original intent was to post on the developer's forum. I then found out I couldn't. So I'll post here and include a couple of questions/comments I have.
1. Have you noticed that XDA looks like a really happy dude puking the first letter of the alphabet? (That's totally an aside, just getting it out of the way.)
2. Due to some ridiculousness, I now have two Cricket Zios. One of them is working, the other one not. I've had the old one for a few months now and all this time I've been wondering what the heck to do with it. To specify: It went nuts when I tried the update on it (it originally had 1.6) and the corporate store flashed it when I brought it to them. Now when you turn it on, it shows the Android android and tells you to touch it (with the disembodied hand appearing, moving over it, then disappearing, as it's supposed to), but it ignores all input. Have to pull out the battery to shut it off, even. I can then turn it on (so at least I know the End Call button works and I *think* I've tried some combinations that work) and go through the process all over again. The good thing is that I now have a spare battery (go, me). In reading all the threads where developers are unsure of certain things, like whether or not the trackball can light up and whatnot, I'm wondering if it might be worth it for me to take the damn thing apart and take detailed pictures. At the very least, people would be able to see chipsets, individual chips, connections, lights, etc. Does anyone think this would be worth the effort? And, of course, complete loss of the device, though possibly I could use parts in other projects. (The screen, for instance, might be cheap, but it'd be REAL handy used as a miniature second/third monitor like those Liliput monitors.)
3. As a Linux user that doesn't give a damn whether a Windows OS can communicate with my microSD card, is there a reason I should not just format the entire card to something better than fat32?
4. As we all know, the trackball input on the Zio sucks like the Spaceball 1. Could this be improved by replacing the ball itself? It feels cheap anyway and I'm wondering if I could, for instance, take the ball out of a MyTouch 3G and put it in my Zio.
The FCC already has detailed pictures of the zio available, so that would be a waste of a phone.
If your 2nd phone doesnt work, you can always send it to me as a guinea pig phone -- it _really_ would be helpful to have an extra phone to develop with (provided I could get it working -- no guarantees but I'd be willing to try for the following reasons)-- being as any release, mod or anything for that matter I wish to test for you guys has to be done on my main phone, which Im sure any tester could tell you, is a major pain in the ass. lol. So if you really wanna help the cause, that would help me greatly
As for formatting the SDcard -- dont. Your phone saves all data to FAT. The only thing you _may_ wish to do is partition 512Mb off as an ext3 and use link2SD to symlink ur apps to the ext partition.
As for the trackball -- you can try taking it out (if you have the right screwdriver for it), cleaning the contact points, and putting it back together -- that might make it respond better (as I have no problems with my trackball.).
Hope that helps.
~Cheers!
Thank you very much! And I'll totally donate to you the phone (I appreciate a lot of what you've done anyway). Would you mind getting it without the battery?
Don't mind at all -- it'll be plugged in 100% of the time.
Not home atm, but Send me a pm m8.
Sent from my Zio using XDA App
Nice! as an openZio user I thank you
@ SilasMortimer :
Any updates m8? Havent heard from you in a while.
Cheers.
Heya. Sorry I disappeared. I kind of forgot to come back. I think I need to change my settings so I get email notifications.
It'll be sent soon.
Hello,
I see in most of the guides I've read here on XDA that people mention that not all the ROMs are compatible with the devices and it depends in many factors, but most of the time, the information either it's not mentioned or it's confusing (for me at least)
Is there a guide of some type that I can read to learn about all this?
I want to be able to go and test as many of the ROMS around here and see wich one fits best for me, and I want to do it without bricking or semi-bricking my phone.
For example, this phone I have right now I bought it from another person and it was already been tempered with. How can I tell what has been done to the phone (without having to ask the last owner)?
Been going around all the forum but I only get more and more confused from all the comments I've read.
Thanks a lot for the pointers/help/tips or whatever you can help me with!
Well first lets go over what was done to your phone by the previous owner. To make this a little less confusing I want you to power off your phone and when you go to power back on, hold power and the volume down key. there will be info on the screen that comes up. put that info here and I will help you.
You know, I've been looking everywhere for a little while now.
I remember when the first root of the note8 was shown publically, and how they used a su binary left in a combination firmware to facilitate the use of the user mid debug level.
But what has never been explained, even when I ask some dev's, is how it was really implemented in the first place on the n950U.
That root method is now depricated, can some one point me to the specifics of the original Note8 root?
I would really like to continue on where others have left off, but I've found it tremendously hard to get any information to take on the task of continuing where others left off.
Can someone please, give me details. I'm really willing to work on rev 5 bootloaders if some dev's from the older process can give me a crash course or two to catch up please.