want to go to Rogers, recovery.img upg procedure and more ?? - G1 General

I'm rooted. When I rooted I installed the JF1.42 recovery.img file. I'm currently running Cyanogen's 3.3.4 with the latest radio and HardSPL.
I'd like to go to the Roger's build, but I'm a bit worried. I believe that for the Rogers build I need to upgrade my recovery image to 1.43 and my SPL to 1.33.
I've done lots of searching and not been able to confirm this procedure for upgrading the recovery image. Every search that I do is the initial root procedure.
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
Can anyone confirm that the above is the correct procedure and tell me why the last line isn't just
-- flash_image recovery /sdcard/recovery.img
Also, I'm a bit worried about having to go to the newest SPL. It seems that going to that SPL is a bit of a minefield and the original supposition that having the newest radio would keep you from bricking, is not necessarily the case.
Can anyone confirm or advise me on the best method to upgrade from where I am recovery1.42/CM3.3.4/latest radio/hardSPL, to recovery1.43/RogersR2/latest radio/SPL1.33?
Thanks tons!

smasraum said:
I'm rooted. When I rooted I installed the JF1.42 recovery.img file. I'm currently running Cyanogen's 3.3.4 with the latest radio and HardSPL.
I'd like to go to the Roger's build, but I'm a bit worried. I believe that for the Rogers build I need to upgrade my recovery image to 1.43 and my SPL to 1.33.
I've done lots of searching and not been able to confirm this procedure for upgrading the recovery image. Every search that I do is the initial root procedure.
* mount -o remount,rw /dev/block/mtdblock3 /system
* rm -f /system/recovery.img
* flash_image recovery /sdcard/recovery_testkeys.img
Can anyone confirm that the above is the correct procedure and tell me why the last line isn't just
-- flash_image recovery /sdcard/recovery.img
Also, I'm a bit worried about having to go to the newest SPL. It seems that going to that SPL is a bit of a minefield and the original supposition that having the newest radio would keep you from bricking, is not necessarily the case.
Can anyone confirm or advise me on the best method to upgrade from where I am recovery1.42/CM3.3.4/latest radio/hardSPL, to recovery1.43/RogersR2/latest radio/SPL1.33?
Thanks tons!
Click to expand...
Click to collapse
The 1.42 recovery image is fine, don't worry about changing it. I have RogersR2, radio 26I, SPL 1.33 no issues.
The key to the new SPL is the 26I radio AND a PVT board, wiping before SPL flash, and flashing/reflashing firmware immediately after upgrading SPL or doing a nandroid restore immediately after upgrading SPL.

I know it can be a little gut-wrenching to risk our phones like this - it definitely was for me. But I think most of the pitfalls have been ironed out and your chances for success are very good.
1st thing though is to make sure you have a PVT board by booting with camera+power. It'll say right near the top of the screen. I wouldn't try to update to the new SPL with the other board.
The order is:
recovery
radio
SPL
ROM
You can get an update.zip for the 1.43 recovery in this thread. It's near the bottom. Much more fool-proof then pushing the image.
Then you can flash the newest radio. Your phone will still boot and run with the new radio.
Then flash the new SPL and ROM. This was kinda a 1-2 punch for me.The new SPL flashes over really quick and there are messages in the recovery to let you know what's going on. Make sure you reboot to let the new SPL finish installing. It will reboot one more time on it's own after that.
My old ROM wouldn't boot with the new SPL. I had to use a card reader to get an update.zip on the card and wipe/reflash. So make sure you have an update.zip ready to go.
You can get the new radio and SPL here.
Let me tell you - it was all worth it to me. The new Rogers Rom runs great and Exchange support is icing on the (cup)cake.

Thanks all. I guess I'll wait until I get home to use the 2 SDCard method of updating the SPL and then new ROM.

Related

Rooting flashing clarifications

