Develop Bugs

How to change bootloader from cyanogen rom to Amon Ra's

Any one know if this is possible I would like to use Amon Ra's as it allows you to partition the sd card. I can't figure out how to do this without using Amon Ra's

This is the Hero forums, we don't a Cyanogen recovery. I would recommend you consult the Dream or Sapphire boards. But to answer your question it should be as easy as:
Code:
adb push <the recovery you want to use>.img /sdcard
adb reboot
The phone will restart. After it finishes restarting you type the following commands:
Code:
adb shell
su
cd /sdcard/
flash_image recovery <the recovery you want to use>.img
reboot recovery
And you will be in the new recovery.

Also using modaco 3.1 (which is excellent) just cant figure out the aps2sd part
I am using the htc hero maybe I got mistaken but when I boot in recovery mode
I get a pic of a green android and the following options
android system recover
reboot system now
apply sdcar updare.zip
apply any zip from sd
wipe data factory reset
nandroid 2.2 backup
restore lates backup
repair ext file system
Build Cyanogen mod 1.4 +jf

The Cyanogen recovery should not be able to run on a HTC Hero...

gu1dry said:
The Cyanogen recovery should not be able to run on a HTC Hero...
Click to expand...
Click to collapse
You can make it.
Just replace the kernel in the img and it should work just fine.

Of course Cyanogen works on Hero.
It was used in plenty of tutorials on how to root your phone.
I ended up with it as well.
I might want to change to Amon however... I don't have a need for the moment.

Hmmm I used a tutorial as well must of been an old one.
How to I partition the sd card so.

mickb00 said:
Any one know if this is possible I would like to use Amon Ra's as it allows you to partition the sd card. I can't figure out how to do this without using Amon Ra's
Click to expand...
Click to collapse
In the RA-hero-v1.5.2 topic it has a section: Install ...via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
thats at forum.xda-developers.com/showthread.php?t=561124
You can use the flashrec as well.. theres a guide here forum.xda-developers.com/showthread.php?t=622228&highlight=Root
you only need to do steps 1-6 on the second method.
im in the same boat as you i still have the cyanogen recovery im going to use flashrec tomorrow tho.. to tired just now lol
hope this helps you

Lads got it working thanks for all the help. Just used my current recovery with the adb shell commands worked a charm

A rooting attempt gone astray

So I was trying to root my evo so I could try the fresh rom (please note that this was my first ever root attempt and my phone had the OTA update). I followed the instructions from this guide:
Latest OTA rooted! - Page 2 - Android Central Forums
This is where my problem is:
11. Once back at the Home screen type:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
When I enter the "cat /sdcard/flash_image > /data/flash_image" code I get:
"cannot create /data/flash_image: permission denied"
After some googling I found other people typed "su" prior to typing in the "cat /sdcard/flash_image > /data/flash_image" command. That didn't work for me. I received "su: permission denied" after entering su.
Would going back and starting this tutorial all over cause serious damage? I'm wondering if maybe I messed up earlier.
I'm very worried I really screwed something up. Can anybody please offer up some advice for a newbie?

Weigh the stakes
Man, just try the "SimpleRoot 1.47 OTA update" app for Windows. You save time, money and a lot of feces on your tract by the worries that everything is ok.
Now, I want to remind the stakes. If you haven't looked at my post here at Q&A, I pretty much effed up my phone while being rooted. I don't know if it was too much exposure to heat caused by WiFi Tether, or of mysterious powers regarding the RSA 256 bit encryption update process screwed my phone up. So before trying to crack your phone, please, review the stakes and stay stock.
BTW, you haven't completed the root process, so a simple Factory Reset should do the trick to go back into Stock without any trace of root procedure. That is, if you want to play it safe.

Okay, first things first. Just so I'm clear.
1. Which guide(exactly) did you follow?
2. What software version do you have now?

Yeah i was having problems with my administrator password so I switched from simple root to this method. Maybe I was using the wrong version or something, could you post a link to simple root for ota?
churchwin88 said:
Okay, first things first. Just so I'm clear.
1. Which guide(exactly) did you follow?
2. What software version do you have now?
Click to expand...
Click to collapse
1. http: // forum.androidcentral. com/htc-evo-4g-roms-hacks/ 21043-latest-ota-rooted-2. htm
2. My software number is 1.47.651.1
Thanks for the help

