hi guys
i have vodafone's sgs3 i9300 4.0.4 with stock rom.
i flashed package with desktop odin with CF ROOT 6.3 and Hebrew language enabler from - bit ly/QLREa3.
later i updated android from 4.0 to 4.0.4(via built-in update option)
some time after SuperSU updated automatically to 0.96. on opening it said 'the SU binary needs to be updated. Continue?' > 'Instalation failed !'
tried uninstall in play store, in settings reinstall and full unroot.later flashed cf root 6.4 and did wipe clean from recovery mode. still the same.
be happy to find a way to reinstall it somehow.
(btw i intend on install some custom or original JB rom, maybe it can also solve this problem)
First one reset factory reset on recovery mode than without power on flash official ICS or JB rom. After that flash cfroot 6.4. Thats all. Now your phone rooted
Related
I am getting alot of force closes after i rooted my galaxy s2 XLPQ with CF root kernel...(a compatible one)
as well as when i use wifi with my charger plugged in the phone gets really hot...
i installed spiderman (gameloft) yesterday and its not working too...it hangs just after playing for one minute....
There are someother Rooted kernels available on the XDA...like Siyah..
Try them, if problem still remains, that is not CF-root problem. some other settings on your ROM
Is it just that you did or you also updated to ics from GB. If yes wipe
Sent from my GT-I9100 using Tapatalk 2
I had the same problems with ICS after rooting with CF-Root. That's why I decided to root it without CF-Root. Now, there are no insecure kernels available for ICS yet, so u will have to root it a bit differently.
First of all, get the latest ICS as per your country, if u are in UK, then I would suggest that you get
I9100XWLP7 ICS 4.0.3 (Official UK SIM Free Release, upgradable via Kies)
obviously reset wipe etc..
After that download
CWM Manager and SuperUser Installer package
Copy both the zip files to your External SD Card
Power off your phone and start it in standard recovery mode.
Select apply update from external storage
Select Choose CWM.zip and wait for CWM to load
Once CWM is loaded, Select install zip from internal SD
Then you will see a list of files and folder, Select SU-Installer-signed.zip
This will root your phone and install the SuperUser App.
Once done, reeboot your phone and that it, your phone is rooted.
This will give you permanent root access. The root will stay even after resetting the phone via recovery mode or from the OS itself. This method doesn't install any insecure kernel, so you will not get the infamous yellow triangle neither it will effect the custom binary counter. This root method keeps your phone as close to stock as possible. You will still have your stock recovery, i.e. it will not be replaced by CWM, unlike when you use CF-Root.
So if you have to give your phone for a repair, you can simply unroot by same method, though this time instead of using SU-Installer-Signed.zip, you use SU-Uninstaller-Signed.zip
Hope this helps..
PS: If you wanna reset your custom binary counter without using any patches or using an old bootloader, then flash your phone to an older firmware.
I9100XWKE7 Gingerbread 2.3.3 (Official UK SIM Free Release, upgradable via Kies)
After flashing, use a USB Jig to reset the counter, upgrade to 4.0.3 using the link above or via Kies and follow the step above to root etc.
Cheers
- me!
Hi there,
yesterday I updated from 4.0.4 to 4.1.1 with Kies.
It's the German Version XXDLID.
After the upgrade I wanted to re-root my phone. I used Odin and CF-Root 6.4.
Odin showed, that the first try was a succes. But I did gain root permissions.
So I tried it again and it worked this time. (strange?)
The installed app "CWM Manager" was able to do a backup with the recent 4.0.4. But when I open
that app with 4.1.1 it keeps saying:
"This version of CWM manager should be used with CF-CWM v1.1 or newer.
It appears you are running a different recovery. Various features have been disabled."
Do I need to wait for a new CF-Root version or is there a fix available?
CWM manager needs an update for Jelly Bean
But you are still able to make backup if you reboot in recovery
as above....it's just the app, boot into recovery and all usual options are there
yeap, CWM needs a little update for JB support.
But I've done several backups/restores since I flashed JB with no problems.
Ok, that's what I thought.
I really liked the CWM App, hopefully there's an update soon.
Thank you all
Hi,
My phone quits during the update process to JB in recovery at around 32% and then once booted back into android displays a popup saying failed to update software, try again using kies or use a samsung service centre. It doesn't connect to kies (stays stuck at connecting) and pretty sure samsung will just wipe the phone which I'd rather not do.
I originally had the phone rooted with Siyah 1.5.3 but have since reflashed the stock i9300 3e android recovery, reset the flash counter to 0 and official binary with triangle away and fully removed root from within SuperSU. I have also wiped the cache, any ideas on why the update is still not applying? I would like to stick the stock rom and avoid wiping.
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Aladdin Sarsippius said:
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Click to expand...
Click to collapse
Haven't tried to update since I unrooted (ota is only available during a few hours in the afternoon here and hasn't become available yet) but it removed the SuperSU.apk when I unrooted. Stweaks app is still there but doesn't work due to the lack of root. The only other non-stock thing left is the kernel but I don't think that should matter seeing as I've used triangle away and reset the counter and binary to official. I'll post on whether it works next time around
Try removing cwm somehow, many people find that this is a problem, same happens with me, apparently cwm fixed it in newer updates.:good:
CWM is the culprit. I really don't know why people insist on using that. It is utterly useless.
Download the ROM you want from samsung-updates.com or through CheckFUSDownloader, extract the .MD5 file from the downloaded ZIP, copy the .md5 file to the device, and flash using MobileOdin.
Then, if you want, just flash SiyahKernel again using Odin.
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
this worked for me.
viva.fidel said:
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
Click to expand...
Click to collapse
in triangle away there is a box that says something like modified workaround, tick that then run triangle away, when it restarts your status will be normal, then go to application manager and remove triangle away. after about 15 minutes go into superSU and unroot.
HI,
I have a P7510 that had Overcome 3.2 ROM (that i rooted without problem). Some days ago, I decide to update to Samsung 4.0.4 original UK firmware. I use ODIN and the tablet are working as expected. I didn´t do any wipe and the programs wasn´t lost.
But I´m trying to get root, but I can´t flash the CWM with ODIN. I try several tar files indicated for P7510, for ICS and other olders and I can´t get the option to boot into CWM download mode. I try ROM manager, but no way Because this, I can´t flash the root zip.
Is this happen because I didnt do any wipe or factory reset ?
Is there any way to get root in this case ?
Thanks
I encountered a strange problem while using Mobile Odin Pro v.3.85 with 4.3 MK6
My phone : Samsung Galaxy S3
I usually use Mobile Odin Pro to flash firmware, i enable inject Root and SU so I wont lose Root and dont increase counter, staying all official.
Let me explain what I did.
I started from 4.1.2 all stock with root and MOP v 3.50 (mobile odin pro v 3.50). Downloaded MK6 firmware from thread in general s3 section and flashed using MOP with ever root: everything okay Im on 4.3. I tryied to open SuperSu and it says there isnt any SU binary with a message saying: "if you just updated to 4.3 install root manually". So i used CF Auto Root for S3 and installed it: once rebooted i couldnt find any SU icon in drawer, had to download latest from Play Store and I was rooted but with counters to "Unofficial" since I flashed with odin.
Now I reflashed 4.3 to avoid getting Unofficial Status: updated MOP to 3.85 latest, it auto downloads flash kernel, flashed 4.3 with everroot (I was already on 4.3 but with unofficial status). All I was hoping to achieve was a 4.3 rooted with MOP 3.85 and all counters to official. For past versions like 4.1.2 it worked!
MOP rebooted S3 and started flashing 4.3: at the end it was in a loop, it continued to flash 4.3 over and over.
Why I got that loop? It was an compatibility issue with 4.3 bootloader and MOP flash kernel?
Have I to downgrade bootloader to ICS first (like I had before)?
I had to go in download mode and flash 4.3 using pc odin, I was so scared! Now im on 4.3 without root but id like to have it with counters set to official.
Thank you, steebro.
loop issue
steebro said:
I encountered a strange problem while using Mobile Odin Pro v.3.85 with 4.3 MK6
My phone : Samsung Galaxy S3
I usually use Mobile Odin Pro to flash firmware, i enable inject Root and SU so I wont lose Root and dont increase counter, staying all official.
Let me explain what I did.
I started from 4.1.2 all stock with root and MOP v 3.50 (mobile odin pro v 3.50). Downloaded MK6 firmware from thread in general s3 section and flashed using MOP with ever root: everything okay Im on 4.3. I tryied to open SuperSu and it says there isnt any SU binary with a message saying: "if you just updated to 4.3 install root manually". So i used CF Auto Root for S3 and installed it: once rebooted i couldnt find any SU icon in drawer, had to download latest from Play Store and I was rooted but with counters to "Unofficial" since I flashed with odin.
Now I reflashed 4.3 to avoid getting Unofficial Status: updated MOP to 3.85 latest, it auto downloads flash kernel, flashed 4.3 with everroot (I was already on 4.3 but with unofficial status). All I was hoping to achieve was a 4.3 rooted with MOP 3.85 and all counters to official. For past versions like 4.1.2 it worked!
MOP rebooted S3 and started flashing 4.3: at the end it was in a loop, it continued to flash 4.3 over and over.
Why I got that loop? It was an compatibility issue with 4.3 bootloader and MOP flash kernel?
Have I to downgrade bootloader to ICS first (like I had before)?
I had to go in download mode and flash 4.3 using pc odin, I was so scared! Now im on 4.3 without root but id like to have it with counters set to official.
Thank you, steebro.
Click to expand...
Click to collapse
Hi! Regarding your boot loop problem, may I suggest that after you flash with MOP, do go into recovery (cwm) and first do a wipe data / factory reset, followed by wipe cache partition. This will give you a fresh rom install. I may be wrong, but that is usually where the problem lies (not doing a wipe data / wipe cache after a fresh (official) ROM install. That's what I have read on countless forums. Hope it helps. Good luck!