yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] Mr. Jedge:
For the transparent bar, Installed Launcher3 (Google Home).
[One (M7) Android Development] trjlive:
If your firmware is too old, that might be the problem. You said in previous post you've never updated it. See my other post to you about how to check. While you don't need to have the new GPE firmware, if your firmware is too old, it might be causing problems. So read my other post about how to check your version and then let me know what firmware version you have. Radio shouldn't make a difference in rom installation, it'll just affect your cellular/wifi reception.
[One (M7) Android Development] remix92:
Hboot:1.54.0000

Radio:4A.16...

OpenDSP-v31.120.274....

OS- ( nothing is wtring behind this )

now ?
[One (M7) Android Development] baedaa:
Are all the people where it's not working s-on?

Gesendet von meinem HTC One mit Tapatalk
[One (M7) Android Development] FanDroid09:
I'm installing just fine but having the reboot issues at the set up screen, constantly reboots.

I am running the latest firmware from AT&T... Its hboot 1.55 and a 3.x firmware. ( came with AT&Ts 4.3 update) I am also S-on.
[One (M7) Android Development] Sveke:
Firmware means nothing. I'm on older 3.22 and it works fine. Nonsense.
[One (M7) Android Development] iamsloany:
Having same issue managed to adb flash recovery to twrp 2.6.3.3 and got the phone booted up having the issues of rebooting at set up screen.

so close yet so far
[One (M7) Android Development] pigr8:
it only works on the homescreen and drawler, not in lockscreen.
[One (M7) Android Development] mt3g:
S-off here, latest cwm and didn't think I selected to odex anything as I use xposed. Gonna be running an RUU tonight in hopes to restore my phone to normalcy lol.
[One (M7) Android Development] EclipzeRemix:
seems to me like its happening to everyone with old firmwares. I never bothered updating mine and I'm having the same problem
[One (M7) Android Development] Sveke:
Incorrect. Firmware means nothing again. Don't confuse people even more. I'm on old sense 3.22 firmware and everything worked fine first shot.
[One (M7) Android Development] trjlive:
Firmware does mean something. We're trying to troubleshoot things here. The part where you say you're using 3.22 and it's working fine is helpful to know, and I'm glad you got it working. The rest of your post was unnecessary. While this rom seems to be working with various 3.x firmwares, try installing it on a device still running the original 1.x firmware. It won't boot. So my question about the firmware is indeed valid. While not necessarily needing to be running the newest firmware, knowing if it's a very old firmware is important for troubleshooting.
[One (M7) Android Development] iamsloany:
Im going to sound a bit noobish now but how can I get my phone back a normal working condition via adb?

have looked around the forum so many links but i cant seem to follow them or im doing something wrong
[One (M7) Android Development] Sveke:
I'll just agree to disagree w you.
[One (M7) Android Development] Perry977:
Did you not have a backup? If not try adb sideload
[One (M7) Android Development] Powereh:
I'm coming from FTL CM11 4.4 build which is working 100% fine & I get the same issues. Albeit this is with sinlessrom but same thing is applying here.

The only thing I can think of & seems to be common so far is s-on.
[One (M7) Android Development] trjlive:
So are you saying you have an HTC One m7 with 1.x firmware that works just fine with this 4.0-1 rom?
[One (M7) Android Development] Sveke:
Nope I said I have 3.22 and I still disagree w you. All good. I'm over it.
[One (M7) Android Development] trjlive:
Looking back through the thread at the people who it's working and not working on, from those who've posted their s-on/off status, it looks like you're right about that. The s-off people seem to be, for the most part, able to get it working. Most of the people with problems are either s-on or they used the odex option, which we know doesn't work yet. At this point, I don't know what s-on/off would affect in the rom that's preventing it from booting. I'm on call right now for a client so I have to keep my phone up and going for a while, so I can't dig into it at this time unfortunately.
[One (M7) Android Development] Powereh:
Yeah it is the first time I have come across something like this since owning my HTC One, I'm not brave enough to go messing around with s-off even though its probably really easy to do!

