Related
Hi all,
Not sure whether to root or not, as I fear for my warranty :/ does it affect warranty ? and can it be reversed?
Thanks
James
Just want to know if it can be easily reversed please
Also what are the main advantages and disadvantages ? ...
I wanna remove some samsung apps, install droidwall and install LCD Density
Root can be reversed, and we can reset the flash count for unsigned kernels too
So yeah it should be undoable fine by flashing a stock rom and resetting download counter.
How do you go about removing a root? And is data lost?
You could re-flash back to the stock rom....but that will erase your data.
does the stock rom also update the kernel back to a secure one??
Sorry to bump this old thread but can Samsung or others detect if the phone has been rooted and then unrooted it it were for example to sent back for repair under warranty?
Lone_Star said:
You could re-flash back to the stock rom....but that will erase your data.
Click to expand...
Click to collapse
No it doesn't if you flash it properly.
theinstagator said:
Sorry to bump this old thread but can Samsung or others detect if the phone has been rooted and then unrooted it it were for example to sent back for repair under warranty?
Click to expand...
Click to collapse
No if you reset the counter and flash the stock firmware for the device.
Thanks, I purchase one of those jigs just in case The amount of tegra only games coming out is beginning to bug me, I'm hoping the possibility that the two best selling android phones of the year (Galaxy S2 and Sensation) not being tegra will swing developers back our direction.
theinstagator said:
Thanks, I purchase one of those jigs just in case The amount of tegra only games coming out is beginning to bug me, I'm hoping the possibility that the two best selling android phones of the year (Galaxy S2 and Sensation) not being tegra will swing developers back our direction.
Click to expand...
Click to collapse
Just use the Chainfire3D application for the market to destroy nVidia's BS.
That was my plan cheers
theinstagator said:
Thanks, I purchase one of those jigs just in case The amount of tegra only games coming out is beginning to bug me, I'm hoping the possibility that the two best selling android phones of the year (Galaxy S2 and Sensation) not being tegra will swing developers back our direction.
Click to expand...
Click to collapse
can you link me to where you purchased your jig? Also have u tried to see if the jig works? or you havent rooted your phone yet?
Would it be possible to unroot just using Superoneclick?
I tried once and it worked. However, does it completely remove all traces of root?
porkchop8 said:
can you link me to where you purchased your jig? Also have u tried to see if the jig works? or you havent rooted your phone yet?
Click to expand...
Click to collapse
I haven't got one yet but there is a how 2 vid up on you tube and apparently you can get them off of ebay (item no: 250824932406)
I flashed Gs2 with lightening ROm v5 ... Now I want to get back to stock rom and kernel ... Although I managed to flashed my kernel with stock kernel after flashed my GS2 with lightning ROM. But now when I flash my lighting room to get back to stock rom, my phone reboots and keeps animating galaxy S sign and nothing further happens. did I do something wrong?
4iedemon said:
Would it be possible to unroot just using Superoneclick?
I tried once and it worked. However, does it completely remove all traces of root?
Click to expand...
Click to collapse
As far as I know. Yes it does
porkchop8 said:
can you link me to where you purchased your jig? Also have u tried to see if the jig works? or you havent rooted your phone yet?
Click to expand...
Click to collapse
I got this jig for $8, it will reset the flash counter and get rid of yellow triangle also.
danijaan said:
I flashed Gs2 with lightening ROm v5 ... Now I want to get back to stock rom and kernel ... Although I managed to flashed my kernel with stock kernel after flashed my GS2 with lightning ROM. But now when I flash my lighting room to get back to stock rom, my phone reboots and keeps animating galaxy S sign and nothing further happens. did I do something wrong?
Click to expand...
Click to collapse
I am a newbie as well here but I thought I will share my experience.
I did have a bootloop and someone in the forum advised me to clear the cache and data using recovery mode. It worked.
give it a try
4iedemon said:
Would it be possible to unroot just using Superoneclick?
I tried once and it worked. However, does it completely remove all traces of root?
Click to expand...
Click to collapse
the easiest and safer method to unroot is to flash the stock kernal
4 months ago i've rooted my Galaxy S3 international (I-9300). Before rooting i took a nandroid backup of the Samsung's ICS. Then i flashed CM10 and recently (1 month ago) i flashed CM10.1. Everything was working OK (except some issues that come with the CM10-10.1). I also came against the SOD (Screen of Death) but as the devs warned us i was OK with that. From time to time i flashed a newer version of the CM10.1 nightly (recent one was 4th of Jan 2013).
Today as i was sitting in my office i picked up my device and pressed the power button just to check the time. The device did not respond and i presumed that it was another case of SOD. So i removed my battery and put it back inside as i always did when a SOD occured. I long-pressed the power button but nothing happened. I went to the nearest Samsung supplier and i bought a brand new Samsung battery to replace the old one but the device never powered up. Now i am stack with a device that cannot power up. I cannot get into download mode as well.
Is it a case of a bricked device? If it is, is there anything i can do to bring it back to life?
Thanks in advance!
In this case you cannot do much....take it to center and require motherboard replacement, if its case of brickbug it will he warranty covered....right now im interested if you flashed XXELLA or newer bootloader or did you flash kernel compiled from 7th source from samsung?
Sent from my GT-I9300 using xda app-developers app
tsangaris said:
4 months ago i've rooted my Galaxy S3 international (I-9300). Before rooting i took a nandroid backup of the Samsung's ICS. Then i flashed CM10 and recently (1 month ago) i flashed CM10.1. Everything was working OK (except some issues that come with the CM10-10.1). I also came against the SOD (Screen of Death) but as the devs warned us i was OK with that. From time to time i flashed a newer version of the CM10.1 nightly (recent one was 4th of Jan 2013).
Today as i was sitting in my office i picked up my device and pressed the power button just to check the time. The device did not respond and i presumed that it was another case of SOD. So i removed my battery and put it back inside as i always did when a SOD occured. I long-pressed the power button but nothing happened. I went to the nearest Samsung supplier and i bought a brand new Samsung battery to replace the old one but the device never powered up. Now i am stack with a device that cannot power up. I cannot get into download mode as well.
Is it a case of a bricked device? If it is, is there anything i can do to bring it back to life?
Thanks in advance!
Click to expand...
Click to collapse
Sudden death, all you can do is get a motherboard replacement at a service center, however they may never know you flashed CM10.1 because the NAND is dead.
gaspernemec said:
In this case you cannot do much....take it to center and require motherboard replacement, if its case of brickbug it will he warranty covered....right now im interested if you flashed XXELLA or newer bootloader or did you flash kernel compiled from 7th source from samsung?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply but i am not sure i can help you with the bootloader! I am not an advanced user. I just used Odin v3.04 to flash CF-Root-SGS3-v6.4. When i finally rooted my device i downloaded the CM10 and afterwards the CM10.1 rom and flashed it along with the GAPPS. And then i used a program to match the modem with the RIL (XXDLID). Ofcourse i fixed permissions.
One thing i need to know? Does the phone stays in the warranty if you root it?
delsus said:
Sudden death, all you can do is get a motherboard replacement at a service center, however they may never know you flashed CM10.1 because the NAND is dead.
Click to expand...
Click to collapse
You mean that i shouldnt say anything about root and CM10.1 right?
Also, is there a way for the technicians to find out that i've rooted the device and flashed CM10.1? I mean on a device that it cant even power on!
ps: i live in Cyprus (small island in the meditteranean sea) , so there isnt any advanced service center to examine my motherboard (at least i hope so).
tsangaris said:
You mean that i shouldnt say anything about root and CM10.1 right?
Also, is there a way for the technicians to find out that i've rooted the device and flashed CM10.1? I mean on a device that it cant even power on!
ps: i live in Cyprus (small island in the meditteranean sea) , so there isnt any advanced service center to examine my motherboard (at least i hope so).
Click to expand...
Click to collapse
Don't mention it, don't say anything about firmware, if they ask play dumb and just say the latest version, it's up to them to prove your warranty is void, also is Cyprus in the EU? If so check this out http://forum.xda-developers.com/showthread.php?t=2092530&highlight=eu
In short for your warranty to be voided by flashing Samsung has to prove that it was CM10.1 that caused the problem.
I don't think this will be needed though because your NAND is completely dead so it will be extremely hard if possible for them to prove you flashed anything.
delsus said:
Don't mention it, don't say anything about firmware, if they ask play dumb and just say the latest version, it's up to them to prove your warranty is void, also is Cyprus in the EU? If so check this out http://forum.xda-developers.com/showthread.php?t=2092530&highlight=eu
In short for your warranty to be voided by flashing Samsung has to prove that it was CM10.1 that caused the problem.
I don't think this will be needed though because your NAND is completely dead so it will be extremely hard if possible for them to prove you flashed anything.
Click to expand...
Click to collapse
Yes Cyprus belongs to EU.
I will not mention a thing about firmware and CM hoping they dont find it out.
In the meantime, if they replace the motherboard, i will be running Android with Touchwiz by default?
tsangaris said:
Yes Cyprus belongs to EU.
I will not mention a thing about firmware and CM hoping they dont find it out.
In the meantime, if they replace the motherboard, i will be running Android with Touchwiz by default?
Click to expand...
Click to collapse
Yes you will be on touchwiz, but you can always change that
I have no idea which version though, it depends what they flash at the factory.
delsus said:
Yes you will be on touchwiz, but you can always change that
I have no idea which version though, it depends what they flash at the factory.
Click to expand...
Click to collapse
Samsung should worry about their skin, because i am a user that rooted his device to flash a custom ROM, then the device is not booting by any means and i am thinking to root it again after the motherboard is replaced!!
By the way, the problem on the motherboard is caused 100% because i root the device??
Thanks so much for your answers!
tsangaris said:
Samsung should worry about their skin, because i am a user that rooted his device to flash a custom ROM, then the device is not booting by any means and i am thinking to root it again after the motherboard is replaced!!
By the way, the problem on the motherboard is caused 100% because i root the device??
Thanks so much for your answers!
Click to expand...
Click to collapse
No it is not caused by rooting your device. Your case is a typical Sudden Death Syndrome one. For more info go here:
http://forum.xda-developers.com/showthread.php?t=2091045
You said that the last CM 10.1 you installed was from 04.01.13? Well in that case the Samsung Update7 source wasn`t applied yet to CM10.1 Kernel, so the Kernel was not secure.
Scarface1991 said:
No it is not caused by rooting your device. Your case is a typical Sudden Death Syndrome one. For more info go here:
http://forum.xda-developers.com/showthread.php?t=2091045
You said that the last CM 10.1 you installed was from 04.01.13? Well in that case the Samsung Update7 source wasn`t applied yet to CM10.1 Kernel, so the Kernel was not secure.
Click to expand...
Click to collapse
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
tsangaris said:
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
Click to expand...
Click to collapse
Yes there is a problem with a specific type of eMMC chips in the SIII. There is plenty of evidence now that Samsung fixed this issue with the Update7 Source release and most S3 Kernels have this fix by now. You can read it in detail by clicking the link I posted a couple of posts ago.
I hope that they will repair your device without any problems but they should and if you couldn`t even access download mode it`s pretty much impossible to find out that you had Root or a custom ROM installed.
tsangaris said:
I didnt find the time to read the thread you post (i am reading it later on). So the not secure Kernel could cause this?
Click to expand...
Click to collapse
Some people are saying that the kernel fixes it some are saying they havent, but the service center should fix it because its a known problem.
Also the latest kernel has only been rolled out in UK and Spain. If there has not been a stock update available in your country there is really nothing they can do.
Sent from my GT-I9300 using xda premium
delsus said:
Some people are saying that the kernel fixes it some are saying they havent, but the service center should fix it because its a known problem.
Also the latest kernel has only been rolled out in UK and Spain. If there has not been a stock update available in your country there is really nothing they can do.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I don`t know of any case where someone had an SD while having a fixed Kernel installed. But you are right that nobody knows 100% if the fix really works.
Thank you all for your responses!! I am taking my GS3 to the place that i bought it for repairing first thing tomorrow!
I will let you know of the outcome!
Again, thanks a lot!!
tsangaris said:
Thank you all for your responses!! I am taking my GS3 to the place that i bought it for repairing first thing tomorrow!
I will let you know of the outcome!
Again, thanks a lot!!
Click to expand...
Click to collapse
Good luck
Hey guys,
I have a similar problem except that my screen turns on and shows the Galaxy S3 logo when I try to power it on but it won't go further (shows logo until I pull the battery). It doesn't boot into recovery either but I can start download mode.
The phone just turned off while I was listening to music. I think I was running Omega v27.
So my question is: Should I try flash a stock ROM since I can boot into download mode? And is this even "sudden death"?
Thanks in advance!
Half of sudden death. You should also get the phone to samsung
avrano1 said:
Hey guys,
I have a similar problem except that my screen turns on and shows the Galaxy S3 logo when I try to power it on but it won't go further (shows logo until I pull the battery). It doesn't boot into recovery either but I can start download mode.
The phone just turned off while I was listening to music. I think I was running Omega v27.
So my question is: Should I try flash a stock ROM since I can boot into download mode? And is this even "sudden death"?
Thanks in advance!
Click to expand...
Click to collapse
I would take that to samsung, toy could try flashing stock but if it wasn't a failure flashing something I'm not sure it would work.
I would imagine it will fail before it tries to flash.
Sent from my GT-I9300 using xda premium
vasp3690 said:
Half of sudden death. You should also get the phone to samsung
Click to expand...
Click to collapse
Tried to flash the + RESCUE FIRMWARE SGSIII I9300 + but it doesn't work. It can't flash the .pit-file and it doesn't work without either.
So I really have to return it but:
since the phone boots into download mode they will see that I used a custom firmware. Any chance to change this?
Hey all,
Just a very quick question.
Setup:
Unlocked I9300 16GB White on I9300XXEMC2 and rooted with CFTool.
Counter is at 1, naturally. This means that the phone wont check for OTAs. What Im wondering is if I use Triangleaway to clear it to 0 will the phone then check for OTA updates again(pretty sure it will) but more importantly is that safe with CFTool root still applied? Dont want to use triangleaway unnecessarily either as its risky.
Thanks,
Scratchling(Still getting used to this new plaything)
Root means no ota updates if I am not wrong, you could get updates via kies though if firmware and csc are aligned. Updating will result in loss of root though.
Sent from my GT-I9300 using xda app-developers app
The counter has nothing to do with it checking for ota, in settings under about phone it will say "modified" thats why it wont search for OTA updates.... ive never used kies so cant comment there, I just use XDA to get the most recent updates
Ivw used Triangle Away loads of times with no problems so have many many of people... the warning is just disclaimer.
Sent from my GT-I9300 using xda app-developers app
Anything you flash to your phone should rightly be treated with caution, if you read and follow the guidance you shouldn't have any problems, but the warning is mainly for people who might not have read anything up to that point and flash the wrong file, bricking their Iphone.
elspanish88 said:
The counter has nothing to do with it checking for ota, in settings under about phone it will say "modified" thats why it wont search for OTA updates.... ive never used kies so cant comment there, I just use XDA to get the most recent updates
Ivw used Triangle Away loads of times with no problems so have many many of people... the warning is just disclaimer.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Really its just convenient to not have to manually look and see if theres an update every few weeks.
Went ahead and gave TriangleAway a punt. It reset the counter alright but:
Code:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
So while the flash count is reset it can still tell its non standard. Oh well. Its no biggie, just would have been nice. May not even end up keeping it anyways, still sort of attached to my Xperia S.
Scratchling said:
Really its just convenient to not have to manually look and see if theres an update every few weeks.
Went ahead and gave TriangleAway a punt. It reset the counter alright but:
Code:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
So while the flash count is reset it can still tell its non standard. Oh well. Its no biggie, just would have been nice. May not even end up keeping it anyways, still sort of attached to my Xperia S.
Click to expand...
Click to collapse
A factory reset will put the status back to normal mate or if you dont want to lose your data go back in triangle away and right at the bottom there is an option to put it to normal I think its called "allow tracker to run"
And make sure you have stock kernel and recovery
Sent from my GT-I9300 using xda app-developers app
Scratchling said:
So while the flash count is reset it can still tell its non standard.
Click to expand...
Click to collapse
It depends on the bootloader version you have. If it was a JB bootloader (which means you were on JB before you rooted) then every reboot triggers the custom status if you have a custom recovery or kernel.
May I ask, why are you rooted? What I mean by that is - what are your actual requirements?
TB would be the number one reason, followed by the option to underclock and a few other apps that I wont mention here.
I updated to I9300XXEMC2 before rooting so yeah, it would be a JB Bootloader.
Scratchling said:
TB would be the number one reason, followed by the option to underclock and a few other apps that I wont mention here.
I updated to I9300XXEMC2 before rooting so yeah, it would be a JB Bootloader.
Click to expand...
Click to collapse
If you're using those sorts of functions anyway, I would suggest using CWM recovery to flash de-odexed custom touchwiz ROMs would be a better way. Sure, you have to check for updates manually and download to SD card, but you get the updates quicker this way and also you get better fixes than the official updates, that devs apply themselves and extra functionality.
That was my plan in a month or so, only just got the phone a week ago(free, sammy were dumping stock pre S4 release) so I'm giving stock a shot for a little while to then see what I want in a ROM. Likely go to CM10.1 first.
Scratchling said:
That was my plan in a month or so, only just got the phone a week ago(free, sammy were dumping stock pre S4 release) so I'm giving stock a shot for a little while to then see what I want in a ROM. Likely go to CM10.1 first.
Click to expand...
Click to collapse
There are a lot of ROM's based on stock too though. There are definitely a lot of Samsung features I'd recommend you check out before going AOSP.
But as far as Stock (Touchwiz) custom ROMs, Wanam Lite is my favourite. Fast, stable and Lite. Good ROM.
Yeah, only ever used Touchwiz on the mothers S2 and for short periods. Not going to dump it until Im sure I wont use its features.
Scratchling said:
Yeah, only ever used Touchwiz on the mothers S2 and for short periods. Not going to dump it until Im sure I wont use its features.
Click to expand...
Click to collapse
Even as a massive AOSP advocate, I stuck with Touchwiz from between May until only last month. Nearly a year
Only pressing thing is the low ram overhead sometimes(shame they didnt give us 2GB). Thanks for all the feedback anyways
If you use triangle away from the playstore it has a work aeound where it disables supersu for a few minutes at boot allowing you to check for OTA updates
Sent from my GT-I9300 using xda app-developers app
k6? said:
If you use triangle away from the playstore it has a work aeound where it disables supersu for a few minutes at boot allowing you to check for OTA updates
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Interesting....
Ooooh. Nice! Missed that before. Just tried and it works.
Waiting for SU to return now so I can then disable the option and safely check for OTA(there wont be anything but just as a proof of concept).
OTA check worked.
Swish. Thanks guys, exactly the kind of solution I wanted.
Scratchling said:
OTA check worked.
Swish. Thanks guys, exactly the kind of solution I wanted.
Click to expand...
Click to collapse
Don't thank us. Thank chainfire.
Sent from my GT-I9300 using xda app-developers app
Hey lads, two things that are bugging me, thought I'd be better put them here than a new thread:
Screenshots: Over compressed, look terrible, really bad banding at times
Menu capacative button: Activates all the time while typing with left hand, if I hit Y etc it opens the menu so I dont hit the key and instead open up a settings menu
No clear answers from googling, thoughts?
Hi, i'm trying to upgrade my samsung s3 to the latest firmware and as my phone was rooted i tried to unroot in by installing a stock firmware. I first flashed this firmware xxx.sammobile.xxx/firmwares/3/?download=10895 (i have put xxx as i don't have enough posts to provide links) and it did not wipe any data, but after flashing it still said device status modified so i could not update.
So then i flashed another firmware xxx.sammobile.xxx/firmwares/3/?download=16495 (by clicking check your firmware) and this time it wiped all the data on the phone (i had made a backup of all important information).
Now when i go into to settings and try to update it says "the latest updates have already been installed" but in settings under android version it says "4.1.2"
Can someone help me with this please
Thanks
The latest version for the galaxy s3 is 4.1.2. I see no fault since u flashed the stock firmware? Unless u flashed a custom rom, it will be 4.1.2 no matter how many times u search for ota.
Sent from my GT-I9300
The latest firmware is 4.3 i just just googled it and before i tried to flash anything i had a software update notification (about75mb) but i could not update as my phone was rooted.
There was an update for the s3 4.3 but there was many bugs and many complained of huge battery drain so samsung removed the update. Why not flash custom roms?
Sent from my GT-I9300
---------- Post added at 09:16 PM ---------- Previous post was at 09:11 PM ----------
You could try flashing the 4.3 firmware from sam mobile. U might like tat. But there might be bugs etc.
Sent from my GT-I9300
iMirage said:
The latest firmware is 4.3 i just just googled it and before i tried to flash anything i had a software update notification (about75mb) but i could not update as my phone was rooted.
Click to expand...
Click to collapse
Try a better google as said the latest 4.3 was stopped a few weeks back .
We are waiting on the new release .
As to your problem read the basic faqs and guides first its all answered .
UNDERSTAND FIRST
http://forum.xda-developers.com/showthread.php?t=2362743
Network IMEI EFS
http://forum.xda-developers.com/showthread.php?t=2393289
Kies will update over a rooted phone but OTA will fail.
I believe tat if u are rooted and update thru kies. U will lose ur root and have to root again. Based on experience
Sent from my GT-I9300
Ok thanks, just checked and it was pulled back.
One question if i install a custom rom and want to upgrade to official when its released will i have to install a stock rom first and lose all the data?
or can i upgrade like jellyyoguart said and only lose root access
iMirage said:
Hi, i'm trying to upgrade my samsung s3 to the latest firmware and as my phone was rooted i tried to unroot in by installing a stock firmware. I first flashed this firmware xxx.sammobile.xxx/firmwares/3/?download=10895 (i have put xxx as i don't have enough posts to provide links) and it did not wipe any data, but after flashing it still said device status modified so i could not update.
So then i flashed another firmware xxx.sammobile.xxx/firmwares/3/?download=16495 (by clicking check your firmware) and this time it wiped all the data on the phone (i had made a backup of all important information).
Now when i go into to settings and try to update it says "the latest updates have already been installed" but in settings under android version it says "4.1.2"
Can someone help me with this please
Thanks
Click to expand...
Click to collapse
Somewhere I read in this forum long time back - To try best of both worlds, Root + flash any AOSP rom + change bootanimation to samsung default + triangleaway => to eventually use custom rom but 'kind' of remain official. (although no kies support). I think the jist was if had to sent to repair center, the boot animation and triangle away would be sufficient for cover up.
U will have to flash back to stock then u can receive the ota or kies. I dun believe kies will update ur fone when u are on a custom rom. Easy way i always do is before flashing a custom rom, i do a nandroid back up and transfer it to my computer. Then flash the custom rom so when i wan to go back stock. Just flash the nandroid back up and wipe data and cache. And i am back to stock.
Sent from my GT-I9300
iMirage said:
Ok thanks, just checked and it was pulled back.
One question if i install a custom rom and want to upgrade to official when its released will i have to install a stock rom first and lose all the data?
or can i upgrade like jellyyoguart said and only lose root access
Click to expand...
Click to collapse
Correct as he said but most users on xda would have a nandroid to cover that anyway .
JJEgan said:
Correct as he said but most users on xda would have a nandroid to cover that anyway .
Click to expand...
Click to collapse
Ok thanks
JJEgan said:
Correct as he said but most users on xda would have a nandroid to cover that anyway .
Click to expand...
Click to collapse
Like i said tnx for verifying.
Sent from my GT-I9300
hyperorb said:
Somewhere I read in this forum long time back - To try best of both worlds, Root + flash any AOSP rom + change bootanimation to samsung default + triangleaway => to eventually use custom rom but 'kind' of remain official. (although no kies support). I think the jist was if had to sent to repair center, the boot animation and triangle away would be sufficient for cover up.
Click to expand...
Click to collapse
It would not. U are on a custom rom and tat will prove tat u void the warrenty.
Sent from my GT-I9300
JellyYogurt said:
It would not. U are on a custom rom and tat will prove tat u void the warrenty.
Sent from my GT-I9300
Click to expand...
Click to collapse
That comment was more related to bricking; may be when the phone gets stuck at boot logo.
hyperorb said:
That comment was more related to bricking; may be when the phone gets stuck at boot logo.
Click to expand...
Click to collapse
How was tat comment related to bricking at any sentence? Well nvm
Sent from my GT-I9300
JellyYogurt said:
How was tat comment related to bricking at any sentence? Well nvm
Sent from my GT-I9300
Click to expand...
Click to collapse
It's getting confusing !! Let me elaborate.
Somewhere I read in this forum long time back - To try best of both worlds, Root + flash any AOSP rom + change bootanimation to samsung default + triangleaway => to eventually use custom rom but 'kind' of remain official. (although no kies support). I think the jist was if had to sent to repair center, the boot animation and triangle away would be sufficient for cover up.
Click to expand...
Click to collapse
The idea in the source was => if a phone gets bricked and it can't be booted and if it need to be taken to be repair center, then in that condition ideally one should have official status to avail warranty. Even if that is ok repair center team 'could' see the boot animation and if that too remains stock, that would be perfect cover up.
still if not clear.... nvm
hyperorb said:
It's getting confusing !! Let me elaborate.
The idea in the source was => if a phone gets bricked and it can't be booted and if it need to be taken to be repair center, then in that condition ideally one should have official status to avail warranty. Even if that is ok repair center team 'could' see the boot animation and if that too remains stock, that would be perfect cover up.
still if not clear.... nvm
Click to expand...
Click to collapse
Oh do u mean if the op flashes a custom rom, if he uses samsung boot animation. The warrenty will work? The prob is if it is bricked, u can just flash stock firmware. Well. I get it now lol xD it was just tat ur prev post. The first few words kinda 'misguided' me. U said to try the best of both worlds or sth arnd tat.
Sent from my GT-I9300
hyperorb said:
It's getting confusing !! Let me elaborate.
The idea in the source was => if a phone gets bricked and it can't be booted and if it need to be taken to be repair center, then in that condition ideally one should have official status to avail warranty. Even if that is ok repair center team 'could' see the boot animation and if that too remains stock, that would be perfect cover up.
still if not clear.... nvm
Click to expand...
Click to collapse
Yes i have a custom rom zero count.
Custom status official .
Boot screen normal stock .
Only negative is in settings about phone .
So it may be missed that i have root and custom rom .
BUT Samsung repair centre have a check list to work from and a reminder what to look for from Samsung re root etc .
JJEgan said:
Yes i have a custom rom zero count.
Custom status official .
Boot screen normal stock .
Only negative is in settings about phone .
So it may be missed that i have root and custom rom .
BUT Samsung repair centre have a check list to work from and a reminder what to look for from Samsung re root etc .
Click to expand...
Click to collapse
The fix for the device status is basically to unroot or temp unroot. It worked for me.
Sent from my GT-I9300
Hey all, i wanted to ask if anyone is having the same problem as me.
So i bought a new Galaxy s9+ (G9650) and im experiencing some issues when slowly dragging my finger across the screen. It happens both in portrait mode and landscape. If i were to say... scroll across an image veeeery slowly or Play a game that requires fine accuracy (PUBG Mobile, its how i found the problem), the screen would start to jump around very slightly and repeatedly. If anyone has this problem or knows how to solve it please let me know. Thanks!
I will upload a video of the issue so you can see what i mean
https://youtu.be/2nLyy3h6dSM
lukesky1313 said:
Hey all, i wanted to ask if anyone is having the same problem as me.
So i bought a new Galaxy s9+ (G9650) and im experiencing some issues when slowly dragging my finger across the screen. It happens both in portrait mode and landscape. If i were to say... scroll across an image veeeery slowly or Play a game that requires fine accuracy (PUBG Mobile, its how i found the problem), the screen would start to jump around very slightly and repeatedly. If anyone has this problem or knows how to solve it please let me know. Thanks!
I will upload a video of the issue so you can see what i mean
Click to expand...
Click to collapse
Nope - Not an issue with my S9+
Did you make any changes in Developer Options for GPU Rendering etc?
Does this happen in all apps or just this game?
Sent from my Galaxy S9+ using XDA Labs
shaggyskunk said:
Nope - Not an issue with my S9+
Did you make any changes in Developer Options for GPU Rendering etc?
Does this happen in all apps or just this game?
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
No, no changes in anything. I did not even have developer options enabled. i did read about it and tried them but no success. I have been using the OEM charger and cable and never used anything else to charge it. it also happens when in google chrome, maps, Quora, etc. The problem seems to get aggravated when i charge the phone. I'm losing my mind T.T such a beautiful phone with this problem. My latest whack at the problem is going to be a cache partition wipe. If that doesn't work im going all out and flashing a De-bloated firmware (Goodbye Knox and Samsung pay)
lukesky1313 said:
No, no changes in anything. I did not even have developer options enabled. i did read about it and tried them but no success. I have been using the OEM charger and cable and never used anything else to charge it. it also happens when in google chrome, maps, Quora, etc. The problem seems to get aggravated when i charge the phone. I'm losing my mind T.T such a beautiful phone with this problem. My latest whack at the problem is going to be a cache partition wipe. If that doesn't work im going all out and flashing a De-bloated firmware (Goodbye Knox and Samsung pay)
Click to expand...
Click to collapse
Sadly no luck, cache partition wiped but no problem is fixed. I am currently downloading 2 stock firmwares (i hope theyre de bloated) from dominican republic, one Orange and one from Claro. I would just go to samsung for their warranty but i do not have the original reciept because i did not buy the phone.
If i flash my own firmware (No root, downloaded from sammobile) will it void my warranty?
lukesky1313 said:
If i flash my own firmware (No root, downloaded from sammobile) will it void my warranty?
Click to expand...
Click to collapse
Rather than doing what you're talking about - Why not just Factory Reset? Backup everything you need or want using Smart Switch or move to your external sd card / computer.
To answer this question - Flashing the Stock Samsung Firmware with Odin will not void your warranty ?
Sent from my SM-G965W ??
shaggyskunk said:
Rather than doing what you're talking about - Why not just Factory Reset? Backup everything you need or want using Smart Switch or move to your external sd card / computer.
To answer this question - Flashing the Stock Samsung Firmware with Odin will not void your warranty
Sent from my SM-G965W
Click to expand...
Click to collapse
I did factory reset. Installed all apps new and still got the problem. I paid 640USD for the device and now i have this crap, Its the latin american version (G9650).
Im currently downloading the Firmware as i said, i read somewhere about Product code changing while installing a firmware, would that be a sign to the warranters that someone messed with the device and would refuse to service my device? also, i read about Brazilian Firmware being closest to BTU (Bloatware free Android) but sammobile's link is not working ? Do you know someone with expertise in this area that could help?
lukesky1313 said:
I did factory reset. Installed all apps new and still got the problem. I paid 640USD for the device and now i have this crap, Its the latin american version (G9650).
Im currently downloading the Firmware as i said, i read somewhere about Product code changing while installing a firmware, would that be a sign to the warranters that someone messed with the device and would refuse to service my device? also, i read about Brazilian Firmware being closest to BTU (Bloatware free Android) but sammobile's link is not working ? Do you know someone with expertise in this area that could help?
Click to expand...
Click to collapse
Don't know if your device has an unlocked bootloader - If it doesn't - Then you can't really Flash anything that could void your warranty - Even if you don't change the CSC that shouldn't do anything to your warranty - it's Stock Samsung Firmware - Doesn't seem like you're too familiar with what you are trying to do - You might want to do some more reading & research ??
Sent from my Galaxy S9+ using XDA Labs
shaggyskunk said:
Don't know if your device has an unlocked bootloader - If it doesn't - Then you can't really Flash anything that could void your warranty - Even if you don't change the CSC that shouldn't do anything to your warranty - it's Stock Samsung Firmware - Doesn't seem like you're too familiar with what you are trying to do - You might want to do some more reading & research
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
I know a thing or 2 (Just gotta catch up on some terms) ? Had an Honor 5 with Cyanogen and an S4 rooted and running AOSP. im just rying to be veeeeeeery cautious since i worked very hard for this phone and i dont wanna brick it or loose warranty. I really apreciate your input on this topic. I spoke with the previous phone owner to see if i could get a purchase reciept and bring it in for warranty repair, untill then i wont touch the phone. if all else fails, then im flashing De-bloated firmware and crying my phone to repair every time i use it ????. I have the worst of lucks ?
Is there a forum for newbies that explain all these terms? it would be nice for all them people trying to get the most out of their phones but arent very tech savvy.
ph forgot to say: on the bootloader, it seems most if not all snapdragons have locked bootloader
lukesky1313 said:
ph forgot to say: on the bootloader, it seems most if not all snapdragons have locked bootloader
Click to expand...
Click to collapse
Yup pretty much - Chinese version doesn't have a Locked Bootloader & MAYBE... a South American variant? ?
Sent from my SM-G965W ??