Been reading lots of guides and forum posts in preparation to getting my stock G1 all did up, just wanted to clear a couple things up
I'll probably be installing the jf 1.5 firmware,
Just to be sure:
1) once I have a rooted RC29 installed, I can install hardspl, and then install the JF firmware version I want?
2) What's the difference between the jf 1.5 US rom and the jf 1.5 ADP rom, I assume the ADP is the dev phone version, but can it be/is it worth it to install it on a normal G1?
3) In the wiki it says this about rooting:
On RC29 phones and lower, a huge exploit existed where anything you typed into your keyboard was also being run in a hidden console with root permissions.
1. Download recovery.img and copy it to your SD card (see the previous section on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
If I'm just going to be installing the JF firmware immediately, do I really need to do step 8? - what does that get you?
Thanks for the help, I suspect probably these questions have been answered before, so if you've got links to those answers, please do post.
1- Never installed hardspl :-S Haykuro's wipes your ROM, as in, you have to boot in to recovery and reinstall your ROM, but hardspl is probably different. Hard SPL is an optional step really, I never installed it. If you're not going to use fastboot, you don't need it, and you can always install it later when you find out more about it and actually need it.
2- Yeah ADP is the dev phone version. There are hardly any themes for the US version but loads for ADP. Not really sure of the other differences, I don't think ADP has the amazon mp3 store.
3- Step 8 is what installs your custom recovery image, so when you hold down home+power it will give you the options to wipe and flash your phone. Without the recovery image, you can't install a ROM.
hospadar said:
Been reading lots of guides and forum posts in preparation to getting my stock G1 all did up, just wanted to clear a couple things up
I'll probably be installing the jf 1.5 firmware,
Just to be sure:
Click to expand...
Click to collapse
1) once I have a rooted RC29 installed, I can install hardspl, and then install the JF firmware version I want?
Yes
2) What's the difference between the jf 1.5 US rom and the jf 1.5 ADP rom, I assume the ADP is the dev phone version, but can it be/is it worth it to install it on a normal G1?
ADP is the developers version and US has MyFaves. ADP takes up less system space.
3) If I'm just going to be installing the JF firmware immediately, do I really need to do step 8? - what does that get you?
You DEFINITLY want the SPL. In fact, use my signature to acquire the 1.4 recovery so you can install any zip from the sdcard, create backups with Nandroid and restore in case you mess something up later on. Without it, it's a hassle and time consuming.

Flashing problem on Magic_Rogers 3.54.631 rom

hi everybody!
some days ago i flashed my magic (TIM Italy, so 32A) whit the Magic_Rogers3.54.631.3 rom, that was a ruu exe file.
It flashed my spl and radio, that now are hboot-1.76.0010 (SAPP10000) and 6.35.16.19.
Now i wanted to change rom because of the language (i'm not able to put an italian dictionary when i write), but i don't succeed.. i tried to reflash the recovery, but i can't because fastboot says that is not possible to send data to the phone, so i can't also boot some recovery image.. same problem via adb or via terminal on the phone.
i rooted the phone with the last universal androot, but it's the same..
i succeeded to change recovery only with rom manager, but the phone doesn't go in recovery mode (it's still on the "rogers" splash screen), or if it goes, it reboot alone after a few seconds.
oh, at last, i'm not able to flash other rom, like the RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver or my original TIM rom.
I'll be really grateful to who will help me!!
thanks for reading!
download this application FlashRec
install it to your device
then download any of Amon_RA recovery imgs (HERE) (Choose the correct one for your device)
then push it to your sdcard
then open the FlashRec and press backup,
then write in the blank box "sdcard/xxxxx.img"
where xxxxx is the name of the img you pushed to your SD
then press flash .. if it is successful, connect your phone to adb
and write "adb shell reboot recovery"
I tried this on 32A 1.33.0010 and Radio 3.22,
I'm NOT 100% sure it will work with you,
try it at your own risk.
it says "phone type is EBI1/32A"
i press backup with or without the name in the box,and the result is
"backup failed: could not run command."
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
renedlog said:
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
Click to expand...
Click to collapse
I think you are right, because i was on stock 1.5 when i used this method.
OmarAta said:
I think you are right, because i was on stock 1.5 when i used this method.
Click to expand...
Click to collapse
me too... but the htc magic 32a with the actual stock rom, android 1.5 with sense form january, is already bugfixed.
Moving to General
sorry for the mistake, i thought it was the right section..
anyway i followed the guide in the post linked by renedlog and.. it worked!!! i didn't know where to put the flash_image file.. but it was written there.. so i did all, and now my rom is the RCMagic 5.0!
do you think it's good to try something different?
i use RCMagic 4.2
the version 5 is still a little buggy with the wake up from standby.
i will upgrade to an android 2.2 rom, if there is an update today for the 32B and hopefully it will be patched to my 32A.
yeah, i saw that bug.. it's really a pity, the rom was a little faster than the 4.2..
i suppose it would not be a big bug, so i hope somebody that is able will fix it!!
are there so big changes beetwen the 2.1 and 2.2?

[Q] Please help!! I may have messed up my MT3G!!

Okay, so I installed a radio version 2.22.27.08 via clockwork recovery on my 32A device when it should be only used on 32B!!!! I wanted to use yoshi's rom and I followed the directions but must have clicked on the wrong one!
I downloaded the old radio (3.22....) and tried to flash it via fastboot (it only comes in a .img file) but it keeps failing on the signature!
Is there anything I can do to downgrade to that radio?
I made a nandroid backup and my phone still works fine with the wrong radio, but I am not able to install another rom that I want!
Give us complete fastboot info

Is there a chance for my (new) Magic ?

