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.
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!
Well, anybody or devs who can explain to me why the official OTA would trip flash counter for noob like me?
I did flash CWM 5.5.0.4 via ODIN that caused counter to become 1.
Then flashed Super User v0.87 (now updated v0.93) via CWM, and counter stayed at 1.
I did not get into download mode after that, nor flashed anything via CWM.
No custom Rom installed yet.
Installed insecure boot using Samsung Tool Kit V1.0 by Mksip (great tool):good:
Then OTA update this morning.
It downloaded fine, and after backing up Google search by TB, I tried to install.
I went into recovery automatically, and gave me "installation aborted. unverified signature"
So I went into download mode to check, and it shows flash counter now upto 3.
And shows as custom binary, and custom Rom.
I know I did not install any custom ROM yet, why does it think as custom rom and binary?
Is it because of insecure boot I installed?
Any light to this is so much appriciated for my learning for android.
Thanks in advance.
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
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
HI all, a few months i rooted my S3 phone then an update messed everything up, it stopped giving permissions to applications and they could not run, Im also trying to reset binary counter but triangle away is not working.
SuperSU is reporting that SU binary is not installed and it cannot install it.
None of the SuperSU functions do anything anymore and it does not function and i cannot uninstall it. I am trying to reset binary counter to see if it will fix the issues but triangle away keeps crashing on startup. Any advice please? Thank you
Other things that my phone does:
On startup it always says android is updating has dont for the past few months it is no longer downloading or installing other updates.
you need to root it again. The update will have removed it.
gzanothor said:
HI all, a few months i rooted my S3 phone then an update messed everything up, it stopped giving permissions to applications and they could not run, Im also trying to reset binary counter but triangle away is not working.
SuperSU is reporting that SU binary is not installed and it cannot install it.
None of the SuperSU functions do anything anymore and it does not function and i cannot uninstall it. I am trying to reset binary counter to see if it will fix the issues but triangle away keeps crashing on startup. Any advice please? Thank you
Other things that my phone does:
On startup it always says android is updating has dont for the past few months it is no longer downloading or installing other updates.
Click to expand...
Click to collapse
The update removed the SU binaries.
For the "Android is Updating..." thing; re-flash recovery (Via Odin and preferably a kernel after that) and wipe the dalvik cache, that should take care of the problem. Once you've installed the kernel, your root problems should go away as well
familyguy59 said:
The update removed the SU binaries.
For the "Android is Updating..." thing; re-flash recovery (Via Odin and preferably a kernel after that) and wipe the dalvik cache, that should take care of the problem. Once you've installed the kernel, your root problems should go away as well
Click to expand...
Click to collapse
Ok thanks i'l give it a try
familyguy59 said:
T" thing; re-flash recovery (Via Odin and preferably a kernel after that) and wipe the dalvik cache, that should take care of the problem.
Click to expand...
Click to collapse
ok i'v rerooted it and that fixed the SU problem, how do you go about re-flashing recovery with odin?
gzanothor said:
ok i'v rerooted it and that fixed the SU problem, how do you go about re-flashing recovery with odin?
Click to expand...
Click to collapse
Just follow the instructions for whatever recovery you choose .
Basic is file in PDA slot .
jje