Database Develop

custom roms and radio updates fail

Hi all,
I am trying to flash my G1 to one of the nice custom roms. I flashed the recovery and spl just fine.
Now I cannot flash anything. I've tried different roms (cyanogen and dude's) and even tried flashing the radio. No love. The error is that it cannot find my sdcard or update.zip.
Phone is pvt and is rooted.
Any thoughts?
Thanks,
Hank

What steps did you take to root? Is your card fat32?

Did you mount the sdcard on windows? If you did, rename the file to update not update.zip on WINDOWS! Also, can you even mount your sdcard? If not, then there's your problem.

I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?

djscamper said:
I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?
Click to expand...
Click to collapse
That will probably help.. By default Windows hides the extension (the .zip part) so when you rename it to "update.zip" you actually make it update.zip.zip
Easy way to check is look at the original file.. if it says something like
Code:
update-cm-3.6.6-signed.zip
you need to rename to
Code:
update.zip
if it says
Code:
update-cm-3.6.6-signed
then just call it
Code:
update

Thanks. Getting a signature error now.
Will try a different version of the file once I am off Caltrain.

Yeah - if you have a modded recovery and get that error, it's most likely a bad download. Good luck.

That did it. It is always something so simple.
Thanks a ton. Hopefully this thread will help someone else as well.

A few questions about unrooting/wiping

I have a T-Mo G1 that had CM 4.1.11.1 on it and I was looking to upgrade to the newest stable, 4.2.1, using CM recovery 1.4. Something went wrong while upgrading so I decided to unroot the phone. I've read many guides on rooting and unrooting, but something just doesnt seem right to me.
1. When I return to rC29 should Telnet be downloading automatically? Does this mean I still have stored info somewhere in there?
2. When performing tasks in CM 1.4, such as flashing, it prompts me to reboot so I do it. Should I be returned to the recovery screen again after boot every time? I don't remember this happening before...
3. Which update.zip do I use when unrooting, the 177kb (droids on skateboards) or 205kb (red, green, blue, white) file?
4. Can someone give me a guide to unroot and fully wipe with CM 1.4?
Any help is appreciated, thanks alot.

I'll give you the steps to unroot which should answer your questions
1) Flash the stock SPL (the tri colour one). If you have 1.33.2005 (AKA Danger) SPL and you do downgrade to 1.1/RCx YOU WILL BRICK.
2) Flash the RC29 DREAIMG.nbh from the SPL - boot in to it by holding power and camera (it should be tricolour). Telnet should not magically be there, even if it was, doesn't matter
3) Put a recovery image of your choice on the root of the sdcard as 'recovery.img'
4) Flash the recovery image
1. Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
After that you can flash the 26I radio then a 1.5/1.6 ROM.

only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/

*Double post fail*

mrnv45 said:
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
He wants to re-root I believe, so not point updating.
RC29 and RC7 aren't root enabled ROMs, they just have security flaws which can be exploited to flash root enabled ROMs. Updating doesn't matter...

Thanks for your help, I'll be able to try this in about a half hour, will report back. As you said after step 4, I will need to flash a "26I" radio?
Had to install Telnet manually. Good to see a sign of normalcy here.
Flashing 26I Radio, HTC Recovery 1.6, and CM 4.2.1. Flash Radio, reboot, HTC, no reboot, CM 4.2.1, reboot. Right?
Tried the above, also tried with a reboot in between the HTC flash and CM 4.2.1 flash, stuck at G1 screen.

I'm still stuck at the G1 screen.

Probably be me next.
Finding myself having to do the same thing, somehow doing the CM 4.2.1.? whatever the last one was. I managed to lose root, be really nice to have a second card right now having to move 8 gigs off and repartition it to make it see the R29 image so i get to do literally everything all over again.
As someone once said, Ah Linux! Its Free! assuming your time is worth nothing. So true, lol. well ill be even better once it all works, if i can figure out what it takes to make it all work ill come back and try to help you out. Looks like mine wont see the image cause of my multi-partitioned microSD card. Not sure if yours is like that too or not, something to think about.

virtually painless
Kind of like virtual reality i guess?
Only gotcha i found in going back and reinstalling the RC29 image back on to be able to reclaim root was that my SD card having being partitioned. would cause it to fail. I would hit the tri-color screen, see a real quick gray flash and a message that vanished as quick as it popped up and then i would be stuck back on the colored screen.
So, i backed up the whole card, followed by
removing all data from the card. then running fdisk /dev/sdg. deleting the 3 partitions, writing a filesystem to the root of the disk via mkfs.vfat /dev/sdg , copying the 5 required files over and proceeding to get root and then recreating the paritions and copying data back over.
Back up and running.

