yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] rayborn:
You can still root as long as you have a sprint hero

http://xdaforums.com/showpost.php?p=4930043&postcount=1

thats what I have done and ive rerooted just have to use the fastboot command to reboot and cant load the custom recovery but eh still works as being rooted
[Hero CDMA Android Development] Visionikz03:
All we really need the official sprint 2.1 update for is to build custom roms off of that will solve all of these "ported" rom issues. I don't plan on utilizing the official sprint rom cuz it's still gonna be loaded with crapware. Not to mention once we have the raw 2.1 rom from sprint i'm pretty sure someone can create a 2.1 ruu just like one was created for 1.56xxxx for those that would like to flash back to stock and then try out the official sprint rom. Of course that is assuming the official 2.1 update contains the same baseband version that is posted in the forum.
[Hero CDMA Android Development] phishstics:
ended up taking the easy way out and exchanging the phone at sprint since i was within the 30 days...no harm no foul...not sure i'll be rooting this one anytime soon though.
[Hero CDMA Android Development] ssblood:
null and void...
[Hero CDMA Android Development] danimal_01:
my question is to the users that have this 110 error. Before you decided to go back to stock did you follow the directions on the exe? When it told you before starting you must do these things? Like did you disable the lockscreen and usb debugging etc? I'm wondering if this might have caused the problem...

~Danny
[Hero CDMA Android Development] wcgbmd:
I bricked my phone, not from this though. It was a 50/50 that I was going to solve anything by this but it worked for me.

Boot up into fast boot mode.

Load up ADB

Enter the command "rm -r /" you may have to mount it first.

Enter the command "rm -r /system" you may have to mount it first.

Enter the command "rm -r /data/dalvik-cache"

Enter the command "rm -r /data/boot-cache"

Don't Reboot, load up the RUU and restore your phone. If you reboot you won't be able to get to fast boot even.
[Hero CDMA Android Development] ssblood:
On the first hero I got the failure to boot and the 110 error I had used fresh's prekitchen to root and failed to flash to recovery image before I restarted the phone. My failure to completely read the instructions before starting caused this problem.

The second hero I manually rooted and installed the Alyicious (spelling) rom and used it for a day or so. I installed Fresh 1.1 next and used it for a few minutes. I then installed the Chocomatic 2.1 rom and was fine. I flashed the 1.6.2 recovery over my 1.5.2 recovery and here is where my problem started. I renamed the nandroid folder with my serial number instead of the contained nandroid backup and had to manually restore a back with nand-restore.sh through adb shell because I had wiped before I restored as usual this was done thru the recovery screen with adb thru computer. When the phone restarted the 1.5.2 recovery screen was displayed. Rut roh. So I again wiped the phone and restored the Chocomatic nandroid backup and the phone restored. I instantly knew I was in trouble when it showed me just the HTC screen because I had bricked one before.

So I boot using fastboot oem boot and decided to screw around figuring it couldn't get no worse. I went thru rerooting the phone again and mounted the system partition per the instructions. I did not realize that the system partition I would be mounting was the actual oem part of the phone and wiped it. Now I have a true brick. If anyone has any ideas I'll be happy to try them while waiting for a new phone and relying on my bb.

Tried the instructions in the above post but is says that /system/bin/sh can not be located.
[Hero CDMA Android Development] fixxxer2008:
i don't get how you guys can brick your phone running the stock RUU? i did it with no issues at all. :confused:
[Hero CDMA Android Development] ssblood:
I have restored many times with the stock RUU too. Sometimes everything just doesn't line up exactly right and boom. Brick. Go figure. I'm starting to wonder if this is a permanent brick thing. I will not be rooting the new phone when I recieve it as the cons extremely outweigh the pros IMHO. Maybe if someone finds a way around this at some point I'd try it again but the way my luck is going I'd find the next way to brick a hero.
[Hero CDMA Android Development] fixxxer2008:
well once 2.1 comes out we don't even know if we will be able to root anymore. ill wait until a dev tests it first. ;)
[Hero CDMA Android Development] crash447:
Hey guys, I have been out of town and unable to respond or try these ideas. Thanks for all of them. I will read through and try them out tonight of tomorrow.
[Hero CDMA Android Development] ssblood:
Yea, I really hope we get the 2.1 update soon. If I can make it look like the Chocomatic 2.1 rom without rooting it I will have no desire to root the phone.
[Hero CDMA Android Development] crash447:
I am having a little trouble with this or just getting access denied like everything else.

