Database Develop

[Q] adb remount

Hi guys,
sorry if my english isnt so good...
i'm in trouble with ADB..
i want to upgrade my swype keyboard on my NEW M1 rom eu....i got the 1.58 and i want to try the 1.60..
i found a thread on this forum with commands for upgrading the swype like this way:
Code:
adb remount
adb shell
su
pm list packages -f | grep swype
rm /system/app/<restOfApkPathFoundInAboveCommand>
pm uninstall <value after apk= found in result of 2 commands above>
exit
Install normally. If you want the apk in the rom:
adb push <newSwype.apk> /system/app/<newSwype.apk>
adb remount
adb shell
pm install <newSwype.apk>
(found here-> LINK)
I'm stuck at the beginning:
Code:
C:\android\tools>adb devices
List of devices attached
9000ec2a228b device
C:\android\tools>adb remount
remount failed: No such file or directory
my phone is rooted and in debug usb mode..I dont understand how can I go ahead...
what can I do?
thanks
ivan

Same here.

gbates said:
Same here.
Click to expand...
Click to collapse
oh..i'm not the only one! : >
we need to find the solution...but it's not easy..
are u using the NEW M1 rom too?

Rooting doesn't automatically give you remount permissions AFAIK.

i just use this command
Code:
adb push test.txt /sdcard/test.txt
and the copy is ok....i found the file in the sgs sdcard...
The command adb remount is for the /system directory (for set write permission) .... i think it cant find the directory /system on the phone......why?!?!

danmullen said:
Rooting doesn't automatically give you remount permissions AFAIK.
Click to expand...
Click to collapse
mmmm what do u mean? i need to do something else? thanks

Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.

Same results using a different ROM?

psychedelic'd said:
Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.
Click to expand...
Click to collapse
No lagfix installed at the moment..i installed lagfix when i was on M2 but i think that reflashing removed the lag fix...is it right?
harold4 said:
Same results using a different ROM?
Click to expand...
Click to collapse
Not yet but i think i'm gonna try it this afteroon if i dont find a solution.
Sent from my GT-I9000 using XDA App

adb remount as well
Trying to remap hard keys, adb remount along with push and pull do not work. Depending on whether im in shell or not I get no such file or directory or file not found errors. I can change into directory of each of the folders im trying to work with, and look at the file but I can't push it from my tools folder(locally) or pull it from the system folder. Every tutorial I see has adb remount command first, which fails every time.
Samsung Fascinate
Blackhole-build your own rom
(also tried on jt's latest rom, same issue

Crazy
I'm having the same issue here too. I'm trying to get a custom boot screen on my rooted Samsung Infuse and I've tried every way I can think of and it wont take. Clockworkmod says successfully installed, but its not. Soon as I reboot I see the At&T stock boot. I've fixed all of my permissions and still no luck.
So I saw a solution to do it via adb by typing "adb remount" and I get the same thing u guys are getting. I've got a headache now. Done all I could, even typing "shell", "su", that all goes well then when I tried to push it "adb push bootanimation.zip system/media" I get adb: not found. Smh, is it a device issue?

i think ive got the solution
flash a new kernel..................................worked for me................

[Q] rooting new thread as I can't get answers and nothing makes sense, vrgh

I tried to follow these instructions, first it says ''Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).'' but when you go to the video it says '' Be sure to install ADB on your computer first!''
I have installed it but thats confusing information to begin with right there.
I have installed ADB and downloaded the files, putting the SDK file in C: drive, now it gets confusing....
I have run the Qemu program and it hangs at ''Daemon Started Successfully''
Nothing happens from this point onwards, I've looked around and asked but receive no answers, so I do more googling and find this - http://www.androidpolice.com/2012/09/17/amazon-kindle-fire-hd-7-already-rooted-heres-how-to-do-it/ ...........
this seems ok instructions but I have no clue what to do with these instructions!
''After you download the file, extract the contents and pull SU from /system/bin/ and SuperUser.apk from /system/app/ and put them in the directory you'll be working from''
!! DIRECTORY??? COME AGAIN!???
After that, execute the following commands:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
adb shell
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local.prop
exit
adb reboot
adb install Superuser.apk
!! VERY GOOD BUT HOW AND WHERE !!
Anybody care to translate these confusing conflicting nonsense instructions please?
Yes I'm well aware I will be wrong with some of my statements.
I need and idiots guide as it were.
Please reply with helpful comments guys, cheers
I should mention I tried following the video instructions but there is a great big picture of a KFHD in the middle of the screen and the quality is so bad you can not make out what is being type in the command prompt.....

