yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
hi

you can just flash the RUU which will update your device to official marshmallow ( and it will wipe your internal storage so make sure to backup all your data )

here is the RUU

https://www.androidfilehost.com/?fid=24459283995310669

and here is the guide ( replace the RUU by the one i linked ) and you don't need to relock the bootloader

start from

http://xdaforums.com/showpost.php?p=64926626&postcount=6
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
Thanks ahmed for your reply.I got one question.Is it safe to apply RUU downloaded from third party website.I mean is it guaranteed to be 100% stock without any chances of compromised security inside the RUU?
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
Depends on the RUU and the provider

You have to decide what you will do

You came here asking for help and when you find your answer you got suspicious :eek:

Anyway you choose if you want to download the 3rd party website RUU or not
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
The file says "signed". If that is true, there is virtually no way (at least form a practical/feasible sense) for it to be anything but an official HTC RUU. My understanding, the encryption involved with being a signed file is far too complicated for anyone to bother messing with (never heard of anyone breaking that encryption to make a file "signed"). At least, its not worth it to spend all the time to make it "signed" just for the purpose of malware, etc. Far too many other "lower hanging fruit" possibilities.

That being said, since are s-off, I don't know how you would verify that file is truly signed. With s-off, you can flash unsigned RUU files. With s-on, only signed RUUs will flash. But I don't know its worthwhile to go s-on just for the purpose of making sure the RUU is signed.

You've already flashed custom recovery and a SuperSU file, all from 3rd parties (maybe from reputable sources, or not). There is no more or less reason to believe those files are safe.
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
Hi ahmed, I assure you that i was asking that question about in a constructive way and i really appreciate your help and i think that's what i will be doing.I just put up my genuine fear/concern in a positive way.

Thanks redpoint for your reply.Yes i agree with you.I am gonna go ahead and flash that RUU as ahmed said.

I have my own full TWRP backup which i made before touching my M8 last year but it was from kitkat.

Can i run that backup to go back to kitkat and start from there?Thanks again ahmed and redpoint!!
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
if your backup is non rooted then you can just restore it and flash the stock recovery and do OTA ( multiple until marshmallow ) this way you will be sure that the download from HTC directly to your device

i'm curious to know how do you concern about the downloaded RUU while you have s-off rooted device ?
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
Its because i did rooting and S-off by myself (i am not an expert in any way.Did it by reading and getting help from XDA)on my brand new phone using third-party software (But well known and reputable sources-SuperSu and Sunshine).

I am not saying at all that downloaded RUU is infected or has some problem.It could be 100% stock and i might go that way you had described in your first post.I just expressed my genuine concern.But if that disturbed you then accept my apologies....
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
no need to an apology that's your own security

but my point is you did unlock your device bootloader,flash custom recovery,flash supersu and used sunshine to s-off ( for what purpose all of this )

you just killed all of this device security
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
Yes i know i did.

But don't you think that downloading RUU from unknown source (If someone has injected something) is more dangerous than doing S-off and unlocking bootloader?I think after s-off and rooting ,It depend on me how i use my phone.Hope you understand my point.

I think there is no end of this security discussion.We can stretch it as much as we want and better...:)
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
I can't say anything

But as redpoint73 said earlier the signed RUU is protected by htc sign keys and i don't think that someone will decrypt then encrypt the RUU to push a malware software inside it

at the end it's your device,your own security and your decision

do what you see right :)
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
The stock TWRP non rooted backup from the same phone when it was brand new is from android 4.4.3. Will it go backwards and accept that 4.4.3 old version? Thanks
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
yes it will update to the latest but you need the proper recovery version to flash the OTA
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
I think my question wasn't clear.

Right now i am android version 5.0.1 and the TWRP backup i have is from 4.4.3.

So my question is that will my phone accept quite old backup (4.4.3) without any problems? and then i can take OTA updates step by step?Is that right?Thanks.
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
yes it will work no worry
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
Thanks for confirming!! will try this weekend.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
You can use your TWRP backup 2.23.631.2 that you already have and you need to install 2.23.631.2 stock recovery to accept and install OTA but this is not productive. See option 2 below for the reason.

You have 3 options :

Option 1 :

You can install the RUU zip as mentioned in post #2 - http://xdaforums.com/showpost.php?p=70110165&postcount=2

It is a HTC Signed RUU and that's the reason why you need to use htc_fastboot to install the RUU not the generic fastboot

Personally, I don't like to use RUU as it is a hassle to backup all my files from Internal Storage as this RUU will wipe everything on the phone.

Option 2 :

As you have a S-Off device, you can use your TWRP backup 2.23.631.2 that you already have but you need to have stock recovery 2.23.631.2 installed to proceed with OTA.

But this is not productive as you need to accept and install multiple OTAs

2.23.631.2 --> 3.34.631.4 --> 4.20.631.2 --> 4.20.631.3

Also you need to restore all boot, data & system from 2.23.631.2 as your current data on 4.20.631.3 won't work on 2.23.631.2

Option 3 :

As you are running a rooted stock ROM (if not, you won't receive OTA notification) and on 4.20.631.3 firmware, the best for you is restore a stock non-rooted 4.20.631.3 backup.

You only need to restore boot & system, no need to restore data. This way you have all your data intact, no need to re setup after OTA to Marshmallow 6.13.631.7

You can get the non-rooted stock 4.20.631.3 backup and stock recovery 4.20.631.3 from my thread - http://xdaforums.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

1. Download the 4.20.631.3 backup

2. Download the 4.20.631.3 stock recovery

3. Restore 4.20.631.3 backup (select only boot & system)

4. Install 4.20.631.3 stock recovery

5. Reboot

6. Check for update

7. Accept, download and install OTA

8. Done.
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
Thanks a lot ckpv5!!! Will try as you described.I really appreciate your help!
[One (M8) Q&A, Help & Troubleshooting] ninja_zx11:
Hi ckpv5, Thanks for your help and i finally updated my M8 using your option 3.It really saved my time as i didn't have to delete my data and pics..

One question, Even after updating to marshmallow,the android security patch is still dated to dec 2015? Is it the latest patch and nothing came after?Thanks.
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
yes it's the latest

no more updates or security patches
[8125, K-JAM, P4300, MDA Vario Software Upgrading] SharpieMarker:
I was reading some information regarding WM7 and WM8 that microsoft are working on currently but what I was really wondering was, and this is only speculation at this time considering the lack of solid details regarding windows mobile 7 & 8, but if the wizard meets the minimum requirements for the new WM OS's do you guys think you will be attempting to port it? Any speculation?
[8125, K-JAM, P4300, MDA Vario Software Upgrading] xeno1:
I don't think any speculation is needed, I'm pretty sure the answer to that is yes.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] SharpieMarker:
There usually isnt a need for speculation but I was asking if anyone had any thoughts pertaining to system requirements or on the article I linked to. Or maybe just on any of the things microsoft are trying to accomplish in the new version. Just trying to start a dialog. Thanks.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] redtails:
quite frankly I don't think the wizard will meet the requirements of WM7 or WM8, although that's only my thought, there aren't any numbers to back it up, but you must admit 195mhz (which got put down to 170 for power saving) is not that fast for a pda, even the earlier models like the well known hp2210 had 312mhz to spare
[8125, K-JAM, P4300, MDA Vario Software Upgrading] SharpieMarker:
Yea, honestly I'm really disappointed with the processor. For the cost of the phone initially and what with HTC being on the bleeding edge.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] iriarteerick:
hey guys i have a pentium I runing with xp, why not my phone with wm7 or 8, just sit and relax maybe some good cooker may develope this for our dinosaurs (jejeje).

PD. BTW. I love my wizard it`s better than others.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] SharpieMarker:
Wow a pentium 1. Thats gotta suck. Here's to hoping.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mestrini:
I think you're being quite unfair to a processor that has been considered excellent in terms of speed/performance relation. And don't forget the fact that it was directed to a light WM5 and is still alive and kicking with muscled WM6 ROMs :p

And i believe you should simply forget the idea of WM7 & WM8 in Wizard because it's something that will take a while to release (if ever with that name) and, as the article says, with minimum requirements much, much higher
[LG V20 Guides, News, & Discussion] KedarWolf:
Worth the wait, pretty incredible to be honest. Got almost 56mb/sec down, over 36 up with Speed Test app.
[LG V20 Guides, News, & Discussion] netgh0st:
Did you switch to their LTE plan?
[LG V20 Guides, News, & Discussion] KedarWolf:
Yes, I did a few weeks ago.
[LG V20 Guides, News, & Discussion] netgh0st:
I was hoping I would be able to connect to the LTE network without the LTE plan, just not get the LTE speeds, but apparently they do not allow you to register on the LTE network at all without the proper plan. I checked in field test by forcing phone to be in LTE Only mode and I do see Band/BW: B66 / 15MHz, EMM state: DEREG, Sub State: ATTACH_NEEDED. I wish they could just give a $5/mo add-on to enable LTE on any existing plan.
[General Questions and Answers] MAsadJahangir:
I have rooted my Note 3 and install Note7 custom rom by DARKLOAD..

Its a great rom..It was working fine but suddenly some issues occur,

Camera is not working properly , some times work normal and sometimes only shows a blank screen specially back camera

sometimes mobile suddenly restarts.

i am new here and i rooted any phone for the first time..

I have samsung galaxy note 3 korean N900L
[General Questions and Answers] Droidriven:
Did you factory reset and wipe caches before installing your custom ROM?
[General Questions and Answers] MAsadJahangir:
Should i install this rom again or is there any process to solve the issues especially the camera
[General Questions and Answers] Thunderoar:
It's a bug, everything that isn't working right is called bug,

Report this issue to the rom developer.

He the one who made it and the one who can fix it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
About Us:

Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.

We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and again, gain contributors. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew even more and learned a whole lot more.

It has been an awesome learning experience and is still not over! We are still learning every day and continue to move forward. Lastly, we DO NOT accept, nor ask, for donations. We don't believe in that. Everything that is necessary to keep this project going is out of our own pocket. Gerrit, Jenkins, Websites, Devices, etc. We will never ask for a dime. All we do ask, is that you have patience, search, read and try to enjoy the process with us!!

This build comes with GApps pre-installed and no SuperSU. A flashable package for GApps is in the works, as is proper linking for SuperSU.

All of the major necessary functions work. WiFi Calling on VZW is not working. That is the only issue that I have encountered in the last 24 hours.

Kernel Source:

Flashing Instructions:

- Verify that you're using the latest version of TWRP for sailfish

- Perform a FULL WIPE as described below

(A full wipe is when you wipe system/data/cache)

- Flash the Dirty Unicorns Rom package

- Flash the TWRP installer, again (YES, for real)

- From TWRP, reboot to bootloader

- Disregard the "NO OS INSTALLED" message

- Flash the vendor image using fastboot (NMF26O - not AOSP current, will change soon)

- Reboot and ENJOY!![/b]

**If you fail to follow these instructions, please don't bother reporting any bugs**

**If you use Xposed, please don't bother reporting any bugs**

**If you use another kernel, please don't bother reporting any bugs**[/sub][/mod]

Download link: Mod edit: link removed at developers request

Google+ Community: https://www.google.com/url?sa=t&sou...THl2Sq0BmZc0OmRYA&sig2=xk6QSYGgq8xUboA2fTbUzQ
[Google Pixel ROMs, Kernels, Recoveries, & Other De] SynisterWolf:
Thread Closed,

Permission must be obtained before posting others work.
[YotaPhone] TheArt.:
Hi all, I have a YD206 flashed with 124 RU keeping the CN radio. Then updated to 134.

I noticed that the proximity sensor stays always active, you can also see it with naked eyes, no camera needed.

What can I do to enable it only during calls?

EDIT: SOLVED. See the All-In-One guide to know how
[YotaPhone] tazzix:
Got the phone yesterday and updated to lollipop right away. I can not locate the sensor even with a camera.
[YotaPhone] Avv.Kobayashi:
Hi,

it's the same for me.

I have flashed 5.0.0 RU.124 + 4.4.3 CN .32a radio folder (now, after OTA update I have RU .134) and the proximity sensor always blinks.
[YotaPhone] muidumees:
did exactly the same flashing process, but prox. sensor is working like it should for me. strange
[YotaPhone] sibKM:
Also for me. Always active when the main screen is on :!
[YotaPhone] dmix_shinri:
update 4/1/17 14:43pm (gmt +8)

- I tried with another simcard from different provider, seem only 3g (hspa) and 4g (lte). no 2g network

- 1st sim Digi Malaysia - gsm 900, 1800/ umts 2100/ lte 2600

> test got all edge, hspa, lte

- 2nd sim Maxis Malaysia gsm 900, 1800/umts 2100/lte 1800+,2600

> test only got hspa, lte

maybe this radio for gsm only got 1 working band either 900 or 1800

update 4/1/17 11:06am

- if I run antutu benchmark, that proximity blinking come in. need to close and clear it from memory then it gone.

First, I didn't realized that problem until I read about that problem

- I bought yd206 with 4.4.3 hk 61 firmware.

- I manually update to 5.0.0 hk 1.1.66

- ota to 124d

- read about no 2g/3g network. I check mine also got this problem. read about manually update radio to cn 1.0.3.32a (fastboot). I did update and got all 2g/3g/4g

- at this stage I didn't know about problem of proximity sensor always blink/on and not check to verify it.

- I manually update to ru 124 by replacing ru radio with cn radio and ota to 134

- read about proximity problem. verify by using camera. yes it always blinking.

- I tried downgrade using yotaflasher to hk 66. failed. bootloop

- update using fastboot also using cn radio. success update

- sadly still got this proximity blinking

- ota to hk 124. same problem..

after all that and days of days.. I thinking, how about I try radio from original firmware that I got when I bought my yotaphone, which is hk 61a.

so I did, fastboot.

YES! it work, no more blinking and I got all 2g/3g/4g

baseband now s01_003_3034_ru1_m15_p2.. :confused:

dmix.
[YotaPhone] TheArt.:
Hi [MENTION=7974822]dmix_shinri[/MENTION] I also noticed that the blinking sensor is when you use CN radio in a different firmware, so I flashed like you HK 66 radio (which is identical to the RU radio) and I don't have blinking. The problems is that on this radio I don't have 2G and 3G is a bit weaker. Instead on CN radio I had full 2G signal.

My configuration is:

radio: S01_003_4240_RU1_M05

firmware RU 134

I'll check again with yours, but I'm sure I already tried it.
[YotaPhone] dmix_shinri:
[MENTION=1303378]TheArt[/MENTION]

Take radio from 4.4.3 61a firmware. Not from 66.

Ur baseband will became RU1_M15_P02

Hope this solve some problem. Do note that for 2g/gsm only either band 900 or 1800 only not both available. I think only 1800.
[YotaPhone] TheArt.:
flashed 61 radio and 2G still doesn't work. It was the same with 66 radio. Proximity sensor doesn't stay active in both of them.
[YotaPhone] sibKM:
Here where I live i can't be without 2G, so maybe we could try to reach out to some dev? Also, anyone tried the MM beta fw? still blinking?
[YotaPhone] dmix_shinri:
after using radio s01_003_3034_ru1_m15_p2, I cannot cast to screen/mirroring.

so I tried flash radio cn.

yes, still got that proximity blinking BUT only when screen turn on. OR when there is activity at back screen/epd.

previously if i used this radio cn, I got this blinking every time unless I turn off the phone.

I got two radio cn from two earliest and latest cn firmware. got different date and same size. when compare hex/binary, got different in few place. so I tried flash this old radio cn.

yup.. still got same problem, proximity blinking but the blinking seem not stop (as I didn't try long enough). so I play with *#*#4636#*#*. used some method one former mention here to select option with all network (before unknown), radio off, radio on, select 2g,3g,4g..

now the blinking will turn off as screen off (few second).

for cast screen, I didn't test yet. I will stick to this radio (for now), as the blinking doesn't bother me anymore.

now my baseband radio is S01_003_3034_CN_M01
[YotaPhone] TheArt.:
I'm not sure if I understood well, you found a radio which make the sensor blink only during screen on (and EPD screen on), right?

That's progress, even if it's not the final solution.

Where CN M01 can be found?
[YotaPhone] dmix_shinri:
[MENTION=1303378]TheArt[/MENTION]

When i change to CN M05, i notice the blinking stop when screen is off and no epd used.

I have another CN radio (M01) rom first kitkat cn firmware (at yota server). I compare with CN M05 and both file not identical in content. So i tried flash it to see any different.

Result with CN M01:

Blinking. Even screen is off (but i didnt leave phone with screen off long enough to verify either blinking stop)

For now it only detect lte, take time to detect 3g/2g

So i tried select network gsm only, wcdma only.

Still blinking when screen off.

So i enter mode *#*#4636#*#*

So i select all network, radio off, radio on, gsm only, wcdma only, lte only, did random thing

Then i notice blink stop few second (7s) after screen is off.

So, u can try with CN M05. Enter mode 4636..

Fyi. I m on HK 124d.

Cast screen still not working.

I thing i already test it first time with RU modem, its working.
[YotaPhone] 7Stormwarrior:
I have try something on second yotaphone I have, (HK edition) that still I don´t have change the rom.

It blinks only when you use a sim, rest of the time works ok (WIFI, bluetooth...) its very strange... As I said before I didn´t modified anything on it

https://postimg.org/image/5i77lflj3/

In other yota I have flash a lot of different roms and have always the blinking when using a sim on it...

I don´t understand very well how can I do to stop blinking (At least when screen is off) could you tell me what rom / radio to use? And what can we do on 4636 menu? There are a lot of options on it....
[YotaPhone] cvzalez:
I discovered that I also have this problem, I was with the wrong radio, had to flash the Chinese radio and it suddenly appeared, this is what I have found I have an YD206, so I wonder how the YD201 behaves:

On YD206:

With wrong radio. radio (Russia xx versions) on YD206 , in KitKat or Lollipop ROMs the proximity sensor is OFF by default BUT, as soon you turn ON an app that uses it, it won't turn off again, it keeps blinking even if you force kill the app that started. However it will turn off if the screen is off, after 5 seconds after. Also it's important to acknowledge that 2G only with this radios fails. On Lollipop Wifi won't turn off automatically, just manually.

YD206 With the correct radio. radio S01_003_3034_CN1_M05 2G 3G (UMTS) and 4G (LTE) all work and with better reception, but as soon the screen is ON, the proximity sensor starts working, does not matter what app you have open, when you turn OFF the screen the proximity sensor will turn OFF in about 5 seconds. If you are using the EPD screen the proximity sensor will turn OFF faster than 5 seconds, but as soon you touch the EPD it will turn ON for 3 seconds or so. On Lollipop Wifi won't turn off automatically, just manually.

So the problem acts differently when you flash a different radio, I am not sure where's the bug comes from, but it seems there's also a bug with YotaRom. There's a Xposed module to disable proximity sensor in specific apps, I haven't tried that, I also would like to know how this behaves with the Marshmallow Beta.

(For the ones that are not aware of this problem, keep in mind that to see this problem you need to be on a dark place to see the very faint red light of the proximity sensor.)

Best regards,
[YotaPhone] Dahlan abdullah:
Blinking has stop by using RU1_M15_P2 on my latest RU firmware by ota update.. just flash radio folder with yota flasher then leave them on.. blck pic is after in few minutes screen off blink not appear..

But my problem for now is,

1.i cant using epd screen anymore by transfer button from coler display

2.screen still on and cannot sleep when make some colling.

3.trying to test sensor from 4636 and is stop working

3. Downlod some apps from store to test sensor and said NO PROXIMITY SENSOR

What the hell of this problem guys, :confused:
[YotaPhone] queser.info:
The only hope is Android 6!
[YotaPhone] SpPes:
Just to inform.

I have 6.0 RU1.1.31 Baseband S01_003_3034_CN1_M05 and I see no red Proximity Sensor .
[YotaPhone] R00S:
Same here:

I never changed the baseband from the 4.4 one on my 206. Just installed twrp and installed a MM backup from my 201.
[YotaPhone] TheArt.:
The problem has finally been solved! Using a hybrid baseband we can have all the benefits from both modems, see the all-in-one guide for more details: https://xdaforums.com/yotaphone-one/help/guide-everything-to-yotaphone2-t3547194
[YotaPhone] Pak07:
Small tip: Telegram also activates the sensor all the time, unless the option "Raise to speak" is off.
[YotaPhone] dmix_shinri:
I already used patch version ru-cn. Reception signal for 2g very bad..