Database Develop

Reboot into recovery?

Maybe this should be in Q&A. If so, sorry.
Anyway, is there a way to create a shortcut with a terminal emulator command for "reboot recovery?" or any other method to quickly reboot into recovery? Thanks.

There are probably several. GScript can do this. If you're using enomther's TheOfficial, his Spare Parts also does this (though not as a shortcut AFAIK).

Part Four said:
Maybe this should be in Q&A. If so, sorry.
Anyway, is there a way to create a shortcut with a terminal emulator command for "reboot recovery?" or any other method to quickly reboot into recovery? Thanks.
Click to expand...
Click to collapse
You're right, this is not the place but I don't resist the tentation:
There's an app for that! It's name, Root Booter. Search the Market.

rgl12miami said:
You're right, this is not the place but I don't resist the tentation:
There's an app for that! It's name, Root Booter. Search the Market.
Click to expand...
Click to collapse
Ah, thank you sir.

App quick boot on the market. Short cut to reboot, recovery, bootloader

jerrycycle said:
App quick boot on the market. Short cut to reboot, recovery, bootloader
Click to expand...
Click to collapse
Yeah, thanks. That's the one I went with. Found it the day I created this thread.

Part Four said:
Maybe this should be in Q&A. If so, sorry.
Anyway, is there a way to create a shortcut with a terminal emulator command for "reboot recovery?" or any other method to quickly reboot into recovery? Thanks.
Click to expand...
Click to collapse
Yes sir, download either quick boot or reboot control widget.. those are it.. enjoy, I prefer reboot control.. it allows you to power down, wipe, reboot to recovery, boot loader and fastboot. So your pretty much covered there.
Your welcome..

i use quickboot.. and im loving the shortcuts that it comes with... saves the finger gymnastics

[Q] Recovery image

I'm currently running DarchDroid 2.7, and I'm not sure if the recovery image that I have is the one that he uses. Does that come with the ROM, or am I using the same recovery image that I used to root my phone? Many thanks in advance.

troyneuenschwander said:
I'm currently running DarchDroid 2.7, and I'm not sure if the recovery image that I have is the one that he uses. Does that come with the ROM, or am I using the same recovery image that I used to root my phone? Many thanks in advance.
Click to expand...
Click to collapse
when you flash it doesnt update the recovery image. what's it say when you boot into recovery (press home and power on)? If it doesnt say RA-Darchstar 1.7 then its most likely not the one he recommends. you can dl it here. http://www.4shared.com/file/ct5xCGYb/RA-Darchstar.html
and follow these instructions.
1. Place on your SD Card. Don't put in any folders
2. Download Terminal Emulator from the market its free
3. type su then hit enter
4. then type flash_image recovery \sdcard\RA-Darchstar.img then hit enter
5. type exit, then type exit again.
6. Reboot into recovery should have a ninja tux and state RA-Darchstar 1.7

i like it when people give quick, efficient answers. thumbs up for helping dude out.

Outstanding... thank you very much.

westicle said:
i like it when people give quick, efficient answers. thumbs up for helping dude out.
Click to expand...
Click to collapse
yeah most people on xda don't answer questions.

yeah sometimes they just leave jackass non-constructive comments.

westicle said:
yeah sometimes they just leave jackass non-constructive comments.
Click to expand...
Click to collapse
"use the search" lol

sdotcarlisle said:
"use the search" lol
Click to expand...
Click to collapse
I have to say this is good advice, but sometimes a search just doesn't do it.

does anyone know if Amon_Ra has completely quit making his recovery images, or did he just stop making them for the cdma hero.

[Q] please tell me my n1 isn't a paperweight now....

running rod's miui rom and was trying to remove excess crap via titanium pro. when trying to remove facebook it would reboot and give an error message about signature failure. so i thought i'd see if it would successfully remove a different app. rod included a fancy widget app that i had no desire for. when trying to remove that, it did a number on my n1. i cannot get into the recovery mode or anything.
this is a video of what the phone now does. no matter if i pull the battery or what.
http://www.youtube.com/watch?v=6a4DP3IjZiQ

