Develop Bugs

Idea to get back to 3.70, possibly earlier?

Alright, not sure if this has been gone over or not. What would happen if a person complained enough to Sprint or HTC about how much they dislike the GB update, would they have a way to revert you back to Froyo. Tell them you are not at all happy with the new system and you want to undo the update. Would they just tell you to go pound sand? I am almost thinking it would have to be a direct complaint to HTC, not?

Send a email to H T C

I did shortly after making the post. Just trying to find out if anyone else had tried to appeal to them on it. I will post any response from them I receive.

Better yet, send them an email asking for them to put hot naked ladies for our backgrounds on our evos and also to root them for us. :-D

runcool said:
Better yet, send them an email asking for them to put hot naked ladies for our backgrounds on our evos and also to root them for us. :-D
Click to expand...
Click to collapse
Thought about that, but I figured that might be a little too obvious

legasus233 said:
Alright, not sure if this has been gone over or not. What would happen if a person complained enough to Sprint or HTC about how much they dislike the GB update, would they have a way to revert you back to Froyo. Tell them you are not at all happy with the new system and you want to undo the update. Would they just tell you to go pound sand? I am almost thinking it would have to be a direct complaint to HTC, not?
Click to expand...
Click to collapse
According to multiple sprint reps/techs that I have talked to, they do not have the tools to downgrade back to Froyo. Doubt calling HTC would help, they will probably just say since it is software, Sprint is responsible.

tgruendler said:
According to multiple sprint reps/techs that I have talked to, they do not have the tools to downgrade back to Froyo. Doubt calling HTC would help, they will probably just say since it is software, Sprint is responsible.
Click to expand...
Click to collapse
I guess I must have missed this somewhere, Sprint develops the software, not HTC? Now I'm officially confused!

been there, done that..
just go check out their tweeter feeds, lots of people DID complain
i personally spoke to a customer service guy , he fed me the "trying to downgrade would make your phone innoperable" line, and basically he said sprint doesnt have the capability to do it , and htc will simply claim not to be able to do it, you are welcome to do it though, enough complaining and maybe one of the higher ups decides its worht a listen , but to be honest, root will be here long before that happens, somone already found an exploit, its a matter of making stable and usable to the public

legasus233 said:
I guess I must have missed this somewhere, Sprint develops the software, not HTC? Now I'm officially confused!
Click to expand...
Click to collapse
partly true in the sense that sprint has final say on what software to push through to their users, htc develops the sense and phones firmware, but its sprints call on what final os will the devices use, wich is why the bloatware is most of the time uninstallable as its "part of the os" wich sprint pushed, htc makes it but sprint has the final say on approving it and adding whatever the hell they want to it (aka blocking hotspot and such) wich is understandable since they are the ones that have to deal with the customer

Sprint is full of criminals. :-D HTC attempts to do the right thing. :-D Sprint just keeps blocking them. HTC and myself know EXACTLY how to do it. lol. However, we are required by contract law not to spread it do to issues related to lack of a normal customers knowledge. :-D Any of you actually program chips and design circuit boards? What we do, is we find ways around the software... They really go into the chip itself.

No, but the final build that comes to our phone had sprints dirty hands all over it.
Swyped from my Supersonic

tgruendler said:
No, but the final build that comes to our phone had sprints dirty hands all over it.
Swyped from my Supersonic
Click to expand...
Click to collapse
I wouldn't put it past sprint employees to illegally put stuff on our phones that would monitor our use. They're that evil. muhahahhahaha

I called my local sprint store right after the ota and asked about downgrading back to froyo. The rep said that i would have to contact the local corporate store and that they could do it. So when i called they said "just bring the phone in here and we will get you back to 2.2" Now whether or not this is true, i dont know. I never took the ota so i'm still rooted. But for those of you that did take the ota or have a new evo you might give this a shot. Knoxville, TN