There must be something stopping it working with s-on devices. We need someone to post back if they have managed to get it working with an s-on device.
[One (M7) Android Development] Sveke:
Yeah I'm s off and I saw that pattern as well but not sure why it would Bork the install.
[One (M7) Android Development] remix92:
How can i update my firmwire ?

Im running ftl 4.4 at the Moment.

I can install this Rom but i get reboots..
[One (M7) Android Development] Mikey:
Installed fine for me:

M7- S-Off

CID-11111111

HBoot:1.54.0000

Radio-4T

OpenDSP-32.120.274.0909

OS-3.58.1700.5

Twrp-2.6.3.3
[One (M7) Android Development] adamboyd83:
Same here.
[One (M7) Android Development] Mikey:
Download the firmware from post 1

Follow these instructions here: http://xdaforums.com/showpost.php?p=46513625&postcount=1
[One (M7) Android Development] Krisbo:
This seems to have killed my Telstra HTC One. I'm bootloader unlocked but S-On. Tried installing with latest CWM, no deal. Tried installing with latest TWRP, still no deal. Not my phone reboots randomly and won't boot any other ROM without bootloops and random reboots :(

The price of being an early adopter I guess...
[One (M7) Android Development] iamsloany:
yes have a backup and tried and tried adb sideload but nothing is happening apart from the usual endless scrolling of adb commands which tells me it didnt work and no imformation on the phone either. rebooted into recovery and no files have been transferred
[One (M7) Android Development] mt3g:
I failed with s-off and no clue what firmware I'm on T-Mo and had the 1.44 hboot when I got the phone, haven't done anything else to it.

does everyone else have a "paperweight"? Mine is only rebooting from attempting recovery back to a normal boot never getting past a splash screen lol. It seems most of you are able to get back to a different rom easily. I've tried holding down power buttons and holding volume down and power to get to fastboot nothing after that works, same results all over. Will run RUU after worl I get home in 5ish hours. This g2x is painful lol.

This is why I wanted to make a different thread. I think my issue is different from others haha.
[One (M7) Android Development] Perry977:
I guess then run the RUU
[One (M7) Android Development] trjlive:
make sure you're wiping dalvik, cache, and system in recovery before installing any other rom. What you're describing is a common result of dirty-flashing a different rom over the top. Different roms from different devs undoubtedly have differences, even more so when the bases differ. So always full wipe in recovery before installing. I've found the aroma wipe options many devs put in their installer don't always do the best job, just doing it manually in recovery before choosing the rom install file is the best method.

Thanks for the details about your device that didn't work. Looks like there might be something s-on/off related to the install problems.
[One (M7) Android Development] johnvicencio:
Yes I did deodex as well no go using both recoveries. Clean wipe. So on. Tried both GPE ROM's available SenseLess and this. No go.
[One (M7) Android Development] Old-school:
I was having problems getting it to install too. Would get to the first (Language) screen and reboot immediately. I was able to go into bootloader by holding down power and volume down, go into recovery, and use a backup to restore.

However, I finally got it to install after doing s-off. It would not boot at all after S-OFF was complete, was stuck on the white HTC screen for quite a while. However, I plugged it into the computer and realized that adb was working. Then I booted into the bootloader using adb, went into recovery and tried to install this rom again. The only thing I did different this time around was to keep Volume button Wake checked, and also to install all Google Apps. Flashed succesfully, rebooted the first time and has been running smooth as silk since.

I did not upgrade the firmware, or radio or anything else. I am on T-Mobile, was running InsertCoin 6.0.5 (Sense 5.5) before this with S-On.

TL;DR: S-OFF should take care of most issues. If it does not boot after completing S-Off, plug it into the computer again (when it is on the white HTC splash screen) and adb should be working. Thats all you need to recover a phone.
[One (M7) Android Development] mt3g:
I unchecked the volume wake option as well.
[One (M7) Android Development] Old-school:
I think you are missing the main point of my post. If it fails to boot after moonshine S-Off, and just displays the HTC splash screen, plug it into the computer and adb should be working.
[One (M7) Android Development] mt3g:
Oh, I understood your point. I already stated previously that I have adb and fastboot all working normally, just wondering why it all happened and why I'm the "special" one that got a hard brick leaving me with the only option to ruu out.
[One (M7) Android Development] Old-school:
I am pretty sure all the people that got it working the first time were S-Off. There is probably something that doesn't get written if you are S-On. I was trying to help you out since I went through the same thing, and didn't have to use a RUU or even revert to stock recovery.

EDIT: Does anyone know if there are any changes from the stock kernel? Someone mentioned that "Ok Google" would not work with tbalden's kernel, but started working fine as soon as he reverted to the stock kernel. I dont have "Ok Google" working even after installing the Google Experience Launcher.
[One (M7) Android Development] mt3g:
I appreciate your help. I'm s-off have been since a couple days after getting the phone. First time I had any issues, sad now lol. Ill try and side load first but I don't mind doing a ruu good to learn new things.
[One (M7) Android Development] Perry977:
Everything works great so far!! I hope he fixes the odex version so we could try the ART.. My recommendation, make sure you wipe...just wipe wipe wipe..yes I wiped system dalvik and factory reset three times..and it booted up the first time without any problem whatsoever.. Oh BTW I was on CWM recovery
[One (M7) Android Development] Krisbo:
Appreciate the help but as you can likely tell from my phone history in my sig, I've been around the block a few times. I've not been stumped by forgetting to wipe.

Seems form reading around that S-on and HBOOT 1.44 may be causing issues, both of which I have. This ROM and Sinless are having the exact tame issue for me. I've tried the most recent versions or CWM touch/classic and TWRP.
[One (M7) Android Development] Billyrouth:
Are you S-off or S-on?
[One (M7) Android Development] trjlive:
[MENTION=922716]Krisbo[/MENTION]

Sorry didn't mean to offend, I didn't even look at your sig before posting. I've actually gotten into kind of a habit of ignoring sigs due to some users just having huge obnoxious sigs. Yes I think the issue with with s-on, as it happens with hboot 1.44 and 1.54/5. Though there's been a few s-off with problems, but I think those were something else/user error. BaadNewz will hopefully be back on here soon, almost morning in Romania, and will be able to dig in a bit more. I started looking through code, but being s-off, I can't really duplicate the problem.

To Everyone:

What would be awesome is to get some logs from when the rebooting is happening. If it's in aroma, there should be aroma install logs, if its in the OS itself, then capturing a logcat would be good (if you can't get booted into kitkat long enough to install catlog, then use the adb logcat from your pc). I've tried installing the rom with several variations that people were saying weren't working, and they all install just fine for me. But if I had logs to look at, I might have something more to go on to help Baad here in a bit.
[One (M7) Android Development] Perry977:
S-off and on 1.54 hboot I believe
[One (M7) Android Development] bts0uth:
Absolutely love the ROM. Question though, my camera is literally covered in purple lines that I've never noticed before. I updated firmware to the latest in this thread but they are still there. It is really bad sometimes and you cant make out anything in the picture. Any idea why it's so bad or how I can make it any better?

edit: So if the flash is on all the purple lines that are showing up in the preview before snapping a pic are not there. If the flash is not on, it takes a picture with the purple lines all over and looks terrible.

I love the ROM and don't use my camera very much so I will live with it for now. Awesome work!
[One (M7) Android Development] ANDR01DN00B:
adb logcat to logcat, right?

Sorry, I'm a N00B
[One (M7) Android Development] Krisbo:
Was just kidding bro. No offence taken at all. Being a flashaholic I'm OK with flashing but when it comes to Logcats and Install logs, that's where I'm too lazy to learn anything.

I've attached my logcat and install log for you to have a gander at.

Kris
[One (M7) Android Development] nukeman239:
Will GravityBox work with Odexed? I need to get rid of the search bar from the Homescreen.
[One (M7) Android Development] Perry977:
I haven't tried the odexed one...and I have never used gravity box ..sorry
[One (M7) Android Development] baadnewz:
im still sleepy and in a hurry to go to work. from what i saw. your phone booted fine but rebooted at some point right? might be the kernel (which i build from sources) , see that in the firmware.zip i posted there is boot.img included. flash that boot.img via fastboot and see if it's ok
[One (M7) Android Development] Krisbo:
I've been watching it and it usually won't boot at all but it did boot once or twice to the language selection screen but then rebooted pretty much instantly. I'll give it a whirl and report back.

