yashsingh1/xdaforums huggingface dataset:
[Moto X General] Mister_Magister:
Is my sailfishos for motox Messiah of this forum or what lol
[Moto X General] culiacanazo:
Well, I actually own one that i keep in mint condition without cases or glasses, although lately I've been looking for something to protect it more since I'm turning up the heat on it: you see, in the States, they just recently established the new rules and laws for truckers, and well let's say I'll be doing (and have been) all things work from it off a hotspot, EXCEPT TALK (and never will i be using it for that, so i don't mind handicapping sprint and their draconian handset locking policies, so, what's the chance i start seconding you in the testing before the release, since more likely than not you're focusing inevitably, more on fixing what's broken. Whadya say?
[Moto X General] Mister_Magister:
Exerything is working except video playong/recording and mics but the thing is that there is random reboot that i have to take care of :/
[Moto X General] stefanowall:
What do you think, is it likely that you manage to fix those issues? Unfortunately, microphone and camera bugs in the existing Nougat roms for ghost couldn't be fixed anyway :(
[Moto X General] Mister_Magister:
What do you mean? Camera and microphone is working in los13 https://xdaforums.com/moto-x/development/rom-lineage-os-android-distribution-13-t3529795
[Moto X General] culiacanazo:
He said nougat, 14
[Moto X General] Mister_Magister:
Great news! I fixed random reboots! Thanks to guy who created this kernel https://xdaforums.com/moto-x/development/kernel-3-4-112mmxkernelv1-5-18-05-2016-t3456380 cyanogenmod one has serious problems with itself…
[Moto X General] stefanowall:
Wow:good::laugh:so, everything is working now? Also camera and microphone in calling?
[Moto X General] Mister_Magister:
no camera video recording aswell with video playing is not working. Mic is not working too :/
[Moto X General] Mister_Magister:
https://twitter.com/Mister1Magister/status/968229661552660480

HYPE TRAIN
[Moto X General] stefanowall:
It seems great...unfortunately, you said that many things don't work yet:p
[Moto X General] Mister_Magister:
Not that many only mics, bt and video recording :P

When i was doing my G2 port not even wifi sensors or sim were working so… :P
[Moto X General] stefanowall:
The fact is that I'm still using my ghost as my daily diver;) and without mics... :D
[Moto X General] TriTon2k:
Do you need help, to test the versions that you are doing?
[Moto X General] Mister_Magister:
Thats why i dont want to release it yet :/ i would use it as daily along with my x2 (mic on this one is not working too you have to talk in loudspeaker mode)
[Moto X General] YedanyXD:
Wich version Of LOS are you using as base? (Date)
[Moto X General] Mister_Magister:
Not los but cm13
[Moto X General] YedanyXD:
Is the same error as the moto x2?
[Moto X General] Mister_Magister:
not quite on x2 when you are talking in loudspeaker mode its working. on x1 not
[Moto X General] YedanyXD:
I see, why dont try with LOS, cm13 is to old and i dont remember the problems that it contains
[Moto X General] Mister_Magister:
its not too old cm13 is same fresh as los13 there is no difference. it had no problems
[Moto X General] tom.etc:
any chance of getting support for the cap buttons on a xt1080m? runs ghost firmware no problem, but i have to use a few drivers from the droid ultra/maxx forums to use the caps
[Moto X General] TriTon2k:
Die ?
[Moto X General] Mister_Magister:
why do you want me to die?
[Moto X General] TriTon2k:
Sorry, I do not know how to speak or write in English. I use translator, I would like to know how this is going to be the new rom for GHOST. Thank you and once again I'm sorry.
[Moto X General] zmanjnr:
Any update here on whats going on? thanks
[Moto X General] Mister_Magister:
Not releasing untill i get mics working
[Moto X General] stefanowall:
Do you bet you'll manage?? Or isn't it so probable?
[Moto X General] Mister_Magister:
I mean ill not give up on getting it full working but i dont want to release something that cant be used as a phone :/
[Moto X General] stefanowall:
I absolutely agree with your opinion! Although, more than someone would like to give your rom a try, for amusement or sake of knowledge go on my friend!
[Moto X General] AxlRose77:
When you say camera and audio issues on LOS, do you mean audio coming from videos taken with the phone?

Are there any mic issues during calls?

Are there any other issues with LOS 13 or CM13? I'm thinking of buying an XT1053 and installing either LOS13 or CM13. Are they the same thing? I'd only install if I knew it was pretty much bug-free.

Thanks!
[Moto X General] stefanowall:
M

I've been using Los 13 for nearly one year, with satisfaction, after trying a lot of other custom roms. LOS13 is the evolution of CM13 and it is surely better. No problems at all with microphone in calls...only, when you record a video, audio seems worse than in the original rom. But maybe it's only a wrong impression! Bye
[Moto X General] Belotto:
Hello friend.

Did you get some success?

I got my old Moto X alive so I am thinking about testing sailfish on it.

Enviado de meu SM-G950F usando o Tapatalk
[Moto X General] Ferchurito:
download link?
[Moto X General] kucher5:
so, how it goes?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Hi,

I didn't see any post about using MTTY on Kaiser.

If I did a bad ROM flash with my previous device (HTC Universal), I could always fix this by clearing the FAT table with MTTY.

Believe me... if you flash and it stops ad 85% you will be very happy if you can use this tool!

Reason I started this thread is to help out people who are having such a problem with there Kaiser!

This is the correct procedure to get you out of trouble

;)