1) When you say load up ADB? Do you mean adb shell?

2) When you say you may need to mount it first, what does this mean?

I would appreciate more information on mounting if anyone has it, could this be apprarently why so many other things we have tried came back with access denied?

Thanks again everybody.
[Hero CDMA Android Development] mrinehart93:
I think he means "adb shell", and then mount the filesystem.
[Hero CDMA Android Development] crash447:
How do you mount the filesystem, I may have tried, but I want to see if I am doing it correct?
[Hero CDMA Android Development] danimal_01:
okay this is a long shot but since you guys are able to get into the phone os navigate to Settings > Security > Firmware Download > Auto Download then in that same menu you will see factory reset. Try selecting that option and see what happens?

~Danny
[Hero CDMA Android Development] crash447:
Danny,

Man thanks for all your help. I really appreciate that. I already tried that one. Just had to fastboot oem boot when I turned it back on.
[Hero CDMA Android Development] jmxp69:
adb remount

That normally remounts the filesystem read/write.

adb shell

# mount

should show you all of the mountpoints. Look for (rw).

J
[Hero CDMA Android Development] jmxp69:
I'm trying to follow what's going on, but I'm not sure I understand exactly where you are with this crash.

You can root the phone right?

If the phone is rooted, can you use adb to install an RA recovery image?
[Hero CDMA Android Development] jmxp69:
I don't think that's it. I've RUU'd with RA's recovery image no problem.

I'd like to know if they have a recovery image on there at all..?
[Hero CDMA Android Development] crash447:
When I do adb remount it says access denied.

When I do ...

adb shell

# mount

it does not show anything.
[Hero CDMA Android Development] crash447:
I have tried so many things it is hard to remember everything, but yes I have tried and I think I have gotten access denied. One problem too is most instructions show muching RA recovery on the sdcard and booting into recovery which I cannot do. Can you or someone post specific adb instructions to go straight from the pc to the hero without sdcard since I can't boot to recovery?
[Hero CDMA Android Development] jmxp69:
1) Phone has to be rooted

2) Boot up

3) Place this in your android tools folder

4) Drop to your command line, go to your sdk tools folder and enter the following:

adb remount

adb push recovery-RA-heroc-v1.6.2.img /system/app/recovery-RA-heroc-v1.6.2.img

adb shell

cd /system/app

flash_image recovery recovery-RA-heroc-v1.6.2.img

reboot recovery

You mentioned in your pm to do this w/o the card which is why I'm telling you to push the RA img to /system/app.

Let me know what happens.
[Hero CDMA Android Development] jmxp69:
Is the phone rooted??
[Hero CDMA Android Development] jmxp69:
Looks like you dropped offline.

If adb remount doesn't work:

Type:

adb shell

You should see the # for a prompt. If you don't, you're not root, and we have to fix that first. If you do, keep reading.

Type:

#/system/bin/mount
...
/dev/block/mtdblock3 /system yaffs2 [b]ro[/b] 0 0
...

That "ro" means /system is mounted read only. You can't write the recovery image to that partition if it's read only, so we have to make it read write.

Type:

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

You will not see any output from this command.

Type:

# /system/bin/mount
...
/dev/block/mtdblock3 /system yaffs2 [COLOR="Red"][B]rw[/B][/COLOR] 0 0
...

Now /system should be remounted as read write. If you can get this far, we should be able to get the recovery image on the phone.

Type:

# exit

You'll be back at your PC's command line now.

Type:

adb push recovery-RA-heroc-v1.6.2.img /system/app/recovery-RA-heroc-v1.6.2.img
adb shell

Now you're back on the phone.

Type:

#cd /system/app
#flash_image recovery recovery-RA-heroc-v1.6.2.img
#reboot recovery

Let me know...
[Hero CDMA Android Development] crash447:
I keep getting permission denied...this is where I keep getting confused.

$ su

su

# adb remount

adb remount

adb: not found

# remount

remount

remount: not found

# #/system/bin/mount

#/system/bin/mount

# /dev/block/mtdblock3 /system yaffs2 ro 0 0

/dev/block/mtdblock3 /system yaffs2 ro 0 0

/dev/block/mtdblock3: permission denied

# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

# # /system/bin/mount

# /system/bin/mount

# /dev/block/mtdblock3 /system yaffs2 rw 0 0

/dev/block/mtdblock3 /system yaffs2 rw 0 0

/dev/block/mtdblock3: permission denied
[Hero CDMA Android Development] jmxp69:
Ok, the key thing is you have system mounted RW. That's important. If you haven't already:

# exit

Then, from your pc command line:

adb push recovery-RA-heroc-v1.6.2.img /system/app/recovery-RA-heroc-v1.6.2.img

adb shell

Now you're back on the phone.

#cd /system/app

#flash_image recovery recovery-RA-heroc-v1.6.2.img

#reboot recovery
[Hero CDMA Android Development] jmxp69:
BTW: An important thing to understand about your previous post.

A prompt on the phone of "#" means you are root. You cannot execute these commands without root access.

A prompt on the phone of "$" means you ARE NOT root. You figured out to enter "su" to switch to root which is good. So when you look at commands to type on the phone that start with "#" that means you MUST BE (or are already) root before executing them.

J
[Hero CDMA Android Development] jmxp69:
Also, another thing I noticed:

You don't run adb commands from inside the phone. ADB is an executable that resides on your PC or Mac. If you want to get this right, you have to follow instructions carefully. Here are a few examples of what I'm talking about:

You issued this one from inside the phone. adb doesn't work from inside the phone, it only works from your computer's command line.

# adb remount

adb remount

adb: not found

I never said to run remount, only adb remount from your pc command line.

# remount

remount

remount: not found

You'll save yourself a lot of aggrevation by understanding where certain commands are. adb is a pc issued command that tells the phone to do something.

J
[Hero CDMA Android Development] crash447:
More permission denied or not found...

C:\AndroidSDK\tools>adb push recovery-RA-heroc-v1.6.2.img /system/app/recovery-R

A-heroc-v1.6.2.img

failed to copy 'recovery-RA-heroc-v1.6.2.img' to '/system/app/recovery-RA-heroc-

v1.6.2.img': Permission denied

C:\AndroidSDK\tools>

C:\AndroidSDK\tools>adb push recovery-RA-heroc-v1.6.2.img /system/app/recovery-R

A-heroc-v1.6.2.img

failed to copy 'recovery-RA-heroc-v1.6.2.img' to '/system/app/recovery-RA-heroc-

v1.6.2.img': Permission denied

C:\AndroidSDK\tools>adb shell

$ su

su

# cd/system/app

cd/system/app

cd/system/app: not found

#
[Hero CDMA Android Development] jmxp69:
Ok:

from your pc command line:

adb shell

su

cd /system

ls -l

paste output here.

Also, you downloaded the RA image and put it in the same folder as adb.exe right (are you on a pc or mac?)
[Hero CDMA Android Development] jmxp69:
The problem with this is you didn't enter a space after cd

It's:

cd <space> /system/app
[Hero CDMA Android Development] crash447:
Yes I put it in the adb folder. Also I know we are not that far yet, but when you say on the phone I am assuming this is in Terminal? Do you have a terminal app you recommend. Here is the paste.

drwxr-xr-x root root 2009-11-09 03:27 usr

drwxr-xr-x root root 2009-11-09 03:27 customize

-rw-rw-rw- root root 0 2010-03-14 19:30 recovery.img

drwxr-xr-x root root 2009-11-09 03:27 lib

drwxr-xr-x root root 2009-11-09 03:30 app

drwxr-xr-x root shell 2009-11-09 03:27 bin

drwxr-xr-x root root 2009-11-09 03:27 fonts

-rw-r--r-- root root 1970 2009-11-09 03:27 build.prop

drwxr-xr-x root root 2009-11-09 03:27 media

drwxr-xr-x root root 2009-11-09 03:27 etc

drw-rw-rw- root root 2010-03-15 00:08 lost+found

drwxr-xr-x root root 2009-11-09 03:30 framework
[Hero CDMA Android Development] jmxp69:
No, adb shell puts you on the phone in a "terminal" You don't need anything else. Just adb.exe and the phone.

That's odd. A 0 byte recovery image. And it's not in the right place...

Also odd. You have rw for the app directory. You should be able to push the file.

From adb shell:

# cd /

# ls -l

paste output.
[Hero CDMA Android Development] crash447:
ls -l

drwxrwxrwt root root 2010-03-15 00:12 sqlite_stmt_journals

drwxrwx--- system cache 2010-03-14 19:11 cache

drwxrwxrwx system system 1969-12-31 18:00 sdcard

lrwxrwxrwx root root 2010-03-15 00:08 etc -> /system/etc

drwxr-xr-x root root 2009-11-09 03:27 system

drwxr-xr-x root root 1969-12-31 18:00 sys

drwxr-x--- root root 1969-12-31 18:00 sbin

dr-xr-xr-x root root 1969-12-31 18:00 proc

-rw-r--r-- root root 11336 1969-12-31 18:00 logo.rle

-rwxr-x--- root root 10296 1969-12-31 18:00 init.rc

-rwxr-x--- root root 2965 1969-12-31 18:00 init.heroc.rc

-rwxr-x--- root root 1677 1969-12-31 18:00 init.goldfish.rc

-rwxr-x--- root root 106804 1969-12-31 18:00 init

-rw-r--r-- root root 118 1969-12-31 18:00 default.prop

drwxrwx--x system system 2009-11-09 03:08 data

drwx------ root root 1969-12-31 18:00 root

drwxr-xr-x root root 2010-03-15 00:08 dev
[Hero CDMA Android Development] jmxp69:
Ok, you have the right permissions to write data to /system/app, so I'm not sure why it's not letting you.

Let's take a different direction with this. Do you have an SDCard?

Can you take the SDCard out of the phone, put it in your computer and copy the RA Recovery image from the computer to the SDCard?

After you do that, put the SDCard back in the phone and reboot.

Try this for rebooting:

adb reboot

We have to get access to the recovery image from within the phone. If adb push isn't letting it happen, let's try the sdcard.
[Hero CDMA Android Development] crash447:
Well I have an sdcard. The only way I have to put anything on it is with the phone connected by usb. I am out of town and don't have a card reader with me.

Also I have done adb reboot many times and it just takes me to a blank black screen or if the usb is plugged in it takes me to the HTC screen where I can do fastboot commands.
[Hero CDMA Android Development] jmxp69:
Ok, then mount the card and do it that way. That's fine too. Just unmount it after you copy the image to it.
[Hero CDMA Android Development] crash447:
When I did adb reboot, it said "closed".
[Hero CDMA Android Development] jmxp69:
Ok. Get the phone back up, mount the sdcard, copy the image to it, unmount the sdcard and let me know when you've done that.
[Hero CDMA Android Development] crash447:
It is copied.
[Hero CDMA Android Development] jmxp69:
Ok:

Make sure you unmount it from the phone (from the notification tray)

Then:

adb shell

su

ls -l /sdcard

paste output.
[Hero CDMA Android Development] crash447:
drwxrwxrwx system system 2009-05-17 18:25 MSMETADATA

drwxrwxrwx system system 2010-03-13 22:42 DCIM

drwxrwxrwx system system 2009-05-17 18:30 WMDRM

drwxrwxrwx system system 1999-12-31 23:00 LOST.DIR

-rwxrwxrwx system system 1232 2009-01-31 13:33 EncFiltLog.menc

drwxrwxrwx system system 2010-03-07 14:19 data

drwxrwxrwx system system 2010-03-14 19:20 albumthumbs

drwxrwxrwx system system 2010-03-13 14:25 download

drwxrwxrwx system system 2010-03-11 23:19 newsrob

drwxrwxrwx system system 2010-03-05 16:58 Android

drwxrwxrwx system system 2010-03-05 16:59 svox

-rwxrwxrwx system system 3809280 2010-03-15 00:49 recovery-RA-heroc-v1.6.2.

img

drwxrwxrwx system system 2010-02-15 11:34 appmanager

drwxrwxrwx system system 2010-02-18 04:08 ime

drwxrwxrwx system system 2010-02-22 15:20 amazonmp3

drwxrwxrwx system system 2010-03-14 20:52 hoccer

drwxrwxrwx system system 2010-03-08 10:31 albumart

drwxrwxrwx system system 2010-02-20 13:29 maps

drwxrwxrwx system system 2010-02-21 21:30 aStopwatch

drwxrwxrwx system system 2008-06-07 16:08 Videos

drwxrwxrwx system system 2008-12-17 07:54 Music

drwxrwxrwx system system 2010-02-14 23:26 Games

drwxrwxrwx system system 2010-02-26 23:08 rosie_scroll

drwxrwxrwx system system 2010-03-09 03:34 nandroid
[Hero CDMA Android Development] jmxp69:
Ok:

adb shell

su

# flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
[Hero CDMA Android Development] crash447:
# flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.im

flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
[Hero CDMA Android Development] jmxp69:
Cross fingers:

# reboot recovery
[Hero CDMA Android Development] crash447:
It did reboot, but it just stayed at the htc screen. I can image if I unplug the usb I will get the same error screen and then would have to plug in usb and type "fastboot oem boot" to get it to boot.
[Hero CDMA Android Development] jmxp69:
Nope, I was looking for the recovery image to load up...<sigh>

The only other thing I can think to do is to flash a new boot image for you. I haven't done this before, so I don't know what'll happen.

I have a boot.img from DCv1.0 if you want to try it.
[Hero CDMA Android Development] crash447:
Sure, I also have boot.img's from nandroid backups.
[Hero CDMA Android Development] jmxp69:
Download this: http://66.197.42.222/boot.img You might need to right click and "save as" to save it on your pc.

Copy it to your SDCard the same way we did the recovery image.

Let me know when you've unmounted the card.
[Hero CDMA Android Development] crash447:
It is there.
[Hero CDMA Android Development] jmxp69:
After you get that boot.img on your sdcard (do an ls -l /sdcard and make sure it's there-it should be ~ 2.5MB in size)

adb shell

su

#flash_image boot /sdcard/boot.img
[Hero CDMA Android Development] crash447:
It is flashed.
[Hero CDMA Android Development] jmxp69:
# reboot recovery
[Hero CDMA Android Development] jmxp69:
This time when it's rebooting if it doesn't load the recovery rom:

adb shell

(keep doing this until the phone lets you on)

# logcat

copy and paste output.
[Hero CDMA Android Development] crash447:
Nope, man I completely understand if you can't do anymore. Sorry for your trouble.
[Hero CDMA Android Development] jmxp69:
Let's see the output from logcat
[Hero CDMA Android Development] crash447:
???? logcat???
[Hero CDMA Android Development] jmxp69:
adb shell

su

# logcat

paste output.

It will be easier to read if you use (code)(/code) tags but replace the ()'s with []'s.

It looks like this:

my output
[Hero CDMA Android Development] crash447:
OK, weird stuff.

1) That is a lot of info that is still pulling up and I don't know what "tags" are.

2) I had # without su that time.

3) My touchscreen does not seem to be responding.
[Hero CDMA Android Development] jmxp69:
If there are any devs watching this:

Why wouldn't a working boot.img and recovery.img solve this?
[Hero CDMA Android Development] jmxp69:
When you post a reply, if you use [ code ] (without the spaces) and [ / code ] (again, without the spaces) and you paste your output between the first and second [ code ] tags, the display on the forum us a fixed width font making it easier to read.
[Hero CDMA Android Development] jmxp69:
BTW: Here's a link explaining boot.img and recovery.img on Android.
[Hero CDMA Android Development] crash447:
Thanks, just pm'd you.
[Hero CDMA Android Development] jmxp69:
What happens if you power the phone off, press and hold the Home Button, and power the phone back on? Keep pressing the home button for a minute or so.
[Hero CDMA Android Development] jmxp69:
If the touchscreen hasn't returned, go back to one of your backup boot images. Same procedure, just copy it to your SDCard.

adb shell

# flash_image boot /sdcard/whatever.img

I'd like to see that logcat when you get a chance.

G'night.
[Hero CDMA Android Development] crash447:
Nothing, my touchscreen is also completely unresponsive.
[Hero CDMA Android Development] jmxp69:
You'll probably have to go back to one of your boot images. See above.
[Hero CDMA Android Development] GrandMstrBud:
I've been watching this thread and my phone is the same way. I think it's going back to the sprint store today.
[Hero CDMA Android Development] crash447:
Does your phone have the new radio?
[Hero CDMA Android Development] jmxp69:
crash:

Can you download one of the new roms like DCv1, name it update.zip and see if fastboot update applies it?

J
[Hero CDMA Android Development] crash447:
I can't remember for sure if I posted the results, back when I was trying that, but basically everytime I tried to flash anything other than the RUU with fastboot. Meaning ROMs, Radio, Boot, Recovery, etc. it would give me the 12 signature verification error.
[Hero CDMA Android Development] jmxp69:
Let me take a step back here...I've been reading about fastboot and trying to find out what's up with the verification error.

In the meanwhile, it appears fastboot boot whatever.img is not supposed to write anything to the phone, just boot from the image on your pc.

You have the RA Recovery image in your tools folder. Try this:

Boot into fastboot, select fastboot mode (home key??)

From your tools folder: fastboot boot recovery-RA-heroc-v1.6.2.img
[Hero CDMA Android Development] jmxp69:
Ok, it looks like fastboot will try to validate the signature. I think you're going to need the stock recovery image and perhaps the stock boot image. Have you tracked those down? Might be in the 1.56 RUU. I'll look.
[Hero CDMA Android Development] jmxp69:
Ok, I got the stock boot.img and recovery.img from the 1.56 RUU.

http://66.197.42.222/boot.img

http://66.197.42.222/recovery.img

What ROM are you running?
[Hero CDMA Android Development] ssblood:
OK. I managed to corrupt the /system folder when i booted using 'fastboot oem boot' by mounting it rw as I had said in one of my earlier posts. I wiped the /system partition you get when you load boot using the fastboot oem. I think the recovery partition you would be flashing is the back oem version that we are booting into. It's like a second phone system when you boot this way. There is no adb access without booting this way so I'm thinking it is a total brick. I also think this is why we keep getting access denied. It's trying to overwrite the 'fastboot oem' side and not the actual phone flash you would normally use. Two seperate systems? This is why you can write the recovery image normally but you can not write it when doing 'fastboot oem boot'... This is all in my opinion but it does make sense. Maybe a dev with really intimate knowledge of the phone can shine more light on this.
[Hero CDMA Android Development] crash447:
OK guys,

I finally broke down and took mine back today. I am sleep deprived from the past week of working on this thing and my wife politely asked if I would consider just taking it back. I also live an hour away from a sprint service center or best buy and I was near them today. Thanks again to everyone who has helped me and while I do not have much knowledge in ways to fix this I will try and still help with any of my failed attempts at fixing it.
[Hero CDMA Android Development] jmxp69:
Crash: Glad you got fixed even if it wasn't from our efforts. I sure wish I could have your old phone. With root access, there has to be a fix.

Anyway, glad you have your phone back.

J