yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] killman2659:
I'm with ya 100%. I am actually more curious about the OTA than the actual 4.3 update and the new features/improvements it brings :D
[One (M7) Android Development] rasstar:
I found a better solution by using the development ruu. Now I have sense and the ability to tether without carrier restrictions. I can guarantee that ota will work as it worked with the development rom. HTC made an awesome device. We can chose from stock google, developer or carrier official roms.
[One (M7) Android Development] C1S12OB:
Thank you all for the hard work, my HTC One has been successfully converted, and loving it, although minus the battery life ( only lasts about 80% of a sense rom that had been optimized )

I have a few questions though,

- can we run a custom kernel with the full conversion ?

- is it possible to undervolt the cpu while using the stock GE kernel ?

- if i were to run a custom kernel, will i be able to receive OTA updates and install them without issues ?
[One (M7) Android Development] dsymbol:
Hi guys,

Does the GPe conversion fix the proximity issue found on 4.2?

the issue to most people, including me is:

during call:

- people are having a hard time to hear me when first connected.

- it gets some interference sound like getting a text message.

- sometimes it opens up other programs

I've installed proximity fix but it's not helping at all.

I'm pretty sure that this is not ROM related & just wanna seek for inputs & advice.

Thanks.
[One (M7) Android Development] metalk9:
AFAIK the issues of which you speak are related to running 4.2 with a 4.1 firmware, and therefore would be fixed by installing the GPe RUU, or alternatively just updating the firmware.
[One (M7) Android Development] killman2659:
1. Yes

2. No

3. No

I have been using this since its release and I can agree battery isn't as good as it should be. A custom kernel can definitely help but you then might as well flash an optimized ROM like Sinless, InsertCoin GE, ARHD GE, etc. Hopefully the 4.3 update is more battery friendly :)
[One (M7) Android Development] Bluewall:
My battery is awesome. 22 hours unplugged, 10 on LTE. 3 hours screen on and 1 hour of music (Spotify). That was my situation at 8 percent.

Envoyé depuis mon HTC One en utilisant Tapatalk 4 Beta
[One (M7) Android Development] killman2659:
Maybe my battery just sucks then? XD

I guess I'm gonna have to flash a ROM and kernel, might as well wait till 4.3 officially drops and see how the battery is first :)
[One (M7) Android Development] dsymbol:
wow..Thank you for the info.
[One (M7) Android Development] Rusty!:
You must be new here, welcome to XDA Devs ;)
[One (M7) Android Development] dryspuri:
The way [MENTION=311497]uncon[/MENTION] has created GE RUU zip can we get similar RUU zip for sense 2.24 Rom.

So that using the same process can be used for complete stock sense reversal.

And guys I know Gunny has posted procedure to reverse in second post so please do not link me to that. I think RUU zip will be most effective method, without using HTC's installer.

Edit: Sorry guys found zips in RUU collection. Thanks any way
[One (M7) Android Development] gunnyman:
Extract rom zip from ruu flash it in rebootruu mode
[One (M7) Android Development] MasterXXXShake:
I've done exactly this for the T-Mobile version (Only it's 4.2.1). Posted it a couple days ago in the T-Mobile one forums. Well the best that I could given what we have for the T-Mo One. I didn't include system or userdata...just download the stock rom that Team Nocturnal put out or grab one of the nandroids floating around to finish up.

http://xdaforums.com/showpost.php?p=43694720&postcount=44
[One (M7) Android Development] dryspuri:
This is helpful, Thanks!!:good::good:
[One (M7) Android Development] MasterXXXShake:
You are welcome...I've been a leech on XDA for years....finally wanted to participate a bit. I'm no dev or anything, but I've hacked my fair share of phones.
[One (M7) Android Development] edgarf28:
I've used the revert guide from post #2 of this thread (flashed Vomer's 2.17 firmware and after that 2.24, and changed my MID and CID back), and flashed an Sense 5 ROM, but when I boot my phone I still get the black Google start-up screen (from the bootloader)

How to get rid of this screen?
[One (M7) Android Development] gunnyman:
you need to find the splash screen post (in dev I think) and download the default splash and install it.
[One (M7) Android Development] edgarf28:
I would be grateful if someone can give me a link to that thread... :good:
[One (M7) Android Development] gunnyman:
http://bit.ly/15u709z
[One (M7) Android Development] Qassim:
Woo! All done and complete, no real issues - just took my time reading the various threads and all worked out fine.

On a phone bought from Three UK. Thanks for putting the work in guys! :)
[One (M7) Android Development] edgarf28:
Flashed the un-modified splash screen from this thread: http://xdaforums.com/showthread.php?t=2316726

But I've still the black Google one :(

I think the problem is the sp1.IMG in the GE RUU firmware, which isn't in the 2.17 or 2.24 sense firmware...
[One (M7) Android Development] metalk9:
Same here. Flashed the RUU with around 90% charge. 24 hours later and I've still got 30% with 3 hours screen time. Never seen battery life like this before. :)
[One (M7) Android Development] descenpet:
that thread only has firmwares from otas so they don't contain splash screen.

if you want just the same look as original sense splash, you can get it from splash screen thead in themes and apps section.

if you want to be sure it is really original, get it from a sense RUU or get someone to dump their splash partition for you.
[One (M7) Android Development] jwtrockz1998:
Thanks so much guys for this amazing conversion worked like a charm, I went into this a noob and came out semi-noob lol, na but everyone who does not exactly how to do this just read through the threads and make sure you have a backup plan to follow through, thats what I did and it worked out great.

Thanks graffixnyc, gunnyman and uncon for the great conversion and effort put into this. Fingers crossed OTA's work :p
[One (M7) Android Development] tzones:
Skype issue

Hi,

I was able to follow the instructions as listed and has successfully converted to running GE. Everything is great except that once in a while I am facing proximity sensor issues(the screen failed to turn off during call even when I brought the phone near to my ear). Also I am seeing issue with Skype, when ever I make phone calls and once the other party answers it, the app is immediately getting crashed. I tried to uninstall and reinstall it back but no luck. Has anyone else facing this issue? If so, is there a fix for this?

Thanks & appreciate your reply,

TZ
[One (M7) Android Development] TarekElsakka:
Hey there

Thank you so much for this thread. I wanted to ask a question that may have already been answered before, but if I just flash the RUU I will not need to flash the recovery, bootloader or anything of the GE since the RUU will take care of that, correct? I already changed my MID before from PN0711000 to PN0710000 so I am going to change it to the GE's one and change CID to GOOGL001 beforehand, of course. Thanks!
[One (M7) Android Development] gunnyman:
The RUU has everything you need
[One (M7) Android Development] Jerzdre:
im in the beginning where i'm about to change my MID but im stuck...im currently on the ATT version..the guy has an asian model ID and CID
[One (M7) Android Development] monkboy24:
Don't change the MID! You dont need to yet
[One (M7) Android Development] Jerzdre:
Excuse me for being a bit slow, so the files that are containted in the PL831MG zip is accurate?
[One (M7) Android Development] prng:
Are you guys keeping it stock or rooting?
[One (M7) Android Development] chiho0516:
Ask this question in the mid thread. ATT doesn't need to change the mid because GE and ATT use the same mid.

I rooted it. I am actually using the viper rom.
[One (M7) Android Development] Jerzdre:
i typed fastboot oem writecid GOOGL001 and im not sure if its doing something or not but it says

fastboot oem writecid GOOGL001

...

not sure if its doing something or not....
[One (M7) Android Development] chiho0516:
Read the red letters on the OP.
[One (M7) Android Development] dryspuri:
Buddy, Do NOT do it, I have been following your posts, and believe me if done incorrectly this can brick your device, so please dont do it!!
[One (M7) Android Development] Jerzdre:
trust me i understand, the only thing im stuck at is where it says " then place the GEBootloader.zip into your adb/fastboot folder"

---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------

i successfully did everything..im now trying to push the bootloader zip so i can do it
[One (M7) Android Development] dryspuri:
well, Good then.

Best Luck!:victory:
[One (M7) Android Development] Jerzdre:
not sure if anyone is having this issue...

<bootloader? zip header checking

<bootloader> zip info parsing

<bootloader> checking model ID

failed < remote: 41 model id check fail.
[One (M7) Android Development] jwtrockz1998:
Make sure the MID is PN071200 and the CID is GOOGL001, then it will flash fine.
[One (M7) Android Development] Jerzdre:
the txt file in the GEBootloader doesnt have the correct CID but the MID is accurate
[One (M7) Android Development] dryspuri:
Buddy u dont have to flash GEbootloader file, just flash [MENTION=311497]uncon[/MENTION] created ruu zip, thats all you need, bootloader zip is created for international phones so that they dont have to change MID
[One (M7) Android Development] jwtrockz1998:
Hey guys got a quick question, If install twrp and back up the Google software, then flash a Sense rom to try and if I dont like it can I restore to the google firmware and flash the recovery in the OP? Will I still get updates and everything else or is it best left alone?
[One (M7) Android Development] Jerzdre:
got that but for some ODD reason, file wont load..thats what its sayin in terminal...im researching to figure out the reason
[One (M7) Android Development] io53:
What is your MID & CID? Both need to be correct for the RUU to work.
[One (M7) Android Development] Jerzdre:
i have the ATT HTC ONE. my CID- GOOGL001 and my MID is modelid: PN0712000

after i did all that i open up terminal on my mac and type in the command, the RUU files its on my desktop, i tried dragging it into the android folder that i have on my macbook.. inside that folder is the SDK files
[One (M7) Android Development] pigr8:
uhm link to this modified bootloader? will it work for receiving future ota's?
[One (M7) Android Development] csensitive:
You should change back the mid and Cid to whatever you're really running and edit the text file with notepad++ with mainver of the RUU file and your stock mid and Cid which you backed up with fastboot getvar all before doing anything. Then you can run the zip with the new hboot and THEN you should change mid and Cid to GE version. That's why it's failing you.

Sendt fra min HTC One med Tapatalk2
[One (M7) Android Development] Qassim:
Yeah, what I did was:

1) Change the MID and CID to my current one in android-info.txt and flashed it (in my case:

(bootloader) modelid: PN0710000

(bootloader) cidnum: H3G__001)

3) Changed the mainver to that of the RUU (which was also the same as the build I was running anyway) in android-info.txt

2) Then I changed the MID and CID via fastboot like so:

fastboot oem writemid PN0712000

fastboot oem writecid GOOGL001

3) Then rebooted and jumped into RUU:

fastboot oem rebootRUU

fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip (It failed the first time, asked me to run again)

fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip

fastboot reboot

All done!
[One (M7) Android Development] Jerzdre:
how did u manage to change the mainver

---------- Post added at 02:39 PM ---------- Previous post was at 02:30 PM ----------

getting an error saying " can not load"
[One (M7) Android Development] Qassim:
Mainver is in android-info. "Can not load" is very vague, there are multiple things that could be telling you that it can't load.
[One (M7) Android Development] Jerzdre:
are you using this on a windows pc or mac? because in the zip file via the mac, there is no android info...but the boot.img META.INF and system.. when i was using the windows pc i saw the android txt
[One (M7) Android Development] Qassim:
Both, I think you're looking in the wrong place. Follow this guide: http://xdaforums.com/showthread.php?t=2322820
[One (M7) Android Development] Jerzdre:
i dont need to change my modelID and CID because because its the same as the GOOGLE HTC edition...same CID and MODELID
[One (M7) Android Development] killman2659:
All you need to do if you have AT&T is download the RUU zip, put it in the folder with fastboot and adb, change CID to GOOGL001 or 11111111, make sure you are S-OFF, reboot to bootloader, make sure it says fastboot USB, then type fastboot oem rebootRUU, then fastboot flash zip filename.zip, then flash it again, then type fastboot reboot.

---------- Post added at 09:07 AM ---------- Previous post was at 09:03 AM ----------

You don't need to edit anything in android-info as the zip has been updated to fix the version number. Just download the latest RUU zip that has been uploaded (I'm not sure if OP has the updated link or not)
[One (M7) Android Development] Jerzdre:
all that is already done, when i reboot it says im S-OFF and my CID is GOOGL001.... is issue we are having is when i try to flash the RUU file its not working..i will try it 1 more time but ive been at this all night
[One (M7) Android Development] gunnyman:
I think you're flashing the wrong zip.
[One (M7) Android Development] Jerzdre:
http://xdaforums.com/showthread.php?t=2353033 thats the link the op provided
[One (M7) Android Development] killman2659:
Wait are you trying to flash a ROM in RUU mode??? I'll link you the full RUU from OP
[One (M7) Android Development] gunnyman:
you flash that zip if all you do beforehand is change cid/mid and flash bootloader

you don't flash THAT rom in rebootRUU mode

you flash uncom's RUU

Like I suspected you are trying to flash the wrong zip.
[One (M7) Android Development] killman2659:
http://d-h.st/T1w

It does seem like you were trying to flash the wrong file, use this and you should be good to go
[One (M7) Android Development] Jerzdre:
see, this is the issue i was having..so you're saying i have to load that ROM, THEN do the conversion
[One (M7) Android Development] killman2659:
No, loading the ROM is a waste of time as the file I linked to contains the system which it the ROM. Just flash the file I linked to.
[One (M7) Android Development] gunnyman:
It indeed does. I just checked.
[One (M7) Android Development] killman2659:
Once you download the file copy it to the correct folder then

1. Backup any data you might have since this will completely wipe your device

2. Reboot to bootloader, make sure you are in fastboot mode and it should say FASTBOOT USB

3. Type fastboot oem rebootRUU

4. Fastboot flash zip the linked RUU zip

5. Flash it again

6. Once the terminal says it is complete then type fastboot reboot.
[One (M7) Android Development] io53:
No. You just have to flash the RUU in RUU mode. There is nothing more with it.

So download the RUU zip to your computer, reboot to bootloader and then to RUU mode, flash the RUU 2 times then reboot, done.
[One (M7) Android Development] killman2659:
Well I must have derped out then xD But yeah the OP does have the most recent zip I guess I read the link wrong
[One (M7) Android Development] csensitive:
FYI the ruu linked to in the OP quoted uncon is the right one with correct OS

Edit: tapatalk is constantly 5 post behind. Omfg

Sendt fra min HTC One med Tapatalk2
[One (M7) Android Development] gunnyman:
Happens to all of us.
[One (M7) Android Development] Jerzdre:
about last week, when i was asking for a video tutorial, that would of been the sucker way out..actually learning the adb commands were kind of helpful...thats what i needed, not the easy way out....thanks again

---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------

now these are the exact commands that im typing in

fastboot oem rebootRUU

fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip

fastboot flash zip RUU-HTC_One_GE-2.14.1700.15.zip

fastboot reboot

now being as im on a mac, we dont have your typical c:/ drive... the RUU files that im dragging will go into the folder on my desktop named "android" right? inside android its adb, a folder called adt-bundle-mac-x86_64-20130522 and fastboot.. inside that adt-bundle-mac-x86_64-20130522 folder is eclipse and sdk folders, inside that sdk folder they are multiple folders...i was able to successfully execute the adb commands and stuff.. i dragged the RUU zip into the platform-tools folder.
[One (M7) Android Development] gunnyman:
here's a mac tip.

type the command "fastboot flash zip" leave a space then drag the file you want to flash into the terminal window.
[One (M7) Android Development] Jerzdre:
got this error while trying to flash it FAILED (remote: 90 hboot pre-update! please flush image again immediately)

finished. total time: 24.653s

---------- Post added at 04:13 PM ---------- Previous post was at 04:02 PM ----------

i think i did it.... theres a progress bar and its loading up the files!!!!!!!

ive finally converted to the Google edition htc one....thank you guys VERY much for being very patient with me....i know i was acting like a NOOB and trust me you guys have taught me ALOT...thanks again

---------- Post added at 04:17 PM ---------- Previous post was at 04:13 PM ----------

now im assuming by me doing this, i lost my root access correct?id have to go ahead and root the phone again?
[One (M7) Android Development] gunnyman:
Yes. You need to root again.
[One (M7) Android Development] io53:
Yes your phone has been wiped. To root you can flash clockworkmod recovery, reboot to recovery and flash superuser zip, reboot to fastboot and flash stock recovery.
[One (M7) Android Development] prng:
Will you get OTA updates if you do this?
[One (M7) Android Development] iElvis:
Attention Noobs!

I'm starting to see reports of people bricking their phones after doing this conversion and then deciding to go to something else.

I would suggest not doing this full conversion if you're just "trying it out." There are roms that you can flash without doing the full firmware conversion if you just want to see what GE is like.

If you do it, at the very least DO NOT GO BACK TO S-ON as you may not be able to s-off again, and changing things later may screw up your phone. I've seen two people make this mistake so far.
[One (M7) Android Development] killman2659:
No

---------- Post added at 10:35 AM ---------- Previous post was at 10:31 AM ----------

Not to sound like a asshole but it is their problem if they bricked their device. I mean you would think they would at least know what the RUU zip contains and what it will flash. Even the OP warns of this (last time i looked at it). If this process was noob friendly then it would be pinned to the top of the general section, there is a reason why it is in the development forum ;)

---------- Post added at 10:37 AM ---------- Previous post was at 10:35 AM ----------

The more you know :highfive:

Keep in mind that by installing a custom recovery you will not get OTA updates, im glad you got it to work :good:
[One (M7) Android Development] gunnyman:
There's nothing about the conversion that will brick a phone on its own. What people fail to grasp about s-off is once you have it, leave it that way.

I don't want this conversion blamed for people's stupidity. It isn't fair to everyone who worked on it.
[One (M7) Android Development] iElvis:
Yes, of course, everyone is responsible for their own phones, but I think some people are not thinking this through all the way and realizing that undoing this is as risky as doing it, and needs to be handled carefully. It's not just a matter of flashing a different rom.

It's NOT the conversion--not suggesting that at all. It's going back to s-on and then flashing other stuff that's the problem.
[One (M7) Android Development] housry23:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)

The reason you got that is because, as stated in the directions for the full RUU, you have to flash again. This is normal and what's supposed to happen. Obviously, you did and got it to work. I am just pointing that out to you. I'm glad you got it working!

Also once you put a custom recovery on the phone, you won't get OTA's. But...you can flash a prerooted GE Rom. I use Bigxie's because it's stock rooted with Koush's superuser. Also, keep in mind, even though you won't get OTA's, devs are very good about having a stock rooted rom you can flash from recovery the same or next day. So no big deal there.
[One (M7) Android Development] graffixnyc:
I actually just added something to the OP under uncon's instructions about that "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"

thingy telling people to run it again. I realized that his instructions have the command twice but don't state you will get this message after the first command is run
[One (M7) Android Development] housry23:
I think that will be very helpful. I've seen a lot of people a little confused on that.
[One (M7) Android Development] xperia x root:
There is no reason to flash back the 1.44 Hboot! The RUU allready contains the right Hboot! If u are going to flash the Devoloper Edition u also wont need to relock the bootloader!
[One (M7) Android Development] tazb:
do you need to relock bootloader to receive OTA? or can I leave it open?

Sent from my HTC One
[One (M7) Android Development] Bluewall:
Well, I did the conversion since one week and I couldn't be happier :l

Envoyé depuis mon HTC One en utilisant Tapatalk 4 Beta
[One (M7) Android Development] gunnyman:
Open is fine.

---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------

I'm sorry but that isn't the case. Ruu will fail with mainver error unless you flash hboot manually. I have converted back and forth several times and even with s-off I've had to flash 1.44 hboot before the ruu would work.

---------- Post added at 01:58 PM ---------- Previous post was at 01:54 PM ----------

Edit
[One (M7) Android Development] Dark Fable:
So if we go through this conversion will we get OTA updates from google on it ?
[One (M7) Android Development] Bluewall:
Probably. Can't tell for sure since we didn't have any OTA yet, but you have all the files from GE with correct CID and MID. So it should work !

Envoyé depuis mon HTC One en utilisant Tapatalk 4 Beta
[One (M7) Android Development] RaptorMD:
I have been enjoying my DE H1 for a few weeks now and completed everything I need to do through the great help of this site. I am trying to decide if I want to stay Sense based, fully convert to GE as everyone here has or run a GE ROM. I know I won't have this phone for more than a few months more (always upgrading) as I am looking at the HTC One Max due out in a few months.

So for those who have upgraded to a full GE experience how do you feel its working out? Performance wise, experience wise. I don't care about the IR Blaster (though it will come along sooner or later) I care about not losing what made this phone an awesome phone to begin with. Responsiveness, Boom Sound, etc.

Also I want to make sure when I go to sell my DE 64GB H1 if its converted to a GE 64GB H1 (rather a unique find perhaps) will it hurt resale?
[One (M7) Android Development] descenpet:
if you think it will be hard to resell as converted, you can restore to original. it should be easy since DE has ruu available.
[One (M7) Android Development] RaptorMD:
Good point. The conversion part actually doesn't scare me anymore, I truly have learned a lot and keep the how to videos form YouTube handy along with links, .pdf's and notes on to do commands.

I would think a 64GB GE/DE would be a nice buy (for some).

So descenpet what are your honest thoughts since converting? Do you miss Sense, do you feel as though you are missing out on anything or any quality issues etc.?