Database Develop

[Q] Help me ! Please problem with bad memory sector on boot partition

Hi all ...
Excuse me for my bad english, i'm french ....
I have a big problem with my nexus one.
I would like to flash the latest cyanogen Nightly but since the V243 i have a error 7 when the phone try to update the boot.img ....
After a long search on the web , i found that the problem is probably that i have a bad sector on my boot partition.
to Fix this problem i have to update my bootloader with the Hboot 0.35 ....
My question are how can i update my bootloader ???? i have tried to flash the PASSIMG_Passion_KT_KR_2.15.1010.2_FRF91_release_signed.zip in Clockword recovery but it say that the package is bad ...
Please help ... thx

Extract the hboot.img from the ROM ZIP.
Reboot to bootloader.
Execute:
"fastboot flash hboot hboot.img".
You need fastboot set up for this. Read Wiki to know, how to set it up.
No need to unlock the bootloader, the IMG is original and signed.

thanks for your answer
but i don't have a hboot.img on the package only a hboot_8x50_0.35.0017_100610.nb0 .
when i tried to fastboot flash hboot hboot_8x50_0.35.0017_100610.nb0 it doesn't work ..
Where can i find this hboot.img ?

I have rename hboot_8x50_0.35.0017_100610.nb0 at Hboot.img
When i try to fastboot flash hboot hboot.img i have the following error
C:\android\tools>fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY [ 0.087s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.210s

By the output I see that your bootloader indeed is still locked.
Oh well, since the simple way didn't work - here's a very long, but certain way:
Download UniversalAndRoot.
Reboot to recovery.
Make a FULL NANDROID BACKUP.
[executing "unroot/restore your Nexus from Wiki, PASSIMG method]
Rename your Korean ROM file to PASSIMG.ZIP
Put it on SD card in root directory.
Reboot to bootloader.
Press whatever needed to flash the PASSIMG.
[end of PASSIMG method]
DO NOT LOGIN TO ANY SERVICE!
Execute: "adb install universalandroot.apk" (replace with the actual APK filename)
Root the phone
Install custom recovery (use flash_image guide from Wiki)
Reboot to recovery
Restore nandroid backup you've made.
After all that, you'll have your HBOOT changed, and the ROM with your data as they were.

Its original korean rom, i think you cant flash it because:
1)Bootloader still locked. Korean nbh signed with key came from KT so there is nothing surprsing it says "Signature verify fall"
2)Custom recovery from RAmon wouldnt flash it too. I have no idea why, but seems like flash original roms just forbidden in RAmon's custom recovery. Dont know about Clockworks one
Where are you device came from?
If its an american one, download latest full american rom and flash it.
I hope it would help.
Another, shortest way: unlock your bootloader and flash whatever you want

[Q] Flashing Hboot - Answered!

I see that most CM7's require the new hboot. I have flashed, pushed, fastbooted, just about anything you can do with ADB and am quite comfortable with it but i can't find anywhere the instructions on just "how to" flash the new hboot to the N1. Is it as easy as placing the zip on the sd and flashing through recovery or is there more to it? I even tried looking in the Wiki and it showed the newest hboot but not how to flash. Thanks in advance!!

I thought it was possible to flash from recovery but after some digging around i'm not so sure now. Best to check with somebody who has done this

I flashed new hboot using cw recovery just this morning. No worries.

Thanks for the reply!

fastboot flash hboot whatever_hboot_you_want.img

Hi, am trying to flash my HBOOT, downloaded d6096cac5e9f.signed-hboot-0.35.0017.zip and currently trying to flash but getting this error:
Code:
$ ./fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
The phone is unlocked and fastboot can see the device, any ideas?

braingravyuk said:
Hi, am trying to flash my HBOOT, downloaded d6096cac5e9f.signed-hboot-0.35.0017.zip and currently trying to flash but getting this error:
Code:
$ ./fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
The phone is unlocked and fastboot can see the device, any ideas?
Click to expand...
Click to collapse
I think what they are saying is you can flash that .zip through clockwork and not worry about fastboot. Try that and let me know if that works for you.

just disable verification check and then flash. worked for me

Just in the process of rooting the phone... just rooted it and about to install RA recovery.. guess I'll flash it through that

