hi, after installing the rom manager premium and installing the latest nightly build i no longer can access the recovery. i installed the latest recovery the rom manager said to do, and now i reboot my phone and hold the home button and it just stays in the g1 screen. if i reboot and hold the home button while the phone is connected to usb the phone enters the fastboo g1 bootlader but in the same g1 screen but with red letteres on the corner. i need help. thanks.
fastboot still works but i dont want to have to do all that process again
I would just flash another recovery with fast boot. You won't ned to re root
Sent from my SGH-T959 using XDA App
how do i do this?
djbootleg said:
how do i do this?
Click to expand...
Click to collapse
1: use ADB :
connect ur device with PC , use CMD : type path to ADB folder and then
type : adb shell : enter
type : #mount -a
type : #flash_image recovery /sdcard/recovery.img
reboot
2 : use terminal :
type $Su
type #mount -a
type : #flash_image recovery /sdcard/recovery.img
3 : use Droid explorer tool : download and install newest version
copy img file to sdcard
connect ur device with pc
u'll see a red icon ( Fl ) , click there and show the path to ur img file => ok wait 1' and reboot ur fone
if unsuccessful, u can change ur sdcard and try again !!! ^^
I ran into this issue as well, assuming it's a bug with the latest update of ROM Manager (which I just updated this morning prior to getting this issue.)
Not sure if it had anything to do with the fix but after some fiddling I decided to try reinstalling the ROM Manager recovery (after reinstalling the amon ra recovery from the same app with no success) and it worked, YMMV obviously but that worked for me.
This happened to me too!
Hello,
i'm following this forum a long time, now. But at the moment I have a problem rooting my Vodafone Nexus One I can't solve.
It has 2.2.1 (FRG83D) on it. I unlocked the bootloader using fastboot. Now it shows the open lock when booting.
When I try to install a custom recovery using adb or terminal emulator, all looks good. But when i restart and go into recovery menu, always that damn standard menu appears (after putting power on & volume up).
Now I read, that I have to delete the install-recovery.sh in systems/etc and another file, I don't remember right now. I always get an error, when I try to delete or rename them. I tried it using adb, terminal and root explorer.
Does anyone have a clue how I can get rid of them?
Thanks!
Marco
Use fastboot, since you've already gone to the trouble of unlocking your bootloader...
fastboot flash recovery name-of-recovery.img
fastboot boot name-of-recovery.img
You have to remount the system partition as writable.
You only have to delete the install-recovery.sh file. The other one can be left alone.
hey guys, thanks...
i just did it using the following program and steps:
* - Download Superboot and extract it to a directory on your computer
* - Put your device into bootloader mode. You can either use ADB or turn the phone on whilst holding the trackball to enter the bootloader.
* - If on Windows double click ‘install-superboot-windows.bat’
* - If on a Mac, cd into the directory containing the files and type ‘chmod +x install-superboot-mac.sh && ./install-superboot-mac.sh’
* - If on Linux, cd into the directory containing the files and type ‘chmod +x install-superboot-linux.sh && ./install-superboot-linux.sh’
after that i had to remount it as R/W partition.
If you are new to rooting your phone, there are simple ways to go about getting clockwork mod onto your LG thrill
You can root it easily with the 1 click root tool (I dont have the link on hand) after installing the LG Drivers from the LG Website.
Then, Download Rootexplorer, Rom manager (which i think is installed with 1 click root along with superuser)
First thing, download the recovery.img here after installing ADB guide is located here
After downloading recovery image, go to your pc's user folder C:\users\yourname and move it to there, that way there is no mistaking its location for adb
Now, on your phone you first need to go into root explorer, go to the /data folder, long click and go to permissions and select all available boxes and also make sure your device is in R/W mode not R/O mode.
Run CMD as administrator and do the following:
adb push recovery.img /data
then type:
SU
(this makes superuser active)
then:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
then after clockwork is flashed to finalize the settings type:
rm /data/recovery.img
reboot
Presto, Clockwork Mod is installed, remember you can access the clockwork menu via rom manager menu, or 3D+Volume Down +Power releasing the power button when the LG screen appears.
I will soon post onto this, how to update to gingerbread just making sure it works well on my own first. also, working on ICS as well.
Hope this helps anyone who has had trouble with it!
kobos311 said:
If you are new to rooting your phone, there are simple ways to go about getting clockwork mod onto your LG thrill
You can root it easily with the 1 click root tool (I dont have the link on hand) after installing the LG Drivers from the LG Website.
Then, Download Rootexplorer, Rom manager (which i think is installed with 1 click root along with superuser)
First thing, download the recovery.img here after installing ADB guide is located here
After downloading recovery image, go to your pc's user folder C:\users\yourname and move it to there, that way there is no mistaking its location for adb
Now, on your phone you first need to go into root explorer, go to the /data folder, long click and go to permissions and select all available boxes and also make sure your device is in R/W mode not R/O mode.
Run CMD as administrator and do the following:
adb push recovery.img /data
then type:
SU
(this makes superuser active)
then:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
then after clockwork is flashed to finalize the settings type:
rm /data/recovery.img
reboot
Presto, Clockwork Mod is installed, remember you can access the clockwork menu via rom manager menu, or 3D+Volume Down +Power releasing the power button when the LG screen appears.
I will soon post onto this, how to update to gingerbread just making sure it works well on my own first. also, working on ICS as well.
Hope this helps anyone who has had trouble with it!
Click to expand...
Click to collapse
All of this is already posted as is the instructions on how to update to gingerbread.
i have install CWM by as your guide. but when i use Rom Manager to Back up , message pop up that install CWM first to complete this action. i am new to these things.
Thanks
Hello, as I said in the title, I have a problem with the recovery menu (Same with OR) - problem is I can boot in recovery (the screen with the triangle) but there can not go to the menu. I press Volume Up + camera and nothing happens. Remains the same screen with the triangle and phone.
Please give me a solution because my phone is moving very slowly with Android 2.2.x
Device - Motorola a853 Milestone
Bootloader - 90.78
Button on the camera work, as well as the volume.
What could be the problem?
Sorry for bad English ..
Come on guys, 26 views and no response to my question?
I searched all forums and tried all the solutions posted there, but none worked! But those were old solutions ...
No one knows who could be my problem?
Not sure what kind of problem you are facing. You can surely try this.
Looks like OR is not loading in ur case. You can download the latest OR, I'm using minimod OR, copy the update.zip file into the root of SD card, again reboot into recovery. If u find ur milestone stuck in triangle button try pressing volume up button. This time it should invoke the OR or it should ask u to update the zip file.
Still if it doesnt works i think u have to take advice from experts who can help u to use ADB comnands to troubleshoot further. Anyways best of luck.
Sent from my Milestone using xda app-developers app
like the last post, you should verify if you have OpenRecovery folder and update.zip file in your /sdcard.
You can try via adb or terminal emulation "reboot recovery"
I tried what you said nagabushan.c, but it does not work ... Always the same problem, no menu displays..
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
nagabushan.c said:
At least do u get exclamatory mark when u booted or milestone while pressing camera button ? Then give a sec gap and then press volume up button.
Any device both rooted or non rooted should display this.
Try ADB steps..
Let us know what u observe
Sent from my Milestone using xda app-developers app
Click to expand...
Click to collapse
I see an exclamation mark only when you press power + x (bootloader 90.78).
I tried ADB steps..not working.
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
What rom you said you currently have?
Have you installed vulnerable recovery?
Have you verified OpenRecovery folder and its update.zip on sdcard? Try to re-download and unpack it fresh new.
I tried, does not work ...
What rom you said you currently have?
Stock rom 2.2.x.
Have you installed vulnerable recovery?
Of course, just as there's no difference ... the menu does not show.
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
mrvek said:
The menu should show. Any menu. Either from stock or OpenRecovery. I would try with a different sdcard because the older kernel (2.6.29) in recovery does not support some cards well. If the buttons are working and you have installed everything correctly then it should work. I'd try with different sdcard.
Alternatively, you can try to tell recovery to apply update.zip from sdcard automatically
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
but note that I am not sure if you need to be rooted for that. I assume not. You can either install Terminal emulator from PlayStore or enable usb debbuging in settings and try to connect through adb if you choose to try.
To see if adb detects your device
Code:
adb devices
if all is OK you should get some output (aphanumeric) and after that 16 characters, it should display in what mode is your device (device for a normally booted system, recovery for device in recovery...)
And then
Code:
adb shell
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
reboot
I'm no expert but it might be an unsupported sdcard...
Click to expand...
Click to collapse
Here's what I get from cmd:
C:\android-sdk\platform-tools>adb devices
List of devices attached
04037B7518003010 device
C:\android-sdk\platform-tools>adb shell
# echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
cannot create /cache/recovery/command: directory nonexistent
#
My device is rooted wth "superoneclick" method.
es7ar said:
cannot create /cache/recovery/command: directory nonexistent
Click to expand...
Click to collapse
Create it.
Code:
adb shell
mkdir -p /cache/recovery
mrvek said:
Create it.
Code:
adb shell
mkdir -p /cache/recovery
Click to expand...
Click to collapse
C:\android-sdk\platform-tools>adb shell
$ mkdir -p /cache/recovery
mkdir -p /cache/recovery
mkdir failed for -p, Read-only file system
$
Try without -p
Code:
mkdir /cache/recovery
mrvek said:
Try without -p
Code:
mkdir /cache/recovery
Click to expand...
Click to collapse
I created the folder "recovery" inside "cache" with root explorer.
Now cmd shows me: ( check attachments )
are you missing "echo"?
Code:
echo "--update_package=SDCARD:update.zip" > /cache/recovery/command
it simply writes what is in the first argument (in quotes) to file named "command" located in /cache/recovery
Edit: you can ommit adb devices. You just test the first time when you connect to be sure if adb detects your device. After that it should generally give "device not found" or something like that if connection to device is lost.
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
es7ar said:
I do not understand ...
The command "echo" - update_package = sdcard: update.zip "> / cache / recovery / command" should create a file called "command" in the folder "recovery" from the "cache"?
If so, there is no file called "command"
Sorry, I'm newbie ... I do not want to stress you out.
Click to expand...
Click to collapse
Yes, it should create that file with that content, to instruct recovery to automatically apply update.zip.
You can try to create that file manually with the
Code:
--update_package=SDCARD:update.zip
content in it.
Could you post the content of
Code:
mount
executed in adb? i was sure you can write to cache, it should be mounted read-write.
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
es7ar said:
Edit : Hmm ...
Instead of reboot, like you said, I typed "reboot recovery" then restated the phone ... and the loading bar appears. The phone has rebooted when it came to approx. 30% ..
Click to expand...
Click to collapse
hm...
could you please execute in adb:
Code:
ls -laR /sdcard/OpenRecovery /sdcard/*.zip
post output.
Okay, it looks like it was done!
You've explained it very well ... but I did not openrecovery and update.zip in sdcard.
I thank you so much for helping me! Thanks a lot!!
es7ar said:
but I did not openrecovery and update.zip in sdcard
Click to expand...
Click to collapse
That leads us back to the very begining of the process...
Is it possible to boot into CWM directly.
I am currently using this..
Bricked my phone while renaming framework-res.apk to framework-res.apk.bak .
Can't use adb push in recovery "Read-only file system" error..
Can't use adb remount as well, "Operation not permitted"
Edit: Sorry, please delete this thread. Found a way to rename back the framework-res.apk within recovery and using adb shell