StrummingLevi said:
Yeah i was having problems with my administrator password so I switched from simple root to this method. Maybe I was using the wrong version or something, could you post a link to simple root for ota?
1. http: // forum.androidcentral. com/htc-evo-4g-roms-hacks/ 21043-latest-ota-rooted-2. htm
2. My software number is 1.47.651.1
Thanks for the help
Click to expand...
Click to collapse
For the 1.47 you need to use this version of simple root(if you haven't already) - http://forum.xda-developers.com/showthread.php?t=720565
I'm not sure why it would have problems with the password. Only thing I can think of would be something along the lines of not having administrator privileges.
EDIT: Make sure to have all the requirements and if you successfully run that let me know so we can proceed to the next step(it is really simple).

I did the simple root for 1.47 and it was a success! Although I did not understand what the flash recovery did. I tried the clockwork recovery and it took me to a screen with a bunch of options, but I didn't know what to do so I just rebooted. What's next? I want to try the newest version of the fresh rom.

TO try fresh first download it and place the zip file on your computer, boot into recovery, (power phone off then hold down volume and power untill you get to the white screen) select flash zip fron sd card then select the fresh rom and flas, presto fresh should flash, the recovery is a seperate area which is used to flash a rom, as you cant flash a rom from within a rom.

So do I use the clockwork recovery to flash the fresh rom? I was looking at the guide to flash the new fresh rom and it says that I need to have nand unlocked. How do I do that?

if you did simpleroot nand should be unlocked, and yes clockwork recovery is used to flash the fresh rom. clockwork recovery is what you are in when you boot with the down volume and power button held down. If it doesnt work you may want to try amon ra recovery, find the toast root method and do the last step:
- on your PC open a shell again and do:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
- you should now be in recovery mode
- do a wipe of data and dalvik cache
- navigate to nandroid restore and restore the previous rom setup
- come here to the forum, get and flash the latest radio
- enjoy... you can now reboot into recovery, write to system and other partitions while in Android. Also you now have a Engineering SPL so you can fastboot and much more.
It also wont hurt to do the whole part two of toasts guide if you dont think your nand is unlocked. FYI Nand unlocking allows both a read write option in the recovery which is needed to write the custom roms.

StrummingLevi said:
So do I use the clockwork recovery to flash the fresh rom? I was looking at the guide to flash the new fresh rom and it says that I need to have nand unlocked. How do I do that?
Click to expand...
Click to collapse
Your nand is unlocked. Just download Fresh, boot into recovery, wipe caches, and apply Fresh via zip file.
ifly4vamerica said:
if you did simpleroot nand should be unlocked, and yes clockwork recovery is used to flash the fresh rom. clockwork recovery is what you are in when you boot with the down volume and power button held down. If it doesnt work you may want to try amon ra recovery, find the toast root method and do the last step:
- on your PC open a shell again and do:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
reboot recovery
- you should now be in recovery mode
- do a wipe of data and dalvik cache
- navigate to nandroid restore and restore the previous rom setup
- come here to the forum, get and flash the latest radio
- enjoy... you can now reboot into recovery, write to system and other partitions while in Android. Also you now have a Engineering SPL so you can fastboot and much more.
It also wont hurt to do the whole part two of toasts guide if you dont think your nand is unlocked. FYI Nand unlocking allows both a read write option in the recovery which is needed to write the custom roms.
Click to expand...
Click to collapse
Ignore this post, unless you want to flash Fresh with Amon Ra Recovery instead of Clockwork Recovery (what you have now)

Agreed, I was only posting that "if" he had problems using clockwork sorry for the confusion.

jerryparid said:
Your nand is unlocked. Just download Fresh, boot into recovery, wipe caches, and apply Fresh via zip file.
Ignore this post, unless you want to flash Fresh with Amon Ra Recovery instead of Clockwork Recovery (what you have now)
Click to expand...
Click to collapse
So I decided I was going to use Amon Ra's recovery because flipz recommended it. That was going well until "- navigate to nandroid restore and restore the previous rom setup". I selected nandroid restore and it said something like /sdcard/nandroid not found. Aster that I just rebooted , which took a while and had me pretty nervous. It eventually booted up though. This stuff is a lot more confusing than windows mobile was haha. I'm wondering if nandroid was indeed unlocked with simple root. I'm still willing to press forward if the help is still available. By the way, what and how can I make a nandroid backup?

Turn phone off, turn phone on holding down volume and power, when you get to white screen select recovery then scroll through your options, i believe it it backup/restore then creat nandroid backup, FYI you cant restore a nandroid backup if you haven't created one, IE the not found error you got before.

Ok so how exactly would I go about flashing(if that's even the right word) fresh rom from what I already have?

I'm not sure what you actually have, can you get to recovery, then the option to 'flash zip from sd card? if you have that option just place the fresh rom on the root of your sd card (put the zip file there and don't open the zip) then reboot to recovery, ie vilume down and power button when you get to white screen volume down to recovery, then flash zip from sd then select the fresh rom zip, then hit power button to select, hit power button again to confirm and away you go.

Ok that sounds simple enough. I can't thank you guys enough for all your help. What does a nandroid backup do?

it makes a copy of your rom basically, so say you put on fresh do a nandroid backup then flas CM6, you decide you dont like CM6, so you nandroid restore of your fresh and presto right back to where you were before you flashed CM6, also useful if you have screwed something up ... you can go back ... make sense?

[Q] Changed the builb.prop and now stuck in bootloop

I tried to change my build.prop file with ROOT EXPLORER to this:
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.board.platform=qsd8k
ro.build.product=ace
Click to expand...
Click to collapse
in order to able to run apps no compt with desire, but desire HD.
unfortunately, as I saved the file the device rebooted itself and is now stuck in bootloop. (edit: I also can't access recovery for some reason, it's stuck on E:Can't open /cache/recovery/command and doesn't let me flash the update.zip)
I saved a copy of the unedited build.prop file on the SD card.
How is it possible to restore the file into the /system directory (adb maybe)?
Thanks!
*I'm not currently S-OFFed
*I think that a full wipe and reflashing the ROM will solve it, but I prefer not to, unless it is necessary.
edit:
Now that I think of it, is it even possible to edit files in /system while device is booted and not S-OFFed?
Was that the cause of it?

You can restore your old build.prop via ADB while in recovery.
Here it is:
Connect the USB cable while in recovery and use the commands (from command prompt):
1) adb shell
2) su
3) mount -o remount rw /system
4) adb push build.prop /system
And reboot.

