yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] deagleone:
shutdown device, plug in wall charger, screen turns on showing bat icon, after 10 seconds icon disappears but screenbacklight stays on :confused:

Can someone confirm that?

Insertcoin'ed

In the beginning God created dev/null and dev/random. And dev/random was was formless and empty....
[One (M7) Android Development] altimax98:
Thanks!
[One (M7) Android Development] semdoc:
Yup. It's expected behaviour - same as 3.06 firmware...

http://xdaforums.com/showthread.php?t=2391611
[One (M7) Android Development] DroidRC1:
Have you flash the radio yet?
[One (M7) Android Development] deeevan:
fastboot boot, which is disabled in hboot 1.54 too.
[One (M7) Android Development] ChongoDroid:
Hey just wondering where did you get the latest leaked radio? Like the actual zip file?
[One (M7) Android Development] godfirst:
I unzipped it from the firmware package!:cool:
[One (M7) Android Development] alhuang69:
Thanks vomer,

Just flashed the entire latest firmware ... let see how good it is.
[One (M7) Android Development] altimax98:
Yeah flashed it... Works great, don't notice any difference so far though... It may be similar to the GPE radio since that's what I was running
[One (M7) Android Development] runganwt:
One thing I found about new radio (4A.19), the switching between 3G and H come back. (with 4A.18, It not switching back and forward) :eek:
[One (M7) Android Development] air2k57:
Will this work on T-Mobile USA version? Is it safe to flash on it? If so, do I need to change cid?
[One (M7) Android Development] rynfrnk:
you'll need to be supercid to flash the package. it worked fine for me though. just fastboot oem writecid 11111111 and then do the firmware flash and then change the cid back if you don't want to stay supercid (in my case, i change back to cws__001 so that my at&t icons show in lieu of the international generic icons). fastboot oem readcid will show you what your cid is so you can change it back afterwards, which for tmo is T-MOB010 if i'm not mistaken.
[One (M7) Android Development] DroidRC1:
As long as you have superCID you should be good
[One (M7) Android Development] iElvis:
Went from 3.06 to 3.09 with no issues. My guess is that there may not be a whole lot of difference between the two.
[One (M7) Android Development] Magpir:
CAN SOMEONE MAKE A MODIFIFED FIRMWARE OF THESE?

i dont want the HVoot and what is TZ img?

what are the files to remove that may cause potential problems in the future?
[One (M7) Android Development] runganwt:
You can check by yourself by open the zip, copy file Android-info.txt to desktop and then open it. If you see you CID in the list. You can flash it.

This is only the matter of you can or cannot flash this zip. Is it save or not, It's always do at your own risk. Most people have done it with no problem. But it's no guarantee that it 100% save for you. :o

---------- Post added at 03:23 AM ---------- Previous post was at 03:05 AM ----------

You can do it yourself. Just open the zip and replace nbootsignedbyaa.img with the one you want then save the zip.

TZ.img is Trushed Zone image.
[One (M7) Android Development] Magpir:
i have maximus 4.3 installed now

what else should i remove? boot.img , hboot.img , and also boot.img right?

there are 2 more i am not sure what does

cir.img

pg2fsspcustom.img
[One (M7) Android Development] runganwt:
You now trying to move almost every files that matter for this update:eek:

So, I do not see the reason why you should do this update. :confused:
[One (M7) Android Development] Magpir:
i am still on 4.2.2 firmware intended for my device and S-off

so in some case if there is any need to be sent for servicing i need to flash my recovery back only and turn back locked bootloader again
[One (M7) Android Development] runganwt:
As long as you S-off you can do whatever you want. Flash new firmware will not turn your S-off to S-on. ;)
[One (M7) Android Development] Magpir:
btw i think cir.img refers to the Infrared sensor or something, possibly related tot he HTC tv feature

got the info here

---------- Post added at 04:42 AM ---------- Previous post was at 04:41 AM ----------

I am on 1.54 if i want to lock the botloader using revone, will the revone commands work?

if i remove the tz.img, what happens?

---------- Post added at 04:54 AM ---------- Previous post was at 04:42 AM ----------

ok i compared earlier firmwares i flashed before, they dont contain the tz.img

i think its safe to remove tz.img and also hboot.img

the rest just leave it as it is. DOING IT NOW

EDIT : I HAVE SUCCESSFULLY FLASHED IT AFTER MODIFYING AND ALL IS WORKING FINE

it does not contain Hboot and tz.img but still contains the touchdrivers.

SO MAKE SURE U HAVE THE LATEST TWRP INSTALLED FIRST

here is the modified version

https://mega.co.nz/#!hNhHzTDI!OfPTMmHZtUIMWCOmTVJmOg4WIN55Av_iS88IaB-PytY
[One (M7) Android Development] cubitusclaudius:
Lucky guys with s-off superCIDs and unsigned firmwares. :cool:

Just a question or 2 :

where will I find Original 3.09.401.1 Dump on August 28 10 am. GMT ?

my CID is HTC_102 . I suppose it will match with Firmware (I'll check on text file)

I suppose also I will lose everything on SDcard, I backed up by ADB pull my ARDH nandroid on computer, and saved all visible stuff on SD card. will I be able to Nandroid restore after flashing back CWM recovery?
[One (M7) Android Development] joselv456:
I tried reinstalling stock rom but touch screen does not work after install I guess its not compatible with official stock t-mobile rom but its cool works on maximus 12.1
[One (M7) Android Development] jay661972:
you need to go back to 2.24 or lower firmware. i did that few weeks ago and running 3.06 fw and yest touch screen wont work. i just flash the 2.24 fw and all good
[One (M7) Android Development] joselv456:
Okay thanks that's what I figured I'll just stick with 4.3 with sense though

Sent from inside the T.A.R.D.I.S
[One (M7) Android Development] phab3k:
everytime I try to flash this I'm getting this with MaximusHD 12.1 installed, tried all kinds of CID's, even my original one, all the ones in the android-info.txt, and I get this message

C:\adb>fastboot flash zip firmwarenew.zip

sending 'zip' (28171 KB)... OKAY [ 2.906s]

writing 'zip'... FAILED (remote: not allowed)

finished. total time: 2.941s

even after running it twice, same message every time. any ideas?
[One (M7) Android Development] descenpet:
You are not supposed to flash it in fastboot :p

RebootRUU first
[One (M7) Android Development] phab3k:
Oh, I think I figured it out, did a rebootRUU and it was giving me a modelid error. my model is PN0712000, can I maybe just change it in the android-info.txt to mine? the one in the txt is PN0710000, not sure what the difference is
[One (M7) Android Development] descenpet:
Just use supercid. it's easier. It will bypass model id check too.
[One (M7) Android Development] phab3k:
already tried that, and now in the process of trying to change the MID, I think I semi bricked my phone, after an hour I've finally been able to get back into RUU mode, need to try and find an RUU that will work, but I keep getting an hboot error

edit: I think it's alive! I might just give up on this hboot update, this is becoming a lot more work than I thought.
[One (M7) Android Development] victoryo:
Do you guys also have this when you turn off

your phone and put it on the charger you see a big battery for a phew secconds

and then it goes a way and the backlight of the screen goes on and screen stays black.
[One (M7) Android Development] phab3k:
actually, nvm, got it to work! woot!
[One (M7) Android Development] JoeM01:
I just edited the android info file to reflect my mid and cid. Flashed fine.
[One (M7) Android Development] mattisfaction:
Hi everyone, before you tell me I'm mad for messing with my phones boot partition without knowing what in doing, a) this is only my first HTC phone, I've had many android devices and am very good at trouble shooting on the fly b) I've got phone insurance.

However I have a question, if after flashing this I forgot the command for the final reboot of the procedure and therefore rebooted my phone by switching it off holding the power button, is there anyway that in missing some of the new files. The command prompt stated everything was successful and the phone boots and works absolutely fine. Or was it just risky to do the above as the flash may have been incorrect and therefore my phone could have been rendered a expensive paperweight?
[One (M7) Android Development] backfromthestorm:
Your fine.
[One (M7) Android Development] Upstreammiami:
Ok I'm on T-Mobile and this boosted my lte speeds by about 10 more mb
[One (M7) Android Development] formula84:
Coming from what Radio + Firmware package prior to this one?
[One (M7) Android Development] Upstreammiami:
I had the stock firmware that came with the phone but dis update the radio to the latest tmobile ota
[One (M7) Android Development] lmerega:
I would like to upgrade, but I do not want to loose Revone features.

So I have to remain on HBOOT 1.44.

Or perhaps, I could flash 1.44 if I need to go back stock.

Is there any feature I obtain in upgrading to 1.54?

Thx

Bye
[One (M7) Android Development] durius:
I flashed this firmware and now the phone is taking a very long time to boot...Is this normal?

I can stop normal booting by long pressing power button and boot into recovery or bootloader but if retry normal boot it won't pass bootscreen.
[One (M7) Android Development] hccssn:
Hi, you can upgrade the HBOOT without loosing S-OFF; when you would like to set the status back to S-ON, you have to just flash an RUU and update it via OTA to 1.29 version and you will have again 1.44.

The new, 1.54 is an updated version for 4.2.2, with assigned radio, the battery life is better.
[One (M7) Android Development] lmerega:
May I downgrade the hboot if I need to?

Inviato dal mio HTC One usando Tapatalk 4
[One (M7) Android Development] dgtiii:
Yes, with S-off you can downgrade Hboot
[One (M7) Android Development] lmerega:
Thanks, I'm upgrading :)
[One (M7) Android Development] oblivianz:
Just wanted to confirm, this firmware is for Sense and not GE right?
[One (M7) Android Development] jlevy73:
Correct.
[One (M7) Android Development] JoeM01:
Ok, so how is everyone who's flashed dealing with the lack of a functioning touchscreen in recovery? No big deal for cwm functions, but aroma is completely useless without a touch screen.
[One (M7) Android Development] dgtiii:
You need the latest copy of CWM. That will work with the newer touch drivers
[One (M7) Android Development] Tachi91:
Here is the new hboot 1.55 with the Red Legal Text Removed.

>> Click Me <<

Flash twice so

fastboot oem rebootRUU
fastboot flash zip hboot-No_Text.zip
fastboot flash zip hboot-No_Text.zip
fastboot reboot

I put the fash command there twice just incase it doesn't stick the first time.

To each his/her own
[One (M7) Android Development] codeblue315:
Also confirming this works just fine. Coming from 2.24.401.8, didn't lose S-OFF and of course didn't touch my sd card.

Running ARHD 13.3 also.
[One (M7) Android Development] spdrosin:
Is there something special we have to watch out for with that custom hboot?

For example next hboot update flash shoud be a normal flash or shall we do something like reverting to official one?
[One (M7) Android Development] descenpet:
Whatever hboot you flash next will overwrite it.
[One (M7) Android Development] spdrosin:
So if I wait today for the whole firmware to be out which includes everything (radio, hboot, etc) and after that flash on top, this custom hboot it will be ok? Right?
[One (M7) Android Development] descenpet:
What is coming later today should be just boot and system which will compliment what is currently available. They are supposed to work together and won't overwrite each other. Whether you flash firmware now or later doesn't matter.
[One (M7) Android Development] spdrosin:
Ok mate. Just flashed it. Really works. So nice to have those red alert signs away. Thank you so much for that and for your answers. ;)
[One (M7) Android Development] lmerega:
I had to flash firmware a couple of times, but now everythins is correct :)

C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.09.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT3*********************
(bootloader) imei: 35***********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
[One (M7) Android Development] boterkaaseneieren:
it's

time :p
[One (M7) Android Development] Electronic Punk:
GMT is one hour behind current UK time, so 1 hour 41 mins to go.
[One (M7) Android Development] descenpet:
It's not :p
[One (M7) Android Development] boterkaaseneieren:
hihi no rush
[One (M7) Android Development] Wiz:
GMT (Greenwich Meridian Team) does not equal BST (British Standard Time) guys :)

http://wwp.greenwichmeantime.com/
[One (M7) Android Development] Super-Veloce:
but it's 11.30am now.. :P
[One (M7) Android Development] Matt:
Nor does Greenwich Mean Time equal British Summer Time
[One (M7) Android Development] Wiz:
LOL .. that was a typo ... I still have this love/hate relationship with Swiftkey autocorrect that did me in here ... I meant Summer time :)
[One (M7) Android Development] Vicpdx18:
If i have a AT&T One and have their radio but am on Android Revolution which will be soon posting the new base should I change my AT&T radio to this one?
[One (M7) Android Development] LlabTooFeR:
Original dump posted, have fun guys.
[One (M7) Android Development] alhuang69:
Hi Llab ToolFeR,

Are you saying that the original 3.09.401.1 is having issues and suggest to flash the firmware which you posted on 25 August ???
[One (M7) Android Development] EddyOS:
He's listing the faults in the ROM, not the FW
[One (M7) Android Development] descenpet:
both combined is a set 3.09.401.1.. the one posted on 25th is firmware. today's is system dump.
[One (M7) Android Development] gianton:
So it's better to stay on your previous release right?
[One (M7) Android Development] Jonny:
No. LlabToolFeR's Maximus ROM posted on the 25th is based on this system dump. They contain the same bugs.

As for the actual firmware, it can only be flashed if S-OFF and if you are S-OFF then there is no harm in flashing it as it contains some updated parts.
[One (M7) Android Development] shark147:
Thanks LlabTooFeR for sharing the new base,

