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..
Can u belive it ... i just got done doing a 2.1 ruu and reroot to try to fix a problem with not being able to get adb with certain roms including zens .9.6 builds ..kangslayer..newest buffed.. SO i figured let me ruu to take care of this ...WRONG...... I only can get adb from zen.9.5 and < fresh 2.12< does anybody have any input..YES DEBUGGING is enabled
Not having any issues with adb using stock or darch.
Can you run adb shell?
no that is the problem
Error device not recgonized
Trouble shooting would say to check you hardware first:
Comp usb port
Usb cable (broken bent or missing pins or torn wires)
Phone usb port
But sense you can access adb shell on other roms its not any of those.
Soo next up would be to check the roms them selves.
Maybe redownload the roms and do a full wipe before flashing ( don't forget to back up)
And see I'd the problem persists
thanks for the input but i have stressed all those options... I might be ebaying the hero earlier than expected... This is a asurion issued phone..my orginal was stolen 2 months ago
Sorry about the theft.
It'd be a shame if you sold your phone and there was a simple fix ):
Hmmm...
Do you have the sdk located in c?
What recovery are you running?
I think i'm having the same issue, but it could just be that i am very novice with the command line in general. I haven't tried to push anything through adb since i did the initial root a few months back. Now if i type in "adb shell" at the C:\ i get the error "adb is not recognized as an internal or external command, operable progam or batch file" What am i missing? Fresh 2.1.2
Okay
Your suppose to be in C:\android-sdk-windows\tools\
Just cd to the above mentioned
Thank you. That was quick and easy.
Your very welcome.
Enjoy the awesomeness that is adb shell
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
now im thinking that this is only a problem with overclocked kernals....
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
damiandarkwater said:
To my knowledge dd2.7 is oc'd and and works with it fine on my end. Do you have the HTC drivers installed?
Click to expand...
Click to collapse
Yes again because everything works with other roms..i think there is a problem on my end with the phones hardware and the OC kernals..
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
mickdubs said:
well u can enjoy the shell but i cant.... Im gonna wait for flips to release a new version of toast or fresh...then ill determine what im gonna do
Click to expand...
Click to collapse
I'm having the same problem. I believe (a somewhat educated guess), the boot process is locking before the adb software on the phone is loaded. if someone can help to get a console output on the screen during boot rather than the green/white htc screen would help.
tkirton said:
Try these commands:
adb kill-server
adb start-server
adb devices
See if your device shows up.
Click to expand...
Click to collapse
Yes i have tried that with no luck...
Somewhere in the boot process adb is lost like this was said above.
Im just keeping my fingers crossed for adb with the newsest fresh that should be released shortly
so i just flashed the newest (old) version of damage control. NON OC kernal and i got adb access.. So im convinced that this phone is a lemon becuase it was asurion issued and i loose adb with OC kernals. I did have OC kernals running fine on my previous hero that was stolen.
**UPDATE 3:34AM
so after testing out dc.. i tried to flash the newest OC kernal made for DC. Right after flash i lost adb...
Why is the phone loosing ADB on OC KERNALS.. Where phones patched!?
damiandarkwater said:
Your very welcome.
Enjoy the awesomeness that is adb shell
Click to expand...
Click to collapse
Orrrr. You can download and install Regaw's toolbox and it'll make it so you can run abd commands from ANY directory in command box... pretty sweet
But yes, otherwise you need to be in the c:\android-sdk-windows\tools\ folder to run adb commands (or where ever you saved the sdk at)
I am looking for anyone who can help me with installing adb on Ubuntu I've posted a topic in Q&A but received no response so I'm asking here I partition my hard drive and installed Ubuntu I've downloaded the sdk and I've gotton as far as placing the tg file in my home directory but still no go I think I'm missing something but don't know what I'm native to windows and I have adb working on that just fine but Ubuntu is all the way different like I said I'm really new to Linux so I'm asking for a step by step guide to install adb on Ubuntu and a list of commands for adb on Linux as well also I've been asking for a while now and still no answer does anyone know how to disable the force In call touch UI in CM6 its checked and blackend out the setting I'm speaking of can b found in setting /call settings I would like to b able to uncheck it also I'm very fond of the bx theme was wondering if anyone could help me to get it to work on CM6 stable any help with any of these would b greatly appreciated thanks
Root-Hack-Mod-Always™
what happens when you execute adb?
if your getting something like "can't execute blah blah" make sure that adb has execute permissions.
#chmod +x adb
its been awhile since I been on ubuntu you may have to sudo to execute chmod on ubuntu.
Wen I plug in my phone it does not recongize it also wen I hit adb says no command adb found did you mean then gives me a list of commands for something I'm not familiar with lol
Root-Hack-Mod-Always™
laie1472 said:
Wen I plug in my phone it does not recongize it also wen I hit adb says no command adb found did you mean then gives me a list of commands for something I'm not familiar with lol
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
first are you executing adb from the folder its in. If so and it says that the command is not found then make sure that the abd executable has executable perms on it.
Sorry if if I'm not precise on the instruction as I'm trying to do it from memory, I haven used linux in about a year or so and most of my nix time is solaris lately.
But you should by able to #chmod +x adb so that its has execute perms.
if you gets errors trying to run chmod try typing sudo first so that you can switch into root.
I'm not sure on running it threw the window its in I opened up terminal its the only thing open besides a search window on how to install this and when I did type in a command I hit sudo didn't try the other commands u gave yet I'm mobile and to my dismay ill b for a few hours but as soon as I get to my laptop I will and post results anything else you can think of is more than welcome to I don't shun knowledge thanks in advanced
Root-Hack-Mod-Always™
this might help getting adb and your phone working in ubuntu, if you need any more assistance pm me and i'll try my best to help.
http://forum.xda-developers.com/showpost.php?p=7874321&postcount=11
codejunkie78 said:
this might help getting adb and your phone working in ubuntu, if you need any more assistance pm me and i'll try my best to help.
http://forum.xda-developers.com/showpost.php?p=7874321&postcount=11
Click to expand...
Click to collapse
This will work. That was posted in the thread I started with the same question. Been running Ubuntu for over a month and use adb all the time.. Thanks again codejunkie!
Man I knew u guys would come threw I love Google but love xda more ill b home in less than an hr can't wait thanks a million
Root-Hack-Mod-Always™
Thought I had posted this here well unfortunately I ripped out a USB port on my laptop. Besides that I had to pop out my hard drive and send it in to HP because of a warranty repair. I should have it back by Friday and I'll post and let you guys know if I got it thanks again for the info
Root-Hack-Mod-Always™
Update
Got it installed and I posted a thread on how we did it in case anyone needs it thanks for the responses and I started a thread about anything hero so feel free to post and check it out all knowledge on heros is most definitely welcomed and encouraged by
Laie1472
Thanks in advanced
Root-Hack-Mod-Always™
CONFIRMED WORKING ON LINUX.. waiting to hear for windows, mac...
NOTE: Please keep track of what your doing, because if you DON'T know what you broke, your going to have a hard time fixing it.
I'd recommend NOT wiping DATA/factory restore unless you literally have NO other choice (see post 11)
That being said...
Assuming you know what change(s) you made before your bootloop, you are saying to yourself "If i could only boot up so i can UNDO it" ... this IS for you!
Directions:
Battery Pull
Put Battery Back
Hold M button on keyboard then power
Use vol - button to go to BP TOOLS (don't select yet)
Connect via USB to computer with ADB
In terminal on computer...
Code:
adb wait-for-device shell
On phone use vol + button to select BP Tools.. then wait for your terminal to get you into shell (this will happen while the phone is continuously bootlooping)
according to djrbliss root method...
Code:
mv /data/local/12m /data/local/12m.bak
ln -s /data /data/local/12m
exit
9.
Code:
adb reboot
10. wait for the power off then repeat steps 1-7
11. again thanks to djrbliss...
Code:
rm /data/local/12m
mv /data/local/12m.bak /data/local/12m
mv /data/local.prop /data/local.prop.bak
echo "ro.sys.atvc_allow_netmon_usb=0" > /data/local.prop
echo "ro.sys.atvc_allow_netmon_ih=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_res_panic=0" >> /data/local.prop
echo "ro.sys.atvc_allow_all_adb=1" >> /data/local.prop
echo "ro.sys.atvc_allow_all_core=0" >> /data/local.prop
echo "ro.sys.atvc_allow_efem=0" >> /data/local.prop
echo "ro.sys.atvc_allow_bp_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_ap_mot_log=0" >> /data/local.prop
echo "ro.sys.atvc_allow_gki_log=0" >> /data/local.prop
exit
12. then again, repeat steps 1-7
13. You should have root, now go ahead and fix whatever needs fixing and reboot 1 final time
ENJOY
-KrazyKrivda
I followed this exactly but could never get an adb connection. My drivers are good and my adb setup works just fine (I was using it earlier). And idea what I could be doing wrong?
Thank you so much for posting this btw!
one more reason why I choose linux over winblows. Just a personal opinion.
Darksurf said:
one more reason why I choose linux over winblows. Just a personal opinion.
Click to expand...
Click to collapse
I tried both Windows and Linux. Are there any special steps in Linux I may be missing to get adb to work in this mode? I tried my OG Droid to test the adb setup and it worked fine.
you need to be in the android group and have adb properly installed and preferrably the current version. I use a gentoo based linux system so this stuff isn't an issue for me.
Ubuntu and debian based systems are a little different. I really dislike the package management system and Ubuntu separates users from the actual "linux" part of linux. its like linux for n00bs. Not saying its a bad distro, its just not my distro of choice.
But, if you are booting up your device correctly, you should be able to do adb start-server and then do a adb remount (if rooted) then push the files to /system/app/
if you have just ran updates, reboot your computer. If you aren't picking up the device, try using other ports (usb ports can go into a suspend mode to save power and sometimes don't like to wake up, it also happens in windows)
Jonny9797 said:
I followed this exactly but could never get an adb connection. My drivers are good and my adb setup works just fine (I was using it earlier). And idea what I could be doing wrong?
Thank you so much for posting this btw!
Click to expand...
Click to collapse
Join us in IRC and I will try to talk you through it
please help me!
i am having the same problem. i can get into recovery, fastboot, AP, and BP modes, and my device manager sees the ADB interface, but i cannot execute commands. I get this error "C:\Program Files\Android\android-sdk\platform-tools>adb remount error: device not found". i have the latest SDK and moto drivers installed... is there anyway i can install an update.zip from recovery to get me out of the bootloop?
I've updated the OP.. there is no longer a "remount" part... so I'm not sure what you are doing.. again if you can join IRC ( webchat.freenode.com ... #krazyk is the chan ) i'd be more than happy to assist
guys, i need urgent help...
i did some **** by replacing the SystemUI.apk in RootExplorer and it started force closing. i rebooted and i started bootlooping i backed up the apk in a file on my sdcard called 'import'. now i tried BP tools but it wont recognize my device..i had adb working perfectly fine before. what should i do?
Krivda, even in VM ubuntu it still doesn't see my phone... i have jdk, sdk installed... windows and ubuntu both see my xoom but the D3 is not being seen...
if the bootloop is caused due to an issue created in /data then then a factory reset will be fine (if you don't mind losing data).
HOWEVER, if the change it made is in /system.. the factory reset may reset your adb debugging option... which in turn will mean.. you will be stuck in a bootloop without the ability to access adb at all, in which case you are SOL until sbf or a way to run update.zip from recovery.
Yep that's me! I need an sbf lol
royalpunk, let me know if you find a way out... im in the same situation...
yeah, I'm the same as royol and highcee... i guess it just gives us a double incentive to find an sbf
i am also in the same situation ugh
I haven't started to fiddle yet but fear not ill be with yus tomorrow lol
-smc
I know its tempting to foolnaround with files. But no one should be messing with anything till we get an sbf.
suzook said:
I know its tempting to foolnaround with files. But no one should be messing with anything till we get an sbf.
Click to expand...
Click to collapse
SHUTUP lol you're making me feel bad
a little clarification.. OP UPDATED
I wanted to say THANK YOU to krazykrivda.
Because of your how-to I have successfully unbricked my Droid3 )) THANKS
HI All,
I just have recieved my Tablet back after it would no longer power up - looks like they had to re flash it and put it into factory mode and left it there, problem with this is that I cannot lock the screen, I have researched and found a temp fix where you put a engineers code in - but as soon as you re-boot it loses this.
I have also found some code
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
which i have tried using a terminal emulater (on the andriod market) not sure if its me being dumb but i cant get this to work, when it boots now it looks like nvflash is now unlocked. I'm hoping i dont have to send it back again - is there any other things I can try? I have tried other ROMS but because of this factory mode its the same
Thanks in advance
whitehart said:
HI All,
I just have recieved my Tablet back after it would no longer power up - looks like they had to re flash it and put it into factory mode and left it there, problem with this is that I cannot lock the screen, I have researched and found a temp fix where you put a engineers code in - but as soon as you re-boot it loses this.
I have also found some code
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
which i have tried using a terminal emulater (on the andriod market) not sure if its me being dumb but i cant get this to work, when it boots now it looks like nvflash is now unlocked. I'm hoping i dont have to send it back again - is there any other things I can try? I have tried other ROMS but because of this factory mode its the same
Thanks in advance
Click to expand...
Click to collapse
A friend of mine followed this thread and he made it.i think he has the same issue with factory mode.Did u try?if not u can try and see how it works.Good luck.
http://forum.xda-developers.com/showthread.php?t=1870564
thovu1980 said:
A friend of mine followed this thread and he made it.i think he has the same issue with factory mode.Did u try?if not u can try and see how it works.Good luck.
http://forum.xda-developers.com/showthread.php?t=1870564
Click to expand...
Click to collapse
cheers yes thats what i tried following
I wonder if I'm not doing the
adb shell
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
code correctly, whats the best way to enter this code? I think I may need an idiots guide !!
im going to phone the repair place see what they say
Phoned up samsung - they not able to do anything on the phone, sigh!!!!
it has to go back to the repair place - samsung i dont think understood the issue fully - lets hope it gets fixed - i learnt they replaced the motherboard!
Why don't you ask over here? http://forum.xda-developers.com/showthread.php?t=1870561
You can use Terminal Emular and enter:
Code:
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Make sure you are rooted! (SuperSU or Superuser installed)
tracid said:
Why don't you ask over here? http://forum.xda-developers.com/showthread.php?t=1870561
You can use Terminal Emular and enter:
Code:
su
echo -n ON > /efs/imei/keystr
chown 1001:1001 /efs/imei/keystr
Make sure you are rooted! (SuperSU or Superuser installed)
Click to expand...
Click to collapse
just tried teh code again to see if i was going mad - no it doesnt seem to work? the engineers code temp works but the emulator code doesnt
EDITI just did a reset - after doing the code - guess what so far so good I think i have fixed it
Yayyy!!!