So for the first time ever, I successfully rooted my Nexus, and flashed the latest build of the AOKP ROM (40) to my phone using the GNexus toolkit.
Now with Android 4.1 coming to us very soon, I went to the button just to make sure it would still work even after flashing (I tried to search the forums for this q but to no avail.), but sadly the button is gone.
I'm assuming I have to make a Nandroid (right?) and flash back to stock to update and then reflash back to AOKP? Please enlighten me. Thanks for reading this, and thanks to any helpful comments.
itsjaylin said:
So for the first time ever, I successfully rooted my Nexus, and flashed the latest build of the AOKP ROM (40) to my phone using the GNexus toolkit.
Now with Android 4.1 coming to us very soon, I went to the button just to make sure it would still work even after flashing (I tried to search the forums for this q but to no avail.), but sadly the button is gone.
I'm assuming I have to make a Nandroid (right?) and flash back to stock to update and then reflash back to AOKP? Please enlighten me. Thanks for reading this, and thanks to any helpful comments.
Click to expand...
Click to collapse
Woah, you are mixing up a lot of things.
1) You CANNOT update a non-stock ROM unless the dev puts out an update for it.
2) If you are talking about the "System update" "Check now" button, it is still there (at least on stock ROMs -- it won't work anyway on non-stock ROMs).
3) Flashing a stock build, updating it, and then flashing AOKP does absolutely nothing. Why would you update a stock build, just to overwrite it with AOKP?
efrant said:
Woah, you are mixing up a lot of things.
1) You CANNOT update a non-stock ROM unless the dev puts out an update for it.
2) If you are talking about the "System update" "Check now" button, it is still there (at least on stock ROMs -- it won't work anyway on non-stock ROMs).
3) Flashing a stock build, updating it, and then flashing AOKP does absolutely nothing. Why would you update a stock build, just to overwrite it with AOKP?
Click to expand...
Click to collapse
Ok thanks for clearing this up. I'm still thinking that a ROM is somewhat of an overlay over what you already had. But I understand now. If I flash back to stock, I'll have the button back and be able to update.
And I shouldn't update back to AOKP until THEY release another build with 4.1?
itsjaylin said:
If I flash back to stock, I'll have the button back and be able to update.
And I shouldn't update back to AOKP until THEY release another build with 4.1?
Click to expand...
Click to collapse
1) yes, you'll have the button back. I've also gone back to IMM76I, waiting for the OTA to drop. Been meaning to try one.
2) you should go back to aokp? No, you can go back to aokp or any other rom whenever you feel like it.
Just remember that to successfully update a stock rom OTA style, you cannot be using a custom recovery (like cwm), which you need to flash a custom rom.
edit: actually, i've gone back to cm9 hahaha
sent from my i9250
itsjaylin said:
So for the first time ever, I successfully rooted my Nexus, and flashed the latest build of the AOKP ROM (40) to my phone using the GNexus toolkit.
Now with Android 4.1 coming to us very soon, I went to the button just to make sure it would still work even after flashing (I tried to search the forums for this q but to no avail.), but sadly the button is gone.
I'm assuming I have to make a Nandroid (right?) and flash back to stock to update and then reflash back to AOKP? Please enlighten me. Thanks for reading this, and thanks to any helpful comments.
Click to expand...
Click to collapse
Well, seeming as you're not running a stock ROM, there are no OTA updates, for your device, anymore. But as soon as the devs get their hands on the source, they'll get it to you, trust me
itsjaylin said:
Ok thanks for clearing this up. I'm still thinking that a ROM is somewhat of an overlay over what you already had. But I understand now. If I flash back to stock, I'll have the button back and be able to update.
And I shouldn't update back to AOKP until THEY release another build with 4.1?
Click to expand...
Click to collapse
A ROM is not an overlay. When you flash a ROM you are basically replacing the firmware.
It's easy enough to flash the update the OTA gives you, so you're better off using whatever Android version and ROM you really like right now and then updating manually once the OTA comes out
Related
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.
so i rooted my Sprint galaxy s3, Currently i have clockworkmod with a phantom "blazer". My question is why cant i update my phone? i have baseband version ending in lg2, when the update came out already which ends in lg4? my phone tried giving me the update but when i started the update it wouldnt go through? am i suppose to change the recovery back to stock? I just dont want to miss out on the jellybean update. Will i have to go back to factory?
ps. the "blazer" rom is super fast!!!!
mandosgs3 said:
so i rooted my Sprint galaxy s3, Currently i have clockworkmod with a phantom "blazer". My question is why cant i update my phone? i have baseband version ending in lg2, when the update came out already which ends in lg4? my phone tried giving me the update but when i started the update it wouldnt go through? am i suppose to change the recovery back to stock? I just dont want to miss out on the jellybean update. Will i have to go back to factory?
ps. the "blazer" rom is super fast!!!!
Click to expand...
Click to collapse
Baseband only refers to the modem. If you search the development threads, you will find zips to update the modem in clockwork.
As for stock updates, they require the stock recovery to work so if you have clockwork or twrp recovery installed, you will have to go back to stock to receive the ota updates.
Finally on the Jellybean update, you won't miss it. When released, I'm sure the awesome Devs here will pick it up and it would only be a matter of time before a custom rom is released. The benefits of running 'custom' far outweigh anything that releases 'stock'.
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
*Note* If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone. The Stock ROM contains the Bootloader which should never be downgraded. Fyi: the Bootloader is not the Baseband, the Baseband is just what Modem you're using.
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
bullet2binary said:
Are you basically saying to revert back to stock settings and redo the entire root process again?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
spongdangly said:
Yeah, from what I had read that seemed to be necessary since I had used Odin to update the bootloader (MF1 since my phone is the M variant) by itself when the newest Stock ROM had come out a while ago. I still flashed the newest Stock ROM (same MF1 bootloader for the M variant) but the first time I did it I forgot to enter the Stock Recovery to do a Factory Reset and Clear the Cache and ended up stuck on the splash screen of a 4.3 ROM after flashing a custom recovery. So I needed to reflash back to stock and start over.
Going into the Stock Recovery and doing a Factory Reset and Clearing Cache is necessary and doesn't take much time at all so you may as well do it just to be sure. I also recommend backing up your IMEI if you haven't done it yet.
Click to expand...
Click to collapse
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
bullet2binary said:
This seems to have done the job. Running PAC 4.3 right now. I've rebooted successfully once so far.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
exodus454 said:
Exactly what I ended up doing after nothing else was working. After getting it hanging the first time, even flashing 4.2 roms was giving me boot issues. After reverting back to stock and reflashing I'm now running the 9/1 Pac nightly and the 8/31 kt747 kernel.
I'm probably 10+ reboots in without issue and I flashed the kernel separately!
Click to expand...
Click to collapse
I'm glad to hear that this seems to be the proper fix. That's odd that you were having trouble with 4.2 ROMs, but then again I'd been running 4.2 ROMs on my phone since they first started rolling out. It's kind of annoying that everyone's S3 seems to be slightly different then the next.
Yeah this was a weird one all right. Just glad this post had a solution
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
glad i found this otherwise my first noob post would have truly been a noob move. Thanks wouldn't have guessed that fix for a few days at least.
verified it works. but it did require some weird time dealing with a bootloop issue on stock recoveries. had to find a .tar version of CWM to flash via odin for the final result.
Still Stuck at Splash Screen after trying to upgrade to 4.3
Background:
I had been running task's rom since 4.1.x. Upgraded to 4.2 with not problems and I kept the rom current. Tried to upgrade to 4.3 and that is where the problems started. It appeared to work, saw that Google was updating a number of apps but then then I kept getting error messages regarding various about various processes stopping unexpectedly. Rebooted the phone and it came up with Task's kernel splash screen where it remains frozen.
I can get into TWRP (v2.3.3.1) recovery and into Download mode.
I have tried wiping Cache and Dalvik Cache
I have wiped System
I have done a Factory Reset
I have Formatted Data
I have used Odin twice to get back to stock (I747UCDLK3) and both times it says "passed."
When I try to reboot it, however, it comes back to Task's Kernel splash screen (I do not see the Samsung screen)
Any help or suggestions would be great.
UPDATED: Found an older update from April and was able to restore it. Still wondering why 4.3 wouldn't take.
This Works
I was skeptical, but this actually works! Now running Task's 4.3 on my bell i747m without any problems!
Thanks for the tip OP :good:
spongdangly said:
For those of you who keep getting stuck on the splash screen after trying to restart your phone after installing a 4.3 ROM.
My steps were (and I take no credit for this, I can't remember who had said to do this and I wasn't logged in so I couldn't click the thank you button):
1. Use Odin to flash the latest stock ROM
2. Enter the stock recovery and do a factory reset and clear the cache (I did both twice just to make sure)
3. Use Odin to flash the stock rooted ROM.
4. Enter the stock recovery and do a factory reset and clear the cache. (This might not be necessary but I did anyways just to make sure)
5. Use Odin to flash a custom recovery (TWRP 2.6.0.0 was the newest recovery when I did this last week)
6. Enter the custom recovery and wipe everything, then flash whatever 4.3 based ROM and then flash GApps if you want.
*Note* It seemed like the phone was hanging on the splash screen after either the initial boot or the first restart (I can't remember which, it's been a week) but it did boot and reboot fine.
I hope this helps out some people since I found it to be quite irritating that I could install a 4.3 ROM and set everything up but when I went to restart it would hang at the splash screen (going into the recovery and clearing the cache/dalvik cache wasn't helping).
I hope I posted this in the right section but apologies if it's not.
Click to expand...
Click to collapse
If this works you're a life saver! I've been posting around 4.3 threads about this for weeks and no one came up with a decent answer....
Tried reflashing stock with root but didn't work... i'll try your way, see if that works
Gonna try this tonight!!!
Thanks!
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Solved
Thanks, also works for i727 skyrocket
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Kastro1784 said:
wont this brick people phones flashing back 4.1.1 stock ? im on stock 4.3 stuck on samsung galaxy s3 logo meaning flashing back to latest stock rom using odin 4.1.2? 4.3 stock rom or 4.3 custom roms?
Click to expand...
Click to collapse
spongdangly said:
1. Use Odin to flash the latest stock ROM
Click to expand...
Click to collapse
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
spongdangly said:
If you were already on the Stock 4.3 ROM you do not want to flash the 4.0.4, 4.1.1 or 4.1.2 Stock ROM since you will brick your phone.
I'll add a note to the OP about not attempting to downgrade to an older Stock ROM though.
Click to expand...
Click to collapse
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Kastro1784 said:
what framware did you flash to get 4.3 back working ? a leaked 4.3 Rom with no root ? thien reflash the stock 4.3 ?
Click to expand...
Click to collapse
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
spongdangly said:
When I had done this back in August, I flashed the Rogers 4.1.2 Stock ROM since that was the latest stock firmware at the time and I have a Canadian S3.
If you had already flashed or been on the Stock AT&T 4.3 ROM, I'd recommend reflashing the latest Stock AT&T 4.3 ROM and following the instructions in the OP. Just make sure that you don't attempt to flash an older version of the Stock ROM that you were already on since you will brick your phone. The Stock ROM contains the bootloader and that cannot be downgraded. I don't have an American S3 since I'm Canadian so I don't know which 4.3 bootloader is the newest although I'm sure a quick search would answer that for you.
Click to expand...
Click to collapse
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
shortydoggg said:
There is no latest Stock AT&T 4.3 ROM right now to reflash if you're already on the Stock AT&T 4.3 ROM. We cannot keep telling people this. If so, tell us how, because no one has, as of yet.
I've seen entirely too many posts telling people who are having trouble or phone is soft bricked on the Stock AT&T 4.3 ROM to flash or Odin back to stock. Then when asked how, the discussion ends.
That's also one of the reasons why I refuse to upgrade to 4.3 right now. At least I can still Odin back to stock as an option if something does goes wrong, but who am I to tell anyone to stay away from the latest toy, I mean update?
Click to expand...
Click to collapse
I'm sorry that I'm unable to help. As I had mentioned I have a Canadian Rogers phone (since I'm in Canada) so I don't know what's going on with the AT&T Stock 4.3 ROMs other then the fact that lots of people are having problems.
If you never flashed or did an OTA update to 4.3 then I'd suggest flashing the Stock 4.1.2 ROM. That or try what Ozark_8125 did since it saves you a couple steps (just make sure that LK3 isn't an older ROM than the one you were on).
If you're unsure what bootloader is currently on your phone and your phone is rooted I'd highly recommend downloading one of the many Root Check apps from the Play Store to verify which bootloader you're currently on.
*Note* I don't know which bootloader is for the 4.1.2 AT&T ROM nor do I know which bootloader came with the 4.3 ROMs. I'm sure a simple search would answer that for you.
Ozark_8125 said:
I posted in the CM thread about this, but thought I would pass it along.. I didn't have to go back to stock non-rooted. What I did:
I odin'd Mr. Robinson's LK3 rooted
Factory reset from the 3e recovery
Rebooted
Odin'd twrp
Restored nandroid of CM
Good to go.
Click to expand...
Click to collapse
Samsung fixed my phone free thanks for the help
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Alright guys I think I may be screwed here but I'm hoping someone can help me.
A couple of days ago I flashed a 4.3 stock rom from Samsung for my SGH-i747 and decided I wanted to go back to CyanogenMod for a bit. Today things happened with the rom that have caused me to want to revert back to the stock ODIN tar that I downloaded from XDA. It's a pre-rooted stock ROM on 4.1.1
I've made two nandroid backups (1 for CM and 1 for 4.1.1) both of which were before I attempted to flash the 4.3 rom.
I wanted a fresh start and restored back to the 4.1.1 and noticed I had accidentally uninstalled some important components via TiBu. So, as usual, I went to revert back to stock using Odin and the pre-rooted 4.1.1 build I downloaded. Only this time when I went into download mode I noticed a few new things I hadn't seen before.
In red was "Warranty Bit: 1" and something about the bootloader. I researched a little and I know it has something to do with Samsung's implementation of KNOX in 4.3.
My question now is what can I do about reverting back to stock 4.1.1 using Odin? Every time I've tried flashing it since seeing those new things, Odin fails.
Am I royally screwed or is there someone who can help?
n_alvarez2007 said:
Alright guys I think I may be screwed here but I'm hoping someone can help me.
A couple of days ago I flashed a 4.3 stock rom from Samsung for my SGH-i747 and decided I wanted to go back to CyanogenMod for a bit. Today things happened with the rom that have caused me to want to revert back to the stock ODIN tar that I downloaded from XDA. It's a pre-rooted stock ROM on 4.1.1
I've made two nandroid backups (1 for CM and 1 for 4.1.1) both of which were before I attempted to flash the 4.3 rom.
I wanted a fresh start and restored back to the 4.1.1 and noticed I had accidentally uninstalled some important components via TiBu. So, as usual, I went to revert back to stock using Odin and the pre-rooted 4.1.1 build I downloaded. Only this time when I went into download mode I noticed a few new things I hadn't seen before.
In red was "Warranty Bit: 1" and something about the bootloader. I researched a little and I know it has something to do with Samsung's implementation of KNOX in 4.3.
My question now is what can I do about reverting back to stock 4.1.1 using Odin? Every time I've tried flashing it since seeing those new things, Odin fails.
Am I royally screwed or is there someone who can help?
Click to expand...
Click to collapse
Read around in the general section. you'll see that if you try to odin back to 4.1.1 bootloaders from 4.3 your phone will die. be careful. The developers here are trying to figure out solutions for this new update. I hear it's going slower than usual.
Well crap lol thank you. I'm on a pretty stable version of CM 10.2, should I just leave it until reverting to stock is fixed?
n_alvarez2007 said:
Well crap lol thank you. I'm on a pretty stable version of CM 10.2, should I just leave it until reverting to stock is fixed?
Click to expand...
Click to collapse
You installed CM10.2 after you ran the stock 4.3 update? i've heard of a few here that have done that. I'm not real big on CM builds; I actually prefer TW based ROMS so I'm gonna wait out upgrading (since I'm on a stable 4.1.2 ROM). If you've upgraded and you're running something stable right now I'd stick with it until the experts here find out more info.
jack man said:
You installed CM10.2 after you ran the stock 4.3 update? i've heard of a few here that have done that. I'm not real big on CM builds; I actually prefer TW based ROMS so I'm gonna wait out upgrading (since I'm on a stable 4.1.2 ROM). If you've upgraded and you're running something stable right now I'd stick with it until the experts here find out more info.
Click to expand...
Click to collapse
No I installed the CM 10.2 M1 Snapshot before running the stock 4.3 upgrade but before doing so I made a nandroid backup while on CM 10.2 so I just restored back to it.
I'm not a pro at these forums, so I'm not sure if I should be posting in this section. If not, could a moderator please move it to its position? thanks.
I am currently on d2att Snapshot cm11. I wanted to try KitKat, but meh. Running 4.4.2. When I rooted my phone at 4.3.3, I got too excited and forgot to make a nandroid back up (**** ME) so I don't have a back up I can return to. Anyway, I have TWRP and I really want to go back to Stock ICS. Not JB 4.3.3, but stock ICS. Is there anyway I can do this? I want to remove TWRP Recovery, CM, and go back to ICS if possible. Thanks....
More Info? (If Needed)
d2att Samsung Galaxy SIII i747
erm... rooted twice? (Rooted at ICS then updated to JB, I went down to 4.2.1?? i think and it removed root)
Battery Life of this phone is horrendous, I don't know what's wrong with it.
You should be posting questions in the questions forum, not the development forum.
Wrong forum and no you cannot downgrade because you will brick your phone since you were on 4.3.3.
aybarrap1 said:
Wrong forum and no you cannot downgrade because you will brick your phone since you were on 4.3.3.
Click to expand...
Click to collapse
ah. Sigh. Is it still possible to go back to STOCK 4.3.3? I forgot to make nandroid backup, and TWRP idk what to do with it, cm 11...
Damn... I wish i can go to ICS...
imNooby said:
ah. Sigh. Is it still possible to go back to STOCK 4.3.3? I forgot to make nandroid backup, and TWRP idk what to do with it, cm 11...
Damn... I wish i can go to ICS...
Click to expand...
Click to collapse
You CAN downgrade the os version back to a stock rooted 4.3.3. You CANNOT downgrade your bootloader or it WILL brick your phone.
You may want to check on the AT&T Galaxy S III Android Development forum here: http://forum.xda-developers.com/galaxy-s3-att/development
There are a few options for stock ROMs and a lot of options for modified touchwiz ROMs
Moved to Q&A.
I believe the only way to get back to ICS would be with a jtag service as going back to ICS from JB or KK without jtag would brick your phone.
Does no one have a stock 4.4 flash?
Sent from my SAMSUNG-SGH-I747 using XDA Free mobile app
imNooby said:
I'm not a pro at these forums, so I'm not sure if I should be posting in this section. If not, could a moderator please move it to its position? thanks.
I am currently on d2att Snapshot cm11. I wanted to try KitKat, but meh. Running 4.4.2. When I rooted my phone at 4.3.3, I got too excited and forgot to make a nandroid back up (**** ME) so I don't have a back up I can return to. Anyway, I have TWRP and I really want to go back to Stock ICS. Not JB 4.3.3, but stock ICS. Is there anyway I can do this? I want to remove TWRP Recovery, CM, and go back to ICS if possible. Thanks....
More Info? (If Needed)
d2att Samsung Galaxy SIII i747
erm... rooted twice? (Rooted at ICS then updated to JB, I went down to 4.2.1?? i think and it removed root)
Battery Life of this phone is horrendous, I don't know what's wrong with it.
Click to expand...
Click to collapse
Kinda seems to be some conflicting information, so let me give it a shot and hope I dont make any confusion worse.
First you need to verify your current base firmware/bootloader build. Install terminal emulator from the play store, open and enter this:
getprop ro.bootloader
This will tell you what build you have as your base. If it is a 4.3 or 4.4.2 build, you cannot flash any older firmware or modems. But you CAN still flash an ICS rom (or any other rom you want for that matter). (No guarantees this will run well though, since the version gap would be pretty large).
If your firmware/bootloader version is 4.1.2 or earlier, you are pretty much free to flash anything but 4.4.2 touchwiz roms.
I hope thst helps, and good luck!