Develop Bugs

newbie Question about root

after rooting, unlocking nand etc.
do I still have to reboot in to recovery with "recovery-windows.bat", or should I be able to do it without it????
thanks for answering

I'm a new too, but I don't think you need it. If you install a custom recovery and select 'Recovery' from the bootloader, it should launch your custom recovery. If you want to get to recovery without going into the bootloader, check out Quick Boot. It's much easier than going through the bootloader.

Provided you flashed a custom recovery you do not need to use a computer to boot into recovery

thanx for your replies
can you please post a link how to flash recovery and which

bklynfire said:
thanx for your replies
can you please post a link how to flash recovery and which
Click to expand...
Click to collapse
I personally like the AmonRA recovery because of the easy navigation using the few buttons we have. Others prefer Clockwork; though with that one, some have noticed that when wiping,the recovery doesn't exactly wipe completely (or something to that effect, I could be wrong). Try downloading ROM Manager, from there you can flash Clockwork or an alternative recovery, which would be AmonRA. Otherwise, go to the Development forum and search for how to flash AmonRA recovery.

horiveira said:
I personally like the AmonRA recovery because of the easy navigation using the few buttons we have. Others prefer Clockwork; though with that one, some have noticed that when wiping,the recovery doesn't exactly wipe completely (or something to that effect, I could be wrong). Try downloading ROM Manager, from there you can flash Clockwork or an alternative recovery, which would be AmonRA. Otherwise, go to the Development forum and search for how to flash AmonRA recovery.
Click to expand...
Click to collapse
I am trying to use rom manager i get this error
"an error occurred while attempting to run privileged commands"

bklynfire said:
I am trying to use rom manager i get this error
"an error occurred while attempting to run privileged commands"
Click to expand...
Click to collapse
I don't know much about Clockwork, but that message makes it sound like you don't have full root.

Are you root yet? If so, did you give ROM Manager su (super user) permission?

i rooted fine i think (cuz I added foreign fonts succesfuly)
how would I check it
???

if you have your phone connected to your computer and adb running proper
from a command line run
adb shell
Click to expand...
Click to collapse
should return
$
Click to expand...
Click to collapse
type
$ su
Click to expand...
Click to collapse
press enter and it should change to
#
Click to expand...
Click to collapse
if you dont see a # or you get a "permission denied" youre not root. try again.

nenn said:
if you have your phone connected to your computer and adb running proper
from a command line run
should return type
press enter and it should change to
if you dont see a # or you get a "permission denied" youre not root. try again.
Click to expand...
Click to collapse
this is what i got
C:\androidsdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# su
su
#

Why "Read-only file system" message?

this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!

dialbat said:
this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!
Click to expand...
Click to collapse
You're in recovery mode right? I rooted before the tmobile update so I used the original method not the one you're using. I assume that for the most part you need to have your phone in recovery mode.
The /system/ directory is read only unless you're in recovery and I believe that's were that method attempts to write. You usually only get that message when you attempt to write to the system when not in recovery.

Thank you, but there is not a single word about puting phone into recovery mode in the instructions. Unless they mean it my default
i will try though.

Yeah, some steps are left out in certain 'common' tasks like rooting. It's assumed to be common knowledge or that if you don't know to automatically do a step then maybe you shouldn't be attempting it. At least that's the feeling I get sometimes but that's why it's important to search and ask if you don't find the answer.

Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App

If it's under/system, you need to be in recovery. I rooted with the original method though, so I can't really tell you much.

guitarist5122 said:
Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.

Well, i've followed steps to the point. I have rooted my phone before, so even though i am a newbe, i do have a general idea of the process.
But i have no idea why it just won't work for me.
I have tried putting it into recovery using loop script, otherwise it just states that it's in recovery and still won't let me write to it

KCRic said:
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.
Click to expand...
Click to collapse
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App

guitarist5122 said:
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Hmm... Allow me to copy and paste a few lines from that thread, written by the developer:
1:After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
2:Important: If you do nothing after step 12 then you are not "rooted." This program grants itself root permissions in a shell, that is ALL. If you want system-wide root access (what most people consider "rooted"), you MUST flash a custom ROM since the NAND protection on our device prevents us from giving global root access while inside the ROM. When following Eugene's instructions on flashing ENG, make note to NOT run the command 'su' if you already have a pound symbol (#) at your command prompt!
Basically, this 'root' method is actually a program that allows you to flash the ENG package to give you root. By itself, the program does nothing but allow you to operate inside the shell as root for a short time. Sort of like the 'sudo' command in linux - at least from what I can tell.

I'm aware of what the developer said. I'm also aware that I disregarded not having the phone booted since it would be a little tough to toggle wifi without being booted. If you don't believe it can be done, do a nandroid backup and unroot your phone and try rerooting. Pushing exploid and do the root whole process before flashing the eng-build while booted. Or just take my word. Personally I figure out for the life of me how anyone toggles the wifi (which is one of the steps) if not fully booted.
I don't argue just to be right. I just don't want people to be given incorrect info and never solve their problem. Rooting and can be frustrating on this phone if your not too familiar with rooting or using command prompt.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I wan't saying the files can't be pushed while it's on, I've done that before but NAND will undo or not complete it once you reboot. It's the same reason that you can't delete a system app while the slide is booted - well you can but it will still be there, and once you reboot the delete is undone - unless you're in recovery.
All I was saying is that it's not a permanent write to the system, if that's where it's even being pushed and he still has to flash the ENG build to gain full root. I think this guy needs to just redo the steps, maybe read the old root methods to gain some insight too. It might help.
btw, I think there actually is a command to toggle wifi through adb, not sure if it does much in recovery or not. Also, not a chance in hell am I going to unroot - it was a pain in the a** catching my phone in recovery even when I used the loop.bat file

Good to know that's why my apps didn't stay deleted.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?

Thainfamous20v said:
I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?
Click to expand...
Click to collapse
rm, rm -f or any other commmands will not work with terminal emulator because in order to use that program you phone has to be on, and since we can only write to the /system in recovery I'm sure you see what I'm getting at. You can still pull from the /system when the phone is on. The command isn't 'pull' though, it's:
Code:
cp <path to file> <location to copy to>
As far as the unroot thing, use the search bar [slide rom bible].

just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?

PunkRockJesus said:
just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?
Click to expand...
Click to collapse
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App

guitarist5122 said:
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, windows uses \ for local and local network file paths, it only uses / for remote locations and networks.
I'm not sure if this would work without already having root (I received my phone already rooted, never had to do it)
In command prompt, try
adb remount
You can also try this:
adb shell mount -o rw,remount /sqlite_stmt_journals
See if any of those work. Like I said, it may not, since those might be things that need root.

Any updates on this? I cannot push the file either. And "adb shell mount -o rw,remount /sqlite_stmt_journals" does nothing.

[Guide] How to recover your semi-brick

YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html

before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?

Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.

I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App

Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App

renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.

you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.

Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA

Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.

reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?

