yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 / S6 Edge Unified Development] :
That isn't right version I can tell... [MENTION=4921688]The Sickness[/MENTION] will release completly new compile but now he have little bit bigger problems (can look HERE and HERE) then kernel.
[Galaxy S6 / S6 Edge Unified Development] sohailss111:
Oops. Really sorry. Hope everything gets back to normal soon.
[Galaxy S6 / S6 Edge Unified Development] ridwan.sn:
AOD support on this kernel?
[Galaxy S6 / S6 Edge Unified Development] The Sickness:
No. And I will never add it. Sorry.
[Galaxy S6 / S6 Edge Unified Development] ridwan.sn:
Ohh okay thanks ?
[Galaxy S6 / S6 Edge Unified Development] lkbass:
My display after winning has negative colors ... My phone is g925f Rom nne 5.1 s8 port
[Galaxy S6 / S6 Edge Unified Development] The Sickness:
Your on a port...my kernel is not your problem
[Galaxy S6 / S6 Edge Unified Development] :
Mate, I hope Twisted for S6 isn't unreleased? That was intrested one and I really waiting for new release.
[BlackBerry Priv] bullriders:
I've had it for a couple of weeks and today I got a SIM Not Inserted error then phone shut off and will not turn back on.

Second problem is that I'm traveling and have no computer to try to see if it will boot into download mode or use the VZ Assistant app try and reset
[BlackBerry Priv] organic2:
You should dont use any other charger on blackberry priv. Maybe 2 fiuse in charging PF in the phone is breaked. And fix easilie by repairman
[BlackBerry Priv] bullriders:
Update

Seems that computer recognizes the phone, I them used the BB recovery tool and it also recognizes the phone and completes the recovery process without errors.

Screen still won't turn on
[BlackBerry Priv] venkatanonymous:
i boot my blackberry priv phone, after that unable to turn on my phone.

What shall i do?
[ZTE Axon 7 Questions & Answers] skyguy126:
Trying to flash the ota that brings me from B27 to B29 (Android 6.0, M) so I restored my system image and the boot partition. I have not touched any other partitions since I unlocked my bootloader using this guide: https://xdaforums.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 and then this guide https://xdaforums.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165

I flashed the correct stock recovery for B27 (removing twrp) and tried to upgrade to B29 via the settings menu once the phone booted up into Android. The recovery log spits out an error message along the lines of:

"contents of partition ... aboot didn't match EMMC ... doesn't have any of expected SHA1 sums. Script aborted: partition aboot has unexpected contents"

"Failed to stat /cache/saved.file: no such file or directory"

"failed to load cache file"

"script aborted"

Any idea what I'm doing wrong or anything else I need to fix beforehand?
[ZTE Axon 7 Questions & Answers] supergear:
Isn't B29 Nougat?
[ZTE Axon 7 Questions & Answers] skyguy126:
[MENTION=1915837]supergear[/MENTION] I believe its still Android 6.0
[ZTE Axon 7 Questions & Answers] Choose an username...:
I still don't understand the U's updates... I think there are both B29 M and N.

I still think ZTE should've used M29, and N29, then O01... Much more understandable than this crap

Try using MiFlash. The good thing about it is that you can use it even if you have half of the phone... Just put it on EDL, and use the corresponding FULL EDL package (DO NOT use the A2017 or A2017G's!!}
[ZTE Axon 7 Questions & Answers] skyguy126:
[MENTION=7799420]Choose an username...[/MENTION] will give it a go and report back; thanks! It doesn't lock the bootloader right?
[ZTE Axon 7 Questions & Answers] Choose an username...:
Nothing locks the bootloader but the command (oem lock). But don't use it unless your device is totally, COMPLETELY stock (stock recovery, stock system, stock BL).
[ZTE Axon 7 Questions & Answers] tabletalker7:
How did you get on B27 in the first place? If you used a TWRP image or flashable zip to get there the OTA won't work (at least it never did for me).
[ZTE Axon 7 Questions & Answers] William Guo:
Ok

:)
[ZTE Axon 7 Questions & Answers] skyguy126:
[MENTION=7065364]tabletalker7[/MENTION] came installed with the phone, US version.
[ZTE Axon 7 Questions & Answers] tabletalker7:
OK I just read up on how you unlocked and got TWRP. Have you considered backing up your info and just using a TWRP version of B29?
[ZTE Axon 7 Questions & Answers] skyguy126:
[MENTION=7065364]tabletalker7[/MENTION] where can I find the zip file, as of now the only zips I am finding are for B20 and B27 (Marshmallow) and the Nougat ones.
[ZTE Axon 7 Questions & Answers] tabletalker7:
https://xdaforums.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 post #2 has a b29 rollback file there. Flash it in TWRP, then flash TWRP again.
[T-Mobile LG V10 Q&A, Help & Troubleshooting] jetkov:
Would anyone be able to provide a full (anonymized) dump of software version H90130b Nougat of H90120L MM? I am trying to debrick a phone in QDLoader 9008 mode.

