[Q] Connect device to Odin - previously f. reseted - Galaxy S III Q&A, Help & Troubleshooting

Sorry if this has asked before a thousand time, but I'm not sure if what I've done before changed anything from standard operation.
I once did factory reset the phone - its already rooted at the time. It was since that time both Heimdall and Odin can't get access or permission to load things into the phone.
The device was rooted using CF-Auto Root, currently have SuperSU, Titanium Backup, Root Browser Lite, Rom Manager and TriangleAway installed. No CWM and such. Just to note what happened to the phone after factory reset, the device status switch to "Normal" and in download mode, it shows "Custom Binary Download" to No, "Current Binary: Samsung official", and "System Status" to Official ; Everything except binary was before factory reset shown the otherwise (no to yes, official to modified).
Once again, I say sorry if this thing had asked before.
Thank you !

Related

[Q] Need help - failed OTA update with "Failed to update firmware" message

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.

Galaxy root issues with super SU and SU binary

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

issue with KNOX on my S3

Hi, I had a phone which had a corrupted EFS. I followed the procedure here -> http://zidroid.com/how-to-fix-failed-to-mount-efs-for-galaxy-s3-gt-i9300/ and the unit is now booting fine. but it is factory mode. I saw the follow up post regarding how to remove the factory mode, but that requires root access. I flashed CWM recovery on my phone, and also SuperSU. However, after I had flashed superSU, KNOX came into the picture. I cant run SuperSU because of KNOX. So I searched how to remove KNOX. Since I still hadnt had ROOT, I tried to remove it using the steps outlined by samsung. However, when I open the KNOX app in the appdrawer, it says It hasnt been installed yet and I need to install it... so I try to install it, but after downloading it cant install it due to it being in factory mode!! (!!!)
So now I am stuck. I need to exit factory mode, and I need root. I cant root because of KNOX. I cant disable KNOX because I need root (or need to install KNOX to remove it??)
I also found a zip file Degrated_Shadow's_KNOX_removerV2.1 but it didn't work..
any help would be appreciated!
The i9300 doesn't have knox.
It does on 4.3.. I get a "An application attempted to access system on your device without authorization" it has the shield logo..
No. The i9300 does not have knox on 4.3 or any other version.
Either you don't have an i9300 or have some other software installed.

Can't fix root. Do I need to flash recovery again?

