I spent the morning in the AT&T store because I've been having problems, so I was hoping they'd switch my phone out. Instead, they sent me back home and emailed me with this link - *I can't post the link because I'm a new member* It's a link to the youtube video that she told me to use.
The lady told me to just "follow" those instructions so I can update to 2.3. Well ... I can't seem to get it to work? No matter what or from where I try to download the package files, it just doesn't work.
I updated my phone from 2.1 to 2.2 fairly easily, but this is just proving to be incredibly difficult.
Can somebody help the clueless noob out?!
Wow. ....
Sent from my SAMSUNG-SGH-I897 using xda premium
b-eock said:
Wow. ....
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
"Wow." yourself.
I came here for help, and instead, you're a jerk about it. Way to be mature.
Simple answer, as far as I know, is this:
Unless you're on the Rogers network, at this point, there isn't an official upgrade to 2.3 (so no Gingerbread on AT&T). It seems that the person at the store may have given you some misinformation, or else AT&T has been doing an exceptional job of keeping a secret.
Either way, my suggestion would be to either return to the store and speak to someone else about your issues, or if you feel comfortable, check out some of the great custom roms on this site.
There is no ATT release for Gingerbread. What video is it? Just post the link we can copy paste it? or pm me the link
LOL he beat me to it.
jmtheiss said:
Simple answer, as far as I know, is this:
Unless you're on the Rogers network, at this point, there isn't an official upgrade to 2.3 (so no Gingerbread on AT&T). It seems that the person at the store may have given you some misinformation, or else AT&T has been doing an exceptional job of keeping a secret.
Either way, my suggestion would be to either return to the store and speak to someone else about your issues, or if you feel comfortable, check out some of the great custom roms on this site.
Click to expand...
Click to collapse
Thank you for actually answering me.
So then all these threads, youtube videos, etc, that I'm seeing all over the internet - none of them are AT&T customers? Then what the heck was that customer service rep talking about?!
What a waste of my day!
Thank you again. I guess I'll be going back up there.
prbassplayer said:
There is no ATT release for Gingerbread. What video is it? Just post the link we can copy paste it? or pm me the link
LOL he beat me to it.
Click to expand...
Click to collapse
Go to Youtube and the title of the video is "How to Update Samsung Captivate with Gingerbread 2.3.3" by johnnythegeek1
I can't post the direct link - literally. The forum won't allow me. I don't have enough posts yet.
It appears that the video you're seeing is someone walking people through how to flash stock Gingerbread (which is still leaked Gingerbread, nothing official). I'm a little surprised that the AT&T rep pointed you to doing that, as it (technically) voids your warranty and they could potentially be held responsible if something happened.
As far as the videos you're seeing, they are probably AT&T customers - it's just that they're flashing leaked/non-official AT&T Gingerbread that came from Samsung.
jmtheiss said:
It appears that the video you're seeing is someone walking people through how to flash stock Gingerbread (which is still leaked Gingerbread, nothing official). I'm a little surprised that the AT&T rep pointed you to doing that, as it (technically) voids your warranty and they could potentially be held responsible if something happened.
Click to expand...
Click to collapse
Yeah, I said the same thing when I was talking with a friend.
So ... it's "technically" out there, yes? It's just the leaked, unofficial version? My one year warranty expires on 10/10/11. The rep told me that I needed to update to the most recent version (the 2.3) before they'd replace my phone out (again) and see if the update fixes it.
I think I'll just take it up to a different store.
thenewnoob said:
Yeah, I said the same thing when I was talking with a friend.
So ... it's "technically" out there, yes? It's just the leaked, unofficial version? My one year warranty expires on 10/10/11. The rep told me that I needed to update to the most recent version (the 2.3) before they'd replace my phone out (again) and see if the update fixes it.
I think I'll just take it up to a different store.
Click to expand...
Click to collapse
Exactly. There are some packages floating around on this site that will allow you to flash the "stock" Gingerbread, but AT&T hasn't pushed out anything in an official capacity that I'm aware of.
Taking it to a different store (or even the same store on a different day) would probably be a good idea.
Also 2.3.4 would be better than 2.3.3 since it doesn't have that nasty Android OS bug.
Related
I got ahead of myself and installed a radio update on a rooted handset running MoDaCo 2. I ran the updater in update mode and than it prompted a restart.
I restarted and it installed the package than next time i looked the screen was dead. the whole units been dead eversince. no reaction to USB/Power, or to any key combo startups...
Please tell me that this is not the end?
probably dead
from what i have read on this issue, if you flash a GSM radio it runs on a higher voltage and kills your phone.
if you have the insurance they most likely wont be able to tell what broke it.
well there isnt anything you can do. I hope you have insurence. this is the only way that we have found to brick these phones, is to flash the GSM radio.
good luck
arcataslacker said:
I got ahead of myself and installed a radio update on a rooted handset running MoDaCo 2. I ran the updater in update mode and than it prompted a restart.
I restarted and it installed the package than next time i looked the screen was dead. the whole units been dead eversince. no reaction to USB/Power, or to any key combo startups...
Please tell me that this is not the end?
Click to expand...
Click to collapse
Sorry, this is the end.
I didn't think MoDaCo had a v2 for CDMA heros...maybe thats why it told you to update the radio. Nothing that you can do, I think this is the only thing that has killed a Hero is someone not paying attnetion and updating the radio to a GSM one.
Please no one take this the wrong way, but...
At least once a week there's a thread like this, where someone has fried their phone by flashing the wrong package.
Accidents do happen... that's the way it goes. I've been in the tech industry for over 20 years and I've certainly done my share of "what does this do?", but there are pages and pages (and more pages) relating to the process involved in hacking around on your Hero phone and while it is getting easier to do due to the great work by the devs found here in this forum, reading and comprehension of exactly what it is you're doing should always be your #1 step.
Read, download files, read again, verify that you have the correct items, read some more and then start the process.
It's like the old woodworking saying, measure twice, cut once.
To the OP, it sucks that your phone got fried, but one can hope this serves as another warning to others.
There us definitely a modaco 2.0 cdma. What radio update did you use?
adelaney said:
There us definitely a modaco 2.0 cdma. What radio update did you use?
Click to expand...
Click to collapse
It doesn't matter what he used. There are zero radio updates for the CDMA Hero, thus there is no opportunity, at all, to flash something back to the phone that would work.
If you don't know what you're doing, you shouldn't be doing it. It's as simple as that. If you do it anyway, you should expect to get burned.
posguy99 said:
It doesn't matter what he used. There are zero radio updates for the CDMA Hero, thus there is no opportunity, at all, to flash something back to the phone that would work.
If you don't know what you're doing, you shouldn't be doing it. It's as simple as that. If you do it anyway, you should expect to get burned.
Click to expand...
Click to collapse
im sorry to do this because im totaly not into flaming but dude you are a real jerk every post I see from you is condecending and rude. yes you should be sure you know what your doing before you do it but jesus man how did you learn? where you born with total knowledge of the android system? I have posted this to you before, but once again why post anything if you can not be helpfull?
wtphoto said:
im sorry to do this because im totaly not into flaming but dude you are a real jerk every post I see from you is condecending and rude. yes you should be sure you know what your doing before you do it but jesus man how did you learn? where you born with total knowledge of the android system? I have posted this to you before, but once again why post anything if you can not be helpfull?
Click to expand...
Click to collapse
+1
10 Char limit my butt....
wtphoto said:
im sorry to do this because im totaly not into flaming but dude you are a real jerk every post I see from you is condecending and rude. yes you should be sure you know what your doing before you do it but jesus man how did you learn? where you born with total knowledge of the android system? I have posted this to you before, but once again why post anything if you can not be helpfull?
Click to expand...
Click to collapse
+1000 ..... After reading a couple foul posts from this guy yesterday, I did a search for all of his posts and at least 3/4 of them are condescending and rude, in addition to being completely unnecessary and unhelpful.
Why do you come here and post when you have nothing positive to add and nothing nice to say. Seriosly, get some anger management and dont chime in unless you plan to help and be constructive.
rockcrawler said:
+1000 ..... After reading a couple foul posts from this guy yesterday, I did a search for all of his posts and at least 3/4 of them are condescending and rude, in addition to being completely unnecessary and unhelpful.
Why do you come here and post when you have nothing positive to add and nothing nice to say. Seriosly, get some anger management and dont chime in unless you plan to help and be constructive.
Click to expand...
Click to collapse
+1....
was I constructive and helpful?
jk
to OP:
sorry dude... if u have a Sprint CDMA Hero
and you messed with the RADIO
IT is the end of that phone... dead!
As was advised before, take your phone to a Sprint store and fain ignorance. Say, "For the life of me, I tried to turn it on the other day and it just won't respond!" The techs will fart with it for two hours, calling Sprint's techs and attempting every trick in the book to flash it before finally replacing it with a heartfelt apology. Don't tell them anything that you did to it. Just let them make the determination.
posguy99 said:
It doesn't matter what he used. There are zero radio updates for the CDMA Hero, thus there is no opportunity, at all, to flash something back to the phone that would work.
If you don't know what you're doing, you shouldn't be doing it. It's as simple as that. If you do it anyway, you should expect to get burned.
Click to expand...
Click to collapse
We've all been down this road. Maybe not with flashing a phone, but with other things as well. That's called "learning from your mistake." He got a bit too enthusiastic and had a lapse in judgment...it happens to all of us, including me.
He probably thought he was flashing the MoDaCo CDMA 2.0 ROM for HTC Hero and just accidentally picked up the MoDaCo GSM 2.0 ROM for HTC Hero. Unfortunately, the problem is that the GSM Hero and CDMA Hero are named just that, HTC Hero. There is no real designation to the average user. Even the accessories like batteries between the GSM Hero and the CDMA Hero are different...causing an average user to make a mistake and buy the wrong accessory (got close in buying a battery for the GSM Hero because it was labeled as compatible with "HTC Hero"...only problem was it was for the GSM Hero and not the CDMA Hero, but nowhere on the site said that.)
Go easy on the guy...it's unfortunate, but it happened and now he's learned to be more careful in the future.
tkirton said:
We've all been down this road. Maybe not with flashing a phone, but with other things as well. That's called "learning from your mistake." He got a bit too enthusiastic and had a lapse in judgment...it happens to all of us, including me.
He probably thought he was flashing the MoDaCo CDMA 2.0 ROM for HTC Hero and just accidentally picked up the MoDaCo GSM 2.0 ROM for HTC Hero. Unfortunately, the problem is that the GSM Hero and CDMA Hero are named just that, HTC Hero. There is no real designation to the average user. Even the accessories like batteries between the GSM Hero and the CDMA Hero are different...causing an average user to make a mistake and buy the wrong accessory (got close in buying a battery for the GSM Hero because it was labeled as compatible with "HTC Hero"...only problem was it was for the GSM Hero and not the CDMA Hero, but nowhere on the site said that.)
Go easy on the guy...it's unfortunate, but it happened and now he's learned to be more careful in the future.
Click to expand...
Click to collapse
So curiosity kills me here. If 1.6+ has CDMA support in the future could we potentially have 1 set of roms for both devices?? I guess that is probably just wishful thinking due to other differences, doesn't change the fact the radio is still different and a different driver, not just kernel level stuff.
Ignore me i make less sense as i ramble.
Kcarpenter said:
So curiosity kills me here. If 1.6+ has CDMA support in the future could we potentially have 1 set of roms for both devices?? I guess that is probably just wishful thinking due to other differences, doesn't change the fact the radio is still different and a different driver, not just kernel level stuff.
Ignore me i make less sense as i ramble.
Click to expand...
Click to collapse
Theoretically, yes. The ROM should be able to determine which radio is in there and set the settings accordingly (including loading the correct driver).
But, that's in theory. Not sure if that is how this going to play out at 2.1 (since that's the next release for our phone).
wtphoto said:
where you born with total knowledge of the android system?
Click to expand...
Click to collapse
Hardly. I learn something every day.
But it doesn't take "total knowledge of the Android system" to know that:
(A) This over here isn't meant for my phone
(B) People repeatedly post saying "don't do it!"
(C) People who do it anyway report bricking their phone
should lead to:
(D) I really shouldn't do that.
It just takes normal reasoning ability.
I have zero problem with someone who says "gee, I don't understand the difference, will you tell me?"... but the one who decides to do something, I am going to assume the same of him that I would hope he assumes of me.
That he has a clue.
People who don't have a clue should be expecting to be reminded of the fact. This is how people *learn*. Conversely, if I make some stupid mistake, I hope someone pokes ME about it, too.
XDA is a great resource. If only more people would actually use it.
We now return you to your regularly scheduled fora.
To OP:
Do what they said and play it ignorant at a repair center, they will have no clue what happened and give you a new phone.
Well I have insurance so maybe that is why but who knows.
Don't worry OP I did the same mistake, just keep reading and you will be fine. Don't be afraid to get back into the modding scene, just read up before you try anything next time, and maybe create a thread to verify you have a solid process before doing it, once you learn everything that you need to be successful.
arcataslacker said:
I got ahead of myself and installed a radio update on a rooted handset running MoDaCo 2. I ran the updater in update mode and than it prompted a restart.
I restarted and it installed the package than next time i looked the screen was dead. the whole units been dead eversince. no reaction to USB/Power, or to any key combo startups...
Please tell me that this is not the end?
Click to expand...
Click to collapse
Okay...once you get your phone back from Sprint and you want to mod it again, my suggestion is to stick to the Hero CDMA subforum for your ROMs. All are guaranteed not to brick your phone.
The Darktremor has a list and links to updated ROMs.
Thanks for the info guys!
there are no sprint stores near by but I should be able to call support about it.
I know its a no no but they wouldn't be able to tell if the MEID was 0ed out would they?
arcataslacker said:
Thanks for the info guys!
there are no sprint stores near by but I should be able to call support about it.
I know its a no no but they wouldn't be able to tell if the MEID was 0ed out would they?
Click to expand...
Click to collapse
No...without actually getting into the phone, they can't tell if you messed with it. And since the phone is dead, they won't be able to tell you tried to mod it. Just do what everyone here says and play ignorant.
Hey everyone, I kind of have a question that might be hard to answer. But maybe one of you can speak from experience with Rogers and android phones in general. Well my question is this. When the Rogers Captivate comes out later this month will the method of rooting be the same as the at&t version for the most part? I also wonder if there is a chance (maybe this has happened to other android phones in the past?) that Rogers will be a gigantic wiener and make it IMPOSSIBLE to root it at all?
Disregarding my questions for a second, it's a pleasure to finally join this forum and thanks for taking the time to read this.
Cheers!
First off, welcome to XDA, glad to have you with us.
Now onwards with your question. It's almost impossible, maybe even illegal, for a carrier to block rooting on an Android device. The whole point of these phones is OPEN SOURCE. The rooting method should be almost identical for the most part. Because we don't have Rogers here, nobody can truly say for sure, but I'd imagine it would be the same.
Oh, that's really interesting! Thanks
Hey,
The phone releases this Monday and the model number for the Rogers version is SGH-i896 whereas the ATT version is SGH-i897. Some files would need to be updated but nothing major. Hopefully we get the support for the Rogers Captivate and can flash it with the awesome custom ROMS
(my first post on the forum and would love to learn and contribute to the awesome xda team)
iswapnil90 said:
Hey,
The phone releases this Monday and the model number for the Rogers version is SGH-i896 whereas the ATT version is SGH-i897. Some files would need to be updated but nothing major. Hopefully we get the support for the Rogers Captivate and can flash it with the awesome custom ROMS
(my first post on the forum and would love to learn and contribute to the awesome xda team)
Click to expand...
Click to collapse
Welcome to you as well! I'm not so sure that any files would have to be updated. As long as the hardware is exactly the same, all should be well.
miztaken1312 said:
Welcome to you as well! I'm not so sure that any files would have to be updated. As long as the hardware is exactly the same, all should be well.
Click to expand...
Click to collapse
The update scripts have the model number in them which would have to be updated. Nothing major.
Interesting, for roms and such it does not sound like too much of a hassle. But maybe having the exact same hardware wasn't necessarily for the best. I got kind of excited with hopes that this new Captivate would be capable of handling 3.5G I think it's referred to HSPUA+ (Don't quote me on that!) Does anyone know if this is the case?
On a side note, do any current or upcoming phones support 3.5G on the Rogers network?
This is partly a matter of curiosity and partly a technical question. Since Cox has officially launched Cox Wireless in Hampton Roads, Omaha, and Orange County, we can be a little less paranoid about talking wireless tech.
And there will undoubtedly be some non-employee customers here, though they're all lucky enough to be able to start with the HTC Desire. I'm stuck with the Hero until they come up with some upgrade program for us early adopters.
So who here has Cox Wireless with a Hero?
More importantly, who has Cox with a Hero with CyanogenMod? Can you get MMS? If so, I may have other questions...
No I don't have cox. What is MMS.
lol, no. but a while back when i made a custom splash i remember seeing a great splash modified for cox, so whoever requested that should be on cox as well, here's the thread. cox, lol.
http://forum.xda-developers.com/showthread.php?t=766042
@macwilliam21 - that may be the funniest post ever.
il Duce said:
lol, no. but a while back when i made a custom splash i remember seeing a great splash modified for cox, so whoever requested that should be on cox as well, here's the thread. cox, lol.
http://forum.xda-developers.com/showthread.php?t=766042
Click to expand...
Click to collapse
Heh. The only Cox splash I see on that thread is the one I made. Nobody requested it, I just figured I might as well share.
I made it partly because I wanted to "re-brand" my Hero back from generic HTC/CyanogenMod and partly because I wanted to prove I could make a prettier logo screen than our paid developers. Seriously, the Cox logo on the official ROM is tiny and grainy for no apparent technical reason.
And apparently two other people downloaded it.
Two people downloaded Cox.
Sent from my HERO200 using Tapatalk
Wha... ? I though I was on xda. Apparently, I got redirected to 4chan.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
I *had* Cox wireless with the HTC Hero but I dumped the service and went with another carrier for an Android 2.x phone because I can't even use the Cox HTC Hero for the things I want. Many of the apps I use such as Skype, Firefox, and just recently many Google Inc. apps, Google Voice, PayPal, and many other apps I like, aren't even found on the Market because the firmware is not supported. Its stuck on Android 1.5 and when I asked Cox tech support if there were any plans to upgrade the firmware I was told they have no intentions of upgrading the firmware. I wasn't interested in paying more money for an upgraded phone and restarting my contract from day 1 all over again after I've been on the service for the first year. I still have the phone though and looking to find some alternative uses for it besides selling it which I think ultimately I may end up doing because no matter what I try doing with it, or install to it to make the phone more appealing, I almost always get the error that this program cannot be installed to this phone.
I was considering trying to upgrade it to 2.1 but I'm kind of reluctant because word on the street someone tried and it bricked the phone. Although I don't know how true that is.
puffidredz said:
Its stuck on Android 1.5 and when I asked Cox tech support if there were any plans to upgrade the firmware I was told they have no intentions of upgrading the firmware.
Click to expand...
Click to collapse
This is true. I get the feeling that the Hero was more of a proof-of-concept or beta test phone and they had a bunch of them left over at launch time.
puffidredz said:
I was considering trying to upgrade it to 2.1 but I'm kind of reluctant because word on the street someone tried and it bricked the phone. Although I don't know how true that is.
Click to expand...
Click to collapse
It's doable. Someone I know in one of the stores actually got a laundry list of reasons from the HQ in Atlanta about why we couldn't/shouldn't do it ourselves, so I upgraded to a proper 2.1 HTC Sense ROM just to prove it could be done safely and with full functionality. Then I upgraded it to Cyanogen 2.2 just for the hell of it.
But then I switched to a Desire when they came up with an upgrade program for us employee early-adopters who got stuck with the Hero. My interest in this section now is purely out of scientific curiosity.
ok....Im new to xda and new to rooting a phone but i cant take this 1.5 on the hero any longer and am in deperate need of directions on what i need to do. i was promised by cox that there was going to be an upgrade and now we find out that this will never happen. please help
you need to run the ruu from a computer witch will uprade u to 2.1 or since your still on 1.5 rooting will be easy for u and u can install a custom rom.also if theres a sprint tech store in your area they should be able to do the ruu for you regardless if your on a smaller regional carrier.
I can't seem to find a good post or thread about this so I'll be the one to ask the dumbest question.
Can a GSM rom be flashed to a CDMA tab? Other than networking issue with the modem, will phone actually boot and be usable on wifi? I'm assuming it most likely will either not work at all or just FC constantly but wanted to ask first.
MODS please delete after a few answers. I don't want to waste thread space...
Anybody has flashed this before ? And i don't know can Verizon tab be able to flash rom for Sprint Tab ?
Waiting for anwser too .
Sent from my SCH-I800
connexion2005 said:
I can't seem to find a good post or thread about this so I'll be the one to ask the dumbest question.
Can a GSM rom be flashed to a CDMA tab? Other than networking issue with the modem, will phone actually boot and be usable on wifi? I'm assuming it most likely will either not work at all or just FC constantly but wanted to ask first.
MODS please delete after a few answers. I don't want to waste thread space...
Click to expand...
Click to collapse
One of the other members did and it worked, I am not sure what was FC'ing but he was using it that way. A word of WARNING, if you accidentally flash the modem with the GSM one, its dead forever! You cannot restore it!!
But yeah it should boot, and be able to use WiFi.
lhttan said:
Anybody has flashed this before ? And i don't know can Verizon tab be able to flash rom for Sprint Tab ?
Waiting for anwser too .
Sent from my SCH-I800
Click to expand...
Click to collapse
Verizon and Sprint use the same radio's so this should not be an issue
OK second question. Where on earth can I find the VZW firmware files to use with Odin or Heimdall? I flashed the Klean ROM and like it but then I realized I was having problems finding the stock pit and pda files to revert back to stock if needed!
I would love if I could use GSM ROM's. I bought a Verizon TAB (mistake now that I realized this) and just use it for WIFI only so network access is not an issue for me.
Is that file you need ?
lhttan said:
Is that file you need ?
Click to expand...
Click to collapse
Downloading now but I'm pretty sure thats it! You are awesome. And I'm a lazy searcher.
try this... its the vzw recovery package i use... unrar and bring it into hiemdall... try using the voodoo overclocked kernal with it... great improvements, blazing fast, and the sound is unmatched... im not sure why, and i could very well be doing it wrong... but when i flash the zImage for the kernal, i always have to flash that zImage into the recovery as well... like i said idk why but 90% of the time my flash will fail unless i do that... so if you have any problems try it... hope this helps!
http://www.megaupload.com/?d=TC4G5IYC
probably the same files... beat me to it haha
I'd actually really like to know this as well... I've got a VZW tab I was given from a friend who updated to a Xoom... I'm only ever gonna use it wifi, and am a bit disappointed in the lack of roms for CDMA tabs... if a GSM Rom would work, and let me use wifi, that would be great for folks like me.
How can I avoid to flash the modem with the GSM one ? I usally use heimdall-frontend.exe to flash !
I could be wrong, but if you go through frontend dont you have to manually palce the moden file into the slot for modem? couldnt you just flash everything but modem? or is it in the kernal as well??
Soft
Brick.
arariel said:
I'd actually really like to know this as well... I've got a VZW tab I was given from a friend who updated to a Xoom... I'm only ever gonna use it wifi, and am a bit disappointed in the lack of roms for CDMA tabs... if a GSM Rom would work, and let me use wifi, that would be great for folks like me.
Click to expand...
Click to collapse
You could always contribute instead of just ***** about the lack of support. You got a free Tab for pete's sake....
Boushh said:
Soft
Brick.
You could always contribute instead of just ***** about the lack of support. You got a free Tab for pete's sake....
Click to expand...
Click to collapse
Wow, ok... I just got the damn thing, let me, you know, learn how to code and program etc... got a while?
Yeah, I got a free tab, and I know next to nothing about it, so I'm trying to find out some information. I dunno that I would call expressing mild disappointment really classifies as "*****ing" but, hey, thanks for YOUR contribution to the thread too, guy. Super helpful. I understand the VZW tab isn't nearly as popular, and that means less people working on it, or maybe there are technical difficulties or something. I have no idea. I just know there is less information, etc. out there about it, and that's disappointing. Nowhere did I say anything like "people here suck for not supporting my device!" The ROM makers here are a talented bunch, that much is obvious... I really like what they're doing, and I'm guessing so does the OP. That's why we're asking about GSM roms... we obviously liked something someone made, and wish we could use it on our device. We're trying to find information, and you come and attack someone with the equivalent of an ER nurse getting mad at a Vet for coming in with a question about their daughter, and demanding that they help treat her themselves.
If I had ANYTHING even CLOSE to as helpful as some of the people here to contribute right now, I would... but I don't... I'm just trying to learn about this device. At my level of knowledge right now, I don't HAVE anything to give. So very sorry if that somehow offends you personally.
That was ugly!
Boushh said:
Soft
Brick.
You could always contribute instead of just ***** about the lack of support. You got a free Tab for pete's sake....
Click to expand...
Click to collapse
Hmm. I wonder what my PM reply from you will have to say in it lol. Anyhow, is a soft brick inevitable? Are there options I can avoid such as obviously not flashing the modem? Or param.lfs? To prevent a soft brick. One person claims it worked on a certain ROM from them. I know I can find out the hard way myself but if I can benefit from someone else's experience I'd like to see if I can do that first.
connexion2005 said:
Hmm. I wonder what my PM reply from you will have to say in it lol. Anyhow, is a soft brick inevitable? Are there options I can avoid such as obviously not flashing the modem? Or param.lfs? To prevent a soft brick. One person claims it worked on a certain ROM from them. I know I can find out the hard way myself but if I can benefit from someone else's experience I'd like to see if I can do that first.
Click to expand...
Click to collapse
Think about it guys you've got devs, and then you have those of us who are just using what the devs design, be it lack of knowledge or lack of effort, either way if you have a free tab, make a backup, make a couple backups, and try it, or maybe get with a dev working on your tab to add the features of the gsm tab to our vzw tab. help them test it, It makes sense that devs get pissed when someone says i got a free tab, do some research, make some effort to further the development for a device in which the devs purchase in most cases with they're own money, and if they brick it in the process they are out alot more money then you are. and the way they save them selves is by again treading on undiscovered territory. So instead of asking make some attempt. learn to use the emulator, learn your device, if you are just getting to know the device then it may not be a good idea to jump right into rooting, and flashing roms....
matthewflinchbaugh said:
Think about it guys you've got devs, and then you have those of us who are just using what the devs design, be it lack of knowledge or lack of effort, either way if you have a free tab, make a backup, make a couple backups, and try it, or maybe get with a dev working on your tab to add the features of the gsm tab to our vzw tab. help them test it, It makes sense that devs get pissed when someone says i got a free tab, do some research, make some effort to further the development for a device in which the devs purchase in most cases with they're own money, and if they brick it in the process they are out alot more money then you are. and the way they save them selves is by again treading on undiscovered territory. So instead of asking make some attempt. learn to use the emulator, learn your device, if you are just getting to know the device then it may not be a good idea to jump right into rooting, and flashing roms....
Click to expand...
Click to collapse
Good post. Hope you weren't referring to me though! Check my sig I've been around the block with Android.
Oh and I'm running Overcome ROM right now on my VZW TAB. I'll be posting a video of the steps to take to ensure this works correctly some time this weekend.
Looks like my VZW may work out afterall...
arariel said:
Wow, ok... I just got the damn thing, let me, you know, learn how to code and program etc... got a while?
Yeah, I got a free tab, and I know next to nothing about it, so I'm trying to find out some information. I dunno that I would call expressing mild disappointment really classifies as "*****ing" but, hey, thanks for YOUR contribution to the thread too, guy. Super helpful. I understand the VZW tab isn't nearly as popular, and that means less people working on it, or maybe there are technical difficulties or something. I have no idea. I just know there is less information, etc. out there about it, and that's disappointing. Nowhere did I say anything like "people here suck for not supporting my device!" The ROM makers here are a talented bunch, that much is obvious... I really like what they're doing, and I'm guessing so does the OP. That's why we're asking about GSM roms... we obviously liked something someone made, and wish we could use it on our device. We're trying to find information, and you come and attack someone with the equivalent of an ER nurse getting mad at a Vet for coming in with a question about their daughter, and demanding that they help treat her themselves.
If I had ANYTHING even CLOSE to as helpful as some of the people here to contribute right now, I would... but I don't... I'm just trying to learn about this device. At my level of knowledge right now, I don't HAVE anything to give. So very sorry if that somehow offends you personally.
Click to expand...
Click to collapse
LOL You just had a *****fit with the best CDMA dev we have, nice work.
How did you do it?
Hey man, watched your video review great stuff, any update date on how you got the rom on your CDMA Tab however? I just got a Sprint Tab and would love to flash Overcome on it...thanks for any advice
connexion2005 said:
Good post. Hope you weren't referring to me though! Check my sig I've been around the block with Android.
Oh and I'm running Overcome ROM right now on my VZW TAB. I'll be posting a video of the steps to take to ensure this works correctly some time this weekend.
Looks like my VZW may work out afterall...
Click to expand...
Click to collapse
connexion2005 said:
Good post. Hope you weren't referring to me though! Check my sig I've been around the block with Android.
Oh and I'm running Overcome ROM right now on my VZW TAB. I'll be posting a video of the steps to take to ensure this works correctly some time this weekend.
Looks like my VZW may work out afterall...
Click to expand...
Click to collapse
hey connexion2005, any update on the video? i´ve been surfing around the forums for a couple of hours now and haven´t found any procedures on how to get overcome on the VZW tab. just wondering
I've seen a lot of people fretting about being able to RMA their nexus after unlocking/rooting/trying different ROMS & kernels. Likewise there are conversations about & guides about how to reset the device to hide the fact it has ever been unlocked. This is all an absolutely unnecessary worry.
So, to put everyone at ease I share with all XDA'rs the answer I got from Google when I asked "Hey guys, will rooting wreck my warranty?" I think you will all find this to utterly unambiguous.
Thank you for contacting Google!
Warranties and RMA are still covered *regardless* if a device was rooted.
We are not trying to prevent customers from unlocking the bootloader and installing a new operating system that allows for "rooting".
Android has always provided customers the ability to do that on Nexus devices, and encouraged other OEMs to do the same. So in that sense we are not against "rooting."
This being said, we can't guarantee full advertised/promised functionality if the source code for the Android OS has been modified as the functionality may have changed.
Click to expand...
Click to collapse
There you go folks, it's a developer's device so use it to it's full potential. This appears to be Google boilerplate so you're looking at an off-the-cuff response from some random support staffer. (I couldn't import the pretty formatting.)
Think any other brand/manufacturer would have a similar answer to the same question?
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
EDIT: Just to clarify, this about Google's North American policy - it appears that they follow this throughout Europe as well, and that European law probably reinforces this. Still, it can't hurt for anyone to check with Google themselves. Also, as per the thread title, this is about Google. If your warranty is held by anyone else this info may have no relevance at all.
NotFromMountainView said:
I've...
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
Click to expand...
Click to collapse
Is this real? I know they don't care, but would they really say it in writing? Do you have the actual email?
aooga said:
Is this real? I know they don't care, but would they really say it in writing? Do you have the actual email?
Click to expand...
Click to collapse
Yes, I just cut & pasted the actual response as I got it -- but lost the *bullet point formatting. Other than that I omitted the Dear [my name] & the rest of the boilerplate about contacting Google for any other follow-up or other questions.
I understand your question it sounds almost too good to be true.
This is fantastic. Thanks for sharing.
NotFromMountainView said:
Yes, I just cut & pasted the actual response as I got it -- but lost the *bullet point formatting. Other than that I omitted the Dear [my name] & the rest of the boilerplate about contacting Google for any other follow-up or other questions.
I understand your question it sounds almost too good to be true.
Click to expand...
Click to collapse
Cool. Good to know.
They provided us with the tools to unlock/lock our bootloader and set up a website to show us exactly how to do it. I think it couldn't be anymore obvious that they don't care that you stuck some binaries on the /system partition so you could run Titanium Backup
NotFromMountainView said:
I've seen a lot of people fretting about being able to RMA their nexus after unlocking/rooting/trying different ROMS & kernels. Likewise there are conversations about & guides about how to reset the device to hide the fact it has ever been unlocked. This is all an absolutely unnecessary worry.
So, to put everyone at ease I share with all XDA'rs the answer I got from Google when I asked "Hey guys, will rooting wreck my warranty?" I think you will all find this to utterly unambiguous.
There you go folks, it's a developer's device so use it to it's full potential. This appears to be Google boilerplate so you're looking at an off-the-cuff response from some random support staffer. (I couldn't import the pretty formatting.)
Think any other brand/manufacturer would have a similar answer to the same question?
Hope this gives everyone a nice warm feeling -- and I suppose I should sign off begging you to hit the 'thanks' button. :angel:
Click to expand...
Click to collapse
Sorry little edit. Its not advertised as a developers device. Nowhere in google's ads or their nexus page does it says "developer". I'd still be wary of RMA with root if you highly modified system apps and such.
Sent from my Nexus 5 using xda app-developers app
monkeypaws said:
Sorry little edit. Its not advertised as a developers device. Nowhere in google's ads or their nexus page does it says "developer". I'd still be wary of RMA with root if you highly modified system apps and such.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
It never hurts to be wary. And it anyone managed to overclock the device so astronomically that it burst into flames there may be some pushback from Google. But the email is, as I said, unambiguous.
As to the suggested edit, I never said anything about advertising, but certainly you can tap 7 times and be rewarded with "Congratulations, you are now a developer!" That, as well as well as crachel's point seem to weigh towards it being referred to as a developer's device -- at least casually.
yup. ive always told people that if its a hardware issue, google will rma it, even if its rooted. but if its a software issue, most likely they wont. google themselves looked for a way to give us the means to unlock our bootloaders, and fastboot oem unlock is the gift they gave us with the nexus one
i myself have sent in devices that are still rooted, with custom roms, to get rma'd. google never gave me issue.
simms22 said:
yup. ive always told people that if its a hardware issue, google will rma it, even if its rooted. but if its a software issue, most likely they wont. google themselves looked for a way to give us the means to unlock our bootloaders, and fastboot oem unlock is the gift they gave us with the nexus one
i myself have sent in devices that are still rooted, with custom roms, to get rma'd. google never gave me issue.
Click to expand...
Click to collapse
simms22: My guess is that if there's any question of the problem actually being a custom OS issue just re-flash/reset to stock & any remaining hardware issues will be dealt with by Google. My key point was that nobody need worry about resetting any flag that it had been unlocked at some point. From your experience & what they've said and done I think it would take some phenomenally destructive code before they'd even raise the issue.
NotFromMountainView said:
simms22: My guess is that if there's any question of the problem actually being a custom OS issue just re-flash/reset to stock & any remaining hardware issues will be dealt with by Google. My key point was that nobody need worry about resetting any flag that it had been unlocked at some point. From your experience & what they've said and done I think it would take some phenomenally destructive code before they'd even raise the issue.
Click to expand...
Click to collapse
when the nexus one just came out, there was a big name google developer that stopped in xda and helped us out every once in a while. i wish i could remember his name. sometimes we even got "leaked" code directly from google. that would never have happened if google cared that we had root.
simms22 said:
when the nexus one just came out, there was a big name google developer that stopped in xda and helped us out every once in a while. i wish i could remember his name. sometimes we even got "leaked" code directly from google. that would never have happened if google cared that we had root.
Click to expand...
Click to collapse
That is just great! And just one more reason that I find it really hard to become overwrought over rattling buttons.
An obvious extension of this is that on support calls (or email) one can mention root/kernel/ROM without fear. Heck, Google might even want to know how mods perform.
But this is till the time we can RMA it which google is handling but when our warranty will expire we will have take it to Lg service center and I doubt that they will also give the same reply.
Policies for both of them must be different.
LG will most likely not be so understanding regarding rooting in country`s where there you can`t buy a Nexus in the Play store but in a shop.
gee2012 said:
LG will most likely not be so understanding regarding rooting in country`s where there you can`t buy a Nexus in the Play store but in a shop.
Click to expand...
Click to collapse
LG wont be understanding, period. Its only google that will except rooted devices.
If you bought another/extended warranty from your carrier or if your carrier import and service your phone then I think you have to keep hands in yr pockets they may not have a user friendly policy as Google's seems to ...
simms22 said:
LG wont be understanding, period. Its only google that will except rooted devices.
Click to expand...
Click to collapse
What do you think could be the reason Google doesn`t offer Nexus devices in all country`s instead of in selected country`s only?
Besides the obvious $$ reason for LG making more money
gee2012 said:
What do you think could be the reason Google doesn`t offer Nexus devices in all country`s instead of selected country`s only?
Click to expand...
Click to collapse
there could be many, most likely legal though. maybe even something with taxes or the currency being used in that country.
Hi,
I asked too about root, unlocked bootloader/custom rom (custom Android Kit-Kat software) and warranty LG/Google, the French support is light and evasive (even if I detailed all the points):
Google traduction D):
Thank you for contacting the Google team about your Nexus 5. My name is and I'm Rozenn your contact today.
I understand your desire to rooter your phone because it is of course one of the benefits of owning the Nexus 5 and the android system.
However, if you need to claim warranty, we will ask you to return the phone to the Android version of Kitkat.
Also, be aware that we can not guarantee the functionality of the device if it is Roote.
If your phone is a concern and you need to claim warranty, from the moment he received no trace of shock or been in contact with water, simply contact us. If we can not resolve your concern, we will offer you an exchange. Your product is guaranteed for 2 years.
Click to expand...
Click to collapse
But the general idea seems the same as the reply from Google in the OP, less detailed.
viking37 said:
Hi,
I asked too about root, unlocked bootloader/custom rom (custom Android Kit-Kat software) and warranty LG/Google, the French support is light and evasive (even if I detailed all the points
Click to expand...
Click to collapse
If I'm not mistaken there's an European law about that. Basically if we have bought a device in Europe the manufacturer must repare our device even if the software has been modified. (Instruction no. 1999/44/CE of E.U.)