Develop Bugs

Help! Rooted Android & Restart Recovery. Thanks!

Hi all,
Can someone help me on this?
1) how do you "root" your android on sd card install (have root acess)
2) how do you "restart recovery" in Myn's Warm Donut? (i cant find an option for this)
Thanks!

we do not need to root our phones we are already root users because of it running on a non native device.
we also dont have recovery like other android phones we have the Dr. NoMoRootFS menu when android is booting you pretty volume up to boot into the installer

k m8.
thanks!

thoughtlesskyle said:
we do not need to root our phones we are already root users because of it running on a non native device.
we also dont have recovery like other android phones we have the Dr. NoMoRootFS menu when android is booting you pretty volume up to boot into the installer
Click to expand...
Click to collapse
actually I believe we only have the root role, we are not logged in as root. If we were root you could see the data directory, and wouldn't ever need su. Does anyone know how to log in as root on the android(different from rooted)?

[Q] Unable to change bootanimation [UK T-Mob Froyo ROM]

I'm at a loss on how to change the bootanimation.
I've got the T-Mobile UK Froyo Rom with some apps removed via BloatFreezer. I'm rooted and S-Off.
Using Root Explorer, I've managed to get rid of the T-Mobile animation by deleting
TMD_bootanimation.zip
TMU_bootanimation.zip
Startup_480x800_20fps.gif
from /system/customize/resource. I now get the blue Android text which ripples.
I've tried copying various bootanimation.zip files to /system/customize/recourse and /data/local I've checked that all persmissions are as they should be. I've tried a combination of renaming files by adding the TMD_ or TMU_, but still nothing!
I'm at a loss, does anyone know if it's possible to change the bootanimation on the T-Mob UK Froyo ROM?
I'd prefer to do it via the Root Explorer method. All though I think of myself as technically minded, and managed to root and s-off first time without incidence, I'd prefer keeping flashing to a minimum.
Thanks.

random noob questions...

OK,
1st Hi all and thanks for not bashing my lack of knowledge. I have done many searches and am now more confused than before.
I am comming from a droid X, I did the z4 root on it to get wifi tether working, it was on 2.2.1 I believe. Well it went very good, but I never got a push for an update. Got the new GN on verizon and tried to restore it back to stock, didn't work, so instead of selling it I gave it to my mom. Also, did this on a friends and he did get the update push and lost the root and superuser access.
This story is just so you know I am a complete noob. Other than following someones set by set on using Z4 I have really not done anything and have some questions on my new phone.
1. why would I want to unlock the bootloader?
2. after reading about the wifi hotspot by svtp do I need to root?
3. If i root and/or unlock the bootloader will this stop the updates from google (main reason I bought the phone)?
4. I am not into overclocking or modding but I want to be able to have wifi if I ever need it. That is the only thing I want.
Basically I am looking to unlock the wifi and still get all the google updates, is this possible? As of right now I think buying the svtp app is my best bet, I just don't want an unexpected bill showing up.

ok, still not rooted or unlocked. cannot get svtp to work wifi

Follow this guide --> http://forum.xda-developers.com/showthread.php?t=1382163

re #1: you need to unlock the bootloader to do pretty much anything non standard with your phone.
Since unlocking the bootloader wipes all data on the phone it's a good idea to do it early. You can leave it otherwise stock while you think about it, you can even relock it if you need to return the phone for some reason.
Neither unlocking nor rooting the phone will stop you getting the OTAs, it's custom roms that will do that. However most OTAs will stop your root access because they reset the permissions on your su files.
hth

Clancy_s said:
Neither unlocking nor rooting the phone will stop you getting the OTAs, it's custom roms that will do that. However most OTAs will stop your root access because they reset the permissions on your su files.
Click to expand...
Click to collapse
Just to add further to this... not only will custom ROMs stop you from getting OTA updates, having custom recovery (ClockworkMod) will prevent them from applying, even with the stock ROM. If using a stock ROM with custom recovery, you'll need to do the update manually. If you wait until you get the update notification, your phone should have downloaded the update to /cache. You can then use the custom recovery to apply the update. Alternatively, you can look on these forums for someone to post the URL to the OTA update zip file, download it, and flash it manually (this way you don't need to wait until your phone gets the update, you can download it and have it sooner).
In either case, you'll usually need to re-root, as stated. This is easier with a custom recovery, because you should just have to flash superuser immediately after flashing the update, before rebooting.
Until CM9 is stable, I'm running the stock ROM with ClockworkMod recovery. I can download the OTA updates manually and flash them with ClockworkMod then flash superuser and I'm good to go. Custom recovery makes it nice and easy to retain root, as well as the ability to do nandroid backups, etc.