I have one question, this dump is ODEX or DEODEX, if is DEODEX it's possible have ODEX version?

thanks in advanced.

EDIT:

I have finished download and I see ODEX Version, Good...
[One (M7) Android Development] Super-Veloce:
downloading at 1,3mb/sec :)

it's a rar, so it's not able to fastboot flash zip

can I still flash it somehow?
[One (M7) Android Development] gianton:
For firmware update and only if you're S-Off follow the guide here http://xdaforums.com/showthread.php?t=2316726
[One (M7) Android Development] Mouxy:
I have the same question... With s-on devices can se flash it? It depends on CID right? Tks guys
[One (M7) Android Development] gianton:
Thanks for the heads up, silly me lol!
[One (M7) Android Development] Electronic Punk:
You do not flash a system dump via fastboot. tbh, if you aren't rom dev / chef / whatever I wouldn't even download it.
[One (M7) Android Development] Super-Veloce:
what if you rename dir DUMP into system.. put it in a zip file together with android-info..txt and name it firmware.zip

than just ffastboot flash zip firmware.zip

what would it do? :P
[One (M7) Android Development] LlabTooFeR:
It doesn't because I fixed them in my ROM :)
[One (M7) Android Development] Mouxy:
Got it :) thanks.

Btw we (s-on) to update the firmware have to wait for signed firmware or official ruu right?
[One (M7) Android Development] Super-Veloce:
yes

if I'm able to mount system to my pc, when in bootloader, I could copy/paste the dump and reboot phone, but I guess that's impossible too :P

I guess the only way for 4.3, is flashing a custom rom
[One (M7) Android Development] throcker:
your rom has problems with connections (wifi I think, sometimes it works bad, sometimes it doesn't at all)

does this dump have the same issue?
[One (M7) Android Development] Electronic Punk:
I believe the firmware.zip is signed, I could be wrong - then you just need a matching cid. Likely modified as boot_signed.img was removed.

It may work fine without any new firmwares but as an S-Off user I won't try it and already updated.
[One (M7) Android Development] descenpet:
it isn't signed
[One (M7) Android Development] Electronic Punk:
Fair do, I guess boot.img was deleted.

I often find that when trying to add a file to an original ZIP it fails, I have to extract the whole thing and recompress. Oddity but does the job.

I still think this will work without the new firmwares but currently only Maximus users will be able to tell you that, or you can flash it yourself.
[One (M7) Android Development] descenpet:
i think it is more like images taken from RUU, like mike did for 2.17?

and ya, you can't add/remove files to/from original original firmware.zips directly. will have to extract and rezip.
[One (M7) Android Development] mirecc21:
I flashed this firmware HBOOT change from 1.44 to 1.55 but Radio no change. I dont know why ?
[One (M7) Android Development] Electronic Punk:
Did you flash it twice as it will have told you to do?
[One (M7) Android Development] Chenglu:
With stock recovery.img?
[One (M7) Android Development] dragonesdenano:
Thanks for the Dump. :thumbup:
[One (M7) Android Development] Prinz069:
Firmware doesn't get recognized in fastboot. What can I try? Don't know when I flashed last fw :silly:
[One (M7) Android Development] mattisfaction:
As quoted about three posts from the op this is how you should do it http://xdaforums.com/showthread.php?p=44965367

It is not to be flashed through fastboot
[One (M7) Android Development] 09Ram:
I think you are mistaken.

It is supposed to be flashed through fastboot only!
[One (M7) Android Development] WorldIRC:
Considering it requires S-OFF, yes, it needs to be flashed in Fastboot > RUU Mode...twice, just like every other Firmware update.
[One (M7) Android Development] donmarkoni:
You think wrong. [MENTION=4173152]mattisfaction[/MENTION] is right. FW is supposed to be flashed in RUU mode, not fastboot.

You can simply check it by looking into zip file, if it has android-info.txt file, then it is for RUU mode, but if it has meta-inf directory, then it is for fastboot mode.

---------- Post added at 08:02 PM ---------- Previous post was at 08:00 PM ----------

You are right about requiring S-OFF, but are wrong about fastboot. It is to be flashed in RUU mode.

EDIT: You both can check this great guide by [MENTION=1102297]Sneakyghost[/MENTION].
[One (M7) Android Development] WorldIRC:
My apologies -- I consider the two the same since you require Fastboot to get into RUU mode ;)
[One (M7) Android Development] spdrosin:
Today I updated to 3.09.401 firmware and after a full wipe I flashed latest MaximusHD.

