Database Develop

Recovery Gone No ADB Please Help

I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3

crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
Sounds like you need to flash a good hardSPL in terminal and then with fastboot-usb, flash recovery.

Hard SPL
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.

crxforya said:
Do you know where I can find a good one. And doesnt it require me to have a working recovery in-order to flash the spl???
thanks for your response.
Click to expand...
Click to collapse
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
NOTE: Here's a good Wiki on SAFELY flashing hboot/radio/recovery images that I found in Firerat's sig. As someone who has bricked a G1 by willy-nilly flashing, I implore you to have a look-see:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream_Bootloader

rynosaur said:
Anything that can be flashed in recovery/console/terminal can be flashed (more safely, according to lbcoder, ezterry, etc) in fastboot-usb. So you want to use the .img file out of this zip and flash it in fastboot to the hboot partition. This spl is a recoded sapphire 2005 hboot, made to look like 2004 -- for DVT board 32As, but less risk of crossing wires with radio, AFAIK. The second one is just a straight-up 2009, which is pretty current. I assume you have a Sapphire MT3G, not a Magic MT3G (Fender/v1.2) because I wouldn't count on these files working for you. If you happen to have DangerSPL installed (although that's not necessary with MT3G) check the rooting/SPL instructions on that forum to make sure these files are right. Good luck!
Click to expand...
Click to collapse
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue

Firerat said:
BUT, no adb , so chances are no fastboot..........
OP needs to get over the adb issue
Click to expand...
Click to collapse
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?

Ill have to check
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???

crxforya said:
I have used adb before but Im not at my personal computer so I am not able to utilize the adb shell, and the computer that I am using, I do not have access to install. Is there another option that does not require adb, or is there a reason that I cant flash a sappimg file unroot, and start over???
Click to expand...
Click to collapse
No problem at all doing that, nbh overwrites radio, hboot, recovery. Just make sure you have the rooting files stored locally, i.e. custom rom, custom recovery, custom/hard/eng SPL, new radio, recovery test keys, etc.

crxforya said:
because I dont have access to install adb at my location.
Click to expand...
Click to collapse
rynosaur said:
Hmmm, I remember that way back in the day, JF included native ADB access in first custom RC30 Roms and then he packaged it into his custom recovery, but I don't know if losing a recovery image means losing ADB access and therefore fastboot access whatsoever?
Click to expand...
Click to collapse
did you read the post?
no adb = no fastboot
@crxforya'
your best bet is
Code:
su
ash
flash_image recovery /sdcard/recovery.img
if it fails, scroll up with track ball, and hit enter again, repeat until it works

crxforya said:
I tried to flash the new recovery image for Amon- Ra and I have now lost my recovery image. I did see the thread giving instructions on possible fixes and it seemed to work for some, but I am having no luck, because I dont have access to install adb at my location.
On to my problem I am now not able to update any of my apps, and I was not able to un-root to start over. I have tried many different times through the console (terminal emulator) to reflash the proper image, but I have had no luck. So now i feel i screwed myself, because I was not able to get firerats script to work. Can anyone help me with this.
I have a Mytouch 3g I have stock radio and spl 8g cls 6 sd running superbad 1.3
Click to expand...
Click to collapse
read this it might help it did for me when i try 2 use ROM MANAGER APP n i lost my recovery-->>> http://forum.cyanogenmod.com/index....toasted-not-bricked-phone-thread/page__st__40

No luck
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.

ur recovery is corrupted try this
To boot into fastboot you need to hold back and power.
Then plug the original usb cable into your pc then into phone. your phone should say FASTBOOT USB
If not you will have to use USB deview (a few posts above). Then using it unistall anything that says Android or HTC or ADB or Fastboot... You get the idea.
Then unplug and replug the usb cable to your pc.
Windows should say that there is an unrecognised item or something, go into device manager and there should be one with an "!" mark, or a wizard to install the drivers appears.
When it asks you where to find drivers, click the option that says select where the drivers are (advanced), or something. Then point it to the folder were the USB drivers are and let it do its work.
After its finished start cmd and use the command "cd" to go to the tools folder where your sdk is extracted if it was at "C:\android-sdk-windows\tools" you would type in cmd "cd C:\android-sdk-windows\tools"
Then put in "fastboot devices" and it should give you your phones serial number, as long as the drivers work and you are in fastboot (phone should say FASTBOOT USB)
If that works we are back on track
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok now download the latest Amon_Ra recovery XDA link
Now check the md5 using this tiny standalone app Download.cnet.com link this is self explanatory, as the md5 sum is on the XDA link.
Ok, so now you have checked that its not corrupted, move the .img file to the tools folder. For me it would be "C:\android-sdk-windows\tools" . (The .img file needs to be where the fastboot.exe is, so it finds it.)
Now this is where you get the stuff you type in to cmd.
Fastboot devices
Fastboot erase recovery
Fastboot flash recovery recovery-RA-dream-v1.7.0.img
Click to expand...
Click to collapse

same problem
i have the same problem except i have danger spl, i noobed it up and tried to flash recovery with cm 5.0.7...
i tried to flash the recovery a bunch of times, and i treid to get into fastboot, but idk where the drivers are, and idk how to find them.
help plz

