I installed this thing here http://forum.xda-developers.com/showthread.php?t=1781327&page=13, hoping that I'll get my CRT screen off animation back. Unfortunately, I didn't and I now want to go back to my stock Jelly Bean. Any way I can do that?
Here
Flashable via CWM.
Thanks a lot. I get official updates running that?
As long as you don't change the kernel, you should be good to go. Just flash the ROM and none of the other stuff.
chronophase1 said:
As long as you don't change the kernel, you should be good to go. Just flash the ROM and none of the other stuff.
Click to expand...
Click to collapse
i think its deodexed and will not receive otas ... but here you go...just made this thread . http://forum.xda-developers.com/showthread.php?t=1807861
it will return yout phone to jb factory state unrooted with stock recovery and all...you need the drivers . good luck
I did install galaxy nexus sounds and my phone is rooted, so that means i won't get any OTA's?
Root doesn't matter.
If you installed the sounds with a flashable zip then when you're actually pushed a ota it will fail to install automatically because of the custom recovery. It will install manually though as long as the ota doesn't check the stock roms sounds. Not sure if it does but you can just look in the updater script in a ota and look to see if it checks for the sounds.
Related
I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
crankerchick said:
I have a nandroid of my rooted honeycomb 3.2.1 install. If I want to flash the leaked stock ICS, is it possible to go back to the nandroid and then go back to stock recovery to install the leak?
I understand I can use the unrooting method but I'm just trying to understand this better and understand my options. I don't wish to go back to the stock images and lock the boot loader again just to flash the update and unlock and root again if I don't have to unless that is just the best way to do it.
Click to expand...
Click to collapse
I would really advise that you flash the most recent EOS wingray. Rom #36 and the GApps (Google System apps) package version 10. It seems to be more complete than the ota update, it's easier to flash and you preserve your root and recovery.
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
crankerchick said:
Thanks, nice to see someone offer a comparison of the two packages. I'm currently running EOS build 34 from the other night. I guess i was just curious about the stock update. I know there are still some things non-functional with eos and figured the stock rom would be completely functional minus whatever bugs. It does seem like a bit of work to flash it though, since the only thing i can seem to find on what to do is saying to unroot and relock using the moto stock files.
Seems like if im interested in trying a stock rom i shojld just wait for the ota and a rom made from it with root already.
I will miss the notification tray settings in eos if i go stock!
Click to expand...
Click to collapse
True, that.
EOS wingray version 36 with the version 10.1 GApps really fixed most of the remaining issues. There should be a new nightly and there is a new GApps 10.2 to flash today.
I just rooted my TF101 using ViperMod but now I'm not sure whether I should install CWM recovery or not if I want to install further OTAs. I have read some threads but couldn't come up with a clear answer. I read somewhere that only stock recovery can receive OTA updates but also read that CWM can receive them too. If I can't install CWM then what ROMs can I install with stock recovery? What's the best way to go if I want to be ready for the ICS? Thanks!!
theremix said:
I just rooted my TF101 using ViperMod but now I'm not sure whether I should install CWM recovery or not if I want to install further OTAs. I have read some threads but couldn't come up with a clear answer. I read somewhere that only stock recovery can receive OTA updates but also read that CWM can receive them too. If I can't install CWM then what ROMs can I install with stock recovery? What's the best way to go if I want to be ready for the ICS? Thanks!!
Click to expand...
Click to collapse
Technically you'll still receive the OTA update you just can't apply it if you have CWM or a custom ROM installed.
You can't install custom ROM without CWM (if you have an older SBK tablet you can use NVFlash with a compatible ROM).
So I shouldn't install cwm until the ICS drops right?
Sent from my Transformer TF101 using Tapatalk
If you want to update to ICS via OTA don't instal CWM.
As you have been told, you will get the OTA message but the update will fail.
So you have two choices (or three):
* Keep stock recovery and update to ICS when the OTA update is available
* Install CWM and update to ICS as soon as a DEV publishes an ICS ROM
* Install CWM and remove it as soon as you know the OTA is due (pretty lame, but you could do it).
Regards.
CalvinH said:
If you want to update to ICS via OTA don't instal CWM.
As you have been told, you will get the OTA message but the update will fail.
So you have two choices (or three):
* Keep stock recovery and update to ICS when the OTA update is available
* Install CWM and update to ICS as soon as a DEV publishes an ICS ROM
* Install CWM and remove it as soon as you know the OTA is due (pretty lame, but you could do it).
Regards.
Click to expand...
Click to collapse
Thanks, I think I'll just wait for the OTA as I want to update as soon as ICS drops in.
Sent from my PC36100 using Tapatalk
I have a question about removing CWR. Actually 2.
1. Can't we just uninstall and wipe data with Titanium since it was installed as an .apk- from Gnufabio? (pretty sure this won't work but thought I would throw it out there anyways). Where is the recovery located on a tablet (what folders) Same as in phones?
2. Can we just flash the stock recovery by itself and not reset back to .13 or younger? If I am running stock ROM, it seems that I should be able to just reflash the stock recovery and replace it w/o changing the ROM or factory reset.
I have no problem doing it the long way but if it doesn't need to be done and we can replace the CWR with stock and not tamper with the ROM, it seems logical.
Clearly I just got the tab recently and have been reading and reading but they seem so much different than the way phones work. I am very comfortable flashing ROMs/Kernels/Mods on phones, but just a little intimidated with the tablet (for now).
Woodrube said:
I have a question about removing CWR. Actually 2.
1. Can't we just uninstall and wipe data with Titanium since it was installed as an .apk- from Gnufabio? (pretty sure this won't work but thought I would throw it out there anyways). Where is the recovery located on a tablet (what folders) Same as in phones?
2. Can we just flash the stock recovery by itself and not reset back to .13 or younger? If I am running stock ROM, it seems that I should be able to just reflash the stock recovery and replace it w/o changing the ROM or factory reset.
I have no problem doing it the long way but if it doesn't need to be done and we can replace the CWR with stock and not tamper with the ROM, it seems logical.
Clearly I just got the tab recently and have been reading and reading but they seem so much different than the way phones work. I am very comfortable flashing ROMs/Kernels/Mods on phones, but just a little intimidated with the tablet (for now).
Click to expand...
Click to collapse
1- The RecoveryInstaller app only help to flash the recovery image so no you can just delete it.
2- You can flash a stock recovery image via CWM. You can get a repacked version here.
http://forum.xda-developers.com/showthread.php?t=1154947&highlight=unroot
baseballfanz said:
2- You can flash a stock recovery image via CWM. You can get a repacked version here.
http://forum.xda-developers.com/showthread.php?t=1154947&highlight=unroot
Click to expand...
Click to collapse
I figured that would be the case with the executable part of the apk.
I read that thread but wasn't sure if only the stock recovery by itself could be flashed w/o the prepacked ROM.
Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible
Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2
Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse
andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!
Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.
To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:
andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?
Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!
So rumor has it that nexus S would be getting the 4.1.2 update so I thought I'll ask this just in case.
Will I get an OTA notification running custom kernel?
If yes is it safe to apply it?.
If no will I be able to just flash it with CWM without losing data?
Thats all I want to know I know it would revert back to stock kernel and unroot the phone which is not a problem.
Thanks in advance.
Gambler_3 said:
So rumor has it that nexus S would be getting the 4.1.2 update so I thought I'll ask this just in case.
Will I get an OTA notification running custom kernel?
If yes is it safe to apply it?.
If no will I be able to just flash it with CWM without losing data?
Thats all I want to know I know it would revert back to stock kernel and unroot the phone which is not a problem.
Thanks in advance.
Click to expand...
Click to collapse
No problem with the custom kernel. But it won't work with a custom ROM. When the update will flash, it will overwrite the kernel anyway.
polobunny said:
No problem with the custom kernel. But it won't work with a custom ROM. When the update will flash, it will overwrite the kernel anyway.
Click to expand...
Click to collapse
Thanks exactly what i was thinking and yes I am not running custom rom.
And to add on the update will flash just fine if you do it manually with cwm. It won't it you if it gets pushed to your phone and you select install ota... that would require stock recovery.
Either way hold your horses. Code released into aosp doesn't mean a update is coming right away. It may take a while
albundy2010 said:
And to add on the update will flash just fine if you do it manually with cwm. It won't it you if it gets pushed to your phone and you select install ota... that would require stock recovery.
Either way hold your horses. Code released into aosp doesn't mean a update is coming right away. It may take a while
Click to expand...
Click to collapse
So I just dont let it apply the OTA update? Does the phone get bricked if you do it without having stock recovery?
It's not really an issue though since if I get the OTA it will obviously be available as a flash zip as well by then. But I am curious to know what happens in that scenario.
Update fails. Reboot.
FOTA ripped for your enjoyment.
https://mega.co.nz/#!xoZigSqS!YHUa5Umv-8qjyFV1dtHs4lDQXMIn1q7plTz3zWeYSwY
That's completely unmodified. (I tried just installing it in CWM. Think I probably bricked doing something silly...)
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
gee one said:
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
Click to expand...
Click to collapse
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
bigleague4040 said:
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
Click to expand...
Click to collapse
I have a modified boot.img- perhaps that blocks the ota?
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
gee one said:
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
Click to expand...
Click to collapse
OMG, I would like to do it with no hassle.
I just want something to work ... grrr.
Option 2 would probably be the most straightforward. Essentially, you are unrooting. I just remembered, Samsung has Kies which might restore it to stock. You can download it from their website.
sent while running with scissors
mazak23 said:
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
Click to expand...
Click to collapse
the update in this thread is only about JB 4.1.2 that is officially the latest and the last one for our mobile. your message box is normal, there is no need for the usage of the OTA anymore since then. if u want to update to JB 4.3 follow this unofficial image:
http://forum.xda-developers.com/showthread.php?t=2463661
Holy thread resurrection Batman!!!
Oh boy. Here we go. Having troubles here.
I am trying to re-flash my phone to stock so I can return it under the protection plan. I firmly believe my radio might be on the fritz.
Anyway, I used the directions here:
http://theunlockr.com/2013/04/25/how-to-unroot-the-samsung-galaxy-s-relay-4g-sgh-t699/
Now it all completed successfully, and the phone is chilling at the SAMSUNG screen trying to boot. Not sure what to do at this point. Its been sitting there for a good 5 minutes.
Please help!!
UPDATE: Went into stock recovery, cleared Cache and Data, then rebooted it again, and it booted!
Which JelyBean Version...!!!
After installing this update what will be my os (JB 4.X.X) version???
saurabhsaurabhrai said:
After installing this update what will be my os (JB 4.X.X) version???
Click to expand...
Click to collapse
it is just from stock, will be updated to JB 4.1.2