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

About to get a Vodafone UK Nexus One

Hello all,
I am about to get a Vodafone Nexus One. It's secondhand so don't know anything about it. (As in AMOLED/SLCD, or anything about it)
The reason I got it is I just bricked my HTC Desire, flashing a corrupt fastboot N1 Partition table (Learnt my MD5 Lesson). Prior to that I had been rooting, s-off'ing flashing away, happy as can be. Not too much adb, but see I will learn more.
The main reason I'm getting an N1, is all my time was spent trying to get to FRG81, and stripped down froyo's. I regularly used a Cyanogen Mod ROM's. So why buy another Desire, and faff around with all the junk!
Do have a few question though:
I'm on T-mobile UK will I have any problems with that?
And does anyone have any tips for me prior to receiving it?
Please any advice a head of time is appreciated!
Cheers

You won't have any problem with it on Tmo. If you're planning on running stock for a bit, Voda have their own version, but its easy to bin it for Google's offering.

Thanks for that, am getting stuck in to the new reading.....
To root or not to su that is the question.
Well so different the N1 and Desire, but sure it will get easier.

nitrox1 said:
Thanks for that, am getting stuck in to the new reading.....
To root or not to su that is the question.
Well so different the N1 and Desire, but sure it will get easier.
Click to expand...
Click to collapse
rooting is upto, if you need it or not

Diamond_dawg said:
rooting is upto, if you need it or not
Click to expand...
Click to collapse
Root it!
It's the best thing I ever did with my Nexus. It's especially superb now you don't have to unlock the bootloader...

OK, Now I'm bootloader unlocked, and SU superpermission. But can I PVT S-Off the nexus one?

No, no real need to anyway.

No. Unlocked bootloader is the same as S-OFF for any other phone, with the only caveat - you can't relock it.

Jack_R1 said:
No. Unlocked bootloader is the same as S-OFF for any other phone, with the only caveat - you can't relock it.
Click to expand...
Click to collapse
Reason I ask is I am trying to install a radio .img, and need s-off. Am looking for the .zip version now.
Edit: Ok feeling quite lucky and very smug. I am now bootloader open, Superuser, running cyanogenmod (it's what I know well, will investigate others later), newest radio, and app2sd.
So nearly back to where I left my bricked desire, will start to restore my titanium/mybackup pro backup's.
Then later move on to intersectraven's havs kernel etc.
Still can't find out any more about s-off for the nexus one (As I mentioned flashing a corrupt patch for re-partitioning my desire to n1 style partitions, after already being S-Off'ed by Alpharev, is was what bricked my desire, so need help obviously ;-) ). If anyone can link me on to a page would be appreciated..
Again thanks to everyone who helps: Modaco (Again), RA-Nexus for my new grumpy care bear, Cyanogen team for an almost standardised stable exceptionable ROM, Darktremor, everyone who answers even the silliest question on XDA, and even google and HTC. Looking forward to thanking Intersectraven too.

You won't get S-OFF on a Nexus One unless it came from HTC like that. Also, you do not need S-OFF to fastboot flash your radio.

What about freehand editing apps, while using rootexplorer?
Sent from the 25th century.

[Q] HBOOT 1.16.0000, known ROMs to work?

So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk

I know.. I have spoken to him.

jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.

Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?

Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.

katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening

no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?

katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome

no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..

Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.

Hopefully it works for him I couldn't help.

Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.

jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.

I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.

ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.

globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.

[Q] Phone misbehaving after stock RUU flash

I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.

3alaawi said:
I think this is going to need an experienced dev to answer. Its a small question and probably a small answer but I'm going to put all the information I can.
Ok, so my background is that I recently returned my phone stock, the steps I took were:
S-off, flash RUU, root, remove tampered and unlocked flags, unroot, flash stock recovery, lock the bootloader, s-on.
I then OTAed myself up to 4.3 sense 5.5.
My issue is that having returned to stock, my phone has some instabilities like:
1. it randomly restarted once,
2. I can't lock the device (but can power it off so its not the button broken),
3. and once I opened the camera and the camera bit only took a square of the screen, as in it didn't fill up the whole screen, and the camera menus were messed up (when I rotated, half of the menus were cropped out of the screen, but it went back to normal around 15 seconds later).
Anyway, reason I'm posting this is that I have a niggling feeling that, being originally a CID J15 and x.xx.415.x (middle east firmware which has no RUU available) firmware device, I flashed a 401.x (Europe I think) firmware RUU, this is giving my device some issues. Would that be possible? I got the RUU from htc1guru and it listed J15 as one of the suitable CIDs for the RUU. I also, after unrooting, relocking bootloader and s-on, flashed the RUU again, because as far as I know the RUU (something made by HTC officially) will not flash on a CID that it was not made for, and it worked just fine. So, thats not the issue then is it? I can't think of anything else, I didn't even install any apps yet, only whatsapp.
Click to expand...
Click to collapse
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you

