yashsingh1/xdaforums huggingface dataset:
[ZenFone 2 General] Wilkij:
I, too, get the same error and message when printing from Asus browser.

I'm on version 2.19.40.22.

Interestingly, the material printed even though the spooler crashed.
[ZenFone 2 General] itfsos:
Print spooler crashed also on my galaxy tab pro 8.4..so I'm not sure it is a Zenfone 2 problem..
[ZenFone 2 General] fonetyk:
It is a Zenfone 2 problem. I tested on galaxy s3 (KK), galaxy s4 (Lollipop), LG G2 (KK), LG G3 (Lollipop) and it doesn't crash.
[ZenFone 2 General] itfsos:
Lol so you are saying that my galaxy tab pro was infected by my zenfone 2. Also you can find bug reports for print spooler related to a lot of devices, searching in google.

Btw, testing both again today with also LG g2, zenfone 2 and LG g2 are working, galaxy tab pro still gives me the print spooler error. Sigh.
[ZenFone 2 General] fonetyk:
If printing works on galaxy s3 (KK), galaxy s4 (Lollipop), LG G2 (KK), and LG G3 (Lollipop) then it's not a bug of android that ASUS cannot fix. It even crashes without any printer service installed or any third party apps installed -- after a factory reset and cleared cache.
[ZenFone 2 General] itfsos:
Ok but..following your post, I have a fully working print spooler on Zenfone 2 and LG G2 and a not working one on galaxy tab pro 8.4, so I must say it's Samsung's fault, from your point of view? I said the problem could be a combination of google services and certain devices(like zenfone 2) for this reason.

But no problem, I will search somewhere else a solution for my tablet, let's return in topic with the zenfone 2 problems here.
[ZenFone 2 General] fonetyk:
I believe downgrading Google Cloud Print to version 0.9.10 will fix your samsung tablet, sadly it didn't work for my zenfone 2.

So printing works on your Zenfone, that's interesting. What firmware and model do you have?
[ZenFone 2 General] itfsos:
Thanks I'll try! I have a ZE551ML 32GB 4GB RAM, updated to the last firmware 2.19.40.22(WW). I tried printing a PDF and a chrome webpage actually, I will make other tests.
[ZenFone 2 General] corrsea:
I can confirm that printing works on my Zenfone ZE551ML 64Gb 4Gb ram, CN 2.19.40.20 stock, unrooted.
[T-Mobile LG G4] coolmaster121:
http://xdaforums.com/showpost.php?p=61672737&postcount=622

By autoprime

DON'T OTA

going to post this once... please spread the word into the other G4 subforums and any related posts anywhere.

I'm not sure if this is cause for alarm... but just putting the warning out there... based on viewing the latest USCC and T-Mobile files... these recent OTAs for USA carriers seem to be implementing "antirollback" which means you can never "go back" to a lesser version. To simplify things... fresh out of the box all of your phones were at "0" and now after the OTA they're at "1". Both the TMO and USCC KDZ file's are based on the OTA which is a "1" so there's no concern of flashing an older KDZ by mistake... at least for now. Not sure what will happen with future updates.

Can only confirm this on the TMO H811 and USCC US991... Still waiting on Sprint users to grab the OTA URL or zip name for me so I can inspect that... but I suspect all of the recent OTAs from AT&T, Sprint and Verizon also used the "1" update. The European/Asian/Etc variants still seem to be using the "0" version.. even after the recent updates. [Not every OTA will bump up the "version"]

I can't say what this means as a whole just yet... Maybe nothing at all. But perhaps for those who wish to stay at that fresh "0" for now... try your best to avoid the OTA update. I know the intl phones can disable updates but this option has been removed in USA variants. There are talks of an app that allows you to disable apks on your phone... I haven't used it myself but perhaps for those who want to maybe block the OTA app (LGDMSClient.apk)... worth checking out. This is said app: http://xdaforums.com/andr...bloat-t2998294

