[q] help me please!! - G1 Q&A, Help & Troubleshooting

I was flashing and setting up my Froyo for Trout on my G1. But when i restarted and rebooted into recovery (Amon_RA 1.7.0 cyan), things suddenly messed up. In recovery, i could only see "Build: Ra-recovery-1.7.0-cyan" at the bottom of the screen. The rest was black
So i did search, and use fastboot to erase recovery in order to reinstall it. But when i put the command "fastboot flash recovery recovery-RA-dream-v1.7.0-cyan.img", it said "writing 'recovery'....FAILED <remote: image type not support> "
Now i have no recovery, so i cannot do anything!
I guess flashing recovery through fastboot is only able with engineer SPL. But i am having the Hboot 1.33.0013d and 2.22.27.08 radio combo. What can i do now?
Please, anyone have idea? Thanks very much!

I believe you can refer back to ezterry's thread on the 2708 radio. He did post a NBH to use when you want to revert.
Powered by Android

Related

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

Go from 3.22.26.17 radio to 2.22.19.26I radio on Rogers Dream

I bricked my first phone in January after a month of reading and then following the wrong instructions -- now I am quite hesitant to do things.
On my second phone, I followed the rooting rogers dream full guide at:
[http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod] This worked, although it seemed to have almost as much lag as the rogers rom.
I did a nandroid restore back to my original rogers rom which I had backed up per the instructions in the above guide. This confirmed that I was not seeing much decrease in lag using cyanogenmod.
I want to try going to the 2.22.19.26I radio and use non EBI1 ROMs.
From reading I think I need to use amon-ra recovery with no R on the end.
The radio,recovery and rom should all be non - EBI1.
In my reading, I haven't seen instructions to do what I am looking for.
I have put some commands together below.
Will this work or brick my phone?
It probably is missing some things. For example see step 6.
=============================
1.
start up recovery : Shut down your phone and, while holding the Camera button on the side of the phone, turn it on
again. [Amon_RAs Rogers Dream Recovery (recovery-RA-dream-v1.5.2R.img)]
2.
enter fastboot: press Send to go into fastboot mode.
3.
fastboot devices (to make sure that fastboot "sees" your device)
4.
fastboot flash radio radio.img [from givemeroot.zip]
5.
fastboot erase system -w
6.
is this needed?
fastboot erase boot
7.
fastboot erase recovery
8.
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
9.
fastboot flash system system.img [htc_system_img_14721.zip, stock android 1.6 will get rid of EBI1 kernel patch]
At this point it shoule be a working phone with 2.x radio and stock HTC Android 1.6.
10.
powerdown phone
11.
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Now the phone will be:
Device: Rogers HTC Dream phone
recovery-RA-dream-v1.6.2
Engineering SPL - HBOOT version is 1.33.2005
Radio - 2.22.19.26I
ROM cm-4.2.x
checksums:
givemeroot.zip md5: 4a58a5702fdf899547011888d9cc066f
recovery-RA-dream-v1.6.2.img - MD5Sum: de9a2562ed8b7ef3b8dab4ecf369fd13
htc_system_img_14721.zip (md5sum: 7a3a2a9bc99a0e8894b62eb9921c000d)
=============================
I don't see anything wrong with your instructions and it should work but there are a lot of unnecessary steps. You don't need to wipe your whole phone to change the radio. Just flashing the latest cm update on top will restore the original kernel therefore getting rid of the EBI1 patch.
enter fastboot: press Send to go into fastboot mode.
fastboot flash radio radio.img [from givemeroot.zip]
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Are you with Rogers? Have you signed the waiver yet? Please post back and let us know if Rogers disconnects your data.
beav_35 said:
I don't see anything wrong with your instructions and it should work but there are a lot of unnecessary steps. You don't need to wipe your whole phone to change the radio. Just flashing the latest cm update on top will restore the original kernel therefore getting rid of the EBI1 patch.
enter fastboot: press Send to go into fastboot mode.
fastboot flash radio radio.img [from givemeroot.zip]
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Are you with Rogers? Have you signed the waiver yet? Please post back and let us know if Rogers disconnects your data.
Click to expand...
Click to collapse
yea, I did this 2 weeks ago.
I followed this:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
only do it in reverse, as in install the 2.x radio instead and install the ebi0 recovery instead. Then boot into recovery and flash a rom (i would suggest superD rather than cyano because you wont have to also flash the google apps)
troubles...
Thank you for the replies.
I am using this phone on Bell. So the Rogers policy troubles don't come into it.
I checked all the md5sums.
Then I did these commands.
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
oops:
K:\1>c:fastboot flash k:\1\system system.img
sending 'k:\1\system' (58570 KB)... OKAY
writing 'k:\1\system'... FAILED (remote: partition does not exist!)
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
c:fastboot flash system k:\1\system.img
As you can see I typed the command incorrectly for the system image the first time.
Then I issued all the commands again from the beginning -- this time I issued the commands correctly.
When I powered down and then started the phone, it was still stuck on the Rogers logo after 25 minutes. Then I pulled the battery and held camera then power. It did start in the 3 androids screen. Good.
I checked and it also will boot into recovery. Good.
So, now I am not sure what I should do to fix this.
Any ideas?
pictures
Additional info:
pictures of my screens are attached.
david1212 said:
Thank you for the replies.
I am using this phone on Bell. So the Rogers policy troubles don't come into it.
I checked all the md5sums.
Then I did these commands.
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
oops:
K:\1>c:fastboot flash k:\1\system system.img
sending 'k:\1\system' (58570 KB)... OKAY
writing 'k:\1\system'... FAILED (remote: partition does not exist!)
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
c:fastboot flash system k:\1\system.img
As you can see I typed the command incorrectly for the system image the first time.
Then I issued all the commands again from the beginning -- this time I issued the commands correctly.
When I powered down and then started the phone, it was still stuck on the Rogers logo after 25 minutes. Then I pulled the battery and held camera then power. It did start in the 3 androids screen. Good.
I checked and it also will boot into recovery. Good.
So, now I am not sure what I should do to fix this.
Any ideas?
Click to expand...
Click to collapse
You for got to flash the base rom or a modified rom. You stopped at the system img so you don't have anythig to boot to. Flash the 1.6 base and you should be good to go.
I don't understand.
I thought that the system.img that I got from the htc_system_img_14721.zip (md5sum: 7a3a2a9bc99a0e8894b62eb9921c000d) is the base android 1.6. I thought this is a full base 1.6 system.
What am I missing?
In recovery just flash the rom you want to use, then it should boot properly.
OK. I applied update-cm-4.2.14.1-signed.zip from recovery and it boots up to CM now.
Thanks.
Great!! Glad you got it working.
BTW There's a newer version of CyanogenMod out.
Yes, newer CM. OK.
Now that I am on the 2.x radio and non-EBI1 recovery, can I use SuperD?
Yes you can use SuperD. Make a nandroid backup, wipe, then flash the update.zip. No need to flash the system.img. There is also a EBI1 port for SuperD so you could have used it before too.
david1212 said:
Yes, newer CM. OK.
Now that I am on the 2.x radio and non-EBI1 recovery, can I use SuperD?
Click to expand...
Click to collapse
you know that you could have used ALL the roms on ebi1 anyway
you just flash a kernel after you flash the rom
It takes literally 2 minutes to make your own kernels with
http://faruq.yandao.com/magicport/
insert rom boot.img (just extract rom to get this), and out comes a kernel !
good news
I am glad I did this.
The phone works better. I don't lose data connection like I did before. The battery life is better.
Now I will make guesses.
The radio works better - has better signal. At my desk, cell reception is not very good. Now the battery is run down less with better connection strength.
My config is now:
-Device: Rogers HTC Dream phone
-Provider: Bell Mobility Canada
-recovery-RA-dream-v1.6.2 [non EBI1]
-spl: 1.33.2005 DREA21000 aka danger spl from rogers_root_unzipme.zip (md5sum: d522e09be7ddec00ef2354533c14cd2f).
-Radio: 2.22.19.26I
-ROM: SuperD 1.9.3 [non EBI1]
questions about downgrading from rogers radio
HI, i'm on a rogers dream using cyan 6.1 and ebi1 kernel. if i downgrade to the 2.22 radio will i have to sign the rogers waiver to get service? i've also heard that the edge network slows down considerably. if there are problems will i be able to go back to the rogers radio?
thanks.
jeremy boyd
Yes, Rogers will disable your data if you don't have the 3.22.26.17 radio unless you sign the waiver. 2.xx is not a downgrade, its a different type of radio. You can always go back to the old radio just make sure your recovery and kernel match your radio.
If you want try this radio. Your phone will be much faster.
http://forum.xda-developers.com/showthread.php?t=831139

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.

