yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] DerMoo:
You have to rate the game

Dont worry its not your audiochip. The game ask you something like: Rate the Game on Google Play.

If you tap never, the sound will disappear.

I delete the App and install it new, rate the game and now everything is fine.

I hope this will help you,too.

Sorry my English isn't very good... ;)
[Nexus 4 Q&A, Help & Troubleshooting] Yukicore:
What did you mean by sound? I have sound, except for the engine/motor sound in gameplay. Does that sound work to you?
[Nexus 4 Q&A, Help & Troubleshooting] DerMoo:
Yes. I had the same Problem. Only the Engine sound disappear (fade out after 1 second). The BGM and other sounds still working. Install new and rate the game and the everything fine.
[Nexus 4 Q&A, Help & Troubleshooting] Yukicore:
Didn't work for me, I deleted data for the game (only way to start again avoiding automatic backup), it asked me to rate the game, I pressed yes and it sent me to the Google play store. I had already rated the game manually, because of the bug so I just adjusted the rating, went back to the game and still the same problem...
[Android Q&A, Help & Troubleshooting] TioCareca:
Rooting this phone is as simple as using a one click solution.

Download Cydia Impactor for Mac OS X, Windows, Linux (32-bit), or Linux (64-bit)!

The program only installs su in system xbin, then manually we need to install superuser apk and busybox

Official site

http://www.cydiaimpactor.com/

Test rom

Soon

_________OLD MESSAGE_________

Hi,

Does anybody already successfully rooted ZTE KIS PRO?

I've tried z4root, bin4ry, shortfuse, adb pull, chainDD method, framaroot, motochopper, universalandroot, oneclickroot, abuse...

Nothing work's for me... :crying:

ZTE KIS PRO AKA OPTIMOS Zali/Orange Zali

Android 4.1.1 Jelly Bean Kernel 3.4.0 :D

Internal memory :4 GB Free:2 GB :D

RAM memory :512 MB :silly:

Processor 1,00 GHz Qualcomm MSM7225A :rolleyes:

TFT 256k colors 320 x 480 px (3.50")

Camera 3.0 MP

Can't stay stuck in bootloader to use fastboot only FTM mode...

ADB and ADB SHELL working but can't use ADB root...
[Android Q&A, Help & Troubleshooting] TioCareca:
This is the PT oficial rom, is there a way to rooted before instal it?

http://www.ztedevices.com/support/s...aed-4eba-b717-82c7048ea7a0.html?type=software
[Android Q&A, Help & Troubleshooting] TioCareca:
can we edit the rom, adding su binaries and busybox to system/xbin, and superuser apk to system/app...

then edit updater script adding:

run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");

set_perm(0, 0, 06755, "/system/xbin/su");

set_perm(0, 0, 0644, "/system/app/superuser.apk");

set_perm(0, 0, 04755, "/system/xbin/busybox");

symlink("/system/xbin/su", "/system/bin/su");

then flash via stock recovery?
[Android Q&A, Help & Troubleshooting] TioCareca:
The above is not working, sais instalation aborted, by adb the system is read only and it works with ext4...

Any ideas? or news about rooting methods i can try?
[Android Q&A, Help & Troubleshooting] TioCareca:
Recovery mode

Volume up + Power

FTM

Volume down + Power

DFU (diagnostics interface)

Volume up + Volume down + Power :confused:
[Android Q&A, Help & Troubleshooting] Jan Shvets:
no luck too

I have tried all of these things and non of them works. The only success was to unlock it from mobile operator (in service center with help of SigmaKey (only with Sigma dongle)). Any suggestions for how it could be rooted?
[Android Q&A, Help & Troubleshooting] TioCareca:
I've tried many things, my idea is that we have to force the software to upgrade, but i've downloaded the soft from zte, pre-rooted the rom but the stock recovery doesent install it, maybe if we have cwm... Dont know if the bootloader is locked... And for one click solutions we need unsecure adbd...

Tested the phone to vulnerabilities, no luck...
[Android Q&A, Help & Troubleshooting] TioCareca:
http://rootandroid.com can't root this, even paying no root for us...
[Android Q&A, Help & Troubleshooting] Jan Shvets:
Yes, the bootloader is locked. I've tried to install CWM but with no success. I think that Sigma is the only solution in this case, but I'll keep trying. Just for now none of known issues worked for me.
[Android Q&A, Help & Troubleshooting] TioCareca:
Did you build CWM? Or use from another device?

Have you ever worked with a gold card? Don't know if it will work in this case, but it's a try... I don't really know how to build one but will search...

Its the first phone i know from zte that has locked bootloader, is there another? I'll try to contact zte to know more about it...

How do you use sigma to root?
[Android Q&A, Help & Troubleshooting] TioCareca:
http://xdaforums.com/show....php?t=1248095 - goldcard creator...

I’ve tried manual temp root, i get a message saying "adbd cannot run as root in production builds"

Jan Shvets can you unlock bootloader with sigma?

Slovakia has more files in support section:

http://www.ztedevices.com/support/smart_phone/cf298a37-3a36-4cbb-a021-34dad442a0e3.html

Support for Spain:

http://www.ztedevices.com/support/smart_phone/30d59198-a7fe-491c-86b1-bed35e3a03d3.html

Brasil and Venesuela not supported by ZTE...

I will keep an eye in here too:

http://www.htcmania.com/showthread.php?t=629008
[Android Q&A, Help & Troubleshooting] TioCareca:
Finnaly root...

Rooted, see first post...
[Android Q&A, Help & Troubleshooting] xredxda:
I can't obtain root using this metod - cydia impactor.

Using Framaroot 1.6.1 my Orange Zali is rooted now.
[Android Q&A, Help & Troubleshooting] TioCareca:
Strange, i've tried framaroot and in mine have not worked, what his your OS version?

Mine is 4.1.1 with the 3.4.0 kernel...

Maybe they patched the bug that made cydia work...

One more thing, maybe cydia have rooted your device did you instaled su from the playstore after?, framaroot install su.apk and cydia needed that instaled manualy, if you try framaroot after cydia of course it will work, the device was already rooted but you not notice that because of the missing su.apk... Just my 2 cents...
[Android Q&A, Help & Troubleshooting] TioCareca:
This phone as equal specs of the blade3, the only thing difrent i notice is the sceen, maybe cwm from blade3 work in our phone?

This could break the phone and then we have to reinstall recovery via terminal emulator with the command dd from within the phone (not tested because i am again without a proper pc)...
[Android Q&A, Help & Troubleshooting] xredxda:
Yes! After installing manually 'su' it did not work. I tried this with both Cydia - 9.12 and 9.13.

... the same OS 4.1.1 with the 4.3.0 kernel.
[Android Q&A, Help & Troubleshooting] TioCareca:
That's strange, but you are not the first sayng that, so something as changed, but dont know what...
[Android Q&A, Help & Troubleshooting] ysmayl:
Have this phone to ...ZTE Kis Pro (Orange Zali). Succes root the phone with cydia , but i try to wirte anounther firmware and it give me a error

: "assert failed: getoroop("ro.product.name") == "P752D20_ORANGE". If any ideea how to write anounther version, i download the android version from zte site.
[Android Q&A, Help & Troubleshooting] TioCareca:
Got the same here, cant flash firmware from zte... :eek:

Say one thing? is the firmware from zte difrent from yours? another version?

If it is the same the error can be from stock recovery (no custom recovery yet :crying:)
[Android Q&A, Help & Troubleshooting] xredxda:
You tried this? ( http://www.ztedevices.com/support/s...673-4449-b76b-ce781bb53ded.html?type=software )

To me it worked.
[Android Q&A, Help & Troubleshooting] piopio120:
when the rom will be made???
[Android Q&A, Help & Troubleshooting] Theopsis:
I am interested to find this out too... Any news about that Test ROM?
[Android Q&A, Help & Troubleshooting] aleku83:
get rid of orange garbage

For those who want to root is a very simple method, dowload framaroot 1.9.1(use the second exploit "gandalf") on your phone or sd card memory then install it.After reboot the phone is rooted,also framaroot has the option to unroot.

After that you instal link2sd(i use this app,maybe there are other apps who do the same thing) and start unninstal the orange apps(there are lot).
[Android Q&A, Help & Troubleshooting] TioCareca:
I do not own this phone anymore, so my work on it is discontinued...
[Android Q&A, Help & Troubleshooting] maharba1809:
ZTE kis Q version

Anyone knows if ZTE Kis Q can be rooted. I have tried many methods with no success. I need help
[Android Q&A, Help & Troubleshooting] ToNe111:
How to root Orange zali(zte kiss pro)

If you can't root the phone with cidya impactor you can use root genius because for me cidya didn't worked but root genius worked......it will install you an app kinguser but it's the same as SuperSu!!!
[Android Q&A, Help & Troubleshooting] ToNe111:
how to root zte kiss pro aka orange zali

now I'm stuck at unlocking bootloader!!
[Android Q&A, Help & Troubleshooting] brokenmotog60:
i know i am kinda late (11 years lol) but kingo root did the job for me
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] celkin:
Ok... I have been reading way to much today, to the point i did something rather noobish.

Was in the dev section TWRP thread specifically looking to downgrade fron 2.6 to 2.5, saw the last post where someone posted a dropbox link of 2.5. Thought "how convenient" and flashed. But the zip was for another model number, now i cant get into my recovery.

Odin flash of the stock image is always an option. But one that I would prefer to avoid it if at all possible. I was hoping that someone else out there was well... as stupid as I am, and maybe had some advice?

Is there any possibility that goo manager will simply over right the wrong recovery image with the proper?

Or is it by any chance possible to simply flash the TWRP ZIP with Odin?

Any thoughts would be greatly appreciated, and I already know that I'm a burnout lol.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
Just flash the 2.5 twrp zip in twrp. It'll down grade
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] mg2195:
Goo should over write it, and just to make sure ..you have the i337m -Non att variant. Youll have to see if anybody has a non loki version if twrp 2.5
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] celkin:
That's the problem... Cant get into recovery anymore.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] celkin:
Yeah, was hoping someone would say that. My thoughts were the same. But after that last bout of stupidity, i guess I wanted to hear it from someone else...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Tylorw1:
Can you get goomanager to install it?