EDIT: The PC I'm on is running Windows 8.1 and I haven't got fastboot working so I'll give it a whirl as soon as I get home. Will report back in an hour or so.
[One (M7) Android Development] trjlive:
I'm looking through your logs now too. Will update with my findings.

OT

One thing I noticed, completely unrelated to these problems, but an observation, you are running a very old radio version. You have radio (baseband) 4A.14.3250.13. This is (one of) the original radio when the One came out. If it's working great for you, by all means don't fix what's not broken. :) But if you're having reception problems or low signal, a newer radio (which you can flash even with s-on) might help.

The current world-wide edition radio 4A.21.3263.04 has been widely reported as working very well. I used it for a while and it worked quite well, but then I've gone to a T-Mobile USA specific radio (though I honestly don't notice any difference between it and the aforementioned WWE radio). Nonetheless, I have had much better signal strength using the 4A.21.3263.04 radio then when I had the 4A.14.3250.13 radio (which my device had when I first bought it).

If you're interested in trying different radios, check out this page on my website. Has download links and instructions.

/OT
[One (M7) Android Development] CharliesTheMan:
Your phone definitely not bricked, it's very fixable.
[One (M7) Android Development] Krisbo:
The radio is the stock out of the box Telstra approved radio. There are likely others but I get great reception here and I've never once had a drop-out so I figure if it ain't broke, don't fix it :good:

I've never been big on changing my radio if it's working well but I might look at it at some point.

---------- Post added at 04:29 PM ---------- Previous post was at 04:29 PM ----------

It's all good, not worried about a bricked phone. I'm back running ARHD again now. Just wasn't able to get 4.4 to boot.
[One (M7) Android Development] mt3g:
alright back at home and ready to get my phone up and running. "fastboot fastboot getvar all" shows this

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.21.3263.03

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.27.531.8

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: HT36HW911407

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0713000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4305mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))

finished. total time: 0.062s

I can't get into recovery so no adb side loading if I'm not mistaken?? Anyone want to point me into the right direction of where I should go get the RUU for my HTC T-Mobile One?? :) I grabbed the files from here but it doesn't seem to be the proper size, 45ish mb???
[One (M7) Android Development] tron13:
Whats the point to install 4.4 if the ART engine its not available?
[One (M7) Android Development] trjlive:
There's a lot more to 4.4 than ART.

---------- Post added at 09:57 PM ---------- Previous post was at 09:54 PM ----------

Ok no worries! Just wanted to mention it. I know what you mean, although (and my girlfriend will attest to this) I have a habit of taking something that's working perfectly fine and trying to "make it better". And then often ending up knee-deep trying to fix it, or at least just get it working again. I call it my "Tim Allen syndrome" (more power!!!). :D
[One (M7) Android Development] CharliesTheMan:
If you can get that from fastnoot, then you can fastboot flash a recovery, if it errors about size do fastboot erase cache. Then just go to boot loader followed by pressing recovery and it will load into recovery, that's what my solution was when this happened to me.

Also fast boot flashing the boot.ing may fix it right up but I'd try the above.
[One (M7) Android Development] trjlive:
I've found my RUUs on this thread. They should be about 1GB. You're on firmware 1.27.531.8 with 1.44 hboot. I'd recommend upgrading to a firmware in the 3.x.x.x range if you're wanting to run a KitKat rom, since you're s-off should be pretty easy.
[One (M7) Android Development] vickysud:
Home key is not working of i hold home button anyone else facing same problem ?
[One (M7) Android Development] mt3g:
Tried that and still stuck. It sends the recovery fine, I can see it booting the beginning of each CWM and TWRP neither fully boot up unfortunately.

At this point KitKat is the least of my worries, I didn't see a tmobile one there so I went and grabbed a different one 1.27.531.11 I'll do the OTA and update from that and root if possible another time, for now I just want a working phone lol. Could I use the Firmware from a different OS for my phone, that easily?
[One (M7) Android Development] trjlive:
Since you're s-off, yeah it's basically that easy. With one caveat: While you can flash firmwares from other carriers, your CID needs to match. Or you can simply change your CID to super-CID 11111111, which lets you flash any firmware. I used to be on the T-Mobile USA firmwares x.x.531.x, which is the one you choose, but now I'm on the WWE x.x.401.x, since those are generally the first to be updated.

