Database Users

noob question regarding manual nooter

Hello,
I had recently posted about having some issues with my Nook Color,
Well I finally fixed it and now I am getting ready to manually root it. I have 1.2 on my NC. My question is if I root it today and the manual rooter has an update that fixes something. Do I just follow the manual rooter instructions again using the new file and will all my stuff and settings still be saved?

Used nvflash to restore after bricking, now TF won't find latest firmware updates?

So I bricked my TF by trying to root it using a method developed for an older firmware. I was on the most recent (as of yesterday). So I used Nvflash to recover a stock image which is at 8.4.4.5-20110527. If I manually check for updates, I don't find anything.
Can I install the updates manually (if so, where do I find them)?
Or, is something not the right MD5 so Asus doesn't view my tab as stock?

There is a post somewhere (i cannot remember) that says after successful unbricking to 8.4.4.5 via nvflash, you have to manually update using the official asus 8.4.4.5 firmware taken from here: ftp://ftp.asus.com.tw/pub/ASUS/EeePAD/TF101/. The same post says that after the manual update, you will be able to get an ota to 8.4.4.11. Just try; there will be no harm done except a waste of time and effort.
Edit: Here's another method to get to 8.4.4.11 using manual update: http://forum.xda-developers.com/showpost.php?p=15933791&postcount=2

ondoy1943 said:
There is a post somewhere (i cannot remember) that says after successful unbricking to 8.4.4.5 via nvflash, you have to manually update using the official asus 8.4.4.5 firmware taken from here: ftp://ftp.asus.com.tw/pub/ASUS/EeePAD/TF101/. The same post says that after the manual update, you will be able to get an ota to 8.4.4.11. Just try; there will be no harm done except a waste of time and effort.
Click to expand...
Click to collapse
Thanks for the heads up, im working on downloading that now (18kbps on a 25mbps link...)

[Q] 3.2.1 rooted stock rom?

I currently have stock 3.2 rooted (US 7.006.01_COM_GEN2). I got an ota notification for 7.014.01. Is there a rooted version of the ota I can flash via cwm?
From searching around, it's also looking like another ota ( 7.014.02?) Is right behind the 7.014.01. Is that true, and if so, is that available in rooted cwm-flashable form?

Neither available yet. (I'm waiting too. They were just released, so give them some time)

I wouldn't be so quick to update something, without first knowing what it is
Old saying "if it ain't broke, don't fix it"
A little more info on the update;
http://www.androidcentral.com/syste...ia-brings-market-update-and-improved-ui-speed

Yes, the 01 and 02 will break root. But, never fear, I rooted it for you. Here's the link
http://forum.xda-developers.com/showthread.php?t=1307539&page=12

Very cool
Although I don't need it, it's nice to know some people are still doing some neat things for stock 3.2.

update without wiping?
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?

There are some roms currently in the works for 3.2.1. I'd expect them to come out fairly soon, keep an eye on the development forum. A few guys working on them right now.

mpkrcl said:
Thanks for the info. But, unless I'm reading your instructions wrong, it sounds like I have to wipe to update to your rooted 3.2.1. Is there just a rooted update.zip that can be flashed with cwm without wiping?
Or am I missing something?
Click to expand...
Click to collapse
Ok, if I hear you correctly, you are already rooted and want to use CWM to run the updates and keep root? Therefore you don't wipe out everything?
Piece of cake, just grab the update.zip and change it not to wipe your permissions. Then rebuilt it.
If you don't know how to do that, then put a backdoor into your device therefore you can get back into the device as root. Updates (normally) are not evil un-rooting tools. They don't seek and destroy root and rooting tools. Updates just reset the permissions on all files in /system removing the 'sticky' bit. The 'sticky' bit is how you get root.
What is a 'sticky' bit you ask? Well, in Linux (Unix) you can set a permission on a file so that any time it is run, it runs as the user that owns the file. This would be like setting a shortcut in Windows to say always run as 'Administrator'.
So, when you apply an update, the last thing it does is resets all the permissions back to their default. Since they recursively do this on the /system directory they remove the sticky bit on your su program.
So, all you have to do is set up a root backdoor outside the /system folder. My favorite is to set the ro.kernel.qemu = 1. This makes adb run as root. Now after your OTA resets permissions, you can just adb shell and you get #(root). Now you just reset your 'sticky' bits.
TD

[Q] How Do I Prevent OTA 4.3 Update

So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device

You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta

A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store

The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.

Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade

Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app

u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378

Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input

I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.

downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.

timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.

update query

Hi,
On my oneplus 5, current oxygen os version is 4.5.3. There was another OTA update that was available, but i never installed it (the file was downloaded on my phone, but never installed).
Now i believe the OTA update that could be available is higher than the one i skipped (4.5.5 or 4.5.6)
Query is, if i choose to install the new update, will it install all the other older updates which i have skipped or is there a separate procedure that i need to follow.
I have not rooted my phone and don't intend to do it any soon.

user30 said:
Hi,
On my oneplus 5, current oxygen os version is 4.5.3. There was another OTA update that was available, but i never installed it (the file was downloaded on my phone, but never installed).
Now i believe the OTA update that could be available is higher than the one i skipped (4.5.5 or 4.5.6)
Query is, if i choose to install the new update, will it install all the other older updates which i have skipped or is there a separate procedure that i need to follow.
I have not rooted my phone and don't intend to do it any soon.
Click to expand...
Click to collapse
The new update should by default also include all previous update, just need to update one and you're good. you could also manually download the new update and install it in recovery. Either way you should be good

n0013z said:
The new update should by default also include all previous update, just need to update one and you're good. you could also manually download the new update and install it in recovery. Either way you should be good
Click to expand...
Click to collapse
Thanks!!!

user30 said:
Hi,
On my oneplus 5, current oxygen os version is 4.5.3. There was another OTA update that was available, but i never installed it (the file was downloaded on my phone, but never installed).
Now i believe the OTA update that could be available is higher than the one i skipped (4.5.5 or 4.5.6)
Query is, if i choose to install the new update, will it install all the other older updates which i have skipped or is there a separate procedure that i need to follow.
I have not rooted my phone and don't intend to do it any soon.
Click to expand...
Click to collapse
The Updater will force you to update in the appropriate order they were pushed out. This is needed due to some functions may use older updated code.

thanks.