Database Develop

Please Help "Brick" with Cyanogen's newest upate

My first post but I've been lurking for years. Pretty good with search, etc.
If anyone could help I would really appreciate it. I've been working on this for 12 hours!
I updated to Cyanogen 4.1.999
I successfully installed the new radio and fastboot confirms 2.22.19.261
Here's where I made the mistake in the following directions:
I have CMRecovery Image 1.4
-Go to http://developer.htc.com/adp.html
-DL the 1.6 "recovery image" the file name is - signed-dream_devphone_userdebug-ota-14721.zip
-Then DL CyanogenMod-4.1.99
http://n0rp.chemlab.org/android/expe....99-signed.zip
-put them both on your SD card
-Boot up into CM recovery image 1.4 by rebooting and holding the home button, do a wipe.
-update using any zip to that "recovery image" (signed-dream_devphone_userdebug-ota-14721.zip)
(it should auto reboot install radio then reboot again and load back up to the CMrecovery img screen)
I mistakenly rebooted normally instead of applying the update in the next step. This is when the black screen began.
-Then update any zip usig CyanogenMod-4.1.99 (update-cm-4.1.99-signed.zip)
-Then power on the phone
I am stuck at the black screen of death.
I can fastboot and I've fastbooted the pimp recovery and still can't access recovery. Just get the triangle.
So, during update after new radio I rebooted normally instead of updating with the final build update got a black screen and have no recovery.
I've tried fastboot flash recovery and fastboot update.
fastboot flash recovery is succesful
fastboot update or fastboot flashall give me the "archive does not contain android-info.text and android-product.text" errors.
Any ideas would be greatly appreciated.

this should be posted in Q/A not development.

cingall said:
this should be posted in Q/A not development.
Click to expand...
Click to collapse
Sorry!
Mod please move. Thanks!

if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude

theomajigga said:
if you have access to fastboot, do a fastboot flash everything... from radio, system, and what not (forgetting something)
if that doesn't work... do a fastboot of the radio and boot and system, do everything.
basically do a fastboot of the normal dev 1.6 system....
its on htc's website.... gl dude
Click to expand...
Click to collapse
any ideas on the commands to flash them as flashall? HTC's site has them as separate files so I can only flash the "recovery" file.
I'm sorry to be somewhat of a noob with the actual codes. Could you be more specifc with which files to flash with which commands?
TIA!

Using the HTC website 1.6 "recovery" with fastboot update I get the following:
Error: update package has no android-info.txt or android-product.txt
I can't figure out how to flash the radio or system files in any other way than update in fastboot.

Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.

Also remove your SD card while booting, as prior stuff in your ext3 partition can cause black screens during boot. If that fixes it, you need to reformat your ext3.

The triangle you see is the standard recovery, to access it you need to do alt-L?or alt-x cant remember. To fix you need to flash cm-recovery to do this reboot into the boot loader (power + camera) plug in usb and hit the back button you should see "fastboot" then run
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
seehttp://forum.xda-developers.com/showthread.php?t=523558
then install rom as normal

okay this happened to me as well. I just made sure that I wiped, then started allover again. i had to do it a couple of times but it worked. just make sure that you still have the files on your SD card.
Good Luck!!!!

brnbock said:
Did you erase the recovery? When this happened to me, just installing CM 1.4 from fastboot did not work, I had to erase the recovery then install. Hope this helps.
Click to expand...
Click to collapse
You are a STAR!! Thank you, thank you, thank you!! I knew it was something stupid!
Back at the recovery console! woot!!!
Mods please close this thread!

Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???

took 30 min to post a re.. sorry i was late

fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
That should fix it.

ugh, now I am stuck at the g1 screen after a reboot of a successful update.

reformatted sd and all probs are solved!

mghtyred said:
Please Help "Brick" with Cyanogen's newest upate
Do you still need help bricking your phone???
Click to expand...
Click to collapse
Hi mghtyred (of tmobile forums) welcome to XDA

Fastboot Question

I read recently that to flash the danger spl with the least amount of risk it should be done using fastboot. I have fastboot up and running but I am a little confused on using the commands. Can anyone help explain this to me?

You need to boot the phone into the bootloader (spl), open a command prompt on your computer, and cd to where the fastboot binary is.
From here the commands all start with "fastboot." So to erase a partition from the spl, you would enter "fastboot erase recovery" and substitute recovery for whatever you wanna erase. The partitions on the Dream are: system, boot, cache, misc, userdata, and recovery.
To flash a partition you would enter "fastboot flash [partition] [.img file name]"
The .img file has to be in the same folder as the fastboot binary.
Example: "fastboot flash recovery recovery-AmonRa-1.6.2.img"
This is, of course, just about fastboot itself. I have no idea how to flash the spl from fastboot; I didn't even think it could be done. I would suggest using fastboot to flash a custom recovery, and using the recovery partition to flash the spl zip file.

Interesting
Thanks for the reply, that definitely helps me understand fastboot a little more. I was reading in this thread forum.xda-developers.com/showthread.php?t=655097 (sorry no link) that any radio is compatible with any spl as long as you use fastboot to flash the radio and spl, but im having trouble finding any info on how exactly to do it.
Could it possibly be "fastboot flash hboot dangerspl.zip"?

Jaylen said:
Thanks for the reply, that definitely helps me understand fastboot a little more. I was reading in this thread forum.xda-developers.com/showthread.php?t=655097 (sorry no link) that any radio is compatible with any spl as long as you use fastboot to flash the radio and spl, but im having trouble finding any info on how exactly to do it.
Could it possibly be "fastboot flash hboot dangerspl.zip"?
Click to expand...
Click to collapse
You don't flash zip files through fastboot, extract it and flash the .img file directly, but yes, that command is correct.
fastboot flash radio yourfile.img
fastboot flash hboot yourfile.img
then reboot with:
fastboot reboot-bootloader
You'll probably want a recovery .img handy as well, in case you can't get into recovery after flashing. You can flash that with (predictably):
fastboot flash recovery yourfile.img
If anything goes wrong during the radio or hboot flash, DO NOT POWER OFF OR RESTART!! Come back here and get advice. If you reboot the phone without a valid radio or hboot, you will brick.
Remember there's always a risk involved with flashing these sensitive parts of the system.. if you brick it, I was never here

Sweet thanks for helping me understand. One last thing though, I know for sure I have the 2.22.19.26I radio installed already. Should I flash the new 2.22.23.02 radio first then the spl, or the spl and then the new radio?

The new radio is your choice really.. It's not made a lot of difference to me and you shouldn't have any problems just flashing the spl on top of 26i.

Jaylen said:
Sweet thanks for helping me understand. One last thing though, I know for sure I have the 2.22.19.26I radio installed already. Should I flash the new 2.22.23.02 radio first then the spl, or the spl and then the new radio?
Click to expand...
Click to collapse
The order of flashing radio and SPL, in general, is irrelevant. The exception is that the FIRST thing you should ALWAYS flash is an engineering SPL that MATCHES the consumer SPL that you HAVE installed. After that, order makes NO difference. ALWAYS flash radio or spl using FASTBOOT with the exception of the FIRST ENGINEERING SPL (since there IS no fastboot at this point).
Once an engineering SPL is installed, NEVER install a consumer SPL and NEVER use an NBH file.

lbcoder said:
The order of flashing radio and SPL, in general, is irrelevant. The exception is that the FIRST thing you should ALWAYS flash is an engineering SPL that MATCHES the consumer SPL that you HAVE installed. After that, order makes NO difference. ALWAYS flash radio or spl using FASTBOOT with the exception of the FIRST ENGINEERING SPL (since there IS no fastboot at this point).
Once an engineering SPL is installed, NEVER install a consumer SPL and NEVER use an NBH file.
Click to expand...
Click to collapse
Thats what I thought. After reading your thread I flashed the engineering SPL using recovery and now I plan on using fastboot to install the danger SPL. Is it alright to reboot and use recovery to flash a ROM after the SPL is finished or should I just keep using fastboot?

