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

Can't perform OTA ICS installation

Hi All HTC Incredible S expertise,
My phone did received OTA ICS update yesterday and did downloaded the OTA now and yet i did proceed with the update, but it looks like fail to update and yet shows the black screen with blue android only, no progress bar it being show at all.
Anything goes wrong with my phone ? what can i do now in order to install the ICS update ?
noted: i'm still in S-ON but with UNLOCK bootloader from HTC DEV.
Android 2.3.5 with sense 3.0 and
software version 3.11.707.1,
HBOOT- 2.01.0001,
RADIO-3822.01.08.14_M
Kindly pls advise what can i do for this case. and i appreciate much to all ur comment & suggestions.

ericsson3819 said:
Hi All HTC Incredible S expertise,
My phone did received OTA ICS update yesterday and did downloaded the OTA now and yet i did proceed with the update, but it looks like fail to update and yet shows the black screen with blue android only, no progress bar it being show at all.
Anything goes wrong with my phone ? what can i do now in order to install the ICS update ?
noted: i'm still in S-ON but with UNLOCK bootloader from HTC DEV.
Android 2.3.5 with sense 3.0 and
software version 3.11.707.1,
HBOOT- 2.01.0001,
RADIO-3822.01.08.14_M
Kindly pls advise what can i do for this case. and i appreciate much to all ur comment & suggestions.
Click to expand...
Click to collapse
your problem is your unlocked bootloader. relock it and run a official ruu.

naathaanb96 said:
your problem is your unlocked bootloader. relock it and run a official ruu.
Click to expand...
Click to collapse
Hi naathaanb96,
THanks for ur advise. It works for me. now my phone was updated with ICS.
:good:
:victory:

naathaanb96 said:
your problem is your unlocked bootloader. relock it and run a official ruu.
Click to expand...
Click to collapse
When i try to run RUU it gives CUSTOMER ID error. Please tell me how can i get official ICS. Thanks in advance

akshaywani said:
When i try to run RUU it gives CUSTOMER ID error. Please tell me how can i get official ICS. Thanks in advance
Click to expand...
Click to collapse
When you get a CID Error trying to install an official RUU, the solution is you need to make and use a goldcard.

tpbklake said:
When you get a CID Error trying to install an official RUU, the solution is you need to make and use a goldcard.
Click to expand...
Click to collapse
I tried 2 methods to create gold card but no luck.. can you please tell me how can i check whether gold card is created or not.

akshaywani said:
I tried 2 methods to create gold card but no luck.. can you please tell me how can i check whether gold card is created or not.
Click to expand...
Click to collapse
The downgrade script you are using will create a goldcard for you. Did you use that method? If so, then what size was your SD card? Do you have another SD card that you could try. It needs to be at least 2GB and 8GB seems to work the best.

[Q] Q-need help with HD7 rom upgrade

Dear XDA-developers
please i need help , i have a T-mobile hd7 , i live in Egypt and i cant use the market and all the time i have the annoying wm7 screen saver .
i want to know how to install a 7.5 mango rom on it the phone data as follows :
OS version :7.0.7004.0
firmware revision number : 2250.09.11811.531
hardware revision number : 0002
radio software version :5.69.09.29a_22.50.50.21u
radio hardware version : A.a2.0.d4
boot loader version :4.5.2250.0(129291)
chip soc version :2.2.5.0
in boot loader mode i have writing only in the red section
(PD 29110 SS-BC (4K)
i have tried to download a shipped room mango 7.5 for t-mobile but it always keep telling error 260 connection , please advice me what to do the phone is useless in this state .

helaly_2013 said:
Dear XDA-developers
please i need help , i have a T-mobile hd7 , i live in Egypt and i cant use the market and all the time i have the annoying wm7 screen saver .
i want to know how to install a 7.5 mango rom on it the phone data as follows :
OS version :7.0.7004.0
firmware revision number : 2250.09.11811.531
hardware revision number : 0002
radio software version :5.69.09.29a_22.50.50.21u
radio hardware version : A.a2.0.d4
boot loader version :4.5.2250.0(129291)
chip soc version :2.2.5.0
in boot loader mode i have writing only in the red section
(PD 29110 SS-BC (4K)
i have tried to download a shipped room mango 7.5 for t-mobile but it always keep telling error 260 connection , please advice me what to do the phone is useless in this state .
Click to expand...
Click to collapse
Do you want to flash an official ROM or an custom ROM? And do you want 7.5 or 7.8?
Regards,

TheMrThomas said:
Do you want to flash an official ROM or an custom ROM? And do you want 7.5 or 7.8?
Regards,
Click to expand...
Click to collapse
thanks for your reply ,
custom rom 7.8 would be great .

helaly_2013 said:
thanks for your reply ,
custom rom 7.8 would be great .
Click to expand...
Click to collapse
I would advice to use this tutorial http://forum.xda-developers.com/showthread.php?t=1295068
Regards,

But you can also update to the official 7.8 update here's the link http://www.windowsphonehacker.com/articles/want_windows_phone_7.8_now_try_this_easy_tool-01-31-13
Let me know which one you're going to use

helaly_2013 said:
in boot loader mode i have writing only in the red section
(PD 29110 SS-BC (4K)
Click to expand...
Click to collapse
This is a bricked bootloader, the only way to fix this is a RIFF box, you must pay for that...
you have no bootloader at all, the phone can boot but you can't install any rom, maybe you can try the official zune update, one update at the time and see if that fix the bootloader... I've read in other post that zune updates can fix that instead of the RIFF box...
once the bootloader is fixed you can downgrade the rom/bootloader with the goldcard method.

faustolg said:
This is a bricked bootloader, the only way to fix this is a RIFF box, you must pay for that...
you have no bootloader at all, the phone can boot but you can't install any rom, maybe you can try the official zune update, one update at the time and see if that fix the bootloader... I've read in other post that zune updates can fix that instead of the RIFF box...
once the bootloader is fixed you can downgrade the rom/bootloader with the goldcard method.
Click to expand...
Click to collapse
thanks very much , i have tried to update via zone and i have the error ( cant check updates right now , an error has occurred 80070002) .
and also tried with phonehacker tool but no use it keep loading on PC with out any changes .
can you help me in that please ?

helaly_2013 said:
thanks very much , i have tried to update via zone and i have the error ( cant check updates right now , an error has occurred 80070002) .
and also tried with phonehacker tool but no use it keep loading on PC with out any changes .
can you help me in that please ?
Click to expand...
Click to collapse
My advice is to just buy another phone

LOL WHUT!!!
The RIFF box fix only cost less than $50, yes the FIX, not the RIFF Box, that's for technicians... not the average Joe, like US.
According to your logic: buying a new WP device cost less than $100? PLEASE!!!
But I think you are joking... right?

faustolg said:
The RIFF box fix only cost less than $50, yes the FIX, not the RIFF Box, that's for technicians... not the average Joe, like US.
According to your logic: buying a new WP device cost less than $100? PLEASE!!!
But I think you are joking... right?
Click to expand...
Click to collapse
Haha I'm just joking

[Q] Back to scratch ! Help.

Hi People,
Since there is the impossibility to go S-OFF with hboot 1.54.0000 can someone guide me on how can I revert back to stock my ONE ?
I went through the process of unlocking bootloader @ htcdev and then root, flash TWRP and until the moment the only thing I could do is flash some custom roms, but even that does not bring my phone up to date because the OS never changes, as you all can see in the screen attached.
What I would like to do now is get back to stock so I could receive OTA updates from my carrier.
Thanks in advance.

nlcautela said:
Hi People,
Since there is the impossibility to go S-OFF with hboot 1.54.0000 can someone guide me on how can I revert back to stock my ONE ?
I went through the process of unlocking bootloader. @ htcdev and then root, flash TWRP and until the moment the only thing I could do is flash some custom roms, but even that does not bring my phone up to date because the OS never changes, as you all can see in the screen attached.
What I would like to do now is get back to stock so I could receive OTA updates from my carrier.
Thanks in advance.
Click to expand...
Click to collapse
Nothing u can do to back to stock.also after several check,I just know that unlockbootloader just give our to HTC service to know we have unlock and warranty is void even you have relock unless u havent bad luck. u can try from mike stock to get os up to date back.maybe.

nlcautela said:
Hi People,
Since there is the impossibility to go S-OFF with hboot 1.54.0000 can someone guide me on how can I revert back to stock my ONE ?
I went through the process of unlocking bootloader @ htcdev and then root, flash TWRP and until the moment the only thing I could do is flash some custom roms, but even that does not bring my phone up to date because the OS never changes, as you all can see in the screen attached.
What I would like to do now is get back to stock so I could receive OTA updates from my carrier.
Thanks in advance.
Click to expand...
Click to collapse
nouxxer said:
Nothing u can do to back to stock.also after several check,I just know that unlockbootloader just give our to HTC service to know we have unlock and warranty is void even you have relock unless u havent bad luck. u can try from mike stock to get os up to date back.maybe.
Click to expand...
Click to collapse
of course you can go back to stock with s-on and you'll most probably keep your warranty. read first before you answer please...
here is a guide with several options: http://forum.xda-developers.com/showthread.php?t=2265618
just go back to stock as much as possible for you and you're fine. flash stock rom, stock recovery and relock bootloader ("fastboot oem lock"). :good:

herwegan said:
of course you can go back to stock with s-on and you'll most probably keep your warranty. read first before you answer please...
here is a guide with several options: http://forum.xda-developers.com/showthread.php?t=2265618
just go back to stock as much as possible for you and you're fine. flash stock rom, stock recovery and relock bootloader ("fastboot oem lock"). :good:
Click to expand...
Click to collapse
Thank you so much, just followed your procedure and now I only have two more questions.
1 - If possible how do I remove the tampered flag ?
2 - Will I receive further updates automatically ? and from whom, HTC or my carrier ?
Thank you one more.

nlcautela said:
Thank you so much, just followed your procedure and now I only have two more questions.
1 - If possible how do I remove the tampered flag ?
2 - Will I receive further updates automatically ? and from whom, HTC or my carrier ?
Thank you one more.
Click to expand...
Click to collapse
no, to remove tampered flag you'd need s-off, but this should not matter even in case of warranty.
with everything reverted back to stock you'll be able to recieve official OTA updates from your region again

[Q] Am I screwed? [SOLVED]

Hi all. I'm an idiot. I updated to the 5.0 rom, and tried to downgrade to 4.4.3. It went well, until my device tried to update to 4.4.4. Now I'm stuck with a bootloader (xt1053 30.B7) that says it's locked, says it can't be unlocked, and says
Code:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
CID read failure
Invalid CID status 0x69
CustomerID error. Contact dealer: 0xdead
no SP partition found
Please, is there any way to bring my device back to life? I've tried flashing pretty much anything I can get my hands on, but it always fails because the bootloader is locked. I tried unlocking it with the code I got from motorola a while back, but that's not working either. Again, please help if possible.

I'm a jackass. I'm trying the RSD with the newest SBF now.

Hopefully the 4.4.4 will fix you up.

thehanutedtubby said:
Hi all. I'm an idiot. I updated to the 5.0 rom, and tried to downgrade to 4.4.3. It went well, until my device tried to update to 4.4.4. Now I'm stuck with a bootloader (xt1053 30.B7) that says it's locked, says it can't be unlocked, and says
Code:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
CID read failure
Invalid CID status 0x69
CustomerID error. Contact dealer: 0xdead
no SP partition found
Please, is there any way to bring my device back to life? I've tried flashing pretty much anything I can get my hands on, but it always fails because the bootloader is locked. I tried unlocking it with the code I got from motorola a while back, but that's not working either. Again, please help if possible.
Click to expand...
Click to collapse
I am not very familiar with how Moto's phone's do their stuff. But, have you tried flashing the stock image for your device? One thing though, if you used the leaked soak test to upgrade your device, your screwed until the official lollipop image for your device comes up.

thehanutedtubby said:
Hi all. I'm an idiot. I updated to the 5.0 rom, and tried to downgrade to 4.4.3. It went well, until my device tried to update to 4.4.4. Now I'm stuck with a bootloader (xt1053 30.B7) that says it's locked, says it can't be unlocked, and says
Code:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup:0x35
CID read failure
Invalid CID status 0x69
CustomerID error. Contact dealer: 0xdead
no SP partition found
Please, is there any way to bring my device back to life? I've tried flashing pretty much anything I can get my hands on, but it always fails because the bootloader is locked. I tried unlocking it with the code I got from motorola a while back, but that's not working either. Again, please help if possible.
Click to expand...
Click to collapse
IF you updated to one of the 5.02 leaks (or soaks as they were called), and got this message when trying to downgrade by flashing an OLDER Moto SBF (like 4.4.4), then you will likely be stuck until a 5.02 SBF leaks.
GPT.BIN doesn't like being downgraded, or attempted to be downgraded.
However, if your bootloader still says 30.B7, I would try flashing the stock Moto Xt1053 4.4.4 SBF using mfastboot by following option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html

So the bootloader does say it's 30.b7, but it also says it's locked. And when I try to unlock it, it says fastboot oem unlock disabled. I have tried flashing back to 4.4.4, but I think the updated gpt from 5.0.2 is messing it up.

As a few of us have tried to warn people, and just like the mad rush to flash kit Kat when it came out.... You will likely need to wait for the SBF of 5.0.2 for your device. Not much else you can do at this point.
Sorry for your unfortunate situation.

I managed to get it running again by flashing the gpt of the lollipop files. I'm doing my best to go to the 1053 lollipop build to avert another brick. Thanks all for the help!

And I'm successfully on the XT1053 lollipop build. Let it be known that I'm only on lollipop to avoid incompatibilities due to the new GPT I had to flash. Sorry Motorola. Trust me, I wish I had waited.

thehanutedtubby said:
And I'm successfully on the XT1053 lollipop build. Let it be known that I'm only on lollipop to avoid incompatibilities due to the new GPT I had to flash. Sorry Motorola. Trust me, I wish I had waited.
Click to expand...
Click to collapse
I did the same thing with my moto x and now I dont know what to do with it, can you help me?

Does yours say exactly what mine does? If so, flash the gpt.bin from the 5.0.2 zip's root directory, and reflash 4.4.4 completely. Then update using the zip from the other thread.

thehanutedtubby said:
Does yours say exactly what mine does? If so, flash the gpt.bin from the 5.0.2 zip's root directory, and reflash 4.4.4 completely. Then update using the zip from the other thread.
Click to expand...
Click to collapse
Can you explain what you did after flashing 4.4.4 with the gpt.bin from 5.0.2. I'm about to do that but am not sure what update in another thread you are referencing.
thanks.

thank you bro, i was really desperate! this must be stickie!

A sticky on how to possibly brick your device with one false move?