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.
Hello,
I have updated to JF 1.5 and its working great. But when I boot up to make a nandroid backup, it says "Android system recovery utility Build: JFv1.41"
When I press Alt+B to backup I get an error saying:
Error running nandroid backup. Backup not performed.
Any ideas?
I guess you didn't bother to read JF's notes about not having a modified recovery based on 1.5 yet. Anyway, recovery is versioned independently of the main system software, like the radio.
jashsu said:
I guess you didn't bother to read JF's notes about not having a modified recovery based on 1.5 yet. Anyway, recovery is versioned independently of the main system software, like the radio.
Click to expand...
Click to collapse
I did read it, I am totally fried :/
It took me 4 hours to recover my phone earlier and now studying for my 5 final exams this week, so I totally forgot about his post regarding the recovery image
Thanks for the reminder
You should update your recovery though. The latest JF recovery is v1.42. The link in JF's ADP1.5 post links to a v1.43 recovery-only updater, but it is v1.42 (confusingly named 1.43 because it was bundled with the JF1.43 system software updates). It fixes a recovery 1.41 bug where adb didnt run with escalated privileges.
Hi! first of all i dont know if this is the right forum to right this question. Dont know if it should be in the Dream forum but i have a magic, so i write it in the Magic forum.
My problem is that i for some reason can't flash Cyanogen's ROMs.
I have had Cyanogen's 4.0.3 ROM on my magic, but a couple of days ago i decided to upgrade it and try the Experimentel version 4.1.8.
I First tried to use the CM Updater, but for some reason it did not work, it would not flash the ROM.
So i downloaded the ROM manually and did as i always do: boot in recovery, wipe, apply and then reboot. Everything went fine until the reboot. After reboot the phone gets stuck at the HTC Magic screen, and nothing happens, only thing i can do is to remove the battery and the try and boot the phone again, and then it just get stuck at the HTC Magic screen again.
I have no problem flashing a MyHero 1.1.1. It works perfect.
I have also tried with a number of the other Cyanogen ROM versions, even tried 3.9.1 (cant remember the exact version number) have also tried the 4.0.3 version that did work before all this happened, but still no luck.
I have tried installing the Cyanogen Recovery image and the flash the Cyanogen ROM, but it still gets stuck at the HTC Magic screen.
I have tried reformating my sdcard and then flash, but no luck.
Can it be that i need a new SPL, Radio or something?
My current Fastboot screen looks like this:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
If anyone know what i need to do to get the Cyanogen ROM on my magic, i would really like to know.
Any suggestions would be much appreciated. Hope to here from you.
Per
Cyanogen is built for 32B (You seem to have a 32A) so you need to flash a 32A-kernel on top of the cyanogen ROM.
Check this thread:
http://forum.xda-developers.com/showthread.php?t=544854
do what psyduck says, AND wipe before you do it. going from a stable to an experimental build requires a wipe or you will have a lot of issues.
Okay, thx for the answer both of you.
So i just "flash" the kernel first, like if it was an normal update? e.g. rename it update.zip, push it to sdcard, wipe, flash and then reboot. And then flash the ROM like i would normal do?
But what if I would like to flash a stable build, e.g. 4.0.4 what do i do then? i can't find a kernel for that in the link. Or can i just use 1 of the kernels in that link?
Per
Cyanogens ROM first! Otherwise the kernel will be overwritten with the one included in the cyanogen ROM.
Don't know why the old kernels were removed? Better to ask in the linked thread.
Decided to try Donut on my MT3G and had the same issue, I did a wipe after I noticed it didn't get past the first splash screen and that fixed it.
Thx for the help all of you, im now on the Cyanogen ROM, finally. its good to be back
But have 1 last question: When i deside to upgrade the current Cyanogen ROM im on now, i would also need to flash a new kernel right?
the thread listed by PsyDuck has it.
first page, look at the file called "Base Kernel v4.1.9.2"
link for it is right below.
Use amonRA's Recovery so you dont have to rename the updates.
download CM's latest 4.1.9.2 ROM and the basekernal. put both in root directory of SD.
boot into recovery, nandroid backup, wipe, Flash ROM then Flash update.
reboot. should work fine.
I did so, and everything works now. really nice, finally
32a looping after flashing CyanogenMod 4.1.99
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Thanks for replying. I didn't manage to flash successfully before that's why not able to do a nandroid backup ... unless of course if someone is willing to share the backup with me.
str4vag said:
thats actually weird..try restoring nandroid backup..
i followed the same instructions with the exception of not wiping..try that see if it helps.
Click to expand...
Click to collapse
Same Boat
I have the same problem when flashing CM 4.1.99[9] ROMS. It goes into the endless boot/reboot mode.
I used to have the problem with the HoFo ROM as well (between versions 2.0.5 - 2.0.9). HoFo started working after that. I don't know what changed.
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
RADIO-3.22.20.17
Apr 20 2009, 15:30:43
ranger79 said:
I have a 32a and I used to run CM 4.0.4 perfectly fine.
I've been trying to flash to later CM roms but until now still not able to do so.
Every steps in http://forum.xda-developers.com/showthread.php?t=568032 were followed carefully. Here is what I do:
1. Copy the HTC ADP 1.6 DRC83 into the SD card
2. Copy CyanogenMod 4.1.99 into the SD card
3. Copy the Kernel Port file into the SD card
4. Wipe
5. Flash HTC ADP 1.6 DRC83
6. Flash CyanogenMod 4.1.99
7. Flash the Kernel Port file
8. Reboot
The phone reboots into the first screen (HTC Magic) and after a while, reboot again and still stuck at the same screen.
Eventually I have to take out the battery.
I don't partition my SD card and it has been working fine with the other roms such as RA 1.6.1H, MyHero 1.1.2 etc, so I doubt that could be the problem.
I tried to plug the USB and "adb lolcat" but my WinXP says USB device not recognized.
The strange thing is it seems everyone's 32A doesn't have this problem, except me. I've reported this problem before but wasn't able to get a solution.
Is there anyway to troubleshoot to find out what goes wrong?
Thanks in advance.
Click to expand...
Click to collapse
I had CM6 on my G1 with HBOOT-1.33.2005.
I downloaded RC7 and accidentally installed it without flashing HBOOT-1.33.2003 and now it says HBOOT-0.95.0000.
Is this OK? If it is, im gonna start flashing it back to 1.6.
maxppp said:
I had CM6 on my G1 with HBOOT-1.33.2005.
I downloaded RC7 and accidentally installed it without flashing HBOOT-1.33.2003 and now it says HBOOT-0.95.0000.
Is this OK? If it is, im gonna start flashing it back to 1.6.
Click to expand...
Click to collapse
so you went back to android 1.1 or 1.5? you dont have any engineering spl anymore as far as i know.
that means you have to start right from the beginning with rooting flashing etc
pls correct me if im wrong
Edit: do you still have a modified recovery or is it the stock one?
Hi, I went back right to the beginning which is DRC7 (version 1.0)
Im not sure about the recovery image question, how would i find out?
boot into recovery. (did you flash another recovery some time earlier?)
so if it is the one you had then you dont have to start from the beginning.
is it one without a menu or with a menu of 3 options you have to look for tutorials and start all over
why dont you just get into fastboot, wipe everything, fastboot flash EZterrys new radio & hboot, and than flash biffmod 2.1 ROM?
i did it this morning, and i must say... t'is nice ;]