Database Info

[ADP1.1 -> RC33] _HELP_ radio wont update

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!

Newbie, please help, nandroid problems...

Hi,
I hope this is in the right section....
I have recently put the QTEK 1.6 Hero ROM on my Sapphire (UK MAGIC), and its ok but I preferred the stock ROM.
I have obviously done a nandroid backup using the RAV1.2.1G recovery image, using the one-click method (http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/).
I want to revert back to the stock ROM using my nandroid backup. I have follwed the instructions on these forums on how to do it, but I keep getting a problem.
I use the flashboot flash system system.img, it says sending, then writing, but when it comes to verifying info something or other, it says failed, something and something about unable to verify signature (happens on data and boot imgs too).
Is this something to do with SPL, do I need to update my SPL to restore, I have downloaded HARDSPL (version?) but have not gone any further as I dont want a brick....
Any help would be much appreciated.....
Thank you

If you were able to make a nandroid backup with your current SPL, then i assume thats not the problem.
Are you sure the files of your backup is still on your SD-card, and its (foldername "nandroid") location is root on SD-card..?

Hi,
Thanks for your reply.
Yes the nandroid folder is on the root of the sdcard, i've managed to get it working. Very strange??
What I did was to ignore the windows way of restoring, I just booted into recovery and selected nandroid restore, pressed green and hey presto, it worked? Now I tried that before and it said use adb in windows... maybe i missed a file or didnt press something correctly, at least I have my stock and apps back now...
Will try tinkering again though...got to be done... QTEKs rom has a few bugs, want to try Cyanogens, but i cant find his rom anywhere (i realise the issues with google)

Then i guess your SD-card wasnt ready mounted the moment you tried to recover.

He didn't recover via recovery, but via SPL.
so, do 1clickroot again, but instead of flashing a rom in recovery, select: restore nandroid recovery.

What if
What if we never created a Nandroid backup of the OEM ROM from our phone?
Will we still be able to return to the original ROM if we'd like for warranty purposes? I have flashed a Hero ROM and the OEM Tmo for Root Users and AmonRA Recovery. I haven't flashed any Radios or SPLs or anything though.
Just curious, thanks.
I downloaded the Unroot IMage which is exactly the release I used to have, COC10, is this the ROM I need for warranty purposes?

Need help with Recovery/Nandroid issue

