yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] BookCase:
Error!!

Followed all Fastboot instructions perfectly, all that went well.

Upon flashing "BiffModV2.1-2708port_S" this is what I get:

Opening update package...
Verifying update package...
Installing update...
Leaving on a Jet Plain
assert failed: getprop("ro.bootl
oader") == "1.33.0013" ||
getprop("ro.bootloader") == "1.3
3.0013d"
E:Error in /sdcard/BiffModV2.1-2
708port_S.zip
(Status 7)

Installation aborted.

Also, I tried re-downloading the ROM+ re-wiped in fastboot to no avail. Also, tried firerat's SpoofSPL.

Still nothing.

Help? :confused:
[G1 Android Development] djmeistro:
when writing the radio it just hang with the red progress bar on the g1 almost done but not!!! help
[G1 Android Development] roalex:
Did you flash hboot ? Should see versions 1.33.0013d when u restart into fastboot(bootloader) Fire's patch isnt good for this coz he will fake your spl to look like the old one btw :)
[G1 Android Development] BookCase:
Yes, I did.
[G1 Android Development] jcarrz1:
Can this be 100% reversed? if so, instructions in OP please... unless the orange nbh does more than just fix recovery and is a full fix/revert?

Thanks.

Also, is it now possible to use the 100% stock boot.img pulled STRAGHT FROM THE dump?

Will that, if you think it'll work, remove the necessity of your patch?

Thanks in Advance to ezterry or anyone else who answers these questions.
[G1 Android Development] roalex:
Well if you did then you have 1.33.0013d which is what those commands look for 1.33.0013 or 1.33.0013d. In that case it might be something about amon-ra recovery you could try using clockwork recovery since you can enable or not the assert scripts.
[G1 Android Development] Firerat:
duh

the spoof SPL is so that recovery tricks the ROM into thinking that you have a compatible SPL

muppet alert !
[G1 Android Development] Firerat:
to trick a rom into thinking you have a compatible spl use the spoof spl zip

ignore the effing muppet above it is dumb
[G1 Android Development] anghellic:
????

Do you have to install these via fastboot? cause I am having one hell of a time getting fastboot running over here.:confused:
[G1 Android Development] Firerat:
when someone makes these flashable zip you will see bricks

give up or follow the OP
[G1 Android Development] roalex:
Hm not sure i get you, isnt your patch faking 1.33.2005 ? if so why would he want to fake that when the roms check for the new spl :)
[G1 Android Development] ezterry:
That port requires hboot 1.33.0013 or 1.33.0013d what do you have installed?

(try not to over complicate things)

If you are using the SpoofSPL use the original Biffmod installer.

I've already spotted the flashable zips..

The problem isn't if you know how to use them.. but people will flash some combination resulting in a non-bootable recovery causing a brick..
[G1 Android Development] Firerat:
lol,

not going to bother, you are noob
[G1 Android Development] anghellic:
Alright, saying screw fastboot, cause I've done just about everything I've read or could find, and still haven't had any success getting fastboot to work correctly.

and that's what I fugured btw.
[G1 Android Development] roalex:
Im not a noob, but i still dont see the logic. You should also watch you language imo.

Upon flashing "BiffModV2.1-2708port_S" this is what I get:

Doesn't this mean hes SPL IS NOT identified as 1.33.0013 or 1.3

3.0013d ?
[G1 Android Development] BookCase:
HaHa so, I flashed the Spoof and it did nothing and now, I tried going back into fastboot and re-doing the whole process only now, I keep getting all kinds of errors:
[G1 Android Development] BookCase:
Okay, thanx, I will revert to the original BiffMod v2.1 ROM.

**Update: Now, im in a Boot loop. :/
[G1 Android Development] jcarrz1:
wow firerat, thanks. you gonna make me read the whole thread now? lol
[G1 Android Development] cj chitwood:
Will 0013d work on the non-Dream board that he has?

--

Sent from my Leader Impression i10 sportin' a newly flashed, more functional, Ice Cream Sammitch...
[G1 Android Development] AndDiSa:
If I remember well Terry wrote some time ago that the 0013d will work only for 32b-boards, but I may be wrong.
[G1 Android Development] ezterry:
The instructions in this thread are for the HTC dreams and 32b magic boards that are nearly identical to the dream.

The SPL works with the Fender/MT1.2 but the benefits of using it and how to install it on such a device is different.

Thus the warning and link at the top of the op