1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)

kill two processes rapimgr.exe and wcescomm.exe

2. put your device into the cradle

3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)

4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")

5. type "task 8" to get your device formatted

6. type "task 0" to ask your device reboot

7. take the device out of the cradle, and manually reset it if it does not do that already.

Incase of an emergency it could be very helpfull I think!

Thank you all for providing the input in this thread so I could make this small user manual!

Happy flashing!

Leo :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Well... seems like nobody bricked his device yet!

That's cool.... :):):)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
I've read in many places about people using MTTY on thier Kaiser to get it to boot after a bad flash, but I can't remeber where. And I don't know where they got their info from. :D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
I could attach MTTY here but I'm a bit scared if I do is that people going to blame me if they brick there device!

That's why I'm asking someone has experience with it.

It could be usefull for a lot of people.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
You supply a ROM that people can use to Brick thier devices (if they don't Hard SPL). :D

I suppose that's why they invented Big Red Font's and disclaimers.

If you do decide to post it, I'd get _Alex_ or Mike to add it to the Sticky.

P.S. I have yet to expirence it myself.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Hahaha... yes you are right :D

Ok I will attache MTTY.

Thanks,
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] tyoine:
MTTY (How to fix a bad ROM flash?)

Is this thread can help you ?

http://xdaforums.com/showthread.php?t=370169

I can't find the original post that talk about the procedure to unbrick kayser with

MTTY.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] flushbeer:
Hi !

I used it once.

The "info 2" works as designed ;-)

greetz
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
A clear procedure would be nice so you can unbrick your device easy using MTTY.

Thanks,
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Thanks for confirmation! ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] dwny:
If you have a bad flash....that's no reason to worry.

I haven't had to use MTTY to recover.

In most cases, if there's no issues with the Rom itself...you can pop out the battery and re-flash the same ROM from BootLoader Mode. This will also work if for some reason your computer crashes or loses power & restart during the FLASH.

If the Rom has issues.....the flash will not complete and the device will be stuck in BootLoader Mode. At this point,you must FLASH a FACTORY ROM!!

Pop the battery off 1st, power up the device, device will power up in BootLoader Mode, connect to pc & FLASH your devices FACTORY ROM. This will restore your device back to it's original out the box settings.

The above only works if the device has been put through the Hard SPL or SuperCID process.

I personally have never tried to flash a cooked ROM without unlocking any of my devices. From what I've read what others have experienced...the flash would just fail and they're stuck in BootLoader Mode.

Myself ... I've experienced bad flashes, bad cooked roms that I've cooked, lost power to a pc & had my pc crash during a flash. Listed above is how I've recovered. There is life after Bootloader Mode.

The only time you have to worry is if your device does not power up at all

As a public chef...it's your responsibility to set the parameters of your ROM! Meaning, Radio, HardSPL, program conflicts, etc.

You are not ultimately responsible if someone bricks their phone but if they pushed the issue, you could be hit with some form of liabilty because you failed on providing a simple Disclaimer that sets the expectation.

I hope I've been helpful.....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
That's clear :D

Thank you,

Leo :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
Okay, MTTY is a very useful tool & can help save your butt on many occasions.

A few of those occasions include:

1. Bad flash or installation of HardSPL

2. Bad Flash of a ROM.

There are several other problems that can arise & be mended with the use of MTTY. The most common use is for recovery of any flash process resulting in an RUUBNH error.

For most of these error you want to use MTTY to reboot the low level CE of your device to flush out any bad blocks.

Use of MTTY to recover from these errors is usually simple. The basic outline of how to use MTTY to resolve these errors is as follows:

1. Right click on the quicklaunch activesync icon on the lower left quadrant of your pc. (You can also just open up the A/S program)

2. Select Connection Settings.

3. Uncheck the box labeled "Allow USB Connections" & then Click "OK".

4. Open MTTY & select "USB from the Port options drop down menu.

5. Select RTS/CTS from the Flow Control Settings & click "OK"

6. Pay attention, because for a brief mmoment MTTY wil report whether or not it could establish a port connection to USB. If you are successful, a Command window will open.

