Related
Has anyone been successful in update their Nexus 7 device with the following configuration:
1. Stock ROM
2. Rooted
3. SuperSU v0.98 (recently updated)
4. Voodoo RootKeeper
5. DPI set to 160, need confirmation but assuming this needs to be reverted back to 213
I have been viewing other posts of successful upgrades but with prior versions of SuperSU, so I was hoping i could find that one person who has the above configuration and was successful in updating.
Thanks,
JBIRD
Apart from 4, the Rootkeeper, that was my setup when I updated from 4.1.2 via the 4.2 OTA (adb sideload).
Worked fine.
Re-rooted using superboot and am happycat ever since.
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
rmm200 said:
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
Click to expand...
Click to collapse
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
jbird92113 said:
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
Click to expand...
Click to collapse
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
rmm200 said:
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
Click to expand...
Click to collapse
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
jbird92113 said:
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
Click to expand...
Click to collapse
Yes!
rmm200 said:
Yes!
Click to expand...
Click to collapse
One last thing, I changed my DPI settings to 160, do I need to revert to back to 213...
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you recommend to be on the safe side that I disable supersu as well prior to the upgrade?
Thanks again...
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Oh, you didn't mention you were on Safestrap. That may bring up some additional issues. And you do need to revert your build.prop to the original. With any luck, you have a build.prop.bak that you can restore. SuperSU hasn't caused me any problems, but I don't use multi-user.
rmm200 said:
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Thanks again for all your help..
jbird92113 said:
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Click to expand...
Click to collapse
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
If you use MSkips Nexus 7 Toolkit and use option 8 it will not only unlock the boot loader, but root, install busy box, your choice of either cwm or twrp, recommends using the 3.34 bootloader, and recommends using SuperSu 0.98 due to problems with superuser not being updated yet. I can attest to the fact that the 4.13 bootloader causes root issues. At least on my 7. Apparently that isn't so on all 7s.
Sent from my Nexus 7 using xda premium
rmm200 said:
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
Click to expand...
Click to collapse
I am not going to use the multiuser feature as I am the only one who uses the tablet. Will rerooting work on the primary user?
Seems to work fine.
Sent from my Nexus 7 using xda app-developers app
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Gigabitex2 said:
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Only problems I have seen are trying to set up / use a second user while rooted.
Stay away from multi-user and you should be fine.
Note - problems I have reported with SuperSU may just be related to multiuser and root, no matter how you get root.
I have not tried the "superuser" app, so I have no idea if the problems will be the same.
I need help guys. I'm currently rooted running ParinoiAndroid 3.00 and Franco Kernel #82. I'm trying to download the Good for Enterprise App from the Play Store and install for my work email, but the app won't install becasue of my Root status. Is there a way to hide the root status from this app at all times. I really don't want to unroot my phone.
:fingers-crossed:
Not sure if this will work...
Go to SuperSU -> Settings.
There in Access, give default access as Deny
Then set up the whole Good for Enterprise thing
Then once the setup is done, set default access as Prompt again.
rhoadster91 said:
Not sure if this will work...
Go to SuperSU -> Settings.
There in Access, give default access as Deny
Then set up the whole Good for Enterprise thing
Then once the setup is done, set default access as Prompt again.
Click to expand...
Click to collapse
Thanks for the suggestion, but I gave it a try and it didn't work.
Any other ideas????
Unroot. Install. Re-root. ?
Sent from my Nexus 4 using xda app-developers app
chrisrozon said:
Unroot. Install. Re-root. ?
Click to expand...
Click to collapse
I do not think unrooting 4.2.2 is wise. I heard 4.2.1 rooting techniques do not work for 4.2.2.
Gjohnson7771 said:
Any other ideas????
Click to expand...
Click to collapse
Umm... nothing I can think of right now... If you have a spare device you can unroot that, install it on that device, setup your phone, root it, copy its data from /data/data and then restore it in your Nexus 4 Long shot.
rhoadster91 said:
I do not think unrooting 4.2.2 is wise. I heard 4.2.1 rooting techniques do not work for 4.2.2.
Umm... nothing I can think of right now... If you have a spare device you can unroot that, install it on that device, setup your phone, root it, copy its data from /data/data and then restore it in your Nexus 4 Long shot.
Click to expand...
Click to collapse
Ok, that's not good. I guess I will need to do more research on unrooting 4.2.2.
And no this is my only device. I have a couple of old Iphones but that won't do me any good. Oh and if I was to unroot it and install the software, wouldn't the device be wiped when I re-root it and flash a custom ROM?
Gjohnson7771 said:
Oh and if I was to unroot it and install the software, wouldn't the device be wiped when I re-root it and flash a custom ROM?
Click to expand...
Click to collapse
After re-rooting it, backup the data using Titanium. Then flash custom ROM and restore App + data.
rhoadster91 said:
After re-rooting it, backup the data using Titanium. Then flash custom ROM and restore App + data.
Click to expand...
Click to collapse
I'm not sure if you would know this answer or not, but in an app like Good Enterprise does it normally just search for root status upon initial install or does it look for the root status periodically.
Also, I had plans to unroot using the SuperSU "Full unroot" option or even the Nexus 4 tool kit. Are either one of these methods the unroot techniques you were referring too? I really don't want to brick my device if its unwise to unroot.
bump.......
Gjohnson7771 said:
I'm not sure if you would know this answer or not, but in an app like Good Enterprise does it normally just search for root status upon initial install or does it look for the root status periodically.
Also, I had plans to unroot using the SuperSU "Full unroot" option or even the Nexus 4 tool kit. Are either one of these methods the unroot techniques you were referring too? I really don't want to brick my device if its unwise to unroot.
Click to expand...
Click to collapse
I would have tried to check it myself first before suggesting you the solution (I had even downloaded the app) but turns out setting up Good Enterprise requires more than just downloading and installing it. I am not sure if it checks the root status periodically but in this case looks like the only option we have is to hope that it checks only during initiation. However, if the app is any good, I think it will check root status periodically to maintain security (because a lot of app information is compromised on a rooted phone)
Also, I do not think you will brick your phone if u attempt to root 4.2.2. Simply rebooting it in fastboot mode will give you option to revert to stock even in the worst situations. Still, cannot rule out the risk.
Anyway, a simple Google Search revealed this which could be a potential solution
Well thanks for all the info. I'll see what I can figure out.
Un rooting is quite simple , nothing to worry about!
By the way, Good permissions can be set by your administrator. They have the option to allow root, to check every time, Or to check once. It all depends on how your company configures it.
Sent from my Nexus 4 using xda app-developers app
Well, I was able to use nexus 4 toolkit to uproot and relock the boot loader. The app install fine after that and is working properly.
Thanks for the replies. For some reason I was thinking I would have to return the phone back to stock to uproot it, I'm glad I was able to keep my custom ROM and kernel. 1 more question, was re-locking the boot loader necessary or could I have kept it unlocked?
voodoo ota root keeper has a temporary unroot option, grab it from the playstore , much easier than unrooting your phone, also root survives an ota from google. You probably could have left the bootloader unlocked.
easy way ??
An easy way to hide root is renaming the superuser app/apps in the below location.
/system/app
This method did the charm for me for few apps. But the disadvantage is, it will hide root for all apps..
Workaround
http://forum.xda-developers.com/showthread.php?t=2040163 - thread talking about workaround for GFE
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
You can't root mf3. You never should have taken the update if you want to be rooted. Cross your fingers that someone finds a way to root the update but I'm not sure you should hold your breath.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So is doing a stockrom restore back to MDL an option? Then just root that with Motochopper? And disable OTA updates till its figured out?
The real joke here is that to get their built in app-to-sd functionality they give you an update that hogs up another 1GB!
Nope. Can't go back. Just gotta wait it out. Cheers
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
TheKog said:
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
Click to expand...
Click to collapse
A qfuse is blown when you take the update. It won't let you odin or anything else to go back to an earlier firmware.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Ok so my SGH-I337 S4 is rooted using Motochopper and is still stock ROM, just rooted. I did it so I could make Google Wallet work on AT&T, which was successful. Now AT&T has an OTA update that I want. So I will have to unroot. I already have the stock ROM download that I can flash via Odin to unroot. But what will happen to the apps I have installed that require root, like Titanium Backup, ROM manager, etc. Will they automatically be removed or just stop working? Also, has anyone had any experience with the Universal Unroot app? That would sure be easier. But my main question remains: what does Unrooting do to apps that are installed that require root privileges?
Sent from my SGH-I337 using Tapatalk 4
When you user Odin you'll have to do a factory reset or you'll get into a boot loop. So by by apps. Your tibu backup file will still be there, but just in case copy it to your pc before hand. The apps that require root will not work until you re-root.
Hi highly recommend you don't get the ota. Even though it's root able it's very dangerous to do so.
What I will say, if you want the update is to go here http://forum.xda-developers.com/showthread.php?p=43963746 and you will have the benefit of the OTA and not lose the root and custom recovery, and all the app will work! You will not upgrade the bootloader. Once you updated the bootloader is not coming back!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I don't understand why you get a boot loop. I once soft bricked a phone and used Odin to flash a md5.tar of a stock ROM. The phone rebooted and I saw my wallpaper and all my apps and data intact. I have seen threads on Unrooting that describe using Odin that way. They all said that doing a factory reset afterword is if you want to delete all your apps and data like if you sell your phone or just want it as it was out of the box
Sent from my SGH-I337 using Tapatalk 4
feetr2c said:
I don't understand why you get a boot loop. I once soft bricked a phone and used Odin to flash a md5.tar of a stock ROM. The phone rebooted and I saw my wallpaper and all my apps and data intact. I have seen threads on Unrooting that describe using Odin that way. They all said that doing a factory reset afterword is if you want to delete all your apps and data like if you sell your phone or just want it as it was out of the box
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
what device were you using?
That was my S3
Sent from my SGH-I337 using Tapatalk 4
feetr2c said:
That was my S3
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
thats interesting. were you on stock when you soft bricked it?
many, many...many users commonly have to wipe data/factory reset after flashing stock via odin. sometimes they can get away with just a cache wipe. not often, though.
I had used (can't remember his name) Galaxy S3 Toolkit to root the phone. Interestingly, Root Checker said I was rooted, but Titanium Backup wouldn't install... It said I needed root access... Hmmm.... Later when I went to unroot using the same S3 Toolkit, I did something wrong. The phone would boot but stick at tiny little letters in the upper left of the screen that I *think* said recover. I messaged the developer of the Toolkit and he sent me a link to download the original AT&T stock ROM. He told me how to use Odin and check the PDA box. I did it and it fixed my phone.
Sent from my SGH-I337 using Tapatalk 4
I had rooted my S3 using the Galaxy S3 Toolkit by (can't remember his name). Interestingly enough, Root Checker said I was rooted but yet Titanium Backup wouldn't install... Said it needed root access... Hmmm.... When I tried to unroot using the Toolkit, I did something wrong and the phone rebooted with little Teeny letters in the upper left corner of the screen that I *think* said recover. I messaged the developer of the Toolkit and he sent me a link to the AT&T stock ROM. He told me how to use Odin and check the PDA box. I did and it fixed my phone
Sent from my SGH-I337 using Tapatalk 4
thats why i asked if you were still on stock when you used odin. most users are not, which is ultimately what requires them to factory reset in recovery.
I wonder if universal unroot is trustworthy
Sent from my SGH-I337 using Tapatalk 4
All that would happen to your rooted apps is they wouldn't have root privileges anymore, which means they ultimately won't work as expected. I would recommend uninstalling them before you update. You may also be able to do a full unroot via SuperSU or one of the other superuser apps.
NOTE: Your phone may not update even after unrooting. You may have to do a factory reset first. I don't know why, I'm not a developer. I'm just speaking out of my own experience from the past.
Hello developers.
I'm trying to reroot my phone after the latest 4.3 update via ODIN for my Indian handset.
I'm trying using CF-AutoRoot via ODIN and the it says PASS and the phone restarts normally as it should but the root is simply not happening.
there were 2 android 4.3 updates for my device and i installed the latest (you can see the post title for the exact version)
after everything completed properly i simply tried CF-AutoRoot via ODIN and nothing is happening.
Till 4.2.2, it got rooted properly without such or any other problems.
Kindly assist me out in getting my phone rooted.
Regards.
Here too
avineshwar said:
Hello developers.
I'm trying to reroot my phone after the latest 4.3 update via ODIN for my Indian handset.
I'm trying using CF-AutoRoot via ODIN and the it says PASS and the phone restarts normally as it should but the root is simply not happening.
there were 2 android 4.3 updates for my device and i installed the latest (you can see the post title for the exact version)
after everything completed properly i simply tried CF-AutoRoot via ODIN and nothing is happening.
Till 4.2.2, it got rooted properly without such or any other problems.
Kindly assist me out in getting my phone rooted.
Regards.
Click to expand...
Click to collapse
Yep, I can´t re-root it again it seems the CF-Auto-Root-ja3g-ja3gxx-gti9500.tar its not working for the i9500XXUEMJ8 versión, well time to wait to an updated CF-Auto Root :crying::crying::crying:
I9500XXUEMJ5 root working (almost working)... i cant run some app, without root all apps working great ;/
Weird. I rooted using CF Auto Root after flashing 4.3 MJ8, it always worked! I never did OTA update though, always used Odin and full wipe.
avineshwar said:
Hello developers.
I'm trying to reroot my phone after the latest 4.3 update via ODIN for my Indian handset.
I'm trying using CF-AutoRoot via ODIN and the it says PASS and the phone restarts normally as it should but the root is simply not happening.
there were 2 android 4.3 updates for my device and i installed the latest (you can see the post title for the exact version)
after everything completed properly i simply tried CF-AutoRoot via ODIN and nothing is happening.
Till 4.2.2, it got rooted properly without such or any other problems.
Kindly assist me out in getting my phone rooted.
Regards.
Click to expand...
Click to collapse
The rooting worked so far for me. Have you enabled KNOX? They enhanced the security features and as far as I heard KNOX-enabled devices can't get full root. Verify whether it is enabled or not. I'm not sure whether the user enables it or not but that may be the reason. I'm also not sure whether this KNOX security really affects I9500 models. I9505 models are definitely affected.
jujuburi said:
Weird. I rooted using CF Auto Root after flashing 4.3 MJ8, it always worked! I never did OTA update though, always used Odin and full wipe.
Click to expand...
Click to collapse
Probably I never full wiped.
The apps and all other data is retained (normally all is retained when we update rom via odin).
Factory reset (full wipe) was never required earlier to get root to work.
Knox is not on from my side though I get some notifications always that some app tried to access something and Knox blocked that. But I guess that is something else because we need to manually activate Knox after opening the Knox app.
Sent from my GT-I9500 using xda app-developers app
kci83 said:
I9500XXUEMJ5 root working (almost working)... i cant run some app, without root all apps working great ;/
Click to expand...
Click to collapse
It did worked for me too but only at times.
When I updated rom switcher app, root was gone and it never happened again!
Sent from my GT-I9500 using xda app-developers app
anyone with any solution for this?
anyone with any solution for this?
Solved!
Sent from my GT-I9500 using xda app-developers app
what was the solution? did you need to do a fullwipe? or used another method for rooting?
im on 4.2.2 MG9 and would like to update to 4.3 and have root without the know issue.
thanks.
Backup and Factory reset and cache clear after updating to 4.3
Then you'll get stock Samsung 4.3
Follow the same method to root (auto root) or alternatively flash super su via cwm/twrp/stock recovery.
resitm said:
what was the solution? did you need to do a fullwipe? or used another method for rooting?
im on 4.2.2 MG9 and would like to update to 4.3 and have root without the know issue.
thanks.
Click to expand...
Click to collapse
avineshwar said:
Backup and Factory reset and cache clear after updating to 4.3
Then you'll get stock Samsung 4.3
Follow the same method to root (auto root) or alternatively flash super su via cwm/twrp/stock recovery.
Click to expand...
Click to collapse
Thank you. Will this trip the knox thing?
After using CF-AUto root you need to update Super SU App on first boot.
Then Open SuperSU app and choose to install SU Binary without using a custom recovery.
Then reboot.
Then install Titanium backup pro and use it to free all Knox related files.
There are 7 of them and you need to remove all of them.
Remember you need to install a custom recovery to install busybox. (atleast in my case)
Install http://forum.xda-developers.com/showthread.php?t=2489234 via ODIN.
Once you are on custom recovery.
Use busybox installer to install busybox.
reboot.
You are done.
resitm said:
Thank you. Will this trip the knox thing?
Click to expand...
Click to collapse
No mate.
Wait for a future update to trip that.
In the mean time, I'm trying to trip that since it isn't very difficult just lazy to try everything since everytime 1 thing fails, I need to restore the whole data and if takes much of my bandwidth.
Hope you understand.
And the device status will also remain custom.
P.S. Touchwiz UI from Samsung will hang on a later date due to some app compatibility issue (I'm not sure which app but I can tell a large set of apps and it will hang due to any one from that list) so it is preferred to shift to some other launcher on pre hand.
Sent from my GT-I9500 using xda app-developers app
thank you both avineshwar and ajhavery.
i really wanted to update but i guess i am going to wait for a while. lots of issues seem to be happening once rooted. also dont want to lose warranty with the knox thing.
it seems the custom roms such as arrow and crash also have sound issues, FC issues on some apps.
i guess ill wait and see. maybe once the nexus 5 is out i can sell the i9500 and get the nexus 5.
resitm said:
thank you both avineshwar and ajhavery.
i really wanted to update but i guess i am going to wait for a while. lots of issues seem to be happening once rooted. also dont want to lose warranty with the knox thing.
it seems the custom roms such as arrow and crash also have sound issues, FC issues on some apps.
i guess ill wait and see. maybe once the nexus 5 is out i can sell the i9500 and get the nexus 5.
Click to expand...
Click to collapse
Waiting is good.
Don't sell your phone though (for obvious reasons).
You've got much to explore.
When it comes to selling, you'll get money whenever you do that so keep that option as your last bet.
Custom roms aren't really preferred from my side until you are a die hard modification fan!.
Rooting is the only problem (which is solved now I guess) on the latest firmware.
Rooting won't do any problem, believe me (except warranty).
Sent from my GT-I9500 using xda app-developers app
avineshwar said:
Waiting is good.
Don't sell your phone though (for obvious reasons).
You've got much to explore.
When it comes to selling, you'll get money whenever you do that so keep that option as your last bet.
Custom roms aren't really preferred from my side until you are a die hard modification fan!.
Rooting is the only problem (which is solved now I guess) on the latest firmware.
Rooting won't do any problem, believe me (except warranty).
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
hello again, i am asking this question because i cant post in the development forum yet.
i downloaded 3 files from the OP http://forum.xda-developers.com/showthread.php?t=2317105
the PDA, CSC and modem. all for MJ8, downloaded PDA is odex.
when i flashed 3 of the files with ODIN like shown in op my device. After i restarted i got errors for Unfortunately, the process com.google.process.gapps .
i searched on google and did what was suggested, like clearing dalvik cache, resetting default apps, uninstalling the play store update etc.
the phone was unusable, the errors popedup every second.
I had to go back to the MG9 4.2.2 firmware.
What did i do wrong?
have you guys tried the method mentioned in the post. it prerooted and knox free 4.3 firmware.
resitm said:
hello again, i am asking this question because i cant post in the development forum yet.
i downloaded 3 files from the OP http://forum.xda-developers.com/showthread.php?t=2317105
the PDA, CSC and modem. all for MJ8, downloaded PDA is odex.
when i flashed 3 of the files with ODIN like shown in op my device. After i restarted i got errors for Unfortunately, the process com.google.process.gapps .
i searched on google and did what was suggested, like clearing dalvik cache, resetting default apps, uninstalling the play store update etc.
the phone was unusable, the errors popedup every second.
I had to go back to the MG9 4.2.2 firmware.
What did i do wrong?
have you guys tried the method mentioned in the post. it prerooted and knox free 4.3 firmware.
Click to expand...
Click to collapse
Probably you want to upgrade to 4.3?
If so goto sammobile.com and find the latest firmware for your device from there, download and flash the same via odin.
You're now on 4.3!
Once done you can root from the auto root method by chain fire.
Sent from my GT-I9500 using xda app-developers app
avineshwar said:
Probably you want to upgrade to 4.3?
If so goto sammobile.com and find the latest firmware for your device from there, download and flash the same via odin.
You're now on 4.3!
Once done you can root from the auto root method by chain fire.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
that would be the easiest and best solution but i am worried about the knox issue, losing the warranty and also having to sell the phone later on for a lower price.