My girlfriend has the Rogers HTC Dream, while I have the T-Mobile G1.
I was able to properly root both phones (although I had mine longer) and I have tried several different roms on both. When we were both running TheOfficial Rogers 1.8.4 and I think 1.9.1, everything was ok. TheOfficial AOSP 1.6 came out, so I took the plunge and tested it on my phone. It was fine.
She kept complaining that her phone was slow and non responsive at times, and indeed it was. I tried flashing the same TheOfficial AOSP 1.6 on her phone and did a wipe. I believe her phone was still non responsive at times, although I can't seem to remember exactly what it was this time.
I then proceeded to install the latest Cyanogen because I was curious and hoping that it could resolve the problems. -My amnesia kicking in again.. wtf?-
I decided to go back to TheOfficial AOSP 1.6. I do the wipe, flash the base rom, then the expansion, then reboot. On first boot, it connects to the GPRS fine. Connecting to the internet will cause the phone to hang. Only way to use the phone is keep it from connecting to 3G/Edge. If I reboot the phone, sometimes it gets stuck on the Rogers screen. When it does boot, it won't connect to GPRS. The only way to use her phone is to wipe and do a fresh flash. Then I won't be able to reboot or else I have to flash again. I have reflashed and rewiped this rom several times already and it's the same.
Anyone know the reason why? I have the correct radio and spl flashed. I have no idea why this is happening. I have flashed my T-Mobile G1 many, many times and, well.. she's using it now. I'm going to try Dwang's rom to see if the same thing happens.
So far it worked. I'm not getting any force closes. I can't figure out why I can't install TheOfficial Donut AOSP on this phone. Dwang's rom doesn't come with terminal or maps. I'm not sure if it's supposed to be like that. I tried the Google Navigation update mod and for some reason that just restored the normal Google Maps on her phone. I'll try it on my own phone later. I'll just leave it at that and won't update anymore unless someone can figure out for me how to install TheOfficial Donut AOSP.
Bye.
Hate to ask you something you might have answered, but are you sure that you have used the EBI1 radio image on the Rogers Dream?
Related
Is anyone else having this problem?
I've got a Rogers HTC Magic, and whenever I've tried a ROM with Android 1.6 or greater (I've tried 3 or 4) the accessing the camera will cause the phone to reboot itself.
It doesn't happen the first time I use the camera, but it does the second time and consistantly.
Does anyone else have this problem?
1.5 ROMs are fine. I'm currently using cursorsense and it's not an issue but at some point I will want to use a newer version of Android.
I have the same problem :x
Relash the rom. If you are using any of the legal roms (cyanogen/superd) flash the base before the rom. remember to wipe before starting.
I've tried cyanogen 2.1 test2 and Smoki both causes reboot when using camera apps (barcode scanner, google goggles, fxcamera, ...).
It doesn't reboot always tho like 1/3 times i use one of these apps i get a black screen and then a reboot.
Im using CursorSense now and all the camera apps work just fine :s.
Always did a wipe before flashing the roms.
Known issue. Been dealing wirh this for a long time on my Rogers Magic. I think the trouble is the devs dont have this model, and no one has submitted useful logs. http://code.google.com/p/cyanogenmod/issues/detail?id=792
Ok so I've searched up and down and can find nothing so far. Here's amy Phone specs
Phone: Rooted G1
SPL: Danger SPL
Radio: 6250S.20.17U_2.22.19.26I
ROM: CyanomenMod 4.2.14.1
Ok now whenever i flash any rom on my phone whether it is super D, htcclay or cyanogen I get no service and just an x next to where my signal bars are. When I go into settings it under the baseband version it just shows unknown. The only way I can get things back is if I restore from nandroid backup of version 4.2.14.1 i had. Even if I try flashing version 4.2.14.1 fresh it does the same thing, no signal/service. Whenever flashing roms I always wipe multiple times before and that does not work. I try flashing the radio beforehand then flashing the rom that also does not work. I've followed numerous instructions to the letter in the development section for flashing roms but none seem to work. The roms ALL install perfectly but I just get NO SIGNAL after the install. Can anyone assist and tell me why this is please.
Also if I try to flash the new G1 radio 2_22_23_02 it doesn't flash at all. It will install when in the recovery mode and when I hit home+back to reboot it shows the htc logo for a quick second then disappears. When it restarts in recovery mode and I boot the phone up again it still has my original radio. Any assistance is appreciated. I've searched and can find nothing on my particular issue.
I'm having the same problem, except I got there a different way. I was rooted on JF 1.51 and decided to unroot. I flashed the original G1 bootloader and then loaded DREAIMG.img. I waited for the OTA update, and when it did, that's when I had the problem. I've tried manually updating to RC30, RC33, which work just fine, but as soon as I install anything higher than that, the problem starts. I do not know if the unknown baseband version symptom existed with any of these other attempts. Also, a force-close message for com.android.phone repeats endlessly. I tried to check the APN, but when I try to click on Settings -> Wireless -> Mobile networks, it won't open.
Phone: G1
Firmware: 1.6
Baseband version: UNKNOWN
Kernel version: 2.6.29-00479-g3c7df37; [email protected]#19
Build number: DMD64
One last thing: As I was trying things earlier, I started getting a "No SIM card" error so I went to T-Mobile today and got a new one. I don't know if these two things are related or not, but thought I would mention it.
have you try do update Radio??
Do you mean in addition to the OTA update? No. I loaded the DREAIMG file, and then updated with
1. signed-RC30-from-RC29-fat.1582cace.zip
2. signed-PLAT-RC33-from-RC30.zip
When the OTA comes, that's when the problem happens, but I have not tried to update anything after the OTA installs.
I thought that the issue might result from updating too much at one time (e.g., RC29 or RC33 all the way to Donut), but when I then try to update to Cupcake with signed-kila-ota-148830.de6a94ca.zip, then the phone gets stuck in an endless loop on the Android screen. No matter what I do, I can't upgrade above RC33.
I just had the same thing happen although my methods were different.
Basically there is no baseband which means (I think) there isn't
going to be any network activity.
My problem is much worse I'm afraid.
I swapped the Phone.apk from my system/app location,
grabbed another Phone.apk (assuming it was the dialer) because
I liked the theme...so I swapped, rebooted and bam, FC's every second
and then zero network activity.
So I had to use wifi, downloaded rom manager again, and root explorer
and had to reflash the base band...It is flashing right now, and I'm just waiting.
Clockword recovery was borked so I used Sprecovery.
SigmunDroid said:
I swapped the Phone.apk from my system/app location,
grabbed another Phone.apk (assuming it was the dialer) because
I liked the theme...so I swapped, rebooted and bam, FC's every second
and then zero network activity.
Click to expand...
Click to collapse
Phone.apk is the dialer, I swap mine out all the time. However, you have to make sure that it's compatible with your rom (i.e. similar framework, same build as yours, so if you have donut, only donut phone.apk will work)
Are you sure that you grabbed it from an actual rom and not from MM theme which has only drawables?
borodin1 said:
Phone.apk is the dialer, I swap mine out all the time. However, you have to make sure that it's compatible with your rom (i.e. similar framework, same build as yours, so if you have donut, only donut phone.apk will work)
Are you sure that you grabbed it from an actual rom and not from MM theme which has only drawables?
Click to expand...
Click to collapse
Hey man.
Yup, I'm sure, however when I did the search I didn't think it would
link me to a different forum since I'm running a Moto Droid 1
with BB v0.4 The dialer for that ROM is in contacts.
Anyway my phone technically died.
Was resurrected and now I'm running Liquid's Tangerine Frozen Yogurt 1.4
(which is the fastest/snappiest and most responsive ROM I've ever tried!)
It's also the 2nd ROM I've tried but still.
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
I started having this same issue after installing incredible 2 v2.01 and trying all radio with that. Then didn't like the Rom because still buggy, so I went with the original unmodified GB leak and my 3g speeds were gone, kept getting 1x, and no more then two bars. So my solution was to download the RUU in the stock Rom thread. I think the software that installs these roms have yet themselves to work correctly. I don't think they properly format/wipe the phone correctly. After the stock install I'm back to normal with nice speeds and four bars.
Stock 7.28 radio as well.
Add: In the case of a radio hboot doesn't seem to be over-writing the old radio correctly, maybe.
Yes flashing the RUU back to the stock ROM fixes the 3G problems but after doing that you can reflash back to another ROM without a problem. I had the same problem too with a custom ROM the first time but after reflashing the RUU I had no more 3G problems with any of the 3 ROM's I have flashed since.
Agreed - as long as you RUU you should be good to go.
Its odd you would have a data issue with that port though. Its still a Verizon based port and in theory you should be able to #228 with no issues.
There have been times I have tried to #228 and it just wouldnt take until later on (few hours) and when my gf came to see me this week (cross-country trip) she couldnt #228 right away either.
I have noticed that since I have updated CWR the actual functions in CWR take longer to process. Dont know why.
Every unit is different and will yield original results. Dont let this sway you away from flashing away.
I wish there was an actual stable custom, would be nice, and great work done, hats off to everyone, I can only imagine how time consuming it is, but I continue to go back to stock. I however will be looking out for the most stable GB with 2.1.
Sent from my ADR6300 using XDA Premium App
So when I first rooted my phone I put Fresh on there. I installed the ROM and the 2 radio files. I then got the 3d and gave the evo to my gf, but fresh was very slow for me so I installed the CM7 ROM.
CM7 was very buggy for her, especially since she was new to Android I decided Sprint Lover's ROM on there and flashed a newer update on it since.
The problem is that she has been having problems with 3g. She has so many problems and errors with 3g data. It shows that she has 3g, but she gets errors when she tries to access the internet.
My question is, how can I get it back to stock or a nice rooted stock rom to try and fix this problem? Do I just flash a stock rom? I'm guessing the fresh radio's might be messing something up. If there is a simple solution to this without having to do a full erase I'm sure she prefers that, being that we've fully erased her phone like 4 times already, lol.
Thanks guys.
Get the Sprint Lovers all-in-one package from here: http://forum.xda-developers.com/showthread.php?t=830153
It's flashed through hboot (it's a PC36IMG.zip) and will flash not just the rom but also the radios. This will wipe everything.
Alternately you can go here http://forum.xda-developers.com/showthread.php?t=715485 and get just the latest radios and flash those. Flashing this will not wipe everything.
If the problem is with the radios then that should fix it. If it doesn't, then it's likely that the issue lies somewhere else.
thanks, just installed the new radio's. Will see how it works.
I would definitely just get the app mybackup root and back everything up apps/data , sms etc.. Then just restore everything after you flash a new ROM.
Then just do a fresh install of what ever ROM you want then test out different radios till you find the best ones that work for you I'm on old radios because the newer ones didn't work great for me not all evos work the same .
I hope that helps you out some.
Sent from my PC36100 using XDA App
I got simalar problem like u.
I installed new radios, try different roms like MIUI, CM6, CM7, Miks, Minn, OMJ's, etc...... finally I go back to stock rom but still got the same problem.
I almost crazyy
the phone never got 3G signal, it only works 1G no matter what I did.
I've reserched couple days but looks like nobody got my problem.
now I fixed my problem btw... well I'm not sure this thing works to u or not
anyway try it if u still got 3G problem.
*I don't even remember where this posted originally,,, somewhere this forum or not,,
huge thanks to original author btw
download 'MSL reader' at market n get the numbers. it's 6 digits.
go to your phone and type ##3282#
tap 'edit mode'
type that 6 digits from MSL reader
tap 'data profile'
open menu n tap 'restore'
then the phone will be reboot.
when booting is done, your phone will start resistering to network.
after that, if something popup n ask update (mayb PRL update), 'cancel' it.
mine works perfectly now.
hope this work to u.
ok thanks, i'll try it out. I do get "3g" at the top though, but always get an error while trying to retrieve data.
Also, what files in the SD card are necessary? Is there a list? I think there are so many junk files in there taking up space, I don't know whats necessary and whats not.
Please help slow EVO 4G after flashing Sprint Lovers All In One
Obvious Noob here.
having issues with my Evo 4G after flashing Sprint Lovers All in one
phone seemed very fast immediatly after flashing SL but since then has become just overall slow.
in fact, i'm downloading an update to ROM Manager right now (a 2.27MB file) and it's taken literally 20 minutes to get to 75%. it's painful!
when i go in to manage applications...says "computing" on space, data and cache etc.
before i flashed SL all in one i ran factory reset 3x in a row prior to flashing - i did NOT re-format my SD card but had it removed (after unmounting).
Should i try to wipe and re-flash or just go to CM7? Are there any things i can try before re-flashing or moving to another rom? Please help..
thank you OB1B