So last night I used the GUIDE to odin from oc3 to oe2 . I downloaded both TAR files that were included in the guide but only ended up flashing one using ODIN. I used the PingPong root vulnerability and rooted. When I woke up this morning the messaging app was all out of whack. I am unable to send new messages and unable to read any new incoming messages. The notification still works and the messages are coming through, just not showing up in the messages app. My problems didn't stop there. Google Play is not loading up correctly what-so-ever. I did have oc3 rooted last night with everything working fine. It was not until I flashed oe2 with ODIN then rerooted with PingPong when things started going wrong. I think the easiest fix would be to factory restore and try the root process again. Maybe someone else has some experience with this problem.
I guess I am trying to figure out a way to get things working without having to use ODIN or a computer. I am at work and don't have access. If I do a factory restore via the phone, will it take me back to oc3? or leave me on oe2? I could essentially reroot after that and have a working phone for the time being.
If you perform a factory data reset you wok still be on oe2
Related
I rooted my Epic 4G a few weeks ago. I had problems with the 3G, so I eventually had to do a full wipe with Odin (just flashing the kernel never worked, it kept failing. Only a full wipe worked.) So I re-rooted so I could restore all my backups with Titanium Backup and just kept root.
Well, today I went back into Titanium Backup only to discover that it said I was NOT rooted. This didn't make any sense...I did get one OTA update to my phone, but I was under the impression that these didn't remove root.
So I thought maybe it was my BusyBox...I used the link within Titanium to DL BusyBox. Went into the BusyBox installer, and it's main screen said I WAS rooted...the Heck?
So I tried to install, but I got the error saying it failed. The exact wording was "The application failed, either because your device is not nand unlocked or we were unable to remount."
So what gives?
I tried to re-root using the one-click, that didn't work. I tried to uninstall the root using the one-click uninstaller, that didn't work. The windows just hang up and don't do anything. I tried to re-flash the kernel with Odin and, just like last time, it didn't work. I get the feeling I'll have to do what I did last time and do a complete wipe with Odin, which will really suck because I'm not able to recreate any backups this time around.
sounds like a superuser permission issue to me.
ota removes root, always, just reroot
So last night I was using My Backup Pro to back up my files before I tried flashing the new CM for our phone and noticed that I didn't have busybox installed. I installed it and backed the phone up overnight. In the morning I noticed that my WiFi wouldn't turn on and that I couldn't flash anything. Ran root checker and my root is bad now. Anyone else experience any problems with rootbox? That and backing up my stuff are the only things I've done different lately. My phone is rooted with towelroot and bumped. I really don't feel like unrooting and returning back to stock to start the process over again but IDK how to fix the root. Root checker gives these error messages.....
Don't know much about the code, anyone have any suggestions?
kinjo1023 said:
So last night I was using My Backup Pro to back up my files before I tried flashing the new CM for our phone and noticed that I didn't have busybox installed. I installed it and backed the phone up overnight. In the morning I noticed that my WiFi wouldn't turn on and that I couldn't flash anything. Ran root checker and my root is bad now. Anyone else experience any problems with rootbox? That and backing up my stuff are the only things I've done different lately. My phone is rooted with towelroot and bumped. I really don't feel like unrooting and returning back to stock to start the process over again but IDK how to fix the root. Root checker gives these error messages.....
Don't know much about the code, anyone have any suggestions?
Click to expand...
Click to collapse
What does SuperSU or Superuser state when opened? Have you updated the binary or is that even an option?
Everything was up to date when I checked last night and supersu was working fine. I ended up unrooting and reverting back to stock and starting from scratch.
I just purchased a new S6 today from Best Buy. I was lucky to get a OE2 version, saw it on the box labe before I bought it. I would like to root and install a ROM but I want to wait until my 14 day return period is over in case I'm not satisfied and decide to do something else. The prompt to update pops up constantly. It's very annoying and I'm concerned I may accidently tap the update button. I'm coming from a S4. On the S4 I was able to use Root Explorer to rename a couple of system files to stop the request for updates. Since I'm putting off rooting until after 14 days that method is not possible. I cannot uncheck to automatically upgrade because when I go to system update I only get the "update ready to install" message. I tried booting to recovery and wiping system cache but that had no effect. Any suggestions? Thanks
I used titanium backup to freeze mine but I know that requires root access... Before I had that I would constantly keep my phone in airplane mode and set mobile data limit low so it wouldn't dl it... Just an FYI I'm on a rooted gs6.. Still no exposed for our phones, it's for 5.1.1 and there's the risk for stage fright as its not patched on the root able version.
templton said:
I used titanium backup to freeze mine but I know that requires root access... Before I had that I would constantly keep my phone in airplane mode and set mobile data limit low so it wouldn't dl it... Just an FYI I'm on a rooted gs6.. Still no exposed for our phones, it's for 5.1.1 and there's the risk for stage fright as its not patched on the root able version.
Click to expand...
Click to collapse
Thank you very much for the reply. Someone on another forum suggested I do a factory reset, don't enter any user information during initial setup and disable auto check for updates. I tried that but apparently you can no longer stop checking for firmware updates. So I said screw it and rooted last night. I can always Odin back to stock if I decide not to keep the S6.
Eddie Hicks said:
Thank you very much for the reply. Someone on another forum suggested I do a factory reset, don't enter any user information during initial setup and disable auto check for updates. I tried that but apparently you can no longer stop checking for firmware updates. So I said screw it and rooted last night. I can always Odin back to stock if I decide not to keep the S6.
Click to expand...
Click to collapse
The smartest thing to do would be to root, freeze the SDM, then, If you no longer want the device, unroot using Odin
New to the forum, so my apologies if I leave important information.
Short of it is I was having problems post TMobile update (duplicate text messages and random rebooting). Decided to DL Titanium and back everything up... but needed root. Rooted phone via Odin and super user app. Backed my data up, but when I went into my office Good Enterprise and company WIFI were disabled due to rooting. I attempted to uncheck superuser within the app and rebooted... now getting "kernel seandroid not enforcing". I attempted a factory reset wipe with no success. I am very new to this process and I am sure I f***** in up in a myriad of ways. I am hoping somebody can help get me back working either with stock or custom ROM.
Thanks in advance.
Meximize said:
New to the forum, so my apologies if I leave important information.
Short of it is I was having problems post TMobile update (duplicate text messages and random rebooting). Decided to DL Titanium and back everything up... but needed root. Rooted phone via Odin and super user app. Backed my data up, but when I went into my office Good Enterprise and company WIFI were disabled due to rooting. I attempted to uncheck superuser within the app and rebooted... now getting "kernel seandroid not enforcing". I attempted a factory reset wipe with no success. I am very new to this process and I am sure I f***** in up in a myriad of ways. I am hoping somebody can help get me back working either with stock or custom ROM.
Thanks in advance.
Click to expand...
Click to collapse
Try this using Odin. Read the instructions below.http://www.sammobile.com/firmwares/download/54617/N920TUVU1BOH4_N920TTMB1BOH4_TMB/
Ok, I am a regular student here and have rooted several phones.
I rooted OE2 on a Verizon S6 with Ping Pong then I took the OTA from Samsung and lost root.
I then decided to try and return to stock after constant annoying update messages.
So I used ODIN to flash OE2 and all He++ broke loose.
I have not been able to boot up for 2 days. I have factory reset and reflashed with ODIN multiple times.
Sometimes it will go through optimizing apps and either shutdown or lockup, then it will quit after a while and not do anything other than the Samsung screen.
I cant boot into a real recovery and wipe cache because the firmware from sammobile.com doesn't have any recovery other than totally stock so, its applicable option is factory reset.
The blue light will pulse when not charging as well.
I am currently downloading the PD2 Firmware hoping it will work.
I would really appreciate any help, thank you.
xxvisionrider said:
Ok, I am a regular student here and have rooted several phones.
I rooted OE2 on a Verizon S6 with Ping Pong then I took the OTA from Samsung and lost root.
I then decided to try and return to stock after constant annoying update messages.
So I used ODIN to flash OE2 and all He++ broke loose.
I have not been able to boot up for 2 days. I have factory reset and reflashed with ODIN multiple times.
Sometimes it will go through optimizing apps and either shutdown or lockup, then it will quit after a while and not do anything other than the Samsung screen.
I cant boot into a real recovery and wipe cache because the firmware from sammobile.com doesn't have any recovery other than totally stock so, its applicable option is factory reset.
The blue light will pulse when not charging as well.
I am currently downloading the PD2 Firmware hoping it will work.
I would really appreciate any help, thank you.
Click to expand...
Click to collapse
It should work with the PD2 update. Once you accept an update you cannot go backwards in firmware only forwards. Every OTA is a bridge that burns as you cross it.
OK, will let see what happens. I tried the emergency recovery options on smart switch and it didn't work at all. It wouldn't go past recognizing the phone.
I was able to attempt to Odin flash pd2 this am but the pit files I got here reported as corrupted. Then I could no longer locate the pd2 file I downloaded after trying to flash it in odin. It was also from a link on here as well... So I will try again tonight.
Its been a rough several days..... I have uninstalled the kies leftover files via terminal, installed java updates, installed Heimdall updates, tried the one click Heimdall, attempted to learn what in the He}} the Heimdall program was asking me to load as I have no clue which files go where in the program, read tutorials on it.
I unzipped my PD2 (Verizon) file and it runs for a minute and then tells me the file is corrupt. It is the 3rd MD5 I have downloaded. I have no retrievable PIT file and have downloaded no less than 12 of them all of the USA VZW type and ODIN and Heimdall do not like any of them.
I really do not know what to do from here other than throw this POS in the lake. I am so far past frustrated I don't know what to do.....
Any help would be truly appreciated.......
Thanks!
I give up, not really any help here either so I just paid $200 deductible. Bummer.