That's an interesting one.
When you turn it on - this is the first thing you see? No "X" at all?
Did you try ADB to see if it sees the device?
Looks just like radio flash, but with radio flash there are no recovery messages, if I remember correctly.

no, i get the un-animated X, and then it goes straight to this. regardless if i hold down the trackball or not.
what do i need to do to try to adb to it? i don't fool with adb ever, just when i first rooted/unlocked it.

Put a diff update.zip for another rom on your sdcard. Lemme know if it works
Sent from my Bionixed SGH-T959 using XDA App

brnbock said:
Put a diff update.zip for another rom on your sdcard. Lemme know if it works
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
i took enoms rom, renamed it update.zip and placed it on the sdcard. still nothing, same thing.
if i press the powerbutton whilst on the android out of the box thing it says.
"ClockworkMod Recovery v2.5.1.0
Finding Update Package........
Opening Update Package.......
Verifying Update Package......
Installing Update....."
this is shown in the video, but blurry and hard to read.

well, if im doing things right..... adb remount said it successfully did so.
(edit) ok, i can definitely connect via adb, i just ran the reboot bootloader command and the phone rebooted..... albeit back to that stupid looping screen.

any other ideas folks...... i'm up against a wall here.

i am able to get this in terminal
[email protected]:~/Android/tools$ ./adb devices
List of devices attached
HT02KP901120 recovery
[email protected]:~/Android/tools$

You need a rom that can be flashed as an update.zip, most are not flashed that easy. Can you get into fastboot?
Sent from my Bionixed SGH-T959 using XDA App

brnbock said:
You need a rom that can be flashed as an update.zip, most are not flashed that easy. Can you get into fastboot?
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
i don't think so

Try booting into fastboot, if you can your good if not then I will do some digging.
Sent from my Bionixed SGH-T959 using XDA App

brnbock said:
Try booting into fastboot, if you can your good if not then I will do some digging.
Sent from my Bionixed SGH-T959 using XDA App
Click to expand...
Click to collapse
well, i cant get to the recovery screen to initiate fastboot. if i use adb reboot-recovery it just reboots the phone and goes back to the looping crap i'm stuck at.
if i try any fastboot commands, i get nothing. i just can't get it to do anything other than respond to adb commands.

a fella from nexus one forums suggests that perhaps my bootloader is messed up and needs to be restored? that sound possible?

That was this fella, and I'm actually more convinced that the recovery is stuck trying to do an update... xD
Sent from my Nexus One using XDA App

danger-rat said:
That was this fella, and I'm actually more convinced that the recovery is stuck trying to do an update... xD
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
haha. the omnipresent danger-rat is indeed the fella.

I was hoping Jack or Rusty would be here to check my logic...
Here's what we believe so far:
1 - phone appears to be in recovery, and trying to install an update.
2 - phone is in recovery, so adb is (kinda) working.
3 - there's no update.zip on the SD card.
4 - trying to overwrite the recovery via adb gives a "device or resource busy" response...
My guess is that if the install process can be killed, then you should be able to re-gain control?
...I've no idea how to kill processes via adb... :-(
Sent from my Nexus One using XDA App

Woooooo HOOOOOOOO!!!!!!!!!!!!!!!!!!
i'm not entirely sure what i did......... but i think i have it. i transfered amon's 1.7.0 img to the sdcard and aptly renamed it recovery.img. after just now trying to restart to see if i could get fastboot to do anything it must have found the recovery.img and reflash amon. i'm looking at amons recovery now as i type.
i just rebooted and now i'm back into rods miui...... phone is working fine.

danger-rat said:
I was hoping Jack or Rusty would be here to check my logic...
Here's what we believe so far:
1 - phone appears to be in recovery, and trying to install an update.
2 - phone is in recovery, so adb is (kinda) working.
3 - there's no update.zip on the SD card.
4 - trying to overwrite the recovery via adb gives a "device or resource busy" response...
My guess is that if the install process can be killed, then you should be able to re-gain control?
...I've no idea how to kill processes via adb... :-(
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
just wanted to say thanks so much for all your effort and help man.