Just tried to flash in RA Recovery got the following:
Code:
Install:d6096cac5e9f.signed.hboot-0.35.0017.zip?
Press Trackball to confirm,
any other key to abort.
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:No signature (8 files)
E: Verification failed
Zip verification failed!
Zip isn't signed correctly!
Installation aborted.
Surely if the thing is signed then there shouldn't be a problem with the signature?

Check the md5 on the file...
Sent from my Nexus One using XDA App

Hi,
the md5sum is coming back with:
Code:
b0669d79f3ace07fdd3e1c03d88d2c68 d6096cac5e9f.signed-hboot-0.35.0017.zip

tah318 said:
just disable verification check and then flash. worked for me
Click to expand...
Click to collapse
Try this in AR recovery and see if you can flash then.

In AR recovery main menu select flash zip, then in that menu under "select zip" is toggle verification. Select that once and you will get a warning that unsinged zip can corrupt. then you can choose "select zip" and flash the hboot zip from the sd card.

Jack_R1 said:
fastboot flash hboot whatever_hboot_you_want.img
Click to expand...
Click to collapse
I don't think that's correct. It should be: fastboot flash misc whatever_hboot_you_want.img
Sent from my Nexus One using XDA App

braingravyuk said:
Hi,
the md5sum is coming back with:
Code:
b0669d79f3ace07fdd3e1c03d88d2c68 d6096cac5e9f.signed-hboot-0.35.0017.zip
Click to expand...
Click to collapse
Thanks for the tip, just wondering if anyone can confirm the md5sum, there isn't one shown on the sticky for kernels and radios.
Cheers

braingravyuk said:
Thanks for the tip, just wondering if anyone can confirm the md5sum
Click to expand...
Click to collapse
That's the correct value. Note that the d6096cac5e9f is the prefix of the sha1 checksum.

efrant said:
I don't think that's correct. It should be: fastboot flash misc whatever_hboot_you_want.img
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Im 100% sure its fastboot flash hboot whicheverhboot.img
your way may or may not work but this way does

deleted...

[Q] Flashing the latest and brightest

