Database Info

[Q] Rebooting to Bootstrap

I have been trolling the forums for awhile and I never post but this is something that I have not been able to come across. Why after I used the bootstrap app and load into the recovery menu that now every time I go to reboot my phone I automatically go into the recovery menu even after a successful boot? Hope I worded that right. Please help and thank you!!
just realized I am in the theme section. Can this be moved to the appropriate board. THANKS!!

That's the way it works, it hijacks the bootloader, trust me its a good thing. Bootloop, battery pull, recovery, restore backup. Several times I've been glad it works that way.
Sent from my DROIDX using XDA App

Wait. I have a normal reboot. Maybe mine is messed up?

Yeah I got that but I thought it was only if I pulled the battery after it bootlooped. It does it every reboot except after I flashed a "rom", but I didn't like the rom so I reverted back to stock. I mean its awesome to have the security blanket but it can also be a bad thing if my 14 yo cousin gets ahold of my phone then formats my system an then reboots. Thanks for the help by the way.
Sent from my DROIDX using XDA App

The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z

If you want to remove bootstrap, you can do SBF flash, which I did several times and it perfectly works.

Zaphod-Beeblebrox said:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
-Z
Click to expand...
Click to collapse
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Oh and thanks for the help by the way.
UPDATE:
So I think I found it.
Unroot and Remove Recovery Via RootExplorer

jkpair said:
Ok I understand completely I knew the process but did not quite understand. Now the last question, is the only way to remove it to flash or can I use a file manager to remove it?
Click to expand...
Click to collapse
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way

Zaphod-Beeblebrox said:
You can just delete it with a file manager (I am not sure about the permissions though .. you may need rootexplorer?)
I generally just do things like that from adb shell.
I KNOW I can delete it that way
Click to expand...
Click to collapse
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.

jkpair said:
so for adb shell it would be something like:
Code:
adb shell
cd /system/bin
rm -r hijack
If thats right I won't try unless I know for sure. I don't know why but I have just got into a habit of googling after I ask. Lol I think this is it: Easy way to remove Koush's recovery?
So the logwrapper is the main file that matters not the hijack file and the original logwrapper was renamed to logwrapper.bin so I just replace Koush's recovery logwrapper with the previous one by copying over it.
Once again thanks for the help. Seems the answer is always 42.
Click to expand...
Click to collapse
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.

Zaphod-Beeblebrox said:
I'm sorry, I misunderstood you goal here. I thought you wanted to keep the recovery, just fix it so it didn't come up on each reboot. If you are looking to completely remove the recovery, then I yes, I would follow the directions in the post you referenced, not the code section.
If you are only looking to 'fix' your reboot issues, I would suggest looking to see if /data/.recovery_mode exists on your phone. If it does, delete it. That's likely what is causing you to reboot into recovery each time.
Click to expand...
Click to collapse
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol

jkpair said:
Oh wow now I feel dumb. I thought I got it. So this would allow me to reboot and keep the recovery without it going into recovery every time I reboot. I hate asking noob questions lol
Click to expand...
Click to collapse
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.

Zaphod-Beeblebrox said:
Assuming that is the problem. There may be another reason that you are getting dumped into recovery each time, but I suspect this is it. I will say that it's not 'normal' for recovery to come up each time. It should only come up if you somehow stop the boot process mid-way (Battery pull, etc) or use the Bootstrap recovery program to set it to reboot in recovery (which basically just creates the data file in question).
I would suggest you work through fixing this problem rather than just getting rid of the recovery. It's quite a powerful tool.
Click to expand...
Click to collapse
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.

jkpair said:
Yeah I really don't want to rid myself of it. I do believe I have an understanding now I am going to give it a shot when I can leave work. I will come back and post results.
Awesome It worked like a charm. Deleted the .recovery_mode file and am now happy.
Thanks for replying so quickly before I decided to just go ahead and remove the recovery menu all together.
Click to expand...
Click to collapse
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App

