yashsingh1/xdaforums huggingface dataset:
[Moto X Q&A] jayboyyyy:
np. i had to go refresh on my fastboot stuff when i first got the phone because i hadn't touched phone stuff for over a year.
[8125, K-JAM, P4300, MDA Vario General] witte_nl:
Hi,

Sometimes my backlight does not switch on when I've pushed the on/off button for 1 sec to go out of the stand-by mode. I can see that the telephone is working but only without backlight. I don't know where I can find the settings. I'm using the Vario from T-Mobile.

Can somebady help me with this?

thank you in advance.

Regards Witte
[8125, K-JAM, P4300, MDA Vario General] Karzi:
maybe hard reset or rom update? , cant imagin what will do that unless somthing is hogging all cpu power perhaps
[8125, K-JAM, P4300, MDA Vario General] witte_nl:
A reset will help but I'm not happy to update my ROM. I'm afraid for more problems.
[8125, K-JAM, P4300, MDA Vario General] m@rco:
Did you have the power cable in?

I have the same problem when i'm charging the phone.

When i press the power on button the light stays off.
[8125, K-JAM, P4300, MDA Vario General] Izzard-UK:
Maybe you've got Spb GPRS Monitor installed on it?
[8125, K-JAM, P4300, MDA Vario General] naughty:
Spb GPRS Monitor does this problem on my 9100 too, any software with SPB in the name seems quite buggy.. ;-)
[8125, K-JAM, P4300, MDA Vario General] witte_nl:
OK,

right now I don't have the problem anymore but I'll will monitor it and maybe then I will uninstall the gprs monitor.

Thanks!! :lol:
[8125, K-JAM, P4300, MDA Vario General] ccsnet:
You will.. do a search - I posted this a while back... they know about it.

Terran
[8125, K-JAM, P4300, MDA Vario General] TMBEngineer:
MDA Backlight issue

I ran across a problem with the MDA, where I adjusted the Backlight settings. From there on the Backlight woulf not turn on unless I went to the setting control to adjust it. The fix: Go to backlight settings, set your brightness desired (maybe in the middle). Go to Battery power from the tabs that are currently listed. Make sure you have (Turn on Backlight when a button is pressed or the screen is tapped) Selected. Then press ok.

That should fix it if the issue you are experiencing is similar to mine.
[8125, K-JAM, P4300, MDA Vario General] Imaginati0n:
I have the same problem with my artemis. And i think is from spb plus since the backlight control button from today dont even work on this new version. Or from phone profiles. Everytime i make a soft reset i have to reajust the backlight or when it turns off i have to make another soft for reajusting before it goes out. It's quite boring and i'm trying to find an app to replace spb with the close button and task button ant the today buttons shortcuts if is that the problem. And my artemis rom dont know why dont have the option on the backlight settings to turn on when screen tapped or key pressed.
[Nexus 5 Q&A, Help & Troubleshooting] kepapas:
So I've been swapping sim cards from my g2 to my nexus back and forth no problems. Now I can't connect to network on my nexus I get a bronze lte icon on the status bar . I swapped out the sim to see if the sim is bad works fine on my g2 . Did T-Mobile kick my nexus off my network?
[General Questions and Answers] shnyx:
Im trying to factory reset a fake GS4mini labeled GT-I9190 under battery, which is locked because too many incorrect patterns.

Unable to sign-in to google account, because there is no Data Access point created.

Then I tried to factory reset the phone by accessing Android system recovery, which i could by pressing volume + and power key. But nothing happen when i click to 'wipe data/factory reset', instead it only show the warning sign page.

Appreciate if someone could help me on this.
[General Questions and Answers] parkourkarthik:
Which button did u use to select the option, whether the home button or the power button?

Try the alterate button for selecting (i.e. If u tried to select using power button then try home button or vice versa):)

Hit thanks rather than typing it ;) now Free
[General Questions and Answers] shnyx:
Thanks for your reply.

I have tried lots of combination to access Recovery mode and to select options from menu.

Nothing happen when pressing the power button, but when i press home button the screen shows only the warning sign, again i press the warning sign i can see the menu. I can navigate though the menu by pressing Volume + and -, but when i Select an option (by Home button, Power button does not work) only the warning sing shows.

Is there any other alternative method to reset the phone, like using odin or any other tool.
[General Questions and Answers] parkourkarthik:
If u had enabled debugging option in the settings and have necessary drivers of ur device in the pc, try the following commands using the adb:

'adb reboot bootloader'

'fastboot devices'

(in the above command u'll have ur device in the list if everything is alright)

Atlast

'fastboot -w'

Hit thanks rather than typing it ;) now Free
[General Questions and Answers] shnyx:
not working

Not working.

Im not sure usb debugging options is checked.

May be im using the tool not correctly,screenshot attached.
[Verizon Samsung Galaxy S 4] Crwys:
So I don't know why, I have tried this on two different roms. Flashing the 8/25 ktoonsez kernel makes my back and and menu button not work at all, doesn't light up or vibrate or anything. I followed the instructions exactly but they don't work :(. Currently on the latest hyperdrive rom.
[Moto X Android Development] iTchill:
ooo yeah !! Nice job !!

Sa sens le Rooting icite !!
[Moto X Android Development] xpc21:
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
[Moto X Android Development] rubiksmoose:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
[Moto X Android Development] penpen72:
How do I do steps 9-12?
[Moto X Android Development] phositadc:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?

Sent from my XT1053
[Moto X Android Development] Ctrl-Freak:
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.

Hopefully someone else can 'give it a whirl' and report their findings.

These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.

The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
[Moto X Android Development] penpen72:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.

---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------

Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
[Moto X Android Development] Ctrl-Freak:
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.

You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
[Moto X Android Development] rubiksmoose:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
[Moto X Android Development] Ctrl-Freak:
Everything is working fine. Take a look here for other people's observations:http://xdaforums.com/showthread.php?t=2517577

There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.

It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.

[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
[Moto X Android Development] n1ckr0th:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
[Moto X Android Development] Ctrl-Freak:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
[Moto X Android Development] n1ckr0th:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
[Moto X Android Development] Ctrl-Freak:
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.

(The stock bootloader is still enforcing RO mode for a normal boot.)
[Moto X Android Development] HeroSon:
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
[Moto X Android Development] j2cool2012:
So can I clarify a few things for myself?

You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
[Moto X Android Development] Ctrl-Freak:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.

Nothing.

I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...

Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.

The only other thing I did was describe a set of instructions that worked for me.
[Moto X Android Development] j2cool2012:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
[Moto X Android Development] dudumaroja:
the Att bloatware and carrier name in notification bar scared me away :(
[Moto X Android Development] j2cool2012:
It booted for you on VZ?
[Moto X Android Development] ijeff:
Would I be able to use this on the Rogers version of the Moto X?
[Moto X Android Development] strictlyphat:
Why won't this work on a ROM slot ?
[Moto X Android Development] Ctrl-Freak:
I tried 3 different ways to get this to work in a rom slot. Look for my prior posts on the matter.
[Moto X Android Development] Ctrl-Freak:
Developments:

1) After you install 4.4 in the stock-slot using the aforementioned instructions, you can re-install safestrap, and it seems to work fine!

2) I altered the ota intended for the att 4.4 leak, and made it a safe flashable zip. (This ota enables the ART runtime, etc.) I applied the patch to my system, and it seems to work fine. I am probably not going to try and patch the modem, but the 4.2.2 modem (.54 version) seems to work fine.

I will update the OP with the patch after I test it for a while. I hope the ota fixes my [apparent] battery drain issue.

[edit]Safestrap has a new version. Hopefully a tester can see if my rom now works in a rom slot...[/edit]
[Moto X Android Development] Ctrl-Freak:
I updated the OP with the patch to upgrade from 139.44.44.ghost.att to 140.44.3. It only modifies /system and should be safe. You must already have 139.44.44 installed, or it will not do anything.

It is my observation that SS:TWRP does not flash boot, so once again boot.img is included in the zip to be flashed manually.

I was unable to get the patched modem binaries, and I am still running the modem from the att .54 update.
[Moto X Android Development] skulldreamz:
i would love to and i have alot of time to test thouroughly. i actually flashed last night and wiped system data and cache and deleted rom slot 1 and its running really nice for the little tiome i have it installed. im about to flash the new patch now. hope to hear from you so we can make a killer rom!!!!!! -skulldreamz
[Moto X Android Development] Ctrl-Freak:
The settings->security force close was being caused by the old modem. I patched the modem, and will post an update to my patch script to patch the modem along with /system.
[Moto X Android Development] HeroSon:
I just updated the patch and everything feel much smoother. It seem i'm getting better battery compare to 139.44.44 cause my android os is not high but still testing. Just to let you know I did this with new safestrap 3.65 and everything is working, I also skip step 12 don't erase useradata and safestrap data was intact no need to reinstall, even all my apps and data still intact and working. Now waiting to get the patched for the modem. Thanks
[Moto X Android Development] Ctrl-Freak:
Thanks for the help! I updated the OP.

