Recovery Image and Loading New ROMS - Droid Eris Q&A, Help & Troubleshooting

Hey all,
So I have a rooted Eris (checked positively using terminal emulator) running a 2.1v3 ROM. What I'd like to do is eventually get to the 2.1 OTA ROM.
Earlier I downloaded ROM Manager which, after some searching gave me some problems other people have been having. I can't flash to the ClockworkMod recovery image as it gives me a "Error occurred while attempting to run privileged commands!" message. I tried reinstalling, fixing permissions etc. all with the same results.
So now i'm trying to flash Amon's recovery image instead using Terminal Emulator and the command line:
su
flash_image recovery /sdcard/file_name_here.img
only to yield the message that the file could not be found or something. I'm on a mac and I saw another way on here that involves running commands from your computer to your phone using the skd. I started to do that only to run into a "permission denied" when attempting the first "adb" command line.
Am I missing something? I'm trying to read and re-read as closely as I can. I'm not entirely comfortable with this whole process but I'm trying to take the time to really understand it and i'm still having difficulties.

Well I only have a small bit of advice on this because I don't completely understand what you're doing, but when I was trying to run adb commands on my mac, I found that I couldn't get adb to work by running "adb shell" from within the tools directory of the SDK, but if I navigated up one directory into the main SDK folder then ran "tools/adb shell" or whatever, the adb commands worked.

If I go that route, I'll give it a shot.
What I'm trying to do in a nutshell is get Amon's (or any) recovery image on my Eris so I can load ROMS easier. Right now, if I were to boot into Recovery, I get the littly android guy next to a /!\ .. :/

Last night I tried flashing through FASTBOOT and my command prompt window stuck at
<waiting for device>
for about 20 minutes before I pulled the battery.

Related

[Q] Help with ANY recovery image please

I am sorry, I know this has been asked a multitude of times on the forums, and I have gone through probably all of them. Is it possible to flash a perminant Clockwork recovery image to the Aria? Is there a way to unlock HBOOT or turn the S-ON to S-OFF?
I am new to Android, but not to Linux, but if I am doing something wrong, please point me in the right direction.
I originally rooted my phone though the update.zip switch method.
Here is what I tried:
Unrevoked: Hangs at "Waiting for root" rebooting does not help.
The old update.zip adb method: This method works to get me into Clockwork to install custom roms, however it is not persistant, when I reset it goes right back to the stock recovery.
Rom Manager: No matter which version I select, it always says it sucessfully installed Clockwork, but when you try to reboot to the recovery console, nothing. Try Alternate Recovery is greyed out, even though I have AmonRa on the SD card
Fastboot: I assume because security is on, it is not allowing me to use the "fastboot flash recovery" command as it gives me a "failed signature" error
Terminal/Shell: Tried it from the adb shell, and the terminal emulator on the phone itself. I have pushed the recovery images I want to the sdcard but when I try to execute the flash_image command I get an "out of memory" or "no space left on device" error
Firerat's install script: I have executed this script and keep getting the error that says it "cn't move /system/bin/buggerd directory not empty" error
I have tried remounting /system rw, doesn't help in ANY of the cases.
I have tried every method I can think of, other than doing an unroot/stock rom recovery and starting from the top, but I was hoping to avoid that if at all possible.
Are there any sort of firmware updates to change my hardware versions? here is what I have (stock Aria stuff)
LIBERTY PVP SHIP S-ON
HBOOT-0.57.0000
MICROP-031b
TOUCH PANEL-STN21_03
RADIO-7.08.35.06
May 8 2010,03:56:58

Wrong recovery, now can't install any rom or recovery

Guys,
I need help. I tried to work the solution myself and spend days reading different forums and tried different tricks but no luck.
So basically I was asked by my wife to root her Hero as she wanted a higer version of Android to install Viber and some other programmes. I did that using instructions on a Cyanogenmod wiki and everything went fine. However the new rom made the phone a bit slow and clumsy, so I thought I'd look for a different older version that works. I tried numerous roms and they all for some reason were not suitable - either wouldn't boot or were force closing etc...
So at the end of the day I read somewhere that for some ROM you need to install a CWM recovery and I was running a RA 1.7. So I tried to download a newer version of a recovery (to be honest I forgot which one - it was a week ago) and I flashed it and then I realised I have installed a recovery for CDMA and I have a GSM.
So, currently the phone boots and gets stuck at the HERO logo forever. There is no way I can boot into recovery. I have no problem to boot into fastboot, but any attempt to install a different recovery brings a failed signature error. I tried fastboot erase recovery and it did work, but no instalation is possible. When the phone is powered on and while on HERO logo I can run adb and can make it reboot from the command line, but when I try the instructions http://forum.xda-developers.com/showthread.php?t=1630519 I get past the first two lines:
Code:
adb push recovery-clockwork-2.5.0.7-hero.img /data/local/
adb push flash_image /data/local/
and then when I attempt this
Code:
adb shell chmod 777 /data/local/recovery-clockwork-2.5.0.7-hero.img
I get an error message
-exec /system/bin/sh failed no such file or directory
Please help!
PS. A screen shot in fastboot:
http://i3.photobucket.com/albums/y78/tsvet/fastboot.jpg
I managed to fix that with a stock rom and Hboot installation.

[Q] Question about rooting