ak074 said:
I called my local sprint store right after the ota and asked about downgrading back to froyo. The rep said that i would have to contact the local corporate store and that they could do it. So when i called they said "just bring the phone in here and we will get you back to 2.2" Now whether or not this is true, i dont know. I never took the ota so i'm still rooted. But for those of you that did take the ota or have a new evo you might give this a shot. Knoxville, TN
Click to expand...
Click to collapse
99.99% chance the store is full of it. If that .01% chance proves true, Knoxville will be seeing a lot more tourism than they usually do.

bkrodgers said:
99.99% chance the store is full of it. If that .01% chance proves true, Knoxville will be seeing a lot more tourism than they usually do.
Click to expand...
Click to collapse
You are right about them being full of it. When I called again this morning they said absolutely not. She said that all of their software stuff has been updated to 2.3 but that if i had came immediately after the ota then she could have fixed it.

Here was HTC's reply:
Thank you for contacting HTC Technical support about the issues you are having with your device since getting the latest upgrade for it. I do apologize that you are having this issue with your device and I will gladly help you with this. There is no way to revert to the software version that was on the device before the update. I first suggest you do a soft reset by pulling the battery out for about 1 minute then placing the battery back in and booting up your device. If a soft reset does not resolve the issue then you may want to do a factory reset on your device to try to resolve the issue. Factory resetting your device will clear off your device and reset it back to factory settings. If factory resetting the device does not resolve the issue the next step would be to contact your carrier for possible repair or replacement of your device.

Man, that reply is nothing but a big middle finger from HTC.

legasus233 said:
Here was HTC's reply:
Thank you for contacting HTC Technical support about the issues you are having with your device since getting the latest upgrade for it. I do apologize that you are having this issue with your device and I will gladly help you with this. There is no way to revert to the software version that was on the device before the update. I first suggest you do a soft reset by pulling the battery out for about 1 minute then placing the battery back in and booting up your device. If a soft reset does not resolve the issue then you may want to do a factory reset on your device to try to resolve the issue. Factory resetting your device will clear off your device and reset it back to factory settings. If factory resetting the device does not resolve the issue the next step would be to contact your carrier for possible repair or replacement of your device.
Click to expand...
Click to collapse
LMAO
this is the exact response i got, only the guy said "downgrading would make your device innoperable" ....yeah...but the rest of it went exaclty like this ...jokes on them , because if you notice the increasing amoutn of new people on this forum, thats people that will never take an update from htc or their carriers ever again over this fiasco, i never even thought about rooting until i went to try and find a way to go back to froyo from this pos , ended up learing a lot about android and rooting ont his past month ive been waiting for this thing to be cracked , i hope they blew it wide open and they soon add support for our beloved og evo but for now we play the waiting game

OTA update Fix new for O2 Phones/Customers

Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later

JustinL01 said:
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
Click to expand...
Click to collapse
Very nice if it turns out to be true

That is actually smart move releasing to just 1k handsets to avoid any mass problems.

From what i understood the O2 phones firmware was the same as the sim frees/all the others, meaning o2 wont even be involved in ANY updates , that they'll all just come direct from Google.(that has to be good news)
Nice to know it's on the way though, although i've yet to experience the problem in "real life" and not having to put another phone 2mm away from it.

rbs_uk said:
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
Click to expand...
Click to collapse
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?

oscillik said:
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
Click to expand...
Click to collapse
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.

rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
Hmmm I personally doubt it, since the firmware is supposed to be un-tied to carrier tinkering.
If the carriers are aware of what firmware any of it's customers handsets are running, that raises another worrying issue. But I really don't think that they are capable of finding this out.
As an aside, I used to work for the UK's largest pub gaming machine company, and we had the largest network of computer-based touchscreen gaming machines (at the time at least) and they all ran a custom java based software running on top of Windows. When we made updates to the games or anything else, we would always roll out the update to 1000 machines as a preliminary measure.
The difference there however is that we knew exactly which machines had the updates, and could keep track of any issues that popped up. I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).

Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed

oscillik said:
I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Click to expand...
Click to collapse
could be.. as you'd think atleast 1 of the 1000 would have posted here on XDA
**edit**
post above proves me wrong - although my android version is 4.0.1 and i have had no update

drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
The HSPA+ version of the Galaxy Nexus has always had 4.0.1, so you haven't received any update at all.

I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.

rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
It would likely go to Google, not O2, and is IMEI based, so they will know how many and which handsets have received the update. They will log the IMEIs that the update was sent to and if you call your various support options with a complaint one of the questions will certainly be your IMEI number. Then this can be cross-referenced to see if you have received the update or not (and evaluate 1. it's success 2. other problems it generated).
When the phone's IMEI gets released for the OTA, there is a "whisper" service that checks the software/whatever version and if below the impending OTA it will prompt the notification for the update- if the same it will send no notification and the user will have no idea of/no need for the OTA. At least this is generally how the G1 and N1 both worked in the past.

JustinL01 said:
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
Click to expand...
Click to collapse
He never mentioned what build number he had, as you can see he just mentions Android version:
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse

I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...

They all say 'Android is updating' everytime you power the phone on ;-)

oscillik said:
He never mentioned what build number he had, as you can see he just mentions Android version:
Click to expand...
Click to collapse
No not the poster I am talking about what I was advised by O2, it is the buildnumber that differed with the update.

drp297 said:
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
Click to expand...
Click to collapse
Ice Cream Sandwich does that. Everyone's phone does that, it's already been raised on here in at least two separate threads.
It doesn't mean you have received an Android update, it is regarding Android getting the home screen and apps ready.
an OTA update would require user intervention to be applied - you would have to first of all agree to the phone downloading and applying the update.

Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)

gambiting said:
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
Click to expand...
Click to collapse
It was due 5pm yesterday too. Fingers firmly uncrossed, only a single digit is required aimed squarely at sam/goog.

I heard that they are updating the baseband, not the software version...

The ROM who has killed my screen's NOTE 2

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 am thinking in either selling this or just update to official

I haven't been able to fully take advantage of my rooted phone and I get tired of re reading and trying to use other roms and doing back up and always finding myself clueless and returning here to ask you guys what where the steps by steps guide.
I can't get another phone yet because I have a contract with AT&T and it will take a few more months.
I am using SlimBean rom probably a very old version and I haven't update it yet and well I get many bugs and other issues such as my pho0ne restarting when playing videos on full screen.
Sometimes I feel desperate and just want to restart from scratch and unroot the phone by installing the latest update of the official phone.
So, the phone is practically unscratched and well taken cared if any of you are interested.
Suggestions are welcome.

Asking price? Age of phone?

audit13 said:
Asking price? Age of phone?
Click to expand...
Click to collapse
Make your offer.
Age would be... around 2 years or so...

Harkadenn said:
Make your offer.
Age would be... around 2 years or so...
Click to expand...
Click to collapse
I would except I am in Canada and you're probably in the USA.

Harkadenn said:
I haven't been able to fully take advantage of my rooted phone and I get tired of re reading and trying to use other roms and doing back up and always finding myself clueless and returning here to ask you guys what where the steps by steps guide.
I can't get another phone yet because I have a contract with AT&T and it will take a few more months.
I am using SlimBean rom probably a very old version and I haven't update it yet and well I get many bugs and other issues such as my pho0ne restarting when playing videos on full screen.
Sometimes I feel desperate and just want to restart from scratch and unroot the phone by installing the latest update of the official phone.
So, the phone is practically unscratched and well taken cared if any of you are interested.
Suggestions are welcome.
Click to expand...
Click to collapse
Have you tried going to Swappa.com? You'd probably get a better selling price there than on places like that online auction site. Plus you don't pay any fees and it's the XDA recommended option for buying and selling phones.
Seriously though, you may want to revert to a full stock ROM to fix the performance issues. Reverting to a stock ROM would often let you know if any performance issues are firmware or hardware based as different custom ROMs often come with their peculiar issues.

Root in the Future

