Develop Bugs

[Q] Stock kernel for ATT i927

Hello...anyone have stock kernel for ATT i927? Thanks.

2.3.6 upgrage is only on AT&T i believe..
and only available through OTA...
So if you are an AT & T Customer swtich back to AT&T Stock kernel and ROM and do an upgrade..

I just installed this kernel http://forum.xda-developers.com/attachment.php?attachmentid=806478&d=1323125030 and tried the update and it still didn't work. Is this the stock ATT kernel?

I think the problem lies in the recovery image. The update may be relying on the original recovery being intact (not ClockworkMod or any other). Thus, it may not be possible to update without having the original recovery in place. I have CWM recovery and the rooted kernel installed and cannot install the over-the-air updates. When I restart the phone after it's downloaded, my phone reboots into CWM and that's it. Rebooting into the OS afterwards gives me the message that the update failed.
While in recovery, I delved a bit into the filesystem using ADB and saw that the update files are there (this thread has a bit of what I'm talking about), but I don't think CWM knows what to do with them, therefore the update fails.
Are people without CWM having this problem? Furthermore, is there any way to return to the stock recovery if this is, in case, the problem?

Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?

dudejb said:
Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?
Click to expand...
Click to collapse
I never installed or used CWM. Is CWM something that gets installed with the rooted ROM? The only app I noticed installed with the rooted ROM was superuser and I deleted it. When I run AVG I still get the warning that my device is rooted, but when I type "su" in the emulator it says denied...is there something else I'm missing? Thanks.

CWM Recovery is what's installed if you have ever followed this guide. It's separate from the kernel and the ROM. On most phones, it's installed from ClockworkMod's ROM Manager, but we have to flash it via Odin. It replaces the stock recovery, but offers more features (such as the ability to flash ROMs from the phone itself, instead of having to use Odin on a PC, as well as allowing for full, or nandroid, backups of the phone).

I am ATT and I updated after I rooted with no problems. Some people reported that the update will fail if you're battery isn't mostly charged.
CWM won't be there unless you specifically installed it.

I would be interested in this too. I have been unable to get the update to go through after having flashed another ROM.

Help, went from AOSP to Stock rooted

Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.

hunter99507 said:
Can someone help, i just used odin to flash the rooted g1 image. Now i am stuck at the "samsung" screen. I just came from other custom roms such as cyanogenmod, aokp, and other touchwiz roms. I am assuming i have a diffrent kernal or diffrent bootloader and thats why I am stuck? How can i fix this?
My process:
I went from cyanogenmod to a touchwiz rom. Decided to go back to stock. Flash using TWRP Bootloader and kernal from the first post (http://forum.xda-developers.com/showthread.php?p=31802808). Then used odin to flash root injected g1 image. Now it hangs at the samsung logo, i cant get into recovery (pretty sure i flash over that), but i can get into download mode.
Click to expand...
Click to collapse
You might want to try flashing the "UCALH9 Kernel, Modem and TWRP Recovery Tar" from here with Odin. Make sure the "Auto Reboot" switch is not checked in Odin. When the flash is done, disconnect from the computer, pull the battery, then boot into recovery by holding Home and Vol Up and then pressing Power. Hold Home and Vol Up until you see the Samsung logo and some little blue text, then release. If you can get there, do a factory reset, then you should be able to flash the rooted LG1 image with Odin. Or, you can flash LH9 from the same thread or from here by flashing the Bootloader, ROM and Kernel files from the PIECES section (in that order) before rebooting.

Wipe cache and devlik and it will fix your issue. I had the same problem before.

I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion

chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
I had the same issue a few days ago and ultimately fixed it by doing factory reset, wipe cache, dalvik, etc.. I had forgotten to do it after flashing back to stock. You were probably smarter than me and did those things BUT if you didn't it's usually something simple like I did to fix the problem.

\Hey hunter you prolly figured it out already but I was in the same situation today going from AOKP to stock rooted.. what fixed it for me was after flashing, booting into the stock recovery (HOME + VOL UP + POWER) and doing a wipe data and wipe cache. Then going back to download mode and reflashing the stock rooted tar. not sure if reflashing was necessary but it worked like a charm after that.

well as i wasnt in clockwork i was pushing a stock rom through odin i don't beleive i iclearly the cache that could of helped but nonetheless im stuck and i can't get into cwm or regular recovery etc

chemisch said:
I have an extremely similar problem flashed from cm10 jellybean to stock rom + root and experiencing same issues at the moment i have flashed the stock rom and tried your suggestion "drothenberger" i got an error when flashing your suggestion
Click to expand...
Click to collapse
My suggestions including flashing a bunch of stuff. Which one caused the error? The flash of the modem/kernel/recovery tar file in Odin or the subsequent flashing of the zips in recovery? What was the exact error you received?
It's pretty hard to help you if you don't provide all the details.

I can't seem to root

I went back to odin to get a fresh of my gs3. I did the 4.1.1 update and now i have an issue.
I can't seem to install any recovery on my samsung galaxy s3 in order to root it.
I have tried just about all the downloadable clockworks out there and even tried twrp...its no go. I do not know why this is happening because I never had this problem before when rerooting my gs3.
Any one faced this before? suggestion?

You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.

Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).

bikrame said:
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Click to expand...
Click to collapse
I do, personally I only flash via odin....root66...is that a rom? how do I flash that without rooting?
Aerowinder said:
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
Click to expand...
Click to collapse
I am not quite sure what you are saying here about needing to access recovery mode after I flash...I flash the clockwork recovery mode and when i go to access it, i only see the stock.

I i reflashed odin again and decided to root using 4.0.4 ics...now it worked..I guess we can't flash over 4.1.1 anymore?
anyway, thank you both ^.^

The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?

Aerowinder said:
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Click to expand...
Click to collapse
Oh now that make a lot of sense. So I was not suppose to reboot before going into recovery with 4.1.1...will keep that in mind next time!

Even though you're rooted, flash the 4.1 root66 in Odin. You don't want to go from ICS to JB via recovery, it doesn't flash all partitions. After you flash root66 in Odin, you will already be rooted. Then you can just flash a custom recovery.
Sent from my SGH-T999 using Tapatalk 2

If I remember correctly you can still root normally on the later builds, you just have to pop out you battery after you flash, don't let it auto-reboot, then you can put the battery back in and get to clockwork recovery.

[Q] already installed stock firmware, can't install stock kernels or recovery

I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?

lasabrjotur said:
I tried to unroot my phone after getting stuck in a cyanogen bootloop a while back. I managed to get into recovery and install stock firmware via Odin. I did not however install the stock kernel or stock recovery. I am now in a stock t-mobile bootloop. I'm not sure what to do, I have been unable to get into recovery thus far, but I can keep trying. What can I do?
Click to expand...
Click to collapse
Can you get in Download mode? To work with Odin you must be in Download mode, not recovery.
If you can get in Download mode, then start Odin and flash a TWRP Odin flashable recovery:
http://teamw.in/project/twrp2/101
Then at least you should have a functional recovery. From there you could either try to flash your stock ROM again, or any another ROM.
Are you 100% sure what you flashed was a good stock ROM for the T989 ?
Dont you have a nandroid you could restore?

[Q] Completely lost. trying to update from 4.2.2 to 4.4

im sorry if this has been asked before. i was very hesitant to post but ive been trying to resolve this issue for 2 days and browsing and reading as much as i can with minimal results. i am trying to update to 4.4 from 4.2.2. i initially had a hard brick but was able to restore life with the img file but am stuck there. it boots into paranoidkangdroid sometimes (which is the rom i used before it hard bricked but not the one on the img file i created...weird i think). i think the more reading i do the more confused i get. im not sure if i have to flash to stock to get the ota, or whether i can just flash a 4.4 rom. im not sure what other information i should provide. thanks for any help and again, sorry if this is inappropriate.

Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.

audit13 said:
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
Click to expand...
Click to collapse
i am able to boot into twrp no problem

audit13 said:
Does your phone boot into download mode? If it does, flash a custom recovery and custom ROM to at least get your phone into a working state.
Click to expand...
Click to collapse
i was finally able to get some where!
i used this method to restore my phone to 4.3
http://forum.xda-developers.com/showthread.php?t=2658486
what steps do i have to take now to update to 4.4 and flash a custom rom?
do i first need to flash a 4.4 bootloader?

Personally, I prefer cwm over twrp.
Just copy a custom ROM to your external SD card, boot into recovery, wipe cache, dalvik, data, system, install ROM, reboot.
Depending on the ROM you install, you may have to update your bootloader and modem.