I was waiting to root until an official cm 10.1 is available but I was thinking I better unlock the bootloader and root before an ota makes it impossible. the thing is I don't like any of the custom roms available at the moment because of kernal issues. I like everything to work. That means for the time being I would like to run unlocked rooted with cwm recovery and stock rom. My question is is there a stock rom available with ota killer built. in? i don't want some ota to push to my stock rom and screw it up or lose root. Freezing otacert isn't effective so what I want really is a slightly modified stock rom changed only enough to totally block unexpected ota's.
An expanded power menu with boot phone, power, boot recovery, and boot bootloader would be a great addition too but I don't want any theming or other substantial changes.
Does such a rom exist? If so could you tell me where? Thanks!
Sent from my DROID RAZR HD using Tapatalk 2
A custom recovery prevents any OTA from installing successfully, so that is really all that's needed, but you can remove or rename BlurUpdater_VZW.apk and odex if you want to prevent it from even downloading any updates.
cellzealot said:
A custom recovery prevents any OTA from installing successfully, so that is really all that's needed, but you can remove or rename BlurUpdater_VZW.apk and odex if you want to prevent it from even downloading any updates.
Click to expand...
Click to collapse
I have heard of people getting into bootloops who have custom recovery with stock rom. That's why I'm looking for a slightly customized rom with the features I described in op.
Sent from my DROID RAZR HD using Tapatalk 2
Related
This is the Official UK FOTA with root added and the Recovery/Boot update removed. These will not work on a non UK Device. I plan to add updates from other locations so if you have these official FOTA's available, please pm me.
I haven't changed anything else in the update so future upgrades should in theory work with this rom.
Install this with cwm and enjoy the new features that the FOTA update brings without having to worrying about losing root. This rom will only work if you are running the stock rom that the transformer came with. This will only install on top of the previous firmware update and will fail if you are using any other rom.
Root is not required to install this rom
Thanks to MoDaCo for the custom recovery that makes this rom possible.
First FOTA
R1_TF101_FOTA1_Root.zip
Alternative Link
Second FOTA:
R2_TF101_FOTA2.zip
Alternative Link
These are cumulative updates that can only be installed on top of stock HRI66.WW_epad-8.2.2.6-20110325 using custom recovery.
Reserved...
any way u can get a sys dump for us?
like use root explorer and just copy that sys folder and stuff or ADB?
No need for me to do this, as someone already did.
You can get it from this post here:
http://forum.xda-developers.com/showthread.php?p=13028129#post13028129
Good work on the deodexing btw.
thanks man a full rom will be up tonight o and i found this guy and his pet tree in GalleryNew3D.apk
just so we can have some laughs.
Great work. Can I flash this over the Modaco rom?
i dont think so i think u would need to delete app and framework in the system folder then flash my rom
ill be working on the recovery once i get on to help out on the scripts
im uploading a fixed rom go to my topic and u can post there since we r getting OT here.
Thank you for taking the lead on this. We - the new Transformer user base - are in your debt.
My unit, one of the first in the US release, is on its way to me from PC Richard. I'm hearing that it's likely to update its firmware automatically on switch-on. I'd prefer to use your update with root built in, so my questions are:
1. Is there a way to block the auto-update on a new Transformer - e.g. by not setting up its Wi-Fi till I've installed your rom? Or will it update from a version stored in its flash memory regardless?
2. If it is possible to block the initial update, will installing your rom prevent the official OTA from taking place afterwards? Or is a subsequent clash likely to occur?
3. The MediaFire link isn't currently working for me. That's a first! Do you have another link?
Thank you again for all your work.
if u want my rom was based off this just deodexed and a few things were fixed to use less ram etc. if u flash my rom the OTA wont happen. because it will already think u have the latest running since u would.
when the next OTA comes out when it trys to install it will fail most likely just like all other rooted devices.
dc13 said:
if u want my rom was based off this just deodexed and a few things were fixed to use less ram etc. if u flash my rom the OTA wont happen. because it will already think u have the latest running since u would.
when the next OTA comes out when it trys to install it will fail most likely just like all other rooted devices.
Click to expand...
Click to collapse
Thank you for this. So the deodexed rom (V.2) is the latest ASUS firmware with root?
yes everything about it is in the op/changelog area and i will keep that up to date
I really want to try your rom, but i want to know if i can restore the stock and remove clockwork recovery. In case of a warranty
jibril.r6 said:
I really want to try your rom, but i want to know if i can restore the stock and remove clockwork recovery. In case of a warranty
Click to expand...
Click to collapse
The current clockwork is a "soft" recovery - i.e the physical recovery image isn't overwritten.
Therefore, assuming with the new roms you can still use the same clockwork recovery you can backup pre-flash ("factory") flash the new roms. Any issues, boot back into recovery and restore from the Nandroid.
Highland3r said:
The current clockwork is a "soft" recovery - i.e the physical recovery image isn't overwritten.
Therefore, assuming with the new roms you can still use the same clockwork recovery you can backup pre-flash ("factory") flash the new roms. Any issues, boot back into recovery and restore from the Nandroid.
Click to expand...
Click to collapse
thank you very much!
tonight i'm going to flash!!!
The Transformer it's a very good device... it's a pity that honeycomb is still so... experimental!
Anyone else getting 403 Forbidden error from MediaFire when you actually go to download FOTA2.zip?
New links added...
Also, I've tried searching for this, but haven't found anything yet. Maybe you can shed some light. In my build.prop, the fingerprint shows US_pad instead of WW_epad, so it doesn't pass the checks in CWM recovery when I try to update using your ZIP files.
I'm guessing the US_epad signifies that it is the US build, and WW_epad is the UK build? My transformer came with build 20110325, and System Update says that there are no updates available.
Sent from my Transformer TF101 using Tapatalk
I figured they would be different, If anyone can get me the US updates from /cache I can mod these and add these to my first post.
Somehow I don't think the US version has updates pushed out yet. I keep hitting Check Update and it always comes back no updates available.
Sent from my Transformer TF101 using Tapatalk
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.
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!!!
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.
How is it with the Pixel 2, when I am rooted and running a custom kernel but still have stock recovery, can I update using OTA or do I still need to do this manually?
xda890 said:
How is it with the Pixel 2, when I am rooted and running a custom kernel but still have stock recovery, can I update using OTA or do I still need to do this manually?
Click to expand...
Click to collapse
Personally, I find it easiest to just download the full factory image and apply it without the wipe data (-w). Then do my normal tweaks. You can always download the ota and manually sideload it but I found it more flaky and do not want to mess around and have to do modifications/fixes to get it to install, only to end up going the factory image route in the end. IMHO
Aaahh, sounds like a good way to do it.. Didn't know I could disable wiping when flashing full ROM but now I know.. Thx.. ?
I just used the ota img and sideloaded with adb was super easy then pulled the boot.img and used magisk to repack ang get root on .25 update.
Ok, but I am modifying the system partition so I guess full ROM is the best way... ?
Sent from my Nexus 7 using Tapatalk