Hello everyone.
First off all i hope this post is in the right section.
Let me get this out off the way first:
Im not good at english, and im not good at cmd files and so on.
But! i can succecsfully root my phone and get the # in cmd.
The reason im rooting is becouse i want the market patch so i can see all apps.
Here is my questions:
1. Whenever i try to adb push vending......
It says "the file is read-only" i cheked its not read only
So how do i fix that?
2. In the guide to root the phone he says:
"You can do anything then! Look at /system, /data, etc etc. You're broken free, my friend"
Where can i see the /system and so on? he says look at, but where can i look at it? how can i like acces the folders?.
So on the easy way, i search a way to install the market patch.
Thank you everyone
Bump, i really hope someone will help
Anyone? please?
When you have root, you need to mount r/w partition:
- adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko (if you haven't did it before)
- adb shell
$
- su
#
- # insmod /data/local/bin/tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
And now you have mounted in r/w, so:
- adb push Vending-Tattoo-patched.apk /system/app/Vending.apk
p.s. ah...you can access system folders with Root Explore (it needs root)
I never had to mount anything. I did the latest root hack in the sticky at top of forum and then i installed the full market apk. Worked a treat.
ephumuris said:
I never had to mount anything. I did the latest root hack in the sticky at top of forum and then i installed the full market apk. Worked a treat.
Click to expand...
Click to collapse
I'm happy for you, but someone like me (and mafiapanda in that case) did old manual root.
Ty
Thank you im going to try it out now, thanks
Okay, after i get the
#
then i did what you said.
i get it again
# adb push vending.....
"adb not found"
Ehhmm can you help me there?
Everyting was succesfull except pushing it.
mafiapanda said:
Okay, after i get the
#
then i did what you said.
i get it again
# adb push vending.....
"adb not found"
Ehhmm can you help me there?
Everyting was succesfull except pushing it.
Click to expand...
Click to collapse
Of course, it's normal
You have to write "adb push vending....." non in "adb shell" but in "adb" (open another cmd and as for example "cd c:\android\tools", then "adb push" etc.)
Stupid me
Am so thankfull to you guys, you really helped me alot Thank you really much!
Okay, now i get "permisson denied" when im trying to "adb push vending..."
I opened a new CMD and typed cd c android tools, i just get permission denied.
Can anyone help me about that? Thank you guys so far
mafiapanda said:
Okay, now i get "permisson denied" when im trying to "adb push vending..."
I opened a new CMD and typed cd c android tools, i just get permission denied.
Can anyone help me about that? Thank you guys so far
Click to expand...
Click to collapse
Have you opened new cmd closing the other or not?
You don't have to close the first cmd.
Try. If it doesn't work, probably there are some problems with the root procedure, in that case try that solution: Root in 1 click. It contains: root, boot.img, market (also recovery if you choose it).
Yea, i have tryed root in 1 click, but does it really include market?
Root in 1 click gives me the same error ?
Okay maybe this is alot to ask for but is there anyone out there that can make a video of it all from rooting to push market. i would be so thankfull.
And its not just for me, it would help alot out there. im so thank full
Damn, now it says "read only file system" again.
Can anyone post a detalied how-to Thank you really much.
Im going to bed now, cheking this post tommorow.
Btw, i would love to have talk with someone on msn, steam or mail.
Am from denmark if it matters.
THANK YOU
mafiapanda said:
Damn, now it says "read only file system" again.
THANK YOU
Click to expand...
Click to collapse
You have to repeate that every time you reboot:
- adb shell
$
- su
#
- # insmod /data/local/bin/tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
And then you have mounted in r/w:
- adb push Vending-Tattoo-patched.apk /system/app/Vending.apk
(one time)
Okay I Will try that when I get home. Can I use the 2. 1 market I mean so I can have all the 500 apps or is it only for 2 1 firmware modded phones?
mafiapanda said:
Okay I Will try that when I get home. Can I use the 2. 1 market I mean so I can have all the 500 apps or is it only for 2 1 firmware modded phones?
Click to expand...
Click to collapse
Use v2 patch, not 2.1. It has worked for me.
YES! I cant ****ing believe it!! I succed !! im am so happy
Thank you very very very much 1000 times.
YES MAN im so happy now.
Maybe i should at a guide to this forum? i dont know if anyone needs it but..
Okay last last question, when i search for "video" i see 300 results which am very happy for but, on the picture he had 500 how can i get 500 ?
mafiapanda said:
YES! I cant ****ing believe it!! I succed !! im am so happy
Thank you very very very much 1000 times.
YES MAN im so happy now.
Maybe i should at a guide to this forum? i dont know if anyone needs it but..
Okay last last question, when i search for "video" i see 300 results which am very happy for but, on the picture he had 500 how can i get 500 ?
Click to expand...
Click to collapse
You're welcome
300 rather than 500? I'll try..
Related
I have busybox 1.6 on my captivate i see on www.busybox.net 1.17.3 is out. I have downloaded it from the site and its a tar file with a folder with a whole bunch of folders and files. How do you install this?
Are you familiar with the phrase, "if it isn't broken, don't fix it?"
I advise you to heed its warning.
But if you must proceed, a quick google search for "how to install busybox manually" brings up this very good result: http://www.droidforums.net/forum/droid-2-hacks/82573-busybox-manual-install-how-guide.html
Edit: By the way, love the avatar. Great album.
Yes i understand if its not broke don't try to fix it but i'm a OCD updater! Would there be any advantages of updating it? P.S. I saw Megadeth and Slayer a month ago they rocked!
Only advantages I can see are having a couple more bug fixes and maybe 4-5 new commands built in.
Download Busybox-1.17.2 HERE
Extract busybox to your SD Card
Make sure you are in PC Mode and Debugging is enabled in Applications options
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/busybox /system/xbin/
cd system/xbin
busybox --install /system/xbin/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
You can also use Root Explorer or whatever file browser you may use to copy busybox to your system/xbin folder. Some people use system/bin but I prefer xbin...just a habbit.
Click to expand...
Click to collapse
Ya, I read that and got really scared.
What is PC mode and where do you type these commands? (Vista user)
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Cruton502 said:
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
miztaken1312 said:
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
Click to expand...
Click to collapse
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Cruton502 said:
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Click to expand...
Click to collapse
I think you're seriously confused. The Captivate isn't a NAND locked phone. Generally when you root, busybox is installed. (I think. At least it always was for me.) You could also try installing Titanium Backup and have that install busybox for you.
Here is a simple fix for the market issues between stock and 1.5.2 - it assumes you have flashed the 1.5.2 sbf, and also re-rooted your device.
adb shell (or open a terminal on your phone)
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reboot
I have been running with this most of the day with no issues noticed..
-G
how funny i JUST discovered this earlier today was going to post it on the forums. great minds think alike . my n64oid is back!
Funny, I just told someone else how to do this this morning. I'm surprised this hasn't come up sooner. I've been using this since the sbf has been released with no problems, guess I should have posted this solution sooner my b :-(
Sent from my MB860 using Tapatalk
Anyway to do this through terminal?
Sent from my MB860 using XDA App
Same commands without the first adb shell..
How do I enable RW to system?
Trying to do the market fix script but get RO error on write to /system.
from a command prompt in windows/linux:
you: adb shell
reply: $
you: su
(accept prompt on device, make sure it's unlocked and @ homescreen or it might not pop up)
reply: #
you: mount -o rw,remount /dev/block/mmcblk0p12 /system
reply: (copies it back)
you: sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reply:
you: reboot
What are the "market issues?"
Da_G said:
from a command prompt in windows/linux:
you: adb shell
reply: $
you: su
(accept prompt on device, make sure it's unlocked and @ homescreen or it might not pop up)
reply: #
you: mount -o rw,remount /dev/block/mmcblk0p12 /system
reply: (copies it back)
you: sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
reply:
you: reboot
Click to expand...
Click to collapse
Thanks,
I made some assumptions that people would know the prerequisites
I edited the original.
-G
relaxed said:
What are the "market issues?"
Click to expand...
Click to collapse
Well, I had several apps I paid for that I could not load. I had the same issues with my G-Tablet until I loaded my N1 build id in the same file a while back..
-G
Well I did it with the first method and it works fine except the market doesn't update to the new market.
ghost_o said:
Thanks,
I made some assumptions that people would know the prerequisites
I edited the original.
-G
Click to expand...
Click to collapse
Sent from my MB860 using Tapatalk
Fixter said:
Well I did it with the first method and it works fine except the market doesn't update to the new market.
Click to expand...
Click to collapse
First method?
The sed command is the only command I have posted.. You could use 'vi' directly on the device as well.. My market updated to the new version just fine after I made the change. (albeit I used vi on the device through adb shell). I just posted the sed string for people not familiar with unix, or who might want to script it..
ghost_o said:
First method?
The sed command is the only command I have posted.. You could use 'vi' directly on the device as well.. My market updated to the new version just fine after I made the change. (albeit I used vi on the device through adb shell). I just posted the sed string for people not familiar with unix, or who might want to script it..
Click to expand...
Click to collapse
I meant to say the first method where you only posted
Adb shell
su
sed
reboot.
Nothing about remounting, like what Da_G posted. Might have something to do with it?
Fixter said:
I meant to say the first method where you only posted
Adb shell
su
sed
reboot.
Nothing about remounting, like what Da_G posted. Might have something to do with it?
Click to expand...
Click to collapse
Ahhh, you must have already run something that re-mounted it rw for you. It would have failed otherwise... You can always try to put it back, and let the market update, and then change it again to get the apps back. I seriously doubt that is what is keeping your market from updating though.
ghost_o said:
Ahhh, you must have already run something that re-mounted it rw for you. It would have failed otherwise... You can always try to put it back, and let the market update, and then change it again to get the apps back. I seriously doubt that is what is keeping your market from updating though.
Click to expand...
Click to collapse
Thats exactly what I'm thinking. That doesn't have to do anything with the Market updating... Stupid market... -kicks-
Fixter said:
Thats exactly what I'm thinking. That doesn't have to do anything with the Market updating... Stupid market... -kicks-
Click to expand...
Click to collapse
should be able to reverse by switching up this part:
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
to:
sed -i 's!OLYFR_U4_1.2.6/1296900353!OLYFR_U4_1.5.2/1298398352!' /system/build.prop
then have the market update without a problem and then reapply the fix, though I'm sure you thought of this already XD
Djazin said:
should be able to reverse by switching up this part:
sed -i 's!OLYFR_U4_1.5.2/1298398352!OLYFR_U4_1.2.6/1296900353!' /system/build.prop
to:
sed -i 's!OLYFR_U4_1.2.6/1296900353!OLYFR_U4_1.5.2/1298398352!' /system/build.prop
then have the market update without a problem and then reapply the fix, though I'm sure you thought of this already XD
Click to expand...
Click to collapse
Yeah I tried that with no success... I wonder if it was the Gingerblur.
Works great. I was wondering where some of my apps had ran off to!
sed: write error
Hey, I was wondering if anyone here could help me.
I've reflashed from GingerBLUR 6.5, and can't seem to apply the market fix. I keep getting a write error when I apply the sed command.
You have to be rooted, and remount /system as read/write prior. The mount command right before the serd command is needed. Also, make sure your "su" command is successful. If not, the rest will not work..
Hi,
I get through this with my eye's closed but when I have to type in the chmod line,and hit enter, it says, "unable to chmod : / Read-Only file system / I've asked this on many different forms, and researched it and tried a lot of code to fix it, none of witch worked, so now I'm just asking strait out if anyone knows how I can fix this, It's done this on 2 separate computers so It's doubtful that it's a PC problem.
Thanks for reading this and perhaps helping me, I'm about to rip my hair out, lol,
Kn0t
Wait what?
So it's rooted tab yeah and your? Terminal or abd? Into the system. So you have super user rights huh? And the system files are mounted as read/write? If you said yes to these questioned which I assume you will as it sounds like you are savvy with permissions and how android mounts its system files from the "eyes closed" part then its a new one on me, I have never heard of this problem?
Oh and what kernel you running? is it gingerbread or froyo?
Sent from my GT-P1000
Don't forget to grant superuser its permissions. Check if the app is asking for it. Perform adb with tab on, superuser will pop up.
I felt for that couple of times.
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
speldenaar said:
Don't forget to grant superuser its permissions. Check if the app is asking for it.
I felt for that couple of times.
Click to expand...
Click to collapse
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
And lastly I'm thinking this doesn't qualify to be in the development section bud .. its a little cause and general and should be in General section not Here.
Sorry but its out of control on these boards.... these threads shouldn't be in the development section unless you are developing something or are replying to a development thread about, well.... a development ... or finally, ahhhhh....ummm, bah... development... just had to say it one more time and couldn't get a third reason... I don't want to be harsh or you think I'm flaming you its just my 2 cents....
Sent from my GT-P1000
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
it's adb,, and I have super permissions, yes and it says it's a Read-only file system when I go to write my chmod. The "eye's closed" part of my post was just me being sarcastic about the amount of phones I've done this too and the amount of time I've done it with zero problems.. that's all.
Yup, I did that.. thanks a lot for the advice..!!
nobleskill said:
No having super user rights doesn't mean you can write or change system files per say.. you first need the system mounted read/write which as a super user you do have the rights to....
So yes su is important but I suspect the issue here is the way the system is mounted...
Sent from my GT-P1000
Click to expand...
Click to collapse
Yes I agree but I don't know how to fix it that way.. thanks for helping
Sorry man. It was supposed to be moved to Q and A some time ago and it just never happened. My fault, my mistake. sorry to all that this bothers, and thank you to all that are helping me out.
~k~
nobleskill said:
Anyway use root explorer navigate into //system/ and there will be a button on the top to mount the system read/write. Then long press your file and select the permissions you want. Hit the same. Button as before to remount as read only and your away..
Sent from my GT-P1000
Click to expand...
Click to collapse
Thanks a lot for this advice, I tried it and got a message that says, "System permissions cannot be changed because the file system is Read-only"
Thanks again, it was worth a try.
~K~
quick question....
When do I enter that into my command prompt? right before I try to chmod or right after????
thanks a lot
~K~
mchampeli said:
i have a SGH-T849..
i want to carrier unlock it.. also i couldn't find the dialer & the messaging application in the phone.. so wanted to know how to make voice calls & send messages in it??
Sorry for the bad English & for being a noob
Click to expand...
Click to collapse
I think you have to put on a new rom that does that. try http://theunlockr.com/2010/11/29/how-to-flash-a-custom-recovery-image-on-the-samsung-galaxy-tab/
good luck
~K~
GldRush98 said:
You're trying to write data to a partition mounted as read only.
To mount the system partition so you can write to it, simple issue this command:
mount -o remount,rw /dev/block/mtdblock3 /system
And of course to mount it back to read only again:
mount -o remount,ro /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Yea I tried that and it said "system permission cannot be changed becausethe file system is Read-Only" so I don' know. But I do really appriciate you trying to help me out.
knotrkr said:
I tried that. I tried it like this and this is what happened..
# mount -o remount,rw /dev/block/mtdblock3 /system
# chmod 755 / data/local/bin/flash_image
Unable to chmod /: Read-only file system
Did I do it wrong. Should I of put that code in a different spot?
either way thank you for trying to help me out..
~K~
Click to expand...
Click to collapse
Whoops, I thought the file you were chmod'ing was in the system partition.
The data partition is already mounted with read/write.
Your chmod command is incorrect... there is an extra space in there.
It should be:
chmod 755 /data/local/bin/flash_image
I don't think the data partition is mounted as read only (I could be wrong, but I didn't think it was)
Ok, so I haven't figured out the cord thing yet (phone won't connect to any computer using the stock cord, I can get it to show its charging...thats it!), so I am wondering if there is anyway to unroot without a computer? PLEASE HELP!!! I AM GETTING DESPERATE!!!
ajgates92 said:
Ok, so I haven't figured out the cord thing yet (phone won't connect to any computer using the stock cord, I can get it to show its charging...thats it!), so I am wondering if there is anyway to unroot without a computer? PLEASE HELP!!! I AM GETTING DESPERATE!!!
Click to expand...
Click to collapse
Open market and grab "terminal emulator", once you have it open it up and follow the steps as root (first thing you type into the terminal emulator is "su")
1./ remount /system to rw "busybox mount -o remount,rw /system
2./ erase root files "rm /system/xbin/su" "rm /system/bin/su" "rm /system/app/Superuser.apk" "rm /system/xbin/busybox"
3./ remount system ro and reboot "busybox mount -o remount,ro /system" "reboot"
these paths are for root w/zergs but they might be the same for Petes etc. This will clear all files and symlinks that were created when you rooted your device.
I am trying this now, thanks for the quick reply. Will let you know how it works!
Edit: Can you please put the exact code string I should enter into the Terminal? Thank you
Double Edit: I'm an idiot! I read your post wrong, I got it right this time and it worked!!! THANK YOU SO MUCH!!!!!
Droid 3 stock cables suck f(2 d3s and both cables died).. be sure to also check with no stovk cable...
Enviado desde mi DROID3 usando Tapatalk
ajgates92 said:
I am trying this now, thanks for the quick reply. Will let you know how it works!
Edit: Can you please put the exact code string I should enter into the Terminal? Thank you
Double Edit: I'm an idiot! I read your post wrong, I got it right this time and it worked!!! THANK YOU SO MUCH!!!!!
Click to expand...
Click to collapse
No worries, I'm glad you got it working. You're not an idiot, I'm a cryptic poster
So terminal app comes with superuser and busybox?
poetryrocksalot said:
So terminal app comes with superuser and busybox?
Click to expand...
Click to collapse
No, terminal app usually comes on custom roms but stock rooted users will have to download it for free off the market.
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