Revkyle.com did a video with step by step instructions, that is what I used and worked fine.

mate
Chelle01 said:
Revkyle.com did a video with step by step instructions, that is what I used and worked fine.
Click to expand...
Click to collapse
there is no such site as Revkyle,com, and the youtube version makes no mention of rooting anything.
Can you post a link or be more precise please?
I'm finding this very stressful, thank you for the reply
Please tell me you don't mean this http://www.youtube.com/watch?feature=player_embedded&v=CYDBoTtdvcE
I can't see what he's typing, I'm a real noob, I have no clue what he is talking about from 2:20(ish) onwards, I do have ADB in the device manager, from there he might aswell be speaking martian, seeing as you have followed his instructions ( I don't know how you managed that) would you translate what he's saying for me please?

Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaagggggggggggghhhhhhh hhhhhhhhhhhhhhhhhhhhhhhhhh
Why cant i get help on this site!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

First CALM DOWN. We are all here to help each other, but we are not on here 24-7 we have other things to take care of. This is the website
http://www.reverendkyle.com/index.php?start=4. You use command prompt on your computer to do this. Directory is a place on your computer like c drive, you have to know where you put it to be able to make a path to it. Do you understand this? Sorry I'm trying to see what you know and how I can help you.

I got there in the end cheers

HELP! Su was in the folder but device not found!

I followed the instructions exactly but now device not found and I folowed the video exactly, su is in the folder (((
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
abd reboot
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
The adverts are back on the screen, what do I do please
Its nearly 2am in the morning

device is found now, what point do I pick up the command prompts up at?
please

Rovers82517 said:
please
Click to expand...
Click to collapse
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/

Rovers82517 said:
ah, man, I'm seriously lost, it fails everytime with these 2 commands,
adb shell mount -o remount,rw /system
adb push su /system/xbin/su
the su file is definately in the platform-tools folder :/
Click to expand...
Click to collapse
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely

onemeila said:
If your drivers are installed correctly now, use the root tool in development section. Then there are no mistakes. If you insist on the manual method though, you need to put the su file and superuser.apk in your folder titled carol and Start over completely
Click to expand...
Click to collapse
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude

Rovers82517 said:
the files are in there, I've checked and double checked.
when I can get it to see the device again the command prompt has a # instead of a $
I can't afford to brick this thing, I don't know of any other methods, can you tell me what you mean or post the link?
It's gone 2am now I could do with even a little sleep tonight
Thank you for replying
ah, my bad, I know what tool you mean cheers dude
Click to expand...
Click to collapse
No problem, sometimes it just takes a lot of banging your head.

still no luck
I've copied both files to 'carol' as well as platform-tools, what have I done wrong?

Fixed but I'm not sure how
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps

Rovers82517 said:
It repeatedly said file not found but in the end I decided to skip to step 4 on QemuRoot and it had worked lol very strange
Think I'll leave it a while before I attempt custom roms lol
Thanks for your help peeps
Click to expand...
Click to collapse
From my personal experience is best way how to root kindle fire by qemu (development part of forum) its quite easy... to solve problem if your device isn't found I had to create folder .android in my “documents“ like it is when you will instantly sdk
You have to create it via command line... mkdir .android
Create there required file how it is described in qemu thread. Reinstal kindle adb drivers and try qemu once more.. that worked for me like a charm.
Tomorrow when I will be on PC I will post step by step guide
Kerbik

[SOLVED][Q] 4.4.3 after restart restores previous values

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

[ADT-1] Casting

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.