crxforya said:
Thanks for your help Firerat, It seems that everytime I hit enter to flash recovery it just gives me another command line. Ive done it about 30 times and doesnt appear that its gonna take. Do you know what I would need to do to unroot, and start over. I looked at the Unlockr website and the process with the NBH file looks like it works until i reboot and it is still 2.1. Any help there I really appreciate it.
Click to expand...
Click to collapse
ok, thats interesting
straight after you do that
logcat
<track ball> then c
( or in terminal preferences, change the control key )
I'm guessing you see
I/flash_image( 2410): header is the same, not flashing recovery
so, try flashing a different version ( 1.6.2 ) , then 1.7.0
edit: or
Code:
erase_image recovery
flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img

I need to start over
What does changing the control key do??? I know Im a noob!! Sorry and thanks for your help

Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App

Well im back at the out of memory messg
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???

crxforya said:
well after erasing recovery and trying to reflash on the 3rd time it gave me the out of memory error again. Now that script you made Fire do i just
su
sh firstboot.txt and your script will work???
Click to expand...
Click to collapse
well, I have a spaming script here
http://forum.cyanogenmod.com/index.php?/topic/3867-broke-recovery/page__view__findpost__p__39273
spamming the flash in CM5 seems to be working for most
Code:
#!/system/bin/sh
test=1
while [ "$test" = "1" ];do
flash_image recovery /sdcard/recovery.img
test=`echo $?`
done
echo "we got there in the end....."
[attachment=1106:spamflash.txt]
get that onto your sdcard
rename the recovery image to recovery.img and put on the sdcard
then
Code:
su
sh /sdcard/spamflash.txt
that will keep trying to flash until it works
another way is to flash before android starts ( plenty of free memory available )
this is a firstboot.sh script
Code:
flash_image recovery /data/recovery.img
if [ "$?" = "0" ];
then
rm /data/recovery.img
echo "recovery flashed"
else
echo "recovery flash failed..."
fi
[attachment=1107:firstboot.txt]
get that onto your sdcard
then
Code:
su
cp /sdcard/firstboot.txt /data/firstboot.sh
again rename the recovery image to recovery.img, but for this method you need to put it on /data/
It will 'self clean', i.e. if it works it will delete the recovery image, and the bit which runs the firstboot.sh deletes that ( but it will delete that regardless of it working or not )
Click to expand...
Click to collapse

deltawye said:
Same problem here, on mt3g with latest super bad. I no longer have recovery and cant seem to flash one. And the latest amon-ra says not to flash from terminal if using latest cyanogenmod, yet my computer doesn't recognize my device, so I cant use adb.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
When my phone does not recognize the USB connection I simply reboot my G1 while the USB is is still connected and that seems work for some odd reason.

I had the same problem. All I did was install rom manager, flash the rom manager recovery nothing. From there flash RA- recovery nothing and then did that back and fourth until it worked I also tried flashing it with one click root hope all help. Also tried the terminal. Hope you fine a way. Good luck!!!!!!!
-------------------------------------
Sent via the XDA Tapatalk App

[Q] Stuck in boot loop, unable to access recovery

