Hi I have been flashing my g1 like crazy and after going to the hero build I decided to go back to cyanogens rom ver 3.3.6 and have radio 2.22.19.26I. The problem is that the call quality is rubbish. People say they can hear all the backhground noise and I sound very loud. Sometimes I can't hear anything and have to reboot the phone to hear any sound. Also my camera no longer works at all (just blank screen)
Think this may be a radio and or spl issue
If someone could give me a magic fix I would be forever greatfull
Thanks in advance
Searching can be of great help. You might perhaps find the answer you are looking for here:
http://forum.xda-developers.com/showthread.php?t=522213
Had the same problem. The solution is pretty straight forward. If you have problems making the changes, trust me that all the answers can be found on this site. Feel free to ask if you are still unable to make the changes on your own; but since you feel comfortable continuously flashing your phone, I feel confident you will be able to fix this problem.
Hint... AudioPreProcess.csv is where you will find the solution.
Thanks for your fast reply, I did come across this thread but not clear about extracting files from roms etc.
Perhaps I should of said that I re flashed original rom rc7 I belive and replaced spl,radio etc so should not have any remnants of hero left on my g1, then re rooted and upgrade rom spl and radio.
So judging by that post do you think the ion rom would solve my problem.
Thanks again
Ok flashed ion rom and sound problem seems to have been resolved but camera still not working, just black screen and force close.
Please help halfway there
Did you flash back to the ION ROM or did u port the AudioPreProcess.csv file from the ION ROM? ION is much faster than HERO (and stable) but I thought you were trying to make the phone call quality better on the HERO ROM. If I just misunderstood your last post and you are running HERO with the other build's .csv file, then to fix your camera, check this post:
http://forum.xda-developers.com/showthread.php?t=521421
It will also speed up HERO a great deal as well as making it more stable/usable (it adds HTC_IME VK as well as come other things). I've had the best luck so far by copying the app_s dir to /system/sd first using a ROM that supports app2sd such as the ION ROM. This is necessary if you are running Haykuro's orig hero-signed.zip ROM, but not on some of the "compacted" builds that can be found. Then ALT+W and ALT+S the update.zip. After the long initial boot, then it takes you to the initial setup screens. I always just skip/say no to all questions then setup the Google account after my home screen appears which prevents the force closes during setup. Then I replace the /system/etc/AudioPreProcess.csv file with one from a stable/working rom. Then run the HERO speedup .bat/sh provided by tehseano in the post above.
There's another script (created by sandeep I believe but cant find the post at the moment) that will move Rosie.apk to the internal memory as well as make some other useful changes. The link is on my laptop @ work so I can check and post the URL here later if need be. Will check back later. Good luck!
Aloha-
maubig said:
Did you flash back to the ION ROM or did u port the AudioPreProcess.csv file from the ION ROM? ION is much faster than HERO (and stable) but I thought you were trying to make the phone call quality better on the HERO ROM. If I just misunderstood your last post and you are running HERO with the other build's .csv file, then to fix your camera, check this post:
http://forum.xda-developers.com/showthread.php?t=521421
It will also speed up HERO a great deal as well as making it more stable/usable (it adds HTC_IME VK as well as come other things). I've had the best luck so far by copying the app_s dir to /system/sd first using a ROM that supports app2sd such as the ION ROM. This is necessary if you are running Haykuro's orig hero-signed.zip ROM, but not on some of the "compacted" builds that can be found. Then ALT+W and ALT+S the update.zip. After the long initial boot, then it takes you to the initial setup screens. I always just skip/say no to all questions then setup the Google account after my home screen appears which prevents the force closes during setup. Then I replace the /system/etc/AudioPreProcess.csv file with one from a stable/working rom. Then run the HERO speedup .bat/sh provided by tehseano in the post above.
There's another script (created by sandeep I believe but cant find the post at the moment) that will move Rosie.apk to the internal memory as well as make some other useful changes. The link is on my laptop @ work so I can check and post the URL here later if need be. Will check back later. Good luck!
Aloha-
Click to expand...
Click to collapse
Hi
I flashed hero but was not happy but upon flashing back my sound quality in calls was terrible, thats sorted now but my camera is not working, pulling my hair out
Sounds like maybe you forgot to wipe it clean b4 loading ION. If you can, try an ALT+W from recovery then reinstall the ION ROM and it should be good.
maubig said:
Sounds like maybe you forgot to wipe it clean b4 loading ION. If you can, try an ALT+W from recovery then reinstall the ION ROM and it should be good.
Click to expand...
Click to collapse
Hi
I have done multiple wipes. The thing that is also strange is that I created a 2 custom boot images and when I reflashed to original rom the 2nd splash screen was still there which sugests that some things have been left behind. I have had some thoughts about replacing the camera.apk file manually and seeing if this does the trick.
The only other thing I can come up with is the camera has a physical fault although this seems unlikely
Are you flashing backup img's or installing a fresh ROM? If you're installing from an update.zip that problem sounds interesting and you might have a corrupted download of your update.zip. Unfortunately I haven't found the MD5 posted by Haykuro for the ION build but can give you mine which I've had no problems with.
If you're flashing an .img backup, then your backup may be corrupted and manually replacing the camera would most likely work. There are several posts that have links and instructions on installing the camera or you can grab it from your ION update.zip and adb push it to your phone.
The only way to replace the splash screen at boot time (like the T-mobile G1 screen for example) that I know of is to:
fastboot flash splash1 mysplash.rgb565
or
fastboot flash splash1 splash1.img
So unless you've manually changed those, they should stay the same no matter the build you've loaded to your phone.
The boot screen that shows "HTC" or "ANDROID" that has the green robot or is animated is the one tied to the ROM.
Just to make sure there are no residuals, you can also:
fastboot erase boot
fastboot erase system
fastboot erase userdata
before you flash the .img. This will ensure thatn the partitions are clean on the phones internal storage.
Aloha-
Thanks for your quick reply. I will look into these options today, also I said the sound had returned to normal but a couple of times today I have not been able to hear anything even though the call had connected unless I reboot.
Do you think my phone is screwed or just a software issue
Thanks again
quick update ran fastboot commands above ran rc7 update again so everything is stock as it was, still camera not working only black screen with camera icon in corner.
mac_d4di said:
quick update ran fastboot commands above ran rc7 update again so everything is stock as it was, still camera not working only black screen with camera icon in corner.
Click to expand...
Click to collapse
Sounds like the camera app is working. Maybe the camera is not . Have you tried taking off the battery cover and making sure nothing is blocking the lens? Also, if you feel comfortable, you might take the phone apart and make sure the camera module's ribbon cable is seated properly.
Just an update for anyone searching with this problem
I had to return the handset (bought second hand) and moved back to the samsung Omnia
(miss android already though)
Thanks for all the helpfull people on this forum that have helped me out, will still be around just not on android
brian
Related
So today i finally get the gusto mod my phone Android Dev 1. After downloading all the files and following the instructions here i can't get past the black g1 screen (#8). note i can also get the the rgb screen. thats it, but with so many different posts with similar issues, my brain is pounding. At this point if i can get beack to factory, ill live. what i'll hate is the fact that bricked my phone. i'll most likely get screamed on for not searching, but i think i may be searched out. any help would be appreciated.
thanks.
docfu.
first of all dont freak out lol. Download the dreaming.nbh or w/e file from the rooting instructions and place it at the root of the sdcard. Then get into the rgb screen (Camera + Power) and flash it. That should get you back to factory settings. If not, download the update.zip for w/e region you are in place it on your sd card. Enter recovery (Home + Power) and flash the update.
ok...so i tried the DREAMING file and it kept turning up no image found, alternatively i'm not sure what you mean by w/e region update. i ihavent come across that in my searches.
ok dreaming file did infact work. i feel better knowing that the phone isnt bricked. however after running the update when it prompts for action, i hit the trackball and i'm right back at the rgb screen..AGGGHHHH! sorry. i've been at this since 3pm this afternoon.
Chill. Don't freak. You can't just jump in and do something as soon as your read it. Read the whole thing and if you don't have the patients for this work on that before you work on this. bbreath.
I must say start by saying thanks guys. i stepped back, and actually took my [email protected]@ to bed. Rest does wonders. That said. I've accomplished the factory reset. so i back to a stock g1, and boy does it suck. As stated my phone WAS a dev 1. i've already started the upgrade process, my question at this point is where do you recommend i go from here. back to dev 1 or try one of the other roms. i've already installed the spl, and right now im stuck at the telnetd part of the root process. and this too may have me screaming by the end of the day...
any thoughts would be appreciated.
After the recovery image is installed you need to update the radio if you want to install a cupcake 1.5 ROM. You can get it here, rename 'update.zip', place on the SD card and boot in to recovery and flash. Then flash a ROM of your choice. You should be able to do that on RC 30, but I'm not sure if you need to install a rooted image first, so I'd wait for someone else's input before trying that.
I played it extra safe and used the rc29. as far as i know the proper radio is installed. i'll wait around before i do something stupid. thanks for the input tho. i'm trying to learn everything.
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Future reference ^-^
In case you encounter this problem in the future, cause it can happen with flashing new roms if you skip a step:
You're only bricked if you are stuck at the G1 boot screen but can't get into recovery or fastboot, adb or anything. In cases where you can still get to other phone options to start over, rest assured your phone does still work, just need to step back and figure it out, which you did in this case with a little help ^-^ First few times doing anything to my phone, I went into panic mode a couple of times thinking I bricked until I read around and found out otherwise.
Just in case you didn't know these things, if you did, well, hope it was a nice read? ^-^
doctorfugazi said:
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Click to expand...
Click to collapse
Well... if you actually purchased a dev phone it should not be sim locked.
Technically... after the rooting process, we all have dev phones with the exception of the sim lock.
So... what SPL are you using?
What ROM are you trying to install? Some roms you should consider partitioning your sdcard.
What radio do you have?
First thing is first.
Get the 1.4 recovery if you haven't done so already. 1.4 Recovery
Because this allows you to select any .zip file without having to rename it to update.zip. This saves on confusion so you don't try flashing a spl (like danger spl )before a radio (could brick your phone).
Second
You need the 1.5 radio to use cupcake. 2.22.19.26I
Third
Consider an spl. You have 4 choices. HARDSPL (Recommended), Eng SPL (what the dev phone defaults with.. skateboarding androids), the standard spl (nondev) and Danger SPL (risk bricking but worth it because you have more memory for your ROMs and can try HERO builds).
Fouth
Find your rom. NOTE: Read each post carefully! If it says you need a specific spl then get it! Otherwise it won't work. Some require the Danger SPL. If you chose a JF rom then you should be alright and don't even need to partition your card and it will work just like the OTA release. Some (such as Cyanogens 3.9.7) are experiemental and are not recommended for noobs.
Fifth (and probably the most important)
ALWAYS BACKUP WITH NANDROID!!!
In the event that you think that you've bricked your phone. I would say that there is a 90% chance that you didn't. As long as you have a nandroid backup and can get to the bootloader then you still have a phone. Just make sure the fastboot.exe file is in your sytem32 directory of your computer. Open CMD and cd to your fastboot backups saved on your computer. Simply
fastboot flash boot boot.img <enter>,
fastboot flash system system.img <enter>,
fastboot flash userdata data.img <enter>
fastboot reboot <enter>
and you should be back to where you were immediately after the point you backed up. Think of it as a system restore for Windows. It couldn't hurt to have a few backups stored.
If you have any questions or problems include information for us to read in a single post and edit as necessary.
Example:
AT&T
Cyanogen 3.9.7 Rom
Recovery 1.4
HARD SPL
Radio 2.22.19.26l
8GB class 4 sd card (7gb fat32/900mb ext3/100mb swap)
Theme version if any.
That way we know what we are working with.
Happy flashing.
rest assured i was in panic mode yesterday. but honestly the only thing i could really do was just step back for a while, meaning get some rest tackle it with a clean head. its frustrating for sure. this one guy tho who posted in the brick think tank thread...just cuz he couldnt figure things out in an hour he got pissed and started screaming waste of time this that and the other. total BI$CH! I was like whoa. I was at that point too. but Im not tryna be that guy.
Now, if could just figure out if i have to start from scratch, i just might be able to get my phone working again in time fro me to go to work tmrw morning.
So... what SPL are you using?
the hard SPL found here
What ROM are you trying to install?
Well i was trying to follow suggestion on something simple, like one of the early jesusfreke's. if i can step it up sure why not. but i'll pass on the partitioned sdcard setup for now.
actually I'll run with JesusFreke JFv1.51 US CRB43
What radio do you have?
radio number listed in my previous post.
Hey thanks by the way for taking the time out of your day to respond to this. i know u guys get your fair share of spazmiesters, so i appreciate it totally.
after doing research it seems that all the current roms require partitioning. or is that optional just for running apps to sd?
partitioning is optional of apps2sd for preformance. some like myself have three partitions, the third being for a linux swap
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
doctorfugazi said:
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
Click to expand...
Click to collapse
Okay... you have the recommended recovery and spl.
So all you need to do is get your rom and radio and store the zip files to the root of your sdcard. You don't need to rename them.
Just boot in recovery (power+home) and scroll down to:
[Alt+A] apply any zip from sd
And then you should see the zip files.
Upgrade your radio first.
Then your rom.
Another note... make sure you have a data plan once you've installed your rom. Depending on your rom version, you may not be able to sign in without one. If you can't sign in, you can't use your phone which is why most would recommend a custom rom or an adp rom.
Now... if I'm not mistaken... you do NOT have to partition your sdcard to install a rom (unless it's a HERO rom).
You may want to consider doing so however.
The advantages are that you can have virtually unlimited storage for apps and it's much easier to restore them after a wipe because they are still on your sdcard. Some apps will recognize the partitioned sdcard and automatically do all the apps2sd work for you by default. It is also recommended that you use at least a 2gb class4 card at MINIMUM. Any slower then a class 4 may result in system crashes and errors. Any less then a 2gb card is almost not worth all the effort since you'll likely be using at least a quarter of it for the apps2sd. I would suggest buying at least a 8gb class 6 card for less then $50 online. It's both fast and plenty of storage. With apps to sd, if you do need to wipe you still have all of your apps installed. A great advantage of having apps2sd.
Also... try different roms! There are DOZENS out there! Some have the htc music installed, some have myfaves, some have special cameras, etc. Don't be afraid to experiment. As long as you have a backup and can get to the bootloader (skateboarding androids) and a pc, you can't go wrong! If fact... with the 1.4 recovery you can store several different roms on your sdcard, backup your current rom, wipe, flash a new rom to try it, wipe, flash a different rom to try that one, etc. If you decide that you didn't like any of those... just restore back to your previous backup. Simple as that. No pc needed. However having a pc is handy to get logcat information if it's not booting for some reason.
Speaking of roms not booting... while your experimenting with various roms... you MUST have patience. Sometimes (based on my personal experience with about 10+ different roms) they can take up to 15 minutes to boot up. You can literally be staring at the ANDROID or HTC logo this entire time. Unless you are using ddms.bat or adb shell logcat, you will be clueless of whats going on. DO NOT do anything unless you get the infamous "boot loop". This will be obvious. It will stick at the ANDROID or HTC screen for a while and then blink and go back to the logo. If you see it blink and go back to the logo then try pressing power + talk + menu to restart it and then immediately press the home button to bo back to recovery. Wipe... try again. This time it should work. If it doesn't then restore your backup while you research on that partitcular rom. You may have skipped a step or not have the proper requirements (partitioned card, spl, etc).
With all of that said... good luck and you'll be posting help to other users like yourself before you know it.
Hey Doc, if I'm not mistaken (other guys correct me if I'm wrong), if all, and I mean ALL you have is a boot loader (AKA SPL. ie// skating androids or colored bars) you need to reflash dreaimg.nbh to get a system back.
This ALSO flashes your SPL and RADIO back to default so reflash your radio and SPL afterward. (IN THAT ORDER I HOPE)
Binary100100 is a gentleman and a scholar
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
innerspace said:
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
Click to expand...
Click to collapse
Thank you! I do what I can.
Hello everyone! Last night I spent about 3 hours installing the JACXHERO-v2.6.6 rom onto my Tmobile G1 using a method from unlockr.com (http://theunlockr.com/2009/08/22/how...g-best-method/). Unfortunately, it runs extremely slow right now.
For example, when i press home after sending a text message it goes to the HTC screen and simply sits there for about 30 seconds. At first I thought this was due to the weather widget updating but even when I took it off it still does this. Another thing is that it will sometimes take 10 seconds to switch screens when i slide my finger.
I know I am still new to this and realize there are some veterans on this forum that have a lot more experience with this. Can anyone please suggest to me what to do?
The bottom line is, all i want to do is run a stable and lag free (or fast) Rom.
Thanks guys!
i am taking a few liberties...
from the line, that you want a stable and fast rom, i assume you would like another rom besides hero. so download the latest stable rom off of cyanogen's thread.
after you download it and put it on your sdcard go into recovery then to the recovery console and type
Code:
mke2fs -j /dev/block/mmcblk0p2
that will format your ext3 partition.
now type in the recovery console
Code:
reboot recovery
once the phone boots up into recovery again, wipe the phone then flash the rom, then reboot when it is finished.
alright will do but i was wondering if you could give me a step by step instruction on how to do all this (like i said im very new to this sort of thing) =/ im sorrry
mrxkpex said:
alright will do but i was wondering if you could give me a step by step instruction on how to do all this (like i said im very new to this sort of thing) =/ im sorrry
Click to expand...
Click to collapse
i'm no rocket surgeon but here goes
download rom
place on root (no folders) of sdcard
power down phone
boot into recovery with home and power
scroll down to recovery console
enter command above to format ext3.
then type reboot recovery to boot back into recovery
select data wipe/factory reset
press home to confirm
now select flash any .zip (assuming you have cyanogen's 1.4 recovery image, if not, name rom to update in windows or update.zip for mac/linux prior to putting on phone, then select apply update.zip sdcard instead of any .zip)
hit home after selecting your rom (again 1.4 recovery)
when it is done flashing select reboot
happiness is yours.
yes you must wipe the phone and your ext3 partition since you are coming from hero to AOSP (cupcake/donut) (opposite applies as well).
mrxkpex said:
Hello everyone! Last night I spent about 3 hours installing the JACXHERO-v2.6.6 rom onto my Tmobile G1 using a method from unlockr.com (http://theunlockr.com/2009/08/22/how...g-best-method/). Unfortunately, it runs extremely slow right now.
For example, when i press home after sending a text message it goes to the HTC screen and simply sits there for about 30 seconds. At first I thought this was due to the weather widget updating but even when I took it off it still does this. Another thing is that it will sometimes take 10 seconds to switch screens when i slide my finger.
I know I am still new to this and realize there are some veterans on this forum that have a lot more experience with this. Can anyone please suggest to me what to do?
The bottom line is, all i want to do is run a stable and lag free (or fast) Rom.
Thanks guys!
Click to expand...
Click to collapse
dude youre using such and OLD OLD OLD hero rom... a rom thats is getting much hype nowadays is hero2 1.5.1
hero in its current stages arent lag free. no rom is lag free... you will experience some kind of lag always anyways.
brian_v3ntura said:
dude youre using such and OLD OLD OLD hero rom... a rom thats is getting much hype nowadays is hero2 1.5.1
hero in its current stages arent lag free. no rom is lag free... you will experience some kind of lag always anyways.
Click to expand...
Click to collapse
i still have jac 1.4 on my computer. i thought about flashing it once just to see how HUGE the improvement in hero roms has gotten
[ROM]JACxHEROSki-v2.1 - Experimental
...that's all I have to say.
SG_Shadow said:
[ROM]JACxHEROSki-v2.1 - Experimental
...that's all I have to say.
Click to expand...
Click to collapse
So are you saying Cyanogen's "experimental" builds aren't fast? If you were following the Hero scene closely you would know that every Hero build is "experimental," some just happen to be faster than others.
I recommend flashing one of the new ROMs such as Hero2 1.5.1, Modaco 2.2 (requires some tweaking to get flying), JACHEROSki 1.7r2(older but more stable/fast), or Drizzy's 1.4r1
NOTE: this is just my OPIONION
Cyanogens, is based on doughnut, so it looks the same as cupcake etc.. with custom enhancements (personally i think its fantastic)
The hero roms (in my experiance) its a case of reading the threads and trying a few to see what runs / works best for you
thanks a lot guys! it really helped! i have one quick question though
a lot of you have been recommending hero2 1.5.1 rom and i just watched a video on youtube for it where the guy was explaining how fast it was lol (and from the looks of it his seemed to have no lag when scrolling from left to right a bunch of times even with widgets)
my question is: is it really much faster and more stable? there are so many times where i'll be in my messages or something and i press the home key and theres a loading screen for like 30 seconds...i used the unlockr.com's method to partition my sd card to ext3 and what not
if i download and install the new hero rom, what are some suggestions on how to make it run faster?
people keep mentioning 96 mb partition or something like that and i have no idea what there talking about or how to do it
also, just in case i want to go back to the original os that came with the phone, how do i do it?
try moving the cache that is the first thing to do with hero there is a lot of maintence that go along with hero
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Dr. Falken said:
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Click to expand...
Click to collapse
a bit noobish myself, but I think I can answer a bit regardless, anyone feel free to correct me...
1: if everything is working, great! if you dont feel comfortable, and dont mind resetting everything up, go ahead, do it again, cant hurt. whenever reflashing/new flashing, Dont Forget to make a nandroid and wipe! (and you can rename the backups in USB disk mode so you know which ones are what, otherwise go by the embedded date in the autogen'd title. in the nandroid folder on your SD card btw)
2: as far as I know, leave it?
3: HUGE fan of Darchs work, cant go wrong... keep in mind it does not have VisVoicemail in it, fix flash needed.
4: reboot into recovery, make a nadroid backup, WIPE!, flash the new one according to cookers intructions! done! (if ya dont like it, buggy, nandroid restore back to your last good one you did like!)
well I reinstalled the rom and wiped first...and everything is running way smoother than last time. I don't know what in the world happened or what was going on but I'll take it as it is
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...
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Magicnet2 said:
Hi guys, I have an old G1 at home that I've been using as a time killer, to play chess and some music. I want to try changing the ROM on it, because I have some problems with it, but i'm not sure where to begin. I'll give a quick rundown of the phone's problems and what I'm trying to do. This is an old machine I bought for my dad awhile ago. It's not been used for some time and I wanna to do something with it. It has a lot of problems which I don't understand. For example I cannot connect to google nor through a data plan on a simcard or through Wifi. I've seen threads having some tips on this but none helped. Same problem with some applications - facebook, teamviewer and so on. They just won't connect, although wifi works fine with the browser, so I don't know what going on. There are other problems as well and I think it's running slower than it should because it won't even manage to do stuff a generic G1 should - videos have to be heavily converted to even run - trying any video player is useless - it'll lag as hell. I have to convert to a specific audio and video format with lowered fps, then it runs ok, but still only using the generic video player. Anything else will just become a comic book.
Anyway - this is a phone I got off eBay and it already came rooted and with the Super D rom loaded (kernel 2.6.29.6-SuperD) So because all the problems I want to reflash it completely to try find out, whether it's all hardware related or the rom's unstable... Now, because it is already rooted and I'm new to this, I don't know where to start.
I have looked through a few rooting/flashing guides, but my problems is: I don't know whether I need to do it all, or can skip a few steps, because it being rooted already. For example whether I need to downgrade anything again, or not before going on. My first important question is, is there a point in flashing anything higher than android 1.6? As the phone is very limited with it's resources, I'm not sure, whether for example flashing the 2.2 froyo CM rom will do any good. Secondly: there are several different guides out there and I don't know which one is good for me. I believe I tried the one click thing once, but it didn't work then, but not sure what was the problem. I presume it is because I either didn't have to do all of it, or I didn't do something else I was supposed to.
So all in all, if someone could point me to a good guide, that would take in account the option, that it already is rooted and I just need to change the Rom, it would be greatly appreciated.
Click to expand...
Click to collapse
First thing I would do is just factory reset it through recovery (power on while holding home) and see if all works after this. Super d is for sure one of my favorite donut ROMs and it shouldn't be having the issues you have.
If that does little or nothing than write down all info from bootloader (power on while holding camera) here and the version of recovery you have (written in recovery screen)
Sent from my Nexus 7 using Tapatalk 2
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Magicnet2 said:
Hi. Thanks for the quick reply. I've already reset it multiple times, but it didn't change anything. What most angers me, is the Wifi issue (because I know my dad has been using his dataplan and it worked fine and when I tried it later, it just didn't work anymore) and the video thing.
As for the info:
Hboot-1.33.2005 (Drea11000)
Clpd-4
Radio-2.22.23.02
Recovery is ClockworkMod Recovery 2.5.0.7
Click to expand...
Click to collapse
Yes it is strange, try finding a ROM called donut by Laszlo, search is down right now but it should be within the first five pages or so in developers thread. Put on sdcard along with this
http://www.androidfilehost.com/?fid=23212708291678371
First flash super wipe in recovery and then flash new ROM
If it all does not work still we will go from there
Sent from my Nexus 7 using Tapatalk 2
Right, so I've got some new info on this. I wanted to go reflash, but just for the sake of it, I re-wiped though recovery and nothing changed. then on the second time, the market suddeny started working through wifi, which it has not for the past few months, even after 3 or 4 wipes. So it started working, but the signal kept failing. It found the first application, downloaded, installed, then "network problem" so I reflashed using the files you mentioned. It worked beautifully on the first fly, for which I am grateful. This was my main concern - I had no idea, whether I needed to change the radio or bootloader or anything prior to trying to flash the rom. So the rom works nice, the market and facebook and teamviewer do connect now using wifi, but I keep loosing the signal. Better said - he stays connected to wifi, just that the applications keep throwing network errors and loose connection. So I presume, it will be either hardware related, or I was wondering, if a change of radio might help... Secondly, I keep getting one more problem I had with the old Rom and that is - when using ES File explorer, when I close by pushing the back button, it closes and then an error says it stopped working and needs force closing. Wondering how this kind of error can transfer between different Roms. Again - posibly hardware related? I don't know.
Anyway, the rom works nice, so I'll try it out and see if it's better than the previous one. One question though - when flashing to a different Rom, do all of them have specific requirements for radio and bootloader and recovery and so on, or is the setup I have ok for flashing anything, that is suited for the G1?
EDIT: One more thing I just remembered. The Superwipe, as I read the description, was supposed to wipe everything + the SD card as well. First of all I noticed that it took just about a second or two, which I thought was a bit too quick, but the SD card was not wiped at all, so I'm thinking, that theoretically there could be a file on there, that causes the problems, that have transfered from Rom to Rom, as it was not wiped at all. I'll reformat the SD card, superwipe it, reflash the Rom and see what will happen. Will post the results first thing tomorrow.
It only wipes ext partition not fat32
Only newer ROMs will require a different bootloader/radio, which also will give you more ram so it is preferred. See ezterrys post on the 2708+ update or read the through the thread below this on where I discussed the benefits of upgrading with another dream user
Sent from my Nexus 4 using XDA Premium 4 mobile app
Right, so from what I see from the other thread of yours, CM5 should be a good Rom to try. I will definitely wanna go there, cause while the current Rom seems a bit better than the Super D, it seems it uses up more memory - can't install as many apps as before and I'm keeping it pretty low on apps. And I definitely want to see, whether it will improve any of the lingering problems I've been having, or whether it'll be worse. So judging by what you told the other guy, I already have the right bootloader as I have the 2005 with fastboot enabled, but I'll have to update the radio. Here's what I'm not sure and that is, which to choose. Should I stay with the current SPL and get the same radio the other guy had (RADIO-2.22.19.26i) or should I go straight for the 13d SPL with radio-2.22.27.08? I would say, for now would be safer to stay with current SPL, update the radio and then flash Rom + Gapps and see what it does. Plus if I remember right, you said that to get the ramhack I need the 13d spl, which doesn't support fastboot...
You got it all, well you don't need to change radios, the one he has is a Europe version, yours is more us. Both work fine for cupcake, donut and eclair ROMs. You can try out the other if you were getting poor reception but not needed
Cm5 will work fine for you as of now, just full make a backup, wipe, superwipe, fastboot -w whatever, then flash ROM, then gapps then reboot
The ram hack is awesome but so is learning fastboot. I do recommend you at some point upgrade to the .13d SPL but I think its a good idea to flash a few things first and be comfortable before doing so. If you have issues having fastboot is helpful in fixing things
Sent from my Nexus 4 using XDA Premium 4 mobile app
Ok. So what I did is partition the SD card using the nice "Mini tool partition wizard" and went for a 250 MB ext4, made a backup, left the radio be so far, wiped, flashed the CM5 and Gapps and I have to say I'm impressed at how swift the Rom works. It appears to be generally faster than both the SuperD and Laszlo Donut Roms. I have been testing it only a short while yet, but the wifi, although it shows constantly weak signal (one or two lines), it hadn't lost connection yet, which gives me hope and the apps2ext seems to work perfectly right away. At least I'm able to move them around and it installs straight there, without any failure so far and the apps work so thumbs up.
This deserves a big thanks to you for the supplied info. Before I wrote this thread, I was about to try one of the long guides - which would take me through downgrading and everything - you saved me a lot of stress man I'll play around with this and will try going for the ram hack a bit later. I'll let you know any bugs I notice...
P.S.: You were right to suggest getting familiar with fastboot and adb - it's a great thing and it's good to know I've got it set up and running fine.