DrewDanger said:
Where is this file located? Im having the same problem.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
From my earlier post:
The recovery works by looking for a file : /data/.recovery_mode
If it's there, then it goes into recovery mode, if not, then it allows for a normal boot.
However, if doing normal boot, it actually places the /data/.recovery_mode file and then erases it once the system is fully booted. I know this is confusing, but this is how it knows to go back into recovery if you did a battery pull (ie, the file was created, but never erased since you didn't complete the boot process).
All of this is supposed to happen automagically, but I've heard of that file sometimes getting 'stuck' and not deleted. Thus, causing you to reboot into recovery every time.
There is nothing inside the file, just an empty marker. You may want to delete that file and reboot. Should help.
Click to expand...
Click to collapse

I went through Astro and searched "/data/.recovery_mode" but it didnt bring up that file. I guess Im just confused at what exactly Im supposed to be looking for...

Yeah I ended up using a root file manager to do this was really easy. Just go the root menu and browse to data find recovery_mode and delete then reboot.
Oh and astro will not show what is in the data folder you have to get a root explorer app I think the one I used was android mate.
Sent from my DROIDX using XDA App

Ok cool I'll check that out. When I use Astro and go under "system" and scroll down it has a "recovery from boot" folder. Any idea what that is? When I open it there is a bunch of code script in it

Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?

DrewDanger said:
Ok I deleted that file and it fixed it. I think Im just gonna un-root it when I get off work. Im over all this, lol. I'll wait until the Droid has more development as far as root access and what you can do. Can I just do the un-root through the one -click-root I used?
Click to expand...
Click to collapse
Yeah it has an option to unroot, but I can't state whether or not this is the best method to remove the root. I acctually am keeping my root and bootloader. Yeah I will be glad when there is a true rom as well but progress is progress.

Rooted now how do I flash a rom?

My buddy got this phone I want to hook it up as he's not great with tech stuff i rooted with z4root and just need to know how to access recovery cause i didn't see a reinstall packages option in standard recovery ? Any help would be awesome thanks guys

I just rooted with Z4root... then I installed Titanium Backup and then ROM Manager, giving both apps root access (which I verified with the SuperUser app). In ROM Manager I did "Flash ClockworkMod Recovery" and chose the Fascinate option and was told that it downloaded the latest ClockworkMod Recovery. What's my next step?... Choose "Reboot into Recovery" within ROM Manager or do it another way. (My goal is to install Voodoo5 using the stock ROM for now. I have the Voodoo5 file on the SD card.)
EDIT: Whoops. I just realized that I had downloaded the two files to get CWM working but hadn't followed the unzipping, etc. instructions. I'd better go back and read that CWM thread again...

First get CWM working
Then check out this ROM
Or this ROM
and if you really wanna get fancy check out this kernel
Just in case you screw up
If you need more help on each specific topic, just ask in the appropriate areas and there is usually someone around that can answer questions.

Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?) EDIT: Just did this and it ran fine but it switched my Live wallpaper back to stock?!? WTF?

monthlymixcd said:
Thanks for the quick links... really appreciate it.
BTW - Titanium Backup asks for USB Debugging to be enabled... do you have to do this? It creates issues for me when connecting the phone as mass storage to my PC.
ALSO - I'm assuming I should take an initial backup with Ti before I get too far into this, right? Not having done a backup before... is Ti the best to use? (Do I just choose batch and pick an option(s)? Does choosing "Backup user apps + system data" backup game save data?)
Click to expand...
Click to collapse
Quick links are awesome! They save time, for sure.
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
I use TB to do my app and system data backups. Just run a batch backup on user apps and system data, like you said. That's the best option to start with. This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.

phidelt82 said:
Check the box to ask each time for mass storage and kies. Then you can have debugging enabled, and yes you have to have it enabled or TB won't do it's thing properly. You can switch it back and forth also. That's what I do.
Click to expand...
Click to collapse
Perfect. Thanks! Only thing is... USB dubugging doesn't stay ticked, it's ticked and Ti says it's not, or the connection still triggers a missing driver error message with Vista on the PC. Oh well.
phidelt82 said:
This isn't the same as a nandroid backup, but it's a good second choice for if you need to wipe data and restore apps quickly like a ROM install that requires you to wipe data/factory reset.
Click to expand...
Click to collapse
Easiest way to do a Nandroid backup? BTW - Ti backup ate up 5GB of my sd card?!? Yikes!
Also, regarding this thread:
phidelt82 said:
First get CWM working
Click to expand...
Click to collapse
I get "adb: not found"?