apks to attempt to disable:

/system/priv-app/LGDMSClient/LGDMSClient.apk (not in all phones)

/system/priv-apps/LGUpdateCenter/LGUpdateCenter.apk

Again.. I don't really know what any of this means just yet... just reporting what I do know. Spread the word.

And for those who were forced to OTA.. or saying this post has come too late.. everyone knows to never ever OTA.. and the app to disable OTA has been around for a bit now. I'm sorry but..

Cross fingers and hope I'm wrong

Phones with "v1" status confirmed:

H811 10H

US991 10C
[T-Mobile LG G4] funkbuqet:
Seems to work

Thanks for the heads-up. Tried this on my H811 and it seemed to work. It is not able to block the apps, but it can disable them. Hopefully that is enough to stop an OTA.

I did get a message from ES File Explorer that the LG World app had been removed and asked me if I wanted to delete it's folder. So that is a good sign.

After reboot the Update Center in app settings has all options, including force stop, grayed out. So that leads me to believe that it is no longer running. Also, all changes stuck per the debloater program after reboot. :good:

Quick question: How do we tell if the phone has taken an OTA update? This generation has been pretty sneaky about running updates without asking thus far. I am currently on build LMY47D, but I am not sure if that is any different than what originally came on the phone.
[T-Mobile LG G4] coolmaster121:
For T-Mobile the software version of the latest update is H81110h. Find this under software, in About Phone. If you have that you took the FOTA/OTA from T-Mobile.
[T-Mobile LG G4] jnclocker:
That's the one that updated itself by force. H81110H
[T-Mobile LG G4] funkbuqet:
Well damn, looks like I was a bit too late. At least I can avoid the next one.
[T-Mobile LG G4] CalhounAC:
I have the latest software. It didnt ask me just installed it, before I even got phone setup.
[T-Mobile LG G4] dontbeweakvato:
I purchased my g4 the evening before the pre-order for tmobile started .... So may 27th ish early. The girl on The phone said i was The first one to order it. Got it 3days later. When i first powered it on i was careful to not let it update, Which it didn't. Since I've had the phone it has never updated. When i checked software version I'm on h811 10h of lmy47d. I think it came installed with 10h.
[T-Mobile LG G4] Youssarian:
<Deleted>
[T-Mobile LG G4] dontbeweakvato:
But my point was that I received one of the first ones that were commercially available in the United States. I was three first person to get one thru t mo pre-order. Right the second they became available, and it was 10h
[T-Mobile LG G4] dontbeweakvato:
Those greedy bastards just dont want us to experience happiness. (i.e. root, unlock boot). They want us to just be calm in their regime, so they can 'monitor' what we 'do'. Lg......jeez Its just a damn phone, gimme the unlock bin.
[T-Mobile LG G4] DsturbD:
got mine on the 8th, before i walked out of the store it was updating to 10h (didnt know about this till now). i think the sales girl did the update while she had it in her grubby little hands

so if i understand, once you get to 10h you cant go back a version, is that right? didnt this same thing happen with the g2?
[T-Mobile LG G4] Harmtan2:
It auto updates during the setup process unfortunately. I'm sure she didn't care much about it. I'm a rep and I'm pretty sure nobody that is a rep besides me (out of everyone is talked to) knows much about stuff like this. I'm annoyed that we don't have the unlocked bootloader like the g3. :/
[T-Mobile LG G4] TekGadgt:
What app was at this link? http://xdaforums.com/andr...bloat-t2998294 I just ask cause the link is dead and I'm getting my phone soon.
[T-Mobile LG G4] DsturbD:
you mean this link?

http://xdaforums.com/android/software/debloater-remove-carrier-bloat-t2998294

its the debloater tool you can use without root
[T-Mobile LG G4] thenewbigmack:
Just purchased a G4 myself and saw it updating at the counter. Pretty sure it updates during the setup process and we have no choice. Current software version in my hands is H81110h. Is this not the original version? Do we have a KDZ in which is older that we can attempt to use to go backwards? Thanks!
[T-Mobile LG G4] siraltus:
Original was whatever it says on the box label next to "S/W:". Most phones shipped with 10d.
[T-Mobile LG G4] TekGadgt:
Funny. Your link worked, but the one the OP used gives me a 404 error. Weird.
[T-Mobile LG G4] malnash52@gmail.com:
I'm getting a g4 this week most likely does this mean I can no longer root my device
[T-Mobile LG G4] shook187:
This thread is old... You can root with the current update.
[T-Mobile LG G4] malnash52@gmail.com:
Thanks bro just making sure
[T-Mobile LG G4] clockcycle:
You should still disable OTA to be sure it doesn't auto update and render you rootless. I am trying with "Disable Service" app from play store.
[XDA Assist] XDA Visitor:
i am using xolo a500. it ha fully bricked. only blank screen.

if i connect it to windows 7 system .. it is recognised as android bootloader interface with error code 10(device cannot start)

is there anyway to recover it?

pls pls help me

it is xolo a500.

it is bricked by installing swapper app.

after that it shown in windows 7 as qualcomm hs usb qload 9008

after downloading emmc now if i install any driver softer for this it shows with error code 10

i tried all driver software

emmc composite adb

xolo usb driver

qualcomm driver

adb bootloader interface

bt it just shows error code 10 this device cannot start

pls pls help me

or its only a brick cannot revive???
[XDA Assist] StrangerWeather:
Hello, and welcome to XDA Assist! There is not much discussion on your device here on XDA, but I recommend you try and post your question here: Questions and Answers. Hopefully someone will be able to help! You will need to register to post.

Good luck!
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Hi,

After searching a lot in the Google, in this forum and other places, I think its time to write here.

Here it is what I have and want to know/help please : I am gonna to root the device but not able to root it.

Model name : A0001

Cyanogen OS version : 12.0-YNG1TAS213

Android version : 5.0.2

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot devices

49a6b9bb fastboot

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ 0.016s]

finished. total time: 0.016s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot

rebooting...

finished. total time: 0.016s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot devices

49a6b9bb fastboot

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock

...

OKAY [ 0.031s]

finished. total time: 0.031s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot oem device-info

...

(bootloader) Device tampered: true

(bootloader) Device unlocked: true

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ 0.031s]

finished. total time: 0.031s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot

rebooting...

finished. total time: 0.016s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot devices

49a6b9bb fastboot

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.8.1.0-bacon.img

target reported max download size of 1073741824 bytes

sending 'recovery' (12588 KB)...

OKAY [ 0.530s]

writing 'recovery'...

OKAY [ 0.125s]

finished. total time: 0.655s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot format cache

Creating filesystem with parameters:

Size: 536870912

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 2048

Label:

Blocks: 131072

Block groups: 4

Reserved block group size: 31

Created filesystem with 11/32768 inodes and 4206/131072 blocks

target reported max download size of 1073741824 bytes

erasing 'cache'...

OKAY [ 0.047s]

sending 'cache' (10432 KB)...

OKAY [ 0.421s]

writing 'cache'...

OKAY [ 0.125s]

finished. total time: 0.608s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot

rebooting...

finished. total time: 0.000s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>

Questions :

1. Still I don't have TWRP recovery when I Volume Down+Power button, there is Cyanogen recovery menu.

2. Is it not possible to flash supersu.zip in Cyanogen recovery ?

3. If yes, then please give me the download link for it.

4. What else more required after unlock the bootloader to root the device with Cyanogen recovery.

5. Will having TWRP recovery void device warranty ?

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] Heisenberg:
1. The answer to this question lies within my guide thread and also within my FAQ thread

2. No.

3. See above.

4. See above.

5. No. See FAQ thread linked above.

A little searching on your part would have had your problem solved long ago.
[ONE Q&A, Help & Troubleshooting] GirishSharma:
I am really thankful to you for your reply.

I followed exactly your thread to move to root the device.

By looking above steps can you please tell me what next I should download/do to root the device ?

In your steps you have mentioned about TWRP recovery to flash the supersu.zip but I am not able to have TWRP recovery, and I guess this is the place where my rooting procedure is going to stuck.

One more confusion :

I requested to :

2. Is it not possible to flash supersu.zip in Cyanogen recovery ?

You replied

No

So, I am confused this "No".

If it is not possible to flash the supersu.zip then please tell me how do I proceed further.

Kindly help me.

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] GirishSharma:
I rooted my OPO successfully (it seems me like that) :

1.Downloaded twrp-2.8.7.0-bacon.img. Renamed it to twrp.img and placed it platform-tools folder.

fastboot devices

It showed me my OPO's connection.

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery twrp.img

target reported max download size of 1073741824 bytes

sending 'recovery' (10368 KB)...

OKAY [ 0.437s]

writing 'recovery'...

OKAY [ 0.109s]

finished. total time: 0.546s

E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot

pressed enter key and immediately power down button of the device. After few second I got TWRP recovery menu and now its path to root the device by flashing the UPDATE-SuperSU-v2.46-1.zip and bingo... device rooted.

I got this clue from this link :

"Type fastboot reboot to reboot your phone, but hold volume down as soon as your phone buzzes so that it boots into recovery instead of the OS. You have to do this or TWRP may not work."

https://forums.oneplus.net/threads/...lashing-recovery-roms-kernels-rooting.291274/

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Ok, but I don't think you did follow my giude exactly. There's an underlined section at the bottom of the section that deals with the exact problem you were having:

There's also a question in the FAQ thread that addresses this issue:

I gave you links to both of those threads in my first reply to you, so there was no need to go to the OnePlus forums, the answer was right here all along.
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Ok. Thanks again for reply. Earlier I failed to understand your underlined text so, I was bit confused about CM12 and CM12S, since I having CM12 so was bit confused.

At this moment, everything looks fine i.e. unlocked bootloader, installed TWRP, superuser (an app from F-droid open source repository) app, but it is saying "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices. And there are two button Cancel , Recovery Install. When I clickes Recovery install, I gets TWRP menu, and when I installs UPDATE-SuperSU-V2.46-1.zip, it gets installed successfully and when I reboot the device there is only "Cynaogen" logo on the screen, nothing more.

So, can you tell me how do I remove "The Superuser binary (su) must be updated. " message on every reboot the device.

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] Heisenberg:
No you don't have CM12, you have Cyanogen OS 12 (CM12S). You can get the proper SuperSU zip from here. Flash that with TWRP, wipe cache and dalvik cache, reboot.
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Thank you so much for your great help.

I shall open another thread for next/forthcoming question(s) regarding :

1.Will I get OTA updates easily, if I have unchecked "Update recovery with system updates" in developer option. (Particularly in mine case/above setup(s))

2.How it is good to use other ROMs like 12.1 NIghtly.

3.What benefits, features I can enjoy on this OPO rooted device.

4.How do I now restrict the apps to use my mobile data without my permission/wish (This was the main purpose to root the device). I am going to install AFWall app (F-droid repository app) to see how it will work.

5.Anything special which you would like to suggest me to have/have not, do/do not.

6.etc.

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] Heisenberg:
There's no need to open a new thread, we can discuss those questions here.

1. Yes, you should still receive OTA updates even with that setting disabled.

2. It comes down to personal choice. Custom ROMs usually offer more features and optimisations. I use the Exodus ROM, which has nice features and great battery life.

3. There are many benefits to having root access. You can run root apps like Titanium Backup, Greenify, BetterBatteryStats, and many more. You can also access and modify system files, care should be taken with this though because doing the wrong thing can end up with a phone that won't boot.

4. The unsure about this as I don't restrict any apps from using mobile data.