Hello guys,
I've bought my G1 a couple years back, it's still a functioning machine (although becoming a bit of a heavyweight in the smartphone-division), but I want it to do a little more than what it's capable of now. In other words: I want to update to a newer android version.
I'm still running a rooted cupcake.
In order to update to the latest ROMs, I need a new radio and SPL.
Problem is: I can't seem to flash them through fastboot.
This is the error I keep bumping into:
c:\androidsdk\tools>fastboot flash radio radio-2.22.27.08.img
sending 'radio' (21120 KB)... OKAY [ 6.333s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.661s
Click to expand...
Click to collapse
My current fastboot screen reads:
DREAM PVT 32B SHIP S-ON
HBOOT-1.38.0000 (DREA20000)
CPLD-4
RADIO-2.22.16.19
Feb 28 2009, 18:40:30
I had a lot of trouble trying to flash a custom recovery as well, but was finally able to pull that one off (installed the recovery app, flashed cyagonmod custom recovery and from inside that one I was able to flash RA's 1.7 custom recovery).
So now I'm running RA's custom recovery. I've been pulling my hair over this signing problem for two days now, the few threads I seem to find about it on this forum don't bring me any further either...
My question is: how do I flash my new radio? Can I flash them from recovery?
Many thanks in advance!
The Radio I'm trying to flash is:
http://forum.xda-developers.com/showthread.php?t=831139

I had this issue as well.
My fix was re-rooting (hence both of our phones were S=ON and not S=OFF), installing the Engineering SPL, then following the fastboot commands given in the 2708 kernel installation guide you linked us to.
I believe that was my issue, but I did do the whole process of reverting back to the RC29 version, then doing the normal process of rooting and installing the recovery screen, bootloader, etc.
I believe that'll fix it, and if not, just say so and we'll figure it out!
Just to make sure everything is going on correctly,
Root: http://forum.xda-developers.com/showthread.php?t=442480
SPL: http://forum.xda-developers.com/showthread.php?t=455860

Thank you, that was a very useful suggestion!
I flashed HardSPL through recovery and then tried fastboot flashing the radio and hboot again.
This time I bumped into the following error:
c:\androidsdk\tools>fastboot flash radio radio-2.22.27.08.img
sending 'radio' (21120 KB)... OKAY [ 7.954s]
writing 'radio'... FAILED (remote: partition does not exist)
finished. total time: 7.961s
Click to expand...
Click to collapse
Does this mean I need to format my SD card through recovery first?

Sorry for the few day delay, been busy.
I don't think that you need to wipe your SD card.
The HardSPL is 10.95.3000. You must first flash the the 1.33.2003 SPL.
Make sure it is the 2003 and not 2005, because I do not think that the 2005 is compatible.
Here,
Download this
http://www.mediafire.com/?jmt4nnzttnm
hboot: 1.33.2003 - SPL both in update.zip and img format
hboot: 1.33.2005 - in img format
radio: 2_22_23_02 in img format
1. I'd recommend that you flash back down to RC29 (just to be sure everything is done correctly),
2. Throw all the files included in the g1boot.zip onto your sdcard.
3. Root as you normally would, but use Amon Ra 1.7.0 in stead 1.5.2.
http://files.androidspin.com/downlo...OVERY/&file=recovery-RA-dream-v1.7.0-cyan.img
4. Flash the spl_1_33_2003.zip from the recovery screen.
5. After that is complete, your phone will reboot.
6. Then you want to fastboot flash radio radio-2_22_23_02.img.
7. If that works, which it should if everything was done properly, you will fastboot flash hboot hboot-1_33_2005.img.
8. If everything goes as planned, you should be safe to flash your ROM now.
And just for the record, I believe I actually did mine of the Engineering SPL. If those steps don't work, I'd recommend trying that instead.
Keep me posted on how it works.

This worked like a charm! Thanks for all the help. I'm now on the radio, hboot & ROM I wanted to be
I tried doing the engineering SPL first. That didn't work. Then I went for the 2003 version, through that I was able to fastboot flash the radio and hboot. Then in recovery I first partioned my SD card and then flashed the Biffmod 2.1 ROM.
Testing it out right now Really slow first boot though, not sure if this will be fast enough.

First boots always take a while.
Hows it working for you?
Sent from my HTC Glacier using XDA App

ICS upgrade - boot loop - can't fix - bricked?

I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.

jcr67 said:
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
Click to expand...
Click to collapse
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED?
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.

tpbklake said:
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED? .
Click to expand...
Click to collapse
yep
tpbklake said:
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
Click to expand...
Click to collapse
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.

jcr67 said:
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
Click to expand...
Click to collapse
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes

jcr67 said:
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
Click to expand...
Click to collapse
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers

Drugzy said:
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Click to expand...
Click to collapse
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​

jcr67 said:
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
Click to expand...
Click to collapse
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.

tpbklake said:
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
Click to expand...
Click to collapse
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
HBOOT now says:
*** RELOCKED ***
*** Security Warning ***

jcr67 said:
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
Click to expand...
Click to collapse
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.

Reinstall the HTC ruu
Sent from my HTC Raider X710e using xda app-developers app

tpbklake said:
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Click to expand...
Click to collapse
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks

jcr67 said:
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
Click to expand...
Click to collapse
Yes you should be ok.

tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
yep he will be , during my downgrade i had to relock with security warning and ruu fixed it all

tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
Thanks very much. The stock ICS RUU has now installed successfully. I guess when I originally tried to reinstall it, I had left out the 'RELOCK' step, which is why it failed.
So now I am back to the start (stock ICS + HBOOT 2.02 S-ON), and want to get S-OFF and install your ROM zip. ,What I originally intended to do to get S-OFF was:
1) Unlock the bootloader, flash CWM Recovery, flash SU
2) Run downgrade GB RUU
3) S-off with Revolutionary
4) Install Blackrose HBOOT
5) Install your vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But step 2) failed with an unknown error. (I then tried to install your zip, and the rest is the sad history.....).
So what caused step 2 to fail? Did I need to relock the bootloader first?
Many thanks for your help, tpbklake

Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly.
Sent from my HTC Incredible S using xda app-developers app

Drugzy said:
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly. p
Click to expand...
Click to collapse
That's it. HBOOT is remaining at 2.02.0002 after runme.cmd
Is the device rooted?
y OR n:y
Waiting for device to connect
Device found
Pushing misc_version
2455 KB/s (367096 bytes in 0.146s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Cleaning temp files​
Any ideas anyone?

What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Sent from my HTC Incredible S using xda app-developers app

Drugzy said:
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Click to expand...
Click to collapse
No, I'm unlocked and rooted

Does the stock ruu have superuser installed? If it does I'm outta ideas.
Sent from my HTC Incredible S using xda app-developers app
---------- Post added at 07:58 PM ---------- Previous post was at 07:40 PM ----------
One more thing, I would try flashing another ROM, i came from Niks Sense 4a rom, and the script worked with no issues.
Remember you will need to manually flash the boot.img of the rom as you are S-ON.

jcr67 said:
No, I'm unlocked and rooted
Click to expand...
Click to collapse
Open a command window and then type in the command:
adb shell
If you get a # prompt then your ROM is rooted correctly and the script should run. If it doesn't then the ROM isn't properly rooted and the script will fail.

HTC G1 Soft Brick can access bootloader screen

Hey guys I attempted to breathe some life into my old HTC G1 and after failed attempts I was successful in installing the CM6 but this runs Froyo and I couldn't get certain apps to work, more recent apps just would not install so being new to Android I tried installing the CM7 unofficial but that failed giving me a STATUS 7 so I assumed I needed another kernel so I tried doing that but still STATUS 7 so I installed spl saphire signed and then that went through but phone got soft bricked so now I know I can unbrick my device because I can still access FASTBOOT and I can flash a recovery image and I tried that but also my home button gives trouble so I have to fiddle with it to get it to work and that's the only way I know how to get into recovery. Is there another way for me to get into recovery so I can whipe and flash stuff over as fresh?
BOOTLOADER INFO
DREAM PVT 32B ENG S- OFF
HBOOT-1.33.2003 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Marc 26 2009,23:25:49

adb reboot recovery, but need to be in os for that
Just erase partitions and flash ROM through fastboot
fastboot erase system -w
fastboot flash update ROM.zip
fastboot reboot
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
adb reboot recovery, but need to be in os for that
Just erase partitions and flash ROM through fastboot
fastboot erase system -w
fastboot flash update ROM.zip
fastboot reboot
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did a little searching and found the library of "bricked" phones where I tried this solution
As I said I did it.
FYI, I write this msg for somebody has same problem.
I did "flash_image recovery /sdcard/cm-recovery-1.2.img".
After the reboot, it stucked on the second boot screen, it looped forever and ever and never stopped.
So I Alt+w and then Alt+s but it said can't find update.zip
But it was there.
And I tried some of the builds on this fourm.
I got some other messages, but I don't remember, sorry.
Anyway I coudn't fix it with the way.
I also tried to use another SD card.but it also didn't work.
unfortunatry, I didn't have nandroid backup, cos I didn't care much about the backup.
Then I got signed-dream_devphone_userdebug-img-148830.zip from ****
and I did like this.
C:\bin>fastboot update signed-dream_devphone_userdebug-img-148830.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Then I got this error...
Then I unzipped the file, and I did like this.
C:\bin>fastboot flash boot boot.img
sending 'boot' (1604 KB)... OKAY
writing 'boot'... OKAY
C:\bin>fastboot flash system system.img
sending 'system' (54823 KB)... OKAY
writing 'system'... OKAY
C:\bin>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... OKAY
C:\bin>fastboot reboot
rebooting...
Then I got G1 back!
I hope it can help somebody.
Cheers!
So I got the phone to work and it retained the same bootloader and I got recovery back but now I'm trying to install a stable Gingerbread like EzGingerbread and I still get status 7

Change to amonra 1.7 recovery
Change to 2708 radio
Change to .13d bootloader
Now go back making to recovery and flash ezginigerbread
Now you will be happy
Status 7 can mean a few different thing, but for the most part its incompatibility. If you follow the above you will meet all requirements for the "newer" roms
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Change to amonra 1.7 recovery
Change to 2708 radio
Change to .13d bootloader
Now go back making to recovery and flash ezginigerbread
Now you will be happy
Status 7 can mean a few different thing, but for the most part its incompatibility. If you follow the above you will meet all requirements for the "newer" roms
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I appreciate the help. These files are kind of tough to find though, I'm searching still
I believe I found them here on XDA so I assume I'm flashing with recovery first the radio then bootloader.

Best to use fastboot to flash, recovery, then radio, then SPL
Look for ezterry's 2708+ update thread in the dev section
Sent from my Nexus 7 using Tapatalk 2

demkantor said:
Best to use fastboot to flash, recovery, then radio, then SPL
Look for ezterry's 2708+ update thread in the dev section
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I followed your instructions and I was successful. New life is now in my old HTC G1 Thank you for your patience.

that was easy bro,
RenaldoTT said:
Hey guys I attempted to breathe some life into my old HTC G1 and after failed attempts I was successful in installing the CM6 but this runs Froyo and I couldn't get certain apps to work, more recent apps just would not install so being new to Android I tried installing the CM7 unofficial but that failed giving me a STATUS 7 so I assumed I needed another kernel so I tried doing that but still STATUS 7 so I installed spl saphire signed and then that went through but phone got soft bricked so now I know I can unbrick my device because I can still access FASTBOOT and I can flash a recovery image and I tried that but also my home button gives trouble so I have to fiddle with it to get it to work and that's the only way I know how to get into recovery. Is there another way for me to get into recovery so I can whipe and flash stuff over as fresh?
BOOTLOADER INFO
DREAM PVT 32B ENG S- OFF
HBOOT-1.33.2003 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Marc 26 2009,23:25:49
Click to expand...
Click to collapse
If you want you can unbrick your devices by downgrading it to android 1.0 then apply the official update for the G1 from Google. It will bring you back to the stock HTC G1 1.6 but you can repeat the rooting procedure. That's what I'm doing before, specially if I flashed faulty roms or messing up with the radio and spl combos. Hope that help you.

My sd card does not read.
Then what???
Sent from my SGH-M919 using xda app-developers app

Either its not named properly, not on root of SD, SD isn't formatted to fat32, or sdcard or sdtray is bad
Sent from my Nexus 4 using XDA Premium 4 mobile app

please describe how did you>>> flash_image recovery /sdcard/cm-recovery-1.2.img
RenaldoTT said:
I did a little searching and found the library of "bricked" phones where I tried this solution
As I said I did it.
FYI, I write this msg for somebody has same problem.
I did "flash_image recovery /sdcard/cm-recovery-1.2.img".
After the reboot, it stucked on the second boot screen, it looped forever and ever and never stopped.
So I Alt+w and then Alt+s but it said can't find update.zip
But it was there.
And I tried some of the builds on this fourm.
I got some other messages, but I don't remember, sorry.
Anyway I coudn't fix it with the way.
I also tried to use another SD card.but it also didn't work.
unfortunatry, I didn't have nandroid backup, cos I didn't care much about the backup.
Then I got signed-dream_devphone_userdebug-img-148830.zip from ****
and I did like this.
C:\bin>fastboot update signed-dream_devphone_userdebug-img-148830.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.2005
Baseband Version.....: 2.22.19.26I
Serial Number........: XXXXXXXXXXX
--------------------------------------------
checking product... OKAY
checking serialno... OKAY
checking version-bootloader... FAILED
Device version-bootloader is '1.33.2005'.
Update requires '1.33.2004' or '1.33.0004' or '0.95.3000' or '0.95.0000'.
Then I got this error...
Then I unzipped the file, and I did like this.
C:\bin>fastboot flash boot boot.img
sending 'boot' (1604 KB)... OKAY
writing 'boot'... OKAY
C:\bin>fastboot flash system system.img
sending 'system' (54823 KB)... OKAY
writing 'system'... OKAY
C:\bin>fastboot flash userdata userdata.img
sending 'userdata' (2 KB)... OKAY
writing 'userdata'... OKAY
C:\bin>fastboot reboot
rebooting...
Then I got G1 back!
I hope it can help somebody.
Cheers!
So I got the phone to work and it retained the same bootloader and I got recovery back but now I'm trying to install a stable Gingerbread like EzGingerbread and I still get status 7
Click to expand...
Click to collapse
I have the same problem you had. please describe how did you>>>>> flash_image recovery /sdcard/cm-recovery-1.2.img

This would be putting a recovery on root of SD card and naming it cm-recovery-1.2.img
Then booting into the os and running the command in a terminal emulator, that's it
This will only work if your ROM supports the flash_image binary but more than likely yours does.
If you need further help, please explain your problem fully and give all info about your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app