i found a samsung s8000 jet at 199€ and was wondering whether i'd be able to install android on it
i found it has a good 800mhz cpu and it has anything u can ask nowadays apart from the best os avaiable today
any chance ?
Well AFAIK it is possible, but it would take a long time to accomplish (talking about years)
If the Jet was windows mobile, it'd be a lot easier (would still take lot of time)
u know what
my girlfriend wants a Gphone at a reasonable price but still can't find it here in italy.
i really don't understand where the problem is since linux is usually installable on any device
that's very odd
Yeah well the kernel needs to be completely rewritten to fit the hardware.
One different processor already makes a lot of trouble.
Sorry for digging up a dead topic, but, I have come across a way to get Android onto the S8000. I figure it was either that or let the phone get dusty in a drawer somewhere.
Just its not exactly a usable system as yet. None of the phone functions work, there are many Force Closures, the touch screen isnt really sensitive enough for Android either (although things can be scaled up to a larger size, normal presses get misunderstood for long presses), Cant access battery info, screen lock freezes phone, cant read time, etc etc etc. There are many things it cant to but its still an accomplishment to have it to a bootable state.
It does connect to wifi now, and has potential as far as I can tell, but, time will tell.
Still, it was fun to install onto my Jet after upgrading to Galaxy S.
I've only been playing around with it for a day. The project that is trying to get it functional is called JetDroid.
Just goes to show that Samsung could have made the Jet into a really good phone. If a semi functional install can work from people who program it in their own spare time, imagine how optimised Samsung could have gotten it.
Hey All,
Pardon this fundamental query. Just looking for basic layman's counsel. I've had a Sprint TP2 for under 1 year; it's the best I can do on my $30 SERO plan without paying more for access to newer phones. I've been basically content, as I only use it for texting, email, GPS/Google Maps, light occasional web surfing, and music --> bluetooth FM transmitter --> car stereo (plus the rare actual phone call. I actually hate talking on the phone, but sometimes ya gotta just do some talkin'). I had the first TP before this, and I did flash it other ROMs, although I was never 100% convinced that there was much real improvement. I've noticed that the GPS is consistently inferior on the TP2 than it was on the original TP; it can never pinpoint my locale with any greater accuracy than within about 1/4mi, which is kinda ridiculous. The TP got me within a few hundred feet. I figure this is a hardware issue, though, as I've never found a .cab or app that can fix that on the TP2.
So, the TP2 can be a tad sluggish, sometimes a tad buggy, but it gets the job done. I recently took a trip to Florida (from CT) and my phone completely stopped working; froze up, lost track of time, couldn't get into SD card, couldn't get online -- nothing. Took it into Sprint and they wiped and reinstalled everything, now it's back to normal. I bought it used on eBay after all, and turned off the insurance within a few months, so I'm on my own; Sprint won't replace or do anything if I brick it or if anything else happens.
I'm about to get a 7" Android 2.2 tablet that I intend to use for web/games/GPS/movies, and will install a .cab on the TP2 that hopefully allows me to use it as a wifi hotspot. Other than that, I can't see much real need to do any tinkering, but there's this whole world of excitement around custom ROMs and Android, and so I have to ask -- is it mainly for techie satisfaction, or are there genuine gains to be made? Could my TP2 really be made into a better device even for my simple purposes? Would flashing make my GPS work better, my music sound better, my 3G or wifi web experience faster, or my general OS more stable while traveling? Will it make my device live longer?
I don't mean to question the very raison d'être of the culture that abounds on this and other sites. Just wondering if y'all think its necessary for a guy like me to go messing with this stuff.
So I just recently got a Transformer rather unexpectedly which left me without much prior research done. Had taken a glance at some modifications like the ability to use 3G dongles and so, but little beyond that. As such, trying to go through the available ROMS and stuff I'm finding myself pretty overloaded with information and not quite sure where to start.
First of all, if there is some kind of already made "Dummies guide" about all the TF101 has to offer in terms of mods, ROMs, basic guides, so on, do please me link me.
Failing that, those were the kinds of things I was looking for.
Information in how to backup my current ROM, or if there's the possibility to easily install an official one. My only previous experience with Android is a Galaxy S where such was pretty straight forward, so not sure if I should take more precautions with the TF or not.
Best ROMs, pros and cons. Nothing in too big detail, mostly seeking what are the hot ROMs of the moment and what are their most beneficial features and cons if any. Rest I'll try to look into the ROM thread itself.
Modifications that might be helpful like the 3G thing or any other important mod.
Also, not so much on the software front, accessories. I got the version including the dock so there was no gift cover for the tablet or anything.
Are there any well recommended covers for the tablet and tablet+dock combo?
What about the data/charger extension? I find that the included cable is rather short and it really has no reach for the power socket if I have the tablet resting on my desk.
Appreciated for all the help that can be offered.
I can only really speak about 1 ROM but I have fallen in love with it. I rooted and flashed the TF on Day 3. It now runs HD Revolution 2.3.0 and I love it. Days 1-3 I noticed that the TF would be a little sluggish from time to time. Now with HDR it is silky smooth. My battery life also seems to have improved by 30-40%.
The rooting and flashing process was simple and the CWM method of flashing from a zip on the SD card in recovery mode is supper simple. You can even make backups there before you install anything.
One thing... do not update the TF till you read all the Rooting and Flashing threads you will need 8.6.5.19.
Root and have fun.
PSA: *This will be crossposted in xda HTC One X and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!
Hi xda,
So I'm trying to sell my used google pixel -- 120gb (mint condition.)
The thing is -- that It's essentially brand new in terms of usage, it sat on my desk used sparingly for many months due to getting busy with life and
purchasing two phones with only meaning to keep one. And now that I want to sell it, I want to be able to convey that in my Swappa posting that its essentially more 'new' than the manufacturing date may imply.
Is there any statistic that Android carries onto the hardware/bios of the phone that cant be wiped/reset without some difficulty, that can serve the same purpose of an odometer in a car? (Or another example -- when you sell DSLR's used on the open market they often post things like 'shutter click count' sort of stats, to indicate the 'mileage' on the body of the unit).
I've looked into battery cycles but so far found nothing solid, hoping more android pro's know something that can help~!
Also ive looked into battery specific apps, but most seem to ask for root access, and while I can root it, I think some sellers might not prefer it, especially if it'd be only for the purpose of finding one or two statistics. Any other way, or are such stats essentially meaningless on android?
thanks!!
you could just say that it hasnt been used much. honestly, whats more important is how much warranty is left on the phone, especially the pixel since many of them have hardware issues popping up.
The only thing I've seen that comes close to what you're asking for i had on my galaxy s6. It was phone info Samsung app and it gave all kinds of info about the device including how many times the charger had been plugged in as well as the headphone plug. Mine had been plugged in what seemed like a ridiculous amount of times. I think it was well over a thousand, not sure how that's possible. I don't have root now so I can't get that stat out of it anymore. Not sure if there is something similar for other phones.