phone: htc dream/t-mo g1
current recovery: clockworkmod recovery v2.0.1.3
spl: haykuro (pretty sure but i don't remember)
radio: i don't remember but i know i had updated that at one point too
(if there are ways to check i will)
short version is: can i restore a nandroid backup made with amon ra v1.2.2 using clockwork v2.0.1.3?
more of the story: i had amon ra v1.2.2 and made a nandroid backup, wiped phone, and tried to load a new rom. it didn't want to go passed the g1 loading screen so i pulled the battery and restored using nandroid. went to market downloaded free version of rom manager installed clockworkmod recovery(figured maybe a newer recovery tool might be needed) and used rom manager to install the rom. still wouldn't move passed the g1 loading screen. so i load up recovery and click nandroid and restore, but it tells me none found.
are they two different types of nandroid saves that the recovery program can't use either others? or isit that clockwork looks somewhere else for the nandroid save and i could maybe move stuff around on the sd card to make it work?
this question is for after i figure out the above problem: but i had cyanogenmod v4.2.15.1 and the amon ra v1.2.2 when i made the nandroid. and i was trying to put cyanogenmod v5.0.8 and now i am using clockworkmod recovery v2.0.1.3. when i install cm5 and then reboot it sits at g1 screen, it doesn't keep rebooting. sat for a good 10mins before i figured maybe something is wrong. am i missing something? i have already upgraded my spl a while ago when i was trying out hero/2.0 roms a while back (pretty sure i put haykuro on my phone, is there a way to check?). anyone able to help me or suggest something for this?
thanks for your time

not sure if you can never tried.
Clockwork stores it files in a folder clockworkmod\backup\yyyy-mm-dd-hh.mm.ss\
When i first installed cm6 alpha it took about 15mins to reboot. Best thing to do is launch logcat while booting to see whats going on.

My opinion on Clockworkmod

I started discouraging its use on TNT Lite after the TNT Lite 5 fiasco, but I didn't realize that my opinions carried so much weight. So I want to set the record clear for everyone.
First off, if the developer / modder requires clockworkmod for their ROM, then that's the tool you need to use. I've had more than a few PM's on this question, but the answer is simple. Use what the developer asks you to use -- but also understand the risks. I would guess that most of the devs here mod with clockworkmod in mind.
For my own two active mods (TNT Lite 4 and gADAM) -- for the gADAM, it requires clockworkmod to install, right now. The reason why is because you HAVE to do a data wipe post-install, which standard recovery does not have. I have this written clearly in the instructions. As for TNT Lite, I discourage it for flashing, but I have instructions for clockworkmod users regardless. gADAM 1.3.0+ and TNT Lite 4.3.0+ have something called "Recovery Pack" built into them. This allows the user to toggle between clockworkmod and standard recovery.
Flashing is my concern, btw. For nandroid backups, data wipes and SD repartitions, the cwm tool is an absolute must. And if you are flashing between 1.1-based mods, clockworkmod should still be a low risk. HOWEVER, if Viewsonic releases a 1.2-based mod with a new bootloader, then cwm becomes a much higher risk. My point with discouraging clockworkmod for flashing on TNT Lite is just to get people used to the idea that cwm has caveats that might become a problem, later on.
When that new firmware is released, we will pick it apart and tell everyone the results of what we find. Hopefully my concerns are for nothing and the new firmware will be safe for clockworkmod users.
Also, for reference: I've been throwing around the term "1.1-based ROM" for about 2 weeks, now. Viewsonic's stock firmware has come in three flavors, so far: 1.0.1 and 1.1, which seem to be on the same dev branch and compatible (from a clockworkmod standpoint). Most, if not all, of the mods here are 1.1-based. 1.2 is a new dev branch that was introduced with build 3991, which was never officially released. This build has a bootloader that, if not flashed with standard recovery, will soft-brick your device. This is the dev branch that concerns me and that we should be watching out for, when that new firmware is released. As I mentioned, we will test it when the time comes.

when the time comes...
Somewhat quicker.
Thanks for detailed explanations!

absorbers said:
when the time comes...
Somewhat quicker.
Thanks for detailed explanations!
Click to expand...
Click to collapse
Quicker is not always better, imo. If users here use cwm, they should understand the risks. I would argue that anyone using a mod here should also understand how to install and use nvflash - devices like the Advent VEGA, Notion Ink Adam and even Viewsonic's own Viewpad10s have nvflash-only firmware updates. I personally find it to be a critical tool for anyone modding their device.

Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.

severusx said:
Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.
Click to expand...
Click to collapse
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.

There have been some discussions in the partition thread regarding the 'fix permissions' portion of CWM making the repartition suggestion obsolete. I don't have access to standard recovery to check if that option is in there too but the permissions thing may also be a feature of CWM that will be difficult to let go.

roebeet said:
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.
Click to expand...
Click to collapse
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?

I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!

brown14you said:
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?
Click to expand...
Click to collapse
It's a set of scripts - just read my first post, and the Recovery Pack reference link, at the bottom.
jazzruby said:
I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!
Click to expand...
Click to collapse
If memory serves, you should get the "!" and then a reboot. But it might not do anything if there's no command file (just hang there for a moment, and then reboot).

Thanks. Got it!

Thanks, I just booted again to recovery, no command or update.zip and same thing.

jazzruby said:
Thanks, I just booted again to recovery, no command or update.zip and same thing.
Click to expand...
Click to collapse
To verify 100% that it's working, you might want to run an update.zip. ie. use the Recovery Pack standalone, it will just overwrite what's already there. Always good to know before you actually need it.

I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!

jazzruby said:
I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!
Click to expand...
Click to collapse
Pershoot's kernel may not work with standard recovery, just a heads up. But you can certainly give it a go.....

Pershoot's kernel is nested in a subfolder and I need/want to wipe first.
I just flashed 3588 with Stock recovery and all's good.
I got root and flashed 'RP' and CWM restored my backup.
I ran TE 'fixrecovery.sh', rebooted into Stock recovery and I don't see the (!).
Aside from the downloading animation it seems like a normal boot.
This was with no update.zip @ root or command file in recovery subfolder.
So I guess it's safe to say that no (!) is nothing to worry about.
Just to be sure I dropped an update.zip @ root and same results.

why is there no interest in tge HTC A9?

Im just curious, what is the exact reason devs ignore these phones? Is there anything specific that makes them undesirable to work with? I dont think I have seen an HTC device be ignored this much since the HTC Snap?
Like i said... just curious
Cheers,
disco

It's just a phone that didn't really do well in the market, and no one wants to work on a phone that has little buyers...

What I'm wondering is why the Sprint version gets even less love than the out of date AT&T version which at least has a semi-working CM build.

Ok, thanks. Sucks that bad sales numbers can make a pretty decent phone so ignored.
Do you know if M9 or M8 are at all similar enough to A9 to maybe mod one of those roms for A9?

disco_y2k said:
Ok, thanks. Sucks that bad sales numbers can make a pretty decent phone so ignored.
Do you know if M9 or M8 are at all similar enough to A9 to maybe mod one of those roms for A9?
Click to expand...
Click to collapse
I'm not sure on that one, never worked with either, so it's kind of hard to tell, maybe put up a thread in the Q&A section with your question. And yes it does suck ????

This a copy/paste from somewhere in this forum, but I think its due to these reasons:
With the A9 (and the M9 prior to it), HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents."
Since the A9 has dm-verity enabled and forces encryption by default, root can only be achieved using the new "systemless" root methods. There are two currently working methods:
seSuperuser (this requires flashing only flashing a zip and installing an app from the Play Store)
SuperSU (automatically disables forced encryption & dm-verity, but requires a "Format Data" in TWRP)
There is also no way to take an OTA after you root. However, prior to rooting, you can take a fully untouched system image backup with TWRP, which can be used to restore a fully stock system to the device in order to take an OTA.
How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled on the A9's ABOOT, so TWRP must be fastboot flashed over stock recovery. The firmware zip included in the OTA will include a usable stock recovery image. That can be extracted and flashed after stock system is restored so that the OTA can be applied.
How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system).
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.

My ota works fine. Im rooted and you can backup by formatting data partition in the beginning. Fastboot works fine, flashing wirks fine. Really have not had any issues described above.
Oh well