rooting

[Sasazuka]

This works perfectly - I ran into a minor problem which I just want to let others know about:

After booting into Clockwork's recovery, I was no longer able to sideload due to USB drivers issue. I just kept going the first time and said "no" to the extra prompt about fixing root. I just needed to re-install USB drivers in Clockwork's recovery before sideloading and everything went smoothly afterwards.

 

[SamuriHL]

So now you are on 4.3, rooted, with stock recovery for when the next update comes. How awesome is that?

 

[mixgenio]

I recently purchased the S4 GE myself and am looking to try out your automated method. Should I be on 4.2.2 before attempting it? Or will it not matter if update to 4.3? Also, does the method temporarily boot twrp using fastboot and then flash the su zip or does it overwrite the recovery partition permanently with twrp?

Anyone looking to root the S4 GPE can follow along here:

xda-developers - View Single Post - [HOWTO] Root Stock i9505G 4.3 (Google edition)

I automated the process outlined in the OP of that thread.

 

[SamuriHL]

Doesn't matter what version you're on.
Uses cwm, not twrp.
Doesn't overwrite recovery... Only temporarily boots cwm in memory.

Sent from my Xoom using Tapatalk 4

 

[mixgenio]

yeah. not long after asking you I figured out that my questions had already been answered by you/others in your linked thread. And so, because I was anxious to root, I pushed forward with the process and rooted while still on 4.2.2. UNFORTUNATELY, I didn't pay attention to the warnings that said to remove root prior to taking the 4.3 update and proceeded to get stuck in a boot loop at 2AM. Thankfully I was able to follow the instructions you provided to Sasazuka and am now safely on 4.3 with root.

So with that said: Thank you. Your easy to follow root executable was perfect and the instructions on how to get back to 4.2.2 were a savior to me and my brand new phone. lol

 

[SamuriHL]

Glad you got it sorted out!

 

[kjnangre]

Thanks SamuriHL! Couldn't get the drivers to work on my Windows 7 64-bit computer, but I switched to a 32-bit Windows 7 PC and was rooted in minutes!

 

[argold]

I am still really hoping this won't be necessary, but in the event - could someone clear up a couple of points:

1) What is the difference between the UniversalAdbDriverSetup6.msi in the ZIP (9,208,320 bytes) and the UniversalAdbDriverSetup.msi (9,215,488 bytes) I see on the GitHub koush page?

2) If RUN.bat achieves root, what is the process to unroot - for after I have fixed that one missing line in platform.xml?

Thanks.

 

[SamuriHL]

He may have updated it on git since I put that package together. Use whichever version you would like. Latest is best. I only included it as a convenience.

Supersu has a clean up full unroot function.

Sent from my Xoom using Tapatalk 4

 

[argold]

Many thanks.

 

[Burrito_Lte]

SamuriHL, thank you so much for all your contribution, i am very grateful that I was able to fix my gimped phone (ext sd card write access) with your automated rooting process, and not even a trip on the flash counter! I didnt unlock the bootloader either and it worked.

I have a question. I really don't need constant root on my phone and prefer to just fix the sd card problem and unroot the phone.
If for some reason I need to re root my phone again, Can I run your automated .bat file root method once again with no harm?

Just wanted to make sure since i dont want to make this a 700$ paperweight by accident.

Thanks!

 

[SamuriHL]

Yea you can use it to root whenever you need. Shouldn't be a problem at all.

Sent from my Xoom using Tapatalk 4

 

[mixgenio]

Glad you got it sorted out!

So my S4 PE alerted me to another 4.3 system update that was available (consensus is that its a minor security update). My phone was rooted when it alerted me so I had remove root prior to installing the update. Once I removed root, I clicked the update but received an error during the install. Fortunately I didn't get stuck in a bootloop but I am concerned now. Why would I get an error? I removed root prior to taking the update. The only thing that I can think of is that I modified the Build.prop file and the "Generic.kl" file (within "/system/usr/keylayout" to enable soft buttons/disable hard buttons. Could that be the culprit? Perhaps I need to remove my modifications to the system filed before attempting the update again?

 

[kjnangre]

So my S4 PE alerted me to another 4.3 system update that was available (consensus is that its a minor security update). My phone was rooted when it alerted me so I had remove root prior to installing the update. Once I removed root, I clicked the update but received an error during the install. Fortunately I didn't get stuck in a bootloop but I am concerned now. Why would I get an error? I removed root prior to taking the update. The only thing that I can think of is that I modified the Build.prop file and the "Generic.kl" file (within "/system/usr/keylayout" to enable soft buttons/disable hard buttons. Could that be the culprit? Perhaps I need to remove my modifications to the system filed before attempting the update again?

I had rooted my S4 GPE to fix the SD card problem. Today my phone notified me of the software update to 4.3. I did a full unroot (in SuperSU) and then installed the update. Everything worked first time

 

[SamuriHL]

Received an error. That's not very descriptive is it? The error should tell you what the assertion failed on which will give a clue how to fix it. There's so much misinformation about taking updates whole rooted. Having su installed is not enough to have an update fail. Any modifications made to system files is enough to make it fail an assertion. You'll have to see what the error is to figure out how to fix it. It's not because of root though. It's because of something you did with root.

Carved in blood by a wakizashi...

 

[mixgenio]

Received an error. That's not very descriptive is it? The error should tell you what the assertion failed on which will give a clue how to fix it. There's so much misinformation about taking updates whole rooted. Having su installed is not enough to have an update fail. Any modifications made to system files is enough to make it fail an assertion. You'll have to see what the error is to figure out how to fix it. It's not because of root though. It's because of something you did with root.

Carved in blood by a wakizashi...

During the install of the update, the Android logo would end up on its back with the word "Error" written over top. I didn't notice any particular notes on what the failure was related to though. Regardless of that, I figured out the culprit. As you mentioned, it was something I had done with Root. Shortly after posting my question, I remembered that I had modified the build.prop file (to get softkeys) and realized that it needed to be in its original state to accept the update. I simply reverted back to a backup of it and successfully took the update.

Sorry to have bothered you.

 

[SamuriHL]

No bother at all. Glad you got it figured out. I posted a new version of the root script on xda earlier today for those that need to reroot after the update.

Carved in blood by a wakizashi...

 

[mixgenio]

No bother at all. Glad you got it figured out. I posted a new version of the root script on xda earlier today for those that need to reroot after the update.

Carved in blood by a wakizashi...

I used your old script to achieve root after the update and had no problems. What is different with the newer script you wrote?

 

[SamuriHL]

Fundamentally it works the same. I just updated the adb driver and supersu. And updated the cwm recovery image. And I made the script dynamically look for the supersu zip and the recovery img so that people can remove the old versions and replace them with updated versions in the future. No need to alter the script... Just delete the old recovery and supersu and drop new ones in.

Carved in blood by a wakizashi...

 

[mixgenio]

Fundamentally it works the same. I just updated the adb driver and supersu. And updated the cwm recovery image. And I made the script dynamically look for the supersu zip and the recovery img so that people can remove the old versions and replace them with updated versions in the future. No need to alter the script... Just delete the old recovery and supersu and drop new ones in.

Carved in blood by a wakizashi...

You have been an enormous amount of help thus far in our small community. With that said, when 4.4 drops (whenever that is), do you think you will be attempting to update your easy root method? I am sure that a few of us would be willing to make monetary contributions as a thanks.

Posted via Android Central App