A compressed IMG file would be helpful.

I'm planning to flash it to a removable SD card and boot off the SD. It will not boot properly a dump of V20J but I can't find any full dumps of newer software versions to try.

Thanks!

- Alex
[T-Mobile LG V10 Q&A, Help & Troubleshooting] Wilson_Proano:
If you tell me how I can give the dump .I was on 6 and update to 7 with knowing theres no root for nougat I have V10 from T-Mobile, I try to root this phone because is network locked let me know
[T-Mobile LG V10 Q&A, Help & Troubleshooting] jetkov:
I don't actually need this anymore at the moment, but it might be useful for others. Normally you cannot make a dump without root access, but you could look at this thread: https://xdaforums.com/lg-g5/how-to/unlocking-lgup-features-fun-profit-t3634650 about hacking LGUP to allow access to features such as dumping (without requiring root).
[T-Mobile LG V10 Q&A, Help & Troubleshooting] faisalmaliksgd:
kindly guide how to make bootable sdcard from rom dump, i need it badly.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jgmdean:
So, having caught up on my reading about the Kaiser using standard software video drivers instead of hardware I have to ask what to me is an obvious question:

Why can one of our chefs not "acquire" the drivers from a WM6 device with the same chip and bake them into a Kaiser ROM?

Incidentally does the chip vendor have any reference drivers?

Or am I missing something here?

James
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] undac:
No reference drivers are available.

Attempts have been made at making drivers from another device using the same chip work on our HTC products, so far it got us nothing.

We won't see a new HTC device using the same chipset again so "porting" drivers from a newer HTC product is also out of the question.

So.....

Either HTC coughs up the drivers.

Someone with a lot of spare time and intimare knowledge "rips" the drivers from another device such as the LG KS20.

Someone with even more time and knowledge writes new drivers (not very likely to say the least).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
Chainfire already tried this if anybody bothers to read through the OpenGL ES thread, especially, the new people near the end of the thread.

Nobody has tried to cook a rom of it though that I know of, and cooking means all of the linked driver files, not this one file people are passing around like a pot hit.

However, I think Chainfire was pretty thorough and it's not likely cooking would be any more successful.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Isaygarcia:
a KS20 ROM can be ported to Kaiser? (i mean, all generic and hardware drivers) and then make an Hybrid with another kaiser WM6 or WM6.1 rom? it could work..
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] undac:
From what I can remember Chainfire did try to cook it (he was refering to constant reflashing in the other thread).

And all due respect to Chainfire but I'm sure he's not the only person in the world who could potentially pull this off.

From my point of view he just proved that it certainly isn't going to be easy, not that it is impossible.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Chainfire:
Indeed I did do multiple attempts of cooking, with uncountable different versions, hacks, etc. You don't even want to know all the things I've done to get it to work. In the end it was all fruitless and I decided I had spent enough precious time on it without satisfactory results. I don't believe it is impossible at all (just nasty) and there are probably a sizable number of people,

some here on XDA, even

who could possibly do it, given enough time and access to relevant devices. I am neither a noob nor a novice in these matters, but I will happily admit that this is beyond me and will remain so unless I spend a couple hundred more hours ont it (which I won't - sure I have many more ideas how to fix the remaining issues, but I have a company to run and don't think it's worth it).

Furthermore, another reason I stopped trying to do it is because the KS20 drivers have their own issues, so even if it did work, it's still is not a fix-all solution, which eventually makes the whole thing not worth investing hundreds of hours. Not to say it would be impossible to combine the good from Kaiser with the good from KS20 etc. It's a time thing.

It's also possible the WM6.1 releases resolve a couple of compatibility issues - though not very likely - to be honest I haven't even looked at

that

yet.

As for the D3Dm file that is going around... Complete and utter nonsense, as posted in other threads (with explenation), don't let it get you.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ericc191:
Sorry if I'm thread jacking.

Chainfire,

It seems that the official response from HTC has quieted us down a lot. I'm not seeing very much going on anymore since then. Have we all kinda lost hope and feel it's time to throw in the towel? Or maybe it's just in my head and we are all still fighting hard to get HTC to fix this for us.

Also, I read a lot of replies where HTC said they are working on a fix for mid to late feb but I think those were false reports.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Chainfire:
Things are still going on, all I can say :) (just painstakingly slow)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Michaelr219:
This may help...

I was recently at the "pocket hack master" website (i cant remember the name of the company) and as far as I know, they are trying to work out a solution to the qualcomm chip in our kaisers... I doubt theyll be able to provide the missing drivers, but hopefully will atleast provide a boost in the screen response for our phones.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sWuRv:
I think the pocket hack master guys are trying to find a way to overclock the processor, not write new drivers for it. It would help response times to overclock but It won't make up for the lack of drivers. Just imagine if we had those drivers and were able to overclock. I would be pretty sure-footed about bragging that my phone was an Iphone killer. Our phone has the potential to be a bad motherfu$%er, I just wish that HTC gave a ****e about what it's customer base thought, and less about how much money they can milk out of each device. If they released those drivers, in my opinion they would have created the Iphone killer before the damn Iphone even reared it's fruity face. I used to take pride in owning HTC devices, they were the best devices available at one time. Tides have changed, and now HTC's got some competition, and in my opinion, they are failing to stand their ground. I still love my kaiser, but next time I buy a device this whole driver debacle is gonna be whispering over my shoulder telling me to go for the Eten glofiish, or some other windows mobile device, and in the end, may be the deciding factor in leaving behind my high school mobile sweetheart. Dammit I want them drivers lol. Anyways, rant over. Sorry for threadjackin'. Cheers!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Michaelr219:
couldnt agree more, well said. im sure we'll find a fix soon enough, there are a lot of talented individuals who dwell on this site... something will rise from the abyss, i can feel the breakthrough coming lol and we'll all shout from the rooftops... "haha apple, victory is mine" like stewey griffin :p but till that day... we'll just have to wait and wait and wait for htc to tilt some new drivers our way. but yes... rant over
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
I've tried disassembling the drivers from the top down since we know how the API from D3D/OpenGL works, we just don't know how to interface with the Qualcomm crap. But sadly it going to take a lot of time, and the last time I touched ARM-like assembly was on the 65816. x86 experience doesn't apply.

I do appreciate the Kaiser is more powerful cpu and graphics-wise than the PSP and the DS, but oh well.

Thanks Chainfire.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ericc191:
The MSM7200 is more powerful than what's in the DS and PSP? lol
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] undac:
Wll not quite as good as the PSP but certainly a bit better than the DS, according to Qualcomms own comparison charts at least.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
Unless you'd just agreed with me,

DS: yes (ARM9 + ARM7 + specialized multimedia): http://en.wikipedia.org/wiki/Nintendo_DS#Technical_specifications

PSP: toss-up (custom mips cores w custom chip support): http://en.wikipedia.org/wiki/PlayStation_Portable#Design_and_specifications

page 4: http://brew.qualcomm.com/bnry_brew/pdf/brew_2007/Tech-303_Ligon.pdf
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jgmdean:
Everyone thanks for all the responses. Full disclosure: I work on the technical end of High Tech, although at the opposite extreme: Big, bad ass servers and clusters. I too am no ARM assembly guru, but I have messed quite extensively with some ARM based home NAS devices. I'm not dissing anyone, but I guess I should have been more specific in my question and asked for more specific answers:

WinCE like the rest of the Windows family has standard APIs for graphics, with all the nasty, bare-metal stuff abstracted into device drivers (HAL/whatever). Current WinCE (i.e. WM) uses a (somewhat compatible with the Win32/64 systems) DirectX model. The other reason for doing this is so hardware vendors (I'm looking at YOU Qualcomm!) don't have to expose their IP to the world in return THEY have to code the drivers. It's more complicated here since the MSM7200 does more than just drive the display. However the graphics driver portion of the drivers will remain constant across implementations of the chip.

So: Can someone who's actually tried this explain the issues that they ran into when attempting to extract the drivers from another device's ROM and run them on the Kaiser? Is there a list somewhere of systems that use the MSM7200 with WinCE? If we make this a community effort then we can eliminate dead ends very quickly.

Additionally, since HTC seems to be a lost cause: Has anyone approached Qualcomm directly? Something along the lines of: "You're taking a black eye with a very influential group of developers, early adopters and enthusiats. All you have to do to fix this is release the WinCE reference binary graphics drivers for the MSM7200 (no open source required!) to the xda developers forum and let them carry it from there. It doesn't cost you anything, doesn't open up any IP that couldn't be reverse engineered from existing products by a competitor anyway, and it earns you acclimation with an influential group and the type of positive publicity money can't buy. It shouldn't hurt your customer HTC either as they aren't responsible for support for non-official firmware anyway. If the carriers are worried about unlocking, that horse has bolted already, and making the graphics driver issue die down would radically decrease the publicity associated with the device and hence the odds of a carrier user discovering the unlock tools. From a licensing perspective, presumably HTC gets an end-user license with each chip anyway, even if they chose (unwisely) to not integrate and distribute the MSM7200's hardware accelerated graphics drivers."

It's called negotiation. Respect the IP, explain the impact in financial and business terms of future sales, decreased sales risk, and positive publicity. (It helps to try not to look or sound like Eric Raymond too... :p )

If anyone from Qualcomm is lurking and reading this, feel free to PM me. I'd be only too happy to explain how one "sells" this sort of thing internally to management. Been there, done that, printed my own damn T-shirts. :D

I don't know SpecG, would someone who does know the organization comment on any applicability here?

James
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] sebastianmc:
friends.. Im so sad with the performance in Divx of kaiser.. I had a hermes, and it is great running high quality divx..

I think the driver solution will come with WM7, I hope!!!

and if we make an overclock? L26 wm6.1 comes with an app to overclock kaiser...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
Even when all dependencies from grabbing all of the KS20 driver files have been satisfied, booting with the KS20 DDI.dll will cause the Kaiser to hang. There's some hardware specifics either cooked in, or something is misunderstood/missed.

Can't expect a driver blob from Qualcomm because rumor has it they themselves don't have any drivers. They were so closed on IP, they wouldn't even let ATI write some drivers for them, and so Qualcomm did a ****e job trying. So rumor has it that Qualcomm is being more humble now, but it's one of those situations where Qualcomm hardware is nothing more than a poison pill.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] satiros:
i like to thank Chainfire for all the effort he has done

and slowly all experts are goin to collect info and miising pieces

and probably after some time we will have a solution

Anyway another thing is overclocking which might helped a bit and since even that isnt here either think we stuck for a while thanks for your time

satiros
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pserbanp:
Just a question : Did somebody of skilled cheafs around here take a look into HTC Shift drivers (as far as I now this device have also Qualcom MSM 7200 and Intel Intel Stealey) ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jgmdean:
The shift does indeed use the same MSM7200, but as it runs Vista on an x86 CPU it's probably not going to be much use other than to demonstrate that someone, somewhere in Qualcomm/HTC *DOES* know how to write drivers for the damn thing. Given the commonality between DirectX on Win32 and WinCE there should be a great deal of commonality at the source level for drivers too.

James
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pserbanp:
I think for Vista Shift use Intel CPu and for SnapVUE (based on WM under interface) use MSM 400 Mhz for batery life
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jgmdean:
Hmmm. Leaving aside the question of Qualcomm's culpability for driver-cide for the moment:

1) What were those dependencies (or at least were there a lot of files or a handful?)

2) Do we know if the KS20 has anything custom in GWES.exe? (unlikely)

3) The driver config is stored at HKLM\Drivers\Display The Kaiser doesn't have much there, no big surprise. It's a matched set with the dll, so what does the KS20 have there?

4) Likewise GWES scribbles in HKLM\System\GDI what's there on the KS20 vs the kaiser?

5) Is there something other than a KS20 that has the MSM7200 and WM6 to compare with?

6) Does anyone have a KS20 or the dumps from one that we can look at?

BTW for anyone curious, a good primer on WinCE's graphics architecture is here:

http://msdn2.microsoft.com/en-us/library/aa447495.aspx

I'm trying not to be an ass about this, but my enquiring mind wants to know!:D

James
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DomZ:
Active
Affichage à cristaux liquides intégré
(Default) (value not set)
BufferMode (0x1)
Dll (ddi.dll)
TapMode (0x1)
Default (value not set)
GPE
(Default) (value not set)
LogicalPixelsX (0x60)
LogicalPixelsY (0x60)
Primary
(Default) (value not set)
CxScreen (0x280)
CyScreen (0x1E0)
DisplayDll (ddi.dll)
PowerDelay (0x3E8)
Secondary
(Default) (value not set)
CxScreen (0x80)
CyScreen (0x80)
DisplayDll (auxddi.dll)
PowerDelay (0x3E8)
(Default) (value not set)
PowerOff (0x0)
Refresh Interval (0xC)

CLEARTYPE
(Default) (value not set)
ClearTypeSettings
(Default) (value not set)
OffOnRotation (0x1)
DisplayCandidates
(Default) (value not set)
Candidate1 (Drivers\Display\Primary)
Candidate2 (Drivers\Display\Secondary)
Drivers
(Default) (value not set)
BacklightDefault (0x2)
BacklightMax (0xF)
BacklightMin (0x0)
BacklightSupport (0x1)
Bpp (0x10)
ContrastSupport (0x0)
DisplayType (VGA)
MainDisplay (ddi.dll)
PaletteSupport (0x0)
Gamma
(Default) (value not set)
Gamma Value (0x5DC)
GLYPHCACHE
(Default) (value not set)
limit (0x8000)
Rotation
(Default) (value not set)
Angle (0x0)
Angle_Backup (0x0)
LandscapeMode (0x0)
SYSFNT
(Default) (value not set)
CS (0x0)
Ht (0x384)
HtInPts (0x1)
It (0x0)
Nm (Tahoma)
Wt (0x190)
V1
FontAlias
(Default) (value not set)
Arial:-14 (Tahoma:-12)
MS Sans Serif:-13 (Tahoma:-9)
version (0x2000C)
(Default) (value not set)
(Default) (value not set)
DisableFarEastWordBreak (0x1)

There is a dump of the KS20 rom in the XDA FTP (upload directory)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NuShrike:
Please read through http://xdaforums.com/showthread.php?t=339745. Then, inquire.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] jgmdean:
Give me a break! :) I skimmed the thread before posting originally, but I'm only up to page 40 or so on my slower, more careful read. :eek:

However, scratching through the various files and postings I've managed to digest so far has given me one impression: the KS20 seems to have hacked with the kernel more than usual, so I'm not confident that their drivers are going to be much use (but I need to PM chainfire about a few things if they're not in the rest of the thread). Here's hoping that one of the non-HTC devices due to release next month per http://www.pdadb.net/index.php?m=pdamaster&posted=1&cpu=a7200 will have a more "vanilla" implementation. I can't help but wonder why LG jumped through those hoops. I've never seen a software team hack a driver from the kernel end unless said driver was seriously brain damaged in some form. Wrappers on wrappers? Urg. :eek:

"If I have seen further it is by standing on ye shoulders of Giants." --Isaac Newton

James
[AT&T Samsung Galaxy S7 Questions & Answers] helemental:
Hello, question is the title. Who do you receive OTAs from if you switch networks?

I'm assuming that you will continue to receive the updates from AT&T, but I'm not too sure since Cricket is its own company and entity entirely. Can anyone answer this? Thanks!
[Sony Xperia ZL] hhjadeja007:
Just to confirm that you did change your downloaded recovery name to boot.img and placed it inside c drive adb folder, right?
[Sony Xperia ZL] Godlydevils:
yes, I renamed to boot.img after googling and learning,

and as I had minimal adb and fastboot installed in

C:\Program Files (x86)\Minimal ADB and Fastboot

I placed in that directory

is that correct?
[Sony Xperia ZL] hhjadeja007:
Yeah that's correct.