LibertyMarine said:
Could you provide the following informations? Because then it's easier to determine the reason for the misbehaviour...
-Did you also have these issues with the firmware you got from the RUU, I mean did you also experience these issues without any OTAs?
-Could you post the link to the RUU you used? Because I also RUUed my phone a few days ago with the same procedure.. but actually, I am from Europe
-Did you flash the stock hboot 1.44 before flashing the RUU?
And as far my knowledge goes, the middle east HTC One doesn't have other hardware, it only has a bit different software, so this shouldn't be the cause for the issues..
Other than that:
Unlock your phone, use a custom recovery and flash a different ROM, and if it works in this case, you can exclude other firmware parts than the system...
And maybe you wanna try out one of these RUUs:
http://www.androidruu.com/index.php?developer=M7
Maybe there is one for you
Click to expand...
Click to collapse
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.

3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Ok.. I flashed the zip.. but this really shouldn't be an issue
But with "excluding other firmware parts" I meant.. if you try another ROM and there it works, you should definitely know that the issue is caused by the system and not by hardware or bootloader etc...
Try another ROM and if it works fine, you can try another RUU.. maybe the zip.. and then you can re-unroot your HTC One and then they won't have any chance finding out what you'd done

3alaawi said:
Hello,
Here's the RUU I flashed:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
It didn't flash first and it said on the link I just posted that I may need hboot 1.44 and so I downloaded and flashed that one and then it worked.
I couldn't tell you if I experienced this before the OTA or not because I OTAed one update after the other immediately. What I can say however is that the home and back button seemed less sensitive to touch in the initial builds, but one of the OTAs made it how it always is.
A for unlocking again and flashing a different rom, I guess I could flash a stock 401 4.3 rom and redo the unrooting process. I just found it really odd that I'm having these issues whilst being on full stock, I've only ever had these issues when flashing unreliable roms and kernels. You lost me at "excluding other firmware parts" though. My main concern is that I want zero chance for anyone to know that my devices was rooted once upon a time, so I wouldn't want to compromise that.
Click to expand...
Click to collapse
Did it work? Or can I provide more help?

LibertyMarine said:
Did it work? Or can I provide more help?
Click to expand...
Click to collapse
I actually just booted into the bootloader and turned the phone on again. Then I could lock my device again and it seemed stable though I didn't have much time to test it. I just sent it in for repairs earlier today (for another issue, I have the camera tint problem with my device).
I'm guessing the previous times I reset it, it had that option in the power menu on (fast boot or something like that) maybe thats why the problems didn't go away?
Anyway, thanks for your help

Dont't buy HTC. They Thef's .
This is Problem.... Producer send fake updates to destroy all firmware stock too. I Have Desire 626 from ORANGE PL and my phone get update with this same problems. One idea. Dont't buy HTC. They Thef's .

[Q] Basic steps from unlocked to Sprint updates

I'm overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I'm a computer literate person, and I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"​
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions. I've also found step by step guides that each conflict with one another. One may have 5 steps and the other may have 12, and in one way or another they've always gone off the rails until they no longer seemed to apply to my use case.
If you can help, thank you.

Dr.Zee said:
I'm completely overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"​
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions.
If you can help, thank you.
Click to expand...
Click to collapse
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
No need to flash stock recovery if you run the RUU, only lock the bootloader.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.

dopy25 said:
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.
Click to expand...
Click to collapse
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?

Dr.Zee said:
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?
Click to expand...
Click to collapse
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.

dopy25 said:
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.
Click to expand...
Click to collapse
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.

Dr.Zee said:
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.
Click to expand...
Click to collapse
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.

dopy25 said:
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.
Click to expand...
Click to collapse
It's a patch that adds Harmon Kardon sound. Then I incorrectly remembered an app that enables Snapdragon audio (which is far superior to HK sound) but that's not firmware, you just need a rooted phone to be able to drop it into the system folder.