I currently have a stock 4.1 rom, the one that came on the device. It's a german rom, even though I live in the Netherlands. That doesn't botter me, btw I use US english as a system language.
I rooted that with auto root. So I have NO recovery and NO triangle. However I do have system status modified and thus cannot OTA update.
No what I want to achieve is:
-Newest STOCK rom, with ink blob etc
-Maybe different language rom, does that matter for ANYTHING?
-Enable OTA
-Keep root
-No triangle
-Ability to flash zips, most importantly NFC at lock screen, and allow more apps for split view.
-Keep EVERYTHING what is currently on, so no factory reset if possible.
Is all this possible, and how? I cannot for the life of me find any info how to do it.
Thanks VERY much if anyone knows and can explain.
N7100 btw
No, update is not possible via OTA or Kies when you're rooted.
Sent from my GT-N7100
Okay, let's say forget about OTA, is the other combination still possible?
You can use Mobile Odin to flash a stock ROM with keeping root. And flashing a stock official ROM will not wipe any data.
To flash zip's you need to have a custom/advanced Recovery.
Sent from my GT-N7100
Edit: okay I used Xposed for the NFC at lock screen so flashable zips is not really needed anymore. Now my final question stands:
If I flash, for instance this rom:
http://forum.xda-developers.com/showthread.php?t=1915386
1: My triangle will stay away, correct?
2: However, I will need to choose French, which is not a problem, but does this not change anything else besides the default system language? I thought it had something to do with handwriting as well (which I currently don't have)?
3: If I choose either ODEX or DEODEXED, both will keep all my data?
Delano.888 said:
Edit: okay I used Xposed for the NFC at lock screen so flashable zips is not really needed anymore. Now my final question stands:
If I flash, for instance this rom:
http://forum.xda-developers.com/showthread.php?t=1915386
1: My triangle will stay away, correct?
2: However, I will need to choose French, which is not a problem, but does this not change anything else besides the default system language? I thought it had something to do with handwriting as well (which I currently don't have)?
3: If I choose either ODEX or DEODEXED, both will keep all my data?
Click to expand...
Click to collapse
I can't answer your question with regard to language options. However, flashing that ROM via ODIN, either odexed or deodexed, should not wipe your data or increase your flash counter.
However, and another member has already mentioned this, I strongly suggest you familarize yourself with MobileODIN. Currently, there is no way to receive OTA updates with "Modified" system status; and if you're rooted, you'll always have "Modified" system status.
However, just because your device can't receive OTA updates, that doesn't mean your device can't flash OTA updates that you've downloaded manually via an update.zip. Furthermore, flashing an OTA update.zip via MobileODIN Pro will allow you to retain root through the process. Additionally, MobileODIN also has the ability to flash full, PC ODIN-Flashable ROMs just like the odexed/deodexed ones you're currently looking at. Unlike with PC ODIN though, MobileODIN Pro gives you the option to inject root into whatever ROM you happen to be flashing at the time. So, if you wanted, you could go download the absolute latest completely stock, untouched, unrooted OTA or full ROM, use MobileODIN to flash it and root it at the same time, and remain completely stock except for having root access.
Now, I don't know if staying as stock as possible is even important to you. However, if it is, then MobileODIN Pro is your one-stop-shop for flashing stock, PC ODIN-Flashable ROMs whenever you need to. And even if staying completely stock isn't important to you, MobileODIN is still the best way to update to the latest ROM before cooks even have a chance to include it in their custom ROMs.
Sent from my GT-N7100 using XDA Premium HD app
Related
[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search
I've put together a zip file with the I747UCLG1 AT&T OTA update that can be flashed using CWM. This file
does not trip the flash counter
preserves root
does not include the Google search update to remove universal search
does not wipe /data
does require removing all themes and modifications
Standard disclaimer: I am not responsible if this bricks your phone, destroys your IMEI or kills your kids.
Prerequisites: You have to be on stock I747UCALEM for this to work. It may be rooted, but all the standard AT&T and Samsung bloatware must be there with no modifications. It's okay if some of the apps are frozen with Titanium Backup. You must not have any other mods or themes applied. The updater will check this stuff and abort if anything is wrong. I personally restored a nandroid backup I made right after rooting. If you didn't make one, you can use Odin and the instructions here to go back to stock.
To apply it:
Boot into recovery and make a nandroid backup.
Go back to AT&T UCALEM rooted stock if necessary (see above). If you're already on stock UCALEM but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALEM stock.
Make sure CWM recovery from clockworkmod.com is installed. The recovery from Team Epic will not work. You can get a zip file to flash in your current recovery to install v5.8.4.5 from here. Use one of the first two files; the ones that start with "recovery-clockwork". After you flash the zip, restart recovery through the "advanced" menu. Your recovery should say "ClockworkMod Recovery" at the top and not "CWM-based Recovery".
Put one of the zip files from below on your internal or external SD card.
Boot into recovery
Wipe cache and dalvik cache (optional?)
Flash the attached zip
(Optional) Go to Backup and Restore, Advanced Restore and restore the /data from the nandroid backup you made in step 1. If you used a nadroid backup in step 2, this should restore your data and apps. If you used Odin to flash the rooted UCALEM image, this step isn't necessary.
Reboot
Open Settings / Application Manager. Choose All tab. Click on AT&T Software update. Clear "Clear data". If you were getting OTA notifications before, this will prevent them from recurring. After doing this, your phone will know it's up-to-date.
This worked for me. I checked that my flash counter is still at 0 and Google search is still finding local stuff like apps. I still have root.
DOWNLOADS:
I747UCALG1_OTA.zip: This is the full OTA, with kernel and bootloader. You must be using the stock UCALEM kernel for this to work.
I747UCALG1_OTA_No_Bootloader.zip: This is the full OTA without the bootloader.
I747UCALG1_OTA_No_Bootloader_No_Kernel.zip: This is the OTA without the bootloader or the kernel. You can use this if you're already running a non-stock kernel.
I747UCALG1_OTA_Bootloader.zip: This is just the bootloader. You can apply this along with the "no kernel no bootloader" zip above in case you want everything but the kernel.
MODS:
This process requires the stock framework-res.apk, so at this point you'll need to reapply any mods you already applied. Here are some mods that I've rebuilt against LG1. Both are zip files you can apply through recovery.
Tether and Cell Standby Fix: This includes the mod to enable native Bluetooth and WiFi tethering from here and the fix for the incorrect reporting of Cell Standby time from here.
Tether, Cell Standby Fix, Increase Autobrightness: The same as above, but also with a mod to bump up autobrightness levels from here.
No Increasing Ring: This removes the increasing ringtone volume. The mod is from here.
OTHER PIECES:
Kernel: The UCALG1 kernel and kernel modules.
UCLG1 Modem: Just the modem from the OTA.
UCLEM Modem: The modem from the stock UCALEM firmware.
UCALG1 Bootloader
UCALG1 Bootloader (no checks): This is the LG1 bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
UCALEM Bootloader
UCALEM Bootloader (no checks): This is the LEM bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
LIST OF CHANGES IN OTA:
A full list of the files and partitions changed by the OTA is attached to this post.
Only 10MB? Wonder what they updated... not much need for it for me, Im on AOKP, but downloading anyways, and thanx button hit TWICE LOL
Let us know if it's a lockdown flash...
B-Naughty said:
Let us know if it's a lockdown flash...
Click to expand...
Click to collapse
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
drothenberger said:
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
Click to expand...
Click to collapse
Hmmm... guess we'll just to see what users report, but for the wise, to all, use the zip provided just in case... AND FOLLOW THE OP
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
dave1977nj said:
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
Click to expand...
Click to collapse
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
drothenberger said:
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
Click to expand...
Click to collapse
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
dave1977nj said:
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
Click to expand...
Click to collapse
Here you go.
drothenberger said:
Here you go.
Click to expand...
Click to collapse
tried that still the same error message need some help please....
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
dave1977nj said:
tried that still the same error message need some help please....
Click to expand...
Click to collapse
What recovery are you using? Maybe give the CWM 5.8.4.5 a try (in the OP) if you're not already using it.
pinoymutt said:
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
Click to expand...
Click to collapse
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
So if I'm on stock LG1 I flash rooted LEM and then flash your zip? Does your update include the baseband update ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
mobilehavoc said:
So if I'm on stock LG1 I flash rooted LEM and then flash your zip?
Click to expand...
Click to collapse
I don't think I understand. You're already on UCALG1, but you want to apply the OTA to go from LEM to LG1? Why?
If you do want to do that, you do need to flash the rooted LEM tar through Odin. Then follow the rest of the instructions in the OP.
Does your update include the baseband update ?
Click to expand...
Click to collapse
Yup. It includes everything except the Google search update, recovery, and (optionally) the bootloader.
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Odin back to pure stock working fine.. some of my apps fore close though
drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
Many thanks! You never know what kind of goodies they like to through in new bootloaders, so better safe than sorry!
ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
I think there are only two ways to get rooted LG1: Start with rooted LEM and use OTA Rootkeeper to keep root when you apply the OTA or use the method in the OP. In your case, you'd have to Odin back to the rooted LEM to get root, then if you want to go back to LG1, follow the OP steps.
ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
Depends which method of rooting you want to use. If you are interested in the method that does not trip the counter, then yes you would flash that through ODIN (which will technically revert you back to UCLEM with root injected) and then apply the update in the OP here and in the end you should be on a a rooted UCALG1 w/o a tripped counter.
Anyone wanna pull just the baseband for cwm zip?
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.
Hi All,
So I wanted to go back to a stock TW nandroid i made after rooting so that I could get the official sammy JB rom only to find out that my external SD card where I have all my backups is pooched....
My question is, can I use Mobile Odin to flash a stock image right from my device? I am using a mac and don't have enough free space to setup a virtual machine.
Thanks in advance,
Mike
hedphones said:
Hi All,
So I wanted to go back to a stock TW nandroid i made after rooting so that I could get the official sammy JB rom only to find out that my external SD card where I have all my backups is pooched....
My question is, can I use Mobile Odin to flash a stock image right from my device? I am using a mac and don't have enough free space to setup a virtual machine.
Thanks in advance,
Mike
Click to expand...
Click to collapse
Yea it can read the official thread for more help
http://forum.xda-developers.com/showthread.php?t=1347899
Says all the details just for that too. lemme just quote the parts that you are asking about.
"Mobile ODIN will attempt to detect if the OTA wants to flash kernels, recoveries, and modems, and if so will compare the signatures to your currently installed kernel, recovery, and modem. Should the comparison fail, it will offer you the choice to disable the check and the patch inside the OTA. This will allow you to flash the OTA without switching away from your current custom kernel or switching to whichever modem the OTA expects. Of course, if you have selected a kernel, recovery, or modem to flash, it will compare against the selected image instead of the currently installed one.
Mobile ODIN will also compare the OTA's fingerprint checks against the current system fingerprint. If the fingerprint does not match, Mobile ODIN will offer you the choice to disable the check inside the OTA. If you have selected a system image to flash, it will try to find out the image's fingerprint instead. It is not generally recommend to patch out the fingerprint, but sometimes it is needed.
It will also go through all the file signature checks inside the OTA, and compare to the current system files. If files are found to differ Mobile ODIN will offer you the choice to disable the checks and patches inside the OTA. When you have the wrong CSC flashed, it is common for a small number of files (30 or so) to differ. These files usually don't really matter for the firmware's operation. Note that this check will not be performed if you have selected a system image to flash - all files must match signatures in that case, or the OTA will fail." this is from the thread good luck updating
Mobile Odin
hedphones said:
Hi All,
So I wanted to go back to a stock TW nandroid i made after rooting so that I could get the official sammy JB rom only to find out that my external SD card where I have all my backups is pooched....
My question is, can I use Mobile Odin to flash a stock image right from my device? I am using a mac and don't have enough free space to setup a virtual machine.
Thanks in advance,
Mike
Click to expand...
Click to collapse
yes mobile odin will work. I used the lite version last week to restore to stock because i was too lazy to get my computer. it does work and you could use ever root if you want to keep it rooted or just flash a stock rooted img. the new official sammy jb rom rooted is now available for you to flash via odin so i'd suggest that.
Hello, first of all, I'm sorry for the noob question. I tried to search for the answer but I got more confused than when I started. I have rooted my SGS3 just to be able to use the Wifi hotspot, I'm not into other modifications or anything, I just wanted the hotspot. Now the phone wants me to update through OTA, but of course it's not working. My questions are:
-Should I go back to stock (following the videos from qbking77) and then apply the OTA? Is it safe?
-Should I go back to stock and MANUALLY update the phone?
-Is LF9 the latest OFFICIAL update?
-Is there anything else I should consider?
I don't care about custom roms or any other modifications, I like the phone vanilla BUT with the hotspot enabled. I was looking through a lot of videos and threads but I could't find a good answer.
Thanks in advance!
The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.
m20120 said:
The latest official release is LJ7. You have a couple of options to get the update.
- You could go back to stock to accept the update. The key is that you need the stock recovery installed for the update to work normally. You could then reflash the custom recovery if you like.
- You could manually apply the update from the recovery. If you phone is bugging you to apply the update it then you probably already have the update ZIP in your \cache\ folder. You could also download it. The normal OTA update will only work in the CWM recovery (not TWRP) but there are modified versions posted here that remove the check to allow it to work from TWRP.
Other considerations: If you are using the WiFi Tether for Root users it will no longer work one you update to Jelly Bean (LJ7). You will need to unisntall that and get version that was modified by TrevE.
Click to expand...
Click to collapse
Thanks for the help! Yes I think I have CWM on. I followed a video from qbking77 (I think) and installed it. Or at least it was something like custom recovery or something the like. Do you think I can apply the update directly from CWM? Or it would be easier (and cleaner) to go back to stock recovery and do it "officially". Also, are all stock recovery the same? I ask because there are some different files in qbking77's website. I don't know if the version of stock recovery matters at all. Also, thanks for the tip on the modified app.
You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.
m20120 said:
You probably have CWM recovery. You only need the stock recovery if you want to let the phone apply the OTA (i.e. it prompts you to accept the update). You also have to have the phone in a completely stock state (root is ok). You can not have any modified system files.
If you want to apply the update manually you can also do that with CWM. You can copy the file (something like eec955eb4a5b.update_SPH-L710_LI3_to_LJ7.zip) from the \cache folder to the internal sdcard of your phone. You can then boot into CWM recovery and apply flash the ZIP update. You must have stock system files in order for this update to work also.
If you have modified any system files (I removed the system version of Swype) you have to get back to stock in either case.
Click to expand...
Click to collapse
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?
nahuelarg86 said:
Ok, so the only thing I did is install the wfi hotspot app after rooting, I didn't touch anything else. So I shouldn't worry about system files, right?
You mentioned that since my phone is bothering me with updates notifications, it is because it already downloaded the update into the "cache," right? So I should just find that file, put it in the sdcard and flash from CWM? It's really that easy?
Click to expand...
Click to collapse
It is probably there if it is prompting you to update.
One step that I almost forgot about. When you do the update you will reinstall the script that detects a custom recovery and it will install the stock recovery.
There is a good procedure here that gives you the step by step process, including flashing the Team Epic file to prevent the updated ROM from restoring the stock recovery. If you do not flash the Team Epic file the update will still be successful and you will still have root, you will just end up with the stock recovery.
The process is really easy and it is the one that I used to update from LI3 to LJ7.
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