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.
Related
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.
Hi! I have encountered a problem, and really hope someone can help me!
Two days ago i flashed Omnirom Nightly on my n7105 to get Android 4.4. I was running cmw recovery but couldnt get the ota updates to work, so i was trying to flash open recovery instead. I used an apk that was supposed to install a script.
When i rebootet my phone, all i could get was the Note 2 boot image. It wont boot into recovery mode, or the rom. I am however able to boot into download mode.
Custom Binary download: Yes (4 counts).
Current binary: Custom
System Status: Custom.
How should i proceed? I've already tried to reflash cwm recovery, which did work, but didnt solve the problem. I am currently downloading stock firmware, but the file is 1.2 GB so it will take i while. Figured i should ask here in the meanwhile.
I'm not an expert at Android at all, im just a guy enjoying having custom roms and playing around a little. I do know that there are a lot of very talented people in this forum, and i really hope someone can help me find a solution. I've been googling for hours, but cant find anything that seems to work for me / or i dont fully understand and wont risk try before someone approves it.
Thank you, Vetle
EDIT: Is it correct that i cant flash any custom rom trough Odin? Or could i just flash omnirom again trough Odin?
If i manage to flash the stock rom and the bootloop goes away, will everything go back to normal, so i can flash cmw again and then a custom rom again?
No custom rom can be flashed through odin, as most of them are zip cwm/twrp base.
When u can only go to download mode, an official firmware only can help u through odin.
Sent from SM-N9005 with xda-app
Thanks for the answer!
Yup, i have flashed a stock rom now and i got the stock recovery. Everything was working fine.
Then i proceeded to do a factory reset in the stock recovery and flashed cwm trough Odin. When it was done, it wouldnt let me into recovery again! I can still boot up the phone tough.
I've also tried Open recovery. CWM via Rom manager. Open Recovery trough Goo Manager... Still cant get recovery to work, the stock rom works tough.
Any ideas?
Okay, i tried to flash the stock rom again and installed Rom Manger.
It still showes TWRP and CWM under installed recovery and i guess these its these two who makes the problem.
My plan now is to figure out how to completely remove them. I've never done anything related to adb before, so i hope it possible to remove them in another way?
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
vetle666 said:
This is so weird. Somehow i managed to install CWM Touch via Rom Manager and it booted. When i choose reboot /pull battery it will only boot straight into CWM again. I tried to flash TWRP via Odin, wich sucseeds, but then it reboots into CWM again!
I am soo lost its almost funny!
EDIT: Since i could get into cwm now, i tried to flash omnirom, but it aborts and all i get is status 7...?
EDIT2: Latest now is that i suddenly managed to install TWRP via Odin, but i still cant install the latest omnirom, all it says is "updating partition details".
Click to expand...
Click to collapse
I had recovery problems in the last few days also.
Installed DN3 rom using philz recovery, because its capable of prepare the phone to a new rom in a easy way.
It all went fine until first reboot.
I had a recovery boot loop. All I could see were some buttons and then reboot again.
Like you I had download access and flashed philz with Odin, but no luck.
Installed twrp via Odin and all was fine, and flashed philz new version.
Then I had to flash a new kernel (to be able to access wifi) and it all started again. Now I'm back on twrp.
Let's see what happens on my next flash.
My suggestion is to flash the recovery, and if that's OK flash the rom and use it
Next time you need recovery get Odin to help, but not all the way from an original rom. Just the custom recovery.
But if you want to get rid of your strange recovery configuration, and you are not already on new 4.3 recovery(which in your case could explain some of the problems you had) , with knox, install an older original rom, 4.1, and make all the steps, root it, install a custom recovery, and from there the room you want.
Reading your path sorting this problem, that was what would do next
Best regards
When I try to install a rom it wont install system files it skips over them only to extract some apps which means no bootup.
Any suggestions?
I've tried to install stock and then wipe and then install a rom and i still get same result however sometimes when i flash stock with odin i get fail at the very end whether it be for HLOS file or modem...
I think i can fix this if i wipe my partitions and get them partitioned again.. or maybe one of Odin's tick marks could help??
:crying:
please help
I'll probably sell this phone
More information is needed. What version of stock are you running? Are you rooting your phone? Are you installing a custom recovery? Which custom recovery are you using? Name at least one rom other then stock you've tried to install and how you tried to install it. I would guess no one has responded because they don't have the information needed to give you the help you are asking for.
Corwinder said:
More information is needed. What version of stock are you running? Are you rooting your phone? Are you installing a custom recovery? Which custom recovery are you using? Name at least one rom other then stock you've tried to install and how you tried to install it. I would guess no one has responded because they don't have the information needed to give you the help you are asking for.
Click to expand...
Click to collapse
Im having the same problem too I cant seem to install no rom other then the backup of my Stouck MDL...I tired installing wicked rom and of course it got stuck at the Samsung screen and i did everything when it came to wiping it ....sooo the i tried insane KItKat and that to as well got stuck on boot and im on the latest TWRP 2.7.0.1 recovery running MDL stock
I've tried to install with CWM Recovery by OUDSH and TWRP and no luck I've tried installing WickedRom Hyperdrive and GE by Kot49H I can only install stock with Odin and the reason its not installing is because its avoiding the extraction of system files to the phone.
I was able to root my device using these instructions
http://forum.xda-developers.com/showthread.php?t=2401901
I can confirm that it is rooted, TWR is loaded as the recovery and superSU is running as well as some root-only apps.
The problem is that no matter what or how I try, I cannot get a new kernel to install nor can I flash a ROM.
If I try to do either via Odin it completes without errors (either on the computer or tablet) but when the tablet is rebooted, no changes.
If I try to flash a rom from the recovery it just errors out and fails
I even tried using Odin to unroot and reset back to stock and that worked but when I re-rooted it again I was back to where I'm stuck!
Has anyone ever seen this before?
rek410 said:
I was able to root my device using these instructions
http://forum.xda-developers.com/showthread.php?t=2401901
I can confirm that it is rooted, TWR is loaded as the recovery and superSU is running as well as some root-only apps.
The problem is that no matter what or how I try, I cannot get a new kernel to install nor can I flash a ROM.
If I try to do either via Odin it completes without errors (either on the computer or tablet) but when the tablet is rebooted, no changes.
If I try to flash a rom from the recovery it just errors out and fails
I even tried using Odin to unroot and reset back to stock and that worked but when I re-rooted it again I was back to where I'm stuck!
Has anyone ever seen this before?
Click to expand...
Click to collapse
1), If you used the TWRP from that post, then you need to update to a newer recovery. TWRP for KK
2). Telling us that "it errors out" is pointless. You need to tell us exactly what error you are getting.
3). Attach the recovery.log from the failed attempt to flash a rom. Google can tell you how to get the log.
welp, I feel dumb - it was the wrong version of TWRP that was causing the problem all along
I recently rooted my phone, and without much research I attempted to install a custom rom.
Currently, my phone has a unfixable, broken charging port so I have no option of connecting it to a computer.
I was running 4.4.2 Kit Kat stock rom and attempted to install the latest twrp, but instead installed twrp 2.2. Is there any way to update through a sdcard?
I don't have any back up and my phone currently has no rom to go on.
So I'm completely lost as to what to do at this point.. If anybody could help get a stock rom or even a custom; I'll be very grateful!
Download the twrp app from the play Store to update twrp
Sent from my ASUS_Z00AD using Tapatalk
xMozaik said:
I recently rooted my phone, and without much research I attempted to install a custom rom.
Currently, my phone has a unfixable, broken charging port so I have no option of connecting it to a computer.
I was running 4.4.2 Kit Kat stock rom and attempted to install the latest twrp, but instead installed twrp 2.2. Is there any way to update through a sdcard?
I don't have any back up and my phone currently has no rom to go on.
So I'm completely lost as to what to do at this point.. If anybody could help get a stock rom or even a custom; I'll be very grateful!
Click to expand...
Click to collapse
I haven't used TWRP 2.2, I started using it at 2.5 or there abouts. I gather than you did successfully flash TWRP 2.2 and can boot into your custom recovery. If so you should be able to flash a newer version of TWRP from the external sdcard, you can on the newer versions. At the TWRP site the downloads come as flashable zips and as image files you can install with Odin. Download the zip format, put it on the external sdcard, put it in the phone, boot into recovery, and then flash. HTH.