What I noticed is that when I charge the phone while it's powered off the screen goes on (in black).

Is it a ROM or an HBoot/firmware thing ?
[One (M7) Android Development] descenpet:
power off charging stuff is always related to hboot and recovery

it NEVER has got anything to do with rom. rom is not even loaded when phone is off.
[One (M7) Android Development] spdrosin:
Yeap that's what I was thinking too, but was not so sure.

OK after having messed things up my phone can never boot to ROM whichever firmware I flash. For example I just flashed 2.24. HBoot returned to 1.54, radio remained the latest 4A.19, but firmware is still (in red letters) 3.09. WTF? If I flash to 3.09 firmware, all will be latest versions and matched as it should be, but the phone boot loops again.

In addition when I get the splash screen, no red warnigs are shown and I don't know why.

I don't believe that I am flashing wrong files. Can someone please help me with that?

Edit: Now I am on this state: Downloaded and flashed the firmware.zip from the 1st link of this thread. No red warnigs are shown again and boot loops. I stay here until someone can tell me something usefull. Done so many backwards and forwards without any luck. That "backwards and forwards" f*ckd things up. And maybe that "No red warnigs" HBoot has to do with it? I don't know.

Just tell me I did not kinda bricked the phone.
[One (M7) Android Development] spitfire2425:
Any reason to flash this? Any perks to new firmware? I came from Samsung and even after three months this still confuses me.

Sent from my HTC One
[One (M7) Android Development] dgtiii:
Dude, STOP flashing firmware back and forth! Can you boot into recovery? If not, you may not have one installed. Go download TWRP from the thread in the Original Development forum and follow the instructions to flash it to your phone. Once recovery is installed, flash your rom again. Fastboot erase cache wouldn't hurt either
[One (M7) Android Development] S_Dot:
Anyone having poor reception with the new radio?

ATT USA
[One (M7) Android Development] spitfire2425:
Mines normal so far.

Sent from my HTC One
[One (M7) Android Development] spdrosin:
Oh man. Yeap. Can now go to work nice and easy.

I did not realize I had no recovery. How did it get erased? And fortunately I had MaximusHD ROM on my sdcard and did not have to sideload.

Thank you so much mate. ;)
[One (M7) Android Development] 09Ram:
Thanks for the tip, but I have always considered fastboot = RUU mode and the other option to be recovery mode for flashing firmware.

That's what I have gathered from reading the countless discussions on the subject in these forums. ;)
[One (M7) Android Development] pablo11:
It's a simple process - fastboot is used to get to RUU flash mode.

End of story!!
[One (M7) Android Development] dgtiii:
That's awesome, I'm really happy it worked and you're all good now! The firmware updates normally come wit a recovery update, most of the files here have that stock recovery removed, but the update still wipes recovery, so you have to reflash recovery after the firmware update. If you notice in Sneakyghost's firmware and Hboot thread, he usually includes TWRP in his firmware files so you don't have to flash recovery separately
[One (M7) Android Development] wwjdd44:
I get LTE in less places with the .19 radio than I did with the .18 radio, but really not that much of a difference to go back to that fw version. I like to have all the fw files match the radio, if possible. I think they all work together.
[One (M7) Android Development] augie7107:
I have the dreaded black "screen on" when powered down and charging after upgrading to this firmware. Anyone know how to correct?
[One (M7) Android Development] Android The Greek:
Can you get into fastboot reflash firmware twice
[One (M7) Android Development] dgtiii:
It's just how this firmware is. Was the same on 3.06
[One (M7) Android Development] augie7107:
I did flash it twice. I'll give it another shot.
[One (M7) Android Development] Android The Greek:
Mine has 30 seconds of charging animation 30 seconds of dim charging then completely black no light
[One (M7) Android Development] edgarf28:
Where can I find the 3.09.401.1 stock recovery img?

It's not included with the firmware package that I can find in the OP.
[Samsung Galaxy Nexus] navyanup:
After the latest update , Google now doesn't show any cards.
[LG Optimus 4X HD] ezet:
Hello,

I've been trying CyanogenMod for a few days now and have noticed a weird thing.

The phone will either boot to baseband L6260_modem_sic_02.1233.0 or LGP880AT-00-V20a-EUR-XXX-MAR-26-2013 .

That happens with every kernel available for CM at the moment.

Also i noticed that when phone boots to LGP880AT-00-V20a-EUR-XXX-MAR-26-2013 occurs the notorious baseband_xmm_power wakelock .

So anyone got a clue why phone boots randomly to one of these baseband or a way to make it stick to one of these?

Thanks in advance.