G1 stuck on boot, recovery too, fastboot works but can't flash recovery

hi
i am quite desperate after aborting a neverending nandroid backup (created a 2.4gb file Oo) my g1 won't boot anymore. it just stays at the tmobile bootscreen (reboot with red-green-menu still works). even worse when i boot to recovery it instantly freezes there too with the error message :
E: Can't open CACHE:recovery/log
Click to expand...
Click to collapse
the only thing a can do is boot into fastboot. however there i neither flash the recovery:
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
nor boot recovery through fastboot:
downloading 'boot.img' ...
OKAY [ 1.738s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 764.998s
Click to expand...
Click to collapse
actually i did not want to spend days on this... but did i finally manage to brick the g1? i really started thinking it would not happen. maybe it did not like that a talked about getting a new phone today. anyway your help would be appreciated a lot.
thanks
-fleity
phone stats:
Rom:[2.2.2 AOSP] DREAMteam Froyo v1.9.2
recovery: AmonRA 1.7.0
hboot 1.33.0013d
radio 2.22.28.25
You'll need to restore the phone with the orange nbh, then reflash recovery, spl, and radio.
Download this: https://rs766tl2.rapidshare.com/files/422717980/orange-1.58.73.2.nbh
Then flash it through fastboot with "fastboot flash nbh orange-1.58.73.2.nbh"
make sure you don't interrupt it
Reboot into fastboot and reflash recovery, radio, and spl following instructions in here: http://forum.xda-developers.com/showthread.php?t=831139
That thread also has instructions for fixing things if you find yourself without recovery
It's what I just posted. Flash orange nbh and reflash the stuff.
if you still have hboot there is no worries, at least no brick
you cant flash anything with the spl you have but as frankdrey just stated you can flash a .nbh through hboot!
just like the old dreaming.nbh that you more than likely used to root your phone, simply load it onto sd card then turn on phone while holding camera, say yes to update, wait ~5min and bam you have an engineering spl ready to flash amon_ra and pop in a new rom, and when your done go back to the latest radio\spl.
and if you wait a bit you may be able to flash the 1.33.0014d spl - not sure how much better this will be as a whole, but it sounds as if you would get the perks of the 1.33.0013d spl and as an added bonus be able to fastboot flash so no need for the orange.nbh any more... well maybe, soon we should know, going to try it now!
actually fastboot erase system -w already did the trick. thanks a lot for your answers
Unable to use recovery.
This sounds similar to my current difficulty. I have a stock, (supposedly) unlocked? ? Htc G1 with 1.0 firmware RC29.. Can't seem to load anything! Loaded FlashRecs 1.2, 1.4 or Amon Ra's 1.7, and it seems I cannot utilize them. Rooting guied with Dreaming.nbh changes nothing..
Casper Young said:
This sounds similar to my current difficulty. I have a stock, (supposedly) unlocked? ? Htc G1 with 1.0 firmware RC29.. Can't seem to load anything! Loaded FlashRecs 1.2, 1.4 or Amon Ra's 1.7, and it seems I cannot utilize them. Rooting guied with Dreaming.nbh changes nothing..
Click to expand...
Click to collapse
Let's start from the start.
Go to your homescreen and press the enter key on the keyboard, type reboot and press enter again
Sent from my HTC Dream using xda app-developers app

Categories

Resources