Of course the users problem is simple he doesn't have the 1.33.0013 mt1.2 SPL installed so the upgrade zip usually used by the mt1.2 users fails.. and since the 1.33.20Xx spls unlike the 0013/0013d are *not* intended for the mt1.2 the phone is not fully functional.

In general the MT1.2 only work with 1.33.0013 and 1.33.0013d .. some guides do ask the user to install 1.33.2010 temporarily for an action such as changing the boot screen.. but then fast boot back the original SPL.

So all that is needed is to use fast boot to install the proper mt1.2 recovery and 1.33.0013d (here the file in the dream kit can be used for the .IMG) then continue to install thinks as per MT1.2 related instructions.

The important thing to remember is while there is an overlap in many of the files there are different hardware combos out there such as the fender/my1.2 that have quirks thus its important to ensure the guide is designed for the device used.. or you can find combos that are sub optimal and/or brick the device.
[G1 Android Development] NSingh95:
Hey guys I was trying to download the files in the original links and it seems that the links are dead, does anyone have those files in a different location?
[G1 Android Development] lotherius:
No luck here either.

Looking for "update-1_33_0013-to-1_33_0013d_S.zip" myself... doesn't seem to exist anywhere. Google returns hits on the name, but they're all either references to the same deleted rapidshare file, or to virus-laden fake download sites.
[G1 Android Development] demkantor:
Does This Help
[G1 Android Development] azrash:
I still have the G1 folder in my Dropbox, and I found a folder on SPLs etc, you guys can check it out here http://j.mp/ZSrrYS

Maybe someone can mirror the necessary files and post the mirrors here too.

And don't worry, they are legit :P still have the G1,with a broken battery though.

Hope this'll help

Flowed from my Nexus⁴
[G1 Android Development] AndDiSa:
On http://anddisa.minus.com/uploads you should also be able to find what you need.
[G1 Android Development] Phateless:
I deleted my 32b folder a long time ago, but Dropbox keeps deleted folders in history for awhile. If anyone deleted it recently you can get it back.
[G1 Android Development] hrk:
Everybody show some gratitude to our AndDiSa :)
[G1 Android Development] Phateless:
Where is ezterry now? Haven't seen him popping up on any threads in a while.
[G1 Android Development] AndDiSa:
Not sure if he is still active on XDA, but from time to time he is active on Google+.
[G1 Android Development] Phateless:
His 32b work was amazing, would definitely run his kernels again. My sapphire never ran better than stock froyo, with his 614 kernel, newest radio and hboot, 328min/614max.
[G1 Android Development] lorddavid:
Hi, I have2 old t mobile g1, I repaired and want to give it to someone that like those phones. But i want to install this. The two G1 has cm6 (I install that) HBOOT 1.33.2005 (DREA10000) and Radio 2.22.19.26I and amon ra recovery 1.5.2.

Is safe to follow the guide? I need to install the latest recovery? (1.7) And I always read that it must flash first the radio, and i see that flashed all the things,recovery, radio and spl and then reboot. Its safe to install recovery, reboot, radio, reboot, and finally spl? Its because I feel safer to check if everything flash correctly (special the radio, because I fear a brick).

And I see this update_2.22.28.25_S.zip can I simply install that before? so I will only need to flash the SPL via fastboot? Or it will brick the device?

