Develop Bugs

[Q] Still have Bullet Kernel even when i unrooted back?

So i unrooted my phone back to stock and the funny thing is i dont have the stock kernel. i still have the bullet kernel.
What happened?
How can i fix it?

How did you unroot it? Sounds like you just flash the rom, you need to flash the stock kernel too. You also need to flash stock recovery
Sent from my SGH-T989 using xda premium

kernerl
i went into recovery and wiped data and then installed zip. SGH-T989-UnRoot_ROM_Zedomax. ..
now i cant update to 2.3.6

you can install the .tar file thru odin. that will give you the stock kernel back

littleshort said:
So i unrooted my phone back to stock and the funny thing is i dont have the stock kernel. i still have the bullet kernel.
What happened?
How can i fix it?
Click to expand...
Click to collapse
View attachment SGH-T989-Stock-UVKL1.tar
this what i used simply put it into odin

littleshort said:
i went into recovery and wiped data and then installed zip. SGH-T989-UnRoot_ROM_Zedomax. ..
now i cant update to 2.3.6
Click to expand...
Click to collapse
you need stock recovery to do OTA updates. that file only gives you the ROM
I believe you can update through kies too, or flash one through odin.
but the safest way to do OTA update is to have stock everything (rom, recovery, kernel)
there are people who seem to have done the ota update even with some custom stuff.. but not recommended

thanks for the kernel...
now my computer or kies is not reading the phone. :$

how did you go bout installing it?
---------- Post added at 06:22 PM ---------- Previous post was at 06:14 PM ----------
this should be your guide
http://forum.xda-developers.com/showthread.php?t=1311229&highlight=stock+kernel

Clear Answer For Unroot So I Can Update OTA Please

I keep getting the new OTA IMM76I update for my Sprint Galaxy Nexus and every time it downloads & starts to install it just opens up TWRP recovery and nothing happens...
I tried to use the Nexus Toolkit as well and do exactly what it says but get hung up on "waiting for device" after it extracts the files and everything...
I've been searching for 4 hours to try to get this update done because my calls keep dropping...
is it because I have the Franco Kernel installed on a rooted device?
no ROM or anything, just rooted with the Franco Kernel...
I tried like hell to find the stock kernel but couldn't...
DAMN this is aggravating
could someone PLEASE either explain or point to a link where it explains how to deal with this issue?
HATE having a brand new phone and the calls keep dropping....
I know there are "lots of threads on this issue" already but none clearly explain how to fix THIS issue...
please hep me out...thanks in advance.

http://forum.xda-developers.com/showthread.php?p=20843237
While the above link is for how to manually install updates, the reasons why an ota update won't install are the same: if you want it to install ota, you need: the stock kernel, stock recovery, stock radio, and stock rom (with no original files missing/modified). Additionally, all of these have to be the same version.
Maybe you could also get the ota update file name for us as well.
Sent from my Galaxy Nexus using Tapatalk 2

does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
another issue I'm having is damn CWM....I have TWRP on here now and when I go to flash CWM through ROM Manager it get all the way to the end, freezes then fails...can't seem to get CWM installed for my life.
also what is all this "yakju, takju, etc..."??
I'm new to this device from an Evo 4G where we just download & flash and all updates work..never had an issue like this.
my device is v4.0.4., build Imm76D.L700FC12
baseband L700.05 V.FC12/L700.FC12
on the bootloader I saw "toro" on there so I'm guessing that's because it hasn't been updated, correct?
thanks.

broad_st_bully said:
does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
Click to expand...
Click to collapse
If all you changed is the kernel, then all you have to do is flash the stock kernel.

efrant said:
If all you changed is the kernel, then all you have to do is flash the stock kernel.
Click to expand...
Click to collapse
would you have the stock kernel?
can't seem to find it...

Try the GN root kit. You'll find it in the dev section. That will get you back on stock kernel.
Sent from my Galaxy Nexus using Tapatalk 2

You need to have stock recovery too.

broad_st_bully said:
would you have the stock kernel?
can't seem to find it...
Click to expand...
Click to collapse
Unfortunately I do not (I don't own a Sprint device), but I'm sure that it is floating around somewhere.

Unroot using voodo before install of new OS

Does anyone know if I use voodoo OTA rootkeeper to temp unroot my verizon galaxy nexus (toro) and install the new OS jellybean will I loose the root.
If I can do this will it save all my data and stuff and just update my present operating system without having to do a factory reset.

Are you on stock or a custom ROM? If you're going to flash a custom ROM to get to Jelly Bean, you're going to lose everything. It's a clean install of the OS, and custom ROMs are pre-rooted.
Temp unrooting and then wiping the OS to install a new one makes no difference

I am stock rom.

I won't loose what is on my SD card right?

I just flashed stock jellybean ota update using cwm an was on ICS with root an still didn't lose anything, you don't have to unroot to update, I just reinstalled super su after ota update an my root came back an I didn't even need voodoo, you will only lose all your apps when you flash the full jellybean image, ota updates are fine an you keep everything from before.

susieq29 said:
I won't loose what is on my SD card right?
Click to expand...
Click to collapse
If you've already unlocked the bootloader to root, then no you won't lose your SDcard. Custom recoveries used to flash ROMs don't wipe the /sdcard/ path.
---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------
slayr76 said:
I just flashed stock jellybean ota update using cwm an was on ICS with root an still didn't lose anything, you don't have to unroot to update, I just reinstalled super su after ota update an my root came back an I didn't even need voodoo.
Click to expand...
Click to collapse
Well his situation will be different with a CDMA model because he has to flash a custom ROM to do it, meaning he's wiping the entire OS.

[Solved] official JB 4.3 for Maguro ?

Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35

niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.

lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...

First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.

lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.

Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?

niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).

cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all

I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.

Updating(OTA) to 4.3 with root?

I have looked around and can't seem to get a straight answer about this. I have a stock rooted gn2, if i update over the air will it brick it? At the moment i have the att updater frozen with titanium backup. Any insight would be greatly appreciated, happy holiday!

where have you been searching? This has been covered dozens of times...

sorry
could you possibly provide a link sir?

generally speaking you can NOT take/install any OTA update when you are rooted...most OTA updates wont install if a custom recovery is detected.
99% of the time it wont work, .09% of the time it might install but you will have all sorts of issues, and .01% of the time it will work..
I think that pretty much covers it; you should probably just be patient and wait until the dev's incorporate it into a custom rom, and then you wont have to unroot to "enjoy" what ever the wonderful features are that ATT was so kind to include in their update..

And the install checks for stock system

You can install if you have stock rom. Root doesn't matter. My phone was rooted with stock room and twrp recovery. I just flashed stock recovery back. I had my superuser integrated in system partition. After Ota, i upgraded superuser apk. It then disabled Knox and download latest su binary.
So successful update with root preserved. Pm me of you need help
Sent from my SAMSUNG-SGH-I317 using Tapatalk

WARNING :
If you take the official OTA to 4.3 while root is present...you WILL trip the KNOX counter in your boot loader.
And if you root after an official 4.3 update you WILL trip KNOX anyway..
My .02....DO NOT UPDATE....
Stay rooted on the old bootloader and flash a custom 4.3 rom.....g

Wife is getting a new AT&T note 2 on the 24th (it already shipped). I would assume it doesn't have the OTA on it yet. Can you just reject the OTA when it arrives? Or will it try to install automatically on the new phone. Any way to prevent that until I can get my hands on it (have time tio mess with it).

Anyone try flashing a rom After ota update?
Did you thank your Developer today?

Same boat
I too have a stock rooted 4.1.2. OTA fails as root present, got that. All I need is a stock 4.3 root. I have read several posts and still unclear as to what to do. I have either missed it or just not found the answer.
Do I need to unroot via SuperSU? then OTA? Odin flash a stock ROM?
Please don't bash as I am only seeking an answer. And any help is greatly appreciated!

cordless89 said:
I too have a stock rooted 4.1.2. OTA fails as root present, got that. All I need is a stock 4.3 root. I have read several posts and still unclear as to what to do. I have either missed it or just not found the answer.
Do I need to unroot via SuperSU? then OTA? Odin flash a stock ROM?
Please don't bash as I am only seeking an answer. And any help is greatly appreciated!
Click to expand...
Click to collapse
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: http://d-h.st/OYC (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.

flymacs said:
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: link removed (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.
Click to expand...
Click to collapse
I noticed the OTA did not work on my nine as I got the "unable to update" after the OTA downloaded. I initially rooted via the CF-Auto flash.
Just curious as to next step.

flymacs said:
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: http://d-h.st/OYC (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.
Click to expand...
Click to collapse
So you had no trouble flashing TWRP? I went back to 4.1.1 from Skynote, OTA'd 4.1.2 and was going to flash another ROM but my wife got my phone the next morning to play slots and she accepted the 4.3 official update before I woke up. I did root with CF Auto and disabled Knox, but was wondering if Goomanager would work.
The next question is can we flash some ROMS with the rooted OTA 4.3?
Geeve

Is there a pre-rooted stock 4.3 for the i317 AT&T available?

geeve420 said:
So you had no trouble flashing TWRP? I went back to 4.1.1 from Skynote, OTA'd 4.1.2 and was going to flash another ROM but my wife got my phone the next morning to play slots and she accepted the 4.3 official update before I woke up. I did root with CF Auto and disabled Knox, but was wondering if Goomanager would work.
The next question is can we flash some ROMS with the rooted OTA 4.3?
Geeve
Click to expand...
Click to collapse
Goomanager worked fine. No problems with twrp either.
As far as flashing on from ota 4.3, I'm not brave enough yet.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
cordless89 said:
I noticed the OTA did not work on my nine as I got the "unable to update" after the OTA downloaded. I initially rooted via the CF-Auto flash.
Just curious as to next step.
Click to expand...
Click to collapse
Did you debloat or remove any apps from the stock 4.1.2?

flymacs said:
Goomanager worked fine. No problems with twrp either.
As far as flashing on from ota 4.3, I'm not brave enough yet.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
Did you debloat or remove any apps from the stock 4.1.2?
Click to expand...
Click to collapse
Nope, pretty much as stock as you can get plus root. OTA failed but I assume reason being the root... but I'm a newbie on this stuff.

cordless89 said:
Nope, pretty much as stock as you can get plus root. OTA failed but I assume reason being the root... but I'm a newbie on this stuff.
Click to expand...
Click to collapse
Then the next question I have is if you are using the stock recovery? I was using cwm on stock rooted 4.1.2. When I did the ota, the phone rebooted into cwm. Cwm asked if I wanted to do the update. I selected yes. When it completed, the Samsung installer gave a failed to install message, but cwm showed that it completed and wanted to fix root. It couldn't fix since I was unrooted at this point. I rebooted into 4.3 non-rooted. Re-rooted...etc.
I want to say again that I don't recommend anyone follow this procedure. I'm just trying to describe how I solved my own mess and hopefully answer any questions.