Database Users

I897UCJJ4 - More Froyo!

Ok, first off, the email app is busted, fixed is included in the rooting instructions. MobileAP is now MIA. No icons on the launcher at boot. There is also a sweet new app that is like DeskClock. Its snappy.
Firmware: (Flash to anything JI6 First if you are not on it already)
http://www.ponack.net/designgears/I897_JJ4_JF6_JJ4_JJ4_UC_ATT_designgears.zip
Custom kernel:
http://forum.xda-developers.com/showthread.php?t=825025
Root Kit & Email fix:
http://www.ponack.net/designgears/jj4_root_emailfix.zip
Enjoy and thank Chainfire for hooking us up!
This is NOT available on samfirmware.com
HowTo root:
Downlad & extract jj4_root_emailfix.zip
Browse to contents from cmd/terminal
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb shell
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
mount -o rw,remount /dev/block/stl9 /system
/system/bin/busybox --install -s /system/xbin
busybox chmod -R 0755 /system/xbin
reboot now
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thank you sir

Thanks DG and Chainfire!! I was wondering when we would get another leak.
DG, when you releasing a new beta? I love version 9.1.3
Also, do we know of any other change logs from J16? (I'm sure we will find them out soon enough)

Thanks for this!! I'll try when i fix mine!

Gr8Danes said:
Thanks DG and Chainfire!! I was wondering when we would get another leak.
DG, when you releasing a new beta? I love version 9.1.3
Also, do we know of any other change logs from J16? (I'm sure we will find them out soon enough)
Click to expand...
Click to collapse
Seems mostly like bug fixes, more stripping out features for AT&T, this build is smoother, but seems hacked together in comparison to how clean JI6 was.

designgears said:
Seems mostly like bug fixes, more stripping out features for AT&T, this build is smoother, but seems hacked together in comparison to how clean JI6 was.
Click to expand...
Click to collapse
I think I will leave it to your hands to give us the best of both worlds.
Thanks DG!

let me fill this out so it's at least 10 characters

Kaik541 said:
oh, and since I've never been ungrateful of your stuff and I'm not one to be rude when something drops in my lap, let me say thank you. I'd enjoy it a bit more though if you could stop trying to stir up drama so much about something as trivial as a phone, haha
Click to expand...
Click to collapse
Kaik541, trying to turn me into the bad guy while you talk trash me and anything I do, is, well, childish...
You are done. (as in I am bringing in a mod to deal with your crap)

Not going to waist my time flashing this, the last one had some pretty nasty bugs, it was stable yes but a bit buggy, besides this one seems to be missing stuff, il stick with JPM until official comes around.
btw:kaik541 just add him to your ignore list, thats what i did last time >;D

thanks for the release, what method is this one supposed to be flashed with? odin or?

Thank you as always DG! Any changes to GPS? Will the next Cog be built with this?

so will this be used for future builds or will we be sticking with the previous beta release?

cant get anything to go am now doing a master clear
HI DG,
I am trying this out but I cant get very far, I was able to root and sideload with superoneclick, everything wants to FC, phone, messaging, yp mobile, ect... so I am reflashing with repartition selected (this was a REAL Bad idea) cant mount dbdata ectect, now flashing back to stock. THanks cant wait till COG X

huzzah JJ4!

InsaneJester17 said:
Thank you as always DG! Any changes to GPS? Will the next Cog be built with this?
Click to expand...
Click to collapse
GPS is the same, as for building Cognition on this, not sure... building it right now to see how it runs.
buddy17 said:
so will this be used for future builds or will we be sticking with the previous beta release?
Click to expand...
Click to collapse
not sure yet
mattbeau said:
HI DG,
I am trying this out but I cant get very far, I was able to root and sideload with superoneclick, everything wants to FC, phone, messaging, yp mobile, ect... so I am reflashing with repartition selected (this was a REAL Bad idea) cant mount dbdata ectect, now flashing back to stock. THanks cant wait till COG X
Click to expand...
Click to collapse
Ya, one-click root may not work with this... That is why I posted the tried and true manual way...

thanks DG!
A revolutionary leader LOL

ok no prob, i think I will try again later.
Thanks

@designgears: This should work with your CogKernel right?
Have you released your kernel as a separate ODIN flashable tar?

designgears said:
Downlad & extract jj4_root_emailfix.zip
Browse to contents from cmd/terminal
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb push EmailProvider.db /data/data/com.android.email/databases/EmailProvider.db
adb shell
mount -o rw,remount /dev/block/stl9 /system
/system/bin/busybox --install -s /system/xbin
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
chmod 4755 /data/data/com.android.email/databases/EmailProvider.db
busybox chmod -R 0755 /system/xbin
reboot
Click to expand...
Click to collapse
I had to change up the steps a little but was able to get everything to work:
Downlad & extract jj4_root_emailfix.zip
Browse to contents from cmd/terminal
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell
cd /data/local/tmp
chmod 0755 rageagainstthecage-arm5.bin
./rageagainstthecage-arm5.bin
(wait for you to get kicked from adb)
adb shell
mount -o rw,remount /dev/block/stl9 /system
exit
adb push su /system/bin/su
adb push busybox /system/bin/busybox
adb push sqlite3 /system/bin/sqlite3
adb push superuser.apk /system/app/superuser.apk
adb push EmailProvider.db /sdcard/EmailProvider.db
adb shell
mount -o rw,remount /dev/block/stl9 /system
cd /system/bin
chmod 4755 su
chmod 4755 busybox
chmod 4755 sqlite3
/system/bin/busybox --install -s /system/xbin
cp /sdcard/EmailProvider.db /data/data/com.android.email/databases/EmailProvider.db
chmod 4755 /data/data/com.android.email/databases/EmailProvider.db
busybox chmod -R 0755 /system/xbin
reboot

phone fc?
went back to jf6 OC... then put tar in pda slot and flashed w/o repartition.
As soon as it boots up, I get FC on phone... continuously..
am I doing something wrong?

Samsung Vibrant 4G is BLOATED!

I want to remove all the unwanted bull so bad!!! Off the back it comes with so much unnecessary apps from T-Mobile.
I have less then 200MB left!
I can't root because the confirmed root that's out is for Windows. (SuperOneClick)

HeavyComponent said:
I want to remove all the unwanted bull so bad!!! Off the back it comes with so much unnecessary apps from T-Mobile.
I have less then 200MB left!
I can't root because the confirmed root that's out is for Windows. (SuperOneClick)
Click to expand...
Click to collapse
So run a windows virtual environment... or you can always just do rage manually.
And of course its bloated. Every phone comes that way these days. Just gotta root my friend.

Ok this is my first Vibrant so what's Rage and is it perm root? I can't find anything that says Rage on the development page.

I also caught it 190MB at corp store.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It may be defective because some members from hofo said it's 800MB left.
http://www.howardforums.com/showthread.php/1704050-what-to-get-nexus-s-vibrant-galaxy

omg is it sick or what though?? speedtest.net app!! I want to see this bad boy in action!
I'm a huge internet user on my phone btw hahaha

You'll find the Vibrant and SGS4G to be very easy to root compared to MTG4. Its always perm.
EDIT: You need to rename SU-V2 to SU. no extension.
Use the files you extract from that superoneclick to execute this.
- Extract the files to the Tools folder of your Android SDK folder
- Place your phone into Debugging Mode (Settings, Applications, Development, check USB Debugging)
- Open the command prompt (Start > Run > cmd > Press Enter)
- cd c:/wherever-your-sdk-tools-folder (Example: C:\Android-SDK-Windows\Tools)
- Then type adb devices to verify that the phone is connected. If it is connected, you will see the device serial number.
- Type in the below commands:
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage /data/local/tmp/rageagainstthecage
- adb shell From here, you will see a $ instead of C:/
- cd data/local/tmp The output will return the same command as inputted
- chmod 0755 rageagainstthecage
- ./rageagainstthecage At this point, let it run and DO NOT TOUCH ANYTHING until it returns to the DOS Prompt (C:\Android-SDK-Windows\Tools). This will take up to two minutes or so.
- adb shell This time it will show a # sign as opposed to the $ sign before
- All of the below commands will again return the same output as the input
- mount -o rw,remount -t yaffs2 /dev/block/stl9 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/xbin/su
- cp /sdcard/busybox /system/xbin/busybox
- chmod 4755 /system/xbin/su
- chmod 4755 /system/xbin/busybox
- mount -o ro,remount -t yaffs2 /dev/block/stl9 /system
- Exit x2 to close out of adb shell and the command prompt
I THINK that should work. Use at your own risk.

aloneinshadow said:
Use the files you extract from that superoneclick to execute this.
- Extract the files to the Tools folder of your Android SDK folder
- Place your phone into Debugging Mode (Settings, Applications, Development, check USB Debugging)
- Open the command prompt (Start > Run > cmd > Press Enter)
- cd c:/wherever-your-sdk-tools-folder (Example: C:\Android-SDK-Windows\Tools)
- Then type adb devices to verify that the phone is connected. If it is connected, you will see the device serial number.
- Type in the below commands:
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage /data/local/tmp/rageagainstthecage
- adb shell From here, you will see a $ instead of C:/
- cd data/local/tmp The output will return the same command as inputted
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage At this point, let it run and DO NOT TOUCH ANYTHING until it returns to the DOS Prompt (C:\Android-SDK-Windows\Tools). This will take up to two minutes or so.
- adb shell This time it will show a # sign as opposed to the $ sign before
- All of the below commands will again return the same output as the input
- mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
- Exit x2 to close out of adb shell and the command prompt
I THINK that should work. Use at your own risk.
Click to expand...
Click to collapse
Thanks! And this is temp root? If so lets say I rebooted the device how would I get the root back?

HeavyComponent said:
Thanks! And this is temp root? If so lets say I rebooted the device how would I get the root back?
Click to expand...
Click to collapse
All roots on this phone are perm roots. No need for temp.

Oh ok cool.
You mind giving me the link where you got your info from? You did say "THINK" it will work. Lol

Um... Google? To be honest I didn't get it from any one page in perticular, just pieced it together. I've actually done it before, I just can't remember this one detail:
- mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
I can't remember if that one line is right or not. The rest I know works.
EDIT: I just tested this line on my phone and it ran fine. I'd try it and let me know if it works.

Ok good enough or me, I will give it a try.
EDIT: By the way, I'm on a Mac.

HeavyComponent said:
Ok good enough or me, I will give it a try.
EDIT: By the way, I'm on a Mac.
Click to expand...
Click to collapse
Yea I kinda figured. Nothing we can do about that now I'm afraid, I only hope you've learned from your mistakes.

What mistakes? The process works just as if I was on Windows just instead of "adb" I type in "./adb". It should work, I'll give it a try.
One thing I wanted to mention was their is 2 versions of su in the SuperOneClick file. Does it matter which one I use? su-v1 and su-v2.

HeavyComponent said:
What mistakes? The process works just as if I was on Windows just instead of "adb" I type in "./adb". It should work, I'll give it a try.
One thing I wanted to mention was their is 2 versions of su in the SuperOneClick file. Does it matter which one I use? su-v1 and su-v2.
Click to expand...
Click to collapse
rename SU-V2 to SU.
And I was referring to your mistake to buy a Mac.

aloneinshadow said:
So run a windows virtual environment... or you can always just do rage manually.
And of course its bloated. Every phone comes that way these days. Just gotta root my friend.
Click to expand...
Click to collapse
iOS and WP7 Devices aren't, and neither are T-Mobile's newer Blackberries. The excessive bloat seems to be a big thing on Symbian, Android, and Windows Mobile.

aloneinshadow said:
rename SU-V2 to SU.
And I was referring to your mistake to buy a Mac.
Click to expand...
Click to collapse
- adb shell This time it will show a # sign as opposed to the $ sign before
Never turned into "#" still shows "$". I did everything and it all went well until that part.

N8ter said:
iOS and WP7 Devices aren't, and neither are T-Mobile's newer Blackberries. The excessive bloat seems to be a big thing on Symbian, Android, and Windows Mobile.
Click to expand...
Click to collapse
My bad. All phones with operating systems that are worth at least two squirts of piss, are bloated from the start.

HeavyComponent said:
- adb shell This time it will show a # sign as opposed to the $ sign before
Never turned into "#" still shows "$". I did everything and it all went well until that part.
Click to expand...
Click to collapse
Hmmm... not sure why it didn't work. I'm half tempted to just tell you to download Wine for mac and run superoneclick, but you've come this far. I'd just keep going with the code and see what happens. Can't really screw it up, it just won't work.
EDIT: Looks like I had this wrong. I think it should be:
- mount -o rw,remount -t yaffs2 /dev/block/stl9 /system
Based it off of this run by superoneclick:
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
103 KB/s (5392 bytes in 0.051s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1264 KB/s (1062992 bytes in 0.821s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/stl9
OK
Reading OS Version properties...
Version: 2.2.1
OK
Remounting system with read-write access...
OK
Pushing su-v2...
449 KB/s (26264 bytes in 0.057s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1323 KB/s (196521 bytes in 0.145s)
OK
Remounting system with read-only access...
mount: mounting /dev/block/stl9 on /system failed: Device or resource busy
OK
Remounting system with read-only access...
OK

aloneinshadow said:
Hmmm... not sure why it didn't work. I'm half tempted to just tell you to download Wine for mac and run superoneclick, but you've come this far. I'd just keep going with the code and see what happens. Can't really screw it up, it just won't work.
Click to expand...
Click to collapse
Ok I tried the command over right before that step and now it's working.
I'm assuming "cp" is copy and paste? How do I do that? Because I typed in "cp" thinking it's part of the command, but it says "cp: not found".

Try "Busybox cp" I think you also can use dd: "dd if=/sdcard/su of=/system/xbin/su" instead of cp.

Why 'adb remount' failed on a Rooted neuxs one

Hi,
I have rooted my Nexus one. I can do "'adb shell and then 'su' under the shell"
But on my MacOS Desktop, when I execute 'adb remount', it still said
$ adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
Can anyone please help me resolve this?
Thank you.

[size=+4]DO *NOT* POST QUESTIONS IN THIS FORUM - only tips/info/etc.[/size]
Right at the top. Why does this have to be repeated on a daily basis?

Can you please move my thread to the right forum? I can't find a way to do it.

Anyhow, to answer you question... you "adb remount" is disabled in production releases... just rooting does not allow this.
You need a modified boot image where ro.secure=0 in default.props, instead of ro.secure=1. The ro.secure flag in the boot image indicates whether the root filesystem can be remounted as read/write... 0 indicated it can be... 1 indicated it cannot be.
If ro.secure=0, this is referred to as insecure boot.
Most custom ROMs have this by default... some rooted stock ROMs do not have this...

Will the Modified GRI40 (2.3.3 Gingerbread) ROM from this
http:// forum.xda-developers.com/showthread.php?t=968396
Does what I need? Thanks.

Or you can also use these commands to mount and unmount the system partition as writable:
Code:
mount -o remount,rw /dev/block/mtdblock3 /system
mount -o remount,ro /dev/block/mtdblock3 /system

Thank you. That seems to be an easier solution for me.
But after I did
$ adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I go to another shell and i did
adb push sqlite3 /system
failed to copy 'sqlite3' to '/system/sqlite3': Read-only file system
$ adb push sqlite3 /system/bin
failed to copy 'sqlite3' to '/system/bin/sqlite3': Permission denied
Click to expand...
Click to collapse
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.

hap497 said:
Thank you. That seems to be an easier solution for me.
But after I did
I go to another shell and i did
It still does not let me push 'sqlite3' to /system or /system/bin
That is what I need.
Thank you for any more pointers.
Click to expand...
Click to collapse
Don't try to combine adb commands with shell commands.
Copy/move/push the file to your sdcard first.
Then open a root shell, mount it as rw, then copy the file from your sdcard to the directory you want.

Thanks. but I get 'failed on '/sdcard/sqlite3' - Cross-device link'
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# mv /sdcard/sqlite3 /system/
failed on '/sdcard/sqlite3' - Cross-device link
# ls -l /sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
and i have tried:
# mv /mnt/sdcard/sqlite3 /system/bin/
failed on '/mnt/sdcard/sqlite3' - Cross-device link
# ls -l /mnt/sdcard/sqlite3
----rwxr-x system sdcard_rw 24120 2010-10-16 22:04 sqlite3
Click to expand...
Click to collapse
I get the 'sqlite3' from SuperOneClickv1.7-ShortFuse.zip.

Wholly crap, don't use the mv command! Bad idea!!! mv does not move the data, it moves the hardlink to the data! Thank your lucky stars mv wouldn't let you do it.
Use cp instead. cp will actually copy the data to where you're going.

Thank you. But I don't have 'cp' in my adb shell.
# cp
cp: not found
# /system/bin/cp
/system/bin/cp: not found
Click to expand...
Click to collapse
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin

How do you have mv but not cp? Do you not have BusyBox installed?

No. I just need to search 'BusyBox' on Android market and install it? That is?

hap497 said:
Thank you. But I don't have 'cp' in my adb shell.
From here:
http://android-tricks.blogspot.com/2009/02/cp-on-android.html
I use 'cat' command to move to /system/bin
Click to expand...
Click to collapse
The cat command will work fine, no busybox needed: cat source_file > dest_file

efrant said:
The cat command will work fine, no busybox needed: cat source_file > dest_file
Click to expand...
Click to collapse
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
OP, Yes, BusyBox can be installed from the market.

GldRush98 said:
Woah there partner. Cat shouldn't be used on binary files, only ascii files. While it might work fine, it is not the recommended practice and really should not be done.
Click to expand...
Click to collapse
Really? I was unaware of that. It worked every time I used it.

efrant said:
Really? I was unaware of that. It worked every time I used it.
Click to expand...
Click to collapse
On standard Unix/Linux/etc. systems, cat works fine for binary files. It's only under DOS that cat or type shouldn't be used for binaries.

back in my ADB days.. itd say remount failed or w.e but i could still access my phone..
but i dont know.. ever since i switched to linux i stopped using ADB.. hahah

[solved]adb remount

Hello,
Has anyone gotten adb remount to work? I always get
remount failed: operation not permitted
Click to expand...
Click to collapse
I've also tried
Code:
mount -o remount,rw /dev/block/mmcblk0p4 /system
both from adb and in the terminal emulator but I get the same response
Trying to push anything to /system just results in
failed to copy '<file>' to '/system/<path>': Read-only file system
Click to expand...
Click to collapse
Any ideas?

Root?
You are rooted right? and didn't forget to "su" before those shell commands? because the shell command works fine for me, I remount system and changed the fonts

apparently I was just making it more complicated than it needs to be. You don't need to specify the mount point. Just use
mount -o remount,rw /system

[SOLVED] /system cannot be mounted

SOLVED! Thanks to Alex240188
Alex240188 said:
here is what i have done and just tested as working
If you are using Supersu binaries ignore this step
***PHONE***
Apps > Settings > Developer Options > Root Access > Apps and ADB
***PC Command Prompt***
adb shell
su
***PHONE***
confirm SU popup on phone
*** PC Command Prompt***
Ctrl + C (to exit shell)
adb root
Code:
restarting adbd as root
adb shell
mount -o remount,rw /system
mount
look for this line (it will tell you if you have failed or successfully remounted)
Failed
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]ro[/u][/b],seclabel,relatime,data=ordered 0 0
Success
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]rw[/u][/b],seclabel,relatime,data=ordered 0 0
CTRL + C to exit from shell
adb push "yourfile.ext" /system/"whereyouwanttoputit"/
in my case
adb push test.txt /system/app/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after this initial setup and working point, all you should have to do to future mount as RW in adb is the following 2 commands
adb root
adb shell mount -o remount,rw /system
then when your finished
adb shell mount -o remount,ro /system
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
I have a problem making my windows 8 PC write on the /system partition of the nexus 4.
I've tried all of these:
Code:
***adb remount.... FAIL
***adb shell (enter)
mount (enter)
(saw where the system partition is located)
mount -o rw,remount /dev/block/mmcblk0p21 /system....FAIL
***mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system... FAIL
***adb root... FAIL
***called my mother and told her that she wasn't lying to me
The mount -o.... commands do make the system writable, but only on phone and not via PC.
"mount" gives me that /system is rw, but i still can't push files to /system so that means i can only modify /system from the phone itself (or from adb shell), so when i enter the shell, /system is mounted, but when i exit the shell, /system isn't mounted
What i want to do is to make "adb push (bla) /system" work, without going to recovery, nor shell.
I can give details if needed.
Thank you.

Try putting the phone into recovery mode first. Then run:
Code:
adb remount
adb push blahblah.bla /system/

Chromium_ said:
Try putting the phone into recovery mode first. Then run:
Code:
adb remount
adb push blahblah.bla /system/
Click to expand...
Click to collapse
thanks for reminding me... i've added in OP that i don't want to be in recovery, i want to do it while the phone is booted.
Sent from my Nexus 4

so anyone?

Riro Zizo said:
so anyone?
Click to expand...
Click to collapse
here is what i have done and just tested as working
If you are using Supersu binaries ignore this step
***PHONE***
Apps > Settings > Developer Options > Root Access > Apps and ADB
***PC Command Prompt***
adb shell
su
***PHONE***
confirm SU popup on phone
*** PC Command Prompt***
Ctrl + C (to exit shell)
adb root
Code:
restarting adbd as root
adb shell
mount -o remount,rw /system
mount
look for this line (it will tell you if you have failed or successfully remounted)
Failed
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]ro[/u][/b],seclabel,relatime,data=ordered 0 0
Success
Code:
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 [b][u]rw[/u][/b],seclabel,relatime,data=ordered 0 0
CTRL + C to exit from shell
adb push "yourfile.ext" /system/"whereyouwanttoputit"/
in my case
adb push test.txt /system/app/
after this initial setup and working point, all you should have to do in the future to mount as RW is the following 2 commands
adb root
adb shell mount -o remount,rw /system
then you can
adb push blah.apk /system/app/
adb push bootanimation.zip /system/media/
then when your finished
adb shell mount -o remount,ro /system

Thanks a TON! I wouldn't have lived without doing that! I should put that in OP now...