I've got an ADP1, and I'm trying to upgrade to JF's v1.5 image. I started from JFv1.43 and radio 1.22.14.11, which seems to work fine.
From there, I flashed the new radio image, wiped, and flashed the JFv1.5 image. I copied image files onto the SD card root as "update.zip" using the USB cable into a booted Android environment and then flashed them using Alt+S on the (JFv1.43) recovery screen.
Here are the files I've got:
aeecdb49b74a0d4bb67f9d8af70c1889 ota-radio-2_22_19_26I.zip
8d78b985316ec77f81c71cab0eeb9f27 JFv1.50_ADP1.5.zip
On the first boot after flashing JFv1.5, I get three bars, can go through the sign in wizard, and can surf the web. In the phone info screen, it shows the correct baseband version. On second and subsequent boots, I get absolutely no signal (zero bars with an X) and in the phone info screen it shows the baseband version as "unknown".
Reflashing the radio image has no effect with either the 2.22 or the 1.22..11 radio. Reflashing the JFv1.5 image makes it work again for a while, but breaks again with the next reboot. This isn't specific to the JF image either - Hv1.5r3 gives me the same behavior.
Further tests:
- JFv1.43 with radio 2.22 works fine.
- The HTC ADP1.5 release breaks the same way. In this test, web connectivity broke before the first reboot; I had gotten the same result in one of my JFv1.5 tests too, so the reboot may not be the key thing.
Any ideas what I might be doing wrong?
MD5sum
I can confirm that the MD5 sum of the JFv1.5 image is correct. I just installed the two images, like you, and it works fine. (After entering my PIN, it cost 10 seconds before I have bars)
Did you check the MD5 sum of the images after you uploaded them with the android/recovery shell? I don't know if the recovery will detect a corrupt image, but I always check it just in case. I downloaded the image over 3G.
I have a T-mobile G1.
tomvleeuwen said:
Did you check the MD5 sum of the images after you uploaded them with the android/recovery shell?
Click to expand...
Click to collapse
In trying to test this, it magically works now.
I hate it when that happens - if a computer decides to magically work by itself, that means it can decide to magically break again by itself whenever it wants to.
Specifically, I applied the JFv1.5 update over JFv1.43 without wiping this time and I'm now unable to replicate the unknown baseband issue by rebooting.
Edit: Apparently by "works" I mean "google maps and the market both don't work at all". But that's a new problem. Whee...
In playing with the JFv1.43 to Xv1.5 (no wipe) upgrade path, I ran into a couple more issues. That path would consistently result in no working market, and I could only get Google Maps to work on Hv1.5r3.
But I've come up with a new strategy that largely seems to work:
Wipe
Install JFv1.42_R33
Wipe
Boot, Login to Google
Install JFv1.5
When I do this, I get signal and the market works. Google Maps shows a broken icon with the class name and won't launch, but I've basically got a working v1.5 phone.
Apparently all of this stuff just works for everyone else, but I figure I might as well document the fact that it took me two days to install a point-release update on my telephone in case anyone else is equally incompetent.
Edit: Apparently I hadn't installed the new radio. Doing that last doesn't seem to have broken anything.
I managed to solve the Google Maps thing.
I deleted these files:
/system/framework/com.google.android.maps.jar
/system/etc/permissions/com.google.android.maps.xml
/data/data/com.google.android.apps.maps
/system/app/Maps.apk
Then I copied the stuff under /system over from H1.5r3.
I'm relieved - finally Android acted exactly the way I expected it to.
Update 1.5 + radio
Hey, I am also having a problem with updating my g1 when I update to the 1.5v and new radio. When I updated to the 1.5v phone was not allowing me to make calls. I updated the radio and then it started acting crazy. No gps, internet, when a phone call come in it automatically went to speaker phone and none of the buttons would work. I couldn't bring up the dial pad or get to the menu. I had to go back to the old radio and old 1.43adp1.1h build. Has anyone gotten this to work and is there a certain order to update and when to wipe. Also, do I need to have a certain build in before updating and could the copies of the radio and build I got be bad. They came in on my jf updater and downloaded ota.
Related
Hi,
I followed this guide for rooting and JF'ing my G1: http://www.androidandme.com/2009/05...r-rooting-your-android-g1-to-install-cupcake/
Everything worked fine but I cannot for the life of me get the radio to update.
It's stuck on Baseband: 62.33.20.08H_1.22.12.29
I downloaded the HTC radio update, renamed it to update.zip and followed to install procedure (home+power, alt-s).
I have tried wiping the phone beforehand etc. as well, but doesn't seem to make a difference.
It does not show any errors or anything, and seems to complete successfully, but the baseband never gets updated.
Is there something else I can try?
Thanks
If I were you, my next step would be to reflash jf.
Also, did you install the new radio update before jf 1.5? I heard that was the right way to do it.
I've tried reflashing to 1.0, reflashing radio back to original, then updating radio, updating OS - radio version still stuck on the same :/
is the official radio update signed with testkeys or "official" key?
i got my update package from haykuro's site and it worked fine.
you could also try reflashing the recovery image as suggested in the steps to get root, then update the radio image again. also remember to press home+back and wait till the phone reboots itself.
What's the radio package you're using? (Link/filename)
If it's not http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip, then it's the wrong one.
>>If it's not http://sapphire-port-dream.googlecod..._22_19_26I.zip, then it's the wrong one.
This is the radio package I'm using.
>>you could also try reflashing the recovery image as suggested in the steps >>to get root, then update the radio image again. also remember to press >>home+back and wait till the phone reboots itself.
Have reflashed back to original firmware (removing root and hardspl), then tried RC7->RC8 upgrade (radio is not updated) and then OTA update to Android 1.5.. again the radio isn't updated.
I have also tried keeping the phone rooted, and manually updating to stock android 1.5.. again radio isn't updated..
I'm all out of ideas?!
It's starting to sound like you've got a bad EEPROM to me. Does it go through all the normal steps? It should unpack the update, prompt you for a reboot, show a pic of a chip with an arrow pointing to it, and finally reboot again. No errors reported?
Hi,
Thanks for your response.
You're right - it goes through the entire procedure 'successfully,' i.e. it reports no errors and prompts for reboot, then does another reboot cycle after the 'unpacking' logo.
Just for everyones benefit:
Got the handset replaced - must have been a bad EEPROM as mikedmayer suggested.
I'm glad you were able to do that. What did you tell T-mobile? I can just imagine the blank look on the cust-serv's face when you try to tell them you think it's got a bad EEPROM because when you try to flash the radio it wouldn't take. Either that or them asking you why you're trying to flash your own radio.
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.
Hello,
I searched for my 9020A the forum for several updats on 4.0.3 because the calendar crashed always and did not well sync.
Any Update i found here or via RomManager did not work in terms of the Signal. There was no Network found. instead of Bars just a blank gray triangle.
I originally had the "cm_crespo-ota-eng.kalimochoaz.a18.p1" on it and this worked fine ecxept the calender.
With the new rollout of the new 4.0.x I thought i found the Original one and updates this one http://forum.xda-developers.com/showthread.php?t=1398186, I know now, it was wrong.
Now my info looks like
Name HERRING
HW Version Rev16
Bootloader Version I9020xxKL1
Baseband Vers. I9020xxKI1
Carrier Info ATT
Unlocked
System info:
4.0.3,
Kernel:
3.0.8-gb55e9ac
[email protected]#1
Build Nummer IML74K
Status about Signal:
Network unknown
Signalstrenght -111dBM 1ASU
Network GPRS:1
The Rom runs but also NO Signal (as described before with other ROM's)
Back in the Bootloader Mode:
Bootloader yes, Recovery always the Android with the open Belly and big acclamation mark. After pressing long enough (very uncontrolled the left +/. button) i get a menu.
From there i try to load another zip, but it stops after first searching SD card, then open the zip and then abort the process
Is there anything what i can do, I'm sure it is but I just need some help
Thanks a lot in advance
Check out this thread and flash a radio for your i9020a. This will hopefully get reception back for you
As for the bootloader: Stock ROMs replace the bootloader each boot. To change this you need root and rename /etc/install-recovery.sh to /etc/install-recovery.sh.bak
Once you flash a custom bootloader again, it won't be replaced.
Problem solved THANKS
thanks, everything worked after i found the right files Recovery and SU. About the Radio, I tried a few and it works. But I still play a little wich radio version is best.
Update on the calendar issue witch brought me into this at all. calendar crashed again. I exported all calendar items on google, deleted all entries renamed the calnder (was the main calendar you can't delete) and imported the appointments back in.
everything smooth and great now
Thanks again for the HELP
Glad to help and good work getting your calendar issue fixed, something i'll keep in mind if it ever happens to me
Although I saved my problem already, I thought I'd post it anyway, in case somebody has the same troubles. There are many GPS-related threads, but they're more or less all about long fix-times.
When this happened I was running the ported stock-4.0.4 with matr1x-kernel & clockworkmod.
I'll describe how I fixed it (=long way) and a possible faster way.
Today I noticed my GPS wasn't working anymore, despite being on in settings. According to every app it was there and turned on, but they all couldn't find a single satelite. (Maps, Z-Device, GPS Test,...) Also the GPS-Icon in statusbar never showed up. After doing a full wipe and reflash of my rom twice, I was certain it's a HW-failure.
So the plan was: back to GB 2.3.6-stock, lock bootloader and send it in for service.
After flashing stockrom, I decided to give it another try first - it was working again, including the icon.
Flashed back to ICS and no problems ever since.
My theory:
At some point the GPS-chip got stuck between off and on, yet reporting to be fully functional to Android (and thus all Apps). Flashing a rom containing radio reset it and fixed this.
Long way:
(all stock-roms contain stock-recovery, so if you let it start booting, clockworkmod will be overwritten and you have to flash it again via fastboot!)
- flash stock GB (includes older radio and bootloader)
- flash stock 4.0.3 (to get latest version of radio and bootloader)
- flash your favourite custom-rom (they all come without radio and bootloader)
Fast way: (theoretical)
- reflash any radio suitable for your phone-model
Update:
I now know what triggered the bug, running a version of matr1x-kernel with cm9-swapfile on a non-cm9-rom. Or it's a general bug in the cm9-versions of matr1x v18.0 & 18.5.
But it should be noted that once the bug occurred, changing kernel was the first thing I tried. neither flashing an older matr1x-version without the swap nor another kernel (glados) helped. Only after I flashed a stockrom GPS came back to live.
This is consistent across every CM14 ROM I've flashed. I am upgrading from CM13.
The signal bar at the top is blank as in "no service", it attempts to reconnect and show a signal for a split second but then goes back to "no service" again. When I remove my SIM card and reboot the problem simply vanishes, but of course I can't get LTE
Firmware: PCA
Recovery: TWRP 3.0.1.0
I have tried running the ROM stock with no data restore and I have tried flashing APN settings from this post.
I at first thought it was a CM14 bug but then I read that others had no problems with CM14 ROMs.
Assuming you actually have a SM-G900P (since a lot of people ignore that little detail) it's probably a matter of Cm14/14.1 doesn't appear to be wholly happy with anything other than the latest baseband, which is now PK1. To get it, just reflash to stock with Odin and then poke at the thing until it gets the two OTA updates that will bring you up to PK1. At that point if you like you can poke at the controls to update the PRL and Profile (just to be sure everything's good) and then let me suggest you make a call or two and/or send some SMSes to be sure you didn't mess something up when you tried to change the APN settings one almost never needs to touch, and then flash TWRP (or whatever recovery you use) right back in and sideload the Cm14.1 nightly and open-gapps for 7.1. Also, you will need to do a factory reset after upgrading to 14.1 or you'll get a wholly different set of misbehaviours out of the phone (trust me... I deliberately cut corners through multiple rounds of reflashing to find out what symptoms to look for). One of the more endearing failures can be no soft keyboard, nobody wants that.
I had a bunch of weirdness happening (including completely non-functional GPS) with CM14 a few days ago, and since the changelog doesn't seem to show anything addressing the screwy problems I had, it hints very strongly that people will need to update to PK1 before they can expect the device be reliable.
OH... and don't try and enable Adoptive Storage if it asks. The performance is abysmal for some reason (around 2Mb/s on a Class-10 card that otherwise hums along at 14Mb/s) and it will make any apps that are trying to use storage run like crap.
So people have it working on PK1? Has anyone had it working on PCA?
Edit: Odin restored PK1, it didnt want to boot after the reflash. I installed TWRP and restored a PCA Backup, updated PRL and profile. I flashed a cm14.1 ROM and still had the same issues.
It also didn't wipe my internal storage when I ran odin, which I remember it doing in the past.
Worked great on my S5 900P
Gracefully I got it to work on Resurrection Remix. Idk if it was the APNs or just more stable ROMs.
I booted RR stock w/o gapps, I went to enter in the APN settings using this site and it just magically worked after I entered in only the first line. It's hard to tell if it was because the ROM found out how to connect or if the first line of the APN settings triggered something.