b1gdrag0n said:
I tried to change my build.prop file with ROOT EXPLORER to this:
in order to able to run apps no compt with desire, but desire HD.
unfortunately, as I saved the file the device rebooted itself and is now stuck in bootloop.
I saved a copy of the unedited build.prop file on the SD card.
How is it possible to restore the file into the /system directory (adb maybe)?
Thanks!
*I'm not currently S-OFFed
*I think that a full wipe and reflashing the ROM will solve it, but I prefer not to, unless it is necessary.
edit:
Now that I think of it, is it even possible to edit files in /system while device is booted and not S-OFFed?
Was that the cause of it?
Click to expand...
Click to collapse
Just reflash the ROM without wiping

Okay, this one never happened to me, but I can't access my recovery...
I press vol down + power button, and when the /!\ appears, and I press vol up + power button, it's stuck on the:
E:Can't open /cache/recovery/command
and doesn't let me flash the update.zip...
For the same reason, I can't reflash the rom.
Thanks you guys.

What recovery do you have (or had) ?
You tried from the bootloader?

I have CWM 2.5.0.7.
Tried what from the bootloader?
the abd commands?
It says:
adb server out of date. killing...
* daemon started successfully *
- exec 'system/bin/sh' failed: no such file or directory <2> -
Click to expand...
Click to collapse
or did u mean something else?

Well just boot into recovery (the main menu) and then execute the commands.
Oh and also go to the Mount options and mount /system.

Maybe I'm getting something wrong or I don't understand you well, but I can't access the recovery...
I rooted my phone in a pretty old method, and not using UNREVOKED, and in order to get into recovery I used fakeflash.
now, when I try to access recovery, in the bootloader, I press VOL UP + POWER, and now I get stuck on
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
and it doesn't let me flash the update.zip.
thanks for your help!

Manually rooting 4.0.4, is there someone able to do it?