hmmm, just tried to flash with the command "fastboot flash hboot hboot.img" and I got an error, <remote: partition does not exist>. Any ideas?

1) Make sure you have the right radio on your G1.
2) Download the .zip format of the DeathSPL. If you don't have the right radio, download that, too.
3) Boot into recovery mode.
4) If you don't have the right radio on your phone and you had to follow both sentences of step 2, flash the radio.
5) Nandroid backup.
6) Save the Nandroid backup to your computer.
7) WIPE EVERYTHING.
8) Flash the DeathSPL.
9) Boot your phone normally.
10) Reboot your phone into the SPL to make sure that works.
11) Put the Nandroid backup back in the appropriate folder on your card.
12) Flash the Nandroid backup.

blackknightavalon said:
1) Make sure you have the right radio on your G1.
2) Download the .zip format of the DeathSPL. If you don't have the right radio, download that, too.
3) Boot into recovery mode.
4) If you don't have the right radio on your phone and you had to follow both sentences of step 2, flash the radio.
5) Nandroid backup.
6) Save the Nandroid backup to your computer.
7) WIPE EVERYTHING.
8) Flash the DeathSPL.
9) Boot your phone normally.
10) Reboot your phone into the SPL to make sure that works.
11) Put the Nandroid backup back in the appropriate folder on your card.
12) Flash the Nandroid backup.
Click to expand...
Click to collapse
Have you read anything in this thread or any of the awesome work by ezterry over the past few weeks? FLASHING THE SPL THROUGH RECOVERY CAUSED ALL THE BRICKS.
Anyone looking at this thread for help should ignore this and use the fastboot method detailed above.
Jaylen said:
hmmm, just tried to flash with the command "fastboot flash hboot hboot.img" and I got an error, <remote: partition does not exist>. Any ideas?
Click to expand...
Click to collapse
Er.. I've not come across that one before..

Yeah I just put it on hold for the night. It seems that fastboot only flashes to these partitions, system, boot, cache, misc, userdata, and recovery. I'm wondering if the SPL is stored in one of these. I found an ancient JesusFreke thread where he was talking about it being in misc, but I wasn't just gonna go flashing away at random partitions lol...

Ok, I was looking at the commands in fastboot by typing "fastboot ?" in the command prompt and I notice that it says you can flash update.zip files from fastboot. I'm wondering if I rename the original Danger SPL zip file to update.zip and try to flash it this way through fastboot if it will work. Kind of nervous to try it though, what do you guys think?

Yeah that's why I didn't list "hboot" as an available partition. I've had problems with that too. But I've only ever flashed my spl the one time so I didn't even need it.
I would say it's a bad idea to try to flash the spl while in the spl. That may possibly not turn out so nice. I don't know for certain, mind you, but it just sounds dangerous.

FaJu said:
Yeah that's why I didn't list "hboot" as an available partition. I've had problems with that too. But I've only ever flashed my spl the one time so I didn't even need it.
I would say it's a bad idea to try to flash the spl while in the spl. That may possibly not turn out so nice. I don't know for certain, mind you, but it just sounds dangerous.
Click to expand...
Click to collapse
The running spl is in RAM. No need to worry about this.
@Jaylen: That's an interesting one about the partition not being available. I'll look into that -- it could potentially throw a wrench into things.

I don't think its fastboot error or anything, I'm a little bit new at this but I'm pretty sure I set it up correctly. I can see my device in the command prompt, could I have missed a step? @ lbcoder What do you think about flashing the SPL as an update.zip package through fastboot?
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk

hey all, i'm searching around for a general issue i'm having with getting fastboot up and running. i believe i have everything installed, but when i try to run fastboot.exe, it tells me that another file, AdbWinApi.dll, is missing from my comp. but this file is located in another folder in the SDK, platform-tools.... so the file is there and installed, but is there something i need to do with my PATH in my environment variables or something? any help would be amazingly appreciated... i'm trying to get fastboot up and running so i can run some test builds for developers. i'm running 64-bit Windows 7. thx

yogi2010 said:
hey all, i'm searching around for a general issue i'm having with getting fastboot up and running. i believe i have everything installed, but when i try to run fastboot.exe, it tells me that another file, AdbWinApi.dll, is missing from my comp. but this file is located in another folder in the SDK, platform-tools.... so the file is there and installed, but is there something i need to do with my PATH in my environment variables or something? any help would be amazingly appreciated... i'm trying to get fastboot up and running so i can run some test builds for developers. i'm running 64-bit Windows 7. thx
Click to expand...
Click to collapse
You'll need that file to run in ADB mode.

[Q] fastboot flash doesn't work

I am trying to burn stock ROM images on my Nexus One. I am trying to follow instructions in this tutorial http://forum.xda-developers.com/showthread.php?t=614850 but can't get fastboot to flash my ROM with the images nor erase the userdata partition.
When trying
-> fastboot erase userdata
I get "FAILED (remote: not allowed)" message and when trying
-> fastboot flash userimage.img
I get "sending 'userdata' (837 KB)..." but nothing happens even after 10 minutes... This is the same when trying to flash system and boot partition as well.
I can see my device and reboot it using
-> fastboot devices
-> fastboot reboot-bootloader
My HBOOT version is 0.33.0012 and I have this S-ON (can't quite figure out what this means)...
Any ideas?

When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.

Hollow.Droid said:
When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.
Click to expand...
Click to collapse
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.

smichak said:
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.
Click to expand...
Click to collapse
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?

Did you run 'fastboot oem unlock' first?

Rusty! said:
Did you run 'fastboot oem unlock' first?
Click to expand...
Click to collapse
I am pretty sure my phone is unlocked as I see this open lock icon whenever I reboot it.

Hollow.Droid said:
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?
Click to expand...
Click to collapse
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...

smichak said:
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...
Click to expand...
Click to collapse
There was but I can't put my finger on it at the moment. However I used this exact method a couple of days ago so it's still fresh:
1) Download FRG33 image format from here. Versions above this as far as I know cannot use the PASSIMG.zip method.
2) Rename to PASSIMG.zip and place in the root of the sd card
3) Reboot/boot to bootloader
4) At this point the phone will recognise the zip file and check its contents.
5) When prompted press the volume button to confirm.
This will return you to stock (Minus the recovery but from the sounds of it you don't have a custom recovery image).

You have to extract the FRG33 file and then rename the new file passimg.zip

OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?

smichak said:
OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?
Click to expand...
Click to collapse
Using fastboot, flash the custom recovery of your choice. Using that recovery, flash the custom GB ROM of your choice.

Dream fastboot but no recovery

I was trying to improve the speed and battery life on my HTC Dream. I am using cyanogen recovery 1.7.0R. I changed the radio from 2..22.23.02 to 2.22.28.25. I also upgraded the Hboot from 1.33.2005 to 1.33.13d. After making this change the phone hangs at the boot screen and will not enter recovery mode. I am able to get into fastboot however when I try to flash a new recovery, radio or hboot I get signature verify fail. Is there hope for my phone or is it finished?

jmc7895 said:
I was trying to improve the speed and battery life on my HTC Dream. I am using cyanogen recovery 1.7.0R. I changed the radio from 2..22.23.02 to 2.22.28.25. I also upgraded the Hboot from 1.33.2005 to 1.33.13d. After making this change the phone hangs at the boot screen and will not enter recovery mode. I am able to get into fastboot however when I try to flash a new recovery, radio or hboot I get signature verify fail. Is there hope for my phone or is it finished?
Click to expand...
Click to collapse
Most likely you did not flash recovery and your "old" one is corrupted. Your should have read here how to update, but nevertheless because you are able to go into fastboot, now you have to start over.
1. Read the OP of ezTerry's thread carefully
2. Check the type your phone to identify the nbh-file you have to flash to recover from your current situation (most likely you will need the orange-xxx.nbh)
3. Flash that nbh file using fastboot
Now you have an engineering SPL and you can flash recovery, radio and the 1.33.0013d SPL again.

AndDiSa said:
Most likely you did not flash recovery and your "old" one is corrupted. Your should have read here how to update, but nevertheless because you are able to go into fastboot, now you have to start over.
1. Read the OP of ezTerry's thread carefully
2. Check the type your phone to identify the nbh-file you have to flash to recover from your current situation (most likely you will need the orange-xxx.nbh)
3. Flash that nbh file using fastboot
Now you have an engineering SPL and you can flash recovery, radio and the 1.33.0013d SPL again.
Click to expand...
Click to collapse
Thank you for your help. I followed the link and was able to use the orange.nbh to get the phone to boot then used fastboot to reload a recovery image. Thanks again.

[Q] fastboot signature check failed?

i have the latest radio and hboot for G1 (check sig) and in fastboot mode it says S-on.. now im having trouble flashing a custom splash screen via fastboot and i read somewhere that the S-on may be why.. do i need to downgrade to engineering spl to use fastboot flash method? I keep getting a... <bootloader> checking signature failed! in cmd... but i do have fastboot enabled and working properly..

Did you follow ezterry's on how to install the spl and radio:http://forum.xda-developers.com/showthread.php?t=831139? did u follow these steps for installing the spl?
== Installing ==
(Note: Please Do read the information on the SPL below before actually installing)
1) Take a nandroid backup of your current rom (mandatory if you are trying to move the current rom to the new radio/SPL) to simplify things put any update.zips you expect to need on the SD card now
2) enter fastboot mode
3) flash the files and other operations via fastboot
Code:
fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img
fastboot flash radio radio-2.22.27.08.img
fastboot flash hboot hboot-1.33.0013d.img
fastboot reboot-bootloader
now you will see you have an s-on boot loader with 1.33.0013d as its version
Code:
fastboot erase system -w
fastboot erase boot
please remember while fastboot erase works; fastboot flash does not so be careful *not* to remove the recovery
4) Boot into recovery
5) install a system from backup or as a fresh rom some options are:
Click to expand...
Click to collapse

ldrifta said:
i have the latest radio and hboot for G1 (check sig) and in fastboot mode it says S-on.. now im having trouble flashing a custom splash screen via fastboot and i read somewhere that the S-on may be why.. do i need to downgrade to engineering spl to use fastboot flash method? I keep getting a... <bootloader> checking signature failed! in cmd... but i do have fastboot enabled and working properly..
Click to expand...
Click to collapse
You have a perfected SPL installed on your phone (0013d), so you do not have full fastboot support and you are not able to flash a custom splash screen.
If you want to downgrade, flash the orange-xxx.nbh file from Terry's thread (can be found in my signature) and after that you will have an engineering SPL. With this you should be able to flash a custom splash screen. After that you can go back to 1.33.0013d/2.22.28.25 ... everything can be done using fastboot, so your risks to brick your phone are very(?) limited ...

yeah i figured it out thanks guys!! had to temp flash the engineering spl to do what i wanted.. than jus re flashed 0013d everything is all set thank you guys though!!!

I accidentally removed the recovery... and still having same issues with S-ON with HBOOT-1.33.0013d.... need help getting recovery back on my phone. have new radio too.

hubby0925 said:
I accidentally removed the recovery... and still having same issues with S-ON with HBOOT-1.33.0013d.... need help getting recovery back on my phone. have new radio too.
Click to expand...
Click to collapse
You (as I see was indicated in the thread before) go to the 2708+ kernel/SPL/Radio thread:
http://forum.xda-developers.com/showthread.php?t=831139
This has all the information on the use of 2708/2835 radios and the 1.33.0013d SPL including a section on what to do if you loose access to both the system and recovery in the '== Important Information about 1.33.0013d ==' section [Its important to read that section anyway if you are using 1.33.0013d]
If you still have access to boot, just use flash_image or rom manager to restore your recovery image.