now a new quick question... which is what started this whole fiasco.
how can i remove unwanted apps from rods miui rom?

noremacyug said:
now a new quick question... which is what started this whole fiasco.
how can i remove unwanted apps from rods miui rom?
Click to expand...
Click to collapse
adb shell
su
rm -rf /system/app/nameofapp.apk
once the apps are deleted:
(on the phone)
go to settings--> manage applications
and delete any leftover files pertaining to the programs you just deleted
Reboot
Then reboot and make a backup
*EDIT*
You may need to reboot after removing the programs for those file to show up in Manage Applicaions

Bootloader button combos does nothing.

Been trying to do this for two days straight now and I'm going bananas...
Got a GT540 with stock 2.1, now rooted with z4.
Gone thru a shipload of tutorials on how to flash a ROM onto this, downloaded lots of files to make winxp behave and find the drivers.
Somehow these tutorials miss something and I just float in space...
I can't get the phone into bootloader mode to even start the process.
- Camerabutton (all the way down) + Power does only normal boot.
- Camerabutton (all the way down) + USB cable insertion does normal boot.
(it's not even possible to have it to stay shut when USB is connected to PC, it restarts immediately)
- Home + Power does a boot in safe mode.
- VolDown + Power does a Download mode.
Please help me get past this step.
My aim is to get CM7 on it.

you need to install a fastboot rom to install clockwork and cm7
Sent from my GT540 using XDA Premium App

You could try this (but I think you need plenty of ram free):
1) install Terminal Emulator app from Market.
2) Copy the img file for Clockworkmod Recovery to the root of your sdcard and call it "recovery.img".
3) run Terminal Emulator and type in "su" and press enter. It will request SuperUser rights - accept this.
4) next type in "flash_image recovery /sdcard/recovery.img" and press enter
5) reboot into recovery (hold camera + press power)
6) back up your phone
It will either work or it won't but if it does you'll have recovery and from there you should be able to install a recovery image of CM7... But I've never tested it But you would have your backup if it didn't work...
Sorry it's speculative - others might have more experience.

eoghan2t7 said:
you need to install a fastboot rom to install clockwork and cm7
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
When entering this world as a newbie, there are -so- many details folks take for granted that I simply don't understand.
What's the difference between a fastboot rom and a flashed rom?
What and why clockwork?
The russian fastboot image found here does it come in any other language as v2.00?
@fishears: I'll try that if I don't run into lack of memory, as you pointed out.

would you like me to remote control your computer to get you up and going using CM7?

eoghan2t7 said:
would you like me to remote control your computer to get you up and going using CM7?
Click to expand...
Click to collapse
dude i want someone to help me remote! please!!! im more or less in the same boat as the op.

kdm212 said:
dude i want someone to help me remote! please!!! im more or less in the same boat as the op.
Click to expand...
Click to collapse
ok download teamviewer then pm me the password and id numbers

eoghan2t7 said:
would you like me to remote control your computer to get you up and going using CM7?
Click to expand...
Click to collapse
Sure, I'll post my ID and PW to you if you have the time.

eoghan2t7 said:
ok download teamviewer then pm me the password and id numbers
Click to expand...
Click to collapse
ok i will do that. anything i should download to speed this up while your logged in?

stompazorb is now with the CM7 users
kdm212 will be joining use tomorrow in the CM7 world

Ran into a brick wall when it came to mount the SD-card.
It was FAT, now it is FAT32 - no change.
Read something about activating adb thru debugging mode - but I must've missed something, it doesn't work.
What's wrong?

stompazorb said:
Ran into a brick wall when it came to mount the SD-card.
It was FAT, now it is FAT32 - no change.
Read something about activating adb thru debugging mode - but I must've missed something, it doesn't work.
What's wrong?
Click to expand...
Click to collapse
i thought you were helped? you dont have cm7?

kdm212 said:
i thought you were helped? you dont have cm7?
Click to expand...
Click to collapse
Yes I do, but it's not exactly flawless, and it was a truckload of work to get it running.
Still haven't been able to mount the sdcard, any suggestions?

try completely formating it in windows and if that doesn't work try formtting in android

