Develop Bugs

Kernels

I have a T-Mobile Galaxy S2. Rooted it withe hercules tar kernel on Android 2.3. When I upgraded to JB the kernel no longer worked (couldn't root). I tried flashing Cyangoen 10.0 and 9.0 but neither wokred (Waited 20 minutes and nothing). Is there a kernel I need to flash with ODIN?
Also, looking for a good place to learn abot kernels in genral.
Many thanks.
FezK

FezK said:
I have a T-Mobile Galaxy S2. Rooted it withe hercules tar kernel on Android 2.3. When I upgraded to JB the kernel no longer worked (couldn't root). I tried flashing Cyangoen 10.0 and 9.0 but neither wokred (Waited 20 minutes and nothing). Is there a kernel I need to flash with ODIN?
Also, looking for a good place to learn abot kernels in genral.
Many thanks.
FezK
Click to expand...
Click to collapse
Kernel is causing the problem. Flash only kernel which is made for specific rom/android version. follow this if you want to flash via Odin. I recommend you to install CWM because its easy,safe and time saving.

Installed CWM Recovery, tried to flash Cyanogen 9...now it keeps rebooting back into CWM...can't access the Recovery menu. I downloaded the updated kernel. How do I get it flashed?

I was able to connect via ODIN. Can't get recovery-clockwork-touch-6.0.3.1-hercules.tar to flash.

restart your computer log back in and use a different USB port and make sure you have all the DRIVERS for the phone plug it in flash the ODIN CWM file then you should flash an ICS ROM then flash JB to avoid any hiccups 2.3.4 is a big jump to JB might be giving you errors and you are rooted correct ?

Thank you. Yes I'm rooted an runnning smoothly with Juggernaut ROM for now. Want to change to Cyanogen 9.0. I'll flash the ODIN CWM file as you recommend. Where can I find a good ICS ROM and JB? Didn't know the jump from 2.3.4 to JB would be so big.
Many thanks.

what do you prefer the more stocky looking approach or you into AOKP/CM if you like stock then anything from PTMR and JAMISON904 are on point and very stable if you want some options and custom stuff look into the CM/AOKP around here in the development forums since you are rooted i would download a nice ICS you wont be on it long so doesnt matter lol and then finally jump ship to JB give it time for the battery to settle in becuase there was nothin like GB as far as the battery life goes this one guy who has amazing work and dedication http://goo.im/devs/Cl3Kener anything on there will do you justice when you get to the JB stage good luck and happy flashing!!

C13Kener DOES have some amazing stuff. Thanks. I see that he has a nice ICS stock ROM (Samsung-Stock-4.1.2-Tiberius-Kernel-1.1.zip). Can I just flash that from recovery or do I need to flash a new kernel via ODIN beforehand? Apprecaite your patience and help.

FezK said:
C13Kener DOES have some amazing stuff. Thanks. I see that he has a nice ICS stock ROM (Samsung-Stock-4.1.2-Tiberius-Kernel-1.1.zip). Can I just flash that from recovery or do I need to flash a new kernel via ODIN beforehand? Apprecaite your patience and help.
Click to expand...
Click to collapse
I think there is some confusion here. A ROM is not the same thing as a kernel.

I think thats where I'm having trouble. I have an older kernel (recovery-cwm-hercules.tar) and need to upgrade it before I can flash an ICS ROM. Don't know where to find kernels for the ROMS I want to flash. I thought some ROMs came with the kernel embedded in their zipfile, but finding thats not the case. ODIN is fairly easy to use, but I don't know where to find the right kernels for ROMs like Cyanogen.

FezK said:
I think thats where I'm having trouble. I have an older kernel (recovery-cwm-hercules.tar) and need to upgrade it before I can flash an ICS ROM. Don't know where to find kernels for the ROMS I want to flash. I thought some ROMs came with the kernel embedded in their zipfile, but finding thats not the case. ODIN is fairly easy to use, but I don't know where to find the right kernels for ROMs like Cyanogen.
Click to expand...
Click to collapse
Recovery is a tool used to flash ROMs and do backups.
TWRP and CWM are recoveries.
ROMs are the operating system of the phone. They come with a kernel. The kernel is what boots the phone into the OS. You can flash a different kernel if it matches the type of ROM you are on. I hope that clears up some of the confusion.

Help update from Darth stalker android 4.1.1 (T999)

I have not flashed in a while, I have twrp installed and have been running Darth stalker for a while. It's android 4.1.1, so I'm due for an upgrade.
All the newer roms want me to be in v4.3 first, I'm a little lost and confused. Can someone help point me in the right direction?

You only need to have full 4.3 firmware if you are planning to flash a 4.4.2 touchwiz ROM.. Aosp/cm you are good to go. To flash 4.3 firmware just download it from the sticky in development and flash it with Odin. After that, flash your custom recovery of choice (twrp works best in most cases) and flash your ROM

Thank you! I've never been a flash a holic.... didn't want to run the risk of messing something up. Trying to get some new life in my s3, my whole family upgrade on iPhone 6 and I feel a little left out

[Q] Noob needing to go back to stock, help please?

I figure instead of pulling my hair out for three days wading through various methods and likely brick, I'd swallow my pride and ask.
Here's where I'm at: I rooted and flashed Carbon rom way back when, everything was working alright, but with time, things are slowly starting to come apart. Yesterday, it's come to the point it can't be ignored. My nightly is ridiculously out of date, but I just haven't wanted to mess with it anymore. I'm about ready to get a new phone and I want everything back to fresh stock to give to a family member. I don't know where to start and what instructions are applicable or out of date. Model: I747, Android version: 4.4.2
I think I'm done experimenting with the rooting business, it's been a ride. If I could get some clear instructions on getting this phone back to stock, I'd be eternally grateful.
Help me xda community, you're my only hope.

What bootloader is on your phone? This is important to know before trying to get back to a stock ATT ROM.

audit13 said:
What bootloader is on your phone? This is important to know before trying to get back to a stock ATT ROM.
Click to expand...
Click to collapse
Hey there, thanks for replying! Bootloader says I747UCUEMJB.

Since you are on an mjb bootloader, that means you had the ATT stock 4.3 ROM on the phone.
Unfortunately, ATT never realased a stock 4.3 ROM or 4.4.2 ROM. These were only available via OTA.
There was a thread where a stock mjb ROM was compiled for flashing in Odin, but for some members, the flash resulted in a bricked phone.

I had a feeling that might be the case. What are my options here?

I would install a custom recovery and flash a custom rom. There are custom ROMs based on stock Samsung ROMs.

audit13 said:
I would install a custom recovery and flash a custom rom. There are custom ROMs based on stock Samsung ROMs.
Click to expand...
Click to collapse
This is the way to go. Since you most likely already have a custom recovery (assumed since you are running Carbon but verify first though), then it is just a matter of getting a new ROM. There are several custom TW ROMs based on 4.3 MJB. If you really want KK, you can flash the NE4 bootloader and modem along with a custom NE4 TW KK ROM. Please keep in mind that with both MJB and NE4 (KK) if you try to revert bootloaders, you will brick.
I am personally running S3RX 4.3 and have few to no issues other than what most people experience on stock anyway. Just have not had the time to move forward to KK as of yet.
Sent from my SAMSUNG-SGH-I747

Okay, so the bootloader is 4.3, but the Android version in settings says 4.4.2, how does that fit together? Just trying to understand what all this works.
Recovery is currently ClockworkMod. Since I'm planning on giving it to family, I'd like something that is as stable as possible, nothing fancy needed. What ROM would fulfill those needs?

aablee said:
Okay, so the bootloader is 4.3, but the Android version in settings says 4.4.2, how does that fit together? Just trying to understand what all this works.
Recovery is currently ClockworkMod. Since I'm planning on giving it to family, I'd like something that is as stable as possible, nothing fancy needed. What ROM would fulfill those needs?
Click to expand...
Click to collapse
Sounds like you are running a custom KK ROM in order to be using the 4.3 bootloader. A stock KK ATT ROM will not run on a 4.3 bootloader.
Before flashing to a custom KK ROM, make sure you are running the latest CWM. Carbon is a good ROM and should have reached a milestone build.

aablee said:
Okay, so the bootloader is 4.3, but the Android version in settings says 4.4.2, how does that fit together? Just trying to understand what all this works.
Recovery is currently ClockworkMod. Since I'm planning on giving it to family, I'd like something that is as stable as possible, nothing fancy needed. What ROM would fulfill those needs?
Click to expand...
Click to collapse
audit13 said:
Sounds like you are running a custom KK ROM in order to be using the 4.3 bootloader. A stock KK ATT ROM will not run on a 4.3 bootloader.
Before flashing to a custom KK ROM, make sure you are running the latest CWM. Carbon is a good ROM and should have reached a milestone build.
Click to expand...
Click to collapse
You are running the official 4.3 bootloader but an AOSP custom ROM. In the case of AOSP ROMs you can typically do this. As mention by audit13, if it was a custom ROM based off TW AT&T stock, you would only be able to run a modified TW 4.3 ROM.

[Q] Which Firmware W/ Fresh SlimKat 9 Stable Install

Background: I attempted to update from SlimKat 7.0 stable to 9.0 stable and discovered my apn's were missing and when I try to add them manually it fails to save. I have also found others with this same issue but none have an easy fix. I'm on UCDLK3 firmware, after restoring to previous state using nandroid backup apn's are present. If I try to flash any ROM (even other than Slim) my apn's are missing, even a dirty flash of 7.0 over 7.0. I know I can fix this by flashing stock UCDLK3 and root/twrp/flash slim 9 and everything will likely work fine. I plan to do just that but want to make sure I'm doing things as smart and clean as possible. There is a lot of info out there and I'm finding it hard to sift through old stuff and find the current state of things.
Question: Is there an actual advantage if I upgrade the firmware from UCDLK3 to UCUEMJB while still planning to use SlimKat 9 Stable with BMS kernel and TWRP recovery? Are there any disadvantages? Either way what is the shortest path to get back to stock (either LK3 or MJB) and flash SlimKat?
Thanks

Your APN may not be sticking because your modem and bootloader may be too outdated.
Some of the latest CM11 and AOSP ROMs require a KK bootloader and modem.

And then there are some roms that require at least a 4.3 bootloader and modem, either the MJ2 (leaked) or MJB (official) bootlaoder/modem combos. I have seen mention of these working in some OPs and in the body of other threads. In some of the later TW ROMs you may have to use a custom kernel like kt747 or iBuddler's. I don't know if any kernel other than the stock in SlimKat and AOSP ROMs would be needed with the MJ2/MJB firmware and modem.
I don't know of any advantages other than some of the ROMs require firmware newer than DLK3 to properly boot, receive data, or have a working wifi. As far as disadvantages, KNOX was introduced with the MJB firmware and stock ROMs, once going to MJB or newer firmware you can not make firmware downgrades without a very real risk of hardbricking your phone. Also you will need to insure your baseband and modem versions match. If they do not you risk hardbricking of another variety.
I had not yet realized that the newer AOSP and CM11 required you to go all of the way to NE4, thank Audit.

Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)

thanks for posting fix. am sure it will help others. audit13 and dawgdoc , thank you for continued help with the awesome Slll. :good:
"all i can really do , is stay out of my own way and let the will of heaven be done"

jeff.leonard said:
Just wanted to close the loop on this thread and say thanks for the assistance!
I now have my phone working properly on SlimKat 9; it really was just the firmware not being compatible with newer ROMs as many have suggested. Here is the sequence I followed to do it but really it probably only needed a twrp flash of the mjb firmware and the ROM install:
1. Used odin to restore to stock LK3 (only because I had messed with things so much and wanted a clean slate)
2. Used odin to install TWRP 2.7.1.0 recovery
3. Rooted with SuperSU 2.40 using TWRP
4. Flashed combined MJB modem & bootloader using TWRP
5. Flashed SlimKat 9 using TWRP
6. Flashed Slim GApps using TWRP
7. Rooted with SuperSU 2.40 using TWRP (Lost root after flashing ROM)
Click to expand...
Click to collapse
When you restored to LK3, what Firmware version were you coming from? I'm looking to go to LK3 from the NJ1. However there seems to be cautionary red flags all over the place due to bootloader changes that were made in 4.3.

The OP was already on LK3 with a custom ROM.
Since you are on NJ1, you cannot downgrade the bootloader.

[SOLVED] I think my i747M may be soft bricked?

Hey all. I am fairly inexperienced when it comes to rooting, though I have done a few succesfully in the past. I currently have the newest version of TWRP installed on my Samsung I747M. The I747M I have is not from one of the major carriers, but as far as I am aware, the phone is factory network unlocked. Carrier is GCI, in Alaska.
I currently have a 4.4.2 Touchwiz Rom installed and started having problems after I attempted to flash the ROM Dandroid, which is 4.3 (http://forum.xda-developers.com/showthread.php?t=2121506). I had created a backup using TWRP before flashing the ROM and reverted back once I noticed the problem.
The main issue I am experiencing at this time is the Baseband Version, IMEI, and other information related to the modem is showing "Unknown" and features such as wifi will not toggle on.
I had also attempted to flash the most current version of the modem that I was able to find thru Odin. Odin showed the flash as successful. The version I flashed to the phone was I747MUMUEND3: modem_CWM_I747MUMUEND3.zip - 18.80 MB - April 3rd, 2014 (http://forum.xda-developers.com/showthread.php?t=1831898)
At this point, I can still get into recovery, download modem and I am able to boot up the phone and access most all functions. The next step I was going to try was going to be to flash back to stock firmware from sammobile's website (Was using to use the Roger's version of 4.4.2), though I don't want to cause more issues than I can handle or resolve thru software.
Any advice on how to proceed would be greatly appreciated or even just how to get the modem/wifi features functional again would be helpful. I'm just as happy staying on my current ROM at this point if I can get the phone fully functional again.

It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.

audit13 said:
It's possible that the rom is not compatible with the kk modem and bootloader.
Flash cm12.1 to see if your imei comes back.
Click to expand...
Click to collapse
Forgot to mention, this is something I did try. I attempted to flash Cyanogen Mod 12.1 (Download: cm-12.1-20151017-NIGHTLY-d2att.zip (286.76 MB) ) and most recent nightly build & the most recent stable release (CM11) (Download: cm-11-20140210-SNAPSHOT-M3-d2att.zip (194.37 MB) ). When flashing these, I transferred the downloaded ZIP file to the internal storage of the phone in the root directory and attempted to run an install from TWRP. Both installs failed.

Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: http://www.sammobile.com/firmwares/database/SGH-I747M/
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: https://dl.twrp.me/d2att/twrp-2.8.7.0-d2att.img.tar
Create a nandroid backup using TWRP and then try to flash a custom ROM again.

audit13 said:
Since the phone is an i747m, I recommend flashing back to stock using Odin 3.07 and stock ROM file from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
The i747m versions are interchangeable between Rogers, Telus, and Bell.
After flashing back to stock, install TWRP using Odin 3007 from here: URL REMOVED FROM QUOTE DUE TO NEW USER LIMITATIONS
Create a nandroid backup using TWRP and then try to flash a custom ROM again.
Click to expand...
Click to collapse
I'll give that a shot when I get home. Stock firmware was one of my next thoughts. I have it downloading at the measly 15 Kbps offered for free from sammobile so hopefully should be done by the time I get home & update this thread with any progress.

Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in TMS3KK thread. The ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)

dawgdoc said:
Another possibility is a custom kernel, if you are wishing to stay with TouchWiz and not wanting to upgrade your bootloader and modem past 4.3.
Some of the 4.4.2 TW roms will run on 4.3 bootloader and modems using one of ibuddler's kernels or ktoonsez's TW kernel. This was discussed most in the "http://forum.xda-developers.com/showthread.php?t=2725192"Likewise ROM thread and links to the various versions of ibuddler's kernel may be found there. It may have also been discussed in http://forum.xda-developers.com/showthread.php?t=2725750" TMS3KK thread. The http://forum.xda-developers.com/showthread.php?t=1756776" ktoonsez kernel can be found in its own thread.
But, you may really want to consider a newer ROM in order to change to something with the stagefright fixes. I think any of these may require the latest 4.4.2 bootloader and modem. (What say you @audit13?)
Click to expand...
Click to collapse
I'm not opposed to any of this. Mostly just trying to slim down this phone to the basics as much as I can and am quite open to any recommendations. Main thing I want to maximize is battery life & simplicity since this is for my wife and those are her major wants in a phone. I figure any kind of ROM that just covers the basics should cover my bases & would prefer one with a darker/black skin to maximize battery life w/ the OLED screen. I am in the process of flashing to the Roger's stock ROM as I type this w/ my fingers crossed.
Just to add, no over clocking or anything of that nature is desired. If I remember correctly I ended up putting the ktoonsez kernel on one of my handsets, either this Galaxy S3 or my Galaxy S5, though I can't recall which since it was so long ago.

Alright! So progress! Wifi, Baseband version, IMEI and all other missing information restored & now works w/ stock rom flash. In process of reflashing TWRP now.

Let us know what happens.

Still all good with TWRP installed. Have not flashed back on a custom ROM yet. After reviewing some of the above recommendations, I am kind of liking the looks & features of TMS3KK (http://forum.xda-developers.com/showthread.php?t=2725750) and feel it would suit my needs.
I factory reset, cleared cache, and cleared Dalvik thru TWRP & then made a back up. Prior to this, I confirmed everything was still working normally w/ phone fully loaded after TWRP was installed.
One of the things mentioned on the installation instructions for that ROM is the following:
---
Do not mix and match 4.3 firmware (bootloaders/modem) with the new 4.4.2 ones. You will hard brick and I warned you. This works the same as any 4.3 or ND8port ROM with 4.3 firmware and it can use the new 4.4.2 ones also.
Link to recovery flashable i747 and i747M 4.4.2 bootloader and modem packages: http://forum.xda-developers.com/gala...hable-t2856914
---
How would I go about confirming my current bootloader/modem versions to make sure they are both 4.4.2 before flashing this ROM? At the link provided, those files/links to the files were removed because they were causing some bricked devices per a note at the top of that thread. Here's a link to the thread I am referencing since the above link looks to be broken. (http://forum.xda-developers.com/gal...mware-ne4-ne6-nf2-recovery-flashable-t2856914)

If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.

audit13 said:
If you flashed the latest stock rom, you are running the latest 4.4.2 bootoader and modem.
You can download and run the Samsung phone info app from the play store to confirm this.
You should be good to flash any d2lte or d2att rom.
I recommend not flashing any modem or bootoader from this point forward unless the bootoader and modem are newer than the currently installed botloader and modem. Also, the botloader and modem must be matched to each other.
Click to expand...
Click to collapse
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.

fodor362 said:
Thank you so much for the help and information. I guess I never realized that the bootloader & modem were installed w/ the stock rom as I always have flashed those separately through Odin when needed. Definitely good information to have and not easy information to find. I have successfully got my custom ROM on there and am now fine-tuning it for the wife.
Click to expand...
Click to collapse
Glad to hear the phone is running well.
I've heard it said "Happy wife, Happy life."