From your log, your CID is "TELST001". So you could either find a RUU that matches your CID (which I don't see one when I search for it), or change your CID to super-CID and then use any RUU, such as the TMOUS you downloaded. You can always change your CID back later if needed for return-to-stock for service, etc.

update:

Here's another site with lots of RUUs: http://www.htc1guru.com/downloads/ruu-file-downloads/

fastboot oem writecid 11111111

Hope this helps! :)
[One (M7) Android Development] mt3g:
I went with the easy update lol, back up and running I'll probably play with all that this weekend though, would like to update to the latest when I have more time. Thanks for everything man.
[One (M7) Android Development] trjlive:
Yeah it's easy to get started on something thinking it'll be a quick mod, and then find yourself lost in it hours later. That's how my s-off procedure went. Started it at 11pm on a Friday night, thinking i'd be done and ready for bed by midnight. My girlfriend woke up came into the living room and found me still working on it at 3:30am. I was so engrossed in it I didn't even realize what time it was, lol. :)
[One (M7) Android Development] mt3g:
Probably be me tonight lol. Oh well, haha.
[One (M7) Android Development] mikrosmile:
Ok i followed everything mentioned here.

I have INT One, Firmware 3.62, Hboot 1.54 S-ON/Unlocked, Radio 4A.21.3263 WWE, TWRP 2.6.3.3.

The result - It is rebooting on Welcome screen. I flashed kernel from the ROM (via fastboot) and flashed the one from firmware package, same result.

Ok then, will stick with my Sense 5.5 rom.. sad
[One (M7) Android Development] the_maker:
Guys, from what i know, you have to be SUPERCID (111111111) or a GPE CID to get this working... Either you do this after you have S-OFF or you have an original GPE phone model... Without S-OFF or GPE model phone YOU CAN NOT INSTALL THIS VERSION.... So, don't try it.. Either wait for Stock 4.4. or try to S-OFF depending to your hboot version...

If you upgraded to 1.54 or 1.55 with S-ON you will NOT BE ABLE to S-OFF and to install this cookie.. I hope this helps with some info..

---------- Post added at 09:27 AM ---------- Previous post was at 09:26 AM ----------

Check my post above..

MOD, maybe you can edit the OP with the info from above, people are really trying to do something that can not be done...
[One (M7) Android Development] mikrosmile:
Hmm. you mean to flash this version the phone has to have MID from GPE and SuperCID?

I dont get it, as it actually boots and just reboots on Welcome screen where i need to choose language, i dont beleive that this causing by unmatched MID or CID ..
[One (M7) Android Development] FanDroid09:
Man this is devastating... Can't s-off, can't run any GE kitKat. All this waiting for nothing haha.

Has any one heard a dev chime in as to

why there are issues for s-on users?

:confused:
[One (M7) Android Development] baadnewz:
did you flash the rom then after the firmware.zip ? if yes please reflash the rom and see if its ok

if you flashed the firmware 1st and then the rom and it has issues then extract boot.img from firmware.zip and flash it via fastboot

fastboot flash boot boot.img

reboot report. thanks
[One (M7) Android Development] arso120120:
I brick my phone with this ROM

Just installed this rom on my htc one and its bricked.... can't even get to the recovery. Only stuccoed on the Bootloader... can anyone help with this. I have mac... what can i do to fix the recovery from the boot loader... thank
[One (M7) Android Development] uncommonaman:
[MENTION=1186202]baadnewz[/MENTION] did you remove the rcdata.img from the firmware?
[One (M7) Android Development] Perry977:
how the hell is your phone bricked if you can get to the bootloader? lol just flash a recovery again.. fastboot flash recovery recoveryfilename.img
[One (M7) Android Development] the_maker:
I i'm 99% sure that you can not flash this firmware on s-on.. If someone has succeeded please let me know how, since it will be among the first to do it... That is the point of having different CID numbers, and that is mostly what we get with s-off (besides other small benefits)..
[One (M7) Android Development] arso120120:
Can you instruct on how to get there plz...