Hi guys i ever modded my phones since my first android phone, my life without a custom rom and a kernel set up ad hoc, is not the same.
I want to mod my s6, but, I'ts a big deal? Pro: a phone smooth Cons: No guarante. The guaramte repair only fault of phone caused by itself, but i really fear, because i use to repair my phone my self, and last time, my g2 was died without a real motivation, but the guarante was avoid because of the battery change by myself.
Finally: I like this phone, the thing that make me want to mod it, is that a processor like this, should be more fast and whitout any tipe of lag.
With a modded rom how is the situation? It's a deal?
hi used this to not trip knox but u lose fingerprint
http://forum.xda-developers.com/galaxy-s6-edge/general/howto-flash-g92xf-t-tripping-knox-t3158606
READ carefully and all details (twice )
ham4ever said:
hi used this to not trip knox but u lose fingerprint
http://forum.xda-developers.com/galaxy-s6-edge/general/howto-flash-g92xf-t-tripping-knox-t3158606
READ carefully and all details (twice )
Click to expand...
Click to collapse
Can I flash all types of rom?
Edoardo001 said:
Can I flash all types of rom?
Click to expand...
Click to collapse
Yes u can but don't flash any new bootloader except the one in that thread I gave you
Related
hi
guys i did read around could not find any answers may be i missed it sorry
but my question is after rooted adding CWM and custome rom is their a way to lock the bootloader and getting back the stock rom just in case if needed for warranty purposes
yes i do know that on unlocking the bootloader warranty is void but then our service guys here at least at my place are not all that techie so im sure we can get away with this :laugh:
thanks in advance:laugh: and sorry if this has been asked and answered i did not see it
Yep, here http://forum.xda-developers.com/showthread.php?t=1569430 , but so far I didn't find anywhere on how to lock the bootloader properly, you can just make it "Re-locked", if you can put this past them, it's fine I tested two of them cos needed to use warranty. Keep in mind thou that services in my country, are rubbish, so I can get away with almost everithing.
shortyoko said:
Yep, here http://forum.xda-developers.com/showthread.php?t=1569430 , but so far I didn't find anywhere on how to lock the bootloader properly, you can just make it "Re-locked", if you can put this past them, it's fine I tested two of them cos needed to use warranty. Keep in mind thou that services in my country, are rubbish, so I can get away with almost everithing.
Click to expand...
Click to collapse
hi
thanks again buddy ill chek it out and the same thing here with the service i know i can get past them they dont know anything about these things:laugh:
haree said:
hi
guys i did read around could not find any answers may be i missed it sorry
but my question is after rooted adding CWM and custome rom is their a way to lock the bootloader and getting back the stock rom just in case if needed for warranty purposes
yes i do know that on unlocking the bootloader warranty is void but then our service guys here at least at my place are not all that techie so im sure we can get away with this :laugh:
thanks in advance:laugh: and sorry if this has been asked and answered i did not see it
Click to expand...
Click to collapse
There is one way to get guarantee back flash stock rom and lock your boot loader don't flash roms on locked boot loader u will stuck at htc logo try at your own risk risk of hard brick
Just stay away from warranty. Non-HTC repair shops will fix issues for a low price. Unless they are idiots who think a custom ROM causes my power button to go crazy after dropping my phone.
About bricks, I don't think we can do USB UART to make an unbrickable phone, but I've been messing a lot with my phone lately and haven't had it hard bricked yet.
xpmode said:
Just stay away from warranty. Non-HTC repair shops will fix issues for a low price. Unless they are idiots who think a custom ROM causes my power button to go crazy after dropping my phone.
About bricks, I don't think we can do USB UART to make an unbrickable phone, but I've been messing a lot with my phone lately and haven't had it hard bricked yet.
Click to expand...
Click to collapse
What is USB UART ????????
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
lozohcum said:
Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
Click to expand...
Click to collapse
If i relock bootloader and go back to stock, will this regain me warranty?
It may give you big chance that they will take it to warranty.
lozohcum said:
It may give you big chance that they will take it to warranty.
Click to expand...
Click to collapse
Im sending it in after hollidays ( approx 2 weeks, still need music on the plane ) and I'll let you guys know.
No need fo dat.
There must be a better solution
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
JonoIrwinRSA said:
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
Click to expand...
Click to collapse
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Click to expand...
Click to collapse
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Thanks for the info kurotsugi! Lock status = full lock and I've flashed it about 20 times with different roms in different ways. This one isn't coming back
I hope someone comes up with a solution soon. There must be many people with the same problem. Also I hope the issue gets stickied a bit more - I'm not blaming anyone but myself, I know the dangers of flashing, however I never knew of the issue until it was too late.
Jono
Sent from my GT-I9500 using XDA Premium 4 mobile app
kurotsugi said:
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Click to expand...
Click to collapse
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
lozohcum said:
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
Click to expand...
Click to collapse
It's (i think) not in the TA partition, because I had a TA backup from my phone and it didn't unlock again after restoring it.
http://forum.xda-developers.com/showthread.php?t=2550120
It's supposed to let you to be able to install custom roms and mods without tripping knox counter (for sure it does not revert the counter if it's triggered).
Personally i'm not able to test it cause atm my phone is at the service center for 3 weeks (sic) but i'd like to ask to xdaians if somebody has used it and if it works ok in our phone!!!
Waiting for your opinions!!!
:highfive:
interesting, waiting for result.
In theory you should only have to use a thing like this once, to get a custom recoveyr installed. From there you should be able to do anything you want.
The thread does say it SHOULD work for any Samsung device. Does anyone have the stones to try it? Maybe someone who has a broken S4 or one with a bad IMEI or something that's already relatively worthless?
Skipjacks said:
In theory you should only have to use a thing like this once, to get a custom recoveyr installed. From there you should be able to do anything you want.
The thread does say it SHOULD work for any Samsung device. Does anyone have the stones to try it? Maybe someone who has a broken S4 or one with a bad IMEI or something that's already relatively worthless?
Click to expand...
Click to collapse
"This script allows you to install custom roms, and mods that you would normally have to flash with custom recovery".
Looks like that the script does not allow u to install custom rec. but lets u install custom rom. It also looks like that u can use more than once because there's nothing written about it. And as u mentioned it's supposed to work in any Samsung... It looks interesting... I think that when my motherboard is repaired i'll try it... (after some weeks checking that my phone works ok for sure )
I wish i could get some opinions when i have my phone back!!!
Cheers all!!!
Indha Lezzio said:
It also looks like that u can use more than once because there's nothing written about it.
Click to expand...
Click to collapse
No no...I'm saying you shouldn't HAVE to use it more than once.
If it works once, you will have a rooted phone. FRom there you can flash recoveies and roms all day long.
It's just like Odin. Unless something goes wrong and you have to do a full flash back to stock, you only need Odin to root your phone once. After that it stays rooted and you can do almost anything from the phone itself.
That's good because this script is more complicated than normal flashing. So it's good that you would only need it the first time.
So I have a problem with my phone [d2303] is just indicating that there is no SIM card. This ONLY happens on the stock lollipop rom. I'm currently on slimrom to test it but I will revert to stock. No the cyanogenmod rom isn't stable enough for me and I don't like kitkat even dough it fixes problems such as bad camera quality... And NO tis isn't just me. I know someone with the same problems but on KitKat ( he's too lazy to update). Recently I've been also getting some errors while moving files to SD card (with the automatic function and manualy). If it helps I can post some screenshots of the problems if it helps....
I'm starting to get frstrated with this phone and is it a software or hardware problem? Should I take it to service and if so will they accept my phone because I have allredy unlocked my bootloader? Is there an efficient method of relocking a bootloader (links to posts are enough)? I've used the flastool method to unlock the bootloader on my phone(link- http://forum.xda-developers.com/showthread.php?t=2743694).
Is anyone having the same problems?
I also have some experience in rooting and installing costom roms on a few phones so if you know a software solution or a fix I won't have problems installing it.
I am thankful for you at least reading this thread. Also thank you for all your responses in advance.
slole said:
So I have a problem with my phone [d2303] is just indicating that there is no SIM card. This ONLY happens on the stock lollipop rom. I'm currently on slimrom to test it but I will revert to stock. No the cyanogenmod rom isn't stable enough for me and I don't like kitkat even dough it fixes problems such as bad camera quality... And NO tis isn't just me. I know someone with the same problems but on KitKat ( he's too lazy to update). Recently I've been also getting some errors while moving files to SD card (with the automatic function and manualy). If it helps I can post some screenshots of the problems if it helps....
I'm starting to get frstrated with this phone and is it a software or hardware problem? Should I take it to service and if so will they accept my phone because I have allredy unlocked my bootloader? Is there an efficient method of relocking a bootloader (links to posts are enough)? I've used the flastool method to unlock the bootloader on my phone(link- http://forum.xda-developers.com/showthread.php?t=2743694).
Is anyone having the same problems?
I also have some experience in rooting and installing costom roms on a few phones so if you know a software solution or a fix I won't have problems installing it.
I am thankful for you at least reading this thread. Also thank you for all your responses in advance.
Click to expand...
Click to collapse
Did you used flash ftf? I think main reason is you didn't flashed baseband. If this still happens, go to the service with relocking bootloader. I went to the service for dead pixel with relocking bootloader, they swapped my device.
This started appearing before I flashed any rom or unlocked the bootloader, so basically when the phone was stock. Also I'm not sure what is a baseband. I flashed a tft from a xda post with a youtube video with downloads for all android versions and xpria m2 models. The problem seems to be less frequent if I don't use the phone as much. I'll tryt his method: [It's on techbeasts but i'm not alowed to link outside links yet] to restore to stock and relock bootloader maybe even kitat since it has better camera quality. If the problem doesn't go away I'll take the phone to service because I want a reliable phone.
Thanks for the reply I almost gave up on this post. I saw a lot views but no replies this might mean that a lot of people have the same problem.
I'll also post some status updates about my problem so this post can be as an instruction to people with the same problem.
slole said:
This started appearing before I flashed any rom or unlocked the bootloader, so basically when the phone was stock. Also I'm not sure what is a baseband. I flashed a tft from a xda post with a youtube video with downloads for all android versions and xpria m2 models. The problem seems to be less frequent if I don't use the phone as much. I'll tryt his method: [It's on techbeasts but i'm not alowed to link outside links yet] to restore to stock and relock bootloader maybe even kitat since it has better camera quality. If the problem doesn't go away I'll take the phone to service because I want a reliable phone.
Thanks for the reply I almost gave up on this post. I saw a lot views but no replies this might mean that a lot of people have the same problem.
I'll also post some status updates about my problem so this post can be as an instruction to people with the same problem.
Click to expand...
Click to collapse
You must go to the service bro, it seems a serious problem
JuniorCaesar said:
You must go to the service bro, it seems a serious problem
Click to expand...
Click to collapse
Yes, i will but it sounds like a a manufacturing problem since I also know someone else having the same SIM card problem
slole said:
Yes, i will but it sounds like a a manufacturing problem since I also know someone else having the same SIM card problem
Click to expand...
Click to collapse
This phone's problems not limited with sim card, also screen, camera and many more. M2 series are not good.
Don't agree with you sorry, my m2 hasn't missed a beat in over a year of serious use apart from when it's something I've done to it myself tweaking and changing things maybe I've been lucky even gonna keep it when I get my upgrade in a few months(Xperia of course).
[email protected] said:
Don't agree with you sorry, my m2 hasn't missed a beat in over a year of serious use apart from when it's something I've done to it myself tweaking and changing things maybe I've been lucky even gonna keep it when I get my upgrade in a few months(Xperia of course).
Click to expand...
Click to collapse
I love my 2303 too, but I used 4 m2, this doesn't mean all m2's are damaged But mostly of them are little produce damaged (Example, when you pushed screen on normal touch, you can see LCD liquid moving or find dead pixels)