5. Use Titanium Backup to make sure you have backups of your user apps (and their data), the pro version also allows you to backup call logs and sms/mms. You can use Greenify to stop apps from running in the background when you don't want them to, this will save battery life.
[ONE Q&A, Help & Troubleshooting] GirishSharma:
There's no need to open a new thread, we can discuss those questions here.

Yes, we can discuss here, but I think if I opens another thread; then other visitors will also be benefited by your valuable replies.

1. Yes, you should still receive OTA updates even with that setting disabled.

I will see, how I shall get OTA of Exodus as well, because at present I am seeing a long list of OTAs, so I have just downloaded and applied 20150704 version directly.

2. It comes down to personal choice. Custom ROMs usually offer more features and optimisations. I use the Exodus ROM, which has nice features and great battery life.

I have ported Exodus Version 5.1-20150704-NIGHTLY-bacon and now my Android version is 5.1.1_r6. Its really pretty cool to use this first time.

3. There are many benefits to having root access. You can run root apps like Titanium Backup, Greenify, BetterBatteryStats, and many more. You can also access and modify system files, care should be taken with this though because doing the wrong thing can end up with a phone that won't boot.

Fully agree and thanks for your reply.

4. The unsure about this as I don't restrict any apps from using mobile data.

F-droid is also another best open source repository for android. I uses its apps very much, more than Google play store (ad, and pro version)

5. Use Titanium Backup to make sure you have backups of your user apps (and their data), the pro version also allows you to backup call logs and sms/mms. You can use Greenify to stop apps from running in the background when you don't want them to, this will save battery life.

Yes, I have installed Titanium Backup, BetterBatteryStat and Greenify. Now looking into their features and how they works.

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] Heisenberg:
You don't need to create a new thread, just discuss it here. People can find it just as easily here anyway. I don't use the built in OTA updater, I just go to the Exodus download page and get them manually, that way I can check the md5 of the file. Anyway, in the built in updater it shows you the latest update available so it's probably best just to use that one.

XDA Moderator

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Thanks for allowing me to continue to ask the question(s).

Sometime (in fact many time), when I am scrolling something on this device OPO (Same OS and everything same), the device responds like I have clicked on that option, i.e. suppose I am scrolling developer option and there are check/uncheck options only, so it changes its value from earlier one when I am just scrolling the option. Can you please tell me is it a bug in the OS or I have to do some setting in the device ?

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Is it something related to :

cat /sys/class/input/input0/baseline_test

https://jira.cyanogenmod.org/browse/BACON-55

When I run above command (Terminal Emulator), it worked successfully, 0 error(s). All test passed.

I don't know I am addressing correctly in this touch issue.

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] Heisenberg:
It's a touchscreen problem that's plagued some of these devices from the very beginning. I have TWRP and neither have this problem though. The latest update that came supposedly fixed this issue.
[ONE Q&A, Help & Troubleshooting] GirishSharma:
Yes, I too have TWRP and Exodus 5.1-20150704-NIGHTLY-bacon, Android version : android-5.1.1_r6, but I am having the touchscreen problem (may it be a specific this device issue). Can you please tell me above cat baseline_test is something related to this issue or not or Exodus developer community will look into the bug (if any).

Regards

Girish Sharma
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Sorry, that was a typo on my part, it should have read:

I have two and neither have this problem though.

I have no idea about that test. I highly doubt whether the Exodus devs would spend any time on it because it isn't related to Exodus. You were already on the latest stock firmware so you should be fully up to date in terms of firmware but if you want to be fully sure you could do the following:

1. Use TWRP to make a nandroid backup of your current setup.

2. Download the latest CM12.1 nightly.

3. Fully wipe (system, data, cache, dalvik cache).

4. Install the nightly, boot the phone up once (no need to install gapps).

5. Boot back into TWRP and fully wipe again.

6. Restore the nandroid backup you made in the first step.

This will ensure that you're on the latest firmware available.