Related
Hy guys! This is my first post because I've always found a solution in this great fourm for my previous issues
Now, after searching the whole fourm without finding a solution, I've to open a new thread, hoping you could help me
I've upgraded my Dream from JF ADP1.1 to JF RC33 following this [1]. These are the steps I've followed:
-placed the RC33 image [2] in the sd root, after renaming it to update.zip
-boot up the ADP1.1 into recovery mode
-perform a wipe and reboot into recovery mode again
-perform the update and reboot
-activate the phone with my google account via EDGE
-placed the radio update [3] in the sd root, after removing the old update.zip and renaming it to update.zip
-reboot into recovery mode and perform the update.
Everything seems to went fine. Into recovery mode the phone verifies and extracts the image and then asks to press HOME+BACK to reboot. After pressing HOME+BACK the system flashes the radio image and then reboots showing the image with the arrow and the chip. After this image the phone boots again into recovery mode. At this point I've pressed home+back to reboot again and now the dream boots in standard mode, loading the OS.
Everything works (EDGE, SMS, CALLS, WIFI etc.) but, when checking the settings, the build number is ok (*RC33*) but the baseband has not been updated. In fact the version is still the old one *22_12.29
Same thing if I check the baseband version via the SPL (HardSPL)
Any help much appreciated!
Thank you!
Simone "simoneinweb" Mainardi
[1] http://forum.xda-developers.com/showthread.php?t=475381
[2]http://jf.odiness.com/v1.41/JFv1.41_RC33.zip
[3]http://jf.odiness.com/RC33/RC33radio_update_testkeys.zip
I've also tried to reflash the ADP1.1 and then apply the update.zip containing the radio update but baseband version is still the old.
Please help...
Hi!
I did the same thing with my ADP, but I had previously flashed it with JF RC30 1.41. I updated to RC33 with no problem, and then I applied the radio patch. My phone got stuck in the boot logo and I had to do a wipe and reflash with RC33 to get it working. I applied the radio patch and everything was OK, but the baseband is still in the same old version.
Maybe an specfic ADP issue?
I updated from ADP 1.1 to RC33 and flashed radio, and the baseband confirms the update was successful.
How do you flash the radio? I applied JF RC33 update and he mentioned we have to flash the new basebad separately, I've never done that before
Are you using an actual ADP1 or just a G1 flashed with the ADP firmware. I haven't tried it on my ADP1 as I have no real need for RC33 but I believe if you are on a real ADP1 it won't actually flash the radio with the update from a normal G1 because of the unlocked radio in the ADP1. Just my $.02.
Simone: Can you verify the MD5 of the radio update after you have copied it to your microsd? Should be cf8714d273fb0274574d9e3831e11fdd.
Ok this is my problem after I installed jf rc33 and the radio. Yes I did a wipe from my jf adp1.1 installed jf rc33 then did the radio update but now I get no internet on my g1. I went into. Settings > about and it says that the connection is EDGE with no data connection. The g1 its self almost closes the edge as soon as I receive a mms as there is no E in my status bar. Also I live in a market that doesn't have 3g yet so I have tried the settings use 2g only and without. Any ideas what the problem could be? I assume it is the radio but can I reflash an old radio without doing a wipe? Or if I need to wipe and go back to jf rc30 or adp1m1 do I need to flash back to rc29?
You can flash an old radio without a wipe. Replace the radio.img inside the radio updater with the one from signed-kila-ota-116143-prereq.TC4-RC19+RC28+RC29.zip and resign the entire zip file with SignApk.
ok before i do this what else could the problem be if any? causing no internet?
I was with rc30 JF , and then i moved to rc33 , then flashed the radio. What is the number supposed to be after the update or before? Mine right now is
_1.22.14.11
Is this right after i flashed the radio? or this is the old one? no idea..never paid attention to the baseband version.
jojo_angelov said:
I was with rc30 JF , and then i moved to rc33 , then flashed the radio. What is the number supposed to be after the update or before? Mine right now is
_1.22.14.11
Is this right after i flashed the radio? or this is the old one? no idea..never paid attention to the baseband version.
Click to expand...
Click to collapse
i have the same radio baseband version after i did my update... but when mine went into a loop i hit alt x and typed reboot and my g1 booted normally.
another note does anybody have a signed update of the old radio they could post. i have not gotten into signing apks yet and when i did a search for sign.apk i got stercsons thread but i didnt setup the sdk yet my desktop is very limited on space.
Here's the radio from RC30 signed with test keys. (ver 1.22.12.28)
http://drop.io/rc30radio
9817b38ff5797370e3270e40cca36e15 *rc30_radio_testkey_assert-dream.zip
thanks jashsu . Since the version is different than rc30 you just gave, i suppose the radio update was a success. What does that update do? boost 3g or?
How do you flash the radio? I applied JF RC33 update and he mentioned we have to flash the new basebad separately, I've never done that before
Click to expand...
Click to collapse
I've flashed the radio separately, as described in http://forum.xda-developers.com/showthread.php?t=475381
Are you using an actual ADP1 or just a G1 flashed with the ADP firmware.
Click to expand...
Click to collapse
I'm using a G1 flashed with the ADP image. But I've also tried to flash it back (successfully) to jf RC30 and then perform the radio update but without success.
Can you verify the MD5 of the radio update after you have copied it to your microsd?
Click to expand...
Click to collapse
I always verify the checksum before flashing everything in the ROM. I trust in the reliable data transfer service offered by TCP but in this cases an md5sum is a gooood thing!
How? I tried to flash from it to stock RC30 then use the RC33 patch but it won't let me flash to the stock RC30. How can I do it. Sorry if I'm not clear just let me know and I'll edit.
Wipe out all (just in case) then just flash any JF 1.4x RC33. I did it 2 days ago with no problems from JF 1.43 ADP1.1 Holiday Edition to JFv1.42_RC33
Ahh I figured it out. I would have used a JF RC33 but I needed stock to test something. Anyway it didn't like the JF recovery image flashing the stock one so I took the recovery.img file out of the System folder of the update.zip and flashed it with fastboot and it used that update just fine. Thanks!
EDIT: Sorry this post wasnt very clear. I mean after I flashed the stock recovery.img over the JF one with fastboot I just booted into recovery, used the stock update.zip file and it flashed fine.
I am currently rooted on 2.3.3...will manually updating to 2.3.4 cause any issues? Will I need to re-root?
Sorry for the newb question
Sent from my Nexus S using XDA App
Yes you will have to re-root, but you can do it using the same method you used before, I believe.
after doing a bit of reading and having already experienced upgrading from 2.3.1 to 2.3.2 and 2.3.3, i just decided to go for it. here's what you need to do.
i'll give you what my setup was. 2.3.3 running stock with modified radio (kb3) and modified kernal (netarchy 1.3.0.7 bfs).
i got all the files i thought i would need.
1. kb1 radio
2. netarchy 1.3.0.8 bfs for 2.3.4
3. the 87mb 2.3.3 stock zip
4. the superuser.zip
5. the 2.3.4 zip
made a titanium backup of everything, and did a rom backup.
and then i just went for it. booted to clockwork recovery. tried flashing 2.3.4 and of course i got an error. i was expecting that.
updated to kb1 radio which is stock for 2.3.3 and then ran 2.3.4 update, and it errored again. was expecting that since my kernel was still different.
i didnt know how to flash stock kernel so i went ahead and ran the 87mb zip. it went very quickly and it flashed only the radio and the kernel.
tried 2.3.4 again and still no luck.
ran 2.3.3 again and this time it updated fully, taking approx 2 minutes.
NOW i ran 2.3.4 and it installed.
then i ran netarchy 1.3.0.8 cuz i just can't live without the voodoo color/sound enhancements.
i rebooted the phone and it loaded the OS up fine and dandy.
i also figured i would have lost recovery, but that wasnt the case. i rebooted into recovery and clockwork loaded. i then mounted everything and installed superuser.zip. that finished and i booted back into the phone.
all done. superuser back, colors great, radio kd1, stock 2.3.4. the one final thing i did was check system/etc to see if the recovery.sh file was renamed. it wasnt so i renamed it to recovery.sh.old using root explorer.
i rebooted to clockwork to make sure i still had recovery and i did.
done and done.
hope that helps.
Well crap....I'm not really up to speed on half this....had some serious trouble trying to root the first time...this list of what you went through makes me want to vomit just thinking about it lol...
Sent from my Nexus S using XDA App
I followed the thread [ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011 to root TB.
If I use Bamf 3.0 Sense RC4 rom, do I have to upgrade to MR2 or the custom automatically install it for me?
Yes u need to upgrade ur radio only through hboot. Download the mr2 radio in the development section. Chingy posted it
Sent from my ThunderBolt using XDA Premium App
d3rkC3d3r said:
I followed the thread [ROOT] MR1/OTA PermRoot + Unlock Bootloader - Safer/Easier 5/12/2011 to root TB.
If I use Bamf 3.0 Sense RC4 rom, do I have to upgrade to MR2 or the custom automatically install it for me?
Click to expand...
Click to collapse
Download the MR2.5 Radio, rename it to PG05IMG, put it on the root of your SD card, boot into the bootloader (from power off hold vol- & pwr) and then let it run the update.
g00s3y said:
Download the MR2.5 Radio, rename it to PG05IMG, put it on the root of your SD card, boot into the bootloader (from power off hold vol- & pwr) and then let it run the update.
Click to expand...
Click to collapse
This. If you rooted your phone yourself this is easy. I was initially scared to update the radio for my TB coming from my OG droid. Just make sure you're running an MR2/2.5 compatible ROM. Works on CM7; I'm also going to test out a sense ROM for kicks later today. The links on the original radio thread are down but there is another thread with them up. good luck.
Rick
Radio Thread
Working MR2 radio thread
http://forum.xda-developers.com/showthread.php?t=1154010
In addition to what g00s3y said, I highly recommend that after you flashed the radio and are booted up into your GB rom, either rename or delete the PG05IMG.zip file from your sdcard. If you leave it there and have to boot into the bootloader or recovery in the future this may cause you a great deal of annoyance as it will always try to flash it and you'll have to boot the phone up and deal with it afterwards anyways.
This is something I really do not like about HTC phones. It shouldn't automatically go straight for the zip and try to flash without my input requesting to do so. Very very annoying and something I hope to see changed in future bootloader versions.
So, after I rooted the device with MR1, should I flash rom first or MR2 first?
Doesn't actually make a difference. If you flash an MR2 ROM on an MR1 Radio, you just won't have a signal. Go to HBOOT, flash the right Radio, reboot and everything is dandy.
DaRkL3AD3R said:
In addition to what g00s3y said, I highly recommend that after you flashed the radio and are booted up into your GB rom, either rename or delete the PG05IMG.zip file from your sdcard. If you leave it there and have to boot into the bootloader or recovery in the future this may cause you a great deal of annoyance as it will always try to flash it and you'll have to boot the phone up and deal with it afterwards anyways.
This is something I really do not like about HTC phones. It shouldn't automatically go straight for the zip and try to flash without my input requesting to do so. Very very annoying and something I hope to see changed in future bootloader versions.
Click to expand...
Click to collapse
It asks you if you wanna update, you can say no
Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
talbot27 said:
Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
Click to expand...
Click to collapse
What zip did you apply IN CWM?
Sounds like you applied a kernel too. Having CWM is not normal if you just flashed the superuser zip.
You will likely need to flash back to stock prior to updating with the GB OTA whenever it comes out.
_____________________________
Bloat frozen EE4 / Stock Kernel
V6 SuperCharger / Loopy Smoothness Tweak
Thank you for the reply.
The only zip I applied was the su-2.3.6.3-efgh-signed file downloaded here.
For CWM I flashed 0817_charge_recovery.tar.md5 found here.
Again I am now rooted but can still boot into CWM. After flashing the CWM file and disconnecting my phone, I initially fat-fingered it trying to boot into recovery and it rebooted. I then powered off and booted successfully into CWM to apply the zip file.
Any thoughts?
Ok, the main difference I see between my config and yours is that I may have used a different version of the superuser package.
The one at the link that you provided is superuser/su-3.0-d-signed.zip.
The one that I used is the su-2.3.6.3-efgh-signed.zip from here
You did start out from stock correct?
What is the kernel version in Settings->About phone->Kernel version?
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
talbot27 said:
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
Click to expand...
Click to collapse
Looks like you did the same steps that I did other than your extra boot into CWM. Usually, the stock init will check for the proper recovery, file systems, etc and then "fix" that which isn't right.
I have never seen it not do that before (I have had to reflash CWM several times before due to botching the 3 button bit)
_____________________________
Bloat frozen EE4 / PBJT Voodoo 0730
V6 SuperCharger / Loopy Smoothness Tweak
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
hoppermi said:
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
Click to expand...
Click to collapse
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
talbot27 said:
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
Click to expand...
Click to collapse
Enjoy it. I like CWM much better than stock recovery ;-)
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger