yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] carpboy:
I have been running various flavors of AOKP ROM's on SG3's for several years now. I recently obtained a refurb S3 and set it up to do the usual.

It came with stock TW 4.4.

Using ROM Manager I installed CWM and made an image of the stock phone. I then installed my AOKP variant and loaded my apps, blah blah. All is good.

I've since decided I want to revert back to TW for awhile. I restored my nandroid and I get the interminable GAPPS failure messages. I have on occasion been able to get it to calm down and have a working phone, usually be uninstalling play app and clearing framework services cache. This is extraordinarily painful and doesn't always work. I've done all the usual, reinstall GAPPS, etc., and basically it is a MAJOR headache just trying to get the image to function.

But....When it does work the phone does not see my SIM card, IMEI, nothing.. I have no mobile connectivity. Restoring the AOKP nandroid brings me back to a fully functioning phone.

So my questions are:

Can anyone explain to me why the TW nandroid is giving all these GAPPS issues and how to circumvent/fix it?

Why is the system seeming to lose my IMEI/SIM info? Is there a way to fix that? Should I have done something different in my setup/nandroid creation?

Lastly - I don't quite understand how CWM works. There is a recovery image. When I do factory reset, is it resetting to this recovery image as opposed to the factory TW? I seem to think so, when I do a reset I see the android version is not what my factory one is.

Thanks all.
[Android Q&A, Help & Troubleshooting] Eleiyas:
Hi guys, after a long hiatus from XDA , I am now back in need of more advice.

I simply cannot seem to flash TWRP recovery on this phone.

I have followed multiple guides and nothing is working.

I have installed all the necessary drivers and I have tried multiple different versions of flash tool and TWRP Roms.

On an older version of flash tool, my phone just sits off and flash tool finishes by bugging out with an error like "the phone booted too quickly".

I then tried a new version of flash tool and it did actually seem to flash TWRP ,however when I boot into recovery, my phone bugs out for a split second and then boots into standard os.

Can anyone help me?
[Android Q&A, Help & Troubleshooting] Eleiyas:
Managed to fix the issue with some perserverance!
[Android Q&A, Help & Troubleshooting] tirlibibi:
But what did you do ? I got the same problem.
[Tilt, TyTN II, MDA Vario III General] beetlejude:
Hi all. I truly apologize if I'm posting something that's already been covered, but I've searched for a while now on this one. I've done the PTT fix with PTT_Fix_4Tilt.zip (thanks the many posts for showing the way to that one), but I'd like to remap the push and hold feature for the PTT button to bring up the task manager. Has anyone done this, or know how to do it?

Thanks a bunch!
[Tilt, TyTN II, MDA Vario III General] kaluzu:
the answer is not from here, just on the wiki

http://xdaforums.com/showpost.php?p=1577293&postcount=12
[Tilt, TyTN II, MDA Vario III General] beetlejude:
Thanks but doesnt answer my question...

Thanks for replying, but it doesn't answer my question. I was not asking "How to remap the PTT button" - I already have done that (as I said in my post)-, but pointing out that once the PTT button is remappable, ther is no selection under button assignments to choose for launching the task manager. If someone knows, I'd appreciate it.
[Tilt, TyTN II, MDA Vario III General] ChInEsE ChIcKeN:
this helped me a lot thanks
[Tilt, TyTN II, MDA Vario III General] snooginsguy:
Yeah, I did this, but it takes a trick. You have to go into the Windows folder and find the taskmanagerapp.exe and make a shortcut for it. Take that shortcut and paste it into the Windows > Start Menu > Programs folder (or any subfolder you wish thereafter) and get out of file explorer. Then you can pick the shortcut to be used for the button assignment. I also did this for the backlight. If you use AE Button +, you can get a lot more hotkey options and really go nuts.
[Tilt, TyTN II, MDA Vario III General] beetlejude:
Thanks, I'll try that and look into AE +
[Tilt, TyTN II, MDA Vario III General] wireb98:
Thanks.Finally got working Task Manager shortcut :)
[Android Head-Units] barcodejames:
Hey guys, I'm new to installing Subs. I have the Atoto M4171 Android Head Unit. I am loving it so far, however there is no bass, so I am looking to add a sub to it. I was thinking of getting the Sound Ordnance B-8P powered sub from crutchfield. However, I have no clue how to connect the amp remote turn on wire to this unit. Looking at the wiring diagram, there isn't a wire labeled as amp remote turn on (or whatever the wire is called). Does anyone have this HU, and installed a sub with it?

Orange-Radio ANT Power

CANBUX-TX

Purple-Back Cam Control

Red-ACC

Pink Red-Steering Wheel Key1

Red Black-Steering Wheel Key2

Brown-Amplifier Control

CANBUS-RX

Yellow-B+

Those are the only non speaker wires (minus ground, ilumination, and Brake Control

Looking in the owner's manual that came with it, it has a table that lists "basic connection for function working normally" (the manual's wording, not mine) and it says External Amplifier RCA*4 (which is RCA Rear Left) + Wire Number 11 (which is the Brown Amp Control). I currently have that brown wire connected to a matching wire on the after market wiring harness that connects directly to the factory wiring harness. Should I disconnect that wire, and connect it to the Sound Ordnance's amp remote turn on wire, or should I use a different wire?

Sorry in advance if this has been asked before, I've just never installed a sub before, and would like to get specific instructions for this exact Head Unit.
[Android Head-Units] bobbyman:
(I use Google - how about you?)

There are several ways to get your amplifier to turn on and off remotely even if your head unit does not have a remote turn on wire. The cheap and easy way is to run the amplifier's remote terminal off of a switched accessory wire (your Red-ACC wire). This is the wire that your head unit uses. It is only powered when the key is in the accessory or run position of the ignition switch. When you shut the car off the wire loses power and the head unit and amplifier will both turn off. Your amp will be on when your car is on and off when you car is off. If you don't want the amplifier to always be on when the car is on you could wire a simple switch inline with this new remote wire. Normally you would leave it on so that it turns on when the head unit is on. But if you wanted to turn the amplifier off you could flip the switch to off which would stop the flow of 12 volts to the amplifier's remote turn on terminal.

There are also units that will sense the voltage on the head unit's speaker wires and then send a +12 volt signal to the remote wire. These units are an option for those who do not want their equipment on full time (when the ignition is on) and also don't want to wire in a switch. PAC makes some very popular ones such as the TR4 or TR7. David Navone also has an inexpensive model available that has a full amp of current output (you can add more components to it without needing an external relay).
[Android Head-Units] dnfm:
Tap the brown wire and connect to it. It should turn on the amp. The brown wire will have +12V when the deck is on, and it's only used to flip a relay in the amp, so it will draw very little power.
[Android Head-Units] canislupus01:
11. Brown (Amplifier Control)

As dnfm says, the brown wire is what you want.

That's your amp / remote turn-on wire. It connects to your blue wire from your amp.
[Android Q&A, Help & Troubleshooting] hbhorat:
Samsung galaxy S6, phone freezes and i'm forced to restart it when attempting to make a facebook or watsapp call.

Tried googling but couldn't find anything, any help would be appreciated.

Android 6.0.1
[Android Q&A, Help & Troubleshooting] hbhorat:
Ended up solving the issue by reflashing my rom.

Still strange how it used to work fine then one day it stopped working, oh well least there's a solution for it :)

Hope this helps anyone else out there having this issue.
[General Questions and Answers] ramimi:
Hello everybody !

I have the galaxy note 2 - gt-n7100 , stuck with logo , that won't start nor allow into "recovery mode" .

Only possibility - to go into "download mode" , like i did few times , trying to flash it with official samsung firmwares from sammobile site, according to instructions i found in your site .

I tried it first with "kies" -ended with the message : "firmware upgrade encountered an issue . Please select recovery mode in kies and try again .

After that failed, i tried it with odin.

All the times i did , ended with green square at the top left corner , with "pass" written inside , but the device, would go back to logo instead of reboot, as it should .

Besides , when connecting to pc or laptop , using usb cable , mtp driver fails to install, and on screen message , prompted me, to consult the manufacturer of the device.

Obviously , not the pc nor laptop , would even recognize the device !

Please help !

What is wrong with that device ?

What can be done to get it back on track ?

Thanks in advance ! - all the best !

Ramimi .
[General Questions and Answers] Droidriven:
Are you flashing the newest stock firmware?

Have you tried flashing firmware along with the PIT for your device?

Have you tried booting to recovery and factory reset from recovery? If you can't get to recovery, try flashing TWRP and then factory reset in TWRP.
[General Questions and Answers] ramimi:
Thanks a lot ! - unfortunately, nothing works yet .

thank you droidriven ! , for your suggestions , i tried to do so , but unfortunately , nothing works , yet .

I wonder , maybe it's better to seek help, in a lab, for this case , after what i did so far .

Maybe there is a problem, with inner component or so .

Anyway , again , thanks a lot !

All the best !

Ramimi .
[Xiaomi Redmi 2 Questions & Answers] ezrawk:
Hi guys, as you can see from the title, I just bought a new Redmi 2 LTE CN Dual-SIM (Unicom China) WT88047 - HM2014811. I flashed TWRP using Stock Recovery with stock rom (first I tried the 'fresh out of the box stock' and latest global developer rom) and succeeded to boot into TWRP. The problem is (using the 2 stock roms), my touchscreen doesn't work when I try to press or slide when I'm in TWRP. Touchscreen does eventually works after screen time out though. Successfully installed Custom ROMs and stuff, but everytime I boot into TWRP, to use it, I have to wait until the screen goes black (time out) and then the touchscreen becomes responsive. The question is, is this a bug (hardware level bug) or I did things the wrong way? Is there anyway at all to fix this? Because once I accidentally turned off screen timeout and had to flash stock via fastboot to wipe TWRP data. It's becoming pretty annoying. Thank you, please do reply ASAP. :)
[Xiaomi Redmi 2 Questions & Answers] raymond_bqg:
So according to your post....you flashed t.w.r.p by stock recovery .So let me guess.The t.w.r.p was from miui forum.I suggest you to flash t.w.r.p 3.0.2.0 by kumajaya sir (from XDA) by fastboot or rashr or flashify. And flash any custom ROM from here(XDA) and do a clean flash(though clean flash is not a magic wand:p)
[Xiaomi Redmi 2 Questions & Answers] ezrawk:
Yes exactly, you are correct, the TWRP was from MIUI forums. I did try flashing kumajaya's TWRP via fastboot and the results: Can't boot to TWRP (and this was before I found the post in MIUI forums, because it's been my habit to check XDA first before oem forums). Sorry I forgot to mention firsthand about this. Maybe it was because of my Redmi 2 model, it's got different soc parts or something, I'm not that well much informed about the differences between Redmi 2 models. What I did found out was that my Redmi 2 Prime (says the online shop that I bought it from) was not exactly Redmi 2 Prime, but it was the Redmi 2 China LTE Dual-SIM model with 16 GB's of ROM and 2 GB's of RAM (Wingtech 2014811 - Redmi 2 LTE Unicom China Dual-SIM).

I do have past experiences with Redmi 2 from a friend who bricked his Redmi 2, and I flashed kumajaya's (sir) TWRP with ease. No problems, perfectly booted to TWRP without any bugs or other problematic situations. Flashed custom roms and kernels, even reverted back to stock (vice versa).

I'm not totally shocked by the different variants of Redmi 2 (My past HH was a Zenfone 5, and yes A*SUS likes to ship HH with different SoC parts, it made me unable to unlock the bootloader), what makes me curious is the difference between KK bootloader and LP bootloader, the limitations and weird bugs that they offer. Why did Xiaomi suddenly implemented a different bootloader for Redmi 2, thats my main question so far.

*PS: I've tried to use nicknitewolfs Modded kumajaya TWRP, from the LineageOS 14.1 thread, and yes it booted, but the same problems exists.

I'll try once more to do a clean flash of TWRP. *fingerscrossed
[Xiaomi Redmi 2 Questions & Answers] raymond_bqg:
If he phone have a different SOC then I think no ROM in this forum will work(may be I am wrong,and I hope this) perfectly.If kumajaya Sirs t.w.r.p does not work then try Tesla ROM by miui forums t.w.r.p.I once flashed Tesla by miui forums t.w.r.p ,and it worked fine .But lineage by miui forums t.w.r.p never will work.
[Xiaomi Redmi 2 Questions & Answers] ezrawk:
Oh yeah sorry, wrong words to put, just different parts I meant (Touchscreen, proximity, etc.). Okay thank you, I'll try MIUI's Tesla ROM. Thank you for the reply btw. :) :highfive:
[Xiaomi Redmi 2 Questions & Answers] raymond_bqg:
Not miui's Tesla.As u said t.w.r.p from miui forum worked in ur device.So I said try to flash Tesla [MENTION=4453409]premaca[/MENTION] (from XDA) by t.w.r.p(from miui forum).May be that will work.
[Xiaomi Redmi 2 Questions & Answers] ezrawk:
Oh so what you're saying is, "changing the zips original recovery.img (from MIUI) and replacing it with Tesla's TWRP from XDA? I'll try that! ", never mind that, I got it wrong, what you meant was install image right? I've done that before, and 'the situation below' happened.

Oh btw I tried flashing XDA Tesla's TWRP via fastboot commands, clean flashed it (fastboot format system, cache, userdata, fastboot erase recovery, fastboot reboot-bootloader and then flash recovery blablabla.img), it booted, but it made another bug. First, the same as before, touchscreen unresponsive, second when screen time out kicked in, my power button or even volume buttons couldn't wake TWRP up. I'm feeling so hopeless right now.. :D
[Xiaomi Redmi 2 Questions & Answers] raymond_bqg:
You got it wrong again....may be my fault.

I am trying to say that flash Tesla ROM by miui forums twrp.
[Xiaomi Redmi 2 Questions & Answers] ezrawk:
Oh I see! :D

Well which Tesla ROM are you mentioning above? The latest nougat build or the final MM build? Because right now I'm using the final MM build. What does flashing the Tesla ROM have to do on fixing my unresponsive touchscreen on TWRP?
[Xiaomi Redmi 2 Questions & Answers] raymond_bqg:
Rom compatibility with recovery.
[Android Q&A, Help & Troubleshooting] wwe9112:
Hello all,

I was wondering if anyone recently has developed a way to bypass the root check for Mobile Iron.
[Android Q&A, Help & Troubleshooting] peret2000:
Moreover, I think you cannot bypass Mobileiron protection that avoids unlocking bootloader. It does not allow even pressing several times on 'compilation number' just to show developer options (USB debugging, specifically). It seems not to work even with a factory reset. So, it seems the definitive method to avoid rooting
[Xperia Z Q&A, Help & Troubleshooting] mouad94:
hello guys

i have xperia z i rooted it 5 days ago and today i had this error 504 in google play after that i deleted cashe and data of play store framwork then i have this error error-retrieving-information-from-server-rh-01-from-the-play so i didn't know what to do and i reboot the phone when i did that now i am stuck in bootloop i can't turn off or anything just boot loop with out stop

i don't have castum room and its locked bootloader and i have no recovery like twrp please what i can do in this situation

sorry for my bad english
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] dlw1146:
Finished rooting and unlocking N910V using the following method last night

https://xdaforums.com/note-4-verizon/general/easy-guide-how-to-root-verizon-galaxy-t3454593

All seemed to go OK.

This morning, the phone will not boot up.

The error 'kernel is not seandroid enforcing' and turns off.

Any help on solving this will be appreciated.

dlw
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] -spektor-:
Did your phone boot properly after rooting? If the error you mention is in the top left hand corner on the boot screen I belive it's just the kernel and that should be fine if anything I would try the troubleshooting options on the thread you provided or if not have you tried factory reseting your phone I know that not reseting your phone can cause boot loops because that's what happened to me after following the same thread as you.
[Lenovo P2 Guides, News, & Discussion] EypCnn:
EXPLANATION

Hello friends You Lenovo P2 Your device How to install Xposed I will tell it. Take steps to step through the process.

FOOTNOTE

Your device may be a Brick Do not forget the spare person against any odds.

I and OneTeam are not Responsible for Possible Problems.

XPOSED INSTALLATION

Download the Xposed.apk file below.

After downloading, give the application root permission and go to the Main Screen.

On the Home Screen, press the Green zone as shown below.

Your car will popup.

Select the option above from the drop-down menu.

When the selection is complete 2. Installation will start as shown in the picture.

When the installation is finished, press again to start the icon.

You can use Seamless Xposed on your device when the reboot process is complete.

WARNINGS

Loading Resultant Booting can run dull.

DOWNLOAD

XPOSED 3.1
[Lenovo P2 Guides, News, & Discussion] ilmervanhattem:
Guess no exposed for 7.1.1 right?
[Lenovo P2 Guides, News, & Discussion] dip_anker:
Hi, i am using lenovo p2 with nougat and I downloaded this apk and installed the framework but i am not able to use any module even though the modules are activated (ticked) and I rebooted multiple times. I also tried installing the framework (through app and also via recovery) but that also was of no help. Please help me

---------- Post added at 07:33 PM ---------- Previous post was at 07:31 PM ----------

