Related
I am working my master plan to getting a new phone lol...
Does anyone know where I can find a picture of a G2/VISION's ABOUT PHONE stats before its been rooted or a roms been put on it? I dont wanna call TMOBILE and they ask me certain things like the software version and android version I'm running and I give them the information based off what rom I have.
Unless someone knows what those would be off the top of their heads.
Most phones have different factory shipped software, so what in particular are you looking for?
The reason its tough to answer is because you didn't state any info of value. Are you trying to exchange/return? Are you wanting to buy a new one?? I mean that kind of important don't you think?
If its a warranty exchange they won't ask you for any software numbers only ask about damages.
If buying a new one who cares anyways.
If those are wrong please fix your question.
Thanks
Sent from my HTC Vision using XDA Premium App
So... you're trying to scam the T-mobile CS support by giving them false information about a non-rooted phone rather than your rooted phone.
If you're going to get a warranty return and replacement the least you can do is unroot your phone (you'll have to when you return it...(or ffs at least put a stock pre-rooted ROM back on it)) when you call in so if you're not confident in your ability to BS them you can have the real numbers ready....
just downgrade and unroot.....
xudsa II USERT said:
Most phones have different factory shipped software, so what in particular are you looking for?
Click to expand...
Click to collapse
Just whatever info in the ABOUT PHONE STATS for a phone that hasn't been rooted and modded. Software version and stuff like that...
I have a G2 but I have had an issue and had several replaced because it'll just randomly shut off sometimes. And since I've replaced it quite a few times already I was ready to just ask them to replace my phone with something else.
Only thing is I just want to have that information so as they ask me I can be like this is what I have.
d3athb4dishonor said:
Just whatever info in the ABOUT PHONE STATS for a phone that hasn't been rooted and modded. Software version and stuff like that...
I have a G2 but I have had an issue and had several replaced because it'll just randomly shut off sometimes. And since I've replaced it quite a few times already I was ready to just ask them to replace my phone with something else.
Only thing is I just want to have that information so as they ask me I can be like this is what I have.
Click to expand...
Click to collapse
just load a stock pre-rooted ROM on your phone. Could've had it done by now...
martonikaj said:
just load a stock pre-rooted ROM on your phone. Could've had it done by now...
Click to expand...
Click to collapse
I think his phone has problems, cause he mentioned about it rebooting, so I guess he cant downgrade?
d3athb4dishonor said:
Just whatever info...what I have.
Click to expand...
Click to collapse
I have some info I logged down before rooting, but its from a stock Desire Z, not a T-Mobile version, will that do?
BTW: Another guy had similar reboot problems too here
Hi everybody,
I bought a Note 2 in october 2012. I installed the ROM HD Revolution. Until now there was no problem.
Few days ago, my screen has swiched off and there was lot of reds pixels everywere on the screen.
The phone of course was rooted and the garantly not applicable.
So in the samsung shop, i explain that the phone was rooted... The techniciens has puted a new screen thinking that the problem was coming from a screen hardware. This new screen has well worked during 20 mn, after that, same trouble, the screen was killed....
My phone was sent to another tehcniciens ( more specialists and i think, working directly with samsung) in france, who can works on the motherboard. But just before to sent it, the technical personnal has succefuly replace the rom Revolution by another official ROM by Odin. (In order to keep my garantly.....wonderful techniciens)
Today the phone was return to me, with just a new screen. The third screen after mine who was killed in first.
No motherboard trouble, no graphic chipset trouble was fixed, only the HD Revolution ROM who is apparently , and i 'am sure now, has killed the screen
I'am not able to explain why and how, I am not found on the web or another forum the same trouble.
Somebody know what's happened?
thanks
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
silentecho13 said:
You might want to contact the developer, but I doubt the rom was the issue.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
I'am sure, very sure that the problem on the screen is due to the ROM Revolution, otherwise explain me why the third screen has no trouble after changing only the ROM with the lastest samsung ROM?
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
SacGuru said:
The official technicians do try to convince you that a custom ROM is the cause of your problem. Not making a judgement on whether this was what happened in your case, but just my personal opinion.
I am in India, where anyway Sammy tries to avoid taking responsibility however possible. One of my friend had sds on his s3, and the guys from Samsung tried to refuse him warranty on the basis that they believed he had a custom firmware. They were adamant on this even on his pointing out that thousands had had this even on the stock ROM, and thus could not be in any way related to flashing a custom firmware. Only when he threatened them with legal action (as they couldn't prove it was flashed anyway) did they finally took it in for repairs.
My advice is, check out the devs thread for the ROM, if its a genuine problem then it is sure to be mentioned by someone there.
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
prbassplayer said:
I suggest you verify on the forum thread and contact the dev. I highly doubt its the rom. I imagine for what you say to be possibly its not rom related but kernel and would require some sort of color adjustment hack of sorts, even then I highly doubt it as more users would have experienced the same. As for your proof from samsung means nothing. I've sent devices and computers out to warranty and the document says one thing but when I take it apart I see things where changed that do not reflect what the work order says. Not saying its the case just saying take it with a grain of salt.
I can't seem to find the rom your talking about.
Click to expand...
Click to collapse
It was the REVOLUTION HD Rom.
You think that the Samsung technicians when they changed the screen after the other first technicians has not been honnest?
It's incredible, i don't believe in this idea... I cannot see the interest... But if you are talking about the kernel maybe it yes...
It's a crazy story...
HD Revolution....? wait.. isnt it for a international version of Note 2?
No wonder why your phone is acting up. Flashing almost non compatible ROM on your device doesnt give you rights to discredit Dev.
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
cwhitney24 said:
I believe he is talking about this rom that is not in the att section.
http://forum.xda-developers.com/showthread.php?t=1925402
OP, when flashing did you happen to flash anything else such as that gpu rendering thing they have on that page? Also, any extreme overclocking or anything?
Sent from the Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
I use the recovery mode after have put the zip's ROM on my SD card.
And i never use the o/c
I 'am sure that the trouble has been caused by the Kernel or the ROM... I don't remember what was the kernel... i thinking...
prbassplayer said:
Well then if that is the rom there is your problem. Your lucky Note II in general share the same SoC else you would have hard bricked. I suggest you do your research correctly before saying something broke your device. In the end its your responsability to know what you are flashing and even if said rom/kernel/mod does break your device its your fault, you flashed it not the developer. Its a risk we all take when modifying our devices.
Click to expand...
Click to collapse
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
aquasirius said:
I know that, but on the french forum we are several with this ROM, i'am looking for the same trouble in France: nothing...
I'am wondering what's happened and i 'am not here to cry but to exlpain you this trouble and i 'am trying to have an elaborate conversation in order to find the origin, I find it normal beetween enthusiast....
Click to expand...
Click to collapse
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
mike1986. said:
No mate, LTE version is not supported.
Click to expand...
Click to collapse
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
aquasirius said:
I understand but, the first technicians i saw works for samsung, it's not samsung technicians, and these technicians has tried to change my ROM revolution in order to preserve my warrantly. Unfortunatly we have decided together that in first my phone will not send to Paris at Samsung.
The local technicians has received a new screen, and it was impossible for them to change the rom, anyway they has changed my screen by the new, after 20 mn the new screen has crashed...
We decided to send unfortuntly the phone to paris because we has think that the trouble was the motherbord or the graphic chipset. I was very afraid concerning my warrantly. But the local technicians has success just before to send the phone to change the revolution rom to a samsung in order to keep my warrantly. Otherwise the technicians of Paris..
At paris they has changed for the third time just the screen, anything else , and the note 2 is working perfectly....
I have the report by paper of all investigations makes... I am not a lie.. I cannot saw another reason of this trouble....
Click to expand...
Click to collapse
Relax man, I did not think you were lying, neither did I accuse you of it, I merely asked you to, and personally believe,that the developers on this forum (who are people like you and me) are anyday more trustworthy than repair men who are from samsung or freelancers (read people bent on profiting from me screwing up my cellphone). Thus I asked you to visit the developers thread and look for comments about the issues you were facing, that is what I would've done.
Apparently you flashed a ROM which was not meant for your particular model. Whether that is true or not, I am sorry for all the trouble you had to go through with the engineers and all. I hope your note 2 functions great from now on.
Je vous présente mes meilleurs vœux pour l'année 2013
Sent from my GT-N7100.
Those who help noobs go to heaven. True story.
prbassplayer said:
Well you are disproving yourself. If no other LTE variant on that rom has had similar problems then its not the rom/kernel/mod. It was a fluke of bad hardware with lazy techs (don't want to generalize its easier to blame it on an external source than actually debugging). Second your arguments are null in the end becaus:
That includes I7105, I317[M] and T889[V]. It might work, but probably not 100% and the developer simply offers no support for it.
Click to expand...
Click to collapse
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
aquasirius said:
It was the REVOLUTION HD 4, installed in november, not the 8 or the 9
I used the ROM perfectly adapted for my note 2
Now my note is working without problem with the last samsung rom with 4.1.2 android version.
Nothing has been changed into my phone (hardware etc...) just a new ROM...
And never else was happened on my phone before the trouble.
Click to expand...
Click to collapse
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
prbassplayer said:
Man you said your on a 3rd screen so don't say hardware hasn't changed. This is not counting for anything that changed when you shipped out. In the end it doesn't matter if it was a November rom, or January rom its based on the N7100 firmware not N7105 therefor although it might work probably won't work 100%. You are so caught up that it has to be the rom that you are ignoring key points in your argument. It is more likely to be a hardware problem than software. I'm not saying it wasn't the rom/kernel combination because its possible, who knows, however its a rom based on Sammy firmware that isn't made for your device. Plain and simple.
Cheers
Click to expand...
Click to collapse
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Dumbo53 said:
I think several people have made good points though who knows, it's also possible some part of your os got corrupted and it killed the screens. I've seen a lot of wierd stuff happen with computers over the years. I repair phones, desktops and laptops myself and I continue to see new problems. Some of it I figure out, some I never do.
Another explanation that occurs to me - a transitory short that fried the screens. Did you drop or jar the phone? Spill fluid? Have high or extremes of temp or humidity ? **** happens. Intermitant problems are the absolute worst to track down. If it is something lurking in the hardware and they didn't fix it completely, it may say hello to you again! Problem devices often stay problem devices even after a number of "final" repairs that work for a while. That's why if something like that happened to me, I'd be happier with a replacement device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Maybe you right, and the phone has been exposed every time in good condition, and never droped or jared. I will see with the time if it was a another hardware problem.
I think actually the association ROM/kernel has revealed an intrinseq hardware problem on my phone and maybe later even with a samsung rom the problem should be appear again....
aquasirius said:
I mean hardware (motherboard, chipset,....etc) of course screens are hardware.
And I have 7100 and the ROM I used was for the 7100.
The ROM has broken something on my phone, i don't know what, maybe my english is too bad and i'am not able to do understand my story with the corrects words
I'am not a noob to choose the wrong ROM for my note 2...
we thought that the problem has came from a voltage problem beetween the screen and the GPU or the chipset...
Without any else action from me (no o/c, no brutality) i cannot see anything else....
Click to expand...
Click to collapse
Wait.....Your Note 2 is an N7100? Then why did you come to an i317 forum to complain about a ROM somehow breaking your screen?
If you really think you have a legitimate concern that a ROM may have damaged your phone in some way, contact the developer. Maybe it has happened before. Maybe the developer can make changes to prevent it from happening to others. What you probably shouldn't do is to make claims that a ROM damaged your phone on a forum for a different model of phone.
Hey there,
I have been having some issues with my LGOG over the past month or so and I have just started to look into possible solutions.
I first noticed that screen rotation and proximity sensing seemed to be non-functional. I always had problems with screen rotation, but it basically stopped completely after I rooted/unlocked (using manuals on XDA and FreeGee app). I was stuck on ZV8 (couldn't upgrade because root) and figured that an updated ROM would solve my problem.
I have now updated to Lifeless v11 ROM and have found nearly every sensor (including light, sound, proximity, gyro, etc) to be non-responsive. I then thought this must be a kernel problem, so I tried flashing Joker's test kernel (from Aroma) and his Stockish 2.1.1 kernel. No dice. Additionally, I tried to do a sensor calibration and was given the message "Calibration failed. Try again".
I realize there is a possibility that this could be a hardware issue, but is there any other possibility I have overlooked? I have isolated some error messages in logcat, if that would help at all.
Thanks in advance for the help.
Seems like a defective phone. You should return under warranty.
Sent from my LG-LS970 using xda premium
alsaces daddy said:
Seems like a defective phone. You should return under warranty.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Awesome, will do. Do you know if they will give me trouble for having messed around with things? I suppose I could always just restore my old backup I made with the stock ROM and re-lock the bootloader and unroot.
Do you think I need to go through that? Not that it's the end of the world.
rife said:
Awesome, will do. Do you know if they will give me trouble for having messed around with things? I suppose I could always just restore my old backup I made with the stock ROM and re-lock the bootloader and unroot.
Do you think I need to go through that? Not that it's the end of the world.
Click to expand...
Click to collapse
Honestly I would just in case. Ya know? They could say you messed it up with whatever you did and whatnot.
Just for kicks and giggles.. What ROM are you on and what tweaks did you add?
Scratch that. Try reflashing the ROM after a system, cache, and dalvik cache whip. Very well could have been a bad flash. If that's not the case then clear, lock, and unroot.
Sent from my LG-LS970 using xda premium
alsaces daddy said:
Honestly I would just in case. Ya know? They could say you messed it up with whatever you did and whatnot.
Just for kicks and giggles.. What ROM are you on and what tweaks did you add?
Scratch that. Try reflashing the ROM after a system, cache, and dalvik cache whip. Very well could have been a bad flash. If that's not the case then clear, lock, and unroot.
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Very cool, thanks for your great advice!
I was on Lifeless v.11. I tried your suggestion (wipe caches/system and reflash), but unfortunately no dice. I also tried rolling back to my stock backup and there is still no functionality. Seems like I have a broken unit. :/
I'm going to roll everything back as much as I can and cover my tracks so I can try and get a replacement this weekend. Hopefully they don't jerk me around too much in the process!
Thanks again, and have a good week(end).
EDIT:
BTW, I had installed all the tweaks that were installed with Lifeless (quite a comprehensive list). I thought that might be the issue as well, but seeing as how my stock backup is still giving me issues, it looks like it's strictly a hardware issue...
If you have insurance through Sprint you honestly should not need to worry about them knowing you had the phone rooted or anything. They asked me if I rooted the first android phone I had, but said they didn't care, they just had problems with reflashing rooted/unlocked versions of the phone before so were being safe. Now it's to the point where I just tell them I broke it lol. I took my LGOG in yesterday after a failed update/flash back to stock at work. Told him exactly what I did, they ordered me a new phone (New, not a refurb cuz they were on backorder ). I was actually able to get it fixed, and even let them know, and they said they already ordered it so I'll have a new phone on Monday either way lol.
I try to flash back to stock still, just in case that one day they decide to change policies without me knowing. But if I'm in a hurry I don't worry about it.
Sent from my LG-LS970 using xda premium
dont think you are gonna walk in and walk back out with a phone. the G is on backorder. I've been waiting on a replacement since the 16th and still nothing.
Just for future information:
I went into the Sprint Store this afternoon and found, just as others suggested, that they would need time to replace it. They kicker was that they told me that there was no way that I would get a new phone as a replacement. I could expect a refurbished model of unknown quality.
I finally found out that I could take up the issue with LG directly, so I opted to do so. They informed me that as long as there was no impact or water damage (which there isn't), they would do their best to either repair or replace the phone. The problem is that I have to pay to ship the phone to their Texas plant and then wait for up to a week while they repair the unit.
This isn't the best of circumstances, but I figure this might be the better solution. I will be taking photos before I send it to be sure that whatever I get back isn't a random refurb with cosmetic damage (mine is almost pristine).
I'll keep this thread posted with how everything goes.
Same problem
guyz i got the phone from my teacher..he told me that every time he try to factory reset error comes"boot secure error" and phone cant factory reset and also rotation sensor not working ..i flashed official v19G and after that evert single one sensor no working,literally every sensor in showing 0 value through exilar app..any solution which can solve this ..???
my phone model is F180K
That's not a sprint phone. Ls970 is Sprint model,
Sent from my LG-LS970 using xda app-developers app
I received a software update to my tab today, does anyone know what the update included? Looks like possibly a new kernal dated 8/19. The build number is JDQ39.T310UEUAMH2 still 4.2.2.
depechemodegurl said:
I received a software update to my tab today, does anyone know what the update included? Looks like possibly a new kernal dated 8/19. The build number is JDQ39.T310UEUAMH2 still 4.2.2.
Click to expand...
Click to collapse
4.2.2??? Didnt you mean 4.1.2? Which country is ur tab?
FiliBrushedRed said:
4.2.2??? Didnt you mean 4.1.2? Which country is ur tab?
Click to expand...
Click to collapse
My tab has been on 4.2.2 since i bought it on release day. Its a U.S tab..
FiliBrushedRed said:
4.2.2??? Didnt you mean 4.1.2? Which country is ur tab?
Click to expand...
Click to collapse
depechemodegurl said:
My tab has been on 4.2.2 since i bought it on release day. Its a U.S tab..
Click to expand...
Click to collapse
The 7 in is the only version that came with 4.1.2.
depechemodegurl said:
I received a software update to my tab today, does anyone know what the update included? Looks like possibly a new kernal dated 8/19. The build number is JDQ39.T310UEUAMH2 still 4.2.2.
Click to expand...
Click to collapse
While the update was downloading, I think there was a mention of app updates and performance enhancements. My Tab 3 8 seems a little faster since the update, but it could just be my imagination.
Definitely a new build.
Sent from my SM-T310 using xda app-developers app
Hurrycanejohn said:
While the update was downloading, I think there was a mention of app updates and performance enhancements. My Tab 3 8 seems a little faster since the update, but it could just be my imagination.
Definitely a new build.
Sent from my SM-T310 using xda app-developers app
Click to expand...
Click to collapse
For what it's worth, this new kernel has almost bricked my Galaxy Tab 3 8.
Yes, that was this Mon Aug 19 08:55:20 KST 2013 Kernel 3.0.31-1422334
Build numberJDQ39.T310UEUAMH2 that I was stupid enough to install as
a scheduled 90 MB update yesterday, Aug 27.
Now the device spends half of its time in a state where it is extremely unresponsive
and every click requires multiple taps; even the capacitive back and menu buttons
won't light on the first try. Fortunately it feels normal as I'm typing this, but
I know that it might be only temporary - oh, and before you ask, factory reset
did not help. All this brick-on-brick-on stuff persisted even after doing the
volume-home-power factory reset and wipeout dance.
Mind you, the device was never rooted and had just a few apps installed, and
this slow response is present even when they are not running, in the home screen.
Even killing most of the apps and system tasks does not help. So either they
somehow screwed up the input subsystem and drivers, or there is something
very CPU intense running in the background in this new kernel from time to
time.
Do you experience anything like this? Samsung chat help was wortless; of course
they had no clue about all that, and their only idea was the factory reset,
which did not quite work out, since the kernel version stayed the same after
that. Not sure if this all affects the battery life yet - it's been too early, but if
it does, it would be hinting at some tight loop in the kernel and not the drivers
issue.
I wonder, if it's just my device or it is more widespread? Right now I'm trying
to find some shop that would really reflash the device back to factory image,
or, barring that, just returning the Tab and getting the new one. Let's see if
the searches for that build number will bring more people here; at the moment
it is a pretty unique search term on the web, with just a couple of sites,
the second one being the Samsung updates.
This update has messed up my tablet, too. It is very unresponsive. I don't know what to do.
Sent from my SM-T310 using xda app-developers app
update
YEAH shut off auto update ford your tab or tabs:laugh:
dollaz151 said:
YEAH shut off auto update ford your tab or tabs:laugh:
Click to expand...
Click to collapse
Good advice - thanks. But a bit late
Stupid mistake, really. I thought that I did - but that was for apps, not kernel.
By the way, just got off the phone with Samsung. Bottom line is, they don't
reflash devices back to factory images. In fact, their service center does
not even *have* a factory image. They install whatever is the latest load of
junk that Samsung gives them - and in my case it is probably going to be
exactly the problem image that I already have. (Sigh.) I cannot believe these
guys are still in busuness with that approach to customer service.
Anyway, the choice is between finding some underground shop and hoping
that they have a proper OS image and returning the device to Amazon before
its warranty is voided by reimaging. Oh well. If it is a proper original factory
image, it should not void the warranty in any case, right?
Anyone knows what is the factory image build number for US version of
Galaxy Tab 3 8.0, anyway? I was not smart enough to write it down before
the update.
I have the US version tab3 8.0 and I am rooted. Thankfully rooting actually blocks you from getting OTA updates from Samsung it will specifically tell you that you cannot update because you are on a custom firmware.
Probably happens on other tab3 devices that are rooted...
Sent from my HTCONE using Tapatalk 2
No problems for me I installed the update and notice no difference my Tab 3 8 is as responsive as it always was.
osokin said:
Good advice - thanks. But a bit late
Stupid mistake, really. I thought that I did - but that was for apps, not kernel.
By the way, just got off the phone with Samsung. Bottom line is, they don't
reflash devices back to factory images. In fact, their service center does
not even *have* a factory image. They install whatever is the latest load of
junk that Samsung gives them - and in my case it is probably going to be
exactly the problem image that I already have. (Sigh.) I cannot believe these
guys are still in busuness with that approach to customer service.
Anyway, the choice is between finding some underground shop and hoping
that they have a proper OS image and returning the device to Amazon before
its warranty is voided by reimaging. Oh well. If it is a proper original factory
image, it should not void the warranty in any case, right?
Anyone knows what is the factory image build number for US version of
Galaxy Tab 3 8.0, anyway? I was not smart enough to write it down before
the update.
Click to expand...
Click to collapse
You should go to sammobile.com, and click on firmwares, there will be drop down menus to find your device. The firmware for the UK would be a good choice to flash, you have to use odin.
Sent from my SM-T310 using XDA Premium HD app
Sorry to hear about all the problems you guys are having with the update. It's strange because I installed the same update and I've had no problem at all on Tab 3 8.0.
Sent from my SM-T310 using xda app-developers app
osokin said:
Anyway, the choice is between finding some underground shop and hoping
that they have a proper OS image and returning the device to Amazon before
its warranty is voided by reimaging. Oh well. If it is a proper original factory
image, it should not void the warranty in any case, right?
Anyone knows what is the factory image build number for US version of
Galaxy Tab 3 8.0, anyway?
Click to expand...
Click to collapse
Okay, for anyone who's still following this saga, I did find the reflashing shop and here is
what the guy says: he cannot return the device to its original factory kernel state. This
requires the device hardware key that he does not have, so what he can do, he can only
root it and reflash it with what he thinks is the best approximation of the factory kernel.
However, it won't be the exact match - to begin with, the bootloader will be different,
and in his experience, native Samsung images tend to work faster and have better
performance than these approximations. They have better radio perfirmance, etc, etc,
etc. After his work, the device will be left with something fairly close to the good factory
image, but not quite - and since I already had something that was 'not quite' good in a
similar sense, then what was the point.
His normal advice would be to wait a bit before reflashing, maybe it would become better -
but since my return window had just a few days left, he suggested returning the ruined
device while it was still possible and getting a new one instead. Which is exactly what
I did.
There was a suggestion to use sammobile.com on the parallel thread, but it listed
the same bad T310UEUAMH2 as the factory image for Cellular south (XAR) - which
was exactly the latest updated image that I was having problems with - and after
spending the whole day on this investigation, I was not in the mood to try the UK
image suggested by lyall29 above. For the curious among us, here is the OS version
installed on the tablet that I just got from the store just a few miles away from Android
Central in Mountain View, California:
Galaxy Tab 3 8.0 SM-T310
Android version 4.2.2
Kernel 3.0.31-787812
[email protected] #1
Tue Jun 4 09:45:09 KST 2013
Build number JDQ39.T310UEUAMF2
What a difference one letter H instead of F can make...
@osokin...You made the best choice by returning it for a new one. Now the only problem with this tablet is, when we flash a custom recovery and root, there is now way to get back. Sure you can flash the stock recovery and unroot, but the status of the tablet is still custom. Therefore we can never get updates again, unless Chainfire supports the tab 3 with his triangle away tool. I have a jig but it did not work, maybe the jig is bad. Hopefully we can get a custom rom sometime soon. I tried but I can't do it. Oh well, no updates at all for those of us who are rooted.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hello.
11.11.2015 i recived a notification on phone that Elephone had released a new update to improve system functioning ect.
Keep in mind this is a stock p8000. nothing done with it.
I downloaded update, installed and it said phone will reboot.
After that phone is stuck in bootloader and simply wont boot.
Ive tried wiping cache and factory reset but PHONE WONT turn on.
So question is. What the hell do i do now?
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms. ?
This thread should be merged with other ones.
Have anyone found a solution?
pitrus- said:
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms.
This thread should be merged with other ones.
Click to expand...
Click to collapse
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
The Boards are full of Threads and solutions about this problem !
Why aren't you looking around a bit ?
How about the first post in Q&A section ???
http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203
StormiZMo said:
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
Click to expand...
Click to collapse
manually flash the stock rom .. i faced the same ****.. i followed the below steps and my elephone working fine
http://bbs.elephone.hk/thread-9229-1-1.html
hope this will work...
Fixed
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
StormiZMo said:
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
Click to expand...
Click to collapse
LOL, fired for what? it worked on most devices.
you get what you pay for! how are elephone selling a phone with decent specification for that price? they cut corners everywhere.
quality being 1 and skilled staff is the other.
with the given resources, their staff did they best they could with the test hardware they had.
StormiZMo said:
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
Click to expand...
Click to collapse
Also, most China phones don't even get updates, or even more exclusive, source code releases like this one. My guess is that there's likely only a one man show in charge of software development for this model, so give them some slack will you. [emoji1]
mine went off to after the OTA so i had to flash manually and like my friend said there trying, unlike most china phone company's so even though mine failed my father's and my friend's p8000 got there OTA np
It seems like the first 5000 batch delivered had no notification led,they seem to put in different hardware thats available.So end up with a hotch podge of slightly different devices.
So fingers crossed that a update works.Thankfully Elephone allows ,enables development.
It also looks like OTA update fails on rooted phones, which is not so different than what happens to most Android phones. When I used a Samsung phone long ago, OTA update notifications wouldn't even show up if you had rooted your phone, and on other phones I remember having a similar issue after I applied an OTA update with the phone rooted