7. Hit the "Enter" key on your PC twice. You should then see a command prompt that looks like this "cmd>".

8. At the command prompt (cmd>) you should enter the command "boot".

This will reboot the device & report back about any errors or bad or erased blocks.

9. If your device was just hung, it should be fine after the reboot. If it returns to Boot Loader however, it means there was a problem with bad blocks.

10. If errors were reported & you end up back at the Boot Loader screen, then repeat the "Boot" Comand at the (cmd>) prompt.

It can sometimes take two or three boots to fully recover from RUUNBH errors, so if at first you don't succeed keep trying & remember to keep notes about any errors reported in the MTTY info window.

Other Information: MTTY needs to have full access to the USB port. Some anti-spyware, anti-virus & firewall programs can prevent MTTY from gaining the port access it needs. McCaffee in particular should be temporarily disabled & some firewall programs may also need to be disabled.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pedro_se_rooot:
don't work :( damn :(

this is my pda

RUUNBH

KAIS 130

SPL-1.93.0000

CPLD-8

USB

this is mtty

cmd

Command error !!!

Cmd>boot

Command error !!!

Cmd>
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pedro_se_rooot:
this rom RUU_Kaiser_ATT_WWE_1.51.502.0_Radio_sign_22.45.88.07_1.27.11.31_Internal.exe start, but at 1% kaiser reboot...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pedro_se_rooot:
anyone know how much htc customer care ??? :(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] drtolson:
When I sent mine in to look at a problem with connecting via 3G, I was quoted:

a) I'm responsible for shipping to the centre in Texas, US. (Don't know if there might be one closer to you).

b) There would be a charge of USD$28 for diagnosing the problem and producing an estimate to fix. They would call me with the estimate.

c) If I agreed to the fix, the $28 charge would be waived and I would be charged the estimated amount.

d) If I decided against the repair, I would be charged the $28 fee.

e) They would also charge for shipping the unit back to me, typically, about USD$50 for North America.

In my particular case, however, they have repaired the phone and shipped it back -- apparently at no cost to me, other than getting it down there. I guess they figured it was a 'in warranty' problem.

/drt
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Hi there,

Is your device dead or still responding?

Can you come into bootloader?

Did you follow this step before you connected your device and opened MTTY?

It's very important you do!

1) Kill activesync processes: Ctrl+Shift+Esc in Windows to bring up Task Manager. Kill wcescomm.exe and WCESMgr.exe (by selecting the task on the processes tab, and clicking the End Process button below)

Please tell me?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pedro_se_rooot:
the device iss not dead (i think) but with Mtty work only info and task 8.

i've follow all the step and killed active sync.

:(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pedro_se_rooot:
EUREKAAAAAAA

i've follow this guide

2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)

kill two processes rapimgr.exe and wcescomm.exe

3. put your device into the cradle

4. Run mtty (from downloaded) Choose WCEUSBSH001

5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.

6. type "task 28" to get your device formatted

7. type "task 0" to ask your device reboot

8. take the device out of the cradle, and manually reset it if it does not do that already.

:D:D
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] brickedkaiser:
Needing BIG help

Making long history short, recently bought a kaiser from ebay, it arrived doing many SOD, I`ve lurked through the forums, flashed some WinMo roms, ending up with shifu v20 rom, it worked flawlessly, but then I decided to try android on the phone, because it looked cool, during the format part of the android instalation it marked many bad blocks, and wasn`t able to install it (cyanogen mod, with it`s kernel, during instalation not only Nand died, but also the microSD, was able to reformat it only through another cellphone I have, computer wasnt reading neither formating).

Tried to flash again the shifu rom, and there was no room to finish the rom instalation (stopped a bit after half the instalation), tried a lighter rom, almost finished, but stopped at the almost.

Now I have 2 choices: find the smallest WinMo 6.1 rom, flash it and run android from SD (would love if somebody would show me wich one is the smallest possible), or try to task 2a the phone and then use frankenkaiser (but I tried to connect mtty to it and wasn`t able to make it work)

Boot stops in 3 colour screen, showing RUUNBH on top right of the screen,

KAIS*** (always showed this instead of numbers)

SPL-3.29.hard

CPLD-8

Also shows "rom upgrade error".

(got mtty to work, BLOCK 461 until BLOCK 1743 are bad block, seems like I`ll need task 2a and try the frankenkaiser tactics, would anybody help me? even through pm, phone is probably already almost dead, no problem trying to revive it...)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Hakim Rahman:
if your device is security unlocked, then you can use FrankenKaiser SPL Loader to restore the spl that have been erased by the time you perform a task 2a

here thread FrankenKaiser SPL Loader ~ http://xdaforums.com/showthread.php?t=394584
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] brickedkaiser:
Followed frankenkaiser step by step guide up to step 11 when windows wont recognize the usb... it stays in three color boot, with serial showing on screen, and usb device not recognized in windows, kaisercustomruu.exe isn`t able to find the device.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] cdmallen:
cool

