Related
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..
I am using the PRS complete rooting guide. And when it tells me to type cat /sdcard/su > su, i am getting this error message - cat: can't open '/sdcard/su': No such file or directory.
Can anyone help with this?
Do you have su on your sdcard?
use unrevoked. one click root
just use the one click method by unrevoleved its easier
Su is not on the SD card. The sd card is a brand new PNY card. I have Su in the sdk/tools folder.
Then obviously, that command will not work. Use the unrevoked method if you are unsure what these commands do/how they work. Less headache on your end.
where is it located?
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
This is what it's asking me to do.
From PRS Complete Rooting Guide
Now type the following commands to make it persistent through reboot
Code:
adb shell
su
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su /* IF YOU GET AN ERROR HERE DO rm /system/xbin/su THEN REDO */
chmod 06755 su
k_flan said:
maybe i'm missing something obvious, but why pipe the text rather than just copy the file?
Sorry if this is the wrong place, but that command is curious.
Click to expand...
Click to collapse
I don't know what that guide does, but it doesn't seem right --- it'll mess up the privs, that's why the old root was written as an update-payload.
It's redirected I/O since you can't copy across filesystem boundaries -- ie /sdcard to a different mountpoint.
So if I reboot my phone now, do you think I'll lose root and have to start over?
csills said:
So if I reboot my phone now, do you think I'll lose root and have to start over?
Click to expand...
Click to collapse
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to http://unrevoked.com/ and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
askwhy said:
Either way, it shouldn't matter much. If it didn't work or you lost root for any reason, just go to and click on the image for the Incredible. Today unrevoked released version 3 of their tool. This will root your phone and flash the custom recovery all without your needing to do anything in a shell.
Click to expand...
Click to collapse
AND - if you appreciate unREVoked's work - please donate. They do amazing work and they do it all for free! We're the lucky ones to have such [email protected] developers out there who do this kind of stuff so that we don't have to figure out the exact second to push in our SD cards, push files to the SD card, and then push them to the phone at exactly the right time...... just download, run, and you're done.
Just use the unrevoked 3 you will save plenty of pain and struggle
unrevoked3 worked! Thanks for the help guys.
No problem were glad to be of assistance
Sorry... newb question... can not figure out this deal...
Trying to copy the jupiter files to my phone... can not.
I dont have permissions... how can I get permissions opened up?
Below is some of what I am getting in regards to errors -
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /system/etc/jupiter.xml
failed to copy 'jupiter.xml' to '/system/etc/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb shell
$ su
su
Permission denied
$
Note - this is a samsung captivate phone with a fresh cognition 2.36b rom and I used one click root on it to root the phone after the build..... (but I think the rom was rooted to start with??
Sorry ... just need a way to get access to this phone - trying adb.... also is there a windows file manager that would browse/edit the contents of this phone?
thanks in advance Kevin
PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
IF you're on Froyo.. for some reason froyo does not allow pushing to /system .. at least for me that's the case (someone correct me)
root your phone:
1. adb push /sdcard/jupiter.xml
2. adb shell
3. su
4. cp /sdcard/jupiter.xml /system/gps/jupiter.xml (or wherever you need to put it)
5. do the same for the rest of the files.. but tbh
THERE'S NO FIXING GPS YET
darkamikaze said:
PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
THERE'S NO FIXING GPS YET
Click to expand...
Click to collapse
What he said.
If froyo didn't fix your gps then you are sol. But don't be so sure its still broke, it can take some time on the first lock. Once it gets a lock within 5-10 meters it should work decent afterwards with the occasional hiccup usually when its not used every day. But some are reporting poor performance still with froyo.
A factory reset can fix some bugs I have seen on jf7 and ji6 on my phone causing the gps to turn off. Jj4 doesn't seem to have that bug on my phone. Cog2.3b6 is jj4 based
Some claim to have performance degrade over time, I think that's all placebo but others have completely different experiences with gps than I do. I notice it having to occasionally need to get new gps data causing a delay in the initial lock but it seems more random than progressive and I never fail to get a lock.
If you are trying to use the jupiter.xml file in the gps solution thread from clshortfuse our what ever his name is, you will likely see an no improvement to a slight improvement. It gets faster locks on eclair roms but on froyo the jupiter file already resembles his and the major difference being that his forces the google server for gps data.
Sent from my SAMSUNG-SGH-I897
OK thanks for all the help so far -
I had a n82 phone, like 2-3 years ago, it was awesome.... google maps and all... blue dot was where the phone was... I could watch me walk around my house... it would show me getting the mail walking down the drive way to the mail box and back....
I have an iphone 3gs....works fine.... maybe not quite as good as the n82 did, but works ok, locks quick and will the blue dot with in a few feet of me IN MY HOUSE.
While I dont get this whole GPS problem on this phone I hear you about not trying to fix it.
I have some limited unix experience... used vi and other stuff, was able to move,copy, edit and replace files... change permissions and other standard stuff.
So if the cognition rom is rooted as is, and I was rooted before the rom, I assume I still am rooted....
Why wont the commands I tried work?
I did not try the other commands noted in this thread, yet, I will soon.
So is it my phone? or do I have the commands/syntax wrong?
If I am going to stick it out with the phone I need to figure out how to fix it.
thanks again for your help.
Kevin
Any ideas or reasons why this command would not work?
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
My file on my PC is in the folder I am working from ....\tools and I assume I should have permissions to the sdcard folder?
Any help would be appreciated.
thanks Kevin
Have you made sure to grant superuser permission on the phone?
I had that issue the first time I tried it and found that I hadn't granted superuser access.
Also to the OP, if you switch to Perception, DG includes the Jupiter fix in the ROM.
You can't push to /system in FROYO.
you have to push it to /sdcard first
adb shell
su
cp /sdcard/jupiter.xml /<LOCATION>
and chmod it
and chown it.
thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin
haeffnkr said:
thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin
Click to expand...
Click to collapse
I would never do 777 on any file. Jupiter.xml should be 644 and user and group root.
Sent from my SAMSUNG-SGH-I897 using XDA App
I did something stupid, which involved not staying up to date with the news on my kindle hd 7 inch since i got comfortable with my setup and hadn't really done anything much to it lately that needed me going to the forums. Anyways, my kindle decided to download the ota update, which was like a slap in the face because 3/27 was my birthday and I was in the middle of reading manga and it rebooted then tried to update so I naturally held the power button down. Is there anyway to cancel the update via adb? I typically leave adb on as a precaution to any problem I might have. I thought maybe I could run a shell and tell it to remove the update file which I'm assuming is still in /sdcard/kindleupdates (I think thats the folder name), and maybe push the 7.2.3 update as a precaution in case it started to flash already and I didn't notice. I don't want to turn it back on until I know that I can connect to it with adb because I don't want it to update, I planned on flashing cm10 to it whenever it became stable, and I heard the latest update will break the ability for me to put a bootloader on it. Any help would be appreciated.
stunts513 said:
I did something stupid, which involved not staying up to date with the news on my kindle hd 7 inch since i got comfortable with my setup and hadn't really done anything much to it lately that needed me going to the forums. Anyways, my kindle decided to download the ota update, which was like a slap in the face because 3/27 was my birthday and I was in the middle of reading manga and it rebooted then tried to update so I naturally held the power button down. Is there anyway to cancel the update via adb? I typically leave adb on as a precaution to any problem I might have. I thought maybe I could run a shell and tell it to remove the update file which I'm assuming is still in /sdcard/kindleupdates (I think thats the folder name), and maybe push the 7.2.3 update as a precaution in case it started to flash already and I didn't notice. I don't want to turn it back on until I know that I can connect to it with adb because I don't want it to update, I planned on flashing cm10 to it whenever it became stable, and I heard the latest update will break the ability for me to put a bootloader on it. Any help would be appreciated.
Click to expand...
Click to collapse
You can find here instructions on how to disable OTA services:
Code:
adb shell su -c "busybox mount -o remount,rw /system"
adb shell su -c "mount -o rw,remount /dev/block/mmcblk0p1 /system"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAUpdateMessageHandler'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.InventoryUploadService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.UpdatesLookupService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.AppStateMonitorService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.CheckForOTAUpdatesService'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.ViewUpdateActivity'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAStatusActivity'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.ResetOTAMessageHandler'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.InventoryUploadService$InventoryUploadReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.UpdatesLookupService$MountStatusChangedReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTAWakeupReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTADedupeReceiver'"
adb shell su -c "pm disable 'com.amazon.dcp/.ota.OTAService$OTAInstallNowReceiver'"
adb shell su -c "busybox mount -o remount,ro /system"
adb shell su -c "mount -o ro,remount /dev/block/mmcblk0p1 /system"
adb reboot
adb wait-for-device
The question is how to get access to ADB. If you boot your device normally then I guess it will be too late. Kindle OS will proceed with the update. Perhaps, you can get into recovery (if you have it) and run these commands.
Anyway, it is better if you hear a second opinion from somebody more experienced.
thanks for that, i found that script when i was browsing earlier in a sh script, and was going to ask if it worked until i noticed that the script was linked back to the xda forums, wish i had sen it before my kindle started updating, and i don't have a custom recovery installed, thats why i wanted to not install this update i had been waiting around for one to come out and i kinda forgot about it and never checked back to see that it was out. I hope someone can still help me out, or atleast tell me if i will just have to boot up and I'm assuming wait for a new root exploit, since i think they usually patch the previous one when they update. Hope to hear a reply soon because i hate reading manga on my ipod... its got a small screen compared to my kindle... (I NEED MY MANGA FIX xD) and yes i know i could read it on my pc bu ti cant lay in my bed while i do it... love the quickmanga app.
stunts513 said:
thanks for that, i found that script when i was browsing earlier in a sh script, and was going to ask if it worked until i noticed that the script was linked back to the xda forums, wish i had sen it before my kindle started updating, and i don't have a custom recovery installed, thats why i wanted to not install this update i had been waiting around for one to come out and i kinda forgot about it and never checked back to see that it was out. I hope someone can still help me out, or atleast tell me if i will just have to boot up and I'm assuming wait for a new root exploit, since i think they usually patch the previous one when they update. Hope to hear a reply soon because i hate reading manga on my ipod... its got a small screen compared to my kindle... (I NEED MY MANGA FIX xD) and yes i know i could read it on my pc bu ti cant lay in my bed while i do it... love the quickmanga app.
Click to expand...
Click to collapse
When kindle is updated to 7.3.0 you lose your root and some applications will stop working or get deleted. You can still re-root your Kindle 7.3.0 using exactly the same procedure as for 7.2.3. I just re-rooted my device yesterday. it worked without any problem. I had to reinstall Google Play and custom launcher after root.
ok well thanks, I guess I have no choice but to let it finish updating, well maybe unless they find a new bug to let us put custom recovery on it, that other project will get more attention, can't remember the name of it because I haven't been browsing around in the community much for atleast a month. Funny thing is I have to remember how I rooted my kindle... I left all my rooting utilities and scripts in a folder, but my mom has a kindle fire 1st gen that i rooted as well so the stuff is also in the folder, shouldn't be a problem though I'm a pc tech so i can sort this stuff out easily.
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
i have the exact same issue, is there any answer for this??
Wettpassat said:
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
Click to expand...
Click to collapse
i have the exact same issue, is there any answer for this??
Well it's been well over a year since I did that but let's see if I can help..... Before I start I'm hoping you've already enabled adb debugging on the gear and downloaded adb onto your computer. I believe you run the commands after you've run cygnia but before you flash twrp. You run the task from a command prompt from your pc. I'm pretty sure you don't include the $ or #. Before you start try the adb command- adb devices from the command prompt on your pc. That'll let you know if the gear is connected. I remember being a bit intimidated by it all as it was different to any other flash I'd done. In reflection it's very easy, type the line in a command prompt, press enter, wait for the cursor to come up again, type the next line. As for guides..... I can't remember which one I used but there's plenty out there.