(I'm running CM 6.1)
I recently tried to use Titanium Backup to delete Gmail from my phone so I could install the new version (it kept giving me an error during installation), but when the phone reset to complete the uninstallation it gets stuck at a screen that shows an Android coming out of a box with a progress bar at the bottom. The bar fills up to about a quarter then flashes and restarts again. I can hit some buttons and this text comes up:
ClockworkMod Recovery v.2.5.0.1
Finding update package...
Opening update package..
Verifying update package..
Installing update..
(then it restarts)
This is preventing me from booting into recovery, or doing a hard reset, or anything really. It comes up right away when I start my phone up. Has anybody had any experience with this? Please tell me there's a way around this..
EDIT: ISSUE SOLVED!
This was pretty easy to get around, I wasn't too familiar with adb so it made it pretty difficult.
-Download a new recovery ROM if necessary
-Move the image to your android-sdk/platform-tools folder
-open up a command prompt, navigate to the platform-tools folder and enter the following code
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard/
adb flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
adb reboot recovery
-Then when that reboots your phone it should put you back into the recovery ROM and from there you can access your phone as usual.

i had a problem similar to this when trying to upgrade to a froyo rom (it wasn't a boot loop, but the progress bar would get about halfway and then freeze). i started the phone and held 'home' and 'back' and selected 'clear data' and then was able to reinstall. i see a lot around here that people have problems if their battery is too low as well...so if you're under 30% you might try charging and trying again

The problem is that I can't do anything when it boots up because it goes right to this progress bar screen, holding Home+back then Power doesn't do anything, same with any other button combination. Also the battery's at 100%, I charged it overnight to see if that was the problem but it didn't help.

Remove the battery, put it back in, hold down the home button when you start the phone - that should take you into recovery.

It doesn't though, when I say nothing works I mean nothing works. I've booted into recovery many times before but now this screen comes up every time I start it regardless of what button combination I try.

Then your only option would be to RUU and re-root. Have you tried that?

I just tried, but my phone is basically in a vegetative state right now, my computer doesn't recognize it when it's plugged in because of this loading screen thing that keeps repeating. I was thinking about getting a new phone for Christmas, maybe this is a sign

explosivo98 said:
I just tried, but my phone is basically in a vegetative state right now, my computer doesn't recognize it when it's plugged in because of this loading screen thing that keeps repeating. I was thinking about getting a new phone for Christmas, maybe this is a sign
Click to expand...
Click to collapse
assuming that the power light comes on when you have it plugged in, you should be able to get it going. boot into fastboot (vol down and power) and then you should be able to either get to recovery, or push adb commands from there to get it working again. I have never had to do this, but I have seen others report victory after using these methods. here are 2 threads about adb
http://forum.xda-developers.com/showthread.php?t=690362
http://forum.xda-developers.com/showthread.php?t=532719
good luck

I should be able to boot into recovery but it still goes to this install process that restarts indefinitely no matter how many ways I try to start it up. I tried Power+Home, Volume down+power, Home+back then power, but this installation screen comes up every time. When I plug it into the computer it's being charged, but it never recognizes it as being connected. So basically I can't flash or do a Nandroid backup (which I would usually do in this situation) because I can't access any of the tools to do it.

vol down and power doesn't get you to fastboot (NOT recovery) ?
explosivo98 said:
I should be able to boot into recovery but it still goes to this install process that restarts indefinitely no matter how many ways I try to start it up. I tried Power+Home, Volume down+power, Home+back then power, but this installation screen comes up every time. When I plug it into the computer it's being charged, but it never recognizes it as being connected. So basically I can't flash or do a Nandroid backup (which I would usually do in this situation) because I can't access any of the tools to do it.
Click to expand...
Click to collapse
did you read the second link? it says this:
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next lineNow you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!

The device is showing up weird on the list, and none of the commands seem to be working. Here's what it looks like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Oops, not quite what I was trying to show there. I tried adb reboot recovery but after rebooting the phone still starts in this install process for Clockworkmod. I tried putting the update file on the SD card using adb but that didn't work either.

explosivo98 said:
Oops, not quite what I was trying to show there. I tried adb reboot recovery but after rebooting the phone still starts in this install process for Clockworkmod. I tried putting the update file on the SD card using adb but that didn't work either.
Click to expand...
Click to collapse
download a different recovery like amon ra and try to install that thru adb, then reboot recovery
EDIT: if I read that post of your cmd box correctly it looks like you lost superuser, right? get the apk and push it thru adb, then get the recovery and then try to reboot into recovery.... report back.

il Duce said:
download a different recovery like amon ra and try to install that thru adb, then reboot recovery
EDIT: if I read that post of your cmd box correctly it looks like you lost superuser, right? get the apk and push it thru adb, then get the recovery and then try to reboot into recovery.... report back.
Click to expand...
Click to collapse
The installation of recovery files always needs me to boot into my current custom recovery, which I can't do. I have SU permissions, that post wasn't really what I wanted to show. I tried to reboot into recovery but the phone always reboots right back into the install that I'm stuck on.

explosivo98 said:
The installation of recovery files always needs me to boot into my current custom recovery, which I can't do. I have SU permissions, that post wasn't really what I wanted to show. I tried to reboot into recovery but the phone always reboots right back into the install that I'm stuck on.
Click to expand...
Click to collapse
you really ought to read the threads I posted. these are not "recovery files" as you call them. It tells you how to do this with commands in fastboot, you do not need to boot into your recovery, it should work in fastboot, here is yet another link to a thread, I leave you to your reading, the answers are there, specifically how to to what you are trying to while in fastboot, not in recovery.
http://forum.xda-developers.com/showthread.php?t=517874

Fastboot doesn't recognize the phone as plugged in, all the adb commands seem to work but when I try anything with fastboot it hangs at <waiting for devices>. I also checked the device list and it showed none.

explosivo98 said:
Fastboot doesn't recognize the phone as plugged in, all the adb commands seem to work but when I try anything with fastboot it hangs at <waiting for devices>. I also checked the device list and it showed none.
Click to expand...
Click to collapse
Make sure Fastboot is working
Open up Command Prompt
type the following
Code:
cd C:\android-sdk-windows-1.5_r2\tools === Press Enter
fastboot devices === Press enter, your device should be listed
fastboot shell === You should see a # in the next line
type fastboot and press enter for general commands

Fastboot is definitely working, here's what it looks like (note how it doesn't detect any device)
But adb works fine with the phone:

Oh sweet jesus I finally fixed it. Pushed the new recovery image to it and flashed it, then reboot recovery worked. Thanks for all the help!

explosivo98 said:
Oh sweet jesus I finally fixed it. Pushed the new recovery image to it and flashed it, then reboot recovery worked. Thanks for all the help!
Click to expand...
Click to collapse
Nice work! Now please post a detailed step by step of HOW you did it here, and then save this thread as a favorite so you can help the next person in a similar spot! Glad you finally got it.
sent from my hero, which no longer sucks ass

Now it can be S-OFF, how to install a permanent ROOT?

Just finished the S-OFF using alpharevx, want to know how to do the permanent ROOT.
Any tips?

http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed

There is a Sticky at top of the IncS General Forum about this.

You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.

nikkuy said:
You need to install gingerbreak on your phone it's here http://forum.xda-developers.com/showthread.php?t=1044765 and Open Gingerbreak and click Root Device. that's all.
Click to expand...
Click to collapse
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.

Are you done?

geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
This just worked for me - it was simple in the end!
I used a spare SD card (I don't think I needed to), just copy/pasted the clockwork recovery .zip file to the card (not in a folder on the card) and rebooted, holding volume down on start-up. After that, it automatically prompted me to install the file, so I let it install.
Then, I rebooted the phone and deleted the above file from the SD card, and replaced it with the signed root .zip file and rebooted with the volume down button again.
Just follow the steps, one by one, 'To root:' in the above linked post, after you have installed the recovery file - it worked first time for me and was actually simple to follow!!
My phone works as it always has done (as you would expect/hope), but now I have root - confirmed with Root Explorer app from Market.
Thanks to all involved in the linked post above.
I also tried GingerBreak a few times but it just didn't work for me, so I gave this a go and it worked first time.

jkolner said:
Not quite...
I have rooted 4 IncS wit GingerBreak now, and non of them succede first time.
2 got rooted thrid time i ran GB, and 2 of them i had to take the SD card out when the error message came.
But GinderBreak can root the IncS, but somthimes you need some "Ninja" tricks.
Click to expand...
Click to collapse
My phone is still on 2.2 Froyo, Gingerbreak is for 2.3 correct?

geeti said:
http://forum.xda-developers.com/showthread.php?p=14693680
check this out, pretty detailed
Click to expand...
Click to collapse
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?

netwr said:
I dont quite understand step 4, 5, 6:
4. Extract recovery.img from the archive and put it with fastboot.
5. Put the phone is Fastboot USB mode (HINT: Android is not up and running - access it from your hboot screen - see how below)
6. fastboot flash recovery <recovery.img> <<< from a command line (use root for Linux- sudo ./fastboot yadda)
Step 4, it says put it with fastboot, does it mean after i extracted the recovery.img, move it to the same folder with the fastboot app (i.e. to the folder android-win-tools where the fastboot app is located?).
Step 5, Fastboot USB mode, this is done by holding the volume down button and the pressing the power button, when the white screen comes up, select Fastboot, and then plug the phone back to the computer via USB?
Step 6, after the phone is plugged to the computer via USB, double click on the fastboot app (the one inside the android-win-tools folder) and when the black prompt screen comes up, type in Linux- sudo ./fastboot yadda?
Btw, I am on Windows computer, not Linux, so is the command prompt Linux- sudo ./fastboot yadda correct?
Also, if I want to bluetooth the su-2.3.6.1-ef-signed.zip to the phone, will it go directly to the SD root location? If not, when I do clockworkmod recovery and "install zip from sdcard", will it able to locate the file?
Click to expand...
Click to collapse
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.

coy1987 said:
No, follow step 6 you use command line like this: "fastboot flash recovery C:\recovery.img". After you choose "install zip from sdcard" you have to choose the location where you put the file you want to install.
Click to expand...
Click to collapse
So this is exactly how it should be typed in the command prompt?
fastboot flash recovery C:\recovery.img
Are the rest of other steps correct?

I am still getting stuck at the Clockworkmod installation part, without this I cannot get to the root step.
I extracted the android-win-tools.zip, which contains the following files:
adb
AdbWinApi.dll
AdbWinUsbApi.dll
android-info
fastboot
and then extracted the cwm-vivow-4.0.0.4-recovery.img.zip, contains the following:
recovery.img
then I moved all the above 6 files directly to the C: directory. After that went into cmd and typed the prompt exactly like following:
fastboot flash recovery C:\recovery.img
Did I miss anything? Because after typing that line and hit return it came out nothing. Is that prompt correct?

Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S

adaca said:
Why not root with superoneclick -> download clockworkmod from market and install recovery from app? Work perfectly for me...
Sent from my HTC Incredible S
Click to expand...
Click to collapse
clockworkmod from market, is it aka ROM Manager?
This app won't work because it requires a ROOT phone, which is what I am trying to do.

Yes, and before use superoneclick.
Sent from my HTC Incredible S

adaca said:
Yes, and before use superoneclick.
Sent from my HTC Incredible S
Click to expand...
Click to collapse
How did you get it from market, is it not up currently

Superoneclick is not from market, use google. Its for rooting.
Sent from my HTC Incredible S

You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just installed SuperOneClick and clicked Root, it said the phone is rooted successfully. Then clicked on the "allow non market apps" and the result said non-market apps enabled.
But then I went to market and installed a screen cap app (one needs root), launched the app and it said Root required - Your phone does not appear to be rooted or has not been given root privileges.
Did the SuperOneClick really root it?

doctorsax said:
You can also try Gingerbreak if you can't get SuperOneClick to work (again you'll have to search for this as it's not in the market).
Click to expand...
Click to collapse
Does Gingerbreak work with 2.2?

[Q] Questions about CWM/TWRP, Nandroid and SuperSu

Hi..
I have a couple of questions about recovery mode and Nandroid backups. Easiest one first.. Does Nandroid back up everything, right done to home screen layout, personal folders, widgets etc.. an EXACT copy of the phone?
Secondly, I installed CWM/TWRP, and was able to boot into it to install my ROM, however, once the ROM is on the phone, I seem to lose the ability to boot into recovery mode. The CWM app shows that the recovery is installed, however the usual volume- and power key just starts the phone normally. I've put on an Xposed mod, which puts recovery on the power menu, with reboot, screenshot etc, however, that does the same.. Just reboots the phone.
Is this normal, and is it safe to keep pushing recovery to the phone via PC every time I need to use it?
Lastly, my phone is nicely rooted, however SuperSu only seems to grant access when set to "allow". On 4.1.2 I used to have it set to "prompt", however selecting this seems to block root access. I've tested it with an SU checker and a root checker, and with "prompt" selected, it tells me the phone isn't rooted. It's ok having it set to "allow", but not ideal, as I prefer total control over what is, and isn't allowed root access.
Any help and suggestions gratefully recieved. I'm on Android 4.3, .201 on an Xperia SP.
Thanks!

1. Recovery backup usually backs up these things..
-Boot (kernel)
-System partition (ROM with system apps. But not app data)
-Data (apps and app data- with all apks you installed, user settings, accounts etc. Including UI layout. But not sdcard data)
-Cache
*Philz recovery has a nice option to backup internal sdcard (data/media)-very useful!
# So, if you choose the option "custom backup", you can select which component to backup in TWRP/Philz. (CWM has custom restore only).
2. Installing a ROM will erase any recovery installed in the system partition (which is the case if locked bootloader. If BL unlocked, can install a custom kernel with recovery, which won't get erased by ROM installing because it's with the kernel, not in system partition).
#So, you might have to install the recovery every time after flashing a ROM (of course, unless the ROM has pre-installed recovery).
3. SuperSU on "prompt" mode works well for me. Try to clear the data of SuperSu app and see.. or see whether there's a new update..
Hope this is of some help to you

mrhnet said:
1. Recovery backup usually backs up these things..
-Boot (kernel)
-System partition (ROM with system apps. But not app data)
-Data (apps and app data- with all apks you installed, user settings, accounts etc. Including UI layout. But not sdcard data)
-Cache
*Philz recovery has a nice option to backup internal sdcard (data/media)-very useful!
# So, if you choose the option "custom backup", you can select which component to backup in TWRP/Philz. (CWM has custom restore only).
2. Installing a ROM will erase any recovery installed in the system partition (which is the case if locked bootloader. If BL unlocked, can install a custom kernel with recovery, which won't get erased by ROM installing because it's with the kernel, not in system partition).
#So, you might have to install the recovery every time after flashing a ROM (of course, unless the ROM has pre-installed recovery).
3. SuperSU on "prompt" mode works well for me. Try to clear the data of SuperSu app and see.. or see whether there's a new update..
Hope this is of some help to you
Click to expand...
Click to collapse
Thanks.. I've done a Nandroid backup with TWRP.. Can I move the folder from the SD Card to my laptop without any problems, or does it put files anywhere else? I gather doing it with CWM makes transferring to PC quite difficult, which is why I opted to go with TWRP.
Also, if I clear the data on SuperSu, will I lose any of the permissions it has already granted? I don't fancy setting up Greenify all over again!
Cheers!

MetalOllie said:
Thanks.. I've done a Nandroid backup with TWRP.. Can I move the folder from the SD Card to my laptop without any problems, or does it put files anywhere else? I gather doing it with CWM makes transferring to PC quite difficult, which is why I opted to go with TWRP.
Also, if I clear the data on SuperSu, will I lose any of the permissions it has already granted? I don't fancy setting up Greenify all over again!
Cheers!
Click to expand...
Click to collapse
You mean, you want to copy the backup files to your laptop for safe keeping? Yes, you can copy those files to laptop/pc and then copy back to proper backup folder whenever you want to make a restore. TWRP makes backup files under TWRP folder (below many subfolders of course) in internal sdcard ("sdcard" ) or external SD ("sdcard1" ), depending on where you choose to backup. You can easily copy back and forth from there, especially external SD because you can even remove it and read/write with a pc if the phone is screwed up. (Check whether files are copied properly and make sure 'safely remove usb drive' etc in pc. If a small corruption in files when copying, md5 checksum tests will fail and recovery would refuse to use those backup files for restore).
CWM, stores them under clockworkmod folder in external SD (easy access), but in data/media/clockworkmod if you chose internal sdcard. If you're familiar with ADB, you can use pull/push commands to copy back and forth from there to a pc. Philz recovery stores things under same clockworkmod, but under proper "sdcard" though.. so easy access. (Or at least it has an option to look for "sdcard" under /data/media/0, which is a proper place where internal "sdcard" is mounted..). Feel free to ask if any of above is not clear to you..
About SuperSU, yes.. clearing data (Apps>All>SuperSU>Clear data) of the app will erase all yes/no su permission granted settings.. like going back to where you began. But it won't do anything to greenify settings. I have a feeling that you didn't flash SuperSU update after you flashed a new ROM.. is it? You also have to flash SuperSU update zip after ROM flashing, so proper su binaries get installed to the new ROM (I think ). Otherwise you won't get proper root. So, you did/not flash SuperSU update after ROM flashing?

Hi..
I did flash SuperSu 1.93 update after flashing the ROM, and then after a reboot, flashed it to 1.94. I've cleared the data, but it still doesn't offer a prompt. When set to "prompt", Root Checker tells me the device isn't rooted.. As soon as I set it back to "Grant access", it's fine.

MetalOllie said:
Hi..
I did flash SuperSu 1.93 update after flashing the ROM, and then after a reboot, flashed it to 1.94. I've cleared the data, but it still doesn't offer a prompt. When set to "prompt", Root Checker tells me the device isn't rooted.. As soon as I set it back to "Grant access", it's fine.
Click to expand...
Click to collapse
Strange..! No idea what's causing your issue.. but try this:
-Open SuperSu app. "Apps" column should be empty because you cleared its data, no?
-Set to "prompt" mode.
-Open Terminal Emulator (get from Google play if not present)
-type "su -v" (without quotes) and press enter (checking su version). Should show something like "1.93:SUPERSU"
-then type "su" and press enter. See whether any su prompt.
-then type "id" and press enter. What's the output?

mrhnet said:
Strange..! No idea what's causing your issue.. but try this:
-Open SuperSu app. "Apps" column should be empty because you cleared its data, no?
-Set to "prompt" mode.
-Open Terminal Emulator (get from Google play if not present)
-type "su -v" (without quotes) and press enter (checking su version). Should show something like "1.93:SUPERSU"
-then type "su" and press enter. See whether any su prompt.
-then type "id" and press enter. What's the output?
Click to expand...
Click to collapse
With prompt mode set:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nothing happens when trying SU if set to prompt.
I noticed in terminal it reports as being 1.93, so tried reflashing in recovery to 1.94, however it still reports as 1.93. The app is 1.94 though?

mrhnet said:
Strange..! No idea what's causing your issue.. but try this:
-Open SuperSu app. "Apps" column should be empty because you cleared its data, no?
-Set to "prompt" mode.
-Open Terminal Emulator (get from Google play if not present)
-type "su -v" (without quotes) and press enter (checking su version). Should show something like "1.93:SUPERSU"
-then type "su" and press enter. See whether any su prompt.
-then type "id" and press enter. What's the output?
Click to expand...
Click to collapse
When set to grant, this is the output..

MetalOllie said:
With prompt mode set:
Nothing happens when trying SU if set to prompt.
I noticed in terminal it reports as being 1.93, so tried reflashing in recovery to 1.94, however it still reports as 1.93. The app is 1.94 though?
Click to expand...
Click to collapse
I too get 1.93 even though I also flashed latest version. It's the version of su binary. No issues for me. So it shouldn't be the problem.
Wanted to see "id" output after "su" (if "uid=0" like output means root access). Anyway, when "prompt", your su command seems to get stuck.. is it? Doesn't any message saying "su denied" appear after keeping it for a while?
Other thing you can try is to reinstall SuperSU app to see whether it makes any difference. Under SuperSU app settings, there's an option cleanup>reinstall (from google play). Can't be sure that it works, but an option to try. Keep a CWM/TWRP back up before trying it, just in case..

mrhnet said:
I too get 1.93 even though I also flashed latest version. It's the version of su binary. No issues for me. So it shouldn't be the problem.
Wanted to see "id" output after "su" (if "uid=0" like output means root access). Anyway, when "prompt", your su command seems to get stuck.. is it? Doesn't any message saying "su denied" appear after keeping it for a while?
Other thing you can try is to reinstall SuperSU app to see whether it makes any difference. Under SuperSU app settings, there's an option cleanup>reinstall (from google play). Can't be sure that it works, but an option to try. Keep a CWM/TWRP back up before trying it, just in case..
Click to expand...
Click to collapse
Done a reinstall, which went ok.. It updated the binaries, though still says 1.93 in Terminal. I don't get any message in Terminal on prompt mode.. Here's a screenshot of the "id" after "SU" while on "grant".
The other thing I've noticed is that the configured apps list is always empty, although apps do show in the log if I call them up.. For example, terminal shows, with a green hash next to it. Red if I set it to prompt.

Yup, it doesn't come in app list if set to grant/deny for me too. Could be normal.
I've run out of ideas.. One last checking...
Can you check with Root Validator app here https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator
My one is like this
See what's the difference in prompt/grant modes for you.
#And, do this command in terminal to see su permissions
Code:
ls -l /system/xbin/su
#What I would do as a last resort is to reflash the rom and root again (AFTER taking a full cwm backup). Btw, is the ROM you flashed pre-rooted? Is there another su binary in another (conflict?) location like /system/bin..? (Root Validator app would indicate about it anyway). For this you can do..
Code:
find /system -name "su"
#also, check whether daemonsu is running..
Code:
ps |grep -w daemonsu
Could you think of anything else that might cause this?
Edit: Chainfire's SuperSU xda thread is here: http://forum.xda-developers.com/showthread.php?t=1538053
You could post a query there if you wish..

mrhnet said:
Yup, it doesn't come in app list if set to grant/deny for me too. Could be normal.
I've run out of ideas.. One last checking...
Can you check with Root Validator app here https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator
My one is like this
See what's the difference in prompt/grant modes for you.
#And, do this command in terminal to see su permissions
Code:
ls -l /system/xbin/su
#What I would do as a last resort is to reflash the rom and root again (AFTER taking a full cwm backup). Btw, is the ROM you flashed pre-rooted? Is there another su binary in another (conflict?) location like /system/bin..? (Root Validator app would indicate about it anyway). For this you can do..
Code:
find /system -name "su"
#also, check whether daemonsu is running..
Code:
ps |grep -w daemonsu
Could you think of anything else that might cause this?
Edit: Chainfire's SuperSU xda thread is here: http://forum.xda-developers.com/showthread.php?t=1538053
You could post a query there if you wish..
Click to expand...
Click to collapse
Here's my Root Validator (in grant mode)

And here is the terminal output.. Sorry for individual posts.. I can't seem to attach more than one pic at a time (possibly because I'm on an iPad)

Those outputs are similar to mine. Sorry mate.. no idea what to do next. Suggest making a query in Chainfire's SuperSU thread. Don't forget to attach the logcat in your post (after attempting in "prompt" mode).
Catlog app is an easier way to get logcats (need root for that, so run that app in grant mode when collecting logcat).

[Q] Cant get MB886 into custom recovery

I have been trying for hours to install a custom recovery in my AT&T Atrix HD (mb886) phone. Every time I go through the flashing process, no matter what recovery I try, and whether I use the stock SDK fastboot or one of alternatives, when I try to boot into recovery, I get an ominous error message about how my bootloader is unlocked, and Motorola and ATT will not honor the warranty, and so on. However - it then always boots into the normal startup. I did try holding down both volume buttons when I cycled the power button, and I briefly (about 5 seconds, maybe?) got what looked like a text-based recovery menu, but then the error message popped up again, and I'm back to ????? is going on.
Any help? I have read a number of article/forums online, but all assume that your recovery is working so you can install a custom ROM. I have done this on a couple of Android tablets in the past, so I know I'm not totally stupid, but I can't seem to get past the AT&T nanny.
How can I fix this?
Android 4.1.1
System 98.4.20.MB886.ATT.en.US

If I remember correctly, I had to rename install-recovery.sh (or something like that) by adding .bak to the end of the filename. Boot into fastboot, flash your recovery, and try to boot into recovery.

Nevadadave said:
I have been trying for hours to install a custom recovery in my AT&T Atrix HD (mb886) phone. Every time I go through the flashing process, no matter what recovery I try, and whether I use the stock SDK fastboot or one of alternatives, when I try to boot into recovery, I get an ominous error message about how my bootloader is unlocked, and Motorola and ATT will not honor the warranty, and so on. However - it then always boots into the normal startup. I did try holding down both volume buttons when I cycled the power button, and I briefly (about 5 seconds, maybe?) got what looked like a text-based recovery menu, but then the error message popped up again, and I'm back to ????? is going on.
Any help? I have read a number of article/forums online, but all assume that your recovery is working so you can install a custom ROM. I have done this on a couple of Android tablets in the past, so I know I'm not totally stupid, but I can't seem to get past the AT&T nanny.
How can I fix this?
Android 4.1.1
System 98.4.20.MB886.ATT.en.US
Click to expand...
Click to collapse
That warning you see is just the boot logo and can be gotten rid of by flashing a custom logo. Stock Moto boot logos on this platform have two images -- one for locked and another for unlocked bootloaders. It's a non issue and just confirms that the bootloader is unlocked.
You accessed that menu by powering up and holding both volumes and power. Volume down scrolls and volume up selects in there.
To install a custom recovery, boot into fastboot mode and flash it with fastboot. Mythtools, maybe BootMyHD, can do that for you if you don't have moto-fastboot binary or are unable to run "moto-fastboot flash recovery recovery.img" with your phone plugged into a rear usb port in fastboot mode with a terminal/command prompt open to the directory with the recovery image.

More questions
audit13, how do I access that file to change the name? I tried again this morning, and after doing the boot to recovery key sequence, I got a menu, and before it went away, I selected boot to recovery, but got the dead android icon. I tried several other options and it just did a normal boot. Still stumped.
skeevydude, I have tried installing a couple of custom recoveries, using fastboot, and when I do, I get a message saying all went well, but when I boot up, it either does the "failed Android" or just boots up normally. I'll try Mythtools and BootMyHD, but it seems that there is something else going on here.

Nevadadave said:
audit13, how do I access that file to change the name? I tried again this morning, and after doing the boot to recovery key sequence, I got a menu, and before it went away, I selected boot to recovery, but got the dead android icon. I tried several other options and it just did a normal boot. Still stumped.
skeevydude, I have tried installing a couple of custom recoveries, using fastboot, and when I do, I get a message saying all went well, but when I boot up, it either does the "failed Android" or just boots up normally. I'll try Mythtools and BootMyHD, but it seems that there is something else going on here.
Click to expand...
Click to collapse
Maybe something else going on. Are you flashing using the rear usb port of your PC? It really does matter.
To answer the first question about install-recovery, once you're rooted, use Root Explorer or something similar, mount /system as read/write, go to /system/etc, rename the file install-recovery.sh to install-recovery.sh.bak, and reboot.
If you have adb installed on your PC you can do
adb root
adb shell mount -o remount,rw /system
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell rm /system/etc/install-recovery.sh
adb reboot

I'll try it and see what happens
skeevydude said:
Maybe something else going on. Are you flashing using the rear usb port of your PC? It really does matter.
To answer the first question about install-recovery, once you're rooted, use Root Explorer or something similar, mount /system as read/write, go to /system/etc, rename the file install-recovery.sh to install-recovery.sh.bak, and reboot.
If you have adb installed on your PC you can do
adb root
adb shell mount -o remount,rw /system
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell rm /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
OK, I did not know about USB port preference. I'll try it and see what happens. Thanks!

No joy
Nevadadave said:
OK, I did not know about USB port preference. I'll try it and see what happens. Thanks!
Click to expand...
Click to collapse
Well, I tried front and back USB ports, in all cases, adb says "adb can't run as root in production builds". adb sees the phone, but about all I can do is start fastboot, but once there adb doesn't work until I reboot.
I tried running the remount command, but got a message, "Operation not permitted" I'm assuming because I could not root into the phone. Titanium backup shows that the phone is, indeed, rooted.
Stuck again...

Install Root Explorer, find the file, add .bak to the end, reboot to fastboot, install Philz, boot into recovery.

audit13 said:
Install Root Explorer, find the file, add .bak to the end, reboot to fastboot, install Philz, boot into recovery.
Click to expand...
Click to collapse
I tried that, got a "Rename failed". It appears that the file is set to read-only, and the Root Explorer doesn't seem to have a way to change that. I'm open to additional suggestions. I had thought that root access would allow me to do things like change file permissions, but I cannot do this with Root Explorer. Everything I try, I get a message that it can't be done, because the file system is read-only.
At the top of the file list, it says "mounted as r/o, but nothing shows to change that, although I see num,erous web posts that claim that there should be a "R/W" button somewhere.

Better luck
Nevadadave said:
Well, I tried front and back USB ports, in all cases, adb says "adb can't run as root in production builds". adb sees the phone, but about all I can do is start fastboot, but once there adb doesn't work until I reboot.
I tried running the remount command, but got a message, "Operation not permitted" I'm assuming because I could not root into the phone. Titanium backup shows that the phone is, indeed, rooted.
Stuck again...
Click to expand...
Click to collapse
OK, I dropped Root Explorer and loaded ES File Explorer. ES Explorer allowed me to change the file R/W permissions and rename the stock recovery file.
adb would still not allow me to get to root, so I loaded adbd insecure from the Play store, and that gave me root access. I flashed the CWR 6.0.4.4, and so far (fingers crossed) I was able to boot to CWM and I'm backing up my system now. Hopefully, the next update will be to say that I have a new ROM installed...

Nevadadave said:
OK, I dropped Root Explorer and loaded ES File Explorer. ES Explorer allowed me to change the file R/W permissions and rename the stock recovery file.
adb would still not allow me to get to root, so I loaded adbd insecure from the Play store, and that gave me root access. I flashed the CWR 6.0.4.4, and so far (fingers crossed) I was able to boot to CWM and I'm backing up my system now. Hopefully, the next update will be to say that I have a new ROM installed...
Click to expand...
Click to collapse
All you need to gain r/w access is to click on the ro button to change it to read/write.

audit13 said:
All you need to gain r/w access is to click on the ro button to change it to read/write.
Click to expand...
Click to collapse
Audit13 I'm not sure what you mean here. Root Explorer never indicated a "R/O" button or any other way to change permissions, it just kept saying that the file system was write-protected. ES File Explorer was very easily able to change this and allow me to remove the automatic recovery overwrite.
So, at this point, I have Cyanogen 10.2 running on my Atrix HD, and although I have found a few glitches, it is faster and it is now MINE!

Nevadadave said:
Audit13 I'm not sure what you mean here. Root Explorer never indicated a "R/O" button or any other way to change permissions, it just kept saying that the file system was write-protected. ES File Explorer was very easily able to change this and allow me to remove the automatic recovery overwrite.
So, at this point, I have Cyanogen 10.2 running on my Atrix HD, and although I have found a few glitches, it is faster and it is now MINE!
Click to expand...
Click to collapse
In Root Explorer, You'll see the words "Mounted as r/o". To the right will be a button that says "Mount R/W".
I went with Validus 5.1 over 10.2.