man after 2 weeks of research to and fro i was able to fix my Ruunbh error by using the TS method of using mtty..thank u man you save my agony hahaha..now im back to flashing...

i just followed what the ts instructed...hoooo haaaa...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] TheMadxtremist:
can i get into bootloader through MTTY ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rrmdp:
Hello, my tytnt ii kaiser was briked with the "RUUNBH Bootloader", I "guess" is unbriked now i´ve used the ntty tool. now the kaiser boots normaly buy its not SO installed. If I press the camera button and reset the kaiser I get the bootloader screen (with not RUUNBH), i can see:

KAIS130

SPL.1.56.0000

CPLD-8

So now i guess I would be able to flash a new ROM but if I plug the usb cable the bootloader changes from serial to USB, but the activesync never changes to Green (connected), and when i try to flash the rom I get the % bar but always get the 262 error in the "Phone update ROM utility"

Any ideas?? I dont know what else to do to flash a new rom

Thans a lot for your time

PS: i checked an unchecked the "alow usb connections" into activesync.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] rrmdp:
Hello again, now I've tryed doing with the microSD method but it gets stuck: after 3 color screen it changes to a white screen with "Loading..." message.

Please help!!!

thanxs a lot
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] NEOCAPTORX:
hi there!

This program run on Win7 x64 or x32?

Greetings
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Is your device an original HTC or operator branded.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Pfff..... cool :)

Congratiolations!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
@ GSLEON3 and DWNY

Thank you both for your great input ;)

I have updated first page!

Please correct me if I forgot something?

Regards,

Leo :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
The newer 1.93 SPL is giving some issues. We need to take a look into the Boot Loader so we can find the valid commands. It seems that the "boot" command is no longer valid on some spl versions. Many are back to the Task x x commands.

I'm not sure what tool to use to look into Boot Loader to find the valid commands, but I know it's been done on Hermes I believe.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Maybe MTTY 1.16? Did you try?

If you want I can attach that one too?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
Sure, I'd like to have it (1.6).

But the problem lies in the bootloader itself. Each version can have different commands & for the newer versions the boot command simply isn't there. The only way to figure it out is to disassemble the spl & see what commands lurk in there.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
1.16 added to the first page as well!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] _Alex_:
Added to the wiki, under ROM Upgrading / Troubleshooting.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Thank you _Alex_ ;)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Jussonice:
would this get a device to stop booting to the bootloader after every soft reset? my device only boots to the tri-color screen but the os is still there because if i use this tool with the command set 14 0 it boots into windows mobile, but after a soft reset its back at the bootloader again.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] GSLEON3:
URGENT!!!!

the - cmd>set 14 0 - will not work most of the time. The commands do vary between SPL versions. For most devices however the correct commands are:

cmd>set 16 0

cmd> task 8

You see the set 14 0 command is only for action immediately after a reset, but does NOT clear the RUU flag.

The correct command, set 16 0, is RUU Flag: setting it to 0 if your machine starts in bootloader mode may help to solve this problem.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] kjones2k1:
Excellent thread, subscribing now.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] austinsnyc:
Many of this was covered by POF when the kasier came out but thanks for bringing it back up since I'm many do not know. JUST BE CAREFULL using MTTY you can some times do more damage than good if you don't know what you are doing. Also make sure you have a Shipped ROM from what ever provider you got your kaiser/TilT from :)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Laurentius26:
Thank you my friend.

I updated the first page.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] taurusco:
MTYY now stuck on Smart mobility VS Tri Color after MTYY

So, i tried your software since i think my fone is bricked. I got to where I reformated the fone but it never gave me back another prombt for me to TASK 0. It is now stuck on the HTC Smart Mobility screen. What now? Any help would help
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] johncharles:
Help me

It helps me. I have the tytn blocked and I wanted to use the MTTY. The problem is that it is extinguished. I do not succeed to ignite it. For this I do not see option USB?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] :
The best Tool!!

this ist the most useful an unique recovery tool for MDA Vario III !!!!

perfect! :-)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] bangoskank:
I dont know who you are, ... but I love you.

I was caught in the tri color screen of death. At was at my witts ends. Searching this forum high and low. I the whole time thinking, "I bricked another FRACKEN phone" . This did the trick. Thanks. -- Bango
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Feyroce:
Works perfectly !

I was stucked @ tricolor bootloader screen after an unsuccessful Hard_Spl install !

After following your instructions, the device was successfully rebooted using the "boot" command and not the one you have mentioned.

Thanks for your very useful post ! :):D:)

PS: is there a list of all the MTTY commands available somewhere ?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ufmedrudy:
Yes the did the trick for my day old Tilt...thank you SO much