I have an unlocked, rooted, Rogers Dream I bought from a friend who had flashed it with the G1 T-Mobile firmware. It's using the EBI0 radio and firmware 1.5 and no Rogers Mandatory Update(he stopped using this phone prior to the lockdown). I am using it on the Telus network so I've no worries about the update either.
It's slow as sin and buggy as two hells. I was told cyano runs a heck of a lot smoother.
However, I've never flashed an android phone yet and I don't quite want to brick this one though experimentation. Much of the guides I was able to find seem to be how to flash cyano on a stock Rogers or a stock G1 and I'm not sure which one I should follow as the guides on the cyano site said the hardware may be a tad different on each. I've done at least 1 hour of searching on this forum prior to posting but I apologize if I missed something as I know it can be annoying when the "new guy" asks something 50 people ahead of him asked before.
I was hoping to get some advice on what's the best way to upgrade to cyano from 1.5 on this phone would be, considering I'm a newb and all.
Here Is Cyanogenmod Guide Super Easy Steps : Cliick Here
Next Time Search =D
Androiid=D said:
Here Is Cyanogenmod Guide Super Easy Steps : Cliick Here
Next Time Search =D
Click to expand...
Click to collapse
I saw that guide, but is it safe to use it on a Rogers phone using the G1 firmware?
Also turns out the firmware may not be stock G1, though it's definitely branded T-Mobile G1 on the firmware(Rogers on the splash screen)
Model Number
T-Mobile G1
Firmware Version
1.5
Baseband Version
62.50s.20.17U_2.22.19.26I
Kernel Version
2.6.27-TheOfficial-00399-gc7f8bce
[email protected] )
Build Number
killa-user 1.5 CRC1 150275 ota-rel-keys,release-keys
The funny naming(killa-user? @abomb?) are what's throwing me off.
I guess what I want to know is if it's still safe to following the instructions on that wiki page.
Also, since it's already rooted, if I should just start from the step marked "Cyanogen Recovery Image".
And finally, do I still need to install the 2.22.19.26i radio update from those steps if my radio is listed as 2.22.19.26I?
Acck, here I go spamming my own thread...
I found this link one one thread:
ech tee tee pee colon slash slash wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
Would these be the preferred steps given the info I pasted?
Update:
I followed those instructions. Turns out the phone already had Cyano Recovery 1.4
I did a nandroid backup first and proceeded to do a wipe and install all 3 zip files(signed-dream....ota-14721.zip, update-cm-4.2.14.1-signed.zip and bc-4.2.14.1-ebi1-signed.zip, in that order )
Everything went according to those instructions but on the final reboot(after it rebooted once already to recover mode), it hung at the Rogers logo for 25 mins. I turned it off by yanking the battery. I did a nandroid restore to try it again(as they suggested if it hung on the T-Mobile logo) but it just hung there again for over 30 mins until I yanked the battery again.
The restore at least gets me back to my 1.5 so I'm not phoneless(whew!). Any ideas why the update won't work?
Well, my impatience definitely got me doing experimentation instead, but alas, I got it working
Turns out it was that last zip(the radio kernal) that was breaking. I installed only the first two and, voila, it works
And it's soooooo much faster now!
I hope this at least ends up helping someone else with this issue
Background: Switched to backup battery pack, lost internet service. Rebooted a few times, then had no reception at all.
I backed up and wiped, but nope. I'm guessing the SIM card's damaged? (happened before)
So I need to call Tmobile. Before I call Tmobile, though, I need to downgrade and unroot. So I went back to RC 29 with DREAIMG.nbh as usual (done this before. kiiiiinda getting sick of the g1 now.)
Now I have original SPL and have RC29. Also have RA recovery, but I can reapply dreaimg and get rid of that.
Problem: I need to upgrade my phone, since it'd be kinda weird if I called and I said I was on RC29. Thing is, either cellphone reception is needed for OTA updates (that is, non-wifi internet connection), or they're simply not supplying OTA updates for the 29.
I guess I need to manually update, but that would require root (which I have, but need to get rid of before I call t-mo). If you have a way to update an RC29 to 1.6, or have a way to unroot without using DREAIMG.nbh, please post. Also might need a link to the standard, no-root 1.6 file.
If there are any questions, or at some point in the above post i was spouting nonsense, please tell me.
Thanks!
I'm wondering if anyone else ever came across this weird issue. I am on the Rogers network with a HTC Dream. I've tryed several ROMs and none make a difference. The issue is, I lose 3G connection and my SIM card gets corrupted. I have a LG GW620 and I used it for a long time and this never happened. What happens is I totally lose 3g capability and I can't get it on any other phone unless I get another SIM card activated. I've had this happen to me twice now and it ONLY happens when I used my HTC Dream for couple weeks it seems. Could this be due to that my phone is using roms or is my phone just mangled? I'm just thinking of smashing this phone with a hammer as it is useless to me if my 3G connection is gone.
Any information would be appreciated.
Thanks
IIf you currently have radio 3.22.26.17, please find and download the 3.22.20.17 radio image and flash via fastboot 'fastboot flash radio-3.22.20.17.img'
The image is on bcrooks server.
Please note the imei-sv is 3 in 3.22.26.17 but 2 in 3.22.20.17, this means if you are a rogers/Fido customer with a rogers branded dream you will be flagged by rogers for not having the e911 rom.. and thus they will disable your data if you have not filled the wavier. To reactive a call to the call center is usually required (preferably on a phone other than the cell in question)
Note the radio has nothing to do with the e911 issue, as the bug was in android not the radio.. so if you have signed the wavier or are not a rogers customer feel free to use 3.22.20.17.. of if preferred downgrade to 2.x via fastboot
(its unknown if the lattest 2.x or the older 3.x provides better signal on the Rogers network .. but the newer 3.x has problems in every rom.. including the official one HTC/rogers forced on everyone, sad since the bug was just in the Java code of one file on the phone in /system.. nothing to do with the radio)
Alright just let me get this straight.
So they are flagging me because of my phone, or radio? I am a Rogers Customer, have been since 2004 I believe. How would I go about getting data to not dissapear on my phone again? I had just bought this phone used and rooted it and put on a custom OS. I'm not exactly sure which radio I have at the moment, but if i update to 3.22.20.17 would that fix the issue if I got rogers to re-activate my data?
What radio do you have now
I believe this one is on there.
Radio Image update 2.22.23.02
So if I update to Radio 3.22.26.17 via Fastboot and call the support line to re-activate my data or w.e that will work?
Not quite that simple your current rom wont work with the 3.x radio as is..
I recommend one of two things..
1) goto http://rogers.com/htcwaiver and sign it.. then call rogers saying you signed the waiver and want data back.. if it fails tell them that..
2) if this is a rogers branded dream and I assume it is unroot to the stock e911 patched rogers rom and start from scratch on android 1.5 .. this is not optimal and I highly recommend option 1.. and you still may need to call after to get data back http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
Huge low blow in Rogers case. Plus I have to call them cause they say my number does not exist when I put it in that Waiver. What a joke in my opinion.
Thanks for the information though. Much appreciated.
Hi all,
I've purchased a Sumsung Captivate from an U.S.A. Best Buy store less than 30 days ago.
I've unlocked it and I'm using it in Italy.
I've noticed random shutdowns and read that my phone should be changed from Samsung/AT&T for this issue (I'm afraid that it is an hardware issue).
Anybody knows if Samsung may change it after unlock? Is there any way to restore SIM locking as AT&T configuration?
Thank you in advance
backtothefuture81 said:
Hi all,
I've purchased a Sumsung Captivate from an U.S.A. Best Buy store less than 30 days ago.
I've unlocked it and I'm using it in Italy.
I've noticed random shutdowns and read that my phone should be changed from Samsung/AT&T for this issue (I'm afraid that it is an hardware issue).
Anybody knows if Samsung may change it after unlock? Is there any way to restore SIM locking as AT&T configuration?
Thank you in advance
Click to expand...
Click to collapse
As stated in numerous other threads, the random shutdown/reboot on official software is very common and would most likely persist even after the swap. Look into installing a Custom 2.2 ROM that doesn't have this issue(I think all Custom 2.2 ROM's dont have this issue)
****BUT*****
READ UP FIRST on the SIM unlocking procedure on 2.2. You may need to back up files from 2.1 before you do it!
geokhentix said:
As stated in numerous other threads, the random shutdown/reboot on official software is very common and would most likely persist even after the swap. Look into installing a Custom 2.2 ROM that doesn't have this issue(I think all Custom 2.2 ROM's dont have this issue)
****BUT*****
READ UP FIRST on the SIM unlocking procedure on 2.2. You may need to back up files from 2.1 before you do it!
Click to expand...
Click to collapse
You're right, I've installed already a custom firmware and just one shutdown happens 10 days.
However, I was asking it because my "30 days" are expiring and if Samsung changes it with a more reliable one it's not bad!
geokhentix said:
As stated in numerous other threads, the random shutdown/reboot on official software is very common and would most likely persist even after the swap. Look into installing a Custom 2.2 ROM that doesn't have this issue(I think all Custom 2.2 ROM's dont have this issue)
****BUT*****
READ UP FIRST on the SIM unlocking procedure on 2.2. You may need to back up files from 2.1 before you do it!
Click to expand...
Click to collapse
I'm not sure that this is true. My first Captivate (which fell into Samsung's reported 'defective' IMEI range) had shutdown issues regardless of what ROM it was running. I swapped to one outside of the range (better screen as well) and I haven't had a shutdown since.
GGXtreme said:
I'm not sure that this is true. My first Captivate (which fell into Samsung's reported 'defective' IMEI range) had shutdown issues regardless of what ROM it was running. I swapped to one outside of the range (better screen as well) and I haven't had a shutdown since.
Click to expand...
Click to collapse
I said I think it is an hardware problem because if they really echange the phone for that IMEIs it may be necessarily an hardware issue for me.
Anyhow, Is there any way to restore SIM locking as AT&T initial configuration?
(I know how to rerstore firmware but I think it doesn't restore the SIM locking..)
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Cor-master said:
Have you gotten a new sim card yet? That needs to be your first step. My captivate did the same thing and turned out the sim went bad
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Yes I have tried a different sim card. I don't believe thats the issue though being that it worked with the same sim after I let the phone sit overnight. From reading about others experience, it doesn't seem that the sim is the issue but more the baseband version and imei information missing.
centro7710 said:
Hello,
I have searched multiple forums for hours today and have figured out what is going on with my HTC Vivid. (It has been upgraded to AT&T Official ICS.)
It was working fine up until yesterday where it was not receiving a signal from the mobile network and the signal icon has an X through it. The SIM card is properly inserted and another SIM card has been tried as well. Looking through other threads it seems like the Radio RIL files may be missing or corrupt. The IMEI number and *#06# code does not show an IMEI number either. The baseband version says unknown. I am not sure what happened as I have never loaded any other ROM on it.
I downloaded the Official RUU ICS upgrade ROM today and tried reflashing it, with no luck.
What is interesting (and the other person who had the radio problem) is that when I left the phone sit off overnight and then turned it on in the morning, the phone connected to the mobile network and I had a signal. When I restarted the phone, hours later, the phone lost connection to the mobile network and that is when I started digging and found the problem with the baseband version being unknown.
Is there anything anyone can suggest? Can I reflash the baseband files or copy them from someone somehow using ADB? It seems like there is where my problem lays. I've searched for ways on how to downgrade from ICS to the official GB stock rom, but it doesn't seem like it can be accomplished.
(I tried downloading the Holiday Cingular version of the GB stock rom but the update failed. I read about the ICS HBOOT version being different and not allowing it.)
Thank you in advance for helping and any suggestions.
Click to expand...
Click to collapse
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
You can get HBOOTS for both GB and ICS via Hasoons AIO kit
Flash the HBOOT, Flash the Image from Cingular GB RUU and I wish you luck!!!
Click to expand...
Click to collapse
I found the download link, but the website says they're updating their drives, so who knows how much longer that will take.
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
centro7710 said:
I tried finding a download link for the AIO kit on the link provided, but I must be blind?
Also, are you saying I should just use the tools within the kit to flash the HBOOT back to the previous version compatible with GB and then flash the RUU GB image after? Can I do that with the phone connected via USB or does it have to be flashed from the SD card? If it has to be flashed from the SD card, how do I go about doing that? If it can be done from the phone via USB, does the phone have to be in recovery mode?
I have tried reflashing the ICS RUU multiple times w/ version 3.26.502.52 and 3.26.502.56, both do not fix the issue. Do the baseband and or radio files NOT get flashed within these updates?
Thanks for the response!
Click to expand...
Click to collapse
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
centro7710 said:
Thanks for the quick reply.
Your thread was the one I saw earlier with the simliar problem that I am having, only I have not loaded any custom ROMS. The phone just stopped receiving the signal the other day. I am still waiting for the download website to become available to use the tool to perform the flash of HBOOT, however, once I do that, will that erase the ICS rom from my phone? If so, what steps do I have to perform to get it in a "download mode" to accept the AT&T GB RUU? I'm a little confused on that part.
I read your first thread and I am a bit confused on exactly how you were able to correct the baseband/RIL issue (which I am assuming is the root of my issue). Do I have to extract some files from the RUU executable? Are the commands you provided to be used in ADB? I am confused as to what to do with [setprop ro.baseband 3.26.5XXX (<--- mainver: in android-info.txt in RUU.zip)] from your post. If that command is copying a file or just setting information (almost like as a registry setting within Windows) to point to the file or set a version number. Also if the XXX needs to have a certain number.
I thank you for your time and am trying my hardest to understand what to do to accomplish these steps.
Click to expand...
Click to collapse
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
centro7710 said:
I did find the extracted files within the RUU executable and found the rom.zip which included the .img files among other files I assume needed as sources to flash the phone. I see a radio.img file would I be able to do anything with that?
Thank you.
Click to expand...
Click to collapse
And I have a question, if the radio/baseband files are included in the RUU flash, what is happening as to why it is not being reflashed, or if it is being reflashed, why it is disabling the mobile network and providing an Unknown version to Baseband and clearing the IMEI number?
ayulatins said:
For any issues downloading Hasoon AIO tool, please use his thread (earlier provided).
Yes, use the AIO tool to flash GB HBOOT or read the SUPERGUIDE
and obtain rom.zip from the Cingular RUU
I don't know how to flash RUU via Recovery [email protected]@@!!!
I'd advice you follow my first solution here!!!
Click to expand...
Click to collapse
Here's where I am:
I successfully unlocked my bootloader, downgraded to GB, rooted. Tried to gain root access through adb terminal but it was not working properly.
I relocked my bootloader. Installed the ICS RUU AT&T ROM update. Unlocked my bootloader, rooted.
I see the commands you ran in your previous post. I am also receiving the same message of N/A when running the getprop ro.baseband
I tried the second command setprop ro.baseband 3.26.5XXX and then restarted the phone. I have tried it as posted, and also with swapping out the version that is located in my android-info.txt file: 3.26.502.56
Still no luck with setting the baseband version. IMEI still is cleared out.
Am I doing something wrong?
ayulatins said:
I had a similar problem and thought I solved it, but I later realised all my "solutions" didn't bring back the network but coincided with its reappearing cos no same "solution" worked more than once.
It's a very weird problem as the network shows up once in a while and when I'm using Mobile Network for Data, my phone hangs again and the IMEI, Network, baseband disappears on reboot...till further notice. I gave up trying and concluded it's either a bad modem (hardware) or something AT&T knows about!
Click to expand...
Click to collapse
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
ayulatins said:
Please see my initial quotes above...
All the previous steps I took were only a coincidence (not proven to work)!!!
We may need to contact AT&T to be sure its not a lock IMEI (and I'm wondering why it would be) or an experienced Dev
Click to expand...
Click to collapse
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it.
centro7710 said:
Hey thanks for all of your suggestions. I contacted AT&T the day everything happened to see if it was on the block list. They said no. I tried multiple things including trying to re-flash the radio, but I was getting a signature failed error that I could not get around. I really think that's what the problem is. I gave up and ended up selling it, as is, on ebay instead to get a few bucks out of it and getting a new phone.
Click to expand...
Click to collapse
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
ayulatins said:
I really wouldn't mind selling mine too if I get a buyer. I'm just tired of all the troubles and no dev is willing to help.
Click to expand...
Click to collapse
Exactly. It was my sister's phone. The sh*tty thing is we bought two off of ebay at the same time, 1 for me, 1 for her. Well, her phone was not in the box (either never shipped or stolen) so I had to file a claim through eBay which took 3 weeks to get the money back. Meanwhile, I gave her my phone (which is the phone in reference) to use instead. I bought her an iPhone instead now, along with purchasing one myself. I loved Android, but the bugs and fragmentation is getting too much for me to handle.
Dude, if you don't have an IMEI showing up, something is WAY wrong. That goes beyone the RIL not working... The RIL is probably fine. If your phone doesn't have an IMEI somehow, the cell towers are NOT, NO WAY, NEVER EVER going to register your phone on their network. You can put a billion SIM cards in there, or flash a billion stock ROMS, and if you don't have an IMEI, you will never be able to connect.
Something is probably corrupt or broken in your firmware or the hardware itself. I think your device is probably screwed.
My advice, is follow the steps to put your phone back to stock (including changing the bootloader message back to **LOCKED** and S-ON), and get it back to the phone company. They will be able to tell something is boned on the phone right away since it isn't displaying an IMEI.
Sorry to be the bearer of bad news and for your many wasted hours... But on the plus side, you now know a LOT about flashing and how your phone works now
Good luck with everything man! Hope they get you up and running soon!
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
anyone got the Radio.img?
inick73376 said:
I have the same problem as the OP but I have a IMEI showing up and a Basehand But won't connect to AT&T or anything they resent me a Signal & everything it shows a X with no bars it happened after I did a Factory Reset
Click to expand...
Click to collapse
That's weird..you try creating the apns again? I don't see how a factory reset would do that. Try toggling airplane mode too
Sent from my De-Sensed HTC Vivid using xda premium
I am currently having the same issues right now, it works if i leave the phone off for 1 hr it will work until i reboot then its down again, tried every thing possible, airplane mode will crash, reflashing the radios from gb and ics does nothing, setprop does nothing really. from this point it feels like a hardware issue.
sorry to revive an old thread, i just wanted to know if anyone came across this issue and had it fixed
i will get a log to see if there is errors showing up
Return it.
Sent from my HTC Holiday using Tapatalk 2