Here's the story:
So, got another G1, came with 1.33.2005, and an EBI1 radio. So I flashed AmonRA - R, and the updated EBI1 radio to avoid Rogers harassment. Then I went into the recovery; booted fine. Then I flashed the HTC 1.6 ota update, then CM update, then the EBI1 kernel. Little did I not know, I wasn't supposed to flash the OTA since that would update the radio. Now the phone won't boot into HBoot or Recovery. I do however get the Blue LED from holding the trackball down. Anyway, is my phone permanently screwed? Or is there a way out of this?
SilentTweak said:
Here's the story:
So, got another G1, came with 1.33.2005, and an EBI1 radio. So I flashed AmonRA - R, and the updated EBI1 radio to avoid Rogers harassment. Then I went into the recovery; booted fine. Then I flashed the HTC 1.6 ota update, then CM update, then the EBI1 kernel. Little did I not know, I wasn't supposed to flash the OTA since that would update the radio. Now the phone won't boot into HBoot or Recovery. I do however get the Blue LED from holding the trackball down. Anyway, is my phone permanently screwed? Or is there a way out of this?
Click to expand...
Click to collapse
sounds like a brick
SilentTweak said:
Here's the story:
So, got another G1, came with 1.33.2005, and an EBI1 radio. So I flashed AmonRA - R, and the updated EBI1 radio to avoid Rogers harassment. Then I went into the recovery; booted fine. Then I flashed the HTC 1.6 ota update, then CM update, then the EBI1 kernel. Little did I not know, I wasn't supposed to flash the OTA since that would update the radio. Now the phone won't boot into HBoot or Recovery. I do however get the Blue LED from holding the trackball down. Anyway, is my phone permanently screwed? Or is there a way out of this?
Click to expand...
Click to collapse
At present its a brick; as in there is at this point in time no known way out of that state.
Work is being done to attempt to break out using "blue light mode"; but this has not succeeded yet.
The OTA.zip has logic in addition to flashing the radio/boot image; to force the SPL (which is working btw) to go immediately to recovery. Ignoring any requests to enter hboot/fastboot modes.
Related
Here's the story:
So, got another G1, came with 1.33.2005, and an EBI1 radio. So I flashed AmonRA - R, and the updated EBI1 radio to avoid Rogers harassment. Then I went into the recovery; booted fine. Then I flashed the HTC 1.6 ota update, then CM update, then the EBI1 kernel. Little did I not know, I wasn't supposed to flash the OTA since that would update the radio. Now the phone won't boot into HBoot or Recovery. I do however get the Blue LED from holding the trackball down. Anyway, is my phone permanently screwed? Or is there a way out of this?
SilentTweak said:
Anyway, is my phone permanently screwed?
Or is there a way out of this?
Click to expand...
Click to collapse
1. Yes
2. Not currently
We have yet to find a way out of this... Sorry.
Hi,
I'm on MoDaCo r21 (FRF91). Every few days, I get alerts that there's an update. There seem to be some problems that haven't quite been worked out with MoDaCo r22 (FRG83), so I'm holding off on upgrading. So every few days, I get an alert that there's an OTA update available. I go into /cache and delete the .zip file that was downloaded, then "accept" the update, which of course fails because the file isn't there, and then I proceed on my way until it happens again.
Up until recently, it always said the update was "Android 2.2 Update" or something and the filename was
Code:
c8847c98b948.signed-passion-FRG83-from-FRF91.c8847c98.zip
This was, as far as I know, a few minor fixes and was just an update to the /system partition.
Now, I've just noticed that the file I was pushed is
Code:
d6096cac5e9f.signed-hboot-0.35.0017.zip
and this appears to have an hboot.img embedded in it. I don't know how to crack open an .img file, so my question is, what the heck is this update? The update screen says "Update 1 of 2: This is the first part of an update and it must be installed before the second part is installed" or something like that.
I'm getting paranoid here. Is this some trick from HTC to get me to update my bootloader with a locked-down one like the G2?
The thing I love about the Nexus One is that the whole thing can be legitimately unlocked -- so I hope there's not an update that will change that.
I actually rooted my phone without doing the "fastboot oem unlock" as I didn't want to void my warranty (despite the many claims that HTC still honors claims for things that are clearly hardware-related), but I've always felt safe that I have that option in my back pocket in case I ever screw up so bad that I can only recover via fastboot.
Or maybe this is just a new radio and I'm over-reacting
Can anyone confirm? Or point me to some info on how to examine an .img file?
Thanks
I got exactly the same update and I thought it was Gingerbread since this became a 2-part update. I searched around and the new hboot has always been shipped with Korean and SLCD Nexus One(s), and I guess they wanted to update our hboot to the new one as well.
I updated to it, but well you can still install custom roms when you're rooted, and it doesn't affect your current rom as well. So I guess it's perfectly fine, or if someone else wants to correct me.
My bootloader now displays:
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-4.06.00.12_7
Oct 12 2010,14:33:16
Thread moved to Q&A.
I never got an on-screen prompt about it but I did notice while watching ddms after flashing a new rom that hboot-0.35.0017 was pushed to my phone and the verification failed.
I'm oem fastboot unlocked and running CM 6.1 nightly build 262.
Has anyone determined the new bootloader is needed for future things? i.e. Gingerbread?
can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?
hayden1987 said:
can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?
Click to expand...
Click to collapse
Yes, it is safe. And no,you will not lose root.
hayden1987 said:
can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?
Click to expand...
Click to collapse
Well, so far, the 0.35 hboot won't let you use the PASSIMG method to re-image your phone, and doesn't appear to like Amon Ra 2.0 (not confirmed, but I've noticed a few issues). I've also seen potentially related problems with fastboot privileges...
Sent from my Nexus One using XDA App
The other day my girlfriend broke her Blackberry and I said I would lend her my old G1, now obviously I don't use it very often but I knew I would have to flash it because I remembered putting Honeycomb on it when it came out. My predictions were confirmed when I turned it on so I went and found a download of CM5 (Most stable ROM I ever used on it), but very stupidly
of me I didn't do a nandroid cos I figured I wouldn't need one as I didn't care about the Honeycomb I put on it.
Getting to the point, when I flashed CM5 it just got stuck boot looping on the bootloader, I tried some other ROMS I found in the form with G1compatability but they all boot loop too! I have no idea what radio I have etc since I don't use it often and I have no OS to check, any suggestions on how to just get it to boot.
*Flashing with Clockwork mod 2.5.something
Sent from my Desire HD using XDA App
when your phone is off.. hold camera and power to start in boot loader so you can see wat radio and hboot yu have
Thanks, Completely forgot the key combo, was trying Power + Volume down because thats what it is on my Desire HD.
I have 1.33.2005 hboot and radio 2.22.27.08, now what?
didge3 said:
Thanks, Completely forgot the key combo, was trying Power + Volume down because thats what it is on my Desire HD.
I have 1.33.2005 hboot and radio 2.22.27.08, now what?
Click to expand...
Click to collapse
k so now you need a rom compatible with the radio you have.. most of the recent ones that say 27.08 or 28.25 and you should update your hboot to 1.33.0013d.... ooor you could completely un-root it and get back to stock firmware.. what do you want to do?
ldrifta said:
k so now you need a rom compatible with the radio you have.. most of the recent ones that say 27.08 or 28.25 and you should update your hboot to 1.33.0013d.... ooor you could completely un-root it and get back to stock firmware.. what do you want to do?
Click to expand...
Click to collapse
I dont want to unroot and put it on stock in case I want to flash other ROM's to it later (like the Honeycomb that was on it)
The only issue is I have no idea how to flash the newest hboot or where to find it.
Links to the latest hboot and how to install? can I just flash in CWM or do I need to use adb?
didge3 said:
I dont want to unroot and put it on stock in case I want to flash other ROM's to it later (like the Honeycomb that was on it)
The only issue is I have no idea how to flash the newest hboot or where to find it.
Links to the latest hboot and how to install? can I just flash in CWM or do I need to use adb?
Click to expand...
Click to collapse
Ezterry has an excellent guide with links to the latest radio and SPL. You'll need fastboot. You can find it here: http://forum.xda-developers.com/showthread.php?t=831139
didge3 said:
I dont want to unroot and put it on stock in case I want to flash other ROM's to it later (like the Honeycomb that was on it)
The only issue is I have no idea how to flash the newest hboot or where to find it.
Links to the latest hboot and how to install? can I just flash in CWM or do I need to use adb?
Click to expand...
Click to collapse
i use this one http://forum.xda-developers.com/showthread.php?t=983834
Thanks, flashed new hboot and radio and flashed a plain 2.2 ROM, runs fast and seems stable, now just to teach my girlfriend how to use android..... Guess I cant ask for help with that... hehe
Hi all.
I have a rogers HTC dream that I need to unbrick. It is rooted, but I have no recovery at all. Have tried several times to install a recovery, to no avail.
Maybe if I follow an unbrick instructions, I will be able to salvage this device.
Right now, it is still working properly, but I cannot do a factory reset because of no recovery. Need to do a factory reset because I am giving it to a family member.
Thanks
Heeter
Sent from my Nexus S using xda premium
Any help would be greatly appreciated.....
Thanks
Heeter
Heeter said:
Any help would be greatly appreciated.....
Thanks
Heeter
Click to expand...
Click to collapse
Is it a custom rom and you just want to reset the phones data (ie wipe your personal data)? This is prob best as long as the current custom rom worked well for you.
Regardless go into fastboot (turn on holding camera) tell us the radio/spl, then if possible tell us what rom you are using (if known) and more importaint are you rooted?
Edit: nvm about the rooted question, the rest applies
Good Morning ezTerry
It is a completely factory stock rogers Dream (factory ROM). I did use the one-click root and that worked.
I never had a chance to put in another recovery or spl/radio. Cannot at all boot into recovery.
I can boot into fastboot, and I will post what I see when I get home.
BTW, on a side note, I would like to say thanks for all your work, ezTerry, I have been using all your releases for my other HTC Dream.
Heeter
Heeter said:
It is a completely factory stock rogers Dream (factory ROM). I did use the one-click root and that worked.
I never had a chance to put in another recovery or spl/radio. Cannot at all boot into recovery.
Click to expand...
Click to collapse
If that's the case you just want to flash the rogers e911 patched nbh:
Information on the xda wiki
Of course if this phone is going to be used off the rogers network it might be kinder to root it, install the 2708+ radio SPL and my the MT3G ota froyo port to the dream.. As that is still quite stock but gets rid of the rogers e911 patched radio that has very unstable 3g support. (And the rom is easier to deal with)
If it will be used on rogers network there is not much to be done, rogers still scans once a month for those using any radio besides the new rogers one and cuts the data.
ezterry said:
If that's the case you just want to flash the rogers e911 patched nbh:
Information on the xda wiki
Of course if this phone is going to be used off the rogers network it might be kinder to root it, install the 2708+ radio SPL and my the MT3G ota froyo port to the dream.. As that is still quite stock but gets rid of the rogers e911 patched radio that has very unstable 3g support. (And the rom is easier to deal with)
If it will be used on rogers network there is not much to be done, rogers still scans once a month for those using any radio besides the new rogers one and cuts the data.
Click to expand...
Click to collapse
Hey, a million thanks for this, ezTerry.
I will post later today as to the outcome of this reflash.
As it is right now, it is getting the 3G from rogers right now, if this works out, I am going to root it, and install the 2708 and radio SPL as well as that froyo port. I am sending it to a family member in Montreal, also on Rogers.
Heeter
Well this is a kicker,
The Dream is saying "Fastboot USB" on the screen, but I cannot connect to it through fastboot.
I know my fastboot is working as my other phones are showing in the fastboot devices list.
I am using my terminal on my Linux workstation (LinuxMint12)
Maybe my fastboot is too new for the older devices?
Anyways, here is my Fastboot Info:
Code:
Dream PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
Jun 2 2009,21:33:16
Is there a way I can do this through the SDcard?
Heeter
as a DREAIMG.nbh on the root of the SD as usual will also work...
Never had a problem with older vs newer fastboot builds.. hope its not an indicator of a larger issue.
Thanks for sticking with me, ezTerry
I renamed it to DREAIMG.nbh, and now it is loading off sdcard.
Yahoo!! I got a recovery, and a factory reset.
I still can't fastboot into the phone still.
What now?
Thanks again,
Heeter
I will be bringing the Dream to work with me,
I will install the SDK on my Windows7 workstation, hopefully fastboot can work from there.
Which directions should I follow now for the flashing of the radio spl & cwm?
Thanks
Heeter
I am now into fastboot!
How do I turn off the security, because I cannot flash anything (Remote: not allow)
Thanks
Heeter
Heeter said:
I am now into fastboot!
How do I turn off the security, because I cannot flash anything (Remote: not allow)
Thanks
Heeter
Click to expand...
Click to collapse
You can't on the stock split, to flash the NBH you were supposed to first switch to RUU mode." (Via 'fastboot oem rebootRUU' as per the unrooting instructions on the xda wiki)
However if you flashed the nbh you no longer need fastboot yet, just check 'fastboot devices' to make sure its working
To root and follow the rooting instructions on the same xda wiki page I sent earlier, no shortcuts..
After you are rooted and 1.33.2005 is installedyou can install the extra memory radio by fastboot http://forum.xda-developers.com/showthread.php?t=831139 (again no shortcuts)
However since you are giving this to someone else on the rogers network I *DON'T* recommended changing the radio since their data will be blocked on the first business day of Jan unless they successfully sign the rogers e911 wavier. Because of this its best the recipient understand what this means.
Thanks, ezterry
I am leaving it stock and shipped it out today.
Thanks for all your help last couple of days.
Heeter
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
surgehtc said:
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
Click to expand...
Click to collapse
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
majmoz said:
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
Click to expand...
Click to collapse
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
surgehtc said:
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
Click to expand...
Click to collapse
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
majmoz said:
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
Click to expand...
Click to collapse
I did get it from the verizon section.
But I have no custom recovery and no fastboot
I can't adb sideload either.
What should I do?