So I just successfully installed CM13 on my i9300. Everything works fine, but I just found out I lost root rights.
I went and downloaded the Super SU app from the PlayStore, launched it and that gave an error that there's no SU binary installed and I need to manually root again.
So I downloaded UPDATE-SuperSU-v2.65-20151226141550.zip, put it on the sdcard, rebooted into CWM Recovery, installed the zip and booted back into the system (when prompted to fix boot I selected no as recommended), but now I STILL HAVE NO ROOT RIGHTS and the Super SU app still gives the same error.
Is there a specific SuperSU.zip I should be installing in recovery to make it work?
Or is something wrong with the recovery and do I need to flash that through Odin? (I don't think this is the case though, as flashing CM13 and gapps went completely fine)
Thanks for any isnight and tips
There is already Root option in developer settings.Can you try it?
ArdaCsknn said:
There is already Root option in developer settings.Can you try it?
Click to expand...
Click to collapse
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
warriotox said:
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
Click to expand...
Click to collapse
Flash rom again and dont flash SuperSu its better now without using SuperSU
I got the same problem. I tried to root with odin again but it didnt work...
Flash cm13, wipe data and cache and flash cm13 again. Cm13 should be pre rooted.
Sent from my HTC One M9 using Tapatalk
Hi Guys, I have the same problem too after CM13. Unfortunately rooting again with ODIN flashed stock recovery back and am stuck on CM13 now with no root and stock recovery. Can someone help please? Below is the detailed description of what happened.
----------------------------
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
same here after rooting once cm13 by developer option, for some reason i had to use hide my root app, now unable to get root back
Its a problem with the s3, it forgets root. The most reliable is chainfire and sticking with a stock rom.
You must:
Wipe to factory,
flash an original rom via odin,
Boot straight to recovery and wipe to factory again,
Flash original rom again,
Boot straight to recovery and wipe to factory,
Allow the phone to boot.
You must flash at least twice and reset to factory at least twice, even tho I sad it thrice, to kill all remnants of the old rooted rom.
Then you can flash chainfire via odin and go from there.
Beamed in by telepathy.

S6 edge can't boot...

Hi
I'm on 5.0.2 rooted with ping pong root and stock recovery, knox still 0x0 that's why I haven't updated to 5.1.1
Just an hour ago phone went off and in the begining I was able to boot normally but it was stuck and reseted itself 2-3 mins after getting into the system....
At that time I was able to get into recovery and download mode normally
I decided to wipe cache partition just to see if it fixes anything so from that time it's stuck on samsung logo
I used odin to reflash stock rom but without better results, only thing changed is that when I get into recovery a dead android with a yellow triangle (not the red one inside android little man, just a yellow one connected to the android little man with a dotted line if this matters at all) appears before the recovery menu
Download mode still says "Current binary: Samsung official" and "System Status: Custom" just like before the odin flash
1) Only solution now is factory reset from inside recovery??
2) Can I get my files from inside somehow before factory reset or recover them just after the factory reset? It's 6 months without a backup now....
Thanks for your time
pamarakos said:
Hi
I'm on 5.0.2 rooted with ping pong root and stock recovery, knox still 0x0 that's why I haven't updated to 5.1.1
Just an hour ago phone went off and in the begining I was able to boot normally but it was stuck and reseted itself 2-3 mins after getting into the system....
At that time I was able to get into recovery and download mode normally
I decided to wipe cache partition just to see if it fixes anything so from that time it's stuck on samsung logo
I used odin to reflash stock rom but without better results, only thing changed is that when I get into recovery a dead android with a yellow triangle (not the red one inside android little man, just a yellow one connected to the android little man with a dotted line if this matters at all) appears before the recovery menu
Download mode still says "Current binary: Samsung official" and "System Status: Custom" just like before the odin flash
1) Only solution now is factory reset from inside recovery??
2) Can I get my files from inside somehow before factory reset or recover them just after the factory reset? It's 6 months without a backup now....
Thanks for your time
Click to expand...
Click to collapse
This is why you always keep a backup.
No backup = i don't care abut my data.
You might find with remaining files that stock firmware over the top doesn't help. Try flashing something newer like 5.1.1 or 6.0.1 . Will lose ping pong with a newer version. But speed and battery life are like 10x better.
I was always keeping a backup every month or two, it's the first time (and the last) I haven't done so for 6 months
I can't go with a newer version because I'm using SmartView app to stream my TV to my phone and it needs stock kernel which can't be used if rooted with a 5.1.1 or newer version
pamarakos said:
I was always keeping a backup every month or two, it's the first time (and the last) I haven't done so for 6 months
I can't go with a newer version because I'm using SmartView app to stream my TV to my phone and it needs stock kernel which can't be used if rooted with a 5.1.1 or newer version
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
Try this,it uses stock kernel
1. First do a factory reset.
2. If that doesn't help try a newer MM stock ROM.
3. Claim warranty.
4. No warranty? => Custom ROM
Even after factory reset, it is stuck after 1 min of getting into the system
Same thing happens when in recovery menu (I also get dm-verity verification failed), it is stuck after seconds....I don't understand....I even tried reflash stock fw of course....same thing happens....I barely get into the system home screen and then it freezes...only thing that is not stuck is Download mode which works....
If I let it on charger switched off it switches on by itself...getting into home screen and freezes after 1 min....
I also tried nand erase all from odin...results are the same...
What is wrong?
Please anyone help...
hello,
I've the international version G925F 64gb. I tried the CF-auto-root g925f
I follow every step posted in this thread. using Odin, put the phone in download mode using the 3 button-combo.
Odin starts and when it installs the recovery it fails?????
on my phone I see it says:
Custom Binary(recovery) blocked by R/L
ragulr2 said:
hello,
I've the international version G925F 64gb. I tried the CF-auto-root g925f
I follow every step posted in this thread. using Odin, put the phone in download mode using the 3 button-combo.
Odin starts and when it installs the recovery it fails?????
on my phone I see it says:
Custom Binary(recovery) blocked by R/L
Click to expand...
Click to collapse
Check your drivers.

Categories

Resources