CDMA Hero rooted

702DROID

Well-known member
Nov 7, 2009
196
8
0
Visit site
EXCELLENT.

For apps2sd I really recommend installing Mocado's 1.1 ROM. Some folks say apps2sd from the market worked, here it just ate sd cards like they were candy.

Have you installed mocados rom or partioned your sd card for apps2sd yet?
Be happy to help you with this last bit, just need to know where you are in the process so far.

If you are going to use mocado for apps2sd:
Reboot back into recovery
Preform a nandroid backup
Reboot phone
Plug in to pc and back up entire sd card again. It's gonna get wiped.
leave phone plugged in, reboot into recovery.
run the format sd card with fat32+swap+ext script from the recovery image.
When it's done, enable mass storage mode in recovery image and copy everything back to your sd card.
In the root folder of your sd card, copy the mocado 1.1 rom.
On phone, in recovery mode select to Apply SD card:choose zip
select the mocado 1.1 rom

When it's all done reboot. You will have to go to the market app and uninstall/reinstall each app one at a time to fix the links, as they are now on the sd card.

If at any time you get errors, you can boot into recovery and select to restore from your nandroid backup to get where you were.

had to change sd cards and then everything worked while i was trying to flash and do the backup

gone through all that already when i uninstalled my apps i had 798mb free on my sd card and 117 mb on he phone but when i reinstalled the apps my cd memory is still at 798 and my insternal storage went to 113mb im not sure if its on the sd card or not all my apps seam to be working after the uninstall and reinstall idk
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
If you went through it all you're probably set. The internal storage number you see is a bad symlink from old data. Ignore it, unless you wanna got through adb and change it. I'm sure that in due time a rom will be built that fixes it. For now, I suggest you ignore.

Open your term on the phone and run the command top. You'll see a number, followed by a used number. Thats your memory. First number is free, second is used.

Tell us what you see
 

702DROID

Well-known member
Nov 7, 2009
196
8
0
Visit site
If you went through it all you're probably set. The internal storage number you see is a bad symlink from old data. Ignore it, unless you wanna got through adb and change it. I'm sure that in due time a rom will be built that fixes it. For now, I suggest you ignore.

Open your term on the phone and run the command top. You'll see a number, followed by a used number. Thats your memory. First number is free, second is used.

Tell us what you see

says mem 19445k used 2740k free 0k shrd 36k buff 24576k cached
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
NVM. Looks like the top command won't show what we need on the phone...just checked myself :)

I'm headed to a meeting. I'll look into it and figure an easy way to check and post me findings later this afternoon. In the meantime, enjoy your root and your tether. Break out that DS or iTouch :)
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
says mem 19445k used 2740k free 0k shrd 36k buff 24576k cached

Dos prompt in ADK/tools dir:

adb shell
su
cd /system/sd/app
ls -a

if the list is blank, try

cd /system/app
ls -a


If you see the list in /system/sd/app everything is gold. If you see it in /system/app you have the smae issue as many many others. There is either a symlink bug, or or bug in the apps2sd script while running on the hero. Let it be for now, a couple of very smart devs are wokring on the issues and will post a fix for everyone.

Wifi tether (as you know) will still work just fine, as will apps from the market that need root. Apps2sd is hit or miss, and not worth destroying a bunch of sd cards to troubleshoot.
 

702DROID

Well-known member
Nov 7, 2009
196
8
0
Visit site
Dos prompt in ADK/tools dir:

adb shell
su
cd /system/sd/app
ls -a

if the list is blank, try

cd /system/app
ls -a


If you see the list in /system/sd/app everything is gold. If you see it in /system/app you have the smae issue as many many others. There is either a symlink bug, or or bug in the apps2sd script while running on the hero. Let it be for now, a couple of very smart devs are wokring on the issues and will post a fix for everyone.

Wifi tether (as you know) will still work just fine, as will apps from the market that need root. Apps2sd is hit or miss, and not worth destroying a bunch of sd cards to troubleshoot.

THANK YOU i got the list on system/sd/app one more question im using the stock memory card now(2gb) im planing on getting me a bigger sd card in the next week or two any special steps i need to do to swap cards out
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
Scratch that (leaving for my own notes though...pardon the double posts)
Open the term on your phone, and enter:
su
cd /data/app
pwd


If the response is:
/system/sd/app

you're good to go.

The whole things looks like it's just a link issue. The pwd command means present working directory. The /data/app directory is just a list of links to /system/sd/app to trick the OS into thinking the apps are where they should be. The OS is updating the internal storage display in settings with info it THINKS is on the sd card.


To really prove it, pull the sd card and try to run an app.....be warned, this will freeze you up solid, and may not be good for the sd card!
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
THANK YOU i got the list on system/sd/app one more question im using the stock memory card now(2gb) im planing on getting me a bigger sd card in the next week or two any special steps i need to do to swap cards out

Great. Ignore my other post..you are good to go.

When you get the new card:
1. back up existing sd card
2. Swap cards, boot to recovery
3. Run the fat32+swap+ext2 script again
4. Copy your backup from the old sd card onto the new.
5. Reinstall your apps again

One more thing - Don't spend alot of money on expensive high capacity or class 5/6 sd cards. Running ext2 and swap partitions on them shortens their life by about half. I use Sandisk 4 gigs that cost 8 dollars each lol.
 
Last edited:

702DROID

Well-known member
Nov 7, 2009
196
8
0
Visit site
Great. Ignore my other post..you are good to go.

When you get the new card:
1. back up existing sd card
2. Swap cards, boot to recovery
3. Run the fat32+swap+ext2 script again
4. Copy your backup from the old sd card onto the new.
5. Reinstall your apps again

One more thing - Don't spend alot of money on expensive high capacity or class 5/6 sd cards. Running ext2 and swap partitions on them shortens their life by about half. I use Sandisk 4 gigs that cost 8 dollars each lol.

thanks again
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
So were you able to root your Eris following these steps?
Thanks.

Just a side note - The Cell South Hero and Eris have had the null_pointer dereference bug fixed in their kernel. This method will NOT work with either.

What this means -
Newer Sprint Heros may not be able to be root with this exploit.
Htc has found and fixed the bug, so 2.0 is going to be a tough nut to crack.
Htc HAS built a MR/Patch of some sort, and Sprint has yet to release it.

WHAT ARE YOU WAITING FOR SPRINT? TOMORROW IS THE MAGIC 30 DAYS FOR MOST HERO OWNERS.

I encourage everyone to return their Hero tomorrow. State it's buggy and known fixes were not handed out. Sprint needs to realize they aren't really qualified to run QC on code released from HTC for an Android device, and trust their manufacturer.
 

702DROID

Well-known member
Nov 7, 2009
196
8
0
Visit site
You got it bro. I'm glad it all finally got sorted for ya. Damn bad SD card really did a number on you ;)

it didnt even fry that card i can still use it i just put a 700mb .avi movie on it and transfered it from my desktop to my laptop and and im watching it on my lcd right now
 

nfaust01

New member
Nov 12, 2009
2
0
0
Visit site
Cellular south work around?

Well upon trying to root my CS hero multiple times i decided to read on and found the method at the beginning will not work. So my question is, will there be a method that will work or am i out of luck. I am just trying to enable tethering on the hero.
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
Hopefully when Htc releases 2.0 for the device(s) the CS and Sprint versions will be the same, and whatever method is found will work for both.

In the meantime, the only thing you can do is watch the kernel bugtrack and when/if another su exploit comes along it can be tried. As soon as someone finds a way to exploit the kernel and flash an RA, the rest is a piece of cake.
 
Nov 12, 2009
6
0
0
Visit site
First I'd like to say thanks to gbhil. Dude, you have done a great job explaining about the CDMA Hero. Your tips are great and I really appreciate how you follow up on this thread in such depth!

I just got a CDMA Hero from Spr1nt and am very pleased with it. There are obviously a few shortcomings that I'd like to fix as with most Hero owners but overall it's a great smartphone.

I've got a few questions I'd like to ask you before I join the darkside and start doing things like rooting and installing a new ROM. I'll try to start with the broader questions and narrow it down to the more specific. Again, I very much appreciate any questions you can help me with:

1. I'm trying to define the term "ROM". In conventional terms this means Read Only Memory and I'm familiar with this. But when people talk about installing a new "ROM" on their device are they speaking of just installing a modified version of the Android linux kernel and OS? Is there any actual flashing done in this procedure?

2. If one was interested in installing a new "ROM" on their phone, how can I backup my factory one? I understand that if I root my phone and install my own "ROM" that I'm voiding the warranty. So my concern is, will I be able to restore everything back to factory and make it impossible to decipher if my device has been tampered with?

3. The main reasons I am interested in tampering with my phone are because it is a) sluggish and b) full of apps from Sprint that run which I don't want...things like the NFL and NASCAR apps. Which "ROM" would you recommend installing should I want to improve the performance of my phone and get rid of unnecessary apps?

4. Being familiar with Linux, I know that any tools which allow the OS to run in "root" mode are dangerous. Mainly for the security holes they create. Is it really worth this compromise to speed up the phone and customize it? Once rooted, can I install a new "ROM" then unroot the device so it is again secure with the features I want? For that matter, once you root your device for any reason, is there a guide to unrooting the phone again? My impression of the term rooting means changing the system partition from being mounted as a read only mount to a read-write mount. Is that semi-accurate?

5. I understand that many people want to store their apps on the external sd card, mainly because they are natively stored in internal memory which will inevitably run out of space over time. I'm not sure but I remember reading something about creating ext3 partitions on the sd to accomplish this and that shortens their life etc... Why would the sd have to have the ext3 partition to store apps. Does this kernel not understand how to mount a fat32 file system?

6. I have read about dangers in possibly bricking your phone through some of the procedures mentioned above. Is that truly possible if you have a backup of your original OS somewhere? The only way I can imagine completely bricking your phone is if some flashing is going on and you are unable to flash the original image back to the phone. Can you tell me how dangerous this stuff really is?

7. Last question. If I root my phone and maybe install a new "ROM", what to do when Sprint eventually releases Andriod 2.0 for this phone? Would I have to restore to my original image, download the update then reroot the device (if possible after the update)? Or am I stuck with what I've got (I can't imagine this but I have to ask).

Again, thanks! I look forward to reading your response!
 

Jerry Hildenbrand

Space Cowboy
Staff member
Oct 11, 2009
5,567
2,792
113
Visit site
I'll break this into bits for an easier read. I;m sure you're going to like the Hero. The hardware may not be the latest, but it's more than sufficient to drive the phone.

1. I'm trying to define the term "ROM". In conventional terms this means Read Only Memory and I'm familiar with this. But when people talk about installing a new "ROM" on their device are they speaking of just installing a modified version of the Android linux kernel and OS? Is there any actual flashing done in this procedure?

You're on the right track. Think of it as flashing the bios on a motherboard. That's the whole purpose of getting root. You need to flash the ROM of the phone so that it will look for an update in a different location. You point that direction to the sd card on the phone. From there you can load anything that you tell the phone is an update. Only root can send the command to do this, so exploits are looked at in the kernel that's running.

They call them ROMs because they are in the read only memory in the phone.

2. If one was interested in installing a new "ROM" on their phone, how can I backup my factory one? I understand that if I root my phone and install my own "ROM" that I'm voiding the warranty. So my concern is, will I be able to restore everything back to factory and make it impossible to decipher if my device has been tampered with?

Yes. The factory software has been recovered and is archived in quite a few places online. Im sure xda has it hosted. You also have the option to do your own backup as well.

3. The main reasons I am interested in tampering with my phone are because it is a) sluggish and b) full of apps from Sprint that run which I don't want...things like the NFL and NASCAR apps. Which "ROM" would you recommend installing should I want to improve the performance of my phone and get rid of unnecessary apps?

If that's all you need to do, you can do it without changing the whole rom. Since you're root you can swap bits and pieces of the code as well as have access to the file system. Write access :) A rom is basically a rewrite of the os. So much has been done and combined that it's easier to use a rom update. Root has RW on the file memory, but they're called roms anyway. Go figure, it's the interweb. For myself, for now at least I'm running macados rom as it's the only one out, and it does have some great features. I've done a few other tweaks on top of it, like removing some sprintware and fixing a few os bugs (tcp timestamp error and the renaming as package name bug). I like "new" and will probably end up trying a bit of everything, as a full backup and restore utility is built into the recovery image I flashed.

4. Being familiar with Linux, I know that any tools which allow the OS to run in "root" mode are dangerous. Mainly for the security holes they create. Is it really worth this compromise to speed up the phone and customize it? Once rooted, can I install a new "ROM" then unroot the device so it is again secure with the features I want? For that matter, once you root your device for any reason, is there a guide to unrooting the phone again? My impression of the term rooting means changing the system partition from being mounted as a read only mount to a read-write mount. Is that semi-accurate?

I'll be honest instead of tactful on the first question :p You're root. You have to know what you're running, if you can't trust your judgment you shouldn't do it. there, thats done lol.

You can unroot the device, but then how are you ever going to revert? Yep. You would have to singly hunt down an exploit in what you are running to change it back. Don't do that. Just use common sense and don't run random code. You'll be fine.

5. I understand that many people want to store their apps on the external sd card, mainly because they are natively stored in internal memory which will inevitably run out of space over time. I'm not sure but I remember reading something about creating ext3 partitions on the sd to accomplish this and that shortens their life etc... Why would the sd have to have the ext3 partition to store apps. Does this kernel not understand how to mount a fat32 file system?

The kernel can mount fat32, fat16, ext2/3/4 and swap. A script to mount an sd card with 0 as ext2/3 500mb, 1 as fat32 xxxmb, and swap at 32mb is built into a custom recovery image you can copy to the phone. It's a mini bootloader that does other handy things as well. I do recommend you do this, entering text in the terminal gets old quickly with no real formatting. And yes, I recommend you use ext2 as ext3 eats up sd cards about twice as fast. it's the journalizing. Swap does as well. The image only mounts a swap, you have to tell the kernel to use it.

6. I have read about dangers in possibly bricking your phone through some of the procedures mentioned above. Is that truly possible if you have a backup of your original OS somewhere? The only way I can imagine completely bricking your phone is if some flashing is going on and you are unable to flash the original image back to the phone. Can you tell me how dangerous this stuff really is?

It can happen. I've noticed that mostly happens to people who knew damn well it might happen, but had to know anyway...or people who couldn't/didn't follow direction very well and had no idea wtf they are doing. Just by the questions you're asking I think you would do just fine, as you're not seeming like either of those lol.


7. Last question. If I root my phone and maybe install a new "ROM", what to do when Sprint eventually releases Andriod 2.0 for this phone? Would I have to restore to my original image, download the update then reroot the device (if possible after the update)? Or am I stuck with what I've got (I can't imagine this but I have to ask).

Again, thanks! I look forward to reading your response!

You're stuck with what you have until it's determined that the exploit to root still exists (which isn't very likely...nobody hides that sort of thing) or someone figures how to crack the new kernel. Unless you flash a custom recovery image, you can't go back. You can count on lots 'o folks looking, buts that's it.

thanks for asking. This is stuff we all need to keep in mind.
 

Noj

Well-known member
Nov 12, 2009
81
7
0
Visit site
First of all, many many thanks gbhil!!
Your walkthroughs are excellent!

Question :
I want to replace my bootscreen files, but the folder and files are read only.
I am rooted and have verified it via Terminal, but how can I go about replacing the files?

Path to bootscreen files: data\system\media\bootscreen

I already have a new .gif ready to swap and test.
Any help is much appreciated!!