Also when I download a module, there is no button to install it and instead i see the same download button on the completion of download. :(
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Devam03:
Welcome Guys!!!

​

Whats this for?:-

Many users face issues while installing V4A drivers on their device. Here is the ultimate fix for it.

Requirements:-

1. Root explorer like ES File Explorer.

2. The flashable zip of V4A.

3. Some knowledge about flashing, modifying system directory.

Procedure:-

1. Install busybox and make sure device is rooted properly.

2. Go to System > Vendor > Etc and check for the file named audio_effects.conf and copy it and paste it to System > etc (Overwrite).

3. (Not compulsory but do it if it doesn't work) Rename the System > Vendor > Etc > audio_effects.conf to audio_effects.conf.bak

4. Now flash the V4A zip in recovery and Voila!! :) :)

Please Hit Thanks If I Helped :) :)​
[Xiaomi Redmi Note 3 Guides, News, & Discussion] isas123:
How to add effects .irs files.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Devam03:
Pls google all that stuff. No off topic here.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] crullick:
thanks a bunch!

works like a charm (after few other unsuccessul methods)

latest miui.eu 7.2.24_v8-6.0 (kenzo)

ViperFX_2.5.0.5_by_guitardedhero

valuable post :good:
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Devam03:
Your welcome. Please hit thanks if I helped!
[Xiaomi Redmi Note 3 Guides, News, & Discussion] aldichuy:
i still stuck at instal driver, it says i need to instal latest busybox
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Devam03:
Did u install busybox?
[Xiaomi Redmi Note 3 Guides, News, & Discussion] aldichuy:
yes i have

edit: i just uninstal both and reinstall viper first and then the busybox, i did soft restart the phone before instal viper driver, and works
[Xiaomi Redmi Note 3 Guides, News, & Discussion] MadMicro:
4. Now flash the V4A zip in recovery and Voila!!

Where is the V4A zip. I downloade zip from official site but ita just an apk file ???
[Xiaomi Redmi Note 3 Guides, News, & Discussion] c_/\/\_k:
nice effort
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Devam03:
Thx. Hit the thanks button if i helped.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] gu:
I've spent the last few days reading wikis, guides and threads about upgrading my Tytn, but I still have a few questions:

This guide describes a method for preventing hard-SPL from being overwritten with another bootloader. If I understand it correctly, this is only a problem with original shipped ROMs, and not with the ROMs cooked by the people here. Is this correct? Can I upgrade with any of the custom ROMs here without worrying about overwriting the bootloader?

Are the radio ROMs country or region specific or can I use any radio ROM from all over the planet?

Can I run into any problems if I try to downgrade the radio ROM? If I remember correctly, there was a a lot of trouble with this in the old days when I played around with the ROMs on my Wallaby (and I still had the future ahead of me).
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mrvanx:
Olipro wrote HardSPL so that it wouldnt allow itself to be overwritten, as far as i know you can overwrite HardSPL by using SSPL (the software bootloader which runs in RAM and not from the devices flash memory area as a normal bootloader does).

Dont worry.... upgrade to HardSPL v2.10 and then you can flash any ROM you like. Some carrier RUUs wont recognise the newer SPL so might not be happy with it. Depends on what ROM you wish to use.

Radio ROMs are pretty much universal however the best ones generally acknowledged are 1.47 or 1.48 (any variant)....as newer ones are unstable and seem to use the battery alot more.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] gu:
Thanks for a quick and informative reply, mrvanx. And for the brilliant guides!

However, your answer left me with a couple of other questions.

If Hard-SPL cannot be overwritten, is there ever a need for the method I linked to in my previous post? Also - I thought one of the benefits with Hard-SPL was that it can be removed (and the original BL brought back to life) by flashing an official ROM.

If I understand you correctly, you're saying that if I really want to overwrite Hard-SPL, I can do so using the SSPL, but upgrading with custom ROMs having SSPL bundled with them won't mess up Hard-SPL?

Sorry if these are stupid questions, but I'm a bit afraid of bricking the Tytn I'm currently borrowing from a friend :)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mrvanx:
Update to HardSPL....safe in the knowledge that you CAN revert it back to stock if you wish, the details arent necessary dude. Go for it....its the best thing to do even if you dont change the ROM since the latest radios take advantage of the faster radio flashing technique in later SPLs.

You DRAMATICALLY reduce the risk of bricking the device by flashing HardSPL first. :)

Were you planning on using any particular flavour of ROM?