As many of you know the Nokia 8.1 is probably not going to get a method for a unlocked bootloader since H.M.D global shut down the exploit/way to aquire it.
I was wondering if there would be any reason that my beloved 8.1 couldn't be rooted by apps like Kingroot when they get the ability to root android PIE.
I didn't realize upon buying the phone that Nokia was so against rooting and im kinda bummed out that as of yet the phone isn't rootable yet. Might even trade it for a Pocophone and take the lack of NFC for granted

Do have mine unlocked and rooted. But the root is a messy task which will most likely take away OTA updates because any tampering is an end to the incremental OTA. Then flashing stock is a tough task too, because the awesome people at FIH Mobile forgot to disable fuse when bl is unlocked. Also, the process is kinda complicated and still under testing Given the complication, I'm sure it won't be freely available because it starts off by using paid tools to trigger debug mode.

I really didn't know that there's almost no way to root this phone when I bought it 2 months ago, but luckily the only reason I've rooted my previous phone (Mi A1) was because of Gcam which is supported out of the box on this one. So it's fine for me, but I do see that no rooting method could be an issue for some people.
Sent from my Nokia 8.1 using Tapatalk

I have already replaced the phone because of lack of root / development for this phone. Hated the stock ROM because lots of things didnt work with it (samsung gear watch, some wireless APs, car navigation, etc etc) and without the development this would never be solved.
Also I have expected better camera for the price of the phone.
WIll never buy any HMD device ever again.

nitko666 said:
I have already replaced the phone because of lack of root / development for this phone. Hated the stock ROM because lots of things didnt work with it (samsung gear watch, some wireless APs, car navigation, etc etc) and without the development this would never be solved.
Also I have expected better camera for the price of the phone.
WIll never buy any HMD device ever again.
Click to expand...
Click to collapse
Really !! this is surprise for me
I must have searched and read all forum on xda before buying this phone.
hope some body will post some steps to root it.
I read somewhere that some guys was able to root it.
hope I do not have to sell it.

looks like not much active forum for our device.
less people with this device.

light.apps said:
looks like not much active forum for our device.
less people with this device.
Click to expand...
Click to collapse
Looks like not many want to ruin their brand new phone.

Nollie8969 said:
Looks like not many want to ruin their brand new phone.
Click to expand...
Click to collapse
XDA is all about root and ROMs
Every one clever would find out first BEFORE buy Nokia phones about the impossibility of rooting those.
I'm sure when root is possible in future ( some geek will find a way, its a phone and not a high end secure government secret thing lol ) more pple will come see this thread.
Mark my words :good:

You're right. At the end of the update cycle I like to install LOS or likewise. Not for the sake for Adaway only.

Nollie8969 said:
You're right. At the end of the update cycle I like to install LOS or likewise. Not for the sake for Adaway only.
Click to expand...
Click to collapse
Agree.
Just like what we're doing at home. We're using Samsung Note 3 (Cyanogenmod rom) as online phone for local line. Before that, the phone with default OS was too lagging and cannot even install the online phone app I need.

andreoide said:
XDA is all about root and ROMs
Every one clever would find out first BEFORE buy Nokia phones about the impossibility of rooting those.
I'm sure when root is possible in future ( some geek will find a way, its a phone and not a high end secure government secret thing lol ) more pple will come see this thread.
Mark my words :good:
Click to expand...
Click to collapse
well said :good:

Motorola/Lenovo seems to be the last castle of root/development.
I was an early adopter of G7 (I bought it on initial release). As soon as BL unlock support added, BAM! rooted!
How easy it was and I am not developer

singhnsk said:
Do have mine unlocked and rooted. But the root is a messy task which will most likely take away OTA updates because any tampering is an end to the incremental OTA. Then flashing stock is a tough task too, because the awesome people at FIH Mobile forgot to disable fuse when bl is unlocked. Also, the process is kinda complicated and still under testing Given the complication, I'm sure it won't be freely available because it starts off by using paid tools to trigger debug mode.
Click to expand...
Click to collapse
Bro, can you please explain about how to root my nokia 8.1