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
Related
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.
I am unlocked and rooted. I checked with a root check app and it says i am...
Not sure if this has already been posted, but whenever i flash Romracer's cmw5 I can only boot into CWM Recovery under one condition. And that is:
Right after I type "fastboot reboot" and hold the volume down button right as it's rebooting. From here, when I select Android recovery, i can boot into CWM. Any other times, I.E. If i let the phone boot up to the point where I can make phone calls.and other stuff and power down afterwards and try to boot into CWM via Android recovery, the android with the exclamation pops up. At which point, I have to re-flash CWM every time.
Also, I finally found recovery-install.sh, however whenever i try to select it with astro file manager, it says "activity not found" or something like that and won't let me delete it. Does this have any effect on not being able to boot into CWM Recovery?
Thanks for the help, having to reflash CWM is annoying.
PS: I downloaded the file "Blue 5.0.2.7-atrix5 / ZIP version" from http://forum.xda-developers.com/showthread.php?t=1204500 and the file name saved as
"recovery-blue-atrix5.img". So when I type it into the command prompt, I would actually type the exact command of
"fastboot flash recovery recovery-blue-atrix5.img". I know the directions say that the command is "fastboot flash recovery recovery-atrix5.img" Is there any chance that my problem is resulting from this discrepancy in the file name?
Update: I found the CWM boot method inside CM7 itself and it works. Does this mean i'm scott free? Or should i continue to try and delete
"recovery-install.sh"?
If you have that file in /etc, it should be deleted. You don't need to use a file manager for that, a terminal or adb will do.
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Mcsquizzy said:
Hi there everyone!
My main problem is flashing hboot 1.15
I misinterpreted a sentence of instructions over at ViperDNA ROM thread, and attempted to flash Viper 1.3.0 with a custom kernel (it had been so long, I forget which. Cubed or DSB, idk) and after getting through aroma and successfully installing, it was stuck at a bootloop. Well I went back and read the instructions and comment again and apparently installing with anything other than Stock boot.img is a big no no. Anyways, I am stuck here without any type of ROM (relocking the bootloader to attempt to RUU.exe left my internal storage wiped) and unable to get the RUU.exe method to work (Error 155 most likely because I have hboot version 1.33.0001 and not 1.15). I cannot get the RUU.exe or the RUU.zip flash method to work. I have flashed a stock boot.img since then and have gone through different locked/relocked stages and tried ADB sideloading a stock ROM ("unable to mount /data /system" etc.). Right now, I am trying (using the HTC Droid DNA Toolkit program) to flash the 1.15 hboot, but it is stuck at "<waiting for device>". I have also tried "fastboot.exe fastboot oem rebootRUU" and got the same response. I don't know what else to do and I am deeply worried that I have bricked my DNA. I understand that I am completely responsible for attempting these things and for my errors, but I need help in getting back to any form of android so that I can reinstall Viper 1.3.0 with a stock boot.img (like I should have in the first place).
I appreciate all of your help and I hope someone knows what can be done here! Thank you guys!
Click to expand...
Click to collapse
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
try this: boot into recovery and plug the device into the computer then try adb devices and see if the device ID pops up if in fact it does do a:
adb push romzip.zip /sdcard/romzip.zip
or
adb push \path\to\romzip.zip /sdcard/romzip.zip
and it will push it to the /sdcard directory, then reboot the recovery and flash the rom and it should just work
.torrented said:
I can tell you that it's not bricked just having a bit of bad luck.
First off try a different USB port, second there really isn't a need to RUU if all you are doing is trying to reflash a rom correctly.
you didnt happen to flash the boot.img to the hboot partiton? cause that would be bad. (DO NOT DO THIS)
Click to expand...
Click to collapse
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Mcsquizzy said:
I have tried on another (Windows 7 64-bit laptop with correct drivers) computer and multiple USB ports. In the process of unlocking/relocking using an AllInOne Toolkit, it wiped everything from my internal storage (as it said it would). I can flash kernels and recoveries (using TWRP atm) but when I try to flash a ROM (installing using the TWRP recovery) I get messages saying "unable to mount /data" or "unable to mount /cache" and I am unable to check the boxes "Mount Data" and "Mount Cache" within the recovery (I can only check "Mount System" and thus I am unable to wipe/ factory reset/flash a ROM. I have no idea if I flashed a boot.img to the hboot partition, but I have only flashed a boot.img using the Droid DNA All in One Toolkit and also by using the "fastboot flash boot boot.img" command. How can I tell if I flashed it to the hboot partition? I am able to get into bootloader and reboot into RUU using the "oem rebootRUU" command, if that helps determine whether or not I messed up. I recieve a "Error [155]" message every time I use the RUU.exe on both computers, and I read on another post that this could be caused by the wrong hboot version (RUU.exe 'wants' a 1.15 hboot version, but my bootloader is saying I have the 1.33.0001 hboot version) on my DNA. Perhaps this is the cause? In any case, I have been working to flash the 1.15 hboot so that I can successfully flash the RUU.
Thank you for your help and patience!
Click to expand...
Click to collapse
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Mcsquizzy said:
Well... I just kept trying the RUU.exe over and over and over again and it finally worked I don't believe I did anything different, but I have tried so many different things I completely lost track Anyways, thank you for your help and patience, again
Click to expand...
Click to collapse
I flashed Viper 1.3.0 with BeastMode 5.9 and it's running fine no bootloops of any sort
I don't have much experience rooting, but what I did was unlock hboot 2.09.0000 so far, with twrp installed to recovery, but I tried to flash beanstalk and grappa subsequently without rebooting and I think that might have caused it to not work. In the process of trying to fix the boot loop, I also wiped all data, including my backup for the stock rom. Therefor I do not know how to get a new rom onto my phone. I have a folder with adb, fastboot, adbwinapi.dll, and the beanstalk and grapps. I tried typing adb push "beanstalk file name here" /sdcard and that doesn't seem to do anything. It just gives me a big list of adb commands. Any ideas?
bposch said:
I don't have much experience rooting, but what I did was unlock hboot 2.09.0000 so far, with twrp installed to recovery, but I tried to flash beanstalk and grappa subsequently without rebooting and I think that might have caused it to not work. In the process of trying to fix the boot loop, I also wiped all data, including my backup for the stock rom. Therefor I do not know how to get a new rom onto my phone. I have a folder with adb, fastboot, adbwinapi.dll, and the beanstalk and grapps. I tried typing adb push "beanstalk file name here" /sdcard and that doesn't seem to do anything. It just gives me a big list of adb commands. Any ideas?
Click to expand...
Click to collapse
It looks like you didn't get S-off yet. If you haven't, your issue is that you didn't push the kernel in with ADB. There is no real reason to not go S-off, go get it and then flash whatever you want. If you don't want to do the S-off then you need to learn how to push the kernel in before you flash a ROM that requires it, and Beanstalk requires it since it is CM based.
Since you're on hboot 2.09 there are two you could use for S-off:
http://forum.xda-developers.com/showthread.php?t=2321072
http://forum.xda-developers.com/showthread.php?t=2498684
To get a working Rom on your phone, download meanbean (s-on friendly) to your pc. Boot your phone into recovery and connect to your pc. Select mount in TWRP and mount usb storage. You should see your phone on your pc. Drag the Rom to your phone then unmount, install the Rom with TWRP. That should get you up and running. Then get yourself s-off. Life is easier.
EVOlved human
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app