monthlymixcd said:
Perfect. Thanks!
Easiest way to do a Nandroid backup?
Also, regarding this thread:
I get "adb: not found"?
Click to expand...
Click to collapse
Nandroid backup will be there once you get CWM working.
You can do everything from the phone, just read down through the pages to find the people that have done it. They have left instructions using terminal emulator and root explorer. You will find that in a lot of instances many problems will have different ways of dealing with them. You probably don't have the Android SDK which is how you get ADB working on your computer. This isn't critical, it just makes it so that you will have to either install it or use the other means available. (ie terminal emulator and root explorer)

Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?

monthlymixcd said:
Still getting errors after trying several of the things in the thread... Q:I never did get a robot voice when I ran Z4root and never saw a place to choose permanent... should I run Z4root again? I mean, I was able to install Ti, etc. so I must have root, right? But I think my issues stem from not being able to get redbend_ua into the /system/xbin folder. Astro can't paste it there, Root Explorer can't paste it there, but in the terminal it appears like chmod worked... thoughts?
Click to expand...
Click to collapse
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App

phidelt82 said:
Root explorer needs to be mounted RW. There is a button at the top that will say RO or RW.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
EDIT: cd to /system/xbin worked and an ls shows the redbend_ua there but the chmod 777 redbend_ua fails to "Unable to chmod redbend_ua: No such file or directory
EDIT to the EDIT: Hang on... think I may have found where I went wrong. What's the terminal command for delete?

monthlymixcd said:
"Mounted as r/w"
I tried this. Used root explorer to finally get redbend_ua into system/xbin but when I try to run the commands in the post it cannot find redbend_ua. I also cannot cd into xbin within the emulator to ls ... says xbin not found. Explorer can see it there... what gives? do you have to restore redbend_ua inside the xbin directory or will it work to restore it elsewhere?
Click to expand...
Click to collapse
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App

Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol

willsnews said:
Isn't there anyway to flash a rom using odin ? If not are the codes the same for terminal emulator as they are for adb to get cwm working? I'm from the vibrant section of this site running nero v4 right now I have a good understanding of odin for the most part but this not having an easy recovery is bs lol
Click to expand...
Click to collapse
I've never flashed a ROM using Odin, but that doesn't mean that it can't be done. The process should be the same using terminal emulator or adb, just more of a pain. I agree it would be nice to have full CWM Recovery support (or any full recovery support) but I don't have the money to spend on a phone to send to Koush right now to get that done. As soon as I do, this will be done and then I'll have a tester phone for firmware builds. It really isn't that difficult to get it working, though. I've done it probably 30-40 times now and even the first time the only flub was in a typo for the second to last character (thought it was a 1 and not an L)

So you type this stuff in all in one line or what?

willsnews said:
So you type this stuff in all in one line or what?
Click to expand...
Click to collapse
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.

phidelt82 said:
Are you doing /system/xbin? The first / is important. You don't need to cd to xbin, though.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.

monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
I can't remember if Astro has R/W options for the root directory. That may be the problem.

phidelt82 said:
Depending on which parts you are talking about, yes. Each new line is a line of code. If it moves to a new line, hit enter.
Click to expand...
Click to collapse
I just ned to get a custom recovery how did you type it in to terminal emulator? Like extacy how?i just dont want to mess up my buddies phone I want yo hook him up not **** him up lol

monthlymixcd said:
Yes. Something's definitely up 'cause when I try to use Astro to copy redbend_ua to /system/xbin the paste option is grayed out for that directory.
Click to expand...
Click to collapse
You guys are confusing the hell outta me I don't know who's answering me and who's answering you I know this pertains to this thread but im right in the middle of this process and its not even my phone