Hi all,
Well, that's the way, it sometimes goes....
On Tuesday i received in exchange my new Vodafone Magic. After only two days i'm stuck with a "deadlock" situation. Following happened:
The Magic was delivered with the standard 1.6 Donut on it. I then manually flashed the OTA update to 2.1.1 and the apps that I use regularly. Yesterday I used the "Gingerbread.apk from the XDA forum to gain root. Armed with root, i downloaded Rom-Manager from the Market and installed ist. Next, i installed the Clockwork Recovery via Rom-Manager. Then reboot into the recovery and Voila .... Clockwork recovery.
Ok, first thing i did was to make a backup of my current ROM and then came the big mistake ...
I wanted to have a black Notficationbar in OTA. So i flashed "blackbar.zip" from "http://www50.zippyshare.com/d/43974308/12150/blackbar.zip". But after reboot it didn't work (Bootloop).
Well, I thought I reboot back into the recovery and restore my backup.
And then came the shock ...
What I saw then was not the Clockwork recovery but the original HTC Magic recovery.
Ok, tried to flash the 2nd part of the OTA Update again.... Nope. The HTC Recovery reports "Assert Failure". Obviously checksum tests are done and after flasing the blackbar, "framework-res" no longer matches the checksum.
OK, so back to 1.6 with the NBH Image .... Nope, The Magic reads the image, but refuses to install with the comment "main version is older"
Since the OTA update, installs an "S-ON" Spl, no more fastboot...
Searched in Google and found a lot of Posts saying "try using this image", "try using that image", but nothing worked.
So the Situation now is as follows:
- Magic can not start anymore. Bootloop in the "android" Bootscreen
- Fast boot is not possible because of the SPL
- New import of the OTA update, part 2 not possible due to checksum error
- Back to 1.6 not possible due to "Main version older"
- I only have the the original Magic Recovery. (and of course can boot into HBOOT / FASTBOOT mode)
What I would need would be a flash-ready image of Enginnering SPL or an update, however, in the format, which is accepted by the original recovery of the Magic. I also dealt with the idea of creating a Goldcard. Could this be a way to save my Magic?
Has anyone else an idea, or anyone knows how to create a flash-ready image, which is accepted by the original recovery?
Thanks and greetings. lagloose
Is this a 32B or 32A? I've been in that situation before. If you can get into fastboot you can save it. Get a RUU (for 32A I used 3.5.401 from Rogers) and install it. In the process, it'll try to get the phone into fastboot mode, but it's already there, so you'll factory-reset it. After that, you can apply an Engineering SPL through update.zip (using the recovery from the RUU itself, not AmonRa or others's) and then you can do anything else you want on your device.
Good luck! ^^.
I think you're going to have to make a goldcard, which is a problem since you can't boot. If you can somehow make (find?) a goldcard then you should be able to flash a RUU. Can you post you're device specs? Vodafone Magics are supposed to be 32A's right?
I don 't know your phone information,but i think you need a goldcard and flash ruu

15MB extra RAM for ht-03a using T-Mobile bootloader and radio

Posted by SBS
I flashed the new SPL and radio that also came with the T-Mobile Froyo OTA giving myself an extra 15 MB of RAM. This post attempts to compile the background and links to the knowledge needed to do this safely. Because this is much more complicated than rooting with universal androot, and you can very easily brick your phone, this should not be done if you don't fully understand the process and aren't comfortable using the command line. While I believe someone may have created flashable signed zips for doing this, the recommended way is to use fastboot.
The Benefits
ROM Memory Swap Total (KB) Total (MB)
Stock
97708
0
97708
95
Rooted old SPL/radio
97708
31316
129024
126
Rooted new SPL/radio
112844
31316
144160
141
Without swap, that is an additional 14.8 MB of real memory.
First, a few things you need to know before proceeding:
Perfect Secondary Program Loader
The ht-03a shipped with a "perfect" SPL that does not allow remote fastboot. Therefore, an interim engineering SPL will have to be flashed in order to use fastboot to flash the new SPL (1.33.0013) and radio. The new SPL is also perfect, but a version was modified for the Dream/G1 (1.33.0013d) that allows a few fastboot commands, such as fasboot erase system -w for a complete wipe. Fortunately, 1.33.0013d has been confirmed to also work on the ht-03a, a Google-branded 32B magic.
Even with the modified "d" version of the new SPL, you cannot remote boot a recovery image, flash new splash screens, flash a new recovery image (if for example yours became corrupted). You will have to flash an engineering SPL, do what you must, then reflash 1.33.0013d. Unlike flashing ROMs, flashing SPLs is not 100% risk free.
Amon_RA Recovery Recommended
I'm sure this will probably get some feathers ruffled, but I am leery of clockwork recovery and ROM Manager. As outlined here, this is not the developer's fault but a low memory issue. Perhaps this new SPL and radio will fix that, but the fact remains that there have been a number of instances Dream and Magic users getting stuck with no working recovery. With an Engineering SPL, this is no problem because fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img fixes this, but with a perfect SPL, it will be much more difficult, as in making a goldcard difficult.
Another fact is that I have yet to hear of this ever happening with Amon_RA's recovery, and ezterry at XDA is suggesting to use Amon_RA. However, using Amon_RA means you can't use ROM Manager.
(NOTE: ht-03a users need "G" versions of Amon_RA)
Patched Kernel Required
If you are like me, you never cared about kernels. Yeah, you might have been interested in testing out some of the overclocked kernels but you were perfectly happy to use whatever the developers included with the ROM, which will likely be the most stable way to go but maybe not the fastest. Stability versus bleeding edge. For the time being, those days will be over. All of the cooked ROMs available right now will need a patched kernel that may or may not be included with the ROM.
I have no idea what is the "best" kernel. It will depend on what makes it the best for you.
Required Reading
Start with ezterry's XDA write up with links to the radio and SPL. If this doesn't make sense, stop and read more.
If you don't already have one, read the instructions on flashing an engineering SPL.
The SPL in the above link comes from this list of engineering SPLs.
Finally, you'll want to understand how to flash Amon_RA's recovery because it is less prone to problems than clockwork.
If you plan to use CM 6.1, ezterry's CM Forum post contains a port with the new radio.
Required Environment
Engineering SPL (I am using 1.33.2005. Many others are using 1.33.2009. IIRC, there might be issues with 1.33.2010 and CM, so 2009 is probably best.)
fastboot utility installed on your PC
Android SDK on your PC to allow you to use ADB (Perhaps this is technically not required but at this point of getting into your phone you ought to have it installed.)
What I did
The T-Mobile US Froyo OTA with a cyanogen kernel I've been running lately is by far my favorite ROM due to speed and stability. I've mentioned missing some CyanogenMod features, but when it comes to my phone, stability trumps the bleeding edge. So I 1) did a nandroid backup of my current ROM, 2) updated the SPL and radio, 3) restored the backup, 4) flashed the patched kernel, and 5) picked up where I left off with no loss of data on my phone. The actual work involved for me was about 10 minutes because I already had an engineering SPL and Amon_RA. I spent infinitely more time writing about this than I did actually experiencing it.
So far, all seems fine, but I'll need a bit of time to test. Wifi and GPS are working, and the phone does seem snappier. I haven't had a chance to see how battery life is. There are two choices of radio, 2.22.27.08 or 2.22.28.25. The former came with the OTA. The later is a newer radio. Depends on who you ask and where they live, which is better/faster/easier on the battery. For now I am using 2.22.27.08.
Rebooted to recovery and nandroid backup my current ROM.
Followed ezterry's instructions on XDA
Downloaded all necessary files and checked the MD5 sums against what was published.
dream_2708kit.zip which includes 2.22.27.08 radio and 1.33.0013d SPL
Kernel installer for CM Nightly 271
Mounted my SD card, copied the kernel installer to the root of my SD Card, and rechecked the md5 sum.
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
fastboot erase system -w
fastboot erase boot
Reboot to recovery and restore ROM.
Flash kernel.
Reboot normally.
Pray (actually I used ddms watch all the boot messages)
Play.
New v Old SPL/Radio
HBOOT Radio Context Type Security SPL Maker Fastboot USB
1.33.0006 2.22.19.26I
Stock
Shipping
On
Google
No
1.33.2005 2.22.19.26I
My choice
Engineering
Off
HTC
Yes
1.33.0013d 2.22.27.08
Froyo OTA
Shipping
On
Google
No*
*fastboot erase allowed
Here are the hboot/radio combinations I've had on my ht-03a, beginning with the Docomo stock configuration. After that I used the same radio with an engineering SPL. This was prior to universal androot with no one-click option for 1.6 Donut; An engineering SPL was required to root. Finally, I'm back to a mostly perfect SPL but with an additional 15 MB of real memory.
What most of you will need to do
NOT follow these steps but use them as A Docomo ht-03a SPECIFIC REFERENCE for ezterry's instructions.
If you are unrooted, root your phone and flash a custom recovery. clockwork is fine to start with.
Download and flash an engineering SPL from recovery (e.g., 1.33.2009, though I have been using 1.33.2005). VERIFY MD5 SUM after download and after copying to SD card.
Reboot to fastboot (power + back).
Download Amon_RA recovery (NOTE: that the code in exterry's guide is specific to a dream ht-03a users need a sapphire recovery tagged "G". "cyan" refers to the color scheme, not cyanogen.) VERIFY MD5 SUM!
Using the terminal, cd to the directory with the img file and fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img which assumes you have added fastboot to your path (Instructions for mac/linux here. Windows users on their own.)
Continue as I did.
Restore your previous ROM and flash the "2708" ported kernel of you choice.
Or follow these directions for CM 6.1 after rebooting to recovery.

Categories

Resources