{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.

fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.

Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?

im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...

-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....

^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!

marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?

it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file

fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?

[Q] Noob Question

Okay, I am getting ready to root my phone tonight...
As far as all that - I think I got all that covered.
As far as flashing a recovery - I want to use amon-ra's - RA-evo-v1.8.0 found here - http://forum.xda-developers.com/showthread.php?t=705026
In that post it gives two differant ways to flash the recovery:
via fastboot
Code:
Copy recovery-RA-evo-v1.8.0.img to a location where fastboot can find it.
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
via terminal app or adb => Make sure your rom contains flash_image!!
Code:
Copy recovery-RA-evo-v1.8.0.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
My questions are:
first of all - what is "Fastboot"?? I mean is it an application that I can download and install it this way?
second of all - what is a "terminal app"
&
third - what is "adb"?
I keep hearing the term "shell", is a "shell" the same as windows command prompt? Or is that "adb"?
I know these are probably stupid questions for most, but I like to have every thing ready to go before I tackle projects...
Any guidance would be greatly appriciated!!
J

Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.

terrel_b said:
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
Click to expand...
Click to collapse
Great, thanks for the response! That helps alot - I searched around a little while waiting for a reply and still didnt clear any thing up. I have already DL'd ROM Manager and I will just use that... I just like to have as much info as I can...
Thank you!
J

How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically

fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask

ifly4vamerica said:
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
Click to expand...
Click to collapse
Im using unrevoked... I am still running hboot 0.97.0000... thanks for the input, I appriciate it!!
J

roscoenr said:
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
Click to expand...
Click to collapse
Very helpful info - thanks!! I have already DL'd ROM Manger Pro...

Okay - another question, can i place the amon-ra recovery on the SD card BEFORE i root the phone or should I do that AFTER I root the phone? Just curious, I dont even know if it matters one way or the other... Just want to be sure before I do it...

Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...

JayStation3 said:
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
Click to expand...
Click to collapse
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.

alekosy said:
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
Click to expand...
Click to collapse
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...

JayStation3 said:
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
Click to expand...
Click to collapse
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026

alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
Everything is there, pretty much solid on the information. I hope it works out for you, if not don't RUSH and take your sweet old time browsing the forums for help. GL

Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell

alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
cool, I will read them and figure it all out... thanks for the info... i flashed amon ra last night, did a back up w/ TB... did a NAND back up through the recovery of the phone... Im just a little confused on the differant recoveries...

Jbcarrera said:
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I thought I did reboot at least once, when I was preforming the NAND back up - but Im rebooting now and I will test it out again...
I do not have great 4G signal here at my house, so that may be it as well... I will mess with it and see whats up through out the day and let you know tonight...
I have noticed that my touch screen doesnt seem as responsive as it was and the phone in general is kind of glichy...

Ok, my 4G is still working... I must not have had a strong enuf signal at my house for it to kick in... No I'm having problems getting tether to work... I started a new thread on that one though...
Sent from the MATRIX... while plugged into my EVO... using the XDA app... from a galaxy far-far away.......

[Q] Were can I get original Stock Firmware for H815?

as file for download?
Thank you.
Best regards.

I've managed to kill mine worse than that, I cant get it to boot now after installing xposed framework 64bit, I can still get into TWRP recovery... Can't believe I didn't do a nandroid before I really started to play around. Oh well I'll live and learn!
I've gone through the steps to remove the xposed files but still having the same issues.
had to mount system with adb shell
mount /system/ to do the manual file deletions and renames

Same reason.
Nandroid will not help you.
I've made a Nandroid-Backup, but restore fails.
Please tell, if you have a solution.

Just wondering if your nandroid restore is failing because system is not mounted RW, have you tried mounting it whilst connected to a pc and issuing the following
adb shell
mount /system/
system should be now mounted rw in TWRP as well

What have I exactly to write, please?

mystery007 said:
What have I exactly to write, please?
Click to expand...
Click to collapse
In ADB Sideload mode, you need to write as above...
Mine is also dead, but Recovery is still there.

My battery is empty
Loading this is difficult, while the phone is on and can not get off.
Always after connecting the phone reboots and is very hot, so charging is very slowly.

DarthEwok said:
I've managed to kill mine worse than that, I cant get it to boot now after installing xposed framework 64bit, I can still get into TWRP recovery... Can't believe I didn't do a nandroid before I really started to play around. Oh well I'll live and learn!
I've gone through the steps to remove the xposed files but still having the same issues.
had to mount system with adb shell
mount /system/ to do the manual file deletions and renames
Click to expand...
Click to collapse
Find someone who hasn't yet flashed xpos ed and ask them to pull the system partition. Then have them upload it so you can download and flash via fastboot

macdaddie87 said:
Find someone who hasn't yet flashed xpos ed and ask them to pull the system partition. Then have them upload it so you can download and flash via fastboot
Click to expand...
Click to collapse
If anyone is willing, it would be appreciated.

DarthEwok said:
If anyone is willing, it would be appreciated.
Click to expand...
Click to collapse
If I had one I would.. Post something in the h815 boot loader unlock thread and ask them to pull their system. It would be beneficial to everyone who has a h815 until the kdz comes out

I'm not able to establish a connection between PC and Cellphone.
ADB: "error - device not found"
LGMobile Support Tool: Device is found but no further action (writes that all is right).
LG Brigde: Device not found
Windows 8.1 64bit
Drivers all changed from new to old and vice versa - now 3.13.2