As title,
is there someone who is able to manually root 4.0.4 without flashing (you can boot with it) CWM and without using su.zip file?
Is there a step by step procedure using commands without files?
CWM boot (not flash) is accepted.

If you want root access, you will need to install SuperUser.apk and the su binary. The su.zip file that you flash from ClockWorkMod does this for you. You can push the required files manually, but you will first need to boot an insecure boot image and will need to have some experience with ADB. I can help you out in more detail if you want, but this is the gist of it.
1. Boot CMW or an Insecure Boot Image for your ROM version (There's one for 4.0.4 in the Dev Section)
2. If using CWM, go into Mounts and Storage (It might not be under Advanced) and check "Mount System" and "Mount Data"
3. Follow the instructions on this post http://www.freeyourandroid.com/guide/root-galaxy-nexus-manually-windows (You will need Superuser.apk and the su binary file)

HTC One M8 stuck in boot loop cannot "adb push" help!

My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Is there anything we can do to push? Is it because i'm not successfully rooted?

technocrat7 said:
My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Is there anything we can do to push? Is it because i'm not successfully rooted?
Click to expand...
Click to collapse
The recovery does not require root as root is a thing for the Android system. You could always try doing adb sideload and using the command 'adb sideload viperOne.zip', that will sideload the ROM to your device and flash it. An alternative thing to try would be going into the 'Mount' section of your recovery and checking /system, /data, /cache & /boot and re-attempting it. If all else fails then you could attempt to do 'Format data' from the wiping section (take note these are for TWRP, not so sure about CWM).
Also all you need is the 'platform-tools' folder of the sdk. Lastly I would only recommend doing the 'Format data' option after you've tried everything else. If you don't really care about losing your pictures, music, etc then you don't really need to avoid it.

S1L3nTShaDoWz said:
The recovery does not require root as root is a thing for the Android system. You could always try doing adb sideload and using the command 'adb sideload viperOne.zip', that will sideload the ROM to your device and flash it. An alternative thing to try would be going into the 'Mount' section of your recovery and checking /system, /data, /cache & /boot and re-attempting it. If all else fails then you could attempt to do 'Format data' from the wiping section (take note these are for TWRP, not so sure about CWM).
Also all you need is the 'platform-tools' folder of the sdk. Lastly I would only recommend doing the 'Format data' option after you've tried everything else. If you don't really care about losing your pictures, music, etc then you don't really need to avoid it.
Click to expand...
Click to collapse
When trying ADB Sideload, it would always get to 64% and then fail.
Also if I go to "wipe factory data" through philZ, then what will that do?
This all happened when I put InsertCoin on it.

I don't know much about AT&T device as this is more of an Int'l GSM forum and I don't use recovery other than TWRP.
But ... this is basic things that should work for any device when you don't have an external sdcard. If you have one, just put the ROM.zip on it and install in recovery.
If there is no sdcard, Push the ROM.zip to internal sdcard
Put a ROM.zip in your adb/fastboot folder
Put your device in recovery then check the data is mounted
(TWRP - mount - data checked, other recovery maybe - mount & storage - mount data)
Then adb push it to internal sdcard
command : adb push ROM.zip /data/media/0/

That worked, thank you!
And it should be the same no?
I heard TWRP and PhilZ 6 were pretty much the same. I actually heard better things about PhilZ than TWRP

technocrat7 said:
That worked, thank you!
And it should be the same no?
I heard TWRP and PhilZ 6 were pretty much the same. I actually heard better things about PhilZ than TWRP
Click to expand...
Click to collapse
No comparison ... I prefer to try on my own and decide which is better rather then just swallow what people said.
And I like the simplicity of TWRP ... so it's personal preference, that's all that I can say

That's what I would've said too.
But the way you made it sound in your other post made it sound like TWRP can do more than PhilZ or something
I personally like Philz better, but yeah

technocrat7 said:
But the way you made it sound in your other post made it sound like TWRP can do more than PhilZ or something
Click to expand...
Click to collapse
Not that ... I said that I only use TWRP because the step that I mentioned is correct for TWRP but I'm not so sure for other recovery ... that's why I put the word "maybe" there.
(TWRP - mount - data checked, other recovery maybe - mount & storage - mount data)

Oh I see, and yeah it was pretty much the same. It worked