I apologize for the derail... I got mine working. I had a typo. I'm off to voodoo.

I need an easier guide...

To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...

I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though

I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.

DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate

My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...

DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt

I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?

DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have

How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?

DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium

I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"

DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium

You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone

DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium

If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?

DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium

Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/

DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium

Is there perhaps any way to perform a ROM backup with ADB?

DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium

Need help - stupid mistake

Well to make it short and simple. I did a factory reset on my tablet and i had seanz rom running. Now all it did was just get stuck at the nexus loading screen. I went into cwm and wiped everything out. So now it gets stuck at the asus boot screen. I don't have a backup in my tablets internal storage. So im trying to use my sd card. But I can't figure out how to get CWM to read my sdcard. Is there anyway i can fix this problem?

1. Wrong forum. This should be in the Q&A section.
2. CWM (and TWRP for that matter) does not support the external SD card. You will have to ADB push the ROM you want to flash to your internal storage. There are lots of threads in the TF300 section about doing so, filled with instructions and troubleshooting tips.

EndlessDissent said:
1. Wrong forum. This should be in the Q&A section.
2. CWM (and TWRP for that matter) does not support the external SD card. You will have to ADB push the ROM you want to flash to your internal storage. There are lots of threads in the TF300 section about doing so, filled with instructions and troubleshooting tips.
Click to expand...
Click to collapse
Sorry about that. I'll go check it out thanks. Feel free to move or delete the thread.

cmw at the moment doesn't support external sdcards. go into recovery and adb push c:\romfolder\rom.zip /sdcard
Sent from my ASUS Transformer Pad TF300T

Hey heres a tutoral I wrote for flashing back to stock or if stuck between roms

currently adb pushing file to sd card. Ill post back with an update
UPDATE: so I did an adb push of the rom file, but when i go to search for the file, CWM tells me: couldn't open directory, no files found

if all fails then try using adb in linux, most likely a ubuntu live cd(which is free).
Sent from my ASUS Transformer Pad TF300T

joshrod921 said:
currently adb pushing file to sd card. Ill post back with an update
UPDATE: so I did an adb push of the rom file, but when i go to search for the file, CWM tells me: couldn't open directory, no files found
Click to expand...
Click to collapse
I know it sounds weird, but at time when i did it id go looking for the file and it was no where to be found but if you push the file twice it will show up in the folder you selected, it had me a bit worried when i was doing it and couldnt find it, but trust me it works

d_crossfader said:
I know it sounds weird, but at time when i did it id go looking for the file and it was no where to be found but if you push the file twice it will show up in the folder you selected, it had me a bit worried when i was doing it and couldnt find it, but trust me it works
Click to expand...
Click to collapse
I'll try that and see if it works. If not im gonna use ubuntu and try it there. This really sucks for me lol.

Got it working woot!!!!!!
I found someones post here: http://forum.xda-developers.com/archive/index.php/t-1601802.html
in a nutshell, i pushed the blob file of the rom, then used this command as told in the instructions: adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4. I rebooted and bam back to stock completely. Now to flash Seanz rom and make a rom folder in my storage. Thanks everyone for your help!

joshrod921 said:
Got it working woot!!!!!!
I found someones post here: http://forum.xda-developers.com/archive/index.php/t-1601802.html
in a nutshell, i pushed the blob file of the rom, then used this command as told in the instructions: adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4. I rebooted and bam back to stock completely. Now to flash Seanz rom and make a rom folder in my storage. Thanks everyone for your help!
Click to expand...
Click to collapse
Congrats I know the relief !

d_crossfader said:
Congrats I know the relief !
Click to expand...
Click to collapse
I'm glad its working now. I'm leaving for a week long trip Sunday, and I was planning on bringing my tablet with me. Learning from my mistake and moving on.

Odin stuck at "recovery.img" on Tab 2 10.1

Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan

SlickAl41 said:
Hey guys. I admit it....I'm a noob here (man it hurts to say that).
Anyway, I've been attempting to root my Tab 2 10.1 (P5113 w/ 4.0.4 upgrade) using the method weltwon describes here: thread 1657056 and I keep running into the following problem. When attempting to root it Odin keeps getting stuck at the "recovery.img" step (I've let the tablet sit for nearly 30 minutes at that step with no luck).
Based on some other posts I've attempted all the following with no luck:
Removed Lockout Security & Antivirus from the tablet
Disabled antivirus on the computer
Ensured the tablet is directly plugged into a motherboard usb port
Nothing has helped. The only thing I haven't tried is shifting to a different computer (only have a single computer at home). Fortunately I can force reboot the tablet and it comes back up to the stock ROM with no issues.
I'm using Odin V1.85_3 and running Windows 7 64-bit. Any ideas would be greatly appreciated.
Alan
Click to expand...
Click to collapse
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.

If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.

Ryanscool said:
Keep trying... odin sucks. Heimdale is better, but it is a little more complicated lol still figuring it out on my end with my infuse every once in a while.
Click to expand...
Click to collapse
Heimdall did it. Thanks for pointing me that direction. :highfive:

SlickAl41 said:
Heimdall did it. Thanks for pointing me that direction. :highfive:
Click to expand...
Click to collapse
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan

SlickAl41 said:
Well, I thought Heimdall did it. Guess I celebrated a bit early there. When attempting to boot into CWM I get thrown over to the Stock Android Recovery. Based on some more searching it looks like I'll have to roll back to 4.0.3 before flashing recovery.img. Back to the web and to figure that portion out.
Alan
Click to expand...
Click to collapse
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.

Ryan79 said:
Alan, that's because the tabs have a script called install-recovery.sh that re-installs the stock recovery on each boot. you will need to find and remove that before the recovery flash will hold.
trying to find the thread that talked about where that script is located.... but if you have root explorer installed search and you'll find it. I would suggest saving a copy of it to the sdcard before removing it from the system... just incase it is ever needed for anything.
Click to expand...
Click to collapse
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.

SlickAl41 said:
Ok, now I feel like my head is starting to spin. The script is located in /etc (not to surprising there). This is where my head starts to spin. /etc has permissions of 777 (which rather blew my mind based on past unix and linux experience). Install.recover.sh has permissions of 544 which I would expect for an executable in /etc. That means I have to have root permissions to modifiy the file since root is the owner.
So, from my understanding I need to get CWM recovery installed so I can flash cwm-root which will grant me root access......seems kinda like a case of the chicken and the egg to me.
Click to expand...
Click to collapse
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan

SlickAl41 said:
Ok, I think I may see how to get around this.....Heimdall is rebooting my tablet after the recovery flash. Need to figure out the command line parameter that prevents reboot and then reboot directly to CWM Recover (guessing there but that's what I'm going to look for at least).
That did it.....found the --no-reboot common argument for Heimdall and then manually rebooted directly to CWM Recovery. That allowed me to boot into CWM Recovery without the install.recover.sh shell running. Waiting for first reboot after flashing the CWM-Root.....rebooted installed SuperUser and disabled SuperSU but still can't rename or delete the /etc/Install.recover.sh (even though the root browser was given su permissions by SuperUser) ..... sigh
I know I'm rooted because I can reboot using Quick Boot after granting it su access - that's just strange.
Finally, figured it out...You can't modify or delete Install.recover.sh in /etc. You must do it at the following location /system/etc
Alan
Click to expand...
Click to collapse
Hey Alan, sorry... been away from the forums for a couple days. But it looks like you got it figured out you are correct on the Heimdall command, the only thing different that I did is that I already had root explorer purchased... so after the SuperUser install I just ran it to move the install_recover.sh to my SD card
Glad to hear you got it working!

I am trying to Flash the Stock ROM on my Galaxy Y PRO after it is gone into a bootloop (by itself), i am using ODIN , but it got stuck on Flashin the recovery img
i tried all The USB ports of my computer and only 1 worked. Please i need help and a sure answer thx

MultipleMonomials said:
If nothing else works you might be able to restore to stock... but I agree Heimdall is a better option.
Click to expand...
Click to collapse
How to use Heimdall when I have bl, ap, etc