Related
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.
I was running the tweeked rom on my Note 2 and was loving it, was running great for a few days...
Today the screen froze when I went to unlock and check a missed call. I am unable to get any response from my finger, nothing... The S pen does work though.
T-mobile tech knew nothing about how to fix it. I tried a different rom and still the same.
Any suggestions? Calibration? Anything? Thanks so much.
As it exists across roms, it regrettably sounds like a hardware issue. Have you tried flashing a stock odin? Likely won't help but it might be worth a shot.
dwitherell said:
As it exists across roms, it regrettably sounds like a hardware issue. Have you tried flashing a stock odin? Likely won't help but it might be worth a shot.
Click to expand...
Click to collapse
Thanks for the reply. I am afraid that is a pretty big problem too, related to hardware. 10 minutes before the finger freeze I was just realizing how much I loved the phone with the Tweaked Rom and totally set-up.
Anyways, it's going back to T-mobile. I used Odin to flash to stock and used Triangle Way to reset the flasher... Now I am scared to root it and run a rom on the new one, but I know it was just a freak incident...
Just sucks, I hate getting a refurb replacement... I don't know what dirty, grungy, smelly pocket it's been in for a couple months, uh...
I had an issue on my first note 2 where the top right and left of the screen couldnt register the s pen, had to send the phone back. I flashed jedi as soon as i got the second one and been happy ever since.
Moral of the story, DONT WORRY AND FLASH AWAY. ur right, it was a freak accident and it wont happen again.
Sent from my SGH-T889 using XDA Premium HD app
moabizzi said:
I had an issue on my first note 2 where the top right and left of the screen couldnt register the s pen, had to send the phone back. I flashed jedi as soon as i got the second one and been happy ever since.
Moral of the story, DONT WORRY AND FLASH AWAY. ur right, it was a freak accident and it wont happen again.
Sent from my SGH-T889 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, appreciate the help... I will definitely flash away and have fun with the new phone.
So today I bought a new Note 2 (SGH-i317M) on Bell Mobility Canada, as I was having issues with my first one. The first one had been rooted, and had a couple different roms on it. The last week or so my reception has been atrocious and constantly in "emergency calls only" mode, so I said "forget it" get a new one, send in the old one and sell it to my buddy when it gets back.
I managed to get a stock recovery and a stock rom on the old Note 2 using Samsung Galaxy Note2 Toolkit. Now, this is where it goes wonky and not sure what happened.
Upon initially getting the stock rom (4.1.1) on it, I noticed another update in the notification tray. At this point my SIM card has been pulled and I am using only wifi on it. I jumped on the update thinking cool my device isn't "modified" anymore, so I will take this update ( to 4.1.2)
After doing that update, I looked in my app drawer and it has 6 or 7 Roger's bloat apps in it, and the kernel version was different. Otherwise baseband, build and Android version are the same Not sure if it happened when I installed the stock rom from the Toolkit process or if the Roger's apps came with the OTA update to 4.1.2.
The problem is, this makes it hard to take a phone back to Bell for repairs with Roger's system apps in it. I've tried flashing the stock rom from the Toolkit via Odin again but there is still Roger's bloat there.
I have no idea what to do now. I pretty much used up all my brain power today getting this far. Could someone point me in the right direction, I would appreciate it greatly.
Thanks ahead of time for any responses, I've been at this most of the day now and I am just out of ideas now. :silly:
If you are getting rogers apps in a fresh flash via Odin...then you likely have the wrong rom being flashed....(it happens)
Look in the "Everything thread" in the development section for the stock bell firmware. this is the bell stock firmware from the thread...I pulled it for you...http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
That rom is the link from the everything thread...
You are the second user this week that has flashed a mis-labeled rom from the kit...
Once bell is flashed, your rogers apps will go away...
Remember to wipe all data and caches in the stock recovery before booting the new rom....g
U need to change ur csc, all stock Canadian fw is the same... it will show bell bloat till u enter the proper csc.
Hopfully this helps http://forum.xda-developers.com/showthread.php?t=1988202
And this http://forum.xda-developers.com/showthread.php?t=2004029
twanskys204 said:
U need to change ur csc, all stock Canadian fw is the same... it will show bell bloat till u enter the proper csc.
Hopfully this helps http://forum.xda-developers.com/showthread.php?t=1988202
And this http://forum.xda-developers.com/showthread.php?t=2004029
Click to expand...
Click to collapse
+1 csc will give you right firmware i always use Samsung Galaxy S csc from pstore. Just choose your carrier and no need to flash firmware again.
https://play.google.com/store/apps/details?id=com.manniakk.cscselector
Sent from my SGH-I317M
gregsarg said:
If you are getting rogers apps in a fresh flash via Odin...then you likely have the wrong rom being flashed....(it happens)
Look in the "Everything thread" in the development section for the stock bell firmware. this is the bell stock firmware from the thread...I pulled it for you...http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
That rom is the link from the everything thread...
You are the second user this week that has flashed a mis-labeled rom from the kit...
Once bell is flashed, your rogers apps will go away...
Remember to wipe all data and caches in the stock recovery before booting the new rom....g
Click to expand...
Click to collapse
Thanks so much. I wish found that earlier.
As well as this.........
twanskys204 said:
U need to change ur csc, all stock Canadian fw is the same... it will show bell bloat till u enter the proper csc.
Hopfully this helps http://forum.xda-developers.com/showthread.php?t=1988202
And this http://forum.xda-developers.com/showthread.php?t=2004029
Click to expand...
Click to collapse
Which may have lead to this......
jon3sh said:
+1 csc will give you right firmware i always use Samsung Galaxy S csc from pstore. Just choose your carrier and no need to flash firmware again.
https://play.google.com/store/apps/details?id=com.manniakk.cscselector
Sent from my SGH-I317M
Click to expand...
Click to collapse
Thanks so much guys. This experience has really stumped me.
I did however manage to get this sorted in the mean time. I installed a custom recovery back in, did a full system wipe the put in a rom that supports Canadian variants (tell ya the truth can't even remember it's name) and in that install process it had an aroma installer. One of the options was to adjust CSC for your desired carrier. After I set it up, I started the intitial process of wiping, and flashing and such over and voila I had all Bell apps and no Rogers apps.
But, in the meantime, the wifi decided to do its hanging thing again and for the last 3 hours or so I have been trying to get Triangle Away running on it. The app requires more data to work with my phone, but as this phone doesn't have a registered SIM and the wifi wont start now I have to manage a way to get it working, reset my binary count, unroot and verify and be done with it.
I greatly appreciate your guys input and will be reading as much as possible. Generally I can go flash crazy with custom roms but Odin messes me up.
I hope others see this thread and don't do what I did, and learn about CSC before they get hung up. Thanks again guys.
p.s. my brain hurts
OK. I officially give up. This 5 month old phone is going in the garbage. If it isn't one thing, it's another. Managed to get the wifi (and BT which I didn't know at first wasnt working) by inserting my new phones SIM. Blam, both worked. Great, now I can install Triangle Away, do my thing, reflash the stock firmware and I'm good.
And now.............the Toolkit won't recognize ADB enabled. I have been at this for over 24 hours now and it's been one roadblock after another.
I am officially McGyver'ed out :crying:
Idk what ur doing wrong but, doing a freash install should fix ur issues..
twanskys204 said:
Idk what ur doing wrong but, doing a freash install should fix ur issues..
Click to expand...
Click to collapse
Right on. Ya I kinda gathered my thoughts and buckled down and started over. So, now I have what appears be the proper firmware on my older Note 2.
Version: 4.1.1
baseband: i317MVLAJ2
kernel: 3.0.31-262790 / [email protected] #1 / SMP PREEMPT wed Oct 3 ........2012
build: JRO03C.I317MVLAJ2
Device Status: Normal
It seems like the exact same software as when I first cracked my new one out the box. After I updated it, the newer one now has:
Version: 4.1.2
baseband: I317MVLBMA3
kernel: 3.0.31-262790 / [email protected] #1 / SMP PREEMPT wed Oct 3..........2012
build: JZ054K.I317MVLBMA3
Pretty sure I got all the numbers right lol.
Still trying to figure out what to do now for Triangle Away, and making this phone seem like it's never been touched. Thanks for your help so far.
Root with cf root ,,run triangle away then do what u just did
twanskys204 said:
Root with cf root ,,run triangle away then do what u just did
Click to expand...
Click to collapse
CF Root. OK I will check it out. Thank you ! I will let ya know how it goes. I appreciate this as it just seems like there is just way too much Note 2 info out there. Thanks for the filter lol !
Update. Well that did it. In the "Download" screen it is saying;
-Custom binary download: No
-Current Binary: Samsung Official
-System Status: Official
In Settings, the device status is Normal
As far as my research has gotten me, my understanding is that I should now be able to send it in with out any warranty issues. My wifi and BT are acting hinky again but I may try my SIM swap again and see if that helps, before I send it away.
Thank you so much for your help. That suggestion of CF Auto-Root helped big time!!!!!
No problem. . Get some rest and hit it up in the morning. .
Valkillmore said:
Update. Well that did it. In the "Download" screen it is saying;
-Custom binary download: No
-Current Binary: Samsung Official
-System Status: Official
In Settings, the device status is Normal
As far as my research has gotten me, my understanding is that I should now be able to send it in with out any warranty issues. My wifi and BT are acting hinky again but I may try my SIM swap again and see if that helps, before I send it away.
Thank you so much for your help. That suggestion of CF Auto-Root helped big time!!!!!
Click to expand...
Click to collapse
Next time you are flashing stock rom for your phone just use rom from link below so you dont need to worry about rooting after. Roms are root injected already and good to go.
http://forum.xda-developers.com/showthread.php?t=2004650
Sent from my SGH-I317M
jon3sh said:
Next time you are flashing stock rom for your phone just use rom from link below so you dont need to worry about rooting after. Roms are root injected already and good to go.
http://forum.xda-developers.com/showthread.php?t=2004650
Sent from my SGH-I317M
Click to expand...
Click to collapse
Nice ! Ya I found the same root injected bell rom but unfortunately it was after I wanted to uninstall and unroot. I will be taking this approach from now on. Thank you good sir!!
I appreciate everyone's patience because I was certainly runnIngl out of it . Going to get the old Note 2 packed up and shipped off sometime today. Again all help greatly appreciated guys .
To add to my ordeal going on now, I did notice that my first Note 2 was made in China, and feels sloppy. Like the battery is slightly loose, and like the assembly just doesn't feel tight. I had to slip a piece of folded paper in behind the battery as the phone always rebooted even just gently dropping it on the table.
My brand new Note 2 I noticed was made in Korea. The battery is seated much, much better, and the phone itself feels like it was put together in a factory, not a car garage.
I am wondering if this is what is going on, because today after messing with the old one (which is now OTA'd to 4.1.2 *thanks again guys!*), and having the same persistent wifi hanging issue (not turning on and not really turning off, just suspended) and BT not wanting to turn on, alongside its original problem of poor cell reception......I thought I wonder if something is just hinky/loose or whatever. So I picked the phone up, dropped it flat on its back (in a case lol) from about 8 inches in the air, onto my coffee table. Opened the notification tray, and tapped the wifi toggle and it instantly turn on, bright lime and I was able to see available networks. The BT turned on immediately after pressing it too. Can't speak on cell signal, and it may well just be coincidence, but after several wipe/flash processes and BT and wifi acting hinky across several factory resets etc, then immediately working after the drop.......strange indeed.
More convinced now than ever that I have had somewhat of a lemon the whole time as I have had weird issues with reception for a long time from in the house to out in the world. The phone has never been seriously dropped and anytime it did slip it was in an Urban Armor Gear case, screen is near mint (didnt have protector first week) , and should be absolutely zero water damage.
Valkillmore said:
To add to my ordeal going on now, I did notice that my first Note 2 was made in China, and feels sloppy. Like the battery is slightly loose, and like the assembly just doesn't feel tight. I had to slip a piece of folded paper in behind the battery as the phone always rebooted even just gently dropping it on the table.
My brand new Note 2 I noticed was made in Korea. The battery is seated much, much better, and the phone itself feels like it was put together in a factory, not a car garage.
I am wondering if this is what is going on, because today after messing with the old one (which is now OTA'd to 4.1.2 *thanks again guys!*), and having the same persistent wifi hanging issue (not turning on and not really turning off, just suspended) and BT not wanting to turn on, alongside its original problem of poor cell reception......I thought I wonder if something is just hinky/loose or whatever. So I picked the phone up, dropped it flat on its back (in a case lol) from about 8 inches in the air, onto my coffee table. Opened the notification tray, and tapped the wifi toggle and it instantly turn on, bright lime and I was able to see available networks. The BT turned on immediately after pressing it too. Can't speak on cell signal, and it may well just be coincidence, but after several wipe/flash processes and BT and wifi acting hinky across several factory resets etc, then immediately working after the drop.......strange indeed.
More convinced now than ever that I have had somewhat of a lemon the whole time as I have had weird issues with reception for a long time from in the house to out in the world. The phone has never been seriously dropped and anytime it did slip it was in an Urban Armor Gear case, screen is near mint (didnt have protector first week) , and should be absolutely zero water damage.
Click to expand...
Click to collapse
Flash away now
Sent from my SGH-I317M
jon3sh said:
Flash away now
Sent from my SGH-I317M
Click to expand...
Click to collapse
Well, I was thinking that, but seeing it's under warranty, I am going to see what happens at Samsung. Hopefully they don't have some new way of seeing its been customed *face palm* lol and just replace it, even if its with a working factory rebuild or whatever. As I had to purchase both devices out right, and I live in Canada, I may be able to buy a car with the money.......holy crap its expensive up here.
Nearly $800 for each one. Ridiculous lol
EDIT: It would be a crappy car, but a car none the less
Ya , im up in canada also.. mine was 840 when it first came out. I payed it right out and unlocked it.
Mind u my build quality is excellent, maybe except for the sqeeky back.
But no problems none the less.:thumbup:
Sent from my SGH-I317 using Tapatalk 2
twanskys204 said:
Ya , im up in canada also.. mine was 840 when it first came out. I payed it right out and unlocked it.
Mind u my build quality is excellent, maybe except for the sqeeky back.
But no problems none the less.:thumbup:
Sent from my SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Ya it is just ridiculous the costs up here, and I live up in northern BC so everything is just a little more than everywher else as expensive at it is already, UGH !
I wonder if there is a new batch shipped because like I said, the one I bought 5 months ago was made in China, and like you say "squeeky". Loose. And big difference in at least mobile data / cell radio performance between my two devices.
This new one made in Korea, even the older battery slides in nice and tight. No squeaky back. Just feels tighter, even the S-Pen. It was always kind of loose on the older Note and even tossing the phone onto the table sometimes dislodged it. Even my camera lense on my older one seemed like it was mounted weird. I'd prefer stuff domestic if possible but I sure notice a difference between the Korean manufactured and the Chinese manufactured.
But I have a feeling I may be sending it back right away if service is as useless as it is everywhere else nowadays. I noticed after getting home on the work order it says
Wifi not connecting
BT not connecting
etc
Well, it was not that BT or wifi wouldn't connect. They connect to my devces/network immediately, BUT if and only if they actually turn on. The toggle stays half lit, and the wifi would say "turning on" then simply shut off a minute later. And the BT just wouldn't turn on at all, UNTIL I "dropped fixed" them this morning.
She also forgot to add that the S-Pen is totally haywire. I think that may be simply a sensitivy calibration issue I could maybe fix myself from YouTube vids I've seen. Just never got to it with other issues. I just hope the tech that checks it isnt as useless as I am picturing them in my mind and they show initiative and actually check the whole phone. Dream on I'm thinking HA !
Valkillmore said:
Ya it is just ridiculous the costs up here, and I live up in northern BC so everything is just a little more than everywher else as expensive at it is already, UGH !!
Click to expand...
Click to collapse
I have to agree Valkillmore, northern BC has horrible pricing. I have had mine since January on Telus and also had strange problems with the radios.
My wireless randomly drops my home wifi signal, regardless of which frequency it uses. This started just the other day and I actually hadn't done any flashing or updates in a few days. Seems strange that it would start now.
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
Years owned : Since 2012
Model : SGH-L317
Carrier : AT&T
Good Morning, everyone.
I've had my note 2 since 2012 and I didn't have an issue until now. The phone is rooted (I believe it was CleanRom Ace with the Apex Settings thing), and as the title says it, I guess it was time the phone finally got some kind major error and it started with freezing on the logo screen when booted. I thought maybe I leave it like that overnight , so I wake up, completely dead now its stuck on battery screen logo. I think I can still get access to the menu (hold home,volume down and power button) where i can access odin. No recovery mode..no nada =/...
So I need to know if this is just a battery issue or maybe its time that I set this to factory settings? But I still want it rooted.. Please help everyone. I understand most of this so I just need a boost of confidence from everyone and know if this is possible to fix. Thank you very much!
Adam.
Had similar issue with note 10.1 tab, turned out the storage became corrupted, now it's just a nice paper weight.... Best of luck thou-
Sent from my Nexus 6 using Tapatalk
johng75 said:
Had similar issue with note 10.1 tab, turned out the storage became corrupted, now it's just a nice paper weight.... Best of luck thou-
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah. I think its really just flashing this and what not. But i really need someone here who's been through this problem and point me to a thread where it directions from A-Z. That's all . I can do the rest.
beatsme2 said:
Yeah. I think its really just flashing this and what not. But i really need someone here who's been through this problem and point me to a thread where it directions from A-Z. That's all . I can do the rest.
Click to expand...
Click to collapse
Well the thing about this note 2 is that it's been pretty much indestructible. I've had to Odin back to stock, flash chainfires files and start over. So is suggest that. Odin back to stock and start over. Ps google is your friend
rhaneyjr said:
Well the thing about this note 2 is that it's been pretty much indestructible. I've had to Odin back to stock, flash chainfires files and start over. So is suggest that. Odin back to stock and start over. Ps google is your friend
Click to expand...
Click to collapse
all due respect, they were my friend, they wouldn't guide me to a bunch of sites that really has no significant answer. It's like i said, I used many versions of Odin. it just doesn't wanna work. I got those Pit at mapping messages and... yea. That's pretty much the end of it.
EDIT : i made another thread about it , so someone should close this.