Okay basically, when I got my phone I used the toolkit to root my phone, busybox, and CWR on the phone. Now I flashed like so many different roms, I want to go back to stock, I realize how important to have a stable OS then a buggy one. How can I do this, do I need Odin? if so would this void any warranty?
I hear if you use Odin, then the device will always show that I voided the warranty. is this true?
Thanks
rayoubi said:
Okay basically, when I got my phone I used the toolkit to root my phone, busybox, and CWR on the phone. Now I flashed like so many different roms, I want to go back to stock, I realize how important to have a stable OS then a buggy one. How can I do this, do I need Odin? if so would this void any warranty?
I hear if you use Odin, then the device will always show that I voided the warranty. is this true?
Thanks
Click to expand...
Click to collapse
Check this post out. It should help you
http://forum.xda-developers.com/showthread.php?t=1725839
rayoubi said:
Okay basically, when I got my phone I used the toolkit to root my phone, busybox, and CWR on the phone. Now I flashed like so many different roms, I want to go back to stock, I realize how important to have a stable OS then a buggy one. How can I do this, do I need Odin? if so would this void any warranty?
I hear if you use Odin, then the device will always show that I voided the warranty. is this true?
Thanks
Click to expand...
Click to collapse
If you want to go back to stock and keep root access, then follow this guide to the letter (skip the custom recovery part if you want to)
http://forum.xda-developers.com/showthread.php?t=1739426
If you want to go back to stock without root, do the same thing, but use the applicable image from http://samsung-updates.com/device/?id=SGH-I747M instead. TLS is Telus, RWC is Rogers and BMC is Bell. None of these will void warranty because they are stock images. I've done this, using the rooted images, to make a backup that I forgot to make when I first flashed a custom rom and It didn't trip my flash counter. Flashing stock images, as I understand, is pretty much like doing an official update, so it won't trip your flash counter or anything like that and your warranty will be intact. Hope this helps!
majingrim said:
If you want to go back to stock and keep root access, then follow this guide to the letter (skip the custom recovery part if you want to)
http://forum.xda-developers.com/showthread.php?t=1739426
If you want to go back to stock without root, do the same thing, but use the applicable image from http://samsung-updates.com/device/?id=SGH-I747M instead. TLS is Telus, RWC is Rogers and BMC is Bell. None of these will void warranty because they are stock images. I've done this, using the rooted images, to make a backup that I forgot to make when I first flashed a custom rom and It didn't trip my flash counter. Flashing stock images, as I understand, is pretty much like doing an official update, so it won't trip your flash counter or anything like that and your warranty will be intact. Hope this helps!
Click to expand...
Click to collapse
You gave me some good info. I flashed my phone with odin using a stock image. However, I rooted my phone and it told me to use a insecure image. So to be rooted you cant use the offical stock rom? is this correct?
rayoubi said:
You gave me some good info. I flashed my phone with odin using a stock image. However, I rooted my phone and it told me to use a insecure image. So to be rooted you cant use the offical stock rom? is this correct?
Click to expand...
Click to collapse
Even if you load your default stock provider ROM with Odin, you can still re-flash recovery and then flash SuperSU or Superuser (whatever app you prefer) and it will show your on a custom binary, but your OS is still stock + root. It won't affect the operation of the stock rom to my knowledge. Anytime I ever run into an issue, I just take my Telus Stock tarball and flash it with Odin, then I'm completely stock, including the bootloader and recovery app. Once I'm ready to start loading ROMs again, just flash the CWM recovery, it goes to custom, but your free to do whatever.
baldockdrew3 said:
Even if you load your default stock provider ROM with Odin, you can still re-flash recovery and then flash SuperSU or Superuser (whatever app you prefer) and it will show your on a custom binary, but your OS is still stock + root. It won't affect the operation of the stock rom to my knowledge. Anytime I ever run into an issue, I just take my Telus Stock tarball and flash it with Odin, then I'm completely stock, including the bootloader and recovery app. Once I'm ready to start loading ROMs again, just flash the CWM recovery, it goes to custom, but your free to do whatever.
Click to expand...
Click to collapse
I was using the toolkit and it made me choose an insecure rom to give me root, busybox, and CWR. if I can just get the stock rom that came with my provider and have it rooted, I rather do that. I mean its not a big deal I guess if im using insecure rom, but I want to know why its called insecure rom. I want to know if there is a difference.
rayoubi said:
I was using the toolkit and it made me choose an insecure rom to give me root, busybox, and CWR. if I can just get the stock rom that came with my provider and have it rooted, I rather do that. I mean its not a big deal I guess if im using insecure rom, but I want to know why its called insecure rom. I want to know if there is a difference.
Click to expand...
Click to collapse
As I understand it, an insecure rom simply means it can grant root access. So if your rom is not insecure, and an application asks for superuser (root) access, it won't be able to get it. If you're insecure, and you have an app to manage superuser access (Superuser, SuperSU) then it can be allowed/granted as you like. As someone else said, if you're using the rooted rom, and you have an issue that you think might need warranty work, simply flash your unrooted stock rom and bring it in. The only problem would be if you had a problem that prevented you from flashing, but even then, if it was that bad, it's probably beyond warranty issues anyway. Again, hope this helps out, cheers.
AT&T Samsung Galaxy S3
Stock Android 4.1.2.
As I tried rooting my phone using the Samsung GS3 Toolkit, the closest option was choosing my device as if it was on 4.1.1. After successfully rooting it, my wifi and camera did not work. My main goal is to install the latest CyanogenMod but I honestly don't know where to go from here. Since then, I have tried resetting my phone to factory from what looked like a recovery app provided by the toolkit but that just wiped all my data and neither my wifi nor camera work.
Question?
1) Where to go from here?
2) Is a ROM a layer on top of an android version, or is a rom the android version?
If it was simply a layer, I would guess I would have to flash it with stock again because its broken. If not, could I still install CyanogenMod and that would fix it?
A ROM is the whole operating system, not a layer on top of anything. Did u make a backup of your stock ROM before flashing cm? What custom recovery do u have?
There presently is no readily available boot image to make an insecure boot for the 4.1.2 MG2 firmware, I had the same problem and reflashing a different rom is not the best way to start, in my case I had a stock rom yo download and flash right now you don't so my hope would be you made a backup with the tool before you flashed anything, however even after returning to stock my camera appeared not to be working in order to fix that I had to format my internal memory, after that I was fine and back to normal. A method at this time to gain root that seems to work well is chainfires auto root method and it is very self explanatory and easy to use. As soon as Samsung posts update for MG2 I am sure there will many choices available I know I for one will pull the update and root and debloat it with dsixda's kitchen, hope this helps
Sent from my SGH-I747M using Tapatalk 4
Stuck on custom status and superSu doesn't work
Tried flashing superSu tried flashing a deodexed roms I found on here tried doing a factory reset hoping to maybe get back unroot status even tried framaroot again.
Can anyone tell me how to either get root again so I can add a custom recovery since my goal is too install the 4.2.2 update or get back to unrooted factory status?
Thanks in advance
roguedroid said:
Stuck on custom status and superSu doesn't work
Tried flashing superSu tried flashing a deodexed roms I found on here tried doing a factory reset hoping to maybe get back unroot status even tried framaroot again.
Can anyone tell me how to either get root again so I can add a custom recovery since my goal is too install the 4.2.2 update or get back to unrooted factory status?
Thanks in advance
Click to expand...
Click to collapse
You shouldn't need root to add a custom recovery. You can flash a recovery in download mode using Odin on Windows, or Heimdall on Windows/Mac/Linux. If you're interested I can give you some help with installing and using Heimdall.
Bear in mind that flashing files in download mode will void your warranty (there is a counter which tracks how many times you've flashed). Flashing also carries a risk of bricking your device permanently. Once the flash counter is nonzero, your device will be detected as "custom" and you still won't be able to install official updates. But you will be able to flash ROMs in recovery from the xda community.
So currently my device is running stock Rom and stock recovery that has a root flashed with Odin so I could manually edit framework on dmd5.
I was thinking of doing the same thing with the new version.
But as I understand it any modification will break the Knox Samsung function and cause issues and can't be reverted.
What would be the best way of getting a stock upgrade with just root?
Probably best to flash a custom recovery and just run a specific stock Rom or is there a way to do this with Odin still?
I so far haven't been able to find a way to do that.
Basically I just would like a stock Rom since I use WiFi calling and would like a modified framework to enable tethering bypass and Bluetooth tethering with it.
Any thoughts or suggestions would be greatly appreciated.
Thank you for your time.
TheArtiszan said:
So currently my device is running stock Rom and stock recovery that has a root flashed with Odin so I could manually edit framework on dmd5.
I was thinking of doing the same thing with the new version.
But as I understand it any modification will break the Knox Samsung function and cause issues and can't be reverted.
What would be the best way of getting a stock upgrade with just root?
Probably best to flash a custom recovery and just run a specific stock Rom or is there a way to do this with Odin still?
I so far haven't been able to find a way to do that.
Basically I just would like a stock Rom since I use WiFi calling and would like a modified framework to enable tethering bypass and Bluetooth tethering with it.
Any thoughts or suggestions would be greatly appreciated.
Thank you for your time.
Click to expand...
Click to collapse
Search for and read on Doc Holiday's thread for Leaked Stock 4.3 update with KNOX Removed.
Oh okay.
I found his thread.
Basically just put on a custom recovery and let it hit the flash counter
then install his rom I guess?
TheArtiszan said:
Oh okay.
I found his thread.
Basically just put on a custom recovery and let it hit the flash counter
then install his rom I guess?
Click to expand...
Click to collapse
For right now yes, this is the best solution.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Hello All,
I am currently looking at different ways to try and update my device to dojc or doj7. Right now it is on DOH6 and seems like I have a few random glitches with the way it works and crashes. I am rooted currently with engineering bootloader with a custom recovery. I am thinking of one of two paths and wondering what might be the better of the two options in your opinion.
First, create a firmware file to flash with Odin that does not have the bootload file in it and flash that. Then root the device again the same way I did with the DOH6 root method and engineering bootloader. Stay on that install from Samsung and just root it.
Second, install a custom rom with that new version as a base (I think I remember seeing some stock rooted roms). and then upgrade the modem only with odin. Not sure if there is anything else other that the modem that would need to be updated with Odin.
I am just not sure if that second option would work if the firmware is too different to work with it. Any opinions on which might be the better option? How have you been able to update to DOJ7 or DOJC and root without worrying about Knox? And input would be greatly appreciated.
Couldn't you just flash a custom Rom and flash the new modem with Odin?
Would that work okay guys? I think that should be fine and leave the bootloader on 5.0 engineering and it won't trip Knox.