Hi guys,
I have the international version of the Galaxy S3 and I have a little problem. The first thing I did when I've got it was root it with Odin and everything went fine but now I see the rooting doesn't work as it should. Buisybox says it needs to be rooted and SuperSu is configured to allow everything. Also, when I launch CWM Manager (v3.55) a popup says that it should be used with CF-Root v5.0 or newer.
My question is, how should I update everything? When I format/upgrade my old Galaxy S2 to give it to my dad, I simply flashed CF-Root to the CW10 and it broke the phone's boot. Luckily I had backed up everything using CF-Root the day before. Should I uninstall it first? How? And how can I do it without loosing the backup I'll make to my S3 before I try anything?
What I mean is... how can I update everything in a "clean" way?
Thanks in advance!
Related
Hi all. Tried my first root + custom rom installation and i messed up the device..
i had the newest KIES firmware update (phone XXBMA5) and (XXBMA6) and i rooted the device with odin (3.07). That went OK.
Then i installed the CWM recovery with odin and that was OK too.
Then i downloaded the latest Omega Rom (i missread that it supports N8020) and followed the installation instructions to the point where it started installing Omega V2.0 from SDCARD and then it asked me to select device from a list that included only (N8000,N8010,N8013)..
So the situation now is that i have working odin, working CWM and backup of the EFS (img+tar) but no working recovery. i live in Finland and the device is Sonera locked i think, so the stock roms (international) do not work i guess.
KIES has a backup of my Note but i can't even get to a point where KIES discovers the device.
So basically i think i need a working ROM for my model (Note 10.1 4G N8020), or can i recover the original samsung software somehow ?
Any advices ?
Removed
Just a thought, but can't you reflash CWM or the stock recovery?
If you didn't install the rom why do you need to re-install anything. Just powering down and powering up should have left you as was....
Alajarvi84 said:
working CWM .......... but no working recovery.
Click to expand...
Click to collapse
Maybe i'm missing something but isn't CWM your custom recovery?
It doesn't sound like you've actually installed any rom yet.The Omega installer doesn't actually install anything until a few steps after the one you mentioned about the model type.
I'm with ultramag69 on this one. You should still be on a stock rom unless you already wiped your original rom.
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
What is truly amazing is that i did not brick the device tough..
switch from cwm to stock
Alajarvi84 said:
Hi again. Problem solved, just had to do emergency thing from KIES. Like i said this was the first time trying root + custom ro install and to be honest it went to ****. Somehow i managed to delete the stock firmware so that is why the recovery gave me (no files). I did make some backup but when tried to restore it said MD5 mismatch or something. At first the KIES emergency recovery could not find the device, but after i switched from CWMcto stock recovery it worked.
So what did i learn from all this ? Nothing, because i am getting too old (tired+lazy ) to do proper investigation. So one could say my strategy is to bang my head to the wall as long as it takes to go trough. Even if i could just go around it
So basically i am now at the point where i started, with stock 4.1.2 rooted. Used the triangle away to wipe the (6) custom installs or something away, but it still says custom in the settings> information. Does this mean that OTA won't work ? Any way around it ? Because i would like to check now and then that is my version of android the newest one..
Could someone recommend a custom ROM for my Note 10.1 4G (LTE) N8020 4.1.2 because the only one i was able to find was the CyanogenMod (or something) and it basically makes the S-Pen (almost) useless. What i would like is the Omega ROM, but like stated before the installation only supported N8000, N8010 & N8013...
Added screenshot from info.
Thanks anyway
Click to expand...
Click to collapse
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
jjndimp said:
How did you switch from CWM to stock? I have having a problem syncing with kies also using omega rom on n8013.
Click to expand...
Click to collapse
I was not easy, i just tried the download mode over and over again with KIES open in windows and somehow it finally did find my device and offered a emergency restore. That is it, and the device was restored to default "original state".
OMG.... one would think after nearly having bricked your device you would either A) stop messing around with it or, B) read and learn more about what you're wanting to achieve and THEN maybe trying something with the ABSOLUTE certainty that a backup to restore is available to you in case of any mishap!
Moral of story :
Don't do anything until you are absolutely sure you have read EVERYTHING about what you are going to do.
For others wanting to mess with their devices, take heed! You may not be as lucky as OP (or troller) whichever is applicable.
There comes a certain point, that when crossed one does not care what happens to the device at hand. After fighting with my n8020 for several days in a row i couldn't care less, and like said before i dont have the level of enhusiasm like i had when i was younger. Of course i know now what went wrong.. But seriously, these are just overpriced toys, so it's not a matter of life and death.
Sent from my GT-N8020 using XDA Premium HD app
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Njord0 said:
I'm currently on 4.0.4 (Canadian version) N8010 and I want to update to 4.1.2 (canadian? not sure if it really makes a difference). I get the notification for the update, but when I select it, it fails, and it also fails with Kies.
When I first got the note I opted for the exynos exploit to root my tablet. I was under the impression that if I disabled root from the app my status would revert back to "non-custom". I've uninstalled exynosabuse and busybox (i think supersu uninstalled with the root disabled) and I've restarted multiple times and waited a few hours. No change. I think I'll try to re-enable root and restore some apps that I froze with titanium backup to see if it reverts back.
The other option I guess would be to get the Canadian rom and flash via Oden. although I think that would wipe by note, which i would like to avoid. I found some links to the canadian rom, but they're down.
Thanks for the help/advice.
Click to expand...
Click to collapse
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
kkretch said:
Did you install a custom recovery or do you still have stock recovery installed and can you tell us your ROM's build number.
.
Click to expand...
Click to collapse
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Njord0 said:
I still have the stock rom, I haven't installed anything custom, just use the exploit for the root access.
Build number: IMM76D.N8010WALG4
Click to expand...
Click to collapse
Without a stock 4.1.2 firmware for your device it looks like you are going to have to do a factory reset to use Kies.
I think your options are limited..........
Have you considered using a firmware from another country?
You know there is a backup program called Helium that does not need root, you may want to consider using it to backup all of your data and then do a factory reset.
I don't know if I have helped you any............
Hey all, I have a bought a galaxy tab 2 on android version 4.1.1 a while ago.
Back then I rooted the tablet so I could run whatsapp etc. on it.
After some research last days I noticed there were a few updates for the tab, and I decided that i want 4.1.2, (but still with root)
now my question is(since I can't update over the air):
How can i update my tab to version 4.1.2 while keeping the root acces and without losing or need to reinstall my apps?
because if i download the stock 4.1.2 ROM and install it, I lose all my apps and I need to reinstall it (from my experience with the htc legend).
thanks in advance!
Make a backup in CWM and install the ota; it seems that usually with this device OTA's will install properly when rooted.
You know, it's a sad day when your cellular service is faster than your home broadband.
MultipleMonomials said:
Make a backup in CWM and install the ota; it seems that usually with this device OTA's will install properly when rooted.
You know, it's a sad day when your cellular service is faster than your home broadband.
Click to expand...
Click to collapse
No, that is the problem. It is not possible because it will say taht my device is modified. But i decided to try cyanogenmod on it. And if it doesn't suit me then i will install stock 4.1.2.
but still thanks
Hi I recently upgraded my phone earlier this week to lollipop 5.0 second update. Software version BOD3. I used cf auto root and soft bricked my phone. Is there any way to root this version of lollipop for my phone. Thank you
Oh I forgot I have the sprint Samsung Galaxy s5 G900P
garbage30 said:
Hi I recently upgraded my phone earlier this week to lollipop 5.0 second update. Software version BOD3. I used cf auto root and soft bricked my phone. Is there any way to root this version of lollipop for my phone. Thank you
Click to expand...
Click to collapse
You need to be reading/checking the Android Development thread. Read the OP's the the roms you're interested in. If they say they are pre-rooted, then all you have to do is use Odin to install a custom recovery first. Plan in advance, you'll need to have the rom you choose copied to your phone first. Then, in Odin un-check auto-reboot. When it finishes installing, unplug your phone, pull the battery. Reinstall battery and immediately go into recovery (Home, Volume UP, Power) and flash your rom. Again, I can't stress enough, "read" about the rom you're interested in. I can give you a couple of rom's that I know will work with OD3, but the decision is yours:
MOAR 6.2. This one has a strong user community for support, more features (and growing) then you know what to do with!
Stock De-odexed Very new, but if you want stock and rooted without any bells and whistles, this would be the one.
Hey can u help me again i downloaded the stock rom and wiped everything in recovery. Then i updated in recovery.everything loaded fine but it is telling me that it is.not rooted. Su say cant get binary and.root checker tells me.no root. I tried to reboot the.phone but its telling me.no root. I thought the.rom was rooted. Am i doing something wrong.thanks
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
So have i with my S6. No cure so far, tried everything. Waiting for chainfire to jump in...
Verstuurd vanaf mijn SM-G920F met Tapatalk
I have also just experienced this. Everytime I try to remember root and run root checker it says not rooted.
try root with twrp and a kernel like "adam kernel" or a nearly stock one. Then try flash form recovery supersu 2.74
Ive got the same issue. I have G920i stock 6.0.1 rom and stock kernel and rooted using cf-root. However today i noticed my device is not rooted anymore. Also a week ago my phone completly froze and i had to go to download mode and reboot the device. Im not really sure if this incident was related for the device to become unrooted. Any help is appreciated
Same problem! I rooted my galaxy s7 with cf-root and odin and it worked fine for a while until I got no root privileges and had to reroot it. It worked once more and again - unrooted by itself, only this time rooting doesn't work! it says that it roots it but when I check supersu, it says no SU binary. Please someone help!
same issue
deveice is s6 and china version.
I just bought it one week
wait the solution.
Strange, same thing just happened to me today in Samsung S7. Phone restarted on its own and now no root access. I had it rooted like 2 months ago with Cf and Odin and had been working fine. What happened??
same here , S6 G920F... lost all access from rooted apps tried re-root with odin , also installing supersu again and again , deleted also all the required-rood apps ... nothing works
Hey guys this is already solved. Samsung pushed a security policy update that broke the root. So now the way to go is that you need to flash stock rom with odin. I used smart switch which is easier and worked too. Then after you have stock rom you root using the new cf-auto root by chainfire. Enjoy.
LAUNCHERMONKEY said:
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Click to expand...
Click to collapse
This happened to me today, I fixed by restoring to stock using smart switch and then using cf-autoroot to re root.
I had same problem
r00tkiller said:
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
Click to expand...
Click to collapse
Basically I just fixed it by reflashing my ROM straight on top of my old ROM (ressurection remix) I did not wipe cache or dalvik just straight reflashed ROM and it fixed it
Nothing else I tried worked not sure if I will get the same error again but it worked for now
Plus I had error previously with su binary update think this is the cause