Database Develop

[Q] What is d6096cac5e9f.signed-hboot-0.35.0017.zip ?

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

[S-OFF] AlphaRev X Open Beta

http://alpharev.nl/x/beta/
Thought you might like to know it's now open, have fun

You're on XDA , welcome back. Great to see the public open beta is out too!

But...! It seems to be only for Hboot 1.x.x users!! If i have bootloader v 0.80.0007, i can't get s-off???

I have some trouble obviously after getting S-off, how do you root then on froyo ?
Unrevoked tells me firmware could be too new... I'll go through their FAQ perhaps some answers are there xD
S-off Process is flawless
You guys Rock !! Thanks !

great great news!
2morrow morning i will s-off my gf's wildfire!

can anyone post the step one by one? cz i dont really get. After i opened the alpharevx -> put the code-> Acquiring root (method 1) ...... unknown command
Then nothing

IT WORKEDDDDDD!!!! thanks to alphareev team

Why it not compatible with HBOOT 0.80xx ?

Dilemmaaaaaaaaaaaa...
The S/N start with HT0 or HTO???

IvanDeadWolf said:
Why it not compatible with HBOOT 0.80xx ?
Click to expand...
Click to collapse
0.80 was not the problem ,we had root or close
Anyway its worth updating your hboot with an official froyo (now)
i like the orange text and my new ability to flash a screen
thanks to alpha

Hi, how long will this public beta be?

Could use at step by step instruction?
I boot into HBOOT and run alpharevx.exe, a command prompt opens telling it's "Waiting for device"??
About a week ago I tried running Unrevoked, which ended up with the known error about hardware being to new - so I'm sure I have the correct HBOOT usb-driver.
I'm on 64-bit Windows at the moment - could it be that??
Please, anyone advice??
EDIT:
This was a question from a newbie early in the morning :d - Solved!
The utility should be run with Android loaded, not i HBOOT mode, and it helps enabling USB-debugging
After getting S-OFF I followed these instructions: http://forum.xda-developers.com/showthread.php?t=1130044
Finally I flashed: http://forum.xda-developers.com/showthread.php?t=957140
I feel pretty fine right now

Alpharev team promised at begining S-OFF for hboot 0.80.. Why they have not released it?

Some Questions to those who know.
I'm currently on HBOOT 0.80.XX having Rooted Hybrid Rom V6.
1. Do I need to update to HBOOT 1.00X to be able to use Alpharev X - if not - which option should I choose in dropdown menu on Alpharev X Beta page..? As it only shows two options - both being 1.00X
2. Do I need to Re-Root after alpharev X - or will my previous root stay (if I can use it without updating to HBOOT 1.00X)
3. Again - Do I need to Re-Flash Rom after alpharev X - or will my previous rom stay (if I can use it without updating to HBOOT 1.00X) *prays*
4. Can I use a (Fastboot) Clockworkmod that still uses Amend - rather than edify? Or is there one that can support both? As I quite dislike edify.
5. Will my old Clockworkmod be overwritten? (2.5.0.7)
I posted these questions in a few places as I haven't the faintest clue - which one is the right place to post them in...apologies for that.

morbosity said:
0.80 was not the problem ,we had root or close
Anyway its worth updating your hboot with an official froyo (now)
i like the orange text and my new ability to flash a screen
thanks to alpha
Click to expand...
Click to collapse
So you're telling me to update my phone with the last ruu, this will update my hboot as well, then i use the alpharev tool and then i root again?
0.80 still does not have S-OFF so this is a problem!

Hello,
Here is a short Guide to get S-OFF if you are at HBOOT 0.80:
1. Make a full Backup of your current ROM.
2. Download RUU Buzz Froyo HTC WWE 2.22.405.1 Radio 13.55.55.24H 3.35.20.10 release 160191 signed.exe
3. Connect your Plhone to your PC and Install it, after 10 minutes you are on HBOOT 1.01.0001
4. Download Alpharev follow the instructions and install.
Now you are S-OFF!´
You ony have to Restore your ROM and enjoy!
Sorry for my bad English.

1. not sure, but i did and it worked, i used
RUU_Buzz_Froyo_HTC_WWE_2_22_405_1_Radio_13_55_55_2 4H_3_35_20_10_release_160191_signed.exe
from
http://shipped-roms.com/index.php?ca...ile&model=Buzz
2.yes, follow this to get clockworkmod installed:
http://forum.xda-developers.com/showthread.php?p=14693680
ur phone needs to be in hboot 4 this to work
3. as far as i can tell not by defoult, but u installed ruu so yes
4. not sure, but i think there shouldnt be a broblem
5. if u run ruu, yes, hence fastboot method
i did a nand backup, installed ruu, ran alpharev, fastbot flash recovery, restoring nand backup as i type, and thats it.
another thing i was careful about is after nand backup, i switched to original sd card, so the ruu wouldnt put sense and other stuff on my primary sd. i switched back after flashing recovery. gl

Thank you!

I keep trying to enter my beta key and it says the key is invalid :S:S

Hmm I just flashed my phone with the new Hboot, ran alpharev and installed clockwork.
It worked perfectly, so maby you are somehow entering the wrong code...
Anyways It worked like a charm for me
(Windows 7 ultimate x64)

[Q] Where to find N1 OFFICIAL Radios?

[DISCLAIMER]
I HAVE searched already, and the only result I get is a .12 radio that is NOT signed properly. I don't want this version.
[/DISCLAIMER]
Anyways, I was wondering if anyone could point me into the direction as to where to get an OFFICIAL signed radio, particularly the .12 Korean version. All links I can find to are not properly signed. I was planning to set up BLACKROSE and it requires the .12 radio to be flashed without disabling signature verification. Thanks much.

http://forum.xda-developers.com/wiki/Nexus_One/Radios

Androidity3000 said:
I was planning to set up BLACKROSE and it requires the .12 radio to be flashed without disabling signature verification.
Click to expand...
Click to collapse
Blackrose does not require the 5.12 radio. The only requirements (found in the first post of the development thread) are:
Code:
Windows PC or Linux PC
USB Debugging(ADB) ON
Connect USB before install
HBOOT 0.35.0017
The 5.08 radio (which most N1s are running) tends to be the best radio for people outside of Korea. In fact, it is the one that google released with the Gingerbread OTA update, and I am sure they did a lot of internal testing to determine which radio is the best.

Signed for "fastboot flash" on locked bootloader? Or signed ZIP to flash through recovery?
If you mean bootloader: 5.12 was only released for Korean version, which is different from Google main line (SW-wise only, since it's the same phone). Thus, if it's not accepted by your current bootloader - you won't get it Google-signed anywhere, and you won't be able to flash it through fastboot with locked bootloader, if that's what you're looking for. Last version in Google updates is 5.08.
On the other hand, if you mean signed ZIP for flashing in custom recovery - then it's funny, because ANYONE can sign those ZIPs. Anyone. I can sign it for you with a testkey (that's all that recovery needs). Would that make it more "official"?
In any case, as mentioned before, you don't need it. You need 5.08 and above.

Thanks for the link. I will just use the 5.08 version then. I thought I read that .12 was needed; however, I guess I am mistaken. Glad to know. And yes, I was planning to flash through recovery. Again, thanks much!

In that case, you can flash 5.12 as well. Being signed doesn't make the update.zip official, since all the files for flashing in custom recovery are signed by people, just like myself. 5.12 radio is just as legitimate as 5.08, and both update.zip weren't signed by Google anyway. You do need to verify the md5sum before flashing, though.

htc freezing on white/logo startup screen

Hi, I tried to update the system on my phone and when it did a reboot after updating and installing, it is freezing on the white/logo startup screen. how can i proceed...?

Remove the battery to turn the phone off, and when turning back on, hold down the power+volume up buttons. This will put your phone in hboot mode and allow you to reflash your ROM from there.
Good luck.
Sent from my Incredible S using xda premium

thanks. Yes i did make it to that step. now i need to flash the official rom for my model which is S710e, but i found so many links that i'm confused which one is the official...can i have some indication...
thanks in advance

If you flashed a custom rom and it is stuck in white screen with logo, your boot partition is messed up. But no worries you can fix it.
Extract the boot.img file out of your custom rom (zip-file).
download the SDK files
put the boot.img in the same folder as the files
Boot phone in fast boot
connect phone through usb with a computer
open command prompt on the pc an go to folder
use command fastboot flash boot boot.img
wait 2 secs
reboot
whole proces takes maybe 10 min, very easy to do.

no i did not flash a custom rom. i just did a system update which was prompted to me on the phone itself; when i did this it got stuck on reboot. then i did a factory reset but it was in vain.
at this point what i want is to have my phone back as it was in the beginning...so I wish to know how i can flash a stock rom so that it will become like brand new. thanks.