eoghan2t7 said:
try completely formating it in windows and if that doesn't work try formtting in android
Click to expand...
Click to collapse
Nope, didn't work, not even after low-level formatting.
But I had a spare SD-card, put it in and it worked right away. Seems like cm7 not accepting every sdcard-brand.
I do not know what the brands are, None are known, and no logos.

3.41 bootloader info from google support

Well I decided to call Google about the boot loader recovery not working as it should. I was hoping this call would help them to work on another update but they say that's the way its supposed to work. Here's the email Instructions:
1. Power down your device
2. Press and hold both volume keys and the power button to enter
Bootloader mode
3. Press the volume keys to cycle to the Recovery mode option
4. Press the power button to select Recovery mode
5. From the Recovery mode screen, press and hold the Power button then
press the Volume up button.
6. Use the volume buttons to select wipe data/factory reset.
7. Select Yes -- delete all user data.
8. The factory data reset process will now start. Once its finished,
select 'Reboot system now.'
The only option we have in the new recovery is to wipe data. Maybe for those having problems accessing twrp or cwm will be able to a access it with step 5. I don't know haven't rooted yet. So I decided to ask about nvflash and they said they're not going to release any nvflash tools or files.

um, yup. thats how stock bootloader and stock recovery work. lol
whats the issue? if your not even rooted, you wouldn't even know if you have an issue or not with the new bootloader.

Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.

xjman said:
Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.
Click to expand...
Click to collapse
No. I saw people posting they couldn't get go cwm and could only see the red exclamation point. And I was just saying maybe after choosing recovery then holding volume up and power it would then go to cWm or twrp. I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was

kieso said:
I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was
Click to expand...
Click to collapse
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app

smirkis said:
didn't know being informed makes me an asshole. stupid me, reading and understanding.
for what its worth, im on the newest bootloader, and selecting recovery goes straight to twrp. which is the recovery i installed.
Click to expand...
Click to collapse
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?

mr_tris said:
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info. I'm going to try unlocking and rooting when I get home. I really want to use the OTG cable and the 720p mod.

kieso said:
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?
Click to expand...
Click to collapse
When I first flashed TWRP onto my Nexus 7 after that official 4.1.2 OTA update, I wasn't able to boot into it. I then flashed it again via fastboot, and then booted the TWRP image that was on my computer, and then TWRP loaded.
I believe TWRP does work normally now as well (I can boot into it and reboot into it).

kieso said:
I'm going to try unlocking and rooting when I get home.
Click to expand...
Click to collapse
Well if I was you I'd just use mskips toolkit, its absolutely epic it'll save you a lot of farting around. I take it that your fully updated? ( Not that it matters) You seem to know and understand your way around adb so just go for it and enjoy.
Its works smooth as silk and save you a lot off time. The options available to you are just staggering!
http://forum.xda-developers.com/showthread.php?t=1809195
Sent from my Nexus 7 using xda app-developers app

Thread Cleaned​
No need for personal insults, lets just try to help each other out and show each other some respect.​

going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.

There are plenty of people that are having issues with recovery on 3.41 bootloader.... Its confirmed some have it some don't.
The issue is that with 3.41 bootloader on some Nexus 7 Devices a custom recovery is unbootable no matter how you try, every time it will try to load recovery and fail at a black screen then reboot into the OS. It does not matter how you try from ADB reboot to recovery or from bootloader with USB attached or not.

psycho2097 said:
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.
Click to expand...
Click to collapse
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.

kieso said:
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
Click to expand...
Click to collapse
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers

mr_tris said:
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers
Click to expand...
Click to collapse
Thank you for all the help! I appreciate it.

kieso said:
Thank you for all the help! I appreciate it.
Click to expand...
Click to collapse
No problem, a click on the 'Thanks' button for me and my colleagues on this thread would really make our day. :thumbup:
I hope you get sorted mate, I wouldn't be able to sleep at night until I got custom recovery working properly on any of my devices!
Sent from my Nexus 7 using xda app-developers app

i tried changing the name of the file, but.. after reboot, the tablet gets stuck on google screen, recovery never loads... any suggestion? Thanks =)