Hello, my girlfriend recently bought a cheap, off contract, Wildfire. I quickly got home and tried rooting it, the lag was making me squeamish . I tried the unrevoked method but was met with "The device "bee" is not supported at this time". I did my research but only found really old threads. Since I'm a complete noob at this I decided to turn to your services to see if you could aid me accomplish root.
The phone is carrying android 2.2.1 and hboot 1.30
HBoot 1.30? Are you sure it is a Wildfire??
They had it labeled as the HTC dragon,yet when I asked the clerk he called it the HTC wildfire (He might have mixed up the names?). A quick search made me realize that both phones look alike. So now I'm left with an uknown phone lol.
In that case, I am pretty sure the applicable root methods will not work. What is the model number and details which are normally written under the battery? Also, what is the first line you see in HBoot? (Google shows HTC Dragon is the first device with a 1GHz processor which was later renamed and released as the Nexus One / Desire!)
Anyway, FYI, Wildfire's with 2.2.1 can be rooted using Revolutionary:
http://revolutionary.io/
But, I wouldn't try it out on another phone / a device it isn't designed for. It may just cause worse issues.
Sorry for the late replies, as I don't have the cellphone physically with me at the moment, and I'm also at work lol; Gf fetched the details for me, she wrote it as follows:
Phone Model: ADR6300VW ADR6225
Model: BTR6300B 3.7VDC 1300mAh 4.81Whr
Hboot: BEE DVT2 SHIP S-ON
It's a CDMA Wildfire? That's why it's different. I don't think HTC Bee's on 2.2.1 can be rooted ATM though. Also, there's no custom recovery for it yet.
Still a bit confused though, ADR6225 is indeed a code for the Bee (Wildfire), but I wonder why it shows ADR6300 which is actually a Droid Incredible...
I wonder if I can fight this, or report them to the authorities. I mean clearly they are using misleading ads (which from what I remember didn't even have the specs on, I had to do a quick google search) naming it the dragon, telling me the wildfire and then actually being a bee. Oh well thanks so very much for your help.
For the general end user (i.e. someone who just uses it as a phone), they are indeed the same, with the difference being that the Wildfire is a GSM device and the Bee is a CDMA device. But, because of that, their internals (esp. baseband) are different, which is why rooting and other modding stuff for these phones are completely different. Since the Bee is not so popular, there is hardly any stuff for it available ATM.
Well, good luck, hopefully you get things sorted out.
Related
Hi guys and gals
My mate got his HTC Desire about 4 days ago, he wasted no time in trying to root it but seems to have fu**ed up. According to his own words:
"I did the unlocker method (made the gold card), got into the boot loader but upon loading the custom and reboot I lost the screen. phone still works but no display, I am still trying various recoveries"
Has anyone had (or know of) any similar experiences? I been thinking about rooting my Desire but now I'm worried...not had mine long either.
Thanks!
DJ Anon said:
Hi guys and gals
My mate got his HTC Desire about 4 days ago, he wasted no time in trying to root it but seems to have fu**ed up. According to his own words:
"I did the unlocker method (made the gold card), got into the boot loader but upon loading the custom and reboot I lost the screen. phone still works but no display, I am still trying various recoveries"
Has anyone had (or know of) any similar experiences? I been thinking about rooting my Desire but now I'm worried...not had mine long either.
Thanks!
Click to expand...
Click to collapse
sounds like your mate has an slcd screen and tried to downgrade his device too an incompatible hboot (f it doesn't mention amoled on the box you have slcd). this is completely recoverable. although a little tricky - see:
http://forum.xda-developers.com/showthread.php?t=748498&highlight=brick
Cheers!
Thanks debully,
Will pass on your comments to my mate.
I must say tho, his experience has sort of freaked me out a bit. I am looking to root my Desire (I wanna be able to connect with a Wii controller) but am feeling a bit aprehensive now...
Go for it man.. I just bought my telus desire last tuesday and by the end of thursday I had rooted and flashed LeeDroid to it.. and havent looked back since. While some of the instructions may seem complicated, once you actually do it, it's really quite easy. I originally used unrevoked without the SLCD support, and it still works, just shows a black screen when doing the updates. Earlier today I re-flashed unrevoked with the SLCD support and switched to Cyanogen 6 RC2, and it was a walk in the park! The advanages of the custom ROMS (and 2.2) far outweigh the chance of a scare. And if you still feel aprahensible about it, just check out the howardforums.com telus HSPA forums, there is a post with a REALLY easy walkthrough, and several success stories for our specific model of the phone.
Thanks mikeandjaimie
i'm gonna go ahead and be a lazy bas**rd, could you please provide a link to this forum u speak of?
Thanks!
try to avoid over the air upgrades to froyo as this throws a nasty spanner in the works should you wish to get root afterwards. Lots of screen presses on a blank screen - not for the faint hearted. Stick with 2.1 and its quite a bit easier to root, then upgrade to froyo via a custom rom.
I only know this because I did an OTA update within minutes of getting out of the box, only to find that this has practically ruined my chances of rooting my device, for the time being at least, until some bright bugger finds a reasonable way round it.
debully said:
try to avoid over the air upgrades to froyo as this throws a nasty spanner in the works should you wish to get root afterwards. Lots of screen presses on a blank screen - not for the faint hearted. Stick with 2.1 and its quite a bit easier to root, then upgrade to froyo via a custom rom.
I only know this because I did an OTA update within minutes of getting out of the box, only to find that this has practically ruined my chances of rooting my device, for the time being at least, until some bright bugger finds a reasonable way round it.
Click to expand...
Click to collapse
I hear you mate. I updated my Android OS to Froyo 2.2 almost on the same day I got the phone. However there are some guides on how to downgrade your Android OS to 0.83 or lower before rooting it so I'll be giving it a try shortly.
Please let me know how you get on and save the links to the guides you use - if you don't mind.
Good luck
Sent from my HTC Desire using XDA App
I know it was only released yesterday, but I know nothing about the current Desire models. I come from the realm of CDMA Hero's and am moving to the Samsung Epic. My brother just picked up a desire and wants to root it.
Is the current Desire a GSM or CDMA phone?
And has anyone who has gotten the new USC Desire, have you tried the current root method to see if it works. I have doubts that it will.
I am going to assume after looking through this forum a little bit that the current model being developed for here is GSM.
The US Cellular Desire is the first CDMA phone to be called "HTC Desire". Tread carefully. But please also report any positive/negative results so that others can learn from your win/fail.
cmstlist said:
The US Cellular Desire is the first CDMA phone to be called "HTC Desire". Tread carefully. But please also report any positive/negative results so that others can learn from your win/fail.
Click to expand...
Click to collapse
Thankfully I am pretty Android savvy. I just wasn't sure if it was CDMA or GSM - No radio updates for this phone .
If the current root method does not work I will attempt the ones for other devices running 2.1 and might even try the new EVO/Epic root for 2.2.
I'll get this thing rooted if I have to find my own.
Kcarpenter said:
Thankfully I am pretty Android savvy. I just wasn't sure if it was CDMA or GSM - No radio updates for this phone .
If the current root method does not work I will attempt the ones for other devices running 2.1 and might even try the new EVO/Epic root for 2.2.
I'll get this thing rooted if I have to find my own.
Click to expand...
Click to collapse
I can't wait to get my US Cellular Desire and I'm really hoping for root. Let us know if you have any luck.
So what are the actual chances that it will work on the uscc desire? I got mine so I guess ill just have to try it tonight.
The us desire has a bootloader 0.98.xxxx you will have to downgrade to a different hboot plus I'm pretty sure all the roms only support a gsm radio.
Odd_Sam said:
The us desire has a bootloader 0.98.xxxx you will have to downgrade to a different hboot plus I'm pretty sure all the roms only support a gsm radio.
Click to expand...
Click to collapse
Again, tread with caution... if a different HBOOT bricks the phone... there's not much recourse!
From what I have read/observed, the USCC Desire is basically the same phone as the Nexus One. I would like to know what is different about this thing that would prevent me from rooting and/or upgrading to 2.2.
Anyone have any advice? I can't wait to upgrade this piece.
CreepingDeath said:
From what I have read/observed, the USCC Desire is basically the same phone as the Nexus One. I would like to know what is different about this thing that would prevent me from rooting and/or upgrading to 2.2.
Anyone have any advice? I can't wait to upgrade this piece.
Click to expand...
Click to collapse
Well, Desire is CDMA. Nexus one is not. completely different cellular radio HARDWARE. and that pesky slcd is also a problem.
Gonna have better luck adapting a cdma android root. (incredible, evo, etc..) at least they use the same radio technology.
i thought the incredible was supposed to get the slcd also...... that would help alot.
I know this doesn't provide any technical information, but just as an FYI I did ask HTC what their policy on rooting is. They said:
"Of course the Desire is your phone. If you would like to root the phone or install 3rd party software to it, you are more than welcome to. It's just that with any 3rd party software, HTC did not create it so we do not have information on how it works therefore, we can not support it. As far as voiding any warranties, I do not have that information. You may contact our Warranty Deparment at 1-800-229-1235 (8:30 AM - 5 PM EST M-F). They will be able to verify that information with you. HTC has repaired some phones that had the incorrect ROM on them. There may have been a fee for this, I am not certain."
I hadn't gotten around to calling about the warranty. I had read elsewhere that as long as the damage wasn't a result of the rooting that they would still repair a rooted phone under warranty, but I don't know if there's any truth to that.
Anyway, I don't know if this helps alleviate any concerns about experimenting with it or not. I had gotten as far as making a gold card for it yesterday, but I'm kind of afraid to go any further until I can get some more information on this specific phone. I feel like there may be a chance with this method since it takes information from your actual device. Anyone have any thoughts on that?
psychache said:
I know this doesn't provide any technical information, but just as an FYI I did ask HTC what their policy on rooting is. They said:
"Of course the Desire is your phone. If you would like to root the phone or install 3rd party software to it, you are more than welcome to. It's just that with any 3rd party software, HTC did not create it so we do not have information on how it works therefore, we can not support it. As far as voiding any warranties, I do not have that information. You may contact our Warranty Deparment at 1-800-229-1235 (8:30 AM - 5 PM EST M-F). They will be able to verify that information with you. HTC has repaired some phones that had the incorrect ROM on them. There may have been a fee for this, I am not certain."
I hadn't gotten around to calling about the warranty. I had read elsewhere that as long as the damage wasn't a result of the rooting that they would still repair a rooted phone under warranty, but I don't know if there's any truth to that.
Anyway, I don't know if this helps alleviate any concerns about experimenting with it or not. I had gotten as far as making a gold card for it yesterday, but I'm kind of afraid to go any further until I can get some more information on this specific phone. I feel like there may be a chance with this method since it takes information from your actual device. Anyone have any thoughts on that?
Click to expand...
Click to collapse
Once you make a gold card, which rooting technique are you going try? Unrevoked is the simplest overall but I think HBOOT 0.98 fixed the exploit that Unrevoked uses.
I tried unrevoked the other day and it said that it was unsupported. I don't know that I'll go as far as trying to root at this point. I was kind of hoping that someone else would try it first, ha . . . Initially I was doing the gold card just to see if I could at least unbrand it so I could install the OTA update. But then I run into the original issue of whether or not it supports CDMA and/or SLCD. Is there any way to tell aside from actually attempting to flash it? Maybe it would be safer to try one of the methods for the Incredible? Not sure what version of HBOOT that has on it. Honestly, I'm pretty far from being any kind of expert on this. So far I've only had experience with rooting the Moto Droid and that was pretty much cake since the phone is so old at this point.
psychache said:
I tried unrevoked the other day and it said that it was unsupported. I don't know that I'll go as far as trying to root at this point. I was kind of hoping that someone else would try it first, ha . . . Initially I was doing the gold card just to see if I could at least unbrand it so I could install the OTA update. But then I run into the original issue of whether or not it supports CDMA and/or SLCD. Is there any way to tell aside from actually attempting to flash it? Maybe it would be safer to try one of the methods for the Incredible? Not sure what version of HBOOT that has on it. Honestly, I'm pretty far from being any kind of expert on this. So far I've only had experience with rooting the Moto Droid and that was pretty much cake since the phone is so old at this point.
Click to expand...
Click to collapse
There's only one set of RUU that support CDMA at this point. Pretty much any other attempt will brick your desire. You could try one of those RUU's and see if it downgrades where you could root then.
Yeah, I think I'm going to wait until some sort of tested method is worked out. I'm not at any kind of skill level to be figuring this stuff out on my own. Overall I'm pretty pleased with how the phone worked right out of the box. My only major complaint is the lack of internal storage for apps and the fact that you can't remove any of the preinstalled crap. This is the only reason I was really even looking into rooting or unlocking at this point. I just hope that the fact that the EVO and Incredible got their updates means that one can't be far off for the Desire.
psychache - I feel ya there. I got mine and I love it. However, was kinda skiddish on testing on this new unit. Whether or not the insurance would cover it if I bricked it. Even then, would still be another $100 deductible.
I am willing to try something. I already tried the Universal Androot to no avail... no brick or anything, it just didnt take.
Well, if anyone else is up to the challenge you could always call the number I posted above to get a definite answer on whether you would still have coverage if you did brick. I had actually had several replies back and forth with them before I asked specifically about rooting and was very impressed by how responsive and open-minded they were. I'd say of any of the manufacturers they're probably the most likely to be "cool" about it. And you're right, primerorico, worst case scenario is you could do an insurance claim and pay the $100 (you know, because you "lost" it). I know that's not cheap but it's a heck of a lot less than paying the full retail for a new one. Just food for thought for anyone who actually knows what they're doing . . . (unlike myself)
Someone has made some progress in rooting. Not sure if he needs some help but here is the thread: http://forum.xda-developers.com/showthread.php?p=7917553
heavymetalmage said:
Someone has made some progress in rooting. Not sure if he needs some help but here is the thread: http://forum.xda-developers.com/showthread.php?p=7917553
Click to expand...
Click to collapse
Thanks for the link. I'll definitely keep an eye on it.
Hi Everyone, this is my first time here in this section of XDA developers, but I have an interesting situation.
I recently acquired the Merge (Verizon's G2 variant that is still in limbo) and I'm thinking of rooting it. I have tried the instructions on the wiki for gfree 02, but it seems that as soon as I enter adb shell and type in su, I get permission denied. I read the wiki for hot to use gfree and also how to install adb but I have not been able to find an answer.
I'm trying to get the merge SIM unlocked and because this is the first android phone I have ever owned, I would really like to be able to use it on AT&T's network. Anyways, I would like to get some help as to why I am getting the permission denied response when I did everythng as the gfree wiki said to do. Is it possible that the merge is so internally different that gfree will not work on it even if it's a variant?
It's GSM coming from verizon?
If you're trying to use gfree to gain s-off, I would HIGHLY recommend running it with the "-s" flag (no quotations) just to be on the safe side
Even then, I still wouldn't recommend running gfree on the merge as it was made to gain radio s-off on the htc vision.
I would suggest using the rage method for now for root. See if that works.
Sent from my HTC Vision using Tapatalk
@ ratchetrizzo: no, it's just a world phone version for verizon users to use in different countries
@ Pancubano: So you would recommend against using gfree on the merge then? I'm trying to learn how to perform this rage method, but I have no experience in android whatsoever so even while reading the wiki, it seems there are a few things that are omitted or assumed that is common knowledge. By using the rage method, will I be able to achieve sim unlock status?
p.s thanks for replying!
The problem is, the merge is a CDMA device, so I'm pretty sure the sim unlock that gfree achieves with our HTC Vision's would not work on the merge. It involves copying partition 7 (on our phones) and making various hex edits to set the secu_flag to 0, supercid to 11111111 and simunlocking the phone, then copy's the modified partition back to the phone. All of which is taken care of by gfree.
Of course in order to process all of this, you're going to need at the very least temp root first, so, I would highly recommend doing more research into the rage method, but, do not try the gfree method yet, as I can't truely confirm if it will work with the merge with just the "-s" flag.
Sent from my HTC Vision using Tapatalk
"Rooting the Merge" sounds dirty...
You might actually have more luck in the HTC Evo Shift 4G subforum - that's Sprint's version of the G2 (more or less), and thus the internals are more likely to be similar to the Merge than the G2 would be.
the orange bandit said:
You might actually have more luck in the HTC Evo Shift 4G subforum - that's Sprint's version of the G2 (more or less), and thus the internals are more likely to be similar to the Merge than the G2 would be.
Click to expand...
Click to collapse
Actually the merge is closer to the G2/DZ than the Shift 4G, right down to the keyboard and hinge, although I see the point since Sprint is CDMA although this phone is CDMA/GSM
well, thanks for everyone's attempt to help, but I finally realized that Verizon is evil and even if I unlock it, it'll simply be on 2G (EDGE) so there's no point of me having it.
EDIT: so I sold it to someone who is on verizon and will take care of it.
how did you get a hold of one? for some reason i dont believe you even had it from the start, haha. because it hasnt been released yet, and you must of been lucky enough to get an early production version.
I got it from a reviewer of the merge when it first came out. The mod who had it decided to sell it so i took a chance and bought it from him. After trying to unlock it, I finally gave up and because I got a leery of rooting it.
believe me or not, I had it, got to test it out, and finally had to give it up.
check htcmerge.com if you don't believe me. My username is the same as it is here.
EDIT: btw, why would I post this if I don't have it? It seems idiotic for me to post a thread asking for help on a phone that does not technically exist. No, I do not care for the attention. I was tempted to root it but as I said, I simply chickened out.
mputtr said:
I got it from a reviewer of the merge when it first came out. The mod who had it decided to sell it so i took a chance and bought it from him. After trying to unlock it, I finally gave up and because I got a leery of rooting it.
believe me or not, I had it, got to test it out, and finally had to give it up.
check htcmerge.com if you don't believe me. My username is the same as it is here.
EDIT: btw, why would I post this if I don't have it? It seems idiotic for me to post a thread asking for help on a phone that does not technically exist. No, I do not care for the attention. I was tempted to root it but as I said, I simply chickened out.
Click to expand...
Click to collapse
Okay okay, its just a lot of speculation about this phone has been floating about and I didn't believe you. How did it run?
Sent from my HTC Vision using XDA App
It ran as well as the G2. What I did like alot was that unlike the evo shift 4g, the slider mechanism is spring loaded so it snaps upwards. the battery backing is odd since you have to pry the bottom part then unhook 2 minihooks on the side.
The heft of it is probably heavier than the G2, but it feels good in the hand and doesn't feel like it will slip at all.
Most of all the design is amazing!!
I definitely like the feel of the physical build. It feels tough, sturdy, and simply a phone that a man should have.
I think I might have only 1 gripe and that it's still stuck with bing since the one I bought was the Verizon version. (this was before the rumor that it was pulled back to be fitted with 4g).
In the end, I had to give it up, because I am on AT&T and verizon will never let their phones work on any carrier but theirs.
anyone been able to root a merge? I just got a merge. Didnt know about the phone beforehand and am using it on gsm(it is a worldphone). Once i got home and googled around and checked these forums... its still not released apparently :s so anyone have any idea on how i can root it?
[reposted from wrong thread]
Hey all, I was thinking of getting a g2 after my contract is ready for it, and ive got a few questions. I'm not really a noob to all this rooting and cyanogen mod, so i might understand some of the technical jargon. i've rooted my g1 with cyanogen 5.0.8
If you use visionary to temp-root your phone daily, is there any chance for bricking it? Are there are any known problems with using visionary?
what are the main benefits with getting permaroot as opposed to just temp rooting it everytime? im not that interested in roms like cyanogen, gingervillan,etc
can you use setcpu with the stock tmobile g2 rom?
is the hinge really that bad?
does tmobile really monitor tethering? some say that the original g1 plan includes tethering but that just sounds absurd.
what exactly does busybox do? i have asked this several times but havent gotten a clear answer; i know that it has to do with linux, but thats about it :/
theres a section on the wiki about g2 radios; i dont understand what is the problem with the stock radio and why someone would want to flash another one besdies for the reason of getting a better signal, but this leads me to the question of 'doesnt tmobile update the radio? why would we need to manually update radio'?
what are the main differences between using visionary temp to permaroot and the adb method? if i were to use the visionary one, at what point could i enable s- off and hboot?
that being said, is there any news about a new release of visionary?
can't people just ask tmobile for a sim unlock code after 1 year? why do we have to root it and do it?
Looking at the wiki, i dont understand what md5 is when the wiki provides downloads and what it means
what is hboot used for and whats the difference between that and a bootloader (whats a bootloader btw)
can both temp rooting and both versions of permarooting work on 1.19 and 1.12?
thanks!
kayway27 said:
[reposted from wrong thread]
Hey all, I was thinking of getting a g2 after my contract is ready for it, and ive got a few questions. I'm not really a noob to all this rooting and cyanogen mod, so i might understand some of the technical jargon. i've rooted my g1 with cyanogen 5.0.8
If you use visionary to temp-root your phone daily, is there any chance for bricking it? Are there are any known problems with using visionary?
what are the main benefits with getting permaroot as opposed to just temp rooting it everytime? im not that interested in roms like cyanogen, gingervillan,etc
can you use setcpu with the stock tmobile g2 rom?
is the hinge really that bad?
does tmobile really monitor tethering? some say that the original g1 plan includes tethering but that just sounds absurd.
what exactly does busybox do? i have asked this several times but havent gotten a clear answer; i know that it has to do with linux, but thats about it :/
theres a section on the wiki about g2 radios; i dont understand what is the problem with the stock radio and why someone would want to flash another one besdies for the reason of getting a better signal, but this leads me to the question of 'doesnt tmobile update the radio? why would we need to manually update radio'?
what are the main differences between using visionary temp to permaroot and the adb method? if i were to use the visionary one, at what point could i enable s- off and hboot?
that being said, is there any news about a new release of visionary?
can't people just ask tmobile for a sim unlock code after 1 year? why do we have to root it and do it?
Looking at the wiki, i dont understand what md5 is when the wiki provides downloads and what it means
what is hboot used for and whats the difference between that and a bootloader (whats a bootloader btw)
can both temp rooting and both versions of permarooting work on 1.19 and 1.12?
thanks!
Click to expand...
Click to collapse
This late in the game jsut wait for the next wave of phones some will has dual core
Sent from my HTC Desire Z using XDA App
Might even see quad core by the end of the year.
Sent from my Liquid Metal using XDA Premium App
sorta didnt answer my question, dont mean to sound ungrateful;
i want the g2 b/c of the keyboard and other asthetics; dual core isnt that big of a factor for me.
As others have said there will be new phones coming out soon, faster processors, more cores, more megapixels, etc.
Another thing to consider is that I would expect new phones from T-Mobile to have radios capable of operating on AT&T's 3G network, making them more future proof.
OTOH If you are a keyboard guy I would expect these to be less and less common, as a former G1 user myself I can tell you the G2 keyboard is quite inferior to the G1 and thanks to better soft keyboards like Swype I rarely use the hardware keyboard anymore.
Also I can certainly sympathize with wanting to upgrade from the G1, the G2 is unbelievably more snappy, I don't think could go back to the G1 again.
One other option is to look at picking up a used device off Swappa (something like a MyTouch 3G Slide) to hold you over until the new hotness comes out later and renew your contact then.
BusyBox is a set of Linux tools that is pretty much essential for a rooted Android phone.
I have never heard of using Visionary only for temp rooting causing any problems, it only gets dicey if you try to use it for permanent root.
As for advantages of permanent root over temp root, I guess in your case it's mainly a matter of convenience, though I found some rooted apps don't behave properly with Visionary temp root.
I haven't heard anything about a newer version of Visionary and I don't think I'd expect one.
The gfree method isn't too difficult once you have ADB working, I'd just do that.
Sent from my T-Mobile G2 using XDA App
I'm no expert but I'll try to answer some things. As for temp rooting, Visionary appears to be relatively safe, but many people warn of using it to perm root as there's a good chance of bricking the phone. It just seems to be less of a hassle to perm root and be done with it. The gfree method seems to be the one that is least risky. I have yet to root my G2 but will probably follow a method that uses Visionary for temp root and gfree for the perm part.
As to the radios, there is often no need to flash a new one and its generally advised NOT to unless you have a very good reason and know exactly what you're doing. The hinge can be bad on some G2s, not so bad on others. Mine is on the loose side but its not really a big deal to me. I can post the link to the "Easy Root" thread if you like. There are a lot of posts from people who used it and have yet to see a reported failure. I'm trying to steel myself up to go through with it. Just wanna have everything in line.
A lot of people it seems are saying wait and don't bother with the G2. Not so sure. It's an awesome phone if you like a physical keyboard. It's plenty fast and capable, even more so when rooted. Playing the technology waiting game is pointless, IMO. There is ALWAYS something bigger and better right around the corner. Everyone is touting the current wave of dual core phones, and soon those will be kicked aside by the tech elites in favor of quad core phones, then THOSE will be swatted aside when something else comes along. Android phone technology is moving faster than any tech I've seen so I think it's better to find a phone you like and chill. So what if some dude you know has a dual core phone? That fact doesn't make a phone like the G2 suddenly slow and incapable. Sure, relatively speaking it's less powerful but that's technology for you. I say if you find a phone you really like, jump on it.
Hi folks
I'm so new here, it took 3 days to find the "thank" button (had to turn off some scripts in browser)
I would be grateful if folks would indicate where to put what posts (subjects, questions), what NOT to post (I suspect I might be speaking "taboo" words) I am a tad autistic, we can be rude without meaning to be. But I been building PC's since '1989, piddling with Linux since mandrake 7, so the good news is CAN read the "destructions" and I know how to use IRC just a bit, on the PC (post code to pastebin, and such)
I'm an old biddy. So old I can remember when a landline "Caller ID" was called a "Snitch-Box". I have grudgingly accepted that wireless phones must send THEIR OWN meid over an unsecure radio in order to work. This was due to happy discovery of pre-paid carriers that don't require MY DNA in order to accept my money. Prior to that epiphany, I totally hated the cellphone concept ... Not Secure. In order to activate the "device", ever, it must first be SECURED.
I *did* lurk around many weeks before diving in with the barage of questions... With the help of the tutorials here, have managed to survive a couple of "brickings" and even got a ROM into my phone :victory:
First -- about me poor "Labaratory Rat" device. Can't really call it "phone" coz it was a "brick" when I got it. My friend dropped it in the sink and thot it was dead, gave it to me with a collection of scrapped CDMA phones. Dried it out in dessicant on the hot H20 heater, and to my surprise resurrection! Trouble was, I had revived a very unhappy 'device'. Crammed full of bloatware, [solved with Cyanogenmod ROM] and still has some "firmware" issues. I am simply trying to restore the "device" to CLEAN, NAKED, OPEN source, before I decide wether it's practical for telecommunication use.
It has an acceptable camera, I enjoyed using it to play music, I didn't really see a need to do anything to it till I found I couldn't load a paid tutorial APP for my class.
I can make a PC poop a popsickle and then carve you a tiny rosary outa the stick. I'm so old I can remember moving "DIPP" switches on a motherboard to clock a CPU. I'm VERY CERTAIN the firmware issues can be cleaned up.
OK, so what I have here:
BRAVOC DVT2 SHIP S-OFF
HBOOT-0.98.000
TOUCH PANEL-SYNT0101
RADIO-2.05.0.11
Jul 5 2010:19:14:11
The good news being it's got a fast little processor and 512K ram (I can remember running autocad on 512K, it's usable) The bad news is it was probably thrown away because the carrier (US Cellular) has shipped it with root-kit (Of course, autistic person cannot understand why anyone would pay for a "device" that has a built in Root Kit) I know, the carriers offer the hardware for free, Like "Here is some free cheese = MOUSETRAP"
Managed to get 4ext recovery touch v1.0.0.5 RC9 testing in there.
I like it ALOT better without "Sense" (Cyanogen 7.2 is what's in there now)
I can see that the Android-ness is very much like Linux, which I "grok", it appears that "hboot" is the Android equivalent of "grub"?
And I am guessing that the "root-kit" is living in this HBOOT (I've noticed that the 98 series seems limitted to US Cellular shipped HTC's)
From the looks of it, I'm gonna have to learn to "build" (again -- and I only did it a couple times way back when) to fix this? since I see there's some very nice ROMs folks are running on this phone, but I don't need the "Sense" part?
Moderator, please move my post if I'm in the wrong place. I honestly cannot find where the "Un-ROOTKIT my BravoC" section is. Or maybe point me toward the discussion of how to make/build/install this HBOOT?
Thanks in Advance
Virginwidow
Thanks in advance