atlam83 said:
... I wish to know how i can flash a stock rom so that it will become like brand new. thanks.
Click to expand...
Click to collapse
First, you have to know what your mainver is:
Boot into fastboot, open a cmd window in windows and type this:
Code:
fastboot getvar mainver
This will give you your mainver (e.g. 2.12.708.4)
And go here: http://www.filefactory.com/f/e45d6fe3dcf51228/
You'll find shipped rom list. The filenames are in format like this: RUU_[name][mainver][radio_version]_signed.exe You must select ones with WWE prefixes (for multi-language support) and higher mainvers than yours! For example, if your mainver is 2.12.708.4, then you can select RUU_Vivo_Gingerbread_S_Sasktel_Canada_WWE_2.33.669.2_Radio_20.2810.30.085AU_3805.06.03.16_M_release_203211_signed (this one's mainver is 2.33.669.2) in the shipped rom list.
Once you've downloaded, you'll face another problem: Flashing.
Flashing is not a real problem but needs some trickies.
The question: Have you rooted your phone?
If yes, this thread is your flashlight to enlighten your way..
If no, you have to obtain a goldcard. A goldcard is a special microSD which prevents the phone to check cid (Customer ID) while trying to flash an original rom. If you haven't created a goldcard yet and cannot boot your phone properly, find another Android based phone and insert your microSD card into it. Then read this thread to create your gold card. Once you've created your goldcard, then it's so easy for you to flash your original rom. Follow the steps in the link above (explaining how to flash).
hth.
-R

i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.

atlam83 said:
i downloaded and flashed a stock rom on my phone by placing the PG32IMG.zip file in my sd card . the update was completed successfully however the phone still got stuck in the htc startup screen. any ideas what the problem might be?
I haven't tried the goldcard yet however.
Click to expand...
Click to collapse
Did you previously use Revolutionary to gain S-Off on your phone. If so by trying to install the OTA update, you now have a HBOOT ROM mismatch. The OTA update requires that the HTC HBOOT 2.00.0000 be installed, but the Revolutionary S-Off HBOOT prevented the OTA from overwriting the hboot, thus creating the situation you are in.
Follow steps 1 - 2c on this thread.
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
The find the OTA file on your SD card and extract the file firmware.zip.
Copy this to the root of your SD card and rename it PG32IMG.zip and then reboot into bootloader and it should reflash the correct HBOOT and you should be good to go.

Thanks very much tpbklake, I managed to solve my issue following the thread you indicated. its been 3 weeks since last i used my mobile. Send it to various ppl including HTC (which did not want to fix my mobile) and no one fixed it. have tried that thread and now its fine working again )

HTC freezing on thie logo startup screen
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(

Aniok said:
Hi
Im new here I had read the all similar threads that the forum found but no one could help me to solve my problem.
Im using Android 2.3.3 and
Sense 2.1,
HBOOT : 6.13.1002
My baseband version is 3822.10.08.28_M
I recived an OTA update with Android 2.3.5 and Sense 3.0 and I proceeded with it, everything goes well until the phone restarts and stay freeze in the green HTC logo. Nothing else happens.
plz give me a link for the official ROM for Incredible S 710e.I tried the links but it didnt work for me...
hope someone could help me.. :'(
Click to expand...
Click to collapse
All you need to do is go to the Development section and upgrade from Revolutionary HBOOT 6.13.1002 to BlackRose 2.02.0002. That will allow your phone to boot.
http://forum.xda-developers.com/showthread.php?t=1509236

Thanx
..
Sent from my GT-I9300 using xda premium

[Q] How to update firmware?

Hi,
I have been using Cyanogenmod, pretty much since I got my phone. I am tired of the non-working stuff and bugs in it and want to go back to stock, but I have no idea how to go about it. I used the CM auto installer method and I have no backup of my original system. TBH I want to flash ViperOne now, but they require the latest firmware, but mine is very old (I think it was 1.x). I have really no idea where to start and how to go about upgrading the firmware. I was not able to get S-Off .
About 2 weeks ago I downloaded a RUU package from a site looking like an official HTC one, but have no idea what can be the damages of running it. It is just a 1.5G .exe.
My questions are:
What will happen if the RUU is not for my CID and MID?
If I just run this RUU, is there any chance to brick my phone (I am still S-On)?
Will this update my firmware version?
If the process is successful, will I be able to flash ViperOne without S-Off then?
I also found this thread - http://forum.xda-developers.com/showthread.php?t=2428276, but have no idea what to download. My phone is unlocked from Hong Kong, but I am using it in Europe (if that information is even necessary).
Any help and pointers are welcome.
Thank you!
Update: After hopping from link to link here, I now cannot see a problem to download the latest RUU .zip for any region, edit the android-info.txt so that it matches my CID and MID numbers and flash it on my device. I read that I do not need S-Off if my firmware version is lower that the one in the RUU. Will this work? Will I have OTA that way?
Thanks