Related
I have been less than pleased with my verizon Titan ever since I have had it. It runs very slow. At least twice a week, I have to remove the battery to unfreeze. The other day, I was in a patients room and noticed that her husband had a phone just like mine. I asked him if he liked it and he said that he loved it. I expressed some of my frustrations and he directed me to this website, telling me that he had installed a new radio and kitchen etc and that it now worked great. Looking at some of the websites, I have only become confused and a bit scared to try and tweak my phone. I do not know where to start.
Will somebody give me or direct me to simple idiot proof instructions on how to unlock/unleash the powers of this phone? I need instructions written for someone who knows nothing about altering smartphones.
Thanks in Advance
Not to be rude, but did you even read the stickies on the forum? Plz read the wiki's gather as much knowledge as you can about the subject and then take the plunge. You will find that the wiki's are most helpful. I would update to DCD's latest ROM and get the latest radio.
You will also find out that alot of basic apps don't come with his ROMs. Make sure you get a list of what you need on your phone before you take the plunge. Get a backup program like PIM backup.
Do searches. Research on your own. nobody here is going to do that for you. People created these wiki's for a reason. USE THEM.
In all truthfulness you should not hack your phone unless you know what you are doing. The wikis and threads are very daunting even to those who have some knowledge of what is going on.
Not trying to be rude, but maybe you need a different phone. One that works the way you want it to work right out of the box.
Best case scenario, even if you manage to fumble your way thru the wikis and then later flash your rom, are you going to be able to recover if you get stuck in the bootloader?
The wikis have the info that you need. But like learning medicine you have to apply yourself.
http://forum.xda-developers.com/showthread.php?t=392133
http://wiki.xda-developers.com/index.php?pagename=HTC_Titan
http://wiki.xda-developers.com/index.php?pagename=dcdtitanroms
http://ppckitchen.org
You may want to try this one first, to see what all this cooking stuff is all about
gc14 said:
Yes, this is the official sprint 6.1 update with 3.42.02 radio. Non sprint customers can use it to flash the radio only (if you can't via sd card), but again CAN'T let customizations run. Non sprint customers will have to wait until the custom rom is released.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=402887
There are different methods to flash your rom, and different choices for rom updates. Read up on all of them. Trust me, you will need the info sooner or later.
Like it says in the DCD thread you need to unlock your phone, you need a rom, radio, and a carrier. I just flashed my sprint titan for the first time and just about cried when it got stuck in the bootloader.
oh looky what I just accidentally found in the forums.
http://forum.xda-developers.com/showthread.php?t=403866
Boomstick said:
oh looky what I just accidentally found in the forums.
http://forum.xda-developers.com/showthread.php?t=403866
Click to expand...
Click to collapse
What an amazing concept, you read the forum.
Unfortunately that many guides offer what I feel to be short-cuts. It may be fine if everything goes perfectly, but the problem with such simplifications is that new people can find themselves stuck in unfamiliar territory.
People should be take the time to be aware of background to what they are doing to their phones. Personally, I'd rather recommend taking care to understand the Wiki as myself and others have made the effort to cover many possibilities and recovers when flashing.
Hysterical that the poster identifies himself as a trauma surgeon. Lets hope that if any of us is ever unlucky enough to find ourselves on the other end of the scalpel from this joker, that he isn't standing at the table saying "how do you do this?", and might have taken the time to read up first.
There is no correlation between Surgeon and Computer literacy. My wife's cousin in finishing up Med school and is as bright as they come yet not computer savy beyond common tasks.
As for the actual question he needs not to worry. Using the link with Step by Step to the Verizon upgrade will go easy for you. I only suggest doing the radio via SD card and Rom via USB.
Big Dawg 23 said:
There is no correlation between Surgeon and Computer literacy. My wife's cousin in finishing up Med school and is as bright as they come yet not computer savy beyond common tasks.
Click to expand...
Click to collapse
Its not the correlation, its the attitude.
Interesting attitudes here
I will start of first saying thank you to those of you who actually are trying to help. For the rest of you, yes I did search the forum and yes I did read the Wiki. I still did not feel like I understood things well enough to run the risk of "bricking" my phone. (That is new lingo for those of us who don't spend all of our time on computers) Of course I could spend 10 or 20 hours or more, learning more about the phone, which would mean that some time in October I might have it figured out. My job simply does not give me the time to spend hours and hours trying to tweak my phone. I am in the hospital 110 to 120 hours a week (not a month). I feel lucky when I get a few minutes with my wife and kids. But rest assured, when you crash you car and you are bleeding to death, I am there for you just as I am for everyone else. So for the rest of you who are too cocky and to much of a smartass to help someone else out, I ask what in the world are you doing in this forum anyway. I would predict that you are only in here to take what others are here to give OR just here to try and belittle or make others feel stupid.
traumasurg, well aren't you special?
(That is new lingo for those of us who don't spend all of our time on computers)
Click to expand...
Click to collapse
Get off your high horse, exceptional ego, relax, and take the time to respectfully learn. Only a single comment here may have generalised and only slightly went over-board, but none were as bad as your absolute swipe against this community -- your second post to XDA.... ebb pegged it, as you do have a horrible attitude. You may have made a far better first impression by not posting your introduction to the forum as a request for a short-cut to flashing your phone without also stating that you had paid notice to the Wiki and current threads concerning flashing guides.... If you had trouble understanding, then why did you fail to state exactly where you went out-of-depth? If terminology is "new lingo" to you then did you at least cover the basics of basic in our Wiki's Titan for Beginners?
You come in here looking for help yet some of us were quite polite, accurate and specific in warning that you should not rush forward with short-cuts before being aware of what you are doing and how to recovery. Links to help were provided to you before in between your two posts. Your phone is possibly your critical property so you should avoid messing with it if unsure upon ensuring that you can maintain its function.
Warning for you in the future -- don't join a tech forum insult all as shut-in computer geeks who owe our life to you. This is an anonymous forum, and therefore all are potentially equal here. What distinguishes members is their decorum of respect and a display of an effort to learn.
Keystone said:
Warning for you in the future -- don't join a tech forum insult all as shut-in computer geeks who owe our life to you. This is an anonymous forum, and therefore all are potentially equal here. What distinguishes members is their decorum of respect and a display of an effort to learn.
Click to expand...
Click to collapse
Look, I in no way implied that everyone in here is a shut-in computer geek, although I have no doubt that some are. If you look back over the replies to my original post, there were a couple of members who showed anything but respect. In fact, two of them even posted twice to my original question without any useful information and replied only to in effect say "look how stupid this guy is." If you were on the other end of that reply, what would you think of those here in this forum? There were however several other responses, yours included, that were helpful. Yes I did read through the Wiki and I also had previously looked at two other websites given me by my patient's husband. It was mostly greek to me. That is why I posted.
I must say, I have been in several different forums, dirtbiking, cycling, climbing, trauma, as well as other computer forums and I have never met such attitudes that I met in here this week.
I'll probably just get an iphone next week.
traumasurg said:
I am in the hospital 110 to 120 hours a week (not a month)
Click to expand...
Click to collapse
sucks to be you...
and since there is only 168 hours in a week and you say 120 of it is for work... that leaves you with 48 hours of sleeping time... which would be a little less than 7 hours of sleep a day... how do you eat? how do you shower? how do you get laid? no wonder the attitude... if no one else understands... I do
It is tough for some to answer the same questions that are (I promise) explained in the wiki. The hope is that most people would understand and be able to follow through with the instructions, but this is not for anyone, similar to HAM radio and FTA satellite.
I encourage you to go for the iphone, it seems more your speed.
Alright traumasurg, I can understand being a noob sucks. So here is a breakdown of what you should do if you want to get your phone with a new rom and gps radio.
That stock rom wont work with GPS radio. You need a non-stock rom for it to work.
Get this rom: http://forum.xda-developers.com/showthread.php?t=402920
Get this radio: http://forum.xda-developers.com/showthread.php?t=403280
use this as a guide: http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
Once the rom is installed assuming you have verizon, run the carrier cab.
Get carrier cab here: http://www.lifesnotsogood.com/dcd1182/carriers/dcd Verizon Carrier 20080706.cab
Remember you will need to install the new boot loader first. Then do the rest according to instructions there.
Also, make sure you have another phone handy or a land-line handy for when u call verizon. To get it re-authenticated. You will need to do this whenever u go from a non-gps radio to a gps one. (I reccomend doing this during business hours so u dont freak and wont be able to contact them until they open in the morning)
Oh yeah make sure you backup your contacts to outlook(activesync) or use Pimbackup or your gonna be pissed off.
I am a new Xperia Ultra owner and whilst not planning to do any flashing just yet I thought tonight I'd take a quick look at threads discussing steps that would be involved in doing this.
Let me qualify what I'm about to say by stating that I appreciate people on this site who develop tools which allow us to hack our devices so we can make better use of our phones. They are incredibly skilled, gifted and generous with their time. I would love to be able to spend the time learning how to do this but I simply don't have the time. So please don't take what I am about to say as a criticism but more as an observation, considering the effort contributors put into this it would indeed be incredibly foolish of me to criticise anyone here.
I can probably safely say that none of the contributors are also trained technical writers and a fair number do not have English as their first language. Its my first and only language and I often have difficulty getting the meaning across succinctly not to mind getting the spelling right . And I know even for large software houses support documentation is not a priority.
I want to approach hacking my phone with confidence this time round. In the past I've reflashed several phones for myself and friends and simply followed steps and not really understanding completely what the hell I was doing. Lordmanhattan I know I sent you an email regarding a contradiction on your thread. And you very kindly got back to me very quickly.....amazing, thank you. And then there is the "TA partition", WTH is that? I did very briefly google this to find a quick answer but no joy....grrrr (also looked in the XDA Wiki acronyms) I'm sure if I looked hard enough I'd find it. It's mentioned everywhere but nobody seems to be offering an explanation what it is or what it does or why it's important or what it stands for !!!!
Very often I find threads on here describing how to do something hard to follow and this is often for the following reasons:
It could be that there is more than one way to achieve something so its a case of different people offering varied procedures, this can be confusing
A process may be described but then to the newbie the author seems to miss out on a step that to the experienced is obvious
The level of English used leads the reader to scratching their head wondering ...did he/she mean this or that
Threads not being updated or corrected even after feedback
Okay I won't go on.
So I have decided my time might be well spent doing some background research before delving into messing about with my Xperia Z Ultra and saving you guys from having to deal with daft questions from me.
Now does this mean I have to spend time reading through threads and trying to piece it all together to find the best way through and possibly getting the wrong end of the stick or reading superseded posts?
OR
Are there a couple of sites that will get me up to speed understanding the terminology, hardware, memory management, etc for my phone?
I have a feeling it's going to be a bit of both......your suggestions please
Oh, I stumbled across XDA University but got the impression it wasn't being maintained???
Some of the pages I visited....
A New User’s Guide to Android.......unfortunately none of the images for this page loaded
Video guides .................................had flash presentations which didn't load
Ferg8080 said:
I am a new Xperia Ultra owner...
Click to expand...
Click to collapse
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
I always try and help anew user by using as few TLA as possible in a reply to them. I also try to do the steps as #'d lists with as many steps as possible.
I do think LordManhattan's guide needs a little love as a few things are a little out of date - but it is as comprehensive guide as you could get, and most vagaries are covered in the thread.
TA = trim area, where your unique DRM keys are stored, and god only knows what else.
Thanks for your well written post! First I want to say - like Blueether just did, that we are not mind readers, so we can't possible know people's skill level or what they want to do. That's why I've started to ask them straight up what they want to do and where in the process they are. That way it'll be easier for me to help the other person, and hopefully write a short but complete step by step guide. It won't happen that often, but if I got some time to spare, why not.
My guide is a little out of date now, and I have planned to update it for quite some time, but things are moving so god damn quick around here that even I will get outdated if I take a short break. I recently sent my Ultra in for repairs, and 12 days later when I got it back and ready to get back in the game, a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
There are (of course) one or four ways of doing things around here, and you'll probably get different ways of doing things if you ask me or blueether about rooting or flashing custom ROMs. I guess it's just the way it is. New methods also pop up once in awhile, so some people will adopt these new methods while some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
The TA partition is, like blueether already said, your device's unique DRM keys which makes X-Reality (and other minor things, I guess) work. It's important to make a backup of this partition since you'll lose it when you unlock the bootloader. Why would you unlock the bootloader? You have to unlock it if you want to flash custom ROMs, or if you want to make rooting easier. The problem is that you need to be rooted to back it up, so you'll have to spend some time reading and researching before you start.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here. Walk around like you do in a new city and check out the locals and see what they do and say. You'll pick up a few things here and there and things will start rolling from there.
Sent from my C6806_GPe using Tapatalk
blueether said:
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
Click to expand...
Click to collapse
LordManhattan said:
a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here.
Click to expand...
Click to collapse
Yes you can see some people just rush in with questions without giving serious thought to what they want to achieve. I think its people who don't often understand the process properly, haven't thought it through and are following what seems like a straightforward step by step process. Understanding what you are doing requires patience and TIME.
XDA I think is an unrivalled repository of amazing contributions from amazing people on a technology that is constantly evolving. Its also a jungle. One doesn't go into the jungle unprepared
Thanks for the fantastic advice guys and I will heed but I can't promise I might come out with some corkers
One last thing, how on earth do you find the time to lead a normal life? You obviously love what you are doing. It might be easy to assume everyone who contributes here is in IT. I imagine there are plumbers, electricians, mechanics, office workers, retired folk.....
Hi, after flashing this rom "pac_ruby-nightly-20140428", my camera stop working...
I tried already to install "pac_ruby_4.4.Alpha-1_20140302-235050", but now says "Blame split screen", need hel, i don't know what to do...
Thanks
Bugaman said:
Hi, after flashing this rom "pac_ruby-nightly-20140428", my camera stop working...
I tried already to install "pac_ruby_4.4.Alpha-1_20140302-235050", but now says "Blame split screen", need hel, i don't know what to do...
Thanks
Click to expand...
Click to collapse
AFAIK camera is broken in all new KitKat roms. If you need working cameras use Jelly Bean or ICS builds.
Bugaman said:
Hi, after flashing this rom "pac_ruby-nightly-20140428", my camera stop working...
I tried already to install "pac_ruby_4.4.Alpha-1_20140302-235050", but now says "Blame split screen", need hel, i don't know what to do...
Thanks
Click to expand...
Click to collapse
Before flashing, did you even bother to read through any of the dev or Q&A threads, or do you always just blindly install the most critical software for any device without thought or ramifications of the consequences? To put it bluntly, it shows a profound carelessness at best, or at worse, willful ignorance. Every dev thread here lists either in the first or second post a list of known bugs with their ROMs. ALL versions of KitKat regardless of the author have serious issues at the moment. Even the most casual of glances would have revealed this to you. To start a new thread over a known major issue is a redundant waste of time and bandwidth.
May I suggest that in the future, you at least take a minute or two, to read through and familiarize yourself with what you're undertaking before doing so, in order to prevent wasting everyone else's time with your complaining about a very well known issue.
Edit: Sorry I came on so strong. Listen, everyone was a newbie once, but it's not an excuse for acting like one. You may not have many posts, but you've been here for awhile. There's a wealth of info on the posts pinned to the top of the forums, including board etiquette. If you discover what you think is a bug or if you have an issue, you should post in the Q&A thread for that ROM. But before posting there, you should read through both the Q&A and dev thread to see if it's already known from being previously reported. This keeps clutter off the board and focuses problem solving to the proper channels.
Re:...
Odysseus1962 said:
Before flashing, did you even bother to read through any of the dev or Q&A threads, or do you always just blindly install the most critical software for any device without thought or ramifications of the consequences? To put it bluntly, it shows a profound carelessness at best, or at worse, willful ignorance. Every dev thread here lists either in the first or second post a list of known bugs with their ROMs. ALL versions of KitKat regardless of the author have serious issues at the moment. Even the most casual of glances would have revealed this to you. To start a new thread over a known major issue is a redundant waste of time and bandwidth.
May I suggest that in the future, you at least take a minute or two, to read through and familiarize yourself with what you're undertaking before doing so, in order to prevent wasting everyone else's time with your complaining about a very well known issue.
Edit: Sorry I came on so strong. Listen, everyone was a newbie once, but it's not an excuse for acting like one. You may not have many posts, but you've been here for awhile. There's a wealth of info on the posts pinned to the top of the forums, including board etiquette. If you discover what you think is a bug or if you have an issue, you should post in the Q&A thread for that ROM. But before posting there, you should read through both the Q&A and dev thread to see if it's already known from being previously reported. This keeps clutter off the board and focuses problem solving to the proper channels.
Click to expand...
Click to collapse
Typical geek answer, "normal" from a "kid" that doesn't have friends in real life, and he hides himself behind a computer, pretending that he's the best and smarter then everyone else...
If i wrote here, was because i was looking for help, not for some stupid replies...
Thanks for nothing loser... Keep those comments to your friends that speak "bit and bites"...
Bugaman said:
"bit and bites"...
Click to expand...
Click to collapse
I just peeked in the Dev thread for PAC-Man ROM 4.4.2 for Ruby.
See post #6:
http://forum.xda-developers.com/showpost.php?p=50798437&postcount=6
Also, see posts:
11, 12, 14, 15, 17, 35, 38.
There is a hint of a temporary fix here, in post 39:
http://forum.xda-developers.com/showpost.php?p=51491700&postcount=39
Odysseus1962 said:
May I suggest that in the future, you at least take a minute or two, to read through and familiarize yourself with what you're undertaking before doing so, in order to prevent wasting everyone else's time with your complaining about a very well known issue.
Edit: Sorry I came on so strong. Listen, everyone was a newbie once, but it's not an excuse for acting like one. You may not have many posts, but you've been here for awhile. There's a wealth of info on the posts pinned to the top of the forums, including board etiquette. If you discover what you think is a bug or if you have an issue, you should post in the Q&A thread for that ROM. But before posting there, you should read through both the Q&A and dev thread to see if it's already known from being previously reported. This keeps clutter off the board and focuses problem solving to the proper channels.
Click to expand...
Click to collapse
Incidentally, it's poor etiquette to call someone "loser."
re...
pbergonzi said:
I just peeked in the Dev thread for PAC-Man ROM 4.4.2 for Ruby.
See post #6:
http://forum.xda-developers.com/showpost.php?p=50798437&postcount=6
Also, see posts:
11, 12, 14, 15, 17, 35, 38.
There is a hint of a temporary fix here, in post 39:
http://forum.xda-developers.com/showpost.php?p=51491700&postcount=39
Incidentally, it's poor etiquette to call someone "loser."
Click to expand...
Click to collapse
Thanks a lot for or reply, i will check the posts... that was exactly what i was expecting from this site,... HELP!
Calling "loser" wasn't nice? I think it was... After the reply that he did to my comment, i think i was too nice, when i call him "loser"...
Once again, thanks a lot... :good:
Bugaman said:
Typical geek answer, "normal" from a "kid" that doesn't have friends in real life, and he hides himself behind a computer, pretending that he's the best and smarter then everyone else...
If i wrote here, was because i was looking for help, not for some stupid replies...
Thanks for nothing loser... Keep those comments to your friends that speak "bit and bites"...
Click to expand...
Click to collapse
Bugaman said:
Thanks a lot for or reply, i will check the posts... that was exactly what i was expecting from this site,... HELP!
Calling "loser" wasn't nice? I think it was... After the reply that he did to my comment, i think i was too nice, when i call him "loser"...
Once again, thanks a lot... :good:
Click to expand...
Click to collapse
FYI Spanky, I'm no kid, I'm a 51yo man, a truck driver (Teamsters Local 769), who could drop you in a heartbeat. If I (someone with no formal IT training and a HS diploma from 30 years ago) can figure this out in my off-time, between dealing with work, and my family, what's your excuse? All you had to do was look at my profile before speaking out of the wrong orifice, and you'd know this.
It appears you're even less capable than I gave you credit for in my previous post, since you show a proclivity for being unable to read or do research, and have wedged your foot so far into you mouth that it's impossible to extricate. I've forgotten more than you've ever learned (obviously not a high bar to leap over). Unlike yourself, I contribute here towards providing useful info and help to others who're willing to help themselves. Hence, my high ratio of thanks to posts in a short time here. You, on the other hand, have never provided one bit of useful information in your much longer time on the board (which is easily verified by searching your previous posts).
I don't pretend to be smarter than you, I know I am! That's because I have enough common sense to know my abilities and limitations, something you obviously lack. You seem to have selected an apropos handle, "Insectman." So by all means, obliviously continue along in your vacuous ways, and slither back into the damp crevice you were hiding in. Have a nice day!!!!
Odysseus1962 said:
FYI Spanky, I'm no kid, I'm a 51yo man, a truck driver (Teamsters Local 769), who could drop you in a heartbeat.
Click to expand...
Click to collapse
You're also very rude.
You wasted more time insulting the guy than you did helping him. While I do support use of the search function sometimes it is not so clear cut for people. The first response you typed out was extremely unwarranted IMHO. This one, not much better. You seem to have quite the ego.
sam_conrad said:
You're also very rude.
You wasted more time insulting the guy than you did helping him. While I do support use of the search function sometimes it is not so clear cut for people. The first response you typed out was extremely unwarranted IMHO. This one, not much better. You seem to have quite the ego.
Click to expand...
Click to collapse
I'm sorry, he's rude? LOL Bruh, look at his thanks meter. He's HELPING people. He knows his stuff, so he deserves to have an ego. ESPECIALLY since he built his own ROM.
But I guess you're too fat headed yourself to be humble and accept the fact that this thread could have been avoided if the OP had just read the changelog. Let's face it, if by some mishap the OP had bricked his device he'd be crying for help (just like I did) and I know for a fact that I didn't read anything before (cause I was stupid, and I can acknowledge the fact that I used to be ignorant and now I take the time to read through the forums properly before I post unnecessarily, and Ody here has helped me a great deal.)
So before you go calling people rude and judge them prematurely, take a minute to really think about what you want to post.
PS. he did apologize, so I see no need for you to be bashing him still. I, on the other hand, don't give a damn.
I'm bored, so I went through the Q&A
Remind me not to do this again.
@Darin_Ram, thanks for your strong defense. I do greatly appreciate it, however, the truth of the matter is that @sam_conrad is correct. I was rude to the OP. No matter how much good I do in assisting others here it doesn't mitigate the matter, because two wrongs don't make a right. I lost my cool when I read the comments he directed towards me and lashed out in an unbecoming manner. For this there is no excuse. If my kids had behaved in such a way I would have had a conniption, so I should expect no less from myself.
Thanks again for your heartfelt comments.
Did you maked backup of your last rom
Bugaman said:
Hi, after flashing this rom "pac_ruby-nightly-20140428", my camera stop working...
I tried already to install "pac_ruby_4.4.Alpha-1_20140302-235050", but now says "Blame split screen", need hel, i don't know what to do...
Thanks
Click to expand...
Click to collapse
DID YOU MAKED BACKUP OF YOUR LAST ROM IF NOT DON"T CRY JUST FOLLOW STEPS
Download this rom Click Here
Flash rom using HTC Amaze 4G All-In-One Toolkit V5.2 - (Extras-Flash Factory RUU zip)
backup?
jitz_ said:
DID YOU MAKED BACKUP OF YOUR LAST ROM IF NOT DON"T CRY JUST FOLLOW STEPS
Download this rom Click Here
Flash rom using HTC Amaze 4G All-In-One Toolkit V5.2 - (Extras-Flash Factory RUU zip)
Click to expand...
Click to collapse
Link's not working.
Maybe what you are offering is that if he can't recover his original system from his nandroid backup, he can download and flash a stock ROM, such as this GingerBread (courtesy ravike14 signature):
http://download2.clockworkmod.com/developer/2184/2115/ruby_unsigned_021812_031444.zip
or perhaps a stock from here:
http://forum.xda-developers.com/showthread.php?t=1617644
Odysseus1962 said:
@Darin_Ram, thanks for your strong defense. I do greatly appreciate it, however, the truth of the matter is that @sam_conrad is correct. I was rude to the OP. No matter how much good I do in assisting others here it doesn't mitigate the matter, because two wrongs don't make a right. I lost my cool when I read the comments he directed towards me and lashed out in an unbecoming manner. For this there is no excuse. If my kids had behaved in such a way I would have had a conniption, so I should expect no less from myself.
Thanks again for your heartfelt comments.
Click to expand...
Click to collapse
This is a much more noble reply. While you're extremely helpful to the community, and I never disagreed that you are, it's no excuse to be an ass. There is never a "deserving right" to be rude in any case. In my world, at least, the people treat each other with respect or they're gone. I know that I don't have time to deal with people that don't want to move forward and get along. Regardless of how stupid some peers might seem, or how smart one may believe he/she is, I think showing some humility and always staying grounded goes a long way.
I often tell people that some of the world's greatest minds are the dumbest of us all - some of your behavior represented why. When we're in an advantaged position of knowledge, we should encourage others to learn from us, not the other way around.
@Darin_Ram - no need to throw personal jabs at me, trying to tell me I'm full of myself (or "fat headed"), please and thank you. I don't claim to be a genius in any regard, and especially not the mobile space. I just have found Ody on a few too many accounts to be unnecessarily rude... My own focus is on computer networking and desktop PCs. :good: I usually reside at XtremeSystems.org and HWBOT.org due to my hobby of extreme LN2 overclocking.
Use original rom of htc
pbergonzi said:
Link's not working.
Maybe what you are offering is that if he can't recover his original system from his nandroid backup, he can download and flash a stock ROM, such as this GingerBread (courtesy ravike14 signature):
http://download2.clockworkmod.com/developer/2184/2115/ruby_unsigned_021812_031444.zip
or perhaps a stock from here:
http://forum.xda-developers.com/showthread.php?t=1617644
Click to expand...
Click to collapse
BEST OPTION EVER AFTER GETTING THROUGH ALL THE ROM FROM DEV FORUM I FOUND THAT NO ONE IS PROPER AND COMPATIBLE FOR OUR DEVICE ONLY ORIGINAL ROM ALLOW YOU TO USE ALL THE FEATURE STRESS FREE + STABLE VERSION BE SMART !
ONE DAY YOU HAVE TO BACK AGAIN FOR THIS ROM .. I ALWAYS DO SO .. MAY BE EXPERIENCED PERSON AGREE WITH ME !
:good:
http://www.htcdev.com/devcenter/downloads
So someone said that if your device dies it can still be detected by adb or something , could someone explain those steps or add in something else I can do to save this kindle.
Heres how I got it bricked.
I changed my build.prop and I forgot to set the permissions to 644, then after shutting down my kindle, it did nothing but pop up to the gray screen and then straight to the black screen.
Same here, but mine seems to have lost root in the process: when I try to mount and chmod through adb, I get "Operation not permitted" and "read-only file system".
mithiirym said:
Same here, but mine seems to have lost root in the process: when I try to mount and chmod through adb, I get "Operation not permitted" and "read-only file system".
Click to expand...
Click to collapse
Exactly same here
wow
Sounds like Amazon locked up ecosystem just got them a pile of returns...
How many threads do we need on same basic subject...because somebody didnt listen the first time somone was walking them though something that they probably shouldn't have been doing to begin with...without days of research...let's have 5 threads one first page of general discussing bricks caused by prop build edits... And people complain because they can't find anything....... right now I believe typing skills are completely overrated because people's fingers are working faster than their eyes and their comprehension level... It's easier to type a question over and over again and expect individual independent attention that it is to read obviously.... Not pointing fingers at OP but the few of us that are here to help are stretched pretty thin over all these threads discussing the same thing....end rant. Try http://forum.xda-developers.com/showthread.php?t=2781665&page=3 post # 66
jimyv said:
Sounds like Amazon locked up ecosystem just got them a pile of returns...
How many threads do we need on same basic subject...because somebody didnt listen the first time somone was walking them though something that they probably shouldn't have been doing to begin with...without days of research...let's have 5 threads one first page of general discussing bricks caused by prop build edits... And people complain because they can't find anything....... right now I believe typing skills are completely overrated because people's fingers are working faster than their eyes and their comprehension level... It's easier to type a question over and over again and expect individual independent attention that it is to read obviously.... Not pointing fingers at OP but the few of us that are here to help are stretched pretty thin over all these threads discussing the same thing....end rant. Try http://forum.xda-developers.com/showthread.php?t=2781665&page=3 post # 66
Click to expand...
Click to collapse
Its no problem because my new replacement kindle is already here but I know there will be a method soon, thats why I made this thread to get some advice for MY problem.
Also if the first method didnt work for me , what would you expect?
Could you also read every word in my starting thread please?
sure
Ause said:
Its no problem because my new replacement kindle is already here but I know there will be a method soon, thats why I made this thread to get some advice for MY problem.
Also if the first method didnt work for me , what would you expect?
Could you also read every word in my starting thread please?
Click to expand...
Click to collapse
I'm glad you got your replacement ....
And like I said there are many threads here for the exact problem you had... Believe me you are not the only one that did this.. And now we have everybody that can help trying to chime in on 10 different threads to say the same thing to fix the same problems.. Your problem was not unique trust me. For example this thread was buried under at least 5 I brick my kindle threads and pushed to second page..read OP and last two page http://forum.xda-developers.com/showthread.php?t=2588608... The point is there was no clear answer at the time you were seeking one and you were inpatient you walked away from the think tank to seek yet more individual attention and so did a bunch of people. When all along you were getting individual attention back in the main thread when you made a mistake and forgot to do something.... So let's complicate the already difficult feet in finding information on this forum by burying them under repeat threads that info and clarity are patchy at best because anybody that can help is trying to be everywhere at the same time...end rant
I knew once people start touch the prop there would be a flood of brickings on the forum. BE CAREFUL WITH BUILD.PROP.
Even I bricked a rom slot messin around. If your unsure about something, DON'T TOUCH IT.
Words of advice.
:good:
Faznx92 said:
I knew once people start touch the prop there would be a flood of brickings on the forum. BE CAREFUL WITH BUILD.PROP.
Even I bricked a rom slot messin around. If your unsure about something, DON'T TOUCH IT.
Words of advice.
Click to expand...
Click to collapse
+1. I thought I did it NEasy way I used Rom manager lite to edit prop build just scroll down edit all lines properly reboot you don't have to mess with the permissions the application takes care of it...worked great. Probably could've used any prop build editing app.
Faznx92 said:
I knew once people start touch the prop there would be a flood of brickings on the forum. BE CAREFUL WITH BUILD.PROP.
Even I bricked a rom slot messin around. If your unsure about something, DON'T TOUCH IT.
Words of advice.
Click to expand...
Click to collapse
Or how about just don't touch the build.prop at all and wait for Hashcode to update Safestrap?
done
failed1234 said:
Or how about just don't touch the build.prop at all and wait for Hashcode to update Safestrap?
Click to expand...
Click to collapse
Moot,yet another redundant abandoned thread I assume. haven't heard back from op.if I had to guess I would guess another false warranty claim do to ignorance an impatients https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing this has gotten adb working for most people
jimyv said:
Moot,yet another redundant abandoned thread I assume. haven't heard back from op.if I had to guess I would guess another false warranty claim do to ignorance an impatients https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing this has gotten adb working for most people
Click to expand...
Click to collapse
I'd like to put out that your ranting isnt helping anything, maybe if you could be calm and just lead some people in a direction, everything can go nice, but no we have ignorant people like you that think they know all about knidles and stuff copy and pasting a bunch of links that dont work.
ok
Ause said:
I'd like to put out that your ranting isnt helping anything, maybe if you could be calm and just lead some people in a direction, everything can go nice, but no we have ignorant people like you that think they know all about knidles and stuff copy and pasting a bunch of links that dont work.
Click to expand...
Click to collapse
Well the last link that I pasted work for me and it has helped at least six other people get their ADB working again if you would read all the other brick threads I have helped several people . My thanks meter didn't go from 5 to 48 in a week just because of the rants I have been a member here for a couple of years now and I never posted anything until the last few months no questions no threads all I did was read read read and I have solved all my problems. And I am no developer a simple mechanic. I currently own three HDX, 2, 7 inch 1 8.9 one S4 still on MdK bootloader running KitKat a Tab a 3 10.1 a tab 3 7.0 a Moto razr m with a unlock bootloader that was done a year ago and a note 10.0 all of them rooted and custom and those are just me and my girls devices not including the children's there are also both tab 2 7.0 and NO BRICKS ( currently of course) not one time have I started a thread. Or even thought adout it with a question that has been answered or at least asked in several other threads. Before doing my own homework and my own research. I did not type my first word on this forum until last few months. So excuse me if I believe a person is responsible for doing their own homework and their own research before asking others of their free time to come rescue me. The only thing that doesn't work here apparently is the comprehension level. And the refusal or inability to follow directions. And the wishes for a 1 click answer which currently is not available for this device. Happy hunting ..... I didnt find all this links " that don't work " by not doing my own research. I was the first person back in the thread u broke ur device in... To successfully follow his original and vague Op...with success and no problems...so like in yo terms whatevea
jimyv said:
I'm glad you got your replacement ....
And like I said there are many threads here for the exact problem you had... Believe me you are not the only one that did this.. And now we have everybody that can help trying to chime in on 10 different threads to say the same thing to fix the same problems.. Your problem was not unique trust me. For example this thread was buried under at least 5 I brick my kindle threads and pushed to second page..read OP and last two page http://forum.xda-developers.com/showthread.php?t=2588608... The point is there was no clear answer at the time you were seeking one and you were inpatient you walked away from the think tank to seek yet more individual attention and so did a bunch of people. When all along you were getting individual attention back in the main thread when you made a mistake and forgot to do something.... So let's complicate the already difficult feet in finding information on this forum by burying them under repeat threads that info and clarity are patchy at best because anybody that can help is trying to be everywhere at the same time...end rant
Click to expand...
Click to collapse
jimyv said:
Well the last link that I pasted work for me and it has helped at least six other people get their ADB working again if you would read all the other brick threads I have helped several people . My thanks meter didn't go from 5 to 48 in a week just because of the rants I have been a member here for a couple of years now and I never posted anything until the last few months no questions no threads all I did was read read read and I have solved all my problems. And I am no developer a simple mechanic. I currently own three HDX, 2, 7 inch 1 8.9 one S4 still on MdK bootloader running KitKat a Tab a 3 10.1 a tab 3 7.0 a Moto razr m with a unlock bootloader that was done a year ago and a note 10.0 all of them rooted and custom and those are just me and my girls devices not including the children's there are also both tab 2 7.0 and NO BRICKS ( currently of course) not one time have I started a thread. Or even thought adout it with a question that has been answered or at least asked in several other threads. Before doing my own homework and my own research. I did not type my first word on this forum until last few months. So excuse me if I believe a person is responsible for doing their own homework and their own research before asking others of their free time to come rescue me. The only thing that doesn't work here apparently is the comprehension level. And the refusal or inability to follow directions. And the wishes for a 1 click answer which currently is not available for this device. Happy hunting ..... I didnt find all this links " that don't work " by not doing my own research. I was the first person back in the thread u broke ur device in... To successfully follow his original and vague Op...with success and no problems...so like in yo terms whatevea
Click to expand...
Click to collapse
Btw , that's not even including the sold six droid Razr's 2 droid x2 and I was a member at droidRazr.com for year prior ever joining this forum.. So as useless as you found my information I have got along just fine thank you. Just because I will not an expert and wasn't willing to hold your hand and spend hours typing all this stuff out personally I was referring you to perfectly good information that had work for me or have been known fixes for many others.. Don't blame me and my rants for your inabilities comprehend and follow directions.. Remember I am not the one that got in a hurry mess up my device and send it in for a false warranty claim due to my own negligence.
jimyv said:
Btw , that's not even including the sold six droid Razr's 2 droid x2 and I was a member at droidRazr.com for year prior ever joining this forum.. So as useless as you found my information I have got along just fine thank you. Just because I will not an expert and wasn't willing to hold your hand and spend hours typing all this stuff out personally I was referring you to perfectly good information that had work for me or have been known fixes for many others.. Don't blame me and my rants for your inabilities comprehend and follow directions.. Remember I am not the one that got in a hurry mess up my device and send it in for a false warranty claim due to my own negligence.
Click to expand...
Click to collapse
It would be better if you could stop with your rants, like forreal no one cares.
stop spamming peoples threads with useless rants
Ause said:
It would be better if you could stop with your rants, like forreal no one cares.
stop spamming peoples threads with useless rants
Click to expand...
Click to collapse
kinda like ur thread yo.
Apparently you are the only one that has been offended. My rants have been thanked more than your pathetic attempts at rebuttals no rant ,good day to you sir.
---------- Post added at 03:15 PM ---------- Previous post was at 02:59 PM ----------
Please close or delete thread Moderator per first rule of forum poster did not search before post several threads were started before this one with same problem..poster did not follow though to a productive result.. Therefore containing no useful information thank you.
Still having a problem that has not been solved in any other threads, I downloaded the QTSP 9008 driver and still nothing.
Please dont reply unless you have some helpful information
this has turned into something else but rants seem to happen because theres no progress
Calm your tits 's. I said it before and I'll say it again to everyone. Impatience = brick. Patience = knowledge. Don't rush it. Read up on what your doing to your $200+ electronic locked device. If you bricked it Amazon can unbrick it so return it. They don't lose a dime. If we're unlocked we will have more to offer but as of now it is how it is.:fingers-crossed:
help
Ause said:
Its no problem because my new replacement kindle is already here but I know there will be a method soon, thats why I made this thread to get some advice for MY problem.
Also if the first method didnt work for me , what would you expect?
Could you also read every word in my starting thread please?
Click to expand...
Click to collapse
how did you get a replacement? could you pelase tell me?
go to
dex101010 said:
how did you get a replacement? could you pelase tell me?
Click to expand...
Click to collapse
The Amazon site go to Kindle troubleshooting and it will show a place to leave your phone number if you would like them to call you they call you you answer you tell him it will not boot correctly and they will send you a refurbished unit. That is of course as long as it is not a black listed unit and you are the original purchaser so on and etc. or just be patient since you are the one that messed up your unit and do the responsible thing by fixing it yourself technically I would believe this would be a false warranty claim but do it at your own choosing and by the way they are making tons of project progress in the recovery of this device hopefully we will have something very very soon and you if you are still on the old firmware you may even get a full bootloader unlock.. Good luck whichever direction you do choose to go. just remember and heed the warnings on your next new device so you don't end in the same situation immediately like so many others here have done.
This will be a launching pad for tips and recommendations for members negotiating long threads and reading pertinent information. I read many posts with members stating that the thread is just too long to read. Then using that as an excuse for not reading at all. Please add your ideas and methods for reading.
The first thing I do when looking at a new thread is read the OP. I always check dates and also the date of the latest iteration of the ROM, kernel, etc. after reading what the author wrote about their thread I'll jump to the end of the thread and read backwards to the date of the latest release. This gets me up to date with the latest build and any issues.
Then I'll decide if I want to flash this on my very expensive device.
Like I said...
Please add on your tips!
Thanks!
RayMcGrath said:
This will be a launching pad for tips and recommendations for members negotiating long threads and reading pertinent information. Please add your ideas and methods for reading.
The first thing I do when looking at a new thread is read the OP. I always check dates and also the date of the latest iteration of the ROM, kernel, etc. after reading what the author wrote about their thread I'll jump to the end of the thread and read backwards to the date of the latest release. This gets me up to date with the latest build and any issues.
Then I'll decide if I want to flash this on my very expensive device.
Like I said...
Please add on your tips!
Thanks!
Click to expand...
Click to collapse
Hi...
The way you use to read a thread pretty much summarize the way I do it myself. I go a step further by searching within the said thread with some key words such as:
Problem, issue, brick, bricked, bootloop, etc...
I may sound paranoid, but I often browse the forum late at night and I could miss an important post due to being tired.
Cheers...
Great idea Ray. Teach by teaching, not by beating a person over the head lol
I go to the OP also and if I am interested in flashing, go back a month or two and read posts to see if things are stable or not. I also follow a bunch of Roms that I don't intent to flash or, have flashed before - just to see what kind of problems have arisen and how they were dealt with. It's a great way to pass a ride on the train or other idle time. I do think that there are many from around the world here and language might be a factor effecting their ability to read and/or search. Either way, I love this XDA, a valued tool! Too bad I came along so late in the game.
Bobbaloo said:
Great idea Ray. Teach by teaching, not by beating a person over the head lol
I go to the OP also and if I am interested in flashing, go back a month or two and read posts to see if things are stable or not. I also follow a bunch of Roms that I don't intent to flash or, have flashed before - just to see what kind of problems have arisen and how they were dealt with. It's a great way to pass a ride on the train or other idle time. I do think that there are many from around the world here and language might be a factor effecting their ability to read and/or search. Either way, I love this XDA, a valued tool! Too bad I came along so late in the game.
Click to expand...
Click to collapse
Great to have you. You're a big help to many folk.
5.1 said:
Hi...
The way you use to read a thread pretty much summarize the way I do it myself. I go a step further by searching within the said thread with some key words such as:
Problem, issue, brick, bricked, bootloop, etc...
I may sound paranoid, but I often browse the forum late at night and I could miss an important post due to being tired.
Cheers...
Click to expand...
Click to collapse
You're right!
Performing a search can be an art form. Using the just right keyword to be successful takes some practice. It is so important to try many paths and exhaust all possibilities before posting your question in the threads. And then phrasing your question with all your information is important as well.
RayMcGrath said:
You're right!
Performing a search can be an art form. Using the just right keyword to be successful takes some practice. It is so important to try many paths and exhaust all possibilities before posting your question in the threads. And then phrasing your question with all your information is important as well.
Click to expand...
Click to collapse
Well, since my first modded android phone in 2008, i have never felt the need of asking anything. Most likely because all issues I encountered were already covered. Either by developers or people answering issues reported by previous users having the same problems. And maybe because I like to get things done by myself. (Which I achieve 1% of the time ).
I check XDA almost every day since. I must say that the "reading thing" may sound challenging for some people. You'll ask me why?
What follows is about novice users for the most part who don't know about/how to use the search function. Try reading a thread where 100 users come each and every day writing the same thing about the same problem over and over. And over again...
Trying to find the relevant posts in-between all this mess is sometimes quite discouraging.
I'm lucky to have affinity with English and of course it's a lot easier to read and find infos when I need them. Google translate became really nice with time. Yet i find myself using it, since English is not my native language and I learned it the hard way. Sometimes it's sad to see people not using such a powerful tool.
People, please use the search function! Take some time to read. If you don't get it, use an online translator. :good:
PS: Hopefully I didn't derail too much from the OP with this post... I'll delete it if needed.
5.1 said:
Well, since my first modded android phone in 2008, i have never felt the need of asking anything. Most likely because all issues I encountered were already covered. Either by developers or people answering issues reported by previous users having the same problems. And maybe because I like to get things done by myself. (Which I achieve 1% of the time ).
I check XDA almost every day since. I must say that the "reading thing" may sound challenging for some people. You'll ask me why?
What follows is about novice users for the most part who don't know about/how to use the search function. Try reading a thread where 100 users come each and every day writing the same thing about the same problem over and over. And over again...
Trying to find the relevant posts in-between all this mess is sometimes quite discouraging.
I'm lucky to have affinity with English and of course it's a lot easier to read and find infos when I need them. Google translate became really nice with time. Yet i find myself using it, since English is not my native language and I learned it the hard way. Sometimes it's sad to see people not using such a powerful tool.
People, please use the search function! Take some time to read. If you don't get it, use an online translator. :good:
PS: Hopefully I didn't derail too much from the OP with this post... I'll delete it if needed.
Click to expand...
Click to collapse
From the beginning, searching for the answer - did someone else have the same situation and fix it(?) - THIS always seemed easier and more gratifying than waiting for someone to answer me on a thread
Actually, I was flashing macks ROM, then CM on my note 2 and I didn't even KNOW XDA existed. I was so grateful when I found it. Especially when I got this phone. With Google ai, now it seems so much easier to do a quick search on the web
Bobbaloo said:
From the beginning, searching for the answer - did someone else have the same situation and fix it(?) - THIS always seemed easier and more gratifying than waiting for someone to answer me on a thread
Click to expand...
Click to collapse
Yeah I know how you feel! At least for me having no real technical knowledge, I'm always glad to find the solutions by myself. Since it's around and just needs a search it's even faster than waiting for an answer. Also, since I only need to search when my phone is broken, I simply can't wait for someone to answer. Imagine no one replied during two days...
Bobbaloo said:
Actually, I was flashing macks ROM, then CM on my note 2 and I didn't even KNOW XDA existed. I was so grateful when I found it. Especially when I got this phone. With Google ai, now it seems so much easier to do a quick search on the web
Click to expand...
Click to collapse
This is the first place I found when I started to flash my HTC vision back in 2008. I started reading guides and development and was like: WTF these guys are cracking bootloader, carrier unlocking, etc... And all can be found so easily... :good: