Database Users

Guide to root Rogers G1's

***********Don't follow this method**************
THIS is what you want to do. This thread is an older method.
Do this at your own risk!!!....I'm by no means an expert on this. In fact it's the first time I have done this. There are probably tons of guide to doing this on the T-Mobile version but I made this to help people with the Canadian Rogers G1. So it only applies to that specific phone. This is also expecting you be using Windows (I use XP but Vista will work but I don't know where the command prompt is found....google it if it isn't in the usual spot). Also the commands would be the same using a Mac but yet again I don't know what or where the equivalent of windows command prompt would be found on a Mac.
First off you need the Android SDK which you can get from here (http://developer.android.com/sdk/1.5_r2/index.html).
Unzip the folder inside the .zip file to C:\Android so the final resulting file structure will look like C:\Android\android-sdk-windows-1.5_r2\
Now do the steps 2 and 3 found here http://developer.android.com/guide/developing/device.html
I have cut and pasted these steps here but if you are using a mac you may need to refer to the link. Actually refer to it anyways in case I missed something.
**************** Steps 2 and 3 *********************​
Turn on "USB Debugging" on your device.
On the device, go to the home screen, press MENU, select Applications > Development, then enable USB debugging.
Setup your system to detect your device.
If you're developing on 32-bit Windows, you need to install the 32-bit USB driver for adb. The USB driver is included in the SDK package. To install it, follow these steps:
1.Connect your Android device via USB. When the Found New Hardware Wizard appears, you'll be asked if you'd like Windows Update to search for software. Select No, not this time and click Next.
2.Select Install from a list or specified location and click Next.
3.Select Search for the best driver in these locations. Browse to the usb_driver/x86 in the SDK package (<sdk>\usb_driver\x86).
4.Click Finish. The system should install the driver files as necessary. Your machine may require a reboot.
********************************************​
Plug your USB cord into your phone and plug the USB cord into your computer.
Open a command prompt in windows by going to Start/Run and then type cmd. You should a dos like window open up. Now navigate to the directory C:\Android\android-sdk-windows-1.5_r2\tools
Type “adb devices” to confirm USB Debugging is turned on
Keep the command prompt open for later use
Get fastboot from here (http://www.htc.com/www/support/android/adp.html) and put it in the tools section of the SDK
Get these files http://drop.io/ii4t2ax and put them in the tools section of the SDK. Mount your sd card so you can copy update.zip to the root of your sd card.
Turn off your phone and then press the camera button and the power on button so it loads up to fastboot mode (or whatever it is called..lol). Once it gets to the screen with 3 androids on skateboards on the bottom you should press the “call” button to the farthest left. It should go to another screen that says “FASTBOOT USB”. If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
Now in the command prompt you need to type “fastboot boot recovery.img” don't touch your phone tile it gets to a new choice of menus in recovery mode. Once it gets there you should make a nandroid backup. I really urge you to make the backup. Make sure there is space left on your SD card.
So follow the menus and press the button combination to make the back up and once that is done press the other button combination to apply the update.zip file....Do not touch your phone at all....I'll cut and paste what Haykuro's directions were on this part to emphasize the importance of not touching anything....
(LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
Mine didn't take very long but if it does still do not touch anything. Please....just don't!
Once it is done press HOME+BACK to reboot the phone out of recovery mode.
Power off your phone and then press the camera button while pressing the power on button to go back to the fastboot menu. Press the “call” button (to the farthest left remember!) so you see it say “FASTBOOT USB”. Once again...If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
In the command prompt which you should have left open for convenience you have to type “fastboot flash boot boot.img”
Then type “fastboot flash recovery recovery.img”
Then type “fastboot reboot”
At this point you basically have root but you need to change permissions on a file that need to be on the phone so everything works as your would expect with root
Turn the phone on to be on the operating system.
Type “adb root” in the command prompt to confirm you have root access
Download this file http://www.magicandroidapps.com/su.zip
Unzip the file to the tools folder of the SDK
In the command prompt type “adb remount”
Then type “adb push su /system/bin/su”
Then type “adb shell” and you should get prompted with a # symbol
Type “chown root.shell /system/bin/su” right after the # symbol
Then type “chmod 6755 /system/bin/su”
That should be it...try running the market enabler or SetCPU which you can get here http://forum.xda-developers.com/showthread.php?t=505419
If they work then you have root....currently you CANNOT use any of the custom roms because they were made for T-Mobile versions of the G1. I'm waiting for conversions of these roms myself so have fun waiting just like me. This is the first time I have ever hacked/rooted any phone so be sure to research stuff yourself...I might have things wrong. Who knows....it's all a risk just like I took when I decided to try it without having a step by step guide to read from.

Remember guys...I JUST wrote this so be sure to read it the whole way through before jumping into things. Post problems you run into here so I can fine tune it.

so you managed to root the rogers G1?? great job!! did you figure this out yourself???

no...Haykuro did this. I just took all the available information and put it in order to help others do it. It was all in this thread here http://forum.xda-developers.com/showthread.php?t=522127

Can we get a tutorial of how to flash a new rom now I really want to try out the new hero rom.

there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.

XwXDv8XwX said:
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
Click to expand...
Click to collapse
Is Haykuro working with Cyanogen? Man I just want to play with the Rogers Rom. Oh well I guess I'll settle for getting rid of the Rogers crap and being able to buy stuff on the Market finally.

Yep, I made a 3.6 for the Rogers Dream. I haven't actually tested it because I don't have one, but I used Haykuro's tools to build the boot image. Let me know if it works for you guys!

Holy...where is that at? lol

My wife has gotta get her ass home with my phone damnit! lol

http://forum.xda-developers.com/showthread.php?t=518851

lol, I just finished restoring my phone too. Oh well I am downloading your files now cyanogen, here's to hoping I don't brick my phone on my first flash attempt.

Can someone point me to a guide to flash this rom to my phone?

XwXDv8XwX said:
Can someone point me to a guide to flash this rom to my phone?
Click to expand...
Click to collapse
After you have rooted, copy the file to your sdcard as "update.zip", boot into the new recovery mode, wipe your data if you are coming from the stock build, then flash the update! The first boot will take a bit longer than usual. Check my thread for a FAQ.

Just wanted to say "Thank You" I have been following the threads in the background for the better part of a week, and was hesitant to give it a shot as I am not too sharp on dealing with dos boxes. However followed it along and everything went off perfect, grabbed set CPU and installed it and works. So I guess I have root. Not really sure what I can do with root, but will look forward to browsing around and seeing what is cool.
The big thing is I want to be able to flash new roms. So I guess this is the first step in doing that. (already actively flash PPC roms on the Hermes)
Again thanks for everyones work on this.

well here it goes....it'll be the first time I ever flashed a new rom to my phone...at least I know some other people have tested this version of cyan's rom so I feel pretty safe doing this. I would just send it back and pretend I don't know what's wrong with my phone if I did brick it but things seem to be going pretty smooth so far.

I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.

XwXDv8XwX said:
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
Click to expand...
Click to collapse
No, you wipe before the update. Wiping doesn't erase your SD card, only the internal data partition.
Also, my ROM is a "Google" based ROM. You'll have to sacrifice the spiffy HTC dialer and Exchange support, but I include all the other HTC apps.

How's your flash going XwXDv8XwX? I tried, but was stuck on the Rogers screen for more than 10 minutes. I rebooted the phone and tried again using the "adb logcat" command to try and see what my phone is doing but as soon as it restarted I stopped getting stats. Is this like a 20-30 minute setup process perhaps?

This is taking ALOT longer than usual. It's staying at the rogers logo right now....how bad is this?

Bricked cdma htc hero after ruu 1.56

i ran the ruu update when i got my phone and went to 90 percent then error 110 missing file,
now it only goes to fastboot menu with no options to select from, ive tried the ruu from sdk and same error,
so if any help i can get from you guys would be greatly appreciated,
ive looked all over the google.com and have come up with no luck on how to fix this ,
i know its like the radio image that doesnt flash or something, also in sdk i cant adb to recognize device.
please help ive been to geekfor.me and no help there,
if it helps the phone is a with google stamp on it. well lets see how this thread goes from here.

Try re-downloading the ruu.
What rom were you coming from?

I haven't found anyone that has a solution to the 110 file error when flashing the RUU...
I as well as a few other gave up hope and have all since gotten replacement Heros.
The main crux of the issue is that the fastboot you are booting into will not allow adb commands and hence will never allow the RUU to install completely.
Hate to say it, but figure out a way to exchange the phone for a new one, you are stuck in an infinite loop of 110 errors...
R

Hi again R.
Yes, error 110 is a nasty one indeed. It's the reason I am hesitant to root Hero #2. I still have my 110'd Hero and am (so far unsuccessfully) hacking it back to health.
@turboek99: Yes, what rom did you have installed? Mine was modaco 2.2

gibsontest said:
Hi again R.
Yes, error 110 is a nasty one indeed. It's the reason I am hesitant to root Hero #2. I still have my 110'd Hero and am (so far unsuccessfully) hacking it back to health.
@turboek99: Yes, what rom did you have installed? Mine was modaco 2.2
Click to expand...
Click to collapse
I already re-rooted both of my phones again and am playing with ROMs, LOL so although I know what the concerns are with RUU, I'm just hoping that I can not mess things up so much that a RUU would be my only choice. My only issue is I cannot deal with the phone being as slow as it was and without Root and a ROM, I feel like I'd rather go get something else... So I have no choice but to play with fire...
The way I see it, if I can keeep these stable long enough and something finally does happen, I only hope the Supersonic is out and I an "forced" to upgrade
R

Didnt know that about ruu...sucks.
Just noticed ur screenname,turboed b16?..u take it out to the tracks or run it in the streets?.....ima take a guess and say u stay in socal?lol

johndoehizzle said:
Didnt know that about ruu...sucks.
Just noticed ur screenname,turboed b16?..u take it out to the tracks or run it in the streets?.....ima take a guess and say u stay in socal?lol
Click to expand...
Click to collapse
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"

I'll probably brick my phone intentionally when the Supersonic or the next-gen Sprint android comes out so I have an excuse to upgrade.

Anyway... back on topic. Try flashing recovery image from ADB like this:
Code:
adb remount
It should then say remount succeded.
Code:
adb push recovery.img /sdcard
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
and then flash a custom ROM. I actually made that mistake when I first rooted.

Kcarpenter said:
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"
Click to expand...
Click to collapse
Niiice.i got 2 ej1's. One auto.the other stick.i used to run that one all the time,had a turboed gsr swap with type r head.got rid of it n back to a single cam...i recently got it stolen too..stereo n black slips with brand new tires got jacked lol.left it sitting on the ground..

Kcarpenter said:
Kcarpenter <- Turbo b16 '94 Coupe. Uber Fun down "The Dragon"
Click to expand...
Click to collapse
Mistamike <- 2001 Integra Type R

HeroMeng said:
Anyway... back on topic. Try flashing recovery image from ADB like this:
Code:
adb remount
It should then say remount succeded.
Code:
adb push recovery.img /sdcard
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
and then flash a custom ROM. I actually made that mistake when I first rooted.
Click to expand...
Click to collapse
there in lies the problem, after you get the 110 error you have no more ADB. it boots into a fastboot that does not have ADB support
so the real problem is how to re-enable ADB commands, then reflashing should be simple and straight-forward...
R

RTessi said:
there in lies the problem, after you get the 110 error you have no more ADB. it boots into a fastboot that does not have ADB support
so the real problem is how to re-enable ADB commands, then reflashing should be simple and straight-forward...
R
Click to expand...
Click to collapse
Well, you can flash in fastboot... but that never worked for me.

I'm on this same boat and have been trying to find a solution. Luckily I just recently got my phone and am planning on taking it in. I did seem to find a thread where someone fixed this but they didn't say how... I messaged the guy who helped that person out but he hadn't replied yet. Forum dot ppcgeeks dot com/showthread.php?t=111587 Hope it is ok to post the link otherwise I apologize. I would really like to get my hero fixed if possible. I have a sprint hero 1.56.651.2 and used the signed RUU that's on a few threads. At first, I kept getting the connection error while trying to do the RUU, I wish I would have stopped here. But I finally got the RUU to detect and start. it was at around 85% when it moved on to the next thing after user settings I believe and it gave me the ERROR[110]. I've tried the holding volume down and powering on and many other keys but no luck.

finally got it replaced
well i got a replacement phone so kinda happy now, too bad it s a refurb unit as opposed to the brand new unit i f'ked up before. well off to what i was when i fked up my other one.haha

Heh, ditto. I got a brand spanken new one though. This time I made a backup before I soiled it.

Lost Root Running Damages Last Rom - What guide do I use to get my root back?

Some how I lost root access to my phone. I was having memory issues with the phone and after uninstalling everything it was suggested I install a memory manager. I did and it didn't work so I uninstalled it and I think my root access went with it.
At any rate I was instructed to open a command line on my phone and type SU and see what happens. I installed ConnectBot so I could get the command line access and typed SU and it came back access denied. So I guess that proves I lost my root access. But my question now is what guide do I use to get it back? The original guide I used said it was for v1.5. The other guides listed are for people that have done the OTA and have the Sprint 2.1 running on their phones. Well I'm in between and I have Damages 2.09.1 rom.
So what is my next move to get the root back? In reality do I need root at this point? What would happen if I just reflashed DC's rom again?
Help or comments will be appreciated.......
Lisa

You didn't lose root, you lost Superuser, search the DC2.8 thread about SU...

I did and either didn't find the right threads or didn't find the solution but I didn't get it fixed. All I found was that debugging needed to be checked and it is. Still no SU access. Give me. More help if you can......
Thanks...
Lisa

I did and either didn't find the right threads or didn't find the solution but I didn't get it fixed. All I found was that debugging needed to be checked and it is. Still no SU access. Give me. More help if you can......
Thanks...
Lisa

Download superuser from the site below and flash it though recovery. That should fix it. Make sure to get the proper zip for your version of Android.
http://handheld.softpedia.com/get/System-Utilities/Enhancements/Superuser-106560.shtml

Open your app drawer...Do you see anything that says Superuser Permissions?
What memory issues were you having? If it was storage problems, perhaps try Apps2SD -- usually takes care of any internal storage issues when you get it working. This thread here is for A2SD: http://forum.xda-developers.com/showthread.php?t=715116
Reflashing the DC ROM really wouldn't hurt anything either, you'd just have to re-setup your accounts, preferences, etc. and redownload all your market apps.

Lots of good information in these two responses. I have some questions. First what Rom do I have? Cupcake, eclair, donut? Just know its DC's last Rom.
Next could you explain how to "flash from recovery". Is that done through Nandroid?
Next I do have SU in my app drawer. It will open and has a green button besides my to programs that use SU. But SU doesn't seem to be working.
Finally flashing the Rom again is something I want to avoid as I really don't want to start from scratch.....
Thanks for your help.........
Lisa

mslisaj said:
Lots of good information in these two responses. I have some questions. First what Rom do I have? Cupcake, eclair, donut? Just know its DC's last Rom.
Click to expand...
Click to collapse
These refer to versions of Android. You have 2.1 which is aka "eclair". 1.5 was aka "cupcake", 1.6 was "donut". Almost all ROMs here are 2.1 eclair, with the exception of the cyanogenmod which is android 2.2 aka "froyo".
mslisaj said:
Next could you explain how to "flash from recovery". Is that done through Nandroid?
Click to expand...
Click to collapse
No, it is done in recovery. To boot into recovery, hold Home then press Power on your phone. One of your recovery menu options will be "Flash zip from sd card". After you put any .zip files on the base/root of your SD card, this is how you will flash (or install) them. "Nandroid" only refers to the process of backing up and restoring your data, which is a separate option in the recovery console (Backup/Restore)
Did you try reinstalling the Superuser.apk? It may just need to be reinstalled.

Mr. chromiumleaf.....
Thanks so much for the information here. I have "flashed" from recovery but didn't realize that was what it was technically called. I have in my own terms refered to "Recovery Mode" as Nandroid. But now I will associate both as one. Thanks for clarifying what version Rom I'm running. I didn't want to guess so I asked. I think I will uninstall the Superuser that I have now and then reflash the new version that I will down load. I will report back. This would be so cool if this settled my problem............
So appreciate it and I will let you know..........
Lisa

I am following through as I alway do to thank you all for your help and tell you how I resolved the problem. I received some great advice from everyone and the last tip, which is usually my luck was the best.
The bottom line someone questioned why I thought I lost root. I explained what was going on and the best and final suggestion was to down load the latest Superuser.apk and flash through "recovery". Yes I had to ask exactly what that meant but I followed the directions and did it. Problem solved. I had SU working on my phone for Root Explorer and Titanium Backup. Then I downloaded Cachecleaner and it worked this time perfectly and it found 25MB of junk on my phone and cleared it out. So now I'm running 40MB of internal memory with all my programs working rather snappy now. In my estimation I screwed up the SU with the memory manager that was recommended somewhere along the line. When it didn't do anything for me I uninstalled it and I think my SU went with it. But the phone is fixed and I want to thank you all for your time in responding to my problem and requests. Sometimes multiple............
Thanks again.....
Lisa

Good to hear you got everything fixed. Glad to have helped out.

Yeah...and that's why there are people in this world more patient than I.
Sent from my HERO200 using XDA App

[Q] Root stuck, Red triangle and exclamation mark

Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.

You need to do the root process to get to the care bear, then flash villainrom on the care bear, before rebooting.
That will get you sorted

Well I rooted using universal androot, then used the teminal to input the su (press enter)
flash_image recovery /sdcard/recovery.img (press enter) part of instructions but at no point do I see the care bear :S

I have the same problem as Ejen. The phone is root i have superuser permission i do titanium backup .I put RA-hero-v1.7.0.1 with Better Terminal Emulator. When I turn off phone and press Home&Power I get a picture phone with a triangle. Does anyone have an idea how to solve this?

Yes, this is because stock rom automatically reflashes recovery with the stock one each shutdown iirc.
You need to stop this happening, but I can't remember the command. When you have root using universal androot though, you can stop it happening.
Or maybe it's too early for me. Wait till I've had a coffee or two and I'll revisit this...

Perhaps you can edit /system/etc/install-recovery.sh. A quick look trough /system didn't find anything like a shutdown script so perhaps this file is run by the android environment.

I had this same issue the other night, been searching for a fix, hopefully one appears here soon, thanks Pulser_g2, i was hoping to install your 1.5 Rom
Bloke

Ah seems I'm not the only one well at least I wasn't just being silly then, well tried it multiple times but still seem to have no success even tried the unlockr websites method with no success either.
If anyone knows thanks

Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try http://forum.xda-developers.com/showthread.php?t=726118 and see if that works.
I'm trying to work out what's going on here...
P

I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help

Ejen said:
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Click to expand...
Click to collapse
Ok,... So how far did you get on setting up adb http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) ?

I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know

Ejen said:
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Click to expand...
Click to collapse
Type adb devices, and if you see your phone's serial number, then you don't need to worry about drivers. Remember to "cd" into the correct folder first.

I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back

Ejen said:
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Click to expand...
Click to collapse
Where have you downloaded your Android SDK too?
for example > "cd c:\SDK\tools"

pulser_g2 said:
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try VillainROM Roots 2.1 and see if that works.
I'm trying to work out what's going on here...
P
Click to expand...
Click to collapse
I guess that is already on the phone RA-hero-v1.7.0.1 as you said stock rom automatically reflashes recovery. I suppose that the method VillainROM Roots 2.1contains RA-hero-v1.6.2.img. What will then happen with recovery if i try to do again root with VillainROM Roots 2.1?

When you try that method, you get the phone booted into patched recovery, at which point you take a nandroid backup and flash a custom ROM.
this prevents the recovery being lost. Just try it

I'm not at home and can not install ADB and run runindos.bat. I have on SD card recovery and FroydVillain 1.5. That's why I tried this method.Next week I'll be home and if someone does not fix the problem i will try the method you suggested me.
Can I try to put again recovery with Better Terminal Emulator, maybe recovery was corrupted ....

i went through the same thing!!
Ejen said:
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
Click to expand...
Click to collapse
helloo!! i apologise if i am interupting or butting in whilst your in the middle of other solutions... i just saw the title and jump right in. i went through the exact same thing just 2 weeks ago!! unfortunately for me there was no successful forums or websites at the time... it sounded like a simple problem, with no simple solution.
this may not be what you where looking for, but its a very quick easy method that definately worth a try.
so... am i right in saying you have the official OTA HTC android 2.1 update?? and you now want to get this rooted?? and have you also tried rooting using the two common methods, the "one click root" and the "unrevoked" one? thats wat i did and i kept being stuck at the same red triangle and exclamation mark.
those methods (and countless others) will not work with the official htc hero android 2.1. (as far as i know) what you will need to do is downgrade the phones software. check htc's website and look for the older RUU and using the computer get your hero back to android 1.5. (under no circumstance should you upgrade your 1.5 android to the 2.1 android via HTC's OTA update... its only going the remove the root access!!!! - always reject it)
then continue to root as per the numerous rooting guides. done? now, obviously you will want to flash an android 2.1 rom. if you want to keep to htc's original 2.1, you can search for this in the forums under 'development'. or go ahead and flash the custom roms (villianrom).
thats exactly how i did it. im not entirely sure if this is the info you are after... but reply back and ill be happy to answer any query - big or small. (i should warn you, im no expert - but this forum is filled with the earths most powerful brains - u should have an answer in no time!!)

I have an HTC Hero. I ran the simple root method and got Carebare response.
I too have read numerous threads in the forum here and elsewhere but can't seem to get past the USB section.
adb says no device
I can use HTC Sync to sync data to the phone.
The SDK is installed and I have previously used it to capture screen shots of my device.
If I try to run one of the RUU executables, it fails with a [114: USB Error] (number may be wrong but the message is right.
I can mount the SD card and copy files to/from it.
I am running Windows 7 Home Premium 64bit on a Quad Core AMD CPU.
If I do the Home/Power thing, I get the same red triangle as described in the 1st message of this thread.
Fwiw, I have successfully and repeated loaded ROM's on my previous phone (HTC S621) so I am not a complete newb (but i am newb to Android).
What am I missing? This shouldn't be this hard (at least from what I've seen posted anyway)

Somebody, i need to unroot my phone using Mac , don't know how

im having problems , on how to unroot my phone , so i can install EB13 , i know that i have to open App Terminal , but don't know what to type next inside of it
and what does this mean's (chmod +x run.sh and run it)
somebody plz explain it to me like a little kid
just recently change from Windows to Apple and everything is different and frustrating ..thanks

Somebody!!!! plz help me

I'm having trouble understanding. Rephrase
Which eb13 did you download? I think z4root can root and unroot an epic. I just used it to perm root my gf's epic last night. She rolled back to di18.
It can be done on a Mac but I gave up and dual booted with XP and flash that way because it's easier.
Or something easier could be to dl a version of eb13 that you can flash with clockwork recovery. Flash it like a rom. Clear all the caches and do a full factory wipe in clockwork then flash the rom. After that root if possible with z4root app. Get eb13 that is a full install in recovery, not an update.

have you tried here? there are instructions for osx
http...forum.androidcentral.com/epic-4g-rooting-roms-hacks/60768-how-factory-restore-fix-bricked-phone.html

I talked my gf through flashing an update.zip that was a full di18 with clockworkmod mod that was already on the phone from when I had it. As long as you already have cwm recovery and there's a version of eb13 that is full and meant to be flashed in custom recovery, I don't see why it wouldn't work. You could do all this without a computer or at least I did when she went from eb13 full to di18 full.
If rom manager had an epic recovery on the server, I checked last night and it's gone, I think in theory it can be done. If you had a new phone, run z4root for permanent root. Then run rom manager for cwm recovery. Then download full eb13 that is set up to install like install.zip. Boot into cwm recovery and clear out all caches and do full factory reset then flash the new rom. Then boot into phone like normal and set it up. Install and run z4root again and hope it works with froyo. Then I think you're done and didn't use a computer. Someone will probably point out that there's some thing that needs a PC for.
Use wifi of course

This is actually quite easy thanks to the directions posted in this thread here:
http://forum.xda-developers.com/showthread.php?t=808103
If you rooted using the one click method, I believe this should work to undo root. Someone please correct me if I'm wrong as I'm still new-ish to this myself.
INTEL MAC & LINUX:
Note: Mac and Linux users may be prompted to enter administrative password, as adb server requires sudo permissions to start.
No drivers required.
Extract the zip file.
Open Terminal. Use the cd command to get to the directory. If you extracted inside the Downloads folder, it would be easy in Terminal as so:
Code:
cd ~/Downloads/epic.aio.v2.04
Now give permissions and run it:
Code:
chmod +x run.sh
./run.sh
Click to expand...
Click to collapse

sorry, let me b clear , i did a clockworkmod(2.5.1) a few month ago with my Mac , now i forgot how to uninstall it. Anyways i download a version of Eb13 to my sd card(on the phone) an when i try to install it on my phone it says that it install , but when i go to chk the version it still's showing 2.1 update 1
i did everything through the phone but it is NOT installing EB13
question, do i need to bring my phone completey to stock, that means removing the Clockworkmod(2.5.1) or can i install EB13 with the CWM already in my phone???
Where can i find a good version of EB13 that i can download straight from my phone, cuz using my Mac and trying to push the program through it is a little bit of confusing inputing all does codes , like , what the hell this means ( chmod +x run.sh)???

come on man, read a little bit. you can do it.
get access to a windows computer for a few hours and use ODIN to flash over EB13. read xda's samsung epic wiki page.

Art77 said:
sorry, let me b clear , i did a clockworkmod(2.5.1) a few month ago with my Mac , now i forgot how to uninstall it. Anyways i download a version of Eb13 to my sd card(on the phone) an when i try to install it on my phone it says that it install , but when i go to chk the version it still's showing 2.1 update 1
i did everything through the phone but it is NOT installing EB13
question, do i need to bring my phone completey to stock, that means removing the Clockworkmod(2.5.1) or can i install EB13 with the CWM already in my phone???
Where can i find a good version of EB13 that i can download straight from my phone, cuz using my Mac and trying to push the program through it is a little bit of confusing inputing all does codes , like , what the hell this means ( chmod +x run.sh)???
Click to expand...
Click to collapse
thats a command u put in terminal..u have to put something before that though.. go here and download the file....leave it in your downloads folder unzipped...go into terminal and paste the first code...then copy second code (chmod + run.sh
./run.sh) and your good it opens a script and im not sure which but one of the numbers does the uninstall....but yea u shouldnt have to uninstall....just find a pc get odin and odin the EXT4 version here and its ALOT easier..

is not working or im not doing it correctly...thanks anyway i give up