Tylor
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] MrSub:
Can you use odin to flash the correct twrp with a .tar file?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] celkin:
Yeah, just finished a backup/restore after goo re installed 2.6.

Everything seems fine. Just with so many "brick" threads on here wanted to be careful.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Tylorw1:
The bricks revolve mostly around the newest update that locks the boot loader on the at&t s4. On the m non at&ti believe you just need a non Loki kernel but I am not positive.

Tylor
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Ol' Dirty Bastard:
If it's I337m or M919, Loki or not, it doesn't matter...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] celkin:
My phone is bootloader unlocked from the start from what i understand its the Canadian Rogers varient.

Im just now after reading countless threads wraping my head round this device. Its way more complex of a situation then the note 2 (previous phone).

My understanding is that we stay away from anything loki'd.

2 days in and im still not comfortable flashing any rom 4.2 or 4.3 lol. Another day or two of reading :-\
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] fukenbiker:
Ponder that, a canuck is less subject to tyranny? Your bootloader isn't locked? NICE! AT&T has degenerated from American Telephone and Telegraph into a globalized melting pot of greed and required upgrade costs and technical support that uses broken English spoken by people in India. You Canadians luck out this time!

I jumped in with motochopper to get root back in May and had the AT&T Software update service frozen with Titanium Backup back in June, I was so lucky to be "on top of it" by reading this forum. I used "Casual" to obtain TWRP 2.5.0.2 a custom recovery. I've never seen it so easy. After burning an image 3.56 GB of my stock firmware, I have since deleted it from my handset and replaced it with a nandroid of my daily driver here because GoldenEye is flawless. I saved a copy of the stock firmware on my desktop computer just in case, but I doubt I'll ever flash it and all of it's horrendous bloatware.

So I'm a happy camper, that only suffers the jone'sen for a fix as a "flash junkie". I will try CyanogenMod on this S4 after they iron the kinks out.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] bo8:
Looks like you're ok now?

FYI for anyone else in similar situation, ROM Toolbox Pro can download and install recoveries as well. It can access TWRP as well as CWM recoveries. A bonus for TWRP, it detects 2.5.0.2 as latest (avoid the occasional Teamwin splash screen hang with 2.6)!

I used this method to downgrade from 2.6 to 2.5.0.2. :good:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AxAtAx:
Word of warning, why upgrade from a working twrp 2.5.0.2, when it works flawless? Sometimes upgrading to a newer, is not always the best...look at the XDA app....yikes...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] celkin:
All good thanks :)

Will Rom toolbox screw anything up if i install TWRP 2.5 over goo's install of 2.6?

I dont trust 2.6... Too many glitches for me and not having faith in your recovery is a scary thing...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] bo8:
You're very welcome! I initially had TWRP 2.6 installed via rooting procedure (one-click method) and recently had ROM Toolbox flash TWRP 2.5.0.2 over it. No probs. Did full nandroid after it.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] vinukind:
Wrong twrp flashed

Dear friend wrong twrp for my device I'm not able to go to the boot menu, how can i get rid of this, help me please. I've my stack memory and kernel already backup in my device memory.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] audit13:
The phone is an att i337? If it is, I assume the bootloader is unlocked since you were able like to flash a custom recovery.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] gujjar0829:
i have no twrp AND I am stuck in boot loop...............................what will I do
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] audit13:
Boot into download mode and confirm the phone's model number. Then flash a stock ROM from sammobile.com with Odin to get the phone back to stock.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] danalog:
I posted this over in LG V20 forum. This can be deleted. Thanks

I need to Frankenstein's monster this thread back to life as I am in need of big help! Like the OP, I made a critical error after days of trying to navigate the minefields of rooting my device. I have a LG V20 h910 and it is no one-click wonder root. It made me work for it and I finally got it. I loaded LineageOS 14.1 and all was good until the USB OTG cable from my PS4 controller did not register anymore. Damn, that was a let down, and probably led to my careless move of needing to downgrade my TWRP, saw the version I needed, forgot these are device specific, and now I'm stuck in a hard place.

Perhaps the fix is easy, but I have not found the answer after many, many searches...

I had TWRP 3.2.1-2 and needed to downgrade to 3.2.1-0 to try SuperRom (hoping it would have OTG ability). I hastily grabbed the first TWRP 3.2.1-0, threw it on the SD card, wiped everything except internal storage, and flashed the img, and did a reboot. Road block went up.

I tried getting back into recovery, did the PWR and DOWN pressing combo and got the Factory Reset screen, but after clicking "Yes" to both, instead of getting the TWRP screen, I got this error screen (attached).

I tried another idea - hooked it up USB to my PC and tried accessing it via adb/fastboot. I tried multiple drivers for my device, but no adb and no fastboot devices were ever found. The only thing that almost worked was booting phone into FASTBOOT mode by holding DOWN btn and plugging in a USB cable attached to PC. Once in FASTBOOT mode, My PC at least saw the ID for fastboot device. I tried to flash TWRP via fastboot, and it looked like it would happen, but in the end there was no phone screen response to my attempt, and the cmd window on my PC would get stuck and just hang.

Can someone please advise me on how I can fix this problem?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jd1639:
This thread is for a Samsung device. Adb and fastboot don't work on Samsung devices. Odin is used for flashing so you probably won't get much help here. I'm not familiar with your device, but you'll probably have to flash the stock firmware and start over. You've borked your recovery trying to flash the wrong twrp. If you can get a stock recovery image for your device you may be able to flash that with fastboot. It should be from the same firmware version you're currently on.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] danalog:
Thanks JD, I will look into that.
[Samsung Galaxy Nexus] MaceBewley:
10.2 Builds (Personal) for Toro has Unknown listed under baseband, MEID, IMEI, ect...

Build for Grouper are fine, and this build for Toro seems to be good with the exception of this problem!

Thoughts and help on how to remedy this would be greatly appreciated!
[Samsung Galaxy Nexus] faisalrizal79:
anyone cannot solve this problem ??
[T-Mobile HTC One (M7)] xgambit823x:
im currently on android revolution rom 12.2 upgraded from version 10 an my option to charge to tmobile on google play has disapered. any sugestions
[T-Mobile HTC One (M7)] ingenious247:
Go to Settings > apps

Clear data for Google Play Store and Google Framework Services.

Then exit settings, open the Play Store, BAM

fixed
[T-Mobile HTC One (M7)] trjlive:
That worked!

I had just enabled the "bill to T-mobile" option when the next day it had disappeared. Thank you for your suggestion, that fixed it!
[T-Mobile HTC One (M7)] xgambit823x:
did this now google has connection error
[T-Mobile HTC One (M7)] trjlive:
I forgot to add that after I cleared the data for the Play Store and Framework Services, I immediately did a full reboot (not soft) and then opened the Play Store app again. Then it was working for me.
[T-Mobile HTC One (M7)] Garmig:
Make sure the build.prop has these lines:

ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase.yt=android-htc
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.gmm=android-htc
ro.com.google.clientidbase.ms=android-hms-tmobile-us

If not add them to the end of the build.prop
[T-Mobile HTC One (M7)] trjlive:
I lost my "Bill to T-Mobile" option again after updating to ARHD 13.3 and the initial fix of clearing Play Store cache and prefs didn't seem to bring it back, but making your suggested changes to the build.prop file worked perfectly. Thank you!
[T-Mobile HTC One (M7)] stivelio:
Can you please tell this noob where to find this file to modify it?
[T-Mobile HTC One (M7)] trjlive:
The build.prop file is located in the /system/ directory. But you can't see that directory unless you're rooted, and you have to use a root file browser app. I use ROM Toolbox Pro (from the Play Store), which has a really easy-to-use "build.prop Editor" (with auto backup) under the Performance tab. Or you could just use any root file browser to navigate to /system/ and edit build.prop. Always make a backup of the file before editing it. Even minor mistakes can prevent your device from properly booting and you can then use recovery file manager to replace mucked-up build.prop with your backed-up copy.

Here is another good thread about editing build.prop. Worth a read. http://xdaforums.com/showthread.php?t=1948558

Good luck, and let me know if you have any other questions about this.
[Verizon Samsung Galaxy S 4] Captain Crypto:
Greetings. My S4 Developer Edition will arrive on Tuesday. When I purchased it online I think I read that once software is installed (I'm assuming recovery/ROM/rooting it, etc.), the warranty is void. Did I read that right? If that's the case and some hardware component dies, that's gonna be one expensive fix.

Yeah, I should have read the whole thing before clicking but all I could think about is ditching this crappy Bionic. So I guess in the end it really doesn't matter, I'm rooting and ROM'ing it no matter what.

EDIT: It appears I will need a new warranty. I'm subscribed to a thread that mentions something about this.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I got a warranty for $99 for 2 years through www.squaretrade.com.
[Verizon Samsung Galaxy S 4] Captain Crypto:
Thanks. It was your post that clued me in. I'll check into it.
[Verizon Samsung Galaxy S 4] equake:
I also got a squaretrade warranty also but realized esquared has a better coverage which includes theft or loss.
[Verizon Samsung Galaxy S 4] fuzzynco:
[Solved] Can you post a ;link to them? (esquared)

google didn't find anything with that name? :confused:

the name is ensquared.

http://www.ensquared.com/
[Verizon Samsung Galaxy S 4] jova33:
You couldn't revert to stock, and have them honor the warranty? I mean, a hardware failure has nothing to do with the software.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
The warranty, even for hardware, is only 30 days on the Dev phone.
[Verizon Samsung Galaxy S 4] Captain Crypto:
I just compared Ensquared and SquareTrade. Same price for two-year plan (US$99). What I've learned so far:

Ensquared has theft/loss protection whereas SquareTrade does not.

Each covers three claims per contract.

Ensquared accepts claims on the 31st day after the application has been accepted.

The SquareTrade agreement states: "Damage to computer hardware, software and data caused by, including, but not limited to, viruses, application programs, network drivers, source code, object code or proprietary data, or any support, configuration, installation or reinstallation of any software or data." So, does this mean if I hard brick the phone, I get no replacement? I guess that's fair, but then again, I plan to hack/mod (software) this phone, so this raises a red flag for me.

The Ensquared TOS states, "Error or omission in design, programming, system configuration, faulty construction, or any original defect in any Covered Product, or recall by the manufacturer." Same comment regarding hard bricking.

So I guess the question is, does hard bricking a phone a hardware or software issue, and will it be covered? For everything else hardware related, either of these two should work.

I'll research both and get a feel for what people out there are saying about both and make a decision. I'll post my findings here if y'all are okay with that.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
I would guess that hard bricking is caused more of the time by failure to properly flash software or a bad software install and not so much by hardware failure? Makes sense that neither will cover any failure related to software. But if the failure is cause by hardware than it should be covered by either. And both cover accidental damage too.
[Verizon Samsung Galaxy S 4] Captain Crypto:
Totally agree, it's a software thing. But from a warranty perspective each carrier states that they don't cover damage caused by software issues that, to me, look like modding/hacking/ROMing, etc. I think I'll call each one and ask specifically, just to be clear about it. Either way, both are cheaper than transferring my Asurion insurance from my Bionic to the S4.