First off, as always, if this causes any damage, or loss of anykind anyhow anyway I am not at fault, don't blame me.
So you rooted? But no longer want root? or want to downgrade to 1.5 with an ruu? or want to flash one of the PB00IMG like the root one with an engineering bootloader?
Tonight I made another custom misc.img, it is attached to this post. You will also need flash_image which can be found here. http://www.multiupload.com/KS2JCAMGBH
Run these commands as root:
Code:
adb push flash_image /data/local/flash_image
adb push misc.img /data/local/misc.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image misc misc.img
Now you can flash any known (to me) ruu or PB00IMG
Cool beans and thx for your continued help even tho you don't have a Eris anymore.
korben dallas said:
Cool beans and thx for your continued help even tho you don't have a Eris anymore.
Click to expand...
Click to collapse
I have 1 motodroid, 1 eris w/ no service and 1 eris with service (Wife), I haven't been able to do dev work on the eris til recently, no root.
That has changed
Great job .thanks for working on the eris
jcase you are a god among eris user keep up the good dev'ing
jcase said:
I have 1 motodroid, 1 eris w/ no service and 1 eris with service (Wife), I haven't been able to do dev work on the eris til recently, no root.
That has changed
Click to expand...
Click to collapse
Oh my bad thought you said while back it had a bad radio and you got a Droid. I guess no more assuming lol
The hits keep on coming!
I suppose this should work equally well for PB00IMG.ZIP installs (from the corresponding RUUs), yes?
This should make life easier for "unrooters"; now if there just some way to convince them that there is really only 1 reason to unroot a phone
bftb0
my only reason for unrooting is sending my phone back ......which i will be doing this weekend..... refurb is suppose to be here today
thanks jcase ....thanks for the continued work on the eris .....
rvpartsguy said:
my only reason for unrooting is sending my phone back ......which i will be doing this weekend..... refurb is suppose to be here today
thanks jcase ....thanks for the continued work on the eris .....
Click to expand...
Click to collapse
Exactaly i just got my beautiful refurb
BTW EVERYONE,......,
if u have a custom boot screen u will want to take it off first or you will be locking it in
Sent from my Eris using XDA App
korben dallas said:
Oh my bad thought you said while back it had a bad radio and you got a Droid. I guess no more assuming lol
Click to expand...
Click to collapse
It did, the one I used. It was the only non leak one I had. Puit kinks in everything.
When I try it it just keeps saying push: not found.
The commands are the same thing for OSX, right? Drag tools to Terminal and then just copy and paste those lines of commands?
hackthis02 said:
When I try it it just keeps saying push: not found.
Click to expand...
Click to collapse
Yeah dude, those instructions didn't work for me either. This is what I did (and it worked):
Code:
adb push flash_image /data/local/flash_image
adb push misc.img /data/local/misc.img
adb shell chmod 777 /data/local/flash_image
adb shell flash_image misc /data/local/misc.img
do we put the two files into the SDK/Tools folder? or are we putting them on the SD card and running these commands while the phone is in recovery? Sorry I'm a little new to this.
derickmc said:
do we put the two files into the SDK/Tools folder? or are we putting them on the SD card and running these commands while the phone is in recovery? Sorry I'm a little new to this.
Click to expand...
Click to collapse
Tools folder.
hey guys, sorry but i'm really confused as to what to do here. i'm running evil eris and i want to downgrade to 2.1leak to get a refurb eris. i'm a complete noob with all the sdk stuff. i've gotten as far as putting the two files in the sdk/tools folder, lol. if someone could help me out with this, it'd be greatly appreciated...thanks a ton.
Just flash the pbooimg.zip back onto the phone. Out should be good from there.
Sent from my Eris using XDA App
niether worked for me. the original post reads.. error opening misc.img: no such file or directory...your method reads..error reading : /data/loca/misc.img headed : Is a directory
lil_dez said:
Yeah dude, those instructions didn't work for me either. This is what I did (and it worked):
Code:
adb push flash_image /data/local/flash_image
adb push misc.img /data/local/misc.img
adb shell chmod 777 /data/local/flash_image
adb shell flash_image misc /data/local/misc.img
Click to expand...
Click to collapse
Me! Me ! Me! too please
Hey I am not understanding what to do either. I have a rooted eris that the screen started flaking out so i Have to send it back.
I rooted alright and I have a basic understanding of the recovery stuff. But could you guys either tell me what to do from scratch on this one or point me in the right direction.
I've been searching the forum for 2 weeks trying to learn how. My kids are teasing me now cuz all I do at home try to learn about this stuff. Well anyway I would appreciate some help.
I have just opened a can of worms
Wow!!! I truly did not realize the full extent of what yous guys are doing on this website. You are smart people!!! hahahaha I opened a can of worms and can't get it shut again.
You guys are the ones writing and developing all kinds of programs.
i hope you guys arent taking this the wrong way!!!
I honestly didnt realize till I researched and found the HTC Developers center.
I have no buisness trying to do any of this stuff!
If some can help me out I would appreciate it!!!!!!
Related
USE ARE YOUR OWN RISK.
http://www.multiupload.com/DXQVBXB93G
http://www.multiupload.com/KS2JCAMGBH
Credit to wag3slav3 and a donate link for him so morons cant claim I am stealing his donations. http://forum.xda-developers.com/showthread.php?t=724741
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
then once booted
adb shell /data/local/flash_image recovery /data/local/recovery.img
This work for non-leakers only right?
Holy crap, it's really that simple? That's amazing.
Should work for EVERYONE.
jcase said:
Should work for EVERYONE.
Click to expand...
Click to collapse
is this just root? it wont wipe out data? i just want to overclock
v941726 said:
is this just root? it wont wipe out data? i just want to overclock
Click to expand...
Click to collapse
Do that then flash SU
Dc_striker said:
Do that then flash SU
Click to expand...
Click to collapse
sorry but, how do you flash su? and you didnt answer if it wipes out my data.
v941726 said:
sorry but, how do you flash su? and you didnt answer if it wipes out my data.
Click to expand...
Click to collapse
sir im saying this in the most friendly way possible
but i was once just like you new to hacking and lots of questions
but you must understand all the questions you have can be answered by reading on here or google search
everyone is tired of answering the same question of the newbies and trust me i have been flamed
also check out the forum rules about posting questions certain questions go in certain places if you want quick answers....all love bro i want to see you rooted and happy
if you have root
su is Super User access
you need to get the su.apk go here and take a look http://forum.xda-developers.com/showthread.php?t=682828
su allows certain apps to do rooted things including overclocking
btw you will alos new the setcpu app to overclock go here http://forum.xda-developers.com/showthread.php?t=505419
but before that you still should do some research
good luck to you brother
Oooh, don't anger the gods.
v941726 said:
sorry but, how do you flash su? and you didnt answer if it wipes out my data.
Click to expand...
Click to collapse
They really do get upset in here when you don't know as much as they do.
Let me help...
Run to this thread and read up:
forum.xda-developers.com/showthread.php?t=724741
There is an automated script that will help you with the root. Many users, including myself had to run it a couple of times before it took - so if it doesn't go off the first time, don't lose faith, just try again.
As for whether or not it wipes, that's moot - You should, after you run the hack flash a custom rom - this will wipe your data. Any ROM you like from the dev forum will do. I am using Froyo v21. But you can certainly try any one you like. As for non-Froyo roms, I like the Cyannogen ELB builds. But again it is your preference that matters.
To flash the new rom, you need to boot into recovery mode. If you run the script from the above thread, it will boot you into recovery mode. If you use the instructions in this thread, type "adb reboot recovery" at your command prompt immediately after you are done. Once there, you can do the following:
-Do a NAND backup
-Put your phone into USB SD mode and copy over your ROM of choice to the root of your SD card.
-Do a factory wipe and a dalvik cache wipe
-flash your new rom
When you flash the new rom, depending on which one you do, you should have su or root. You can then download and install apps that require root.
Remember, you should back-up your data before you try to do anything to your phone. It's just a good idea.
If you have any ROM specific issues, try looking through that ROM's thread for answers. Also, if you have any other questions about how to do anything, the first sticky thread in this forum is a great collection of how-tos. You can also PM Me and I will be happy to help.
Don't forget that a lot of hard work went into rooting leak. Do like many of us have and donate to those responsible.
i understand what your saying about asking here. but seriously, i searched and it seems like every thread says the same thing. so i jump all over the place and end up going in circles. i did my sons moto droid yesterday pretty easily. he now has root and a smoking droid w/o disturbing anything else. so, sorry, but it is tough. thanks for your reply. i got this particular thread from android forums and it looked like the one. a new one at that. but i spent several hours going around in circles. googling and everything. i am a noob with linux based phones. yes. but i'm very capable and dont need baby steps. just need some straight answers. so sorry. i will check your links. thanks for your reply
Works just as good as the automated method. Good deal.
Father_Vic said:
They really do get upset in here when you don't know as much as they do.
Let me help...
Run to this thread and read up:
forum.xda-developers.com/showthread.php?t=724741
There is an automated script that will help you with the root. Many users, including myself had to run it a couple of times before it took - so if it doesn't go off the first time, don't lose faith, just try again.
As for whether or not it wipes, that's moot - You should, after you run the hack flash a custom rom - this will wipe your data. Any ROM you like from the dev forum will do. I am using Froyo v21. But you can certainly try any one you like. As for non-Froyo roms, I like the Cyannogen ELB builds. But again it is your preference that matters.
To flash the new rom, you need to boot into recovery mode. If you run the script from the above thread, it will boot you into recovery mode. If you use the instructions in this thread, type "adb reboot recovery" at your command prompt immediately after you are done. Once there, you can do the following:
-Do a NAND backup
-Put your phone into USB SD mode and copy over your ROM of choice to the root of your SD card.
-Do a factory wipe and a dalvik cache wipe
-flash your new rom
When you flash the new rom, depending on which one you do, you should have su or root. You can then download and install apps that require root.
Remember, you should back-up your data before you try to do anything to your phone. It's just a good idea.
If you have any ROM specific issues, try looking through that ROM's thread for answers. Also, if you have any other questions about how to do anything, the first sticky thread in this forum is a great collection of how-tos. You can also PM Me and I will be happy to help.
Don't forget that a lot of hard work went into rooting leak. Do like many of us have and donate to those responsible.
Click to expand...
Click to collapse
thanks. this may be dumber yet but, i cant find a way to pm you or anybody her
This should get a sticky
sawah said:
This should get a sticky
Click to expand...
Click to collapse
The topic should get deleted...
...and wag3slav3 should just copy/paste this into the bottom of his first post. To me this thread, even with the credit, looks like it's trying to steal his "thunder."
jcase said:
USE ARE YOUR OWN RISK.
http://www.multiupload.com/DXQVBXB93G
http://www.multiupload.com/KS2JCAMGBH
Credit to wag3slav3 http://forum.xda-developers.com/showthread.php?t=724741
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
then once booted
adb shell /data/local/flash_image recovery /data/local/recovery.img
Click to expand...
Click to collapse
wow!? are you serious. thats it. . . that took 8 months, it looks so simple now that its in writing. =(
sad for life
hey better late then never though =) glad you leakers can get root now.
xnatex21 said:
The topic should get deleted...
...and wag3slav3 should just copy/paste this into the bottom of his first post. To me this thread, even with the credit, looks like it's trying to steal his "thunder."
Click to expand...
Click to collapse
Since when does jcase try to steal anyone's thunder. He watches out for the dev community more than anyone.
v941726 said:
thanks. this may be dumber yet but, i cant find a way to pm you or anybody her
Click to expand...
Click to collapse
Just click on the user name.
Father_Vic said:
Just click on the user name.
Click to expand...
Click to collapse
i did. no way to pm there
C:\android\tools>adb push recovery.img /data/local/
856 KB/s (3926016 bytes in 4.477s)
C:\android\tools>adb push flash_image /data/local/
507 KB/s (9640 bytes in 0.018s)
C:\android\tools>adb shell chmod 777 /data/local/recovery.img
C:\android\tools>adb shell chmod 777 /data/local/flash_image
C:\android\tools>adb shell rm /data/local/rights/mid.txt
C:\android\tools>adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
C:\android\tools>adb reboot
C:\android\tools>adb shell /data/local/flash_image recovery /data/local/recovery
.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
C:\android\tools>adb shell
$ su
su
su: permission denied
Click to expand...
Click to collapse
Anyone else get this?
v941726 said:
sorry but, how do you flash su? and you didnt answer if it wipes out my data.
Click to expand...
Click to collapse
Everyone, if you don't want to do a wipe and install a custom ROM, you can just flash EngTools.zip, courtesy of jcase, and it will add su and superuser.apk without disturbing your existing data (apps, settings, etc).
jcase said:
Get follow root tutorials and get amon's recovery installed. If you want to skip installing a new rom after rooting, You can flash EngTools.zip will root your device.
Click to expand...
Click to collapse
Ok I got A Problem. Went to flash a new rom after backing my current one up with rom manager everything went fine till I went to flash it and now it says
E: Failure at line 7 symlink dumpstate SYSTEM:bin/dumpcrash
I dont have a working phone. Tried several different roms and nothing.
what do I need to do??
can u boot in to recovery mode " vol up + power button " ? and dont use Clockworkmod recovery as its known to have issues with the eris.
use the other recovery.
Thanks T.A.
Yes I can Boot into recovery thats it.
How do I go about Flashing a New Recovery Manager
Topaz is right.... Amon_RA FTW !
How do I install that now though. I have been searching through forums looking cant find a step by step
Forgot to say I was a Leaker before they found the method.
would this work
http://forum.xda-developers.com/showthread.php?t=725096&highlight=Flash+Amon's+recovery
metzy75 said:
How do I install that now though. I have been searching through forums looking cant find a step by step
Forgot to say I was a Leaker before they found the method.
would this work
http://forum.xda-developers.com/showthread.php?t=725096&highlight=Flash+Amon's+recovery
Click to expand...
Click to collapse
might work, I imagine you could also try this....
http://forum.xda-developers.com/showthread.php?t=725047
this gives you the S-OFF bootloader and Amon_RA for recovery
you might wait to see if others weight in on the best approach here.
Already turned S-OFF the only reason I have clock work is because my noobie ass used rom manager for convience
metzy75 said:
Already turned S-OFF the only reason I have clock work is because my noobie ass used rom manager for convience
Click to expand...
Click to collapse
"noobie ass" is funny.
jcase's approach in your link is probably all you need then
Phones about to get thrown at the wall. Nothing is working, do the adb push moves file fine then couple commands down it says not there
metzy75 said:
Phones about to get thrown at the wall. Nothing is working, do the adb push moves file fine then couple commands down it says not there
Click to expand...
Click to collapse
if you do
adb devices
does its show a device HTCxxxxxxxxxx (some alphanumeric)?
Do this
Code:
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
try this in fastboot ( SEND + POWER )
not sure u can push files into /data/local/
hopefully it will work and if not and all fails.
put a rom on sd card and boot into recovery and hopefully clockworkmod recovery will flash it.
Yep, really have no idea what to do. I run the commands in what you gave me and the stupid thing says file its there when i use root command to navigate there its right there. idk whats going on.
TopazAaron said:
Do this
Code:
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery.img
adb shell chmod 777 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
adb reboot recovery
try this in fastboot ( SEND + POWER )
not sure u can push files into /data/local/
hopefully it will work and if not and all fails.
put a rom on sd card and boot into recovery and hopefully clockworkmod recovery will flash it.
Click to expand...
Click to collapse
doesn't show its connected, I have fastboot USB showing on the eris
tried flashing many roms no good same error
http://forum.xda-developers.com/showthread.php?t=651669
May help in that it includes the Amon_RA file and offers a different approach...
good luck
have you ever heard of the jitterbug?
Sjflowerhorn said:
have you ever heard of the jitterbug?
Click to expand...
Click to collapse
Idk what a jitter bug has to do with this. But I got the recovery changed but nothing still flashes.
Got to line 8 instead of line 7
says cant chown/mod /system/bin
(no such file or directory
E: failure at line 8
set_perm_recursive 0 2000 07550
Sjflowerhorn said:
have you ever heard of the jitterbug?
Click to expand...
Click to collapse
holy crap... i almost fell outta my chair!!!! LOL (i used to tell this lady at work all the time.... you NEED a jitterbug!!!).
------------------------------------------------------------------------------------------------------------
in any case...
metzy75... you said you backed up (a NAND backup i'm assuming)... are you able to restore your backup? or same failure? different message?
metzy75 said:
Idk what a jitter bug has to do with this. But I got the recovery changed but nothing still flashes.
Got to line 8 instead of line 7
says cant chown/mod /system/bin
(no such file or directory
E: failure at line 8
set_perm_recursive 0 2000 07550
Click to expand...
Click to collapse
what ROM are you trying to flash?
zach.xtr said:
what ROM are you trying to flash?
Click to expand...
Click to collapse
Just Official eris one that came with that all in one zip. and plain jane as wwell
Plain Jane fails at line 7 and offical eris line 8
tenzomonk said:
holy crap... i almost fell outta my chair!!!! LOL (i used to tell this lady at work all the time.... you NEED a jitterbug!!!).
------------------------------------------------------------------------------------------------------------
in any case...
metzy75... you said you backed up (a NAND backup i'm assuming)... are you able to restore your backup? or same failure? different message?
Click to expand...
Click to collapse
Backups all failed.
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
bassmonkey said:
hey all. anyone know if we can turn s-off on wildfire yet? kninda frustraiting... its root but not really root
Click to expand...
Click to collapse
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
gyroing said:
Not yet till Alpharev v2 realesed
Sent from my HTC Legend
Click to expand...
Click to collapse
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
niksakl said:
To me this is a 100% genuine "WTF?" statement... I don't get what you mean mate, please explain..
Click to expand...
Click to collapse
As far as I can tell its a new security thing HTC have added to the hboot, basically makes the system folder read only even with root (think that's correct??)
Sent from my HTC Wildfire using XDA App
bassmonkey said:
Thanks dude, I've just came from having a totally customized hero
N despite the screen rez I'm loving this phone but no access to system folder is pants
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
thanks for the response guys
71baker said:
Well , it's not totally locked down. You can access it (Read and write) if you boot into recovery. Not the smoothest solution but it works. Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
how do you do it through recovery? im guessing thatd be with adb?
Tetractys said:
You can change the /system permission with a terminal emulator as Better Terminal Pro on the phone or by the phone connected to your pc via
Code:
> adb shell
doing in both cases:
Code:
# chmod -R 777 /system
when you restart the phone, /system will be reset to the original 755 permissions.
Click to expand...
Click to collapse
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
bassmonkey said:
thanks for the response guys
how do you do it through recovery? im guessing thatd be with adb?
in terminal i entered su
chmod -R777/system
which then gave me; usage: chmod <mode> <file>
i then entered; /system and got permission denied??
Click to expand...
Click to collapse
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Tetractys said:
If you have written the command exactly as you report is obvious that the os return an error. try to write as i did... (with blanks in between)
of course your phone had to be passed the Unrevoked 3.21 procedure!
http://forum.xda-developers.com/forumdisplay.php?f=701
Anyway if you are not very much concerned in linux shell commands, i would suggest you to wait another more automatic method.
Click to expand...
Click to collapse
lol.'not concerned' very diplomatic yeah, kind of a windoze boy n therefore not really up on linux.
i did root with 3.21 and i tried the chmod command with all the spaces and terminal just gave me 'bad mode' (it also gave me bad mode when i tried adb) so i tried as i posted. bummer but nevermind, come on alpharev 2
71baker said:
Also there is AUFS but i don't think i have gotten that to work at all. Maybe it needs to be enabled, haven't really checked but i boot into recovery when i need to change something.
Click to expand...
Click to collapse
You can enable AUFS in Jacob's latest kernel by typing "aufs --enable" in a terminal emulator app in android, and then reboot the phone.
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.
you know, I've had the same problem lately. --curious to know what's causing it.
decalex said:
you know, I've had the same problem lately. --curious to know what's causing it.
Click to expand...
Click to collapse
Its good to know I am not the only one out there with this issue maybe someone can chime in with a fix. or some insight at least to what the problem may be.
Still no response.... Bump?
watermoore said:
Okay So ever since I have gotten my Epic a week ago I have felt like a total Noob. I came from an HTC HERO which I rooted manually. My wife has an HTC EVO which I rooted using UNREVOKED ONE CLICK (I know I cheated but she doesnt care). This Epic has me heading back to my roots lol. Either I am a total Noob and this is a simple fix and my dumb ass keeps overlooking it (which at this point I am hoping for) or my Epic is Effed and I need to send it back before my 30 days is up.
Basically my problem is that I cant Adb remount or Adb push to save my life. When I use Adb devices it lists my device so I know my phone is talking with my computer correctly. I first Odin'd to DK28 with the root and clockwork etc. Everything seemed fine except I like to swap stock fonts for custom fonts via Adb, simple things like that. Since I cant remount I figured something was either wrong with the Rom or the Root. So I just tried to load a custom ROM up and try my luck seeing as thats pretty simple. I loaded Epic Experience 2.0.06 and got it all set up as my Daily. Then I got busy and just used it for a few days continuing to tweak my Rom and get it all dialed in for daily use.
I wanted to try ViperRom and see what that was all about so I made a backup in Clockwork and loaded ViperROM with no problem. While ViperROM is pretty snappy its not really my taste so I figured I would wipe and restore my EE backup. No matter how many times I did the data wipe, cache, davlik etc my restore would boot up greeting me with force close after force close. So I ODIN'd back to stock 2.2 then used the one click root exploit to get root. it seems like it worked but still ADB problems continue to persist. I have tried everything I can possibly think or research via XDA but now I am out of ideas.
I have uninstalled and reinstalled ANDROID SDK 3 times 2 twice with "Accept-All" radio ticked and once with just the 2.1 and 2.2 goodies.
I have tried different cables none of which are stock. on every usb port on my computer all replicate the same issues: Adb devices shows up right but will not remount only run in shell. and when i run Adb shell it responds with $ first needing me to open su just to get the # symbol.
Any input is incredibly appreciated.
Click to expand...
Click to collapse
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
DevinXtreme said:
Code:
su
remount rw
We have a different method than the Hero did. If you've already tried that, lemme know. Works fine for me on stock rooted, Nebula, and (now) Bonsai.
Also, if that doesn't work, try it from a terminal app on the phone. I use it there more than anything.
Click to expand...
Click to collapse
Hey man thanks for your input, I really appreciate it. That didnt work either, on ADB or on Terminal Emulator. It responds correctly from both sources with:
Code:
remount rw
Remounting /system </dev/st19> in read/write mode
I am wondering if it has anything to do with the fact that the 64bit drivers dont install totally. this module called the "Abstract Control Module" hangs forever and doesn't install. However I ran over to my wifes 32 bit vista laptop where the drivers will install totally with no success either.
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.
DevinXtreme said:
Hrm... That's very strange. It's telling you that it is working. What is the error you get when trying to move stuff from there? So, after remount rw'ing, cp something into a system folder and post those results.
Your output for remount rw is correct, so let's see where that goes.
Click to expand...
Click to collapse
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
Bump again
Sent from my Epic
Okay since I'm not getting much love from the forum I'm guessing this is an uncommon occurance, in which case I am going to try one more thing before I send it back for a replacement. I am planning on going back to DI18 via odin then one click rooting. Then flashing the modem and other nessecary files to run 2.2 epic experience. Its the only possible thing I can think of that I haven't tried to address my problem. Thanks for the feedback I have gotten thus far.
Sent from my Epic
This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2
The e0pic and hero are way differentwhen it comes to adb
I was the same way lol I don't think adb works
Like I think the only way is to cp things
Sent from my SPH-D700 using XDA App
watermoore said:
Okay so here is what happened.
I just made a simple text file that was entitled "movetest.txt". I placed the file on the sdcard and used terminal emulator to push the files successfully to /system/etc
then I placed it in my C:/Android/tools dir and tried to adb push with no success so I ran shell and was able to succeed via shell here to the fonts dir in system.... here is the code:
Code:
c:\Android\tools> adb push movetest.txt /system/fonts
failed to copy 'movetest.txt' to '/system/fonts/movetest.txt': Permission denied
c:\Android\tools>adb shell
$ su
su
# cp /sdcard/movetest.txt /system/fonts
cp /sdcard/movetest.txt /system/fonts
#
Click to expand...
Click to collapse
That last one appears to have worked. Check and see if movetest.txt is in /system/fonts. If so, then you're in business. Just copy stuff across as root instead of pushing.
Well now I can use ADB fully. I odined back to stock then used the one click clockwork 3.0.0.05 ext4 batch then flashed Truley Epic Rebirth 1.2 and was able to remount correctly, push and pull all the way down to the root dir. I am not sure what changed but it just all of the sudden started working.... I'll take that lol
mirth18 said:
This post helped me: http://forum.xda-developers.com/showpost.php?p=8723568&postcount=2
Click to expand...
Click to collapse
Well my issue was a bit different. I could get it show up with the "devices" command. When I tried to "adb remount" it would deny me. It would reply with "device not found". Which is really wierd because I could ADB shell with root access any day of the week. I just had to change my process to accommodate the limitation.
I would just ADB push files to the sdcard, mount into shell to gain full root permissions then finish my work.
Kind of a strange round about way of going about it but I learned quite a bit more linux commands that way lol
Fyi.. I am using ubuntu 11.04
Sent from my SPH-D700 using XDA App
Hello XDA Giants of the Modding world I guess I'll start by saying i am a sorta work in progress rather than a noob. i say that for 2 reasons. a) I have converted over here for awhile from (hopefully you call us this) your friends over at modmyobile. i have burned myself out on my good old cliq 2 and have actually surpassed some very well known devs over there on the modding of the mb611. But sadly, that is close to my extent of knowledge; well that and the nook color aka encore and the cliq mb200 a little. and b) when i went into this section (the q & a thread) i got a headache real fast. But i would suppose i belong here to give someone else a headache until i dont have post restrictions. ok, on to my ordeal...
Through here I successfully downgraded and temp rooted howevs my giant devs, i cannot seem to figure out what it is im missing to the last steps. let me try to do specifics here- i followed this - [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo. i was not able to get the platform tool kit or whatever its called but i found files elsewhere to ride it out andd low and behold i got all the way to Android 2.2.1 and ready to s-off perm root this baby im stuck here-
> adb push psneuter /data/local/tmp/ <---it says cant find that file does not exist
> adb push gfree /data/local/tmp/
> adb push busybox /data/local/tmp/
> adb push hboot-eng.img /data/local/tmp/ <---Im pretty sure i dont have this one either
> adb push root_psn /data/local/tmp/ <---or this one
> adb push su /sdcard/
> adb push Superuser.apk /sdcard/
> adb shell chmod 755 /data/local/tmp/*
> adb push recovery-clockwork-5.0.2.0-glacier.img /data/local/tmp/recovery.img <---this one is not with me anywhere either
> adb shell /data/local/tmp/psneuter
Im sorta thinkin it was the "downgrading rooting tools" download that i couldnt get to download. i would have just asked on that thread but im not allowed to for a bit. if any of you could help me out i would totally let you hang out with a couple of hot wifies i know... or just say thank you and bless your little heart
UrWifesBoyfriend said:
Hello XDA Giants of the Modding world I guess I'll start by saying i am a sorta work in progress rather than a noob. i say that for 2 reasons. a) I have converted over here for awhile from (hopefully you call us this) your friends over at modmyobile. i have burned myself out on my good old cliq 2 and have actually surpassed some very well known devs over there on the modding of the mb611. But sadly, that is close to my extent of knowledge; well that and the nook color aka encore and the cliq mb200 a little. and b) when i went into this section (the q & a thread) i got a headache real fast. But i would suppose i belong here to give someone else a headache until i dont have post restrictions. ok, on to my ordeal...
Through here I successfully downgraded and temp rooted howevs my giant devs, i cannot seem to figure out what it is im missing to the last steps. let me try to do specifics here- i followed this - [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo. i was not able to get the platform tool kit or whatever its called but i found files elsewhere to ride it out andd low and behold i got all the way to Android 2.2.1 and ready to s-off perm root this baby im stuck here-
> adb push psneuter /data/local/tmp/ <---it says cant find that file does not exist
> adb push gfree /data/local/tmp/
> adb push busybox /data/local/tmp/
> adb push hboot-eng.img /data/local/tmp/ <---Im pretty sure i dont have this one either
> adb push root_psn /data/local/tmp/ <---or this one
> adb push su /sdcard/
> adb push Superuser.apk /sdcard/
> adb shell chmod 755 /data/local/tmp/*
> adb push recovery-clockwork-5.0.2.0-glacier.img /data/local/tmp/recovery.img <---this one is not with me anywhere either
> adb shell /data/local/tmp/psneuter
Im sorta thinkin it was the "downgrading rooting tools" download that i couldnt get to download. i would have just asked on that thread but im not allowed to for a bit. if any of you could help me out i would totally let you hang out with a couple of hot wifies i know... or just say thank you and bless your little heart
Click to expand...
Click to collapse
Anything you need you can get here.
http://wiki.cyanogenmod.org/w/Install_CM_for_glacier#Rooting_the_HTC_Glacier
thanks a ton
garleest said:
Anything you need you can get here.
Yup, this site is awesome! Thanks Garleest for that quick and accurate response so I've checked out a few roms so far and I'm clear on the annoying question "what's the best rom?" So I guess I'll just twist it a little and ask, are there a few that stand out from all these gazillions of choices here that u or anyone would recommend I try out? I might get these names wrong but I am on the darkside cm 7.2 right now. And I tried out (very shortly) ummm, lets see here... darkhorse was one, packable and aospx or something like that... thanks in advance
Click to expand...
Click to collapse