Related
I had previously unlocked my bootloader and was running CM6.1, but I had to go back to stock because my company's email app (Good for Enterprise) refuses access on rooted devices.
I would like to monkey around with different configurations to see if I can find a way to run Good on CM6.1. I don't want to do this if I have to reinstall everything if it doesn't work however.
So my question is this. I just want to get the Clockwork recovery on my N1 so I can back up the non-rooted OS and monkey around a little. Can this be done with ABD on a non-rooted device?
Gave it a shot, worked fine.
"fastboot flash recovery clockwork-image-name.img"
Good for Enterprise still runs, so it isn't looking at the recovery to determine rooted status.
Nevermind, clockwork didn't survive a reboot. Good news is I was able to get a backup first.
After installing recovery via fastboot, try removing the following files via adb:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
danger-rat said:
After installing recovery via fastboot, try removing the following files via adb:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
When I try to do this from the recovery, these files are not found, and adb can't see the device from the bootloader. If I boot into the OS, it will be too late - the recovery would be wiped by then and I am back to square one. I must be missing something.
Is there any way to pull the System partition and mount the .img file on my PC to do this? That sounds a little dangerous though
Just thought, you need root to delete the files.
You'd probably have to root, install recovery, then install a non-rooted ROM, but keep custom recovery...
Sent from my Nexus One using XDA App
This is what you need to do:
1) boot your device into the OS
2) download the rageagainstthecage binary and save it as rageagainstthecage in the /tools folder (in the android SDK)
3) plug your device to your computer
4) open a command prompt in the /tools directory
5) type adb devices to make sure your computer sees your device
6) push the rageagainstthecage binary to /data/local/tmp/ by typing adb push rageagainstthecage /data/local/tmp/rageagainstthecage
7) type adb shell to open a shell
8) change the permissions on the binary to allow it to run by typing chmod 700 /data/local/tmp/rageagainstthecage
9) navigate to the directory (cd /data/local/tmp) and execute the binary by typing ./rageagainstthecage
10) wait for it to run, and it will exit the shell
enter the following command at the prompt: adb kill-server
11) enter the following command at the prompt: adb start-server
12) open an adb shell again: adb shell
13) now you should have a temporary root shell. You should see a # instead of a $. if you still see the $, go back to step 9. You may have to do this a few times (I had to do it 3 times before I got root access)
14) now, mount the /system partition as r/w by typing mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
15) delete the two files: rm /system/etc/install-recovery.sh and rm /system/recovery-from-boot.p
16) mount the partition as r/o by typing mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
17) exit the shell
18) now flash your custom recovery
Awesome, thanks. I'll give it a shot later!
This worked flawlessly, thanks for the great writeup!
Santoro said:
This worked flawlessly, thanks for the great writeup!
Click to expand...
Click to collapse
Two things: First, don't forget that any update from Google always has those two files in it, so they will reappear after every update.
Second, I just reread your first post again. I think you should still be able to kepp root and have your company's email working. I think the problem was that you were using an AOSP-based ROM instead of a stock-based one. Follow the directions for rooting in my signature (the first part is essentially the same as what you just did to gain r/w access to the system partition via adb, the second part is copying su and Superuser.apk to the right directories). Root is essentially one additional file copied to your /system directory, so I believe your company's email will still work with root.
efrant said:
This is what you need to do:
1) boot your device into the OS
2) download the rageagainstthecage binary and save it as rageagainstthecage in the /tools folder (in the android SDK)
3) plug your device to your computer
4) open a command prompt in the /tools directory
5) type adb devices to make sure your computer sees your device
6) push the rageagainstthecage binary to /data/local/tmp/ by typing adb push rageagainstthecage /data/local/tmp/rageagainstthecage
7) type adb shell to open a shell
8) change the permissions on the binary to allow it to run by typing chmod 700 /data/local/tmp/rageagainstthecage
9) navigate to the directory (cd /data/local/tmp) and execute the binary by typing ./rageagainstthecage
10) wait for it to run, and it will exit the shell
enter the following command at the prompt: adb kill-server
11) enter the following command at the prompt: adb start-server
12) open an adb shell again: adb shell
13) now you should have a temporary root shell. You should see a # instead of a $. if you still see the $, go back to step 9. You may have to do this a few times (I had to do it 3 times before I got root access)
14) now, mount the /system partition as r/w by typing mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
15) delete the two files: rm /system/etc/install-recovery.sh and rm /system/recovery-from-boot.p
16) mount the partition as r/o by typing mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
17) exit the shell
18) now flash your custom recovery
Click to expand...
Click to collapse
Without unlock recovery i can install Amon RA?(‘fastboot oem unlock‘)In this way as u typed.
W3ber said:
Without unlock recovery i can install Amon RA?(‘fastboot oem unlock‘)In this way as u typed.
Click to expand...
Click to collapse
Not sure what you are asking.
If your bootloader is unlocked, you can use fastboot. Download the recovery image you want into the /tools directory of your SDK and rename it recovery.img. Open a command prompt in the same directory. Type fastboot devices to make sure fastboot sees you device. Then type fastboot flash recovery recovery.img and you are done.
If your bootloader is not unlocked, you can use flash_image, but you need root access. See attachments on how to get root if your bootloader is locked, and how to flash a custom recovery with a locked bootloader.
efrant said:
Two things: First, don't forget that any update from Google always has those two files in it, so they will reappear after every update.
Second, I just reread your first post again. I think you should still be able to kepp root and have your company's email working. I think the problem was that you were using an AOSP-based ROM instead of a stock-based one. Follow the directions for rooting in my signature (the first part is essentially the same as what you just did to gain r/w access to the system partition via adb, the second part is copying su and Superuser.apk to the right directories). Root is essentially one additional file copied to your /system directory, so I believe your company's email will still work with root.
Click to expand...
Click to collapse
I was using the Nexus One 2.2.1 stock image directly from Google. My problem is that the Good for Enterprise actively checks for root. Specifically if the Superuser.apk exists, it refuses to let me in and cites corporate policy.
Since getting my stock backup, I was free to experiment and I had some success getting Good running on CM 6.1. Taking clues from your earlier instructions, I used adb shell to rename su to su.bak and Superuser.apk to Superuserapk.bak on the phone, then rebooted. After the reboot, I don't have root anymore.
This is a compromise, but at least I don't have to give up that CM6 goodness just to use my corporate email. So far I have not seen any issues in CM6 resulting from not having root. In an emergency I can rename them the superuser files back using rageagainsthecage as you outlined but I probably won't do it often.
Thanks for the help!
Santoro said:
I was using the Nexus One 2.2.1 stock image directly from Google. My problem is that the Good for Enterprise actively checks for root. Specifically if the Superuser.apk exists, it refuses to let me in and cites corporate policy.
Since getting my stock backup, I was free to experiment and I had some success getting Good running on CM 6.1. Taking clues from your earlier instructions, I used adb shell to rename su to su.bak and Superuser.apk to Superuserapk.bak on the phone, then rebooted. After the reboot, I don't have root anymore.
This is a compromise, but at least I don't have to give up that CM6 goodness just to use my corporate email. So far I have not seen any issues in CM6 resulting from not having root. In an emergency I can rename them the superuser files back using rageagainsthecage as you outlined but I probably won't do it often.
Thanks for the help!
Click to expand...
Click to collapse
Just for your info, Superuser.apk does not give you root, it only manages the root permissions. If your corporate email application checks only for Superuser.apk, you could technically delete Superuser.apk and keep the su binary. Your would still have root, and your corporate email app would work. The su binary is what actually gives you root access. All that the Superuser.apk file does is manages the permissions for root access, i.e., it allows or denies applications from using the su binary. Everything would work fine (including all apps that require root) without Superuser.apk. HOWEVER, just as a warning, without Superuser.apk, you would have no control over which apps have root access...
I will have to put su back and see what happens. I may be recalling wrong, maybe it checks for su also...
I experimented a bit more and it looks for both files. Sorry for the confusion.
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
dry3333 said:
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
Click to expand...
Click to collapse
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
ajbiz11 said:
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
Click to expand...
Click to collapse
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
dry3333 said:
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
Click to expand...
Click to collapse
That's exactly what I'm referring to (The settings thing)
Lemme go find that command for you
---------- Post added at 06:00 AM ---------- Previous post was at 05:56 AM ----------
Wish I knew this existed when I was working on the L port
There's an app to do exactly what you need without looking up partitions
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Although if you want to go through terminal, here's a tutorial
http://ckirbach.wordpress.com/2012/11/27/how-to-remount-system-as-read-write-in-android/
Basically, you use grep to find the name of the system partition, then run the mount command to remount the partition you found in that precious step
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
dry3333 said:
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
Click to expand...
Click to collapse
The remount app should do exactly that
Try the command option and make your changes then reboot
ajbiz11 said:
The remount app should do exactly that
Try the command option and make your changes then reboot
Click to expand...
Click to collapse
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
dry3333 said:
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
Click to expand...
Click to collapse
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
ajbiz11 said:
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
Click to expand...
Click to collapse
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
You can remove it from the ViperROM zip and format ONLY system and reflash
That SHOULD work
That's like...the be all end all
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
nkk71 said:
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
Click to expand...
Click to collapse
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
dry3333 said:
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
Click to expand...
Click to collapse
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
nkk71 said:
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
Click to expand...
Click to collapse
The windows drivers don't work with recovery mode (usually)
ajbiz11 said:
The windows drivers don't work with recovery mode (usually)
Click to expand...
Click to collapse
they do for me, but sometimes (after flashing a new/different version) i have to manually select the drivers, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
dry3333 said:
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
Click to expand...
Click to collapse
sure, no problem :good: :good:
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title
So I picked up a ADT-1 due to having Ethernet and more HD space on it. FOund out only certain apps can "cast" to it due to it being a dev device has there been anyone that figured out what needs to get it to have full casting features?
https://developer.android.com/tv/adt-1/index.html
Try changing ro.build.type to eng in build.prop, that should open up all apps.
/sub
let us know if this works
Confirmed this works!
HomerSp = worth his weight in gold.
Sorry
HomerSp said:
Try changing ro.build.type to eng in build.prop, that should open up all apps.
Click to expand...
Click to collapse
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again
Bboy_LeoGun said:
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again
Click to expand...
Click to collapse
1. Root
2. Open /system/build.prop
3. Change the line
4. Reboot
5. Enjoy.
I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?
Budius said:
I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?
Click to expand...
Click to collapse
build.prop has to be chmodded to 0644, or the device will not boot.
HomeSp I can't thank you enough!
That was exactly the issue. Third time is a charm.
So at the end of the procedure I:
- cd /system/
- mv build.prop build.prop.bak (just for the the sake of it)
- mv /sdcard/build.prop /system/
- chmod 0644 build.prop
- chown :root build.prop (prolly not needed but what-a-heck, why not)
- ls -l (and checked that both build.prop and build.prop.bak are exactly the same permission, owner and group)
- exit, exit adb reboot and all works great"
Thanks again!!!
Budius said:
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
Click to expand...
Click to collapse
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.
jm9843 said:
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.
Click to expand...
Click to collapse
my idea was a bare-minimum changes too. I just ended up ****ing up stuff and had to re-built a couple of times until I made it right.
but yeah, if you're comfortable with terminal commands and do the proper `chmod` (which I originally didn't), you can get everything done with "adb shell su" following like this:
- from PC: adb shell pull file to your PC
- from PC: edit file
- from PC: adb shell push file to /sdcard/
- from PC: adb shell
- from device shell: su
- from device shell/su: make /system/ writable, chmod file, rename "old" build.prop, copy new one over, double check chmod before rebooting.
ps.: the root from that post does install SuperUser.apk on the device, it's there on the UI, but after you do those changes there's some options in the .apk to remove root and uninstall it (if you want to)
I just thought that I'd directly use some build prop editor apk and do it easily but now my device is bricked :v
Stock ROM on download.
I'm just getting a black screen and bootloader.
So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
jm9843 said:
So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Have any of you tried Slingplayer casting after changing build.prop?
Apple TV just died recently, it was the most reliable thing for Airplaying Slingplayer. Chromecast slingplayer kind of is ****ty at times.
Followed Budius' instructions and it worked perfectly.
adb pull /system/build.prop
----(edit build.prop on Notepad++ and changed ro.build.type=user to ro.build.type=eng)
adb push build.prop /sdcard/
adb shell
su
mount -o remount,rw /system
cd /system/
mv build.prop build.prop.bak
mv /sdcard/build.prop /system/
chmod 0644 build.prop
chown :root build.prop
ls -l
---(checked that both build.prop and build.prop.bak are exactly the same permission, owner, and group)
mount -o remount,ro /system
exit
exit
adb reboot
during the update from 5.0 -> 5.0.2 my ADT-1 stopped working again
It showed the little droid with the belly open and an error message
so that means here I went again to restore it, and this time I manage to streamline a bit the process, so let's share with you guys. Remember, my idea with this process is to have STOCK, but with Cast working from any app. I have no intention to root, or flash custom this or that. I want something that I can cast without issues and hopefully it will update the next update without problems.
first of all, the CWM link I posted before is giving malware warnings on Chrome so I found an alternative, and of course XDA is the source (see downloads).
so to factory restore ADT-1 to good working condition, was the same I said before:
- install CWM:
Code:
fastboot flash recovery cwm_molly_recovery_lpx13d.img
- install stock image. CWM->install zip-> from ADB:
Code:
adb sideload update-molly-Stock-LPV79-1.zip
- reboot and let auto-update run until the end.
now to enable cast to all apps with absolutely minimal modifications to the system (hopefully enabling future updates to run without issues)
- reboot ADT-1, holding the button, enter fastboot mode
- reboot to the CWM, but without installing it:
Code:
fastboot boot cwm_molly_recovery_lpx13d.img
- in CWM go to `mount n storage` -> mount /system
and carry on to do the build.prop modification from there, the trick is that I did not have to install a custom recovery and did not have to install super user. I made the modification directly via a RAM-only CWM and that's it. So below is just a copy of my previous post
Code:
> adb pull /system/build.prop /home/budius/build.prop
then change the build.prop on my computer and rename to new_build.prop.
And back to terminal
Code:
> adb push /home/budius/new_build.prop /system/new_build.prop
> adb shell
# cd system
# mv build.prop build.prop.bak
# mv new_build.prop build.prop
# chmod 0644 build.prop
And that's all! Full cast enabled to ADT-1 with the most absolutely minimal system changes I could come up with :victory: :highfive:
Downloads:
- here you'll find a very nice workin CWM.
- good working stock Android TV image for ADT-1
bonus:
while searching stuff I found this: https://plus.google.com/+AdamLawrence/posts/5Yr5vG7QJUq
I didn't try it but it seems useful, so the link is there.
** Requires ROOT+Busybox and either Terminal or a capable File Manager
So you don't feel like flashing a new ROM and losing all your data, but your carrier's boot up and shutdown branding is getting on your nerves? Here is what you do, the basic idea is the same as putting on a new boot animation
I'll assume you're using a Terminal and bootsamsung.qmg for the rest of this, the other files follow the same method
Copy stock boot and shutdown animations onto your SD card, I'll call the path to this location %sd%. A copy of the stock files in the attached archive.
Open terminal and become root
Code:
su
You may need to remount your /system partition as writable, if you're connecting via ADB, adb.exe may crash here - that's fine, just re-connect the USB cable and you shouldn't need to repeat this step again
Code:
mount -o remount,rw [COLOR="RoyalBlue"]/system[/COLOR]
Copy bootsamsung.qmg from %sd% to /system/media/,
Code:
busybox cp -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]" "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Set the permissions of the file to 644,
Code:
chmod [COLOR="red"]644[/COLOR] "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Get rid of the SD card copy if you don't want it anymore,
Code:
rm -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Clean up any overriding animations, I had this happen for my shutdown animation where my carrier had a shutdown directory in /system/media/video/ which contained another copy of shutdown.qmg, so check for the existence of these and remove them, e.g.
Code:
if [ -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B] ]; then
rm -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B]
fi
Reboot and see what happens!
Extra notes: Always keep backups of original files. If you can't get past the boot animation, restore the backups.
paulie-uk said:
** Requires ROOT+Busybox and either Terminal or a capable File Manager
So you don't feel like flashing a new ROM and losing all your data, but your carrier's boot up and shutdown branding is getting on your nerves? Here is what you do, the basic idea is the same as putting on a new boot animation
I'll assume you're using a Terminal and bootsamsung.qmg for the rest of this, the other files follow the same method
Copy stock boot and shutdown animations onto your SD card, I'll call the path to this location %sd%. A copy of the stock files in the attached archive.
Open terminal and become root
Code:
su
You may need to remount your /system partition as writable, if you're connecting via ADB, adb.exe may crash here - that's fine, just re-connect the USB cable and you shouldn't need to repeat this step again
Code:
mount -o remount,rw [COLOR="RoyalBlue"]/system[/COLOR]
Copy bootsamsung.qmg from %sd% to /system/media/,
Code:
busybox cp -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]" "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Set the permissions of the file to 644,
Code:
chmod [COLOR="red"]644[/COLOR] "[COLOR="RoyalBlue"]/system/media/[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Get rid of the SD card copy if you don't want it anymore,
Code:
rm -f "[COLOR="RoyalBlue"]%sd%[/COLOR][B][COLOR="Green"]bootsamsung.qmg[/COLOR][/B]"
Clean up any overriding animations, I had this happen for my shutdown animation where my carrier had a shutdown directory in /system/media/video/ which contained another copy of shutdown.qmg, so check for the existence of these and remove them, e.g.
Code:
if [ -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B] ]; then
rm -f [COLOR="RoyalBlue"]/system/media/video/[/COLOR][B][COLOR="Purple"]bootsamsung[/COLOR]/[COLOR="Green"]bootsamsung.qmg[/COLOR][/B]
fi
Reboot and see what happens!
Extra notes: Always keep backups of original files. If you can't get past the boot animation, restore the backups.
Click to expand...
Click to collapse
Hello, I'm interested in debranding my verizon s5. I'd love to get rid of the Verizon screen at bootup. I read through your directions and it seems that you are suggesting overwriting the animation with the stock that you provided. All good. It is the use of the terminal that I am completely unfamiliar with. I tried using adb.exe in a command window inside of windows 7 and it didn't even like the first command 'su' My phone is rooted with a custom rom and busybox in developer mode. Could you help me out with what terminal to use and how to connect etc. to enter the commands? I have a decent filemanager installed but It doesn't let me write to system. Thanks for this post.
Eaglebiker said:
Hello, I'm interested in debranding my verizon s5. I'd love to get rid of the Verizon screen at bootup.
Click to expand...
Click to collapse
My first comment must be to say I have a G900F, the international version of the phone and it's using a stock ROM with a few tweaks, e.g. root. A custom ROM will have changed the system partition already so this method shouldn't be applicable there - if it shows a carrier logo on a custom ROM then it's in another partition, not system
Eaglebiker said:
I read through your directions and it seems that you are suggesting overwriting the animation with the stock that you provided. All good. It is the use of the terminal that I am completely unfamiliar with.
Click to expand...
Click to collapse
I gave terminal instructions so people could do it only using their phone but as you've noticed, it's not the only option
Eaglebiker said:
I tried using adb.exe in a command window inside of windows 7 and it didn't even like the first command 'su'
Click to expand...
Click to collapse
If you are using adb, make sure that adb can gain root - the flag should be somewhere in your superuser's settings - then with your USB connected launch adb into shell mode from your computer. This makes adb act as a terminal
Code:
adb shell
If you see a $ then you are not root and will need to gain root, i.e. run su
If you see a # then you are root and don't need to do that
Eaglebiker said:
My phone is rooted with a custom rom and busybox in developer mode.
Click to expand...
Click to collapse
All good things!
Eaglebiker said:
Could you help me out with what terminal to use and how to connect etc. to enter the commands?
Click to expand...
Click to collapse
The terminal I use is can be found here (though I used v1.0.65). Most custom ROMs already include it so you may find it in your apps already. It's all on your phone so you'd type on your phone's keyboard as normal. You shouldn't have to use this if you want to use ADB.
Every time I wrote a %path% you will need to enter the real path for what you have on your device, e.g. %sd% may be /extSdCard/
Eaglebiker said:
I have a decent filemanager installed but It doesn't let me write to system.
Click to expand...
Click to collapse
What doesn't let you do this? If it's "read only" then you may need to remount the /system partition (my step 3). File managers like the one you get with CM do let you do root things but it needs to be in root mode or prompt mode (see it's settings). To find /system in a file manager, the easiest way is to keep going up until you're at /, then you should be able to go down through [/B]/system[/B]
Eaglebiker said:
Thanks for this post.
Click to expand...
Click to collapse
Thank you for letting me give some meaningful answers in post 3!
The Rom I'm using would be better described as a stock lollipop rom for the 900v with a few tweaks.
I now understand that you can have a terminal on the s5. I've installed the terminal and greatly prefer it. Using a terminal on the s5 hadn't even occurred to me and it sounds much easier then hooking to a computer needlessly. Awesome.
I manage to get su access #. in step 2.
in step 3 I type in the mount command and nothing seems to happen. no errors
in step 4 it tells me the folder or file doesn't exist. I'm certain it does. I can see it in my file manager. in the folder /extSdCard/bootsamsung.qmg and the destination folder is /system/media as well. I've tried it with and without quotes and no joy. Any clue what is going on?
Hello my friends
Good as recently know the Sony launched the lollipop firmware for d5803, and also know still do not have the recovery'm waiting anxiously for it haha. good'll do a mini tutorial to help them maintain the permissions so gives to delete some things like native apps. come on
# Install the firmware 23.0.A.2.106
# Make Root how giefroot
# Extract the file giefroot and within it there will be the files folder, you hold down shift and click the right mouse button and go to the option open command window here, Plans to open the cmd and type these commands below or copy and paste one by one. Well look at your mobile screen, will ask the permissions of adb.
adb push systemrw.sh /data/local/tmp
adb push modulecrcpatch /data/local/tmp
adb push wp_mod.ko /data/local/tmp
adb shell
chmod 777 /data/local/tmp/systemrw.sh
chmod 777 /data/local/tmp/modulecrcpatch
chmod 777 /data/local/tmp/wp_mod.ko
su
cd /data/local/tmp
./systemrw.sh
# Once you have done the above option you check with the root explorer to this with the permissions RW-RO
# download the firmware lollipop 23.1.A.0.690 also download the PRFCreator, UPDATE-SuperSU-v2.46, Z3c-lockeddualrecovery2.8.3-RELEASE.flashable. With these files you create a rom zip pre rooteada. place on your sd card, enter the recovery and give the following wipes
**system, data, cache** given wipes, install the rom preroot and the end of the installation you off the phone.
# Open FlashTool in flashmod select the option D5803_23.1.A.0.690_Baltic_Generic firmware on the right side has the option called Exclude: below have numerous options, you mark only the option SYSTEM and click flash, do the flash firmware.
# Turn on the phone and see how this the permissions with root explorer. End :victory:
The files mentioned above to download are all found right here on xda :good:
Thanks my friend >>Pedrooca <<
Do not forget to give me a thank you [:good:], it will be great for me because somehow will encourage me to keep my work and create new roms and mods! Thank you all
So far no bug was found. I ask you please file a bug found that I can fix. Thank you