And finally, I need a permanentsd card with ext4?or can I simply install any rom with this? (because I'm waiting for a sd card that are better quality than the one that sell in my city)

Thanks for your time. I want to give those phone with a good rom, but I have a littlefear because brick problem (I bricked a G1 a year ago :( )
[G1 Android Development] AndDiSa:
You have a fastboot capable SPL installed, so install all needed files using fastboot and there is almost no risk to brick. I would suggest the following steps:

- boot to bootloader

- fastboot flash recovery

- fastboot reboot recovery (only to check whether its working)

- reboot to bootloader

- fastboot flash radio

- fastboot flash spl

- fastboot erase system -w (to clean up everything)

and you should be done.

One additional hint: compare the checksums of the files before flashing them.
[G1 Android Development] demkantor:
Update recovery, then radio, then SPL, just like you said and do it all from fast boot as this is the safest method. And yes you can flash recovery then check then radio then check then SPL to make sure all works.
[G1 Android Development] lorddavid:
Thanks :D so, I will do that way, and check everything individual after flash, (just for be sure), I dont have a microsd so I will search a rom that dont use it.

This is the correct recovery? Dream: recovery-RA-dream-v1.7.0-cyan.img

and this radio update_2.22.28.25_S.zip is the one that i must use right? Because is more recent. And its cwm flasheable but I can just extrack the .img and flash via fastboot right?

Ah, and fastboot erase boot is needed? What exactly do?
[G1 Android Development] demkantor:
That is the most updated recovery so use that (there are some newer cwm but I still recommend amonra)

Yes extract the images

fastboot erase system -w

fastboot erase boot

fastboot erase recovery

fastboot flash recovery recovery.img

(Or whatever the .IMG is named, also feel free to boot to recovery to confirm update but then go back to fastboot)

fastboot flash radio radio.img

(Now you can do a fastboot reboot to check if radio updated)

fastboot flash hboot hboot.img

(Again replace with whatever name you need)

And once all is good reboot to recovery to flash ROM

But here is the kicker, you can't use fastboot to flash a ROM or anything really now with newest SPL so you need to use recovery which means you need an SD card to flash the ROM. You "could" make a fake SD partition and trick your recovery to flash from here but this is highly complicated and if you can just wait until you get a new SD you will be just fine

Best of luck!

Oh and the erase boot just erases the kernel partition, kinda redundant as you will be doing that with the new SPL flash as this partition is reformatted then too, but I'm a sucker for clean wipes :rolleyes:
[G1 Android Development] lorddavid:
Thanks, thats perfect. I was thinking that its going to be more difficult because the radio and hspl that I have, but result to be more easy :D

I will do it when I get home from the work and I will use a old sd card just to flash
[G1 Android Development] lorddavid:
Ok, I do everything today, but, the recover 1.7 isnt flashing anyting, always say: Cant mount /dev/Block/mmcblk0p1 (or /dev/block/mmcblk0)

(no such file or directory)

E: Can't mount SDCARD

In the other phone, the 1gb sdcard works, but in the phone with the new recovery not. And the 4gb sdcard doesnt work too.

Dont Know what can be the problem D:
[G1 Android Development] demkantor:
If you're flashing recovery through fastboot it shouldn't matter if sdcard is working or not for the .img is being flashed from pc

But, did the SD card work on this phone before? Just curious
[G1 Android Development] lorddavid:
Yes,I also try it in the other G1 and work (the 1gb only) but in the g1 with the recovery 1.7,s pl and radio hack, it doesnt mount.

The problem is that the recovery isnt mounting the SD card. And I cant reflash recovery because I have the SPL of this thread

Also I bought 2 4GB microsd and isnt working in any G1 (in the pc its works) 4GB is not compatible?
[G1 Android Development] demkantor:
Hmm, if it worked prior to this then my guess is there is something wrong with the recovery, maybe check to see if the md5sum matches

You may need to flash the orange.nbh (located in op of this thread) then flash recovery again

At this point I would test recovery to see if SD is working then if it is flash new radio and SPL through fastboot, then boot to recovery and flash rom
[G1 Android Development] lorddavid:
But, that will not brick the phone? because I have the SPL from this thread, and orange.nbh downgrade the radio. I read somewhere that flashing a nbh with that, will dongrade the radio and do a brick

If I rename the file, that is not a problem right? Because Always i rename the files.
[G1 Android Development] demkantor:
The orange.nbh is safe to flash (do not rename the file - and md5sums won't match if you rename a file so check before you do)

I have had to use the orange.nbh a few times when screwing with my phone, its a life saver not a phone bricker. Just download, put on root of SD and boot to bootloader (also if this works than SD is for sure good and you know the issue lies with recovery)

Best of luck!
[G1 Android Development] lorddavid:
Ok, will download, My internet is very slow so, maybe I will try when I woke up.

Another question. The 4gb sd card works? The other phone (still with cm6) can read the 1gb sd card, but not the 4gb sd card. Is something else need to do?

Ok, its work, I formatted with my S3. And now its work, But, for partition, The first partition is fat32, then 3xt4 and finally swap right? all primary? I want to prepare the sd.

And if the problem is the recovery 1.7, can i use an older? i was with 1.5.4
[G1 Android Development] demkantor:
Yes that's correct, for the SD

Use whatever recovery works for you, 1.7 had never let me down but if md5sums match and it still fails you use another
[G1 Android Development] lorddavid:
You was right, cant read any sd card, thats strange because i flashed CM6 :/ i will take it to a friend to repair it. Thanks :D

When I come back from the work, i will try this with the other one, if I have any problem I'll tell you

Thank you very much :D

A quick question. I am reading and I Dont know the difference between the 2 radios. Wich one is recommended?

Ok i did all in the other G1. I install rom froyo http://xdaforums.com/showthread.php?t=929678

Use about 700 mb for ext4 and 64 mb for Swap. is that ok?

Thanks :D
[G1 Android Development] hrk:
This isn't true, md5sum has nothing to do with file name, it's computed only on file contents. :o
[G1 Android Development] demkantor:
Fair enough :cool:
[G1 Android Development] amitpmistry:
update htc android 1.6 to 2.2 or latest

version 1.6

baseband 62.50s.20.17u_2.22.19.26I

kernel 2.6.29-0049-gc37df37

build drc92

t-mobile google g1

please help update the android os from 1.6 to 2.2

many thanks

-amit
[G1 Android Development] lorddavid:
Ok, I use a guide that flash via recovery the SPL to enable fastboot, but, they say that is not safe. If someone can tell you a way to flash a fastboot enable SPL, i can help you with the rest of the process
[G1 Android Development] Paul.ryan:
Where did I go wrong?

I was trying to use this guide to get the new radio & hboot on a inactive phone when something went wrong and now I have a real brick ie. phone won't boot in any mode and there is no charge led when connected to charger.

Beginning Info:

Phone "T-Mobile myTouch 3G 32B"

SAPPHIRE RE PVT 32B SHIPP S-ON G

HBOOT-1.33.0013 (SAPP30000)

CPLD-10

RADIO-2.22.28.25

Oct 21 2009,22:33:27

I finally got root and a recovery then installed an engineering hboot (1.33.2010) to get fastboot commands thinking that would make life easier.

Big mistake. Now phone won't boot and I did not know how get hboot 1.33.0013 back.

So I down graded to an earlier (SAPPIMG.nbh) because there were no links to the latest and I had not found this thread yet.

SAPPHIRE PVT 32B SHIP S-ON G

HBOOT- 1.33.0006 (SAPP30000)

CPLD-10

RADIO-2.22.19.261

May 27 2009.19:06:41

Now I'm stuck at the sign in screen with out an active sim card

So I followed this guide (http://xdaforums.com/showthread.php?t=547133) and ended up with a

VodaPhone rom and hboot that would boot but wasn't T-Mobile.

SAPPHIRE PVT 32B SHIP S-ON H

HBOOT-1.33.0009 (SAPP30000)

CPLD-10

RADIO-3.22.20.17

May 8 2009,21:02:32

So in a effort to get back the latest radio and hboot so I could install a custom rom I loaded engineering hboot (1.33.2010)

and proceeded to follow instructions in the OP.

While fastbooting the radio (radio-2.22.27.08) I got this in cmd window.

C:\Android\ADB>fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img

sending 'recovery' (4528 KB)... OKAY [ 1.773s]

writing 'recovery'... OKAY [ 2.574s]

finished. total time: 4.346s

C:\Android\ADB>fastboot flash radio radio-2.22.27.08.img

sending 'radio' (21120 KB)... OKAY [ 5.989s]

writing 'radio'... FAILED (status read failed (Too many links))

finished. total time: 20.610s

As soon as I got the last line in the cmd window the phone shut down never to restart.

Any input as to why this happened is welcome. Fastboot flashing the radio was supposed to be the safest method but it did not work for me.:(

The phone is dead and likely only jtag will revive it and it's not worth that.

I know that I made mistakes early when it would have been easier to recover. However, I would like to know if I made some critical error to cause this or was I just unlucky?
[G1 Android Development] demkantor:
You are correct, fastboot is the safest way and it is rare to get a brick when following this method.

The phone should not have shut off when you got the error, normally it wouldn't so my best guess is you ran out of power in your battery or something to this extent. You probably were just real unlucky
[G1 Android Development] FunkyELF:
I followed this guide.

I didn't flash the recovery because I was already on RA 1.7.0

I did the other three commands though...

Here is my terminal output:

# fastboot flash radio RADIO-2.22.28.25.img
sending 'radio' (21120 KB)...
OKAY [ 6.026s]
writing 'radio'...
OKAY [ 37.364s]
finished. total time: 43.390s
# fastboot flash hboot hboot-1.33.0013d.img
sending 'hboot' (512 KB)...
OKAY [ 0.495s]
writing 'hboot'...
OKAY [ 0.557s]
finished. total time: 1.051s
# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s

My phone never rebooted.

When I try turning it on while a red light blinks very shortly on the top near the speaker.

This also happens when I try turning it on while holding back or home or vol down.

Am I bricked?​
[G1 Android Development] demkantor:
Possibly, but after flashing the radio and hboot you would have wiped all partitions including your recovery, so try to get back into bootloader mode (power on holding camera) if that works you are fine, just use fastboot to flash new recovery and then boot to recovery and flash compatible ROM

Best of luck
[G1 Android Development] FunkyELF:
Thanks for the reply. I don't have a camera button. This is a MyTouch 3G
[G1 Android Development] Paul.ryan:
I think it's "hold volume down and end button" for bootloader mode.
[G1 Android Development] roalex:
If you flashed the HBOOT before it might not work to flash the recovery trough fastboot, OP said something about the limited functions of the new spl. If thats so you gonna have to flash the nbh in fastboot and restart this process, but since it seams im a noob i prolly dont know what im saying here :)
[G1 Android Development] ezterry:
bootloop usually means

1) wrong kernel

2) wrong radio

3) wrong SPL

4) You didn't wipe or restored nandroid before re-installing