So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
none
I would start over. The posts on how to root are very good. There are also youtube videos you can watch. It really is very easy to root this device. if nothing else load a program called team viewer on your computer and I will root it for you, but I want you to try first. You will use something called rumrunner. PM me if you need help
AlphaMons said:
So I recently had my phone temporarily rooted via weaksauce, however, after updating to Sense 6 with the Verizon OTA update, weaksauce will not root properly and it continues to fail. Is there no way to fix this or am I missing something with the OTA update? I sort of need to use weaksauce because I am not confident in my rooting ability to be able to restore the phone to factory when I turn it in for an upgrade in a few months.
Click to expand...
Click to collapse
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Are you on hboot 2.49
statmonkey said:
I would second that. If you are going to root a phone for the first time this is the one to start with. It is extremely well documented and this is a very helpful forum. I had the same feelings when I started (HTC Wildfire) back in the day and I did about everything wrong but in the end figured it out. Now there a several helpful threads and videos as stated above. I would recommend that you do a dry run, have everything together and go through the steps one by one in your mind or on paper before doing the actual root. You may miss something but your odds are better. Trust yourself I thoroughly believe any can root this phone and it's easier than you think and the value besides learning of the great ROMs that are here etc. is well worth it. Even if you temp root it you are going to have to know what to do to get it back before you turn it in so the knowledge will be necessary.
Click to expand...
Click to collapse
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
mrkrowely said:
rumrunner will not work if he's on the ota update of sense 6, he will have to flash a custom recovery, do a nandroid backup, flash vipermax rom, and run firewater.
as to the OP, it's very easy to do, follow the guides for setting up SDK/ADB, download the appropriate custom recovery for your device (i personally like TWRP the best), place that file in your adb folder that you made from the SDK/ADB guide, unlock your bootloader if not already (i did mine via HTCdev, they have a guide). then boot into the bootloader via power+vol down, scroll with volume keys, and select with power button, go to fastboot, plug in your usb cable to your computer, if you have the drivers it will change on your device "fastboot usb". then open up a command prompt in your SDK/ADB folder (do this by shift+right click in the folder and select open command prompt here). in your command prompt type in "adb devices" to make sure your drivers are right and it see's your device. now type in "fastboot oem rebootRUU", your phone will go to a black screen that says HTC on it. now type in "fastboot flash recovery "put the name of the recovery file here".img", then after that completes without any errors, type "fastboot reboot-bootloader" press the power button with bootloader selected, scroll to recovery and press power button, once you're in recovery, do a nand backup of your stock rom, after you've done that while still in recovery, i would strongly suggest saving this backup file to your computer, you can do this in ADB by typing in "adb pull /sdcard/TWRP" and it will pull the entire directory with your backup in it.
to gain s-off and fullroot, download vipermax rom for your device, while in recovery still, you can put the rom zip file in your ADB folder, and in ADB type "adb push "Name of the zip file" /sdcard" and it will copy and paste the rom zip to your sd card, once you see it finish in the command prompt, click on install on your phone, scroll to the zip file and click on it.
when the phone boots up, make sure you connect to wifi and go through the setup, once that is done download the Firewater file, and follow the instructions. and you should get s-off, now in adb type "adb reboot recovery" and then click on restore, and restore your stock rom, now you're stock rooted, with s-off.
set up ADB guide/download here http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=226534558
TWRP guid/download here http://forum.xda-developers.com/showthread.php?t=2498746
Vipermax rom download here http://forum.xda-developers.com/showthread.php?t=2596938
Firewater guide/downloade here http://firewater-soff.com/instructions/
And i think that should be it, if after you do this and want to flash back stock recovery it's pretty simple, find and download the recovery image for the version of rom, you're using, for instance, your ota update should or will probably be in your downloads folder, if you open it with zip, (i use winrar) you will find a zip in it named "Firmware.zip" open it up, and you will see a file named recovery, extract it to your ADB Folder, boot into the "Fastboot oem rebootRUU", then simply type "fastboot flash recovery recovery.img" let that finish, then type "fastboot reboot" and it will start your phone, and now you'll have the stock recovery and be able to receive and install future OTA updates, if there is any. >.<
Click to expand...
Click to collapse
Really an excellent post it's nice to have all that in one place. I also was unable to get rumrunner to work and have used firewater quite successfully (which was part of what I was trying to point out above). Also, I was unable to get HTCdev to unlock my phone. That may or may not be about me. I am a Linux person and I think I might have had the wrong adb/fastboot at the time. The one in the android sdk did not work for me but for anyone on LInux who is interested the one in this link did http://forum.xda-developers.com/htc-one-max/help/andrenaline-rom-constant-reboot-t2853591
Once again, excellent summary, I will be bookmarking this for later.
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
bryanfritz1 said:
I think all of the above info is great and everyone trying to help is awesome. However I really liked having a soft root via weaksauce for a very limited amount of apps like titanium backup and root explorer. So am I to understand that there is no newer Weaksauce or similar available for 4.4.2 and sense 6?
Enjoyment to the MAX!
Click to expand...
Click to collapse
As far as I am aware firewater still works. I used it just a few days ago and just saw a post today http://forum.xda-developers.com/htc-one-max/help/gain-s-off-t2849836 although he doesn't clearly state that he was using sense 6,

[Q] Can't Get to Recovery, Flashboot doesn't see device

So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219​Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.

[Help]Adb Sideload Question

I am yet another idiot that wiped my tab 10.1, and then went to flash the ROM I had downloaded to it. So of course now I'm left with no OS installed and no files on board. I have TWRP installed and can still get to that. I can get to advanced > Adb Sideload. I can type adb devices in the command prompt, and my device is found successfully. But when I type adb Sideload ROM.zip, it states transferring then immediately says 0.00x transferred in the command prompt, and failed in red on the device.
I have never run into this and have googled to no end, but every post I find is related to Nexus devices. Can somebody please offer some insight so I'm not forever stuck in TWRP purgatory
Rather than use adb sideload, why not just use adb push to transfer the .zip file and then flash it normally?
As a last resort, you can also use Odin to flash a stock Samsung ROM or one of Pershoot's old Odin-friendly CM Roms too.
Sent from my GT-N5110 using Tapatalk

Categories

Resources