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!
Related
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,
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.
So I reinstalled the stock GT-I9100T (Vodafone S2) 4.0.3 ICS firmware using Odin, and decided to use a method of rooting I found online which was simply installing "update.zip" using the stock Recovery. A SuperSU app is present and Root Checker says it's rooted. Now I want to install CWM to reflash AOKP, but I'm not sure what method to use, since it's already rooted.
Thanks in advance.
Save yourself hassles & avoid 'temporary' versions of CWM. Just flash the Odin version of the Siyah build which is compatible with the current Android version you're running. Read the first page of the Siyah threads to workout which build you need. You'll have a rooted phone + permanent CWM & you can then flash any rom/other kernel you like quickly/easily.
Well, i'm new in this android/root stuff, but to have something to begin with:
I tried rooting my device(i9505) in 4.3(using that "knox-untouching" way) and, it not only didn't worked (can't use SuperSU), it also installed a custom recovery on my device (triggering everything it could) and know i can't OTA.
So I was thinking, can I just download the OTA and install it over ODIN, then wipe data? Or i have to download 4.3, flash it over, wipe, and than install 4.4.2? (For the record, i can't find my 4.3 ZTO version. Even in sam mobile)
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
I have purchased a galaxy nexus on the cheap to hold me over until the nexus 6 is out but if I can fix my note, I would like to.
I know there were other threads about this same issue but it seems that they are all on a different version of the note, or on a s3 or something. Not to mention, I don't see anything that I could try without asking for some help on here. Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Thanks guys!!!
amberkalvin said:
Okay, So the title pretty much says it all. I am stuck at the Samsung boot logo (not bootanimation) and it only shows for about 1 second then reboots and continues.
This started after I tried to flash a rom and it messed up and I tried to flash via odin. I was on MJ9 and and got a bootloop so I did the odin thing. I've used odin before but it is not working well for me now.
I am able to boot into download mode but TWRP no longer works. I was able to flash via odin and it says success but the phone does not reboot like it should.
Click to expand...
Click to collapse
Before you tried to flash a custom ROM and things went wonky...were you on Verizon's factory stock 4.3 MJ9 firmware, or on Beanstown106’s modified 4.3 MJ9 with TWRP installed?
Does the phone still boot into stock recovery? If so, you may be able to fix the phone by doing a factory reset.
amberkalvin said:
Can someone maybe point me in the direction of the factory firmware (preferably a rootable or already rooted version) that I can flash that will play well with my note.
Click to expand...
Click to collapse
If you were on Verizon's factory stock 4.3 MJ9, then you won't be able to Odin flash back to 4.1.2 or any earlier Android version because the bootloader has been locked down tight on 4.3 (and 4.4.2) with no current do it yourself method to unlock for those newer versions. You would want to restore the phone back to factory stock 4.3 though, if that's what version you were on before your phone got messed up. You can root the phone on 4.3 with saferoot, then use safestrap recovery to flash some custom Touchwiz ROM's.
If you were on the 4.1.2 based bootloader, (but running Beanstown106’s MJ9 firmware and TWRP), then you would want to restore your phone back to factory stock 4.1.2 and then root and unlock the bootloader again with CASUAL. This would give you the most flexibility with flashing custom kernels, ROM's, etc...
Check out Section 1b in Droidstyle's restore guide at this link: http://forum.xda-developers.com/showthread.php?p=34891181. The guide has download links for the files you'll need to restore the phone back to the correct build version.