yashsingh1/xdaforums huggingface dataset:
[Mate 8 Q&A, Help & Troubleshooting] hamadazh:
I don't know :D but I'm in the way and there's no 4g network in this area but I think and must be icon appear when I make call but nothing appear I think like you said not working.
[Mate 8 Q&A, Help & Troubleshooting] hamadazh:
So what the benefit from that option that appear in network setting ? Useless?:D
[Mate 8 Q&A, Help & Troubleshooting] Frank1207:
[MENTION=5107139]hamadaz[/MENTION]

i think the changes in build.prop, do only ad the VoLTE-swith in Mobile Network menü.

There must be also changes in Baseband Firmware.

Because the baseband Firmware handles the radio-unit/frequenzes.

And i ithink, we can all find it, in Huawei P9.

P9 is official listted in Germany at Telekom and Vodafone, as VoLTE enabled device.

And is has the same SoC, with integrated Baseband-unit, as Mate 8

Mate 8 has Kirin 950, P9 Kirin 955

Kirin 950 and Kirin 955 is identic Hardware.

As Kirin 955 is only higher clocked.

So we must copy the baseband Firmware from P9,

or edit the entries llike it is in P9

Greetings from Cologne,

Frank
[Mate 8 Q&A, Help & Troubleshooting] Georgian51:
What should be taken from P9? I'm testing if there's a little chance
[Mate 8 Q&A, Help & Troubleshooting] Frank1207:
[MENTION=8853473]Georgian51[/MENTION]

What we need, to make ist work, is the firmware part, of baseband unit ( Radio unit part of the Kirin SoC)

Mate 8 and P9, is from SoC-Hardware definitely the same.

Kirin 950----> Kirin 955 in P9, ist only a higher clocked Kirin 950.

Greetings from Cologne,

Frank
[Mate 8 Q&A, Help & Troubleshooting] hamadazh:
Editing buld.prop in vendor useless without carrier support

I think it's carrier support, and I think my carrier doesn't support volte.

now I have new thing,, if you put this line this will activate video calling:

persist.rog_feature=1

View attachment 4569839

And video calling option will appear in contacts when you want to make a call

View attachment 4569841

And when I tried to make video call said ( your current network doesn't support video calling :eek: so it's useless too without carrier support.

And now I knew my carrier (Vodafone) doesn't support video calling and volte too in my country :D
[Mate 8 Q&A, Help & Troubleshooting] Frank1207:
Maybe it´s the same thing with this Video-Call Button,

as it is with the VoLTE-Switch.

This editig entries in the build.prop, do only ad the switch in the user-interface/Menu

So you have also to edit the Baseband Firmware part, to realy make it work.

Greetings from Cologne,

Frank
[Mate 8 Q&A, Help & Troubleshooting] Frank1207:
Noboady here, who owns a Huawei P9 ??

So we can look in it´s build.prop and Baseband Firmware entries,

to edit it in Mate 8, to the same values, to make VoLTE work.

Greetings from Cologne,

Frank
[Sony Xperia M5] bunleng234:
Reason I was flash rom.zip of redmi note 2 created with stock Sony rom and boot.img but i not delete uboot of remi note 2 so when restart from twrp my black screen no vibration and nothing at all and no fastboot mode & flash mode too could u help me to flash with usb serial device com3??
[Sony Xperia M5] BonnyBedlamBoy:
as far as i know it sounds like a bricked device. my hope for you that i am wrong...
[Sony Xperia M5] ih8redsn0w:
This has happened to me but from a different way. I think there is a way to get it back with mediatek flash tool but I'm not too sure so you will have to do some research. As far as what I know it is bricked and you will most likely need to send it to a repair centre
[Fire TV Q&A, Help & Troubleshooting] x000x:
I would like to get one, but use it on a hotspot/tether from my phone. The chromecast was never able to connect to my cellular hotspot, and it was mandatory to connect to a wifi connection.

Does the fire tv stick have the same restriction? Or can I use my phone's built-in tethering/hotpot and connect it to the firestick?
[Galaxy S 5 Q&A, Help & Troubleshooting] georgeyj:
Is there any way to make s5 fingerprint active (to wake directly from lock-screen by fingerprint,without turning the screen on)
[Galaxy S 5 Q&A, Help & Troubleshooting] AlBaraa98:
theryre working on ported roms from s7 but this have non working fingerprints

so you have to wait
[One (M8) Q&A, Help & Troubleshooting] carljames0603:
Hi all,

My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.:confused:
[One (M8) Q&A, Help & Troubleshooting] carljames0603:
It might be worth mentioning it boots into extreme power saving mode too.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?

On the bootloader screen, what is the OS number?
[One (M8) Q&A, Help & Troubleshooting] carljames0603:
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.

Always provide as many details as possible when asking for help and answering our questions.

If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).

From there, tell us what OS number it says on the bootloader screen, near the top.

What makes you think that? You haven't provided any details or evidence that would support the statement.

Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.
[One (M8) Q&A, Help & Troubleshooting] carljames0603:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.

The OS is 3.28.605.4
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.

I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.

Hold down the vol down button during the next reboot cycle, and it

will

go to bootloader. It may be that some set of conditions is just making you

think

what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.

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

Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?

When you do go to bootloader, it stays there (doesn't reboot)?
[One (M8) Q&A, Help & Troubleshooting] carljames0603:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.

Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.

The bootloader is locked, and it stays there until I push it to reboot.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.

Or there is the kingroot method, which has some mixed results.

In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.

You can get the RUUs from here: https://xdaforums.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).

You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.

---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------

Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
[One (M8) Q&A, Help & Troubleshooting] carljames0603:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
did you read the post you quoted ?

redpoint73 said clearly what you need and where to find

you used a different RUU and it will not accepted by your device ( in red above )
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).

Further, you posted that you "downloading the SU app as prescribed in the site".

What

website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.

If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.

As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the

proper RUU for your Verizon version M8

was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick -

possibly permanent

).
[One (M8) Q&A, Help & Troubleshooting] carljames0603:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.

Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your

posts

is not the same as attacking a

person

(which

you

did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).

You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] tschombe:
Hi,

i flashed the TOFCLOCK HIMA WM6 AKU.0.7.0 Fresh

upgrading from WM5.

After that I restored a Sprite-Backup that I made from

WM5 to get all my Apps up and running.

Everything works fine so far, only the camera-button is

not working. It says "Error opening the shortcut or locating

the target filename".

I tried to reconfigure the button under Start->Settings->Button

but there I cannot find the Camera Application???

It is gone somehow. I also dont find it with file-explorer.

Can someone tell me the NAME of the Application, where it should

be located? \Windows - folder I guess???

And can I separately install it, do I only need the exe or also some

dlls.

Can someone provide me the files?

Thanks in advance for any help

Greetings
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
did u hard reset it after Flashing

the NO,YES,YES Way
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] tschombe:
Yes, I did this.

I also checked the camera BEFORE applying my Sprite-Backup

and it worked there.

Unfortunately I did not check the filename of the camera app

or saved it.

It is a bit strange since I dont know exactly how sprite backup

applies its backup...

Also I dont want to redo the complete flashing process since

my sprite backup is not up to date right now and my pc for

syncing is at my workplace...

So my Idea was to just "reinstall" the camera app or just

copy the files to the pocketpc to get it working again.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
The problem is your backup..u say that u made the backup from Wm5 and restored it to WM6....Even windows has some limitations...WM5 Is a lot different then Wm6.U cant run WM5 Backup on WM6..my advise is that u hard reset it and then see if its working
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] tschombe:
I know that sprite backup causes the problem.

but I use some apps (financial and business organization)

that I dont know how they store their data on the pocketpc

and they dont sync anymore with vista and new windows

mobile center.

Currently spritebackup is the only way I get them to work again

on WM6 ;-) so I need to apply it.

Since I dont have any other problems right now beside the

camera I am pretty happy with WM6 on my "old" device.

I dont need camera very often but every now and then it

comes in quite handy.

I guess I wait till i come back to my workplace next year,

make a current sprite backup then reinstall WM6, save camera app,

apply sprite backup, apply camera app ...

and see if it is working.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] The_hesham:
Hi, tschombe

go 2

windows\start Menu\Programs\camera.lnk

the shortcut should read

:MSCAMERA?shellres.dll,-8263

then soft reset
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
first copy the shortcut from ur ppc to pc and drag it on a notepad..their u will see what hesham wroted..if it doesent match..fix it..and overright the shortcut by copying it back
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] tschombe:
sorry, I was on vacation for a while.

I tried the above solution, there was NO shortcut, so I created

a new one with notepad and copied it to my ppc

Now I have a shortcut that opens FileExplorer on the root folder,

when I tab the shortcut?
[Huawei P9 Questions & Answers] azgooon:
Hi,

I must admit that I am panicking now because looks like i have bricked my phone and no matter what i try to do i am stuck between erecovery fastboot and TWRP.

To give you some light as to what actually happen... I've replaced oeminfo in originally EVA-AL-10 with EVA-l09. I have installed full system EVA-L09C432B136 and everything was fine at that point.

I thought to myself that it would be nice before putting any data to the phone to actually rebrand it to L19 so i do get a dual sim support.

In another thread I've found oem info for L19-C432. I've replaced it and decided to reflash full image EVAL19-C432B161 which i've also found on this forum due to huawei servers being down? (for some reason I couldn't download anything from the manufacture sources) This is when i got a first error message that updated failed due to incompatibility with the device.

I have been looking for some other full packages but whichever one I've put on a SD card, i couldn't get to work. for some stupid reason i thought about updating B136 hoping that during update process incompatibility issue will get fixed. Unfortunately this wasn't the case and even though the update completed "successfully" on the screen, after the reboot, i ended up in eRecovery.

Having oeminfo in SRK tools which worked for me previously i unlocked bootloader again and installed TWRP so i can root my phone and use srk to update OEM info back to 09.

This is where serious problems started to happen. in TWRP I am unable to use touch screen, only volume buttons and power button to confirm. As its a first launch of the TWRK I cannot even swipe to confirm read/write mode hence I can't go any further to install supersu etc...

Do you have any suggestions what can I do to unbrick it? Is there any workaround to get root via sd card? or maybe forcing somehow stock rom L09C432B136 to install regardless? Maybe there is a way to repack update.app so i doesn't look at the oeminfo?

I have tried replacing images (CUST, BOOT, RECOVERY and SYSTEM) in fastboot mode but I am not having any luck whatsoever.

Please throw me any ideas...

Thanks.
[Huawei P9 Questions & Answers] douyi:
Hi azgooon,

I'm having the same problem, even it's a different huawei phone, did you get your problem fixed? How? Thanks for sharing.

douyi
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cjkacz:
Our Jenkins server is building our weekly builds as we speak. Builds will be found here when completed

https://www.teamoctos.com/oct-n-test-builds/

Please follow the install instructions in this OP. Pixel devices are not the same as Nexus , please familiarize yourself with your device before attempting to flash anything on it.

Remember this is an Alpha build. It has been tested thoroughly but you will find some minor bugs. We will continuously be updating and making it better! Enjoy!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] mrjaydee82:
Nice to see you over here :P ...Been running Pure..I'll give this one a go.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] rockrulez11:
Excellent work OctOs team! So excited to see some new roms on the XL!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cjkacz:
Build is up! Go get it :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
Got the "vendor image may be out of date" message which is an easy fix if you tell us which boot img to flash?

I think I'm on the newest U. Or I was at one point recently.

WiFi, data & calls works.

Ok Google is busted like on other AOSP ROM's but the beta is out there somewhere and supposedly works.

Thank you for the ROM!

A future feature request would be SlimRecents. :P
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cjkacz:
Flash 26U again. Some reason it sometimes doesn't stick first time around
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aholeinthewor1d:
Nice to see more ROMs. Thank you!! Any plans for a non XL version? Also looks like you missed the "flash ROM" part in your install instructions
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cjkacz:
Flash rom is #4 on the install instructions. Yes I plan on working on sailfish soon
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aholeinthewor1d:
Is my XDA app acting up again.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cjkacz:
Ha ha I guess it is
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] aholeinthewor1d:
Holy sh@#...

How is that even possible haha. I don't get why I have so many issues with this app.. starting to wonder what else doesn't show up correctly. Who knows what I've been reading every day haha
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 557953:
Great work looking forward to having a play sometime over the weekend, many thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cntryby429:
That's weird. I see the same post he does which doesn't mention rebooting to recovery and actually flashing the rom. I never knew the xda labs app had such a bug. I rarely use desktop so who knows what I've missed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] cjkacz:
I'm using the original XDA app. PC shows it also. It's strange for sure that such a bug can exist. Important information can be missed!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Guessphx:
Weta rom was having issues when flashing with rc1 I just want to make sure that its good to go before flashing.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BakedTator:
All works well, flash away man...I will say Download SuperSU 2.79 SR2 and use it
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Guessphx:
Thank you I appreciate the response!

---------- Post added at 09:14 AM ---------- Previous post was at 09:10 AM ----------

Possible to get 3minit battery mod running with this rom?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] BakedTator:
This ROM has its own battery options my friend
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] raynan:
I'm trying a few things, but I'm getting issues flashing. It seems my downloads are missing the "update-binary". I double checked the zips and can't find it on my desktop. Any ideas?

Never mind...I thought I was on TWRP RC1
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
You flash in TWRP from internal mem
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] napoleontheruler:
Do I need to update the radio and boot img before I flash or will rom do it when I flash rom
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
Looks like Google Camera is broken on this 3/03 release like it is on some other ROM's too. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] tatootie67:
Just go by the OPs instructions to the letter if you're setting this up new

---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------

Is it totally broken or just the video!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] CZ Eddie:
just 30 frame video. it eventually crashes.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] napoleontheruler:
How do i flash vendor it doesn't show in twrp
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Wacky2bakky:
It's a image, have to choose to flash image at bottom of twrp
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] napoleontheruler:
When I try to flash rom I get error couldn't find meta file. I have all the files in my downloads folder do they need to be on root of memory
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] DaveHTC200:
I'm guessing you're not on RC1 twrp?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] napoleontheruler:
So do I flash that one from the one I'm currently on?

---------- Post added at 01:23 PM ---------- Previous post was at 01:17 PM ----------

Thanks that was the problem

---------- Post added at 01:25 PM ---------- Previous post was at 01:23 PM ----------

Ok lol now which partition do use to flash vendor please and thank you.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yankeesfan714:
Damn, I'm glad I read this before my sons baseball game. I would have been devastated if I lost one of his At Bats. Does it crash on 60fps too?