* If you try to boot the new kernel on the old SPL it wont even start

* If you try to boot the new kernel with the new SPL but old radio it will not show any boot animation and 3d will not function correctly

* If you try to boot the new radio with the old kernel it will boot loop crashing anytime 3d is enabled (older roms may work with lost of 3d.. least I could get asop cupcake to boot)

Yes the nbh can get you out of bind where you can't boot recovery or system (and its safe enough) but its a painful operation to just restore the original recovery.

Use flash_image over adb in recovery (actually I'm quite sure firerat has a update.zip to remove the custom changes to the recovery image command line as well.)
[G1 Android Development] BookCase:
Okay, I'm gonna do the .nbh thing and re-do the whole process.
[G1 Android Development] anghellic:
I'm having the same issues here, anywhere I put it it says it can't load. Correct me if I'm wrong, but the files have to be somewhere on the computer, or does that even matter? Bare with me I'm noobish.
[G1 Android Development] BookCase:
I put the SPL + Radio and whatever files im flashing through fastboot directly in the *\android-sdk-windows\tools folder. I find thats the best way.

Also, I pasted a cmd (command prompt) shortcut in the same folder and execute it right from there.
[G1 Android Development] ezterry:
Its an NBH file it will install a full orange [france] android 1.1 rom I believe (I haven't used it much my french is not that good)

The good thing about it is it contains HBoot 1.42.2000 which is an enginering SPL..

If you need a radio/hboot image you are more familier with install 1.33.2003 or 1.33.2005 useing the img files as directed here

I can't get you a full restore instructions however without knowing where you are.. My op instructions works for people currently on any radio since I flash the correct radio/SPL/recovery (including rogers users currently on the 3.22.* radios)

Um.. I don't understand what you are asking

If you are asking about the Stock MT3G OTA release.. the boot image was not build with trout support (and the asop code doesn't support the new radio+spl on the dream)

May help .. for reference we are at ~250 downloads of the pre-ported biffmod.. and ~300 of the kernel port ..

I see little confusion about the biffmod so either its working or people or downloading to eat my bandwidth

Ok, here is the thing all dreams are 32b trout boards (this includes rogers dreams)

HTC Branded dreams (such as rogers but also orange france and I believe south African dreams) with HTC's cupcake firmware use the 3.22 (ebi1) radio.

While all google branded dreams and pre-cupcake HTC dreams have the 2.22 or 1.22 ebi0 radios

But all the dream hardware is the same besides what frequencies of 3g it supports (and for some reason if powering directly into fastboot is done by pressing "Back" or pressing "Send")

This means Rogers phones have the same benefit of installing the 2.22.27.08 radio along with hboot-1.33.0013 in gaining an extra 14MB ram. Of course if you have a rogers dream & your provider is rogers, they will probably think you removed the e911 update .. thus cut your data if you have not signed the wavier.
[G1 Android Development] anghellic:
okay, thanks I will try this and post an update. *fingers crossed*

****Update****

This worked, but now it's stuck on "sending 'recovery' <4602kb>..."

Now I have other issues to check out.
[G1 Android Development] jcarrz1:
thanks a bunch. I'll try this.
[G1 Android Development] Firerat:
lol, you muppet
[G1 Android Development] anghellic:
Got it to work kind of...

So I got it to attempt to load the Recovery image but it just sits on 'sending recovery <4602kb>... with a blinking cursor. I let it sit for about 25 minutes and nothing changed...

and a little green rectangle outline pops up on my bootloader screen in the upper right corner...I'm assuming this is a loading progress bar...all assumptions aside I am still not getting it to work...what are some possible causes of this?

EDIT: So I quickly just tried to fastboot erase -w and that just sits there forever as well. I'm hopeless