I am trying to figure out how to deliver the modem patch. I am hoping to build a new non-HLOS.bin, but I may have to deliver another patch and alter the existing one.
[Moto X Android Development] Ctrl-Freak:
I updated the OP with the modem patch. This patches the 139.44.44 modem up to 140.44.3.

The 139.44.44 modem must be fastboot flashed manually before running the patch. (I could do this automatically, but I am afraid that safestrap:TWRP has some limitations. For instance, I had trouble flashing boot.img. Maybe someone could correspond with Hashcode regarding what is safe to do within Safestrap.)

As far as I know, the old "fsg.mbn" does not cause any problems, but I would like a better understanding of it's purpose. It appears to be related to the modem, but I am not sure if you can downgrade after you flash this file. If anyone knows for sure, they can answer in this thread or here: http://xdaforums.com/showthread.php?t=2529569
[Moto X Android Development] mj0528:
We'll give this a go today!

Thanks Freak!
[Moto X Android Development] mj0528:
is there anyway to get back to stock without the kitkat FXZ once we do this?
[Moto X Android Development] Ctrl-Freak:
Yes. The only things these instructions/roms/patches modify are /system, the kernel (boot.img) and the modem (NON-HLOS.bin).

(That was the entire point of my work, otherwise you could just do the "flashall" from the leak and take the ota.) [edit]And you can get root through this method.[/edit]
[Moto X Android Development] mj0528:
great! Thanks! so if things go south, we can simply use RSD and flash back to the latest 4.2.2?
[Moto X Android Development] Ctrl-Freak:
Yes. Or you could fastboot flash system.img, boot.img and NON-HLOS.bin (which is the way I do it.)
[Moto X Android Development] mj0528:
you are a gentleman and a scholar!

---------- Post added at 09:32 PM ---------- Previous post was at 08:51 PM ----------

the first boot seems rocky so far but now it's upgrading the apps so we may have a winner. crossing fingers!

---------- Post added at 09:51 PM ---------- Previous post was at 09:32 PM ----------

am i supposed to be in bootloader mode when i attempt to flash the modem?

Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
[Moto X Android Development] Ctrl-Freak:
Yes. Use fastboot just like the kernel (boot.img).
[Moto X Android Development] mj0528:
giving it the last reboot now! Thanks man!

---------- Post added at 10:18 PM ---------- Previous post was at 09:59 PM ----------

so other than the bootloader not being updated and having root on kitkat already! what are the differences from the stock kitkat rom?

Thanks again! It's working great so far!
[Moto X Android Development] Ctrl-Freak:
There shouldn't be any perceivable difference.

There are, however, several potential images that we did not flash. The bootloader is one of them. One skipped image, in which I'm interested, is "fsb.mbn". The OTA replaced "fsb.mbn", but not only do I not know if it is safe, I don't even know the purpose of the file.
[Moto X Android Development] mj0528:
i just switched to ART and it didn't like that all. It won't boot

do I need to start from scratch to get back?

i fastboot erase userdata and I'm back but I guess no ART is a limitation to this release?
[Moto X Android Development] Ctrl-Freak:
Strange. (I made that change also, but didn't have any problems, and I have since gone back to dalvik.)

I believe the dalvik / art data is stored in cache, so the first thing I would try in bootloader mode is this command, then reboot: fastboot erase cache

(This should not hurt anything.)

Can you still boot into recovery?

- Yes:

If you made a backup of the stock slot (since doing all of this) you can try restoring.

If you didn't make a backup, you can flash the full rom, then the patch. (I doubt you need to change/downgrade the kernel or the modem.)

- No or the above didn't work:

If you don't have ANY data you cannot replace you might try this (WARNING YOU WILL LOOSE ALL DATA PLUS EVERYTHING ON THE SDCARD): fastboot erase userdata

If that doesn't work or you want to try and recover your data, you very well might need to start over from stock 4.2.2. (I'm not sure that you will be able to recover any data, because the /data information has potentially been changed to match 4.4.)
​

[edit] I wonder if the difference between your installation and mine is that you kept your /data. If anyone can confirm or deny this theory it would be helpful. [/edit]
[Moto X Android Development] fairct:
The runtime to use is in build.prop
[Moto X Android Development] Ctrl-Freak:
Glad you got it going again. ART worked for me, so I am wondering what was the difference.

Questions:

Did you skip doing "fastboot erase userdata" during the initial install?

Did you get a chance to try 'fastboot erase cache' ?

Have you/can you tried to reproduce the problem since you wiped userdata?

Thanks.
[Moto X Android Development] mj0528:
I did skip it on the initial run through. I have erased cache and user data but haven't tried to reproduce it yet as I'm going to get things built up and backed up before trying again. Thanks for your amazing support on this!!
[Moto X Android Development] freak4dell:
Thanks for posting the update. Seems to be working fine so far. SS doesn't seem to like KK, so I couldn't fully flash the modem patch (I did fastboot flash the modem, and it seems to be working okay, so not sure if I'll have problems).

One problem, though. Is anybody getting a weird soft reboot when trying to uninstall an app? I also got it when trying to restore stuff with Helium. I can't even uninstall through ADB.
[Moto X Android Development] Ctrl-Freak:
Was there an error when SS failed on the modem patch? (It does do sanity checks before it patches...)

Did you patch the rom to 140.44.3? Do you get a force close in settings->security?

I have not had a single reboot of which I am aware. I have installed and uninstalled several apps. I am guessing you mean an downloaded app (vs an app in the /system partition)?

Thanks.
[Moto X Android Development] freak4dell:
Yeah, I think the error was something along the lines of "E: couldn't open zip file" or something. I forget the exact wording.

Actually, I think my problems may lie in the fact that I didn't flash that modem patch. Settings>Security force closes for me, too. So, I'll start over and make sure to flash that before I boot up. It took me two tries to get this far, because the first time I just flashed the leak, then had the same SS problem when I went back to flash the OTA patch. The second time, I flashed the leak, then the OTA patch, and the boot.img, and only then did a normal boot. For whatever reason, it seems like as soon as the system boots into KK, SS just decides to stop working. Maybe it has to do with the 3.65 build of SS, or maybe it's just some KK compatibility thing that Hashcode hasn't fixed yet.

I'm waiting for the phone to charge back up again so I can redo the process. I'll update later when it's done.
[Moto X Android Development] mj0528:
No issues like that here
[Moto X Android Development] freak4dell:
Alright, everything seems to be working now.

For anybody that may run into the same troubles I did, here's the process I used. I was already on the leak because I had flashed system and boot when the leak first came out. So, the first thing I did was RSD back to the very first build. After that, it was just these steps:

1. Root and install SS.

2. Boot to SS recovery.

3. Flash the leak.

4. Flash SU.

5. Flash the OTA patch.

6. Use the SS reboot options to reboot to bootloader.

7. Fastboot flash the newest boot.img and the modem (NON-HLOS.bin).

8. Fastboot reboot, and select recovery when the SS prompt comes up.

9. Flash the modem patch.

10. Wipe cache and reboot to system.
[Moto X Android Development] skulldreamz:
Great job bro! Just installed patch and everything is working great.

I did notice yesterday when I switched to art that it took a while for apps to optimize upon reboot of erasing dalvik cache.

And I was experiencing soft reboots upon uninstalling apps as well but not since applied the updated modem.

Again awesome job!!
[Moto X Android Development] HeroSon:
I also was experiencing soft reboots upon uninstalling apps but after I reinstall the leak fallowing the steps above the problem went away and everything is working now. Thanks
[Moto X Android Development] mj0528:
so when you choose to go to ART and the phone reboots and goes to a black screen. How long should I wait before punting and RSD or fastboot again?

i waited about 10 min of seening the black screen that seemed like nothing was happening and am restoring now. I wonder why I can change from dalvik to ART.
[Moto X Android Development] HeroSon:
only took me 2 min then it boot to where it say Android is upgrading. Optimizing app. If your still in black screen for more then 5 min then you should reinstall the leak following freak4dell steps, it works for me.
[Moto X Android Development] mj0528:
ok, thanks

so a solid black screen is normal for at least a couple of min? maybe i need to wait longer
[Moto X Android Development] Ctrl-Freak:
Mine went through the normal boot, and after the animation, it started the "Android is upgrading app 1 of xxx". It was never black for any significant amount of time. Have you tired it again after you erased userdata?

For those experiencing 'soft reboots' are you uninstalling system apps, or apps you downloaded?

I now have an single rom that represents the leak + the ota. I hope to have it tested today.

I'm going to add 'erase cache' to the OP. Thanks freak4dell. [edit] Already had it... [/edit]
[Moto X Android Development] mj0528:
yea, i did erased userdata yesterday to get my phone to boot yesterday. I restored everything afterwards and here I am trying again. I guess I should start from scratch again to try it. Is ART worth it?
[Moto X Android Development] HeroSon:
not really right now some apps not compatible and some apps does load faster like photoshop touch it load faster by 3 sec. I went back to dalvik until more apps start using ART.
[Moto X Android Development] mj0528:
gotcha, i guess by the time it's worth it, we'll have the full blown kit kat with root available.
[Moto X Android Development] drksilenc:
lost my modem somehow i am doing a complete reflash.