mrnv45 said:
only way i found to unroot completely.. is to go bac thru the unroot process.. then update with an ota.. to remove all root...
unroot g1: http://theunlockr.com/2009/07/05/how-to-unroot-your-t-mobile-g1/
unroot mt3g: http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
Thanks XDA - have to do a TMo warranty exchange and this helps greatly.

First ever attempt at rooting...problem..!

So I followed a guide on youtube for rooting the g1 (should have followed ones on these forums ).
1. I am from the UK so downgraded to the DREAMIMG-RC7.zip first.
2. Then I installed the hardspl (update) and recovery.img.
3. Then did the telnet commands
4. Then downloaded command emulator and entered the commands
5. Finally I updated with the update.zip.
this is where it went wrong
6. I then tried to install open eclare but got this error :
E:Can't chown/mod /sytem/xbin/su
(no such file or directory) E:Failure at line 240: set_perm 0 0 04755 SYSTEM:xbin/su
Installation aborted
7. I rebooted it by back and home but it now gets stuck at the tombile g1 logo part.
I can press home and power to get to the screen, and camera and power does work.
Question...can I just start again by connecting the sd card to my computer card reader and then putting back the DREAMIMG-RC7 and starting again?

Which recovery image are you using?
You might want to try a different rom before openeclair, it needs the death spl, which you don't want to touch just yet. I recommend superD or htcclay fasttest.
Upgrade your radio as well if you haven't already. If you go near the deathspl with the original radio, you'll find out why it's called death.

You got the error because that rom requires the 1.33.2005 spl. Link for radio and SPL are in my sig.

Need Help...can't Downgrade To Rc29

So I've had my G1 for a while now on the stock non-rooted OS and I decided to try to get a 2.1 rom installed on it. After looking around and reading quite a bit, I primarily went off of this blog post to get it done. hxxp://www .myhangoutonline.com/component/content/article/342-tutorials/7-root-and-upgrade-your-g1
I got it downgraded to RC29 successfully and went through the rooting process. Once I tried to reboot it into recovery mode, my phone just sat at the G1 screen indefinitely. Waited up to an hour and restarted the entire process about 3 times with the same result. Then I started looking around thinking maybe the DREAIMG.nbh file that was provided was no good and I got one linked off of this site hxxp:// androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
So the next time I tried to start over by restoring to the RC29 image it gets all the way through and fails at the end. It says "Update Terminate UPDATE FAIL". I tried going back to the image that worked a few minutes prior to that and I'm getting the same thing.
Any ideas on what I need to do? I'm stuck without a phone until I get this resolved...

Your post is difficult to understand.
The first question:
WHY did you install an NBH file?
The second question:
WHAT *exactly* did you do to the thing?
The third question:
WHY are you trying again to install an NBH file?
The fourth question:
What is it doing now?
The fifth and final question:
HOW can you possibly justify following a bunch of steps that some retard spewed out on a "blog"?
Note: NEVER NEVER NEVER NEVER write an NBH file to your phone!!! Especially once you have root! NEVER.
Note2: you say its stock tmoble-branded htc dream? That means android 1.6 and I believe susceptible to the 1-click-root bug... why didn't you run the 1-click root?
What happens if you try to boot the phone ***NORMALLY*** (instead of recovery)?
What happens if you plug in the USB and run "adb logcat"?

lbcoder said:
Your post is difficult to understand.
The first question:
WHY did you install an NBH file?
The second question:
WHAT *exactly* did you do to the thing?
The third question:
WHY are you trying again to install an NBH file?
The fourth question:
What is it doing now?
The fifth and final question:
HOW can you possibly justify following a bunch of steps that some retard spewed out on a "blog"?
Note: NEVER NEVER NEVER NEVER write an NBH file to your phone!!! Especially once you have root! NEVER.
Note2: you say its stock tmoble-branded htc dream? That means android 1.6 and I believe susceptible to the 1-click-root bug... why didn't you run the 1-click root?
What happens if you try to boot the phone ***NORMALLY*** (instead of recovery)?
What happens if you plug in the USB and run "adb logcat"?
Click to expand...
Click to collapse
1. I installed the nbh file because that's what was in every single set of instructions I've found said to do. Step 1 is to downgrade your phone to RC29 for US phones, and the DREAIMG.nbh file is the way to do that from everywhere that I've seen, mostly here and the cyanogenmod forums. If there is a better guide to follow, please link me.
2. I've already explained this. I followed the following instructions:
1. Format your phone's SD card to FAT32 mode:
o Hook your phone up to your computer using a USB cable and then wait for the
notification to show up in your title bar of your phone.
o Click the notification, and then click "Mount".
o A new removable disk should show up on your computer. Right click it and select
Format, and select FAT32 as the file system type.
2. Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card.
(RC29 for US, RC7 is for UK)
3. Turn the device power off.
4. Hold Camera button, and press Power button to entry boot loader mode. You should see a
gray/white screen with instructions to flash your phone with the update on your SD card. If you
don't see that, make sure you followed the instructions properly.
5. As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT
DO ANYTHING TO INTERRUPT THIS PROCESS.
6. After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console
with root permissions. More information regarding that at the bottom of this post. But, to get root access,
do the following:
Instructions:
1. Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy
it to your SD card (see the previous instructions on how to copy from your computer to your
Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it
will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
o mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
o cd sdcard
o flash_image recovery recovery.img
o cat recovery.img > /system/recovery.img
Now you have root!
Click to expand...
Click to collapse
3. Already explained in #1. Again if there is a better, easier guide to follow by all means show me. I am new to this, and from what I've seen if noobs ask "how do I do this" around here, they get flamed for not figuring it out for themselves. Something I'm also sensing from your post.
4. I've gotten past my initial problem. This morning I was shown another DREAIMG.nbh file from another source, and I was able to get it on the phone and get it to boot. I've since gone through the root process (using the guide posted above), but I still can't get it into recovery mode. So that's where I'm now stuck.
5. As opposed to a bunch of steps some retard spewed on a "message board"? All of the guides I've gone through were either on or linked to from this forum or the cyanogenmod forum. Both I assume reputable sources for this type of thing.
Note: I think you need to show me another guide because what you're saying contradicts everything I've seen.
Note2: Don't know. Everything I've seen says I have to go back to 1.4 to be able to root it because the security holes were closed in 1.6.
The phone is again back to the 1.4 image from the nbh file. I've tried to root it and get it to recovery mode without any luck, so I could use some guidance on what to do from here. I'm not really sure what adb logcat is or why I'd want to do it.

TalioGladius said:
1. I installed the nbh file because that's what was in every single set of instructions I've found said to do. Step 1 is to downgrade your phone to RC29 for US phones, and the DREAIMG.nbh file is the way to do that from everywhere that I've seen, mostly here and the cyanogenmod forums. If there is a better guide to follow, please link me.
Click to expand...
Click to collapse
Just because it was written does NOT make it right.
The process of rooting does NOT require an NBH file.
The process of REPAIDING NEVER needs an NBH file.
You should NEVER TOUCH an NBH file. The ONLY thing an NBH file does is it increases the risk that you will brick your phone by a bad flash.
Don't do it!
2. I've already explained this. I followed the following instructions:
Click to expand...
Click to collapse
Reposting that crap doesn't help.
WHAT DID YOU DO? WHERE DID YOU GET TO? WHAT DID YOU SKIP? WHAT BUTTONS DID YOU PRESS?
3. Already explained in #1. Again if there is a better, easier guide to follow by all means show me. I am new to this, and from what I've seen if noobs ask "how do I do this" around here, they get flamed for not figuring it out for themselves. Something I'm also sensing from your post.
Click to expand...
Click to collapse
#1: NEVER do anything without ***UNDERSTANDING THE PROCESS FIRST***. If you don't understand, then how can you possibly adapt to inaccuracies/errors/failures? The answer is that you CAN'T.
4. I've gotten past my initial problem. This morning I was shown another DREAIMG.nbh file from another source, and I was able to get it on the phone and get it to boot. I've since gone through the root process (using the guide posted above), but I still can't get it into recovery mode. So that's where I'm now stuck.
Click to expand...
Click to collapse
Define "can't get it into recovery". WHAT recovery do you have installed? The stock one that came with the NBH? Or some OTHER recovery that you installed? You say that it boots into the OS now? Congratulations. DO NOT INSTALL ANOTHER NBH FILE EVER!
What you need to do is install an engineering SPL, and NOT 1.33.2005! Try 1.33.2003.
You can then flash anything you like using FASTBOOT.
5. As opposed to a bunch of steps some retard spewed on a "message board"? All of the guides I've gone through were either on or linked to from this forum or the cyanogenmod forum. Both I assume reputable sources for this type of thing.
Click to expand...
Click to collapse
A forum filters out the retard posts because 100 different people CALL the retard out! A *BLOG* is TRASH unless you absolutely know that the author REALLY KNOWS what he's doing. And in this case, YOU DON'T.
Note: I think you need to show me another guide because what you're saying contradicts everything I've seen.
Click to expand...
Click to collapse
I don't write guides. I INFORM.
Note2: Don't know. Everything I've seen says I have to go back to 1.4 to be able to root it because the security holes were closed in 1.6.
Click to expand...
Click to collapse
The TELNET-ROOT bug was fixed. That's all!
And FYI: There was never a 1.4. 1.0->1.1->1.5->1.6->2.0->2.0.1->2.1->[future]2.2
The phone is again back to the 1.4 image from the nbh file. I've tried to root it and get it to recovery mode without any luck, so I could use some guidance on what to do from here. I'm not really sure what adb logcat is or why I'd want to do it.
Click to expand...
Click to collapse
Again, what did you do to get there?

I can see that this can quickly escalate into an unnecessary back and forth argument. So to avoid that how about I tell you what I've done and where I'm at currently, and you can inform me on what to do to get to my goal?
From what I've seen I had to essentially do the following things:
1. downgrade to RC29
2. root
3. upgrade radio and SPL
4. Install ROM to get to 2.1
What I've done:
1. Formatted my sdcard to fat32, and put the DREAIMG.nbh file on the root of the sdcard.
2. Shutdown. Start up the phone holding the camera button. Got to the gray screen to update, pressed the power button to update.
3. Update successful. Rebooted by pressing call, menu, and power buttons.
4. Went through the setup wizard to set up the phone with my google account.
5. Installed telnet application from the market.
6. Downloaded recovery.img and spl-signed.zip (Danger SPL) and put them on the root of the sdcard.
7. From home screen, pressed enter twice. Typed telnetd.
8. Opened telnet application. Typed the following commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img/CODE]
9. Shut down phone. Held down the home button while powering phone on in attempt to get to recovery mode.
10. Phone did not go into recovery mode, but went to this image on the screen: (can't post links, so fix the url)
hxxp:// www .modmygphone.com/wiki/images/1/1b/Howtofirm1.png
Currently, the phone is showing the following:
Firmware version 1.0
Baseband version 62.33.20.08H_1.22.12.29
kernel version 2.6.25-01843-gfea26b0 [email protected] #6
Build number kkila-user 1.0 TC4-RC29 115247 ota-rel-keys,release-keys
What exactly do I need to do from here to get a 2.1 rom installed?

TalioGladius said:
I can see that this can quickly escalate into an unnecessary back and forth argument. So to avoid that how about I tell you what I've done and where I'm at currently, and you can inform me on what to do to get to my goal?
From what I've seen I had to essentially do the following things:
1. downgrade to RC29
2. root
3. upgrade radio and SPL
4. Install ROM to get to 2.1
What I've done:
1. Formatted my sdcard to fat32, and put the DREAIMG.nbh file on the root of the sdcard.
2. Shutdown. Start up the phone holding the camera button. Got to the gray screen to update, pressed the power button to update.
3. Update successful. Rebooted by pressing call, menu, and power buttons.
4. Went through the setup wizard to set up the phone with my google account.
5. Installed telnet application from the market.
6. Downloaded recovery.img and spl-signed.zip (Danger SPL) and put them on the root of the sdcard.
7. From home screen, pressed enter twice. Typed telnetd.
8. Opened telnet application. Typed the following commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img/CODE]
9. Shut down phone. Held down the home button while powering phone on in attempt to get to recovery mode.
10. Phone did not go into recovery mode, but went to this image on the screen: (can't post links, so fix the url)
hxxp:// www .modmygphone.com/wiki/images/1/1b/Howtofirm1.png
Currently, the phone is showing the following:
Firmware version 1.0
Baseband version 62.33.20.08H_1.22.12.29
kernel version 2.6.25-01843-gfea26b0 [email protected] #6
Build number kkila-user 1.0 TC4-RC29 115247 ota-rel-keys,release-keys
What exactly do I need to do from here to get a 2.1 rom installed?[/QUOTE]
First you need to be really carefull with the danger spl (make sure you have the right radio installed before installing that spl or bye bye to your phone). You need to install Amon Ra's new recovery. Put 2.1 on sd card. Wipe and flash.
Click to expand...
Click to collapse

supremeteam256 said:
First you need to be really carefull with the danger spl (make sure you have the right radio installed before installing that spl or bye bye to your phone). You need to install Amon Ra's new recovery. Put 2.1 on sd card. Wipe and flash.
Click to expand...
Click to collapse
I got the radio upgraded to 2.22.29.26I.
Turns out I have to hit alt-l to get past the ! screen in recovery mode. So now I should be able to install the danger spl, and then the rom, right?
The one I'm seeing with the guide is Cyanogenmod 4.2.15.1.

TalioGladius said:
I got the radio upgraded to 2.22.29.26I.
Turns out I have to hit alt-l to get past the ! screen in recovery mode. So now I should be able to install the danger spl, and then the rom, right?
The one I'm seeing with the guide is Cyanogenmod 4.2.15.1.
Click to expand...
Click to collapse
To be honest I would flash Amon Ra's new recovery first so you can flash the danger spl and then the rom without a reboot in between. And if you want to install that version of cyanogen you really don't need the danger spl, but if you want to jump up to his 5.0.7 Test5 you'll need to (thats the 2.1 version).

If you want to avoid bricks, you really should NEVER go straight from 0.95.x000 SPL --> 1.33.2005 SPL. The reason for this is that there is no way to make that jump without using recovery, and since those SPLs are so different from each other, it has to use the cache-->update-hboot-->recovery-wipe-cache approach, which is where bricks come from.
If you have a 0.95.x000 SPL and want to go to 1.33.2005, you FIRST go to 1.33.2003 (that's a THREE) using recovery (since 0.95.x000 and 1.33.2003 have equal compatibility) -- this opens up the door for using FASTBOOT to flash your SPL. The move between ANY pair of engineering SPLs using fastboot is guaranteed safe since it can never get stuck in a failed boot-recovery (brick).

Installation Aborted [status 0]

I keep on getting this error when trying to flash a custom ROM into my phone. Is there a way to manually apply the ROM?
I tried booting into recovery then conecting my phone through usb and running the following commands through cmd: "adb push update.zip /sdcard/update.zip". then it tells me if I want to push "update.zipj", but once I press enter it gives me, "error: device not found"
Here's the cmd log:
Code:
C:\Users\Admin>cd\
C:\>cd\android\android-sdk\tools
C:\Android\android-sdk\tools>adb devices
List of devices attached
000000000000 recovery
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zip
protocol failure
C:\Android\android-sdk\tools>
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zipj
error: device not found
C:\Android\android-sdk\tools>
Am I doing the manual flashing corrrectly? I figured manually flashing the ROM would stop the error from coming up. Could someone either show me or point me in the right direction on how to fix this error and/or possibly how to manually flash the ROM in detail. I've already searched and I keep seeing threads with people asking for similar problems but with no real answer.
any help is appreciated.

1. adb push does not flash a ROM - just copies the file to the SD card
2. Looks like you are in recovery and you cannot push a file, unless you mount the SD card in recovery
Not sure what you mean "manually apply the ROM". ROM flash has to be manual, there's nothing automatic about it.
And, if you had really searched... I am sure you would have found atleast 10 references on how to flash a ROM.
Anyways, here's a link that will give you enough information to just about do anything with your CDMA Hero: http://forum.xda-developers.com/showthread.php?t=1063843. BTW, this is a sticky right at the top of where you posted this question...

BOOM. lol. Also the status 0 is an improper mount command, or you have a bad version of busybox. What zip were you trying to flash out if curiosity? And are you rooted, if so how did you do it?

What I meant when I said "manually" I meant to do it through command prompt instead of Rom manager or through recovery. And I was mainly searching for a fix for the status error I was getting. Which there is no info about that in the link you posted, however it does help with flashing my Rom through command prompt. :]
@il duce It's called "nfx speedy kingdom". I've been using the salsa builds in the development section, but I came across this Rom and it says it has everything working including Bluetooth so I wanted to test it out. Ill try using the tutorial on flashing roms without an sdcard and see if it works.

1. By the looks of it, adb is not recognizing your device... so, first and foremost you will have to setup everything properly for adb to connect
2. Even if adb recognizes the device, to the best of my knowledge, you cannot flash anything through adb, you must have confused it with fastboot. And, that too is possible only if you have engineering spl

One of the links from the thread you linked to show how to push the rom to system/data and use cmd to flash it from there, but the rom I'm trying to flash is over 300mb so it doesn't fit :/
I guess I'll try contacting the dev and see if he knows of a solution, might be that the file isn't correctly packed or signed?
edit: flashing using RA recovery it gives me the following:
Code:
E:Missing file:
system/lib/libvoAMRWBDec.so
E:Verification failed
Installation aborted
Does that mean it's the ROM that's corrupted?

Dude wtf... thats an evo rom.

Also, andy is correct 100%. Cease and desist before you bork your phone.

o_o he has it under heroc roms.
http://sprint.hero.ptyork.com/?cat=1
Edit: Sorry everyone for the questions, I just pm'd nfinitefx and he cleared out everything for me.