So, I'm a total newbie at android rooting but, I decided to take a shot at it a few months ago. I flashed the kernel of my Android 5.1 Note 5 to a rooted one, now, I'm about to give the phone back to T-Mobile, but I certainly want the root gone before I do that just for the sake of things going as smoothly as possible.
I didn't flash any custom roms or anything, its still the stock rom, just a rooted kernel. Would doing a simple phone reset through the normal settings put everything back to normal/unroot and get rid of that "Kernel is not seandroid, enforcing" message on boot? Or would it require just simply flashing a stock kernel back through Odin? Or something else? I really just need that damn message gone.
If need be, I have TWRP flashed as the recovery as well.
// NEVERMIND, problem solved.
how do you solved it?
I think Odin should do the trick.
Related
Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
try this: http://forum.xda-developers.com/showthread.php?t=867617
There are others like it too. Just don't try flashing the bootloader or sbl !
AbsoluteZero said:
Hello All,
I'm starting a new thread, because I am in a situation where I want to get my girlfriends phone back to stock so I can warranty it, and hopefully someone here will have the answer and people will have one place to look for putting their Roger's Samsung Captivate back to stock.
I'm hoping someone can tell everyone why we can't seem to get back to stock on these ROM's, here are the things I've tried:
Originally cleared everything rooted the phone through an update.zip, then put on the Clockworkmod Recovery and flashed Cognition v2.3b8, Trying to fix, battery life and lagging issues on her phone, (had a couple of random restarts the day before I flashed, so I was hoping it would fix that).
Then she started noticing the random restarts more often, so I tried:
clearing everything again through the recovery and tried restore from my backup to put things back, it looks like it extracted (or Installed) successfully then when it boots, it gets to the black, "Swipe" screen, then it freezes.
I tried to flash the Rogers_Stock.zip, same thing. Then I extracted the zip, and put it into the backup folder, hoping it will restore it like a normal restore, same thing.
So right now I'm stuck with a phone that says AT&T when it boots (I read one post on how to remove that) and cognition boot up.
Basically, I want to get this to look enough like stock to return.
I was thinking I can try to get rid of that AT&T popup, then flash the stock ROM, and say it just stopped booting for some reason. But then I still need to get rid of the Clockworkmod Recovery.
Wow that was a mouthful.
Thanks in advance for any help anyone can provide for use Roger's users (or their significant others).
AZ
Click to expand...
Click to collapse
Gin's got you on the right path for sure. A couple more items for you:
This post should help with removing the AT&T bootup logo: http://forum.xda-developers.com/showthread.php?t=849789
If you use Heimdall to flash the Rogers stock firmware that is in the post the Gin linked to then you will absolutely need to follow the instructions to use the Heimdall drivers for your captivate when it's connected or it won't see the device when you tell it to start. Like gin said, don't touch primary or secondary bootloader, leave those out and don't try to repartition it.
Restoring the stock firmware will remove the custom kernel that is installed with Cognition (at least it should) and so the Clockwork recovery should no longer be installed once the restore to stock is done. You can double-check once you are back to stock by powering off the phone and then hold both up and down volume + power, let the power button go after it restarts once and you see the I896 for the 2nd time. It should take you to the stock 2e recovery screen. If it does, you should be golden.
HTH
Wow, thanks all,
I used that method without the PIT file,
I just want to say thanks to everyone that offered help,
Goina try to send it for warranty now.
thanks again,
Joe / AZ
Hi guys!
I'm still new to XDA, and I hope this fits here.
A year ago, I decided to root my ATT Note 3 on 4.3 with Kingo Root. After a while, my GPS didn't work, along with some of the stuff in the phone. I plan to unroot it and then restore it to take it back to ATT with the warranty. However, when I unrooted, it still show a custom padlock on my phone. As time moved on, I gave up about it. I then use safestrap and flashed Knoxraid on my stock rom. However, my network keeps dropping with knoxraid, and I constantly have to restart to fix it. (My APNS were okay) When I did more research, I found out hash no longer supported SS, and the Dev's all bailed on knoxraid. I decide to flash another rom (Dynamic kat) However, my SS no longer works before I can flash a new rom. Every time I turn on the phone, the screen would become black for about 5 seconds after the samsung logo. (This was usually where ss would appear). When I click the bottom 2 buttons, it would vibrate, but still black. If I leave it alone, the google would boot up. I was wondering if there is any way i can boot another rom in my phone or fix this issue with knoxraid. I did not tripped knox yet, still 0x0. However, I don't mind if I void it, since it's already passed my 1 yr.
Thanks
Bump
title
Are you still on 4.3 Jellybean?..or did you update to Kitkat?. Either way if you can get to download mode just odin back to MJ5 if your 4.3. If your Kitkat theres no going back to Jellybean and you will have to odin back to NC2 kitkat
FIREKAT V13X...so good you wanna slap your mama
butchieboy said:
Are you still on 4.3 Jellybean?..or did you update to Kitkat?. Either way if you can get to download mode just odin back to MJ5 if your 4.3. If your Kitkat theres no going back to Jellybean and you will have to odin back to NC2 kitkat
FIREKAT V13X...so good you wanna slap your mama
Click to expand...
Click to collapse
I'm already on 4.4.
Can I do that with locked boot loader ? And I can only flash the ATT stock KK Rom right?
Um I dont believe you can flash anything on 4.4. It breaks root. There may be a metheod..i cant remember what post
FIREKAT V13X...so good you wanna slap your mama
Well, I can care less about the root atm. The Usability of my phone is more important. I can root anytime after I flash my phone. Thanks.
Well you have to have root to be able to flash roms...unless you just want to odin back to NC2
FIREKAT V13X...so good you wanna slap your mama
ATT Note 3 Custom Rom Problems
If you don't have root use towelroot to root and get the safestrap 3.75 apk and try uninstalling and reinstalling or just installing it and you should be fine. I have the S5/N4 rom from the international forum and its perfect, just have to flash the MTP fix and deepsleep fix. Try it out! If you want...
Reinstall
Okay, so after a long time of trying to fix this. I found out that it was somewhat of the Knoxraid problem. I had to wipe date from Recovery, and then Delete and re-install SS. Downgrade from 3.75 to 3.72. Now SS works, and I can boot custom rom from there.
OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.
Can you not just odin to reflash it back to stock 4.3?
Maybe but i cant locate the files to odin and im not that famaliar with how to use odin. Can some provide a liitle guidance.
cd23murray said:
OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.
Click to expand...
Click to collapse
I don't think you will find it NB4 build for odin. I was looking for firmware for some time and had no success. You need to get back to NI9 than find update NI9 to MJ5 and then MJ5 to NB4. So i will suggest find this updates so you can sideload after you get stock NI9. and i think you have all files you need to do this here : http://forum.xda-developers.com/showpost.php?p=51468226&postcount=10
Hey everyone, hopefully someone can back me out of my mistake. I was running CPF1 on my galaxy s6 on ATT. i saw a thread (not on this forum) to root marshmallow and proceeded to download and flash a kernel. It flashed successfully but i believe the kernel was for 5.1..1 and now my phone will not do a damn thing. i can get it back into download mode, but it's been several years since ive flashed anything to my device. Total negligence for not fully reading on my part, but is there a STOCK cpf1 kernel i would be able to flash back to my phone for it to boot up? thank you so much in advance!!
dsedapr said:
Hey everyone, hopefully someone can back me out of my mistake. I was running CPF1 on my galaxy s6 on ATT. i saw a thread (not on this forum) to root marshmallow and proceeded to download and flash a kernel. It flashed successfully but i believe the kernel was for 5.1..1 and now my phone will not do a damn thing. i can get it back into download mode, but it's been several years since ive flashed anything to my device. Total negligence for not fully reading on my part, but is there a STOCK cpf1 kernel i would be able to flash back to my phone for it to boot up? thank you so much in advance!!
Click to expand...
Click to collapse
I just went through the same thing yesterday. As far as I could find out, there are no cpd1/cpf1 kernels available online. BUT if you have a Best Buy near you that has a Samsung kiosk you can get a technician there to flash a stock rom for you.
I didn't do this, but you might be able to downgrade to Lollipop (which is rootable) if you tell the tech that's what you had. Mind that you're going to lose all the data on your phone regardless.
Going back to stock from my rooted PopRocksV14. Haven't flashed ROMs in a while, so super rusty. Input welcome. TIA!
Questions:
1 Any faster mirror for N910TUVU2EQI2 than https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/TMB/?
2 How is the latest stock FW? Any reason not to upgrade? I'm just looking to get a stable phone and decent battery life, don't care about bloat
3 I'm looking to overwrite any Kernel and partition changes that PopRocks might have made, so is flashing back to stock rom going to do this?
Steps:
1 Make sure Samsung drivers installed
2 Download Odin 3.13 - https://odindownload.com/download/#.WyvXuCAnbAQ
3 Download EQI2 rom
4 Factory reset N910T
5 Run Odin as Admin
6 Start N910T in Download mode
7 Connect phone to PC via USB cable
8 Check Odin that COM is connected
9 Click PDA and select EQI2 tar file
10 Make sure Auto Reboot and F.Reset Time are checked, all other options disabled
11 Click start and wait for update to complete and phone to reboot
12 Factory reset N910T
I went ahead and tried it after the Sammobile download completed and it worked!
sfsilicon said:
I went ahead and tried it after the Sammobile download completed and it worked!
Click to expand...
Click to collapse
@sfsilicon - hope you're still monitoring this old thread. I'm trying to revive my old Note 4 I found in a junk drawer - for my 6yo boy. It had some custom rom on it, and I've now attempted with Odin to restore the image EQ12 you had listed - it appears to be the most recent.
Oden gets about 99% done then fails and now the phone is stuck in some sort of emergency mode. I can get into download, but not recovery. I assume I hosed it - maybe the bootloader was the wrong kind from the prior custom rom (and I didn't take note of what it was since I was just wiping it out).
Bummer.
Sorry to hear about your problems. It has been a while since I reflashed back to stock. Did it on two note 4s. From your description only thing I can think of would be that you flashed from a rom that was from an earlier Android version to the latest and it is missing some files or partitions that would normally be part of that type of transition. E.g. if you had done all the updates via OTA vs gone from your custom rom to the latest stock TMO release.
So try to figure out what Android revision your custom rom was before this latest flash. Then check the posts about moving from that revision to the next latest one and see if there is anything special in between. You can then look for the stock TMO rom that matches your custom ROM then flash back to that. Once you have a ROM working, even an older you can flash the next updates till you reach the final/latest TMO version or just OTA it.
One other thing to check is if your custom ROM did any changes to the kernel files or other stuff. Then check with the old custom ROM how to reverse them. Not sure if flashing a stock TMO rom undos all this. Its been a while but would think so but its still a step to check.
Hope this helps and good luck! I'm actually using my N4 currently. I use it to hold a foreign SIM when I am travelling. Sort of a glorified hotspot. Gave my 2nd one to my mom where the large screen helps with reading text. Its still a nice phone.
Thanks for getting back with me. I was under the impression that regardless of what custom rom may have been on the phone, Odin was a way to wipe the slate clean and put it back to day-1 state. I have no idea what OS was on there, but I do recall a warning about the bootloader being modified and it may be impossible to roll back. That's going off of memory (which has a very low confidence level).
Now I can't even get it to power up at all. I think I'm going to bail and just get a cheap Chinese android phablet - don't need cell service. It's getting to the point that my time and patience is worth more than what I'm spending to rehab this thing. Sucks too... When I first got the N4, I was pretty proficient at swapping roms... But since I've not played with them in years, I've all but forgotten the basics.
Thanks for the suggestions, tho...
E