i downloaded and have been running asops 2.2 rom but i just changed my phone number with sprint and I cant figure out how to update the msid. obviously sprint cant help me since im not using stock rom. anyone know where to look or an app i can download, because under settings: about phone: phone status: shows my old phone number, and i cant make calls or send msgs because of it.
they kept giving me ## codes but they wont work it just tries to dial the number.
Sorry woulda responded sooner, been busy. You need to flash a sense rom to use dialer codes our have sprint modify the phone or account info tied to it.
ugh... ok can you recommend a quick and simple rom so i can do that real quick
hate flashing it takes forever without a highspeed usb. anyways, downloading a sense rom now. thanks
arrg! ok i downloaded and flashed over to herocs 2.2 sense rom, tried doing the ## codes and nothing happens.
anyone??? im kinda screwed here.. cant use my phone until i get the prl updated
If all you need to do is update prl, and you have a sense rom flashed, you can do that from phone settings. I believe it is under "about phone".
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
user7618 said:
If all you need to do is update prl, and you have a sense rom flashed, you can do that from phone settings. I believe it is under "about phone".
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
Click to expand...
Click to collapse
it should be, but its not. under about phone, this is what i have :
network
phone identity (no update option)
battery
hardware information
software information
legal information
MyHerox25 said:
it should be, but its not. under about phone, this is what i have :
network
phone identity (no update option)
battery
hardware information
software information
legal information
Click to expand...
Click to collapse
Just use LiquidSense to update it.
what is liquidsense?
this is the rom i flashed to for temporary purposes
It is a 2.1 Sense ROM that can be found in the Development section.
well i guess no need to worry about this anymore, the charging dock on my phone is now broken or something because nothing will charge my phone.
Try a different battery. Or a different usb cable.
Root/Hack-Mod_Always*
ok i was in panic mode earlier being without my phone and all...
got liquidsense, updated all info. all good there. however when i flashed back to aosp rom its suddenly really glitchy, i cant get passed the "touch the android" set up screen!
attempting to reflash and see if that helps any...
nope....man this is a nightmare. btw gave thanks to everyone who replied in this post.
well... i flashed back to LS and even that one glitches out at the set up menu. so im still nowhere with my phone.
**UPDATE**
i found a backup copy of aosp rom that i originally downloaded in another folder on my sd. everything is working just fine now couldn't have done this without your help (all of you)
MyHerox25 said:
well... i flashed back to LS and even that one glitches out at the set up menu. so im still nowhere with my phone.
**UPDATE**
i found a backup copy of aosp rom that i originally downloaded in another folder on my sd. everything is working just fine now couldn't have done this without your help (all of you)
Click to expand...
Click to collapse
Glad you got it up and running.
First Just for your future reference so your not crappin all over yourself.lol (Been there) If you haven't already make a nadroid of the LS Rom or sense Rom that you used.
Second,I believe alot of the people around here that flash between sense and CM and AOSP do a factory rest or wipe from fastboot(look in this guide for instructions on this http://forum.xda-developers.com/showthread.php?t=1063843 by forum memeber il Duce )the reason being is that (from what I've read) is that sense roms leave bits and pieces of files behind that can corrupt a flash,or make you phone wonky after it boots up.
P.S. If you ever have to RUU or unroot when you re-root makea nandroid of that after you root and keep it some where safe so you can go back to it.
Yes, wipe data, cache, and dalvik every time you change roms. Especially between sense and aosp. The only exception us when flashing an update to the rom you're currently running. Even then, it may require a cache and dalvik wipe. Wipes are not necessary when restoring a nand. Also, keeping a sense nand is a good idea, as out makes it quicker when prl updates are needed.
-----
Sent from my CDMA Hero. I got some hot Ginger-on-Hero action here!
Related
So, first hello and thanks ahead of time for answering a noobs' problem.
I wanted to search before posting but don't know really where to start.
I followed the Tutorial Ninja guide to rooting found here:
http://tutorialninjas.net/2009/06/27/root-jailbreak-an-android-g1/
(so you can see which ROM, img, etc I used)
Everything went according to plan, except that the second command listed gave an error, that "-f no such file or folder could be found." But commands 1 & 3 worked, so I proceeded.
The problem I ran into was that when I upgraded the ROM at the very end, it would not boot up, it got stuck at the metallic "android" screen and was just stuck in a loop.
So, not having a microSD card reader, I just restored to factory settings. However this time, the beginning screen called my phone a Developer Phone, which it isn't. So it must not have restored everything to factory.
It appears the phone has a lot of the cupcake features, like auto-rotate screen, soft keyboard, but how could it be cupcake if I did a factory restore?
Here's the details listed under About Phone:
Model number: Android Dev Phone 1
Firmware version: 1.5
Baseband version: 62.33.20.08H_1.22.12.29
Kernel version: 2.6.27.25-cm [email protected] )
Build number: dream_devphone-userdebug 1.5 CRB43 148830 test-keys
I'm used to looking for an RC#, like RC33, but since I used a diff ROM, I have no clue what I'm running and if I indeed have root access.
Anyway, the point of rooting the phone was to have tethering capability, so I downloaded the Tether App and when I attempt to tether it asks me if I want to "allow" access for root:root (I'm paraphrasing) so it seems it is rooted. Can someone help me figure this one out?
Also, since I'll have to manual updates, where should I go for them?
This is such an awesome forum, and look forward to being part of the community. Thanks
meanderingthemaze said:
So, first hello and thanks ahead of time for answering a noobs' problem.
I wanted to search before posting but don't know really where to start.
I followed the Tutorial Ninja guide to rooting found here:
http://tutorialninjas.net/2009/06/27/root-jailbreak-an-android-g1/
(so you can see which ROM, img, etc I used)
Everything went according to plan, except that the second command listed gave an error, that "-f no such file or folder could be found." But commands 1 & 3 worked, so I proceeded.
The problem I ran into was that when I upgraded the ROM at the very end, it would not boot up, it got stuck at the metallic "android" screen and was just stuck in a loop.
So, not having a microSD card reader, I just restored to factory settings. However this time, the beginning screen called my phone a Developer Phone, which it isn't. So it must not have restored everything to factory.
It appears the phone has a lot of the cupcake features, like auto-rotate screen, soft keyboard, but how could it be cupcake if I did a factory restore?
Here's the details listed under About Phone:
Model number: Android Dev Phone 1
Firmware version: 1.5
Baseband version: 62.33.20.08H_1.22.12.29
Kernel version: 2.6.27.25-cm [email protected] )
Build number: dream_devphone-userdebug 1.5 CRB43 148830 test-keys
I'm used to looking for an RC#, like RC33, but since I used a diff ROM, I have no clue what I'm running and if I indeed have root access.
Anyway, the point of rooting the phone was to have tethering capability, so I downloaded the Tether App and when I attempt to tether it asks me if I want to "allow" access for root:root (I'm paraphrasing) so it seems it is rooted. Can someone help me figure this one out?
Also, since I'll have to manual updates, where should I go for them?
This is such an awesome forum, and look forward to being part of the community. Thanks
Click to expand...
Click to collapse
Doing a factory restore merely does a wipe of the data folder. You will still keep your ROM, SPL, radio, etc things that you've flashed. Those things stick with you. If its asking you for root, press always allow. You have root.
Firmware Version: 1.5 = cupcake. 1.1 = noncupcake. So you succeeded.
If you want to double check, go into terminal emulator (just download from market if you don't already have it)
When you open it, you should see:
$
from there, type su
$su
if you get:
# <- this means you have root permissions.
You can download custom ROMs from the developers forum. Just find one that you like and try it out, most of them only require you to wipe/flash the ROM from recovery (Home+Power). Cyanogen's are always a nice choice, or you can try Haykuro's or JesusFreke's (JF). But always check to make sure you have to the requirements to flash the ROM before doing so. They're usually located on the first post of the first page, so don't ask if you need this or that.
H
Hi, you do indeed have rooted cupcake my friend when you do a wipe, it's like a factory restore, it doesnt reflash the firmware the phone came with, it just re sets everything so the phone is "as new". This fixed the bootloop you had for some odd reason so your phone now boots up. It shows as an Android Dev Phone because you flashed the dev phone firmware.
That's it really, everything appears to be fine
I was beaten to it by the poster above because I was typing on my G1 Oh well, the 'su' in the terminal is a good point though.
Off the top of my head I'm not sure what version you're running, but yes - it is rooted. Does tethering work? If so, you're all set.
Well, mostly. Your radio is out of date. Use the link in my sig to snag the latest, apply it in recovery like the update.zip you did to flash your ROM.
What to do for updates is up to you.. There are many different ROMs out there, just need to pick which one works best for you. Personally, I suggest Cyanogen. But a new user shouldn't use the link in my sig.. Go over to the Development section of the forum and find the CyanogenMod 3.6.8.1 version - it's currently the stable version. If you want regular updates (new patches from Google, community developed features, etc) CM is the way to go.
SOLVED
h.nocturna - I did get #, I have root! everybody dance. Good to know about the factory restore
AdrianK - thank you. i guess i got kinda lucky fixing it myself, mostly due to lack of options. hehehe
Saiboogu - I have yet to get the tethering working. I tried today at work with a Mac Pro via Bluetooth, was able to pair, but could not establish a connection. I'm going to try later with my Ubuntu laptop which is what I will be tethering to in most cases anyway. I heard Bluetooth is the best way to go, but not sure why. Definitely convenient if you forgot your cord.
I'll check the dev forum to see about upgrading to the latest ROM, but I'm nervous, as I don't want to screw up my phone again. I was out-of-commission for half a day with this trial. But updating ROM should be easier that gaining root right? You don't need any special commands, just reboot and flash?
Again, thanks!!!
meanderingthemaze said:
h.nocturna - I did get #, I have root! everybody dance. Good to know about the factory restore
AdrianK - thank you. i guess i got kinda lucky fixing it myself, mostly due to lack of options. hehehe
Saiboogu - I have yet to get the tethering working. I tried today at work with a Mac Pro via Bluetooth, was able to pair, but could not establish a connection. I'm going to try later with my Ubuntu laptop which is what I will be tethering to in most cases anyway. I heard Bluetooth is the best way to go, but not sure why. Definitely convenient if you forgot your cord.
I'll check the dev forum to see about upgrading to the latest ROM, but I'm nervous, as I don't want to screw up my phone again. I was out-of-commission for half a day with this trial. But updating ROM should be easier that gaining root right? You don't need any special commands, just reboot and flash?
Again, thanks!!!
Click to expand...
Click to collapse
I'm pretty sure the bluetooth stack doesn't have transferring enabled at this point. You can only connect to headsets and whatnot, you can't transfer data. Try Wireless Tether (app from Market) to do your tethering.
Solved Again
Right again h.nocturna.
I am using the WiFi to type this post!
Thanks
meanderingthemaze said:
I'll check the dev forum to see about upgrading to the latest ROM, but I'm nervous, as I don't want to screw up my phone again. I was out-of-commission for half a day with this trial. But updating ROM should be easier that gaining root right? You don't need any special commands, just reboot and flash?
Again, thanks!!!
Click to expand...
Click to collapse
Don't be worried about flashing ROM's, the recovery console (power+home) is always available when you soft-brick, so you can always recover. My advice before you go any further is a) flash your radio if you haven't done so already, if you don't you may notice problems with calls, texts. data ect. b) grab cyanogen's recovery image and flash that. It will let you make an image of the phones memory (a nandroid backup) and then restore it if you soft-brick and are in a hurry to get your phone working again.
I recently sold my hero to a guy. here's the problem, he's having issues activating it on his account. in my mind i'm thinking it's because it's running the 2.2 froyo CM6 extremely blue and there's no access to the ## codes. i'm not nearly as well versed with android as i am with blackberry and winmo. i hate starting new threads but i can't find anything on this except that a sprint based rom "should" have the ## codes in it. He doesn't want to flash it back to stock and lose root access. Any help would be greatly appreciated.
This is what he has to do:
1) Nandroid to create a backup of the system as-is.
2) Wipe and reinstall a rom based on Sense -- don't use Sprint's RUU or any updates from them. When I did this, I nandroided back to an old copy of Fresh 1.5. But any version of Sense should work. Just make sure it's not from Sprint. Check the Development forum in this CDMA section and pick one.
3) Once that is up and running, he can use the ## codes in the Sense dialer app to do whatever he needs to do to provision the phone.
4) Reboot phone into recovery mode and wipe. Don't worry, wiping does not clear out anything done with ## codes.
5) Restore from the Nandroid backup created earlier. Reboot and wait while the phone rebuilds the cache files. Could take 10 minutes to do this.
6) Phone should now be working.
see i haven't messed with nandroid backups, but he hasn't had a chance to really set anything up on the phone. could we just wipe the phone, flash something like damage control (2.1 sprint based sense), get the phone programmed, then flash back to the 2.2?
Yeah but it would probably just be easier to nand backup, lash a sprint based ROM, then nand restore when finished.
ok last question (i think). and recommendations on a sprint based rom that definitely has the ## codes in it? it's hard for me to get internet access at my job so i kinda have to dl to my sd card before i go in. i already have damagecontrol on the card if that would work?
p3tr0s said:
ok last question (i think). and recommendations on a sprint based rom that definitely has the ## codes in it? it's hard for me to get internet access at my job so i kinda have to dl to my sd card before i go in. i already have damagecontrol on the card if that would work?
Click to expand...
Click to collapse
DC should work fine.
awesome guys thanks. i'll post back after i make the attempt
I, for some reason, wasn't receiving any text messages. I put stock back on and about 15 or so downloaded shortly after first boot.
What may have prevented sms from being received on the custom roms?
It seems to be an issue for some people as I have experienced it as well.
Froyo Powered HTC Hero
Just wanted to chime in since I was searching google for this issue. I have an evo and I've had this issue as well for the past two days on CM6 and a sense based rom so if you have sprint this may be an issue with them rather than the rom. I have yet to find an answer myself.
I did find the issue and it is a sms/mms database issue and can be resolved by deleting a file (which is immediately recreated and fixed). I found the answer (and regrettably didn't keep the link) in the CM 6.1 discussion thread.
Thanks for the replies.
Can you point me to that thread I'm having the same problem... Not seeing it.
Make sure your prl is current.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
Backup your current ROM, wipe everything, and flash a Sense ROM. Reboot and update PRL and Profile. Then wipe everything in recovery and restore your custom ROM.
Sent from my HTC Hero CDMA using XDA App
What is a "prl"? Sorry I am a nuub. I have CM6 flashed to my hero and have had it for around 6 or 7 months but all of the sudden I am not receiving SMS. I had read that if you were getting the "low space" msg that could be a cause but I cleared the space and I am still not receiving them. Any help would be appreciated.
chrislail said:
What is a "prl"? Sorry I am a nuub. I have CM6 flashed to my hero and have had it for around 6 or 7 months but all of the sudden I am not receiving SMS. I had read that if you were getting the "low space" msg that could be a cause but I cleared the space and I am still not receiving them. Any help would be appreciated.
Click to expand...
Click to collapse
You need to flash back to a sense based rom, then go to something like
settings > about phone > software version > system update
It should be clear from where you are what you are doing at that point, update your profile and prl from there and then go back to cm6.
Where can I get a sense based rom. I don't believe that I kept a copy before.
chrislail said:
Where can I get a sense based rom. I don't believe that I kept a copy before.
Click to expand...
Click to collapse
In the development forum http://forum.xda-developers.com/forumdisplay.php?f=643
thanks for the help!
I had the same problem. flashed cm7 from may version and no sms. so i got a sense rom, the the update prl and profile update and wipe and all that other stuff to get back my cm7 rom. sms works now on my hero!
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
muziling said:
When I install an new ROM, phone only can call out, cann't call in.
Seems install stock ROM then the first time flash 2.3 ROM, phone can call in and out.
Click to expand...
Click to collapse
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
kifno said:
MODS PLEASE MOVE TO HERO CDMA Q AND A SECTION....
...as for an answer....first answer a few questions and then i can help
what radio?
what prl?
what rom?
what extra "mods/tweaks" did you do/you're currently using?
what carrier?
Click to expand...
Click to collapse
radio: 2.42.02.10.29.zip
PRL: 2.20_003
ROM: aospCMod-HC-20110421-signed.zip
no tweaks
carrier: china telecom
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
kifno said:
try this:
look up on your search engine how to update to the latest prl and pri
then i'd also like for you to try a sense rom, a froyo rom, and cm7.0.2
then i'd like for you to tell me what was the last working rom you used that it worked on?
i have to know this information to help you as best as possible b/c right now there are a broad amount of solutions
Click to expand...
Click to collapse
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
Hmp, stick with a rom that works THAT YOU LIKE, not by what I tell you. But did you try these rom's?
- CM v7.0.2?
- GingerSense?
- AOSP 0.9.9.2 Froyo?
- CM6.1-RC2?
- NFX Stock Rom?
- My Sense Roms?
Try all of those and for whichever the phone calls work, take note of that. And then also I'd like for you choose what you like the best. Also did you try the update prl/pri on a sense rom? Try doing it on the rom you're on now
And glad to see it worked for ya bud
muziling said:
Last working rom is aospCMod-20110310-signed.zip
I update to aospCMod-HC-20110421-signed.zip last night, and phone call in problem happend, Now I flash Sprint_2.1(2.32.651.2), It works.
Click to expand...
Click to collapse
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
il Duce said:
FYI the functionality of the dialer is hard-coded into the phone, not each ROM, so if it works at all, it works. Sometimes phone and data issues can be solved by updating PRL and profile as suggested, but it sounds like your issue may have been simply your carrier at the time. If a phone can call out, it can call in, and vice versa. It may have something to do with the fact that you are flashing Sprint ROMs for a Chinese carrier, but who knows. There are a few members in these forums that are on your same chinese carrier and are running aospCMod without issue, one member in particular is called "oldghost", maybe you should PM him and see if he has had any issues, and what ROM best suits the needs of the Chinese version of the heroC. Good luck.
Click to expand...
Click to collapse
Yes oldghost uses a Chinese carrier and I don't think he had any issues at all. But first try updating the prl/pri
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
hareofthedog said:
Interesting. I just realized I'm seeing similar since (I think) flashing 4/29 aosp 2.3.3. Thought I had just messed up on a setting or something. Incoming calls are going straight to voicemail. I see them almost immediately in the call log on the phone, but no ring or any other indication. The only other record of the call would be the voicemail notification after a bit.
Now, my assumption here is that I messed up on my last flash, so I'll go back and do a redo, including going back to a sense rom just in case.
I was coming from 4/21 aosp 2.3.3. Before the 4/21, I did get rid of firerats, installed fresh, updated prl (now at 60678) and profile, though I think that's been current for me for a while.
I then installed 4/21 from scratch (fr 110/4).
Radio has been current.
4/29, I just wiped caches and flashed over.
Like I said, I'm sure I just messed up at one of these points. I don't know for sure when I stopped receiving calls. I don't get a lot of them, so it took me a while for the loneliness to kick in. It IS possible that I messed up on the 4/21 even.
Click to expand...
Click to collapse
Try troubleshooting the problem by doing the following things one at a time to see if they work:
- Try a different radio that works for the SPRINT HERO CDMA ONLY (else you will brick your phone, if you need help finding radios let me know)
- Try without firerat's
- Try wiping everything using the latest official clockwork mod 3.0 after backing up everything
- Try s0be's kernel
- Try the official CM7 v7.0.2
i can come up with more options for you to try one by one but that should last you for about an hour or so
after doing all those let me know what happens
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
hareofthedog said:
Actually, got this working again.
flashed aosp 2.3.3 4/29 clean, removed firerats, etc (since my next step would have been to put on a sense rom).
clean install seemed to fix the problem. Able to receive calls.
then for fun... did the full factory reset and wipe wipe wipe again, installed this time WITH firerats (100 20), bumped the cache size for the hell of it.
That worked as well. Calls being received. I think something just got hosed, or my original 4/29 install, which was just a cache wipe and flash over, didn't go so well.
Still figure it was user error on my part somewhere along the line, but all is well for me now.
Click to expand...
Click to collapse
Glad to see its working now. If you need any more help feel free to PM me or post again in the q n a forum and the community and myself will gladly answer your question asap.
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
muziling said:
same problem with hareofthedog, strange, phone can't call in ,but call log has call-in logs..Do I can use some command to print kernel logs?
flash cm7.02, now phone can call in
Click to expand...
Click to collapse
if a rom isn't broke, don't fix it...stick with gingerbread, its fresh out the oven
but seriously if cm7 works, then use it. unless if you really don't like cm7....but i doubt that..i hope
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...