Root without unlocking bootloader someday?

I know it can't be done right now but all I want is the stock rom with superuser installed. When the one-click comes out do you guys think it will have the option?
Sent from my Nexus 7 using Tapatalk 4 Beta

Why not just unlock? You can always lock it again if you want to return to factory.

^^ This, plus if you don't want to replace the recovery you can always use ADB to boot do a different recovery like TWRP to flash the SuperSU :good:

Will an unlocked bootloader still be able to accept OTA updates?
If not, will it accept OTA updates after relocking the bootloader?
Thanks.

Godswrath said:
Will an unlocked bootloader still be able to accept OTA updates?
Click to expand...
Click to collapse
Yes.
Unlocking your tablet doesn't really make changes to your system. It sets a flag that allows you to modify partitions which were previous read-only and also allows you to boot unsigned kernels/recoveries.
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.

sfhub said:
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
Click to expand...
Click to collapse
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.

sfhub said:
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
Click to expand...
Click to collapse
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).

Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.

Godswrath said:
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Click to expand...
Click to collapse
you just do
chattr -i /system/etc/install-recovery.sh
I attached an UPDATE-SuperSU-ota.zip install file you can run from TWRP to do it for you. You just run it after UPDATE-SuperSU-v1.51.zip and it will set you up to receive OTAs successfully (you'll need to re-install the two files after the OTA to put root back on)
So basically you do this
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip
install UPDATE-SuperSU-ota.zip
You can even "chain" install them, just select UPDATE-SuperSU-v1.51.zip first.

Aria807 said:
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Click to expand...
Click to collapse
IMO you can actually learn a lot trying to understand out why things fail

Automatic Software Update

Here is my situation: I used Odin v3.7 and root66_RWC_I747MVLDMF1.tar.md5 to root my i747m to rooted JB 4.1.2. The root was successful but stupid me I forgot to uncheck automatic software update on my phone. Come morning I discovered that the automatic software update downloaded the latest version of JB, I'm assuming 4.3 or higher which everyone here knows it is half-baked. I turn on my phone and I get a message saying that the latest software has been downloaded and it's now asking to install it. How do remove the downloaded software update? Where is this file sitting on my phone? Do I need to re-root my S3 to get rid of the software update? Do I need to unroot my S3 and then root it again? What options do I have? Any advice is greatly appreciated.

trial_user said:
Here is my situation: I used Odin v3.7 and root66_RWC_I747MVLDMF1.tar.md5 to root my i747m to rooted JB 4.1.2. The root was successful but stupid me I forgot to uncheck automatic software update on my phone. Come morning I discovered that the automatic software update downloaded the latest version of JB, I'm assuming 4.3 or higher which everyone here knows it is half-baked. I turn on my phone and I get a message saying that the latest software has been downloaded and it's now asking to install it. How do remove the downloaded software update? Where is this file sitting on my phone? Do I need to re-root my S3 to get rid of the software update? Do I need to unroot my S3 and then root it again? What options do I have? Any advice is greatly appreciated.
Click to expand...
Click to collapse
This is kinda a shot in the dark, but maybe go to recovery mode and clear cache? I would assume that's where the file went? Or... get a file explorer and find the file and delete it, or enable debug mode and find the file in /cache and delete it.
After a bit of research, that is where it went. You can also do like this thread mentions and freeze the update service using titanium backup com.motorola.blur.updater
source: android.stackexchange(dot)com/questions/32205/where-can-i-find-the-ota-update-file
offtopic: I downloaded beanstock(4.4) and found a way to enable tethering, apart from that, everything seems smooth and working... If you really dont like 4.3

mpj123 said:
This is kinda a shot in the dark, but maybe go to recovery mode and clear cache? I would assume that's where the file went? Or... get a file explorer and find the file and delete it, or enable debug mode and find the file in /cache and delete it.
After a bit of research, that is where it went. You can also do like this thread mentions and freeze the update service using titanium backup com.motorola.blur.updater
source: android.stackexchange(dot)com/questions/32205/where-can-i-find-the-ota-update-file
offtopic: I downloaded beanstock(4.4) and found a way to enable tethering, apart from that, everything seems smooth and working... If you really dont like 4.3
Click to expand...
Click to collapse
Thanks for the tip. I found the update file which was called, "update.zip" in the /cache/fota directory using the Root Browser app.