yashsingh1/xdaforums huggingface dataset:
[Moto G Q&A, Help & Troubleshooting] lost101:
Flash the appropriate stock firmware image via fastboot.

http://xdaforums.com/showthread.php?t=2537119​
[Moto G Q&A, Help & Troubleshooting] blufmaster:
i have flashed almots 7 diferent files sir but still same :(
[Moto G Q&A, Help & Troubleshooting] reeved:
yes, but have you flashed the RIGHT one?
[T-Mobile, Samsung Galaxy SIII] QuatroQuatro:
Hey,

I just flashed C-Rom, the Bluetooth doesn't appear to be working for any ROMs though. Apparently though, according to persius97, you can change 3 commits to get it working:

"Ok. Here is the CM Commit.

http://review.cyanogenmod.org/#/c/65280/

The 3 files it modified are BoardConfig.mk, bluetooth/vnd_d2.txt, proprietary-files.txt"

I dont understand how to change this though, and couldnt find anything on Google. If anyone could post a procedure or point me to a tutorial, that would be fantastic!

Thanks!
[T-Mobile, Samsung Galaxy SIII] sswb27:
You would have to download the source code and build it yourself. Or request the Dev of the ROM to do it, if he will.
[T-Mobile, Samsung Galaxy SIII] QuatroQuatro:
Oh OK. Thanks!
[Galaxy S III Mini Q&A, Help & Troubleshooting] Shady Nashor:
Español:

Buenas, hace poco mi celular al cargarlo apagado se queda "congelado", normalmente me aparecia una imagen que giraba y luego me mostraba la bateria y cuanto tenia de carga, pero ahora se queda en la imagen que deberia girar pero no lo hace y no puedo prender el celular aunque quite el cargador. Para solucionarlo debo quitar la bateria y no es algo muy lindo porque parece que se va a romper la tapa de lo que me cuesta abrirla xD

Utiliso C11, tengo instalado DU Battery Saver & Widgets y tengo I8190L.

Perdon por no hablar en ingles, pero creo alguno me podra ayudar.

Ingles(Google Translate):

Hi, recently my phone to charge off remains "frozen", I usually appeared an image rotating and then I showed the drums and soon had charge, but now it is the picture that should turn but it does not I can turn the phone even if you remove the charger. To fix should remove the battery and is not very nice because it seems to be breaking cover what it costs me open

Utiliso C11, I installed Battery Saver & Widgets DU and I I8190L.

Sorry for not speaking English, but I think one may help me.
[General Questions and Answers] yjs1600:
Can someone explain me the good thing about deodexed rom vs. ota?

Feel free to enlighten me!
[General Questions and Answers] Zeuscluts:
In short deodexed roms allows you to modify more, means more of modification & theming.

And ota are odexed roms which are fast but doesnt gives ypu much permissions to modify it.

Thankyou,

Zeuscluts

Hit thanks if I helped you.
[T-Mobile Samsung Galaxy Note 3] thankyouxda:
Hi,

Just updated to N900T UVUDNF1 bootlader and ROM and not quite happy with a few things. I was on Jelly Bean till now. Is it possible to install a NB4 or MI7 Rom even though I am on the new boot loader and radio? Would it work? I need to switch to a TW ROM because of WiFi calling.

Thanks much!
[T-Mobile Samsung Galaxy Note 3] Misterjunky:
re: radio, bootloader and basebands

NB4 is not jellybean it's kitkat 4.4.2 TW firmware.

MI7 is jellybean 4.3 TW firmware.

Both the NB4 and the MI7 are Tmobile N900T TW roms and both have

the wifi calling option as long as your phone is a Samsung N900T

Tmobile branded device and you are on the Tmobile network.

If your radio/baseband is NB4 then you cannot downgrade to MI7,

however you can upgrade to NE6 or the latest NF1 firmwares which

are Kitkat 4.4.2 TW firmwares and both have the wifi calling feature.

Good luck!
[T-Mobile Samsung Galaxy Note 3] thankyouxda:
Hi,

I am already on NF1 firmware. Upgraded yesterday(was on M17) and think I may have made a mistake upgrading to it so soon based on my usage of one the new NF1 custom roms.

So I cannot use a M17 (JB) Rom, but could I install a NB4 Rom since it is KK? I have TW recovery(2.7) installed.

Thanks!
[T-Mobile Samsung Galaxy Note 3] thankyouxda:
In case anybody wondering I installed [NB4][AROMA] Hyperdrive KK RLS3.1 ║║ Hyperdrive just right now and it has been fantastic so far

No issues yet. GPS locked inside the house in a second on the first try.

So NB4 Rom works on an NF1 firmware imho.

Cheers!
[G2 Q&A, Help & Troubleshooting] cactusamerica:
Hi guys,

I've tried to do the standard approach of powering off the phone, pressing the Volume Up button and then plugging in the USB cable and does not work. Are there any other ways of getting into download mode?

Thanks in advance.
[G2 Q&A, Help & Troubleshooting] Art Vanderlay:
Through adb type command adb reboot download
[T-Mobile Samsung Galaxy S 5] jjlean:
I am rooted and using twrp recovery. I go to encrypt my device and it goes to the android, but it just reboots once and turns back on. No sign of encryption. Any ideas here?
[T-Mobile Samsung Galaxy S 5] jjlean:
Anyone encrypted their devices at all?
[T-Mobile Samsung Galaxy S 5] jjlean:
Bump
[T-Mobile Samsung Galaxy S 5] fffft:
It's hard to address your question properly because you didn't provide any meaningful amount of information, in particular what TWRP and firmware versions you are using? You only left us a brief summary and didn't give any detailed description of your situation.

I saw your post several weeks ago, but went on to help someone else instead because of the crucial missing information.

Also, you can't have done much of a search (any search?) to see if your question had already asked and answered or you would have found this.

The relevant posts are mid thread where the recent encryption changes in Android and how TWRP is handling them are discussed. This will pertain to you vis a vis whether your version of TWRP support encryption or not.

.
[T-Mobile Samsung Galaxy S 5] jjlean:
I didn't know if it was twrp or some other issue. I'm not a programmer or developer.

I did search Google, but I didn't search xda because I'm using the app. Thank you for the information.
[T-Mobile Samsung Galaxy S 5] fffft:
I'd be happy if the information helps solve your encryption issue.

As to your other comments, it doesn't matter whether you knew if it was a TWRP or other issue. Nor do you need to be a programmer or developer. It's just common sense that you need to provide abundant detail if you have any realistic expectation of effective help.

I have no idea what your profession or hobbies might be. But for a simple analogy, take a failed pie recipe. If you say, awww, my pie didn't turn out properly - and you would like help fixing that, rather than just sympathy.. then don't you need to provide details for someone to easily help you?

How could anyone help you without knowing something about the recipe or how you went about baking the pie? Without information, the best you could hope for is random guesses. You don't need to be a programmer or developer to know that abundant details would greatly increase your chances of being helped.

And almost any combination of keywords on Google would have located the TWRP support forum. And any search with both encryption and TWRP in the search finds the recent thread that I linked you to.

.
[T-Mobile Samsung Galaxy S 5] jon123nyc:
It's funny I've searched this site and scoured google, but I haven't seen a whole lot of info about issues encountered during the device encryption process. I've read that it slows the device down, but this was said about devices other and the S5...I've also heard that when encrypting, the screen goes black after a few seconds of the green android, which is the issue I've encountered....but, again, this was regarding a different device. It was in my search that I found this stale thread. Has anyone elkse had this problem?

Android is still running, there's a blue led on and my computer sees storage, but the screen stays black and doesn't respond to any keypresses. I've got twrp 286 and deviant's rom with the ob1 bl and modem/kernel. Next I tried it with a stock room, the only change I made before trying was installing twrp and reacquiring root after setting back to factory image via odin. I went in knowing that nandroids would be a problem after encryption because twrp wouldn't be able to unencrypt, but it shouldn't affect the actual encryption process or the device once unencrypting by entering the password at boot. Anyway,, I have been sitting waiting for 2 hours now and the blue led is on but nothing else.

Has anyone else had this happen to them? Any workarounds?

Thanks guys!
[MDA III, XDA III, PDA2k, 9090 General] angellonewolf:
the one of the 4 buttens on the front of my xda2s (the internet) butten does not work and the email needs more pressure than any other butten i think it needs cleaning ? or is there an test program just to cheak

one more thing how can you change the back o2 screen as the blue is boring now

are there any more free games for this pda i have found a few shereware and a very few free games but any one got more or know ware to get more from

please could i say thanks in advance angel

ps please could i say a big thanks to this site any any one who helped with the unlocking tool as it saved me £25 and half the shops wanted me to leave the phone for two days the other half said it could not be done !!

again thanks angel
[MDA III, XDA III, PDA2k, 9090 General] znj:
I have somewhat a similar issue. My BA's Navigation button isn't working. I hope someone would help us out with our dilemma.
[Moto E Q&A, Help & Troubleshooting] fenircalderon:
I want move the game on the sdcard for example: Asphalt 8, Modern Combat 4 and others large space games.
[Moto E Q&A, Help & Troubleshooting] Gogeta:
Everyone is a noob like you when he joins XDA.

You just need to read carefully and all the tutorials here are very elaborate, I used to be a noob like you, but I read everything carefully and successfully rooted, and even if you soft brick it, its pretty much regular and normal while flashing, more than 1 hour since your post, you could have rooted your phone easily in one hour instead of waiting for reply, be sure to check that noob video by XDA too :)
[Moto E Q&A, Help & Troubleshooting] lokesh reddy:
To play big games you should install a app called folder mount pro
[Moto E Q&A, Help & Troubleshooting] jitz_:
http://xdaforums.com/showthread.php?t=2796528 [Solution]
[Moto E Q&A, Help & Troubleshooting] fenircalderon:
I forget it, I have Kitkat 4.4.3
[Moto E Q&A, Help & Troubleshooting] fenircalderon:
??

But for this app the Moto E [or any smartphone] need be the rooted, How can do it?

I need unlock the boothloader then rooted the smartphone, I have Android 4.4.3 Kitkat
[Moto E Q&A, Help & Troubleshooting] lokesh reddy:
U should be definitely rooted ...

But up to me their is no other non rooting way

Sorry boss
[Nvidia Tegra Note 7] jardam.cz:
I just would like to share a very good experience about de-Chinesing, rooting and tweaking my Homecare (the Chinese version) Tegra Note 7. I would like to share this because of a lot of struggle I had AND because it is sooo simple. I believe this will work with other brands of the NVIDIA Tegra Note 7. So he is is:

1. I used the ADVENT VEGA Factory image to reflash my Note. Simple and painless. Fast and straight forward!

2. Update to the latest OTA. (2.4 in my case)

3. Use the latest version of SuperTool to install TWRP, root and install the "write-to-SDcard" fix.

4. Download and install Xposed Installer (it is not available in Google Play, just search the web) and install the frame work.

5. Install GravityBox for KK and set up those handy tweaks.

The ultimate device is born!
[ONE Android Development] insestito:
Thank you!!
[ONE Android Development] blak24:
Warranty will NOT be void :P Anyway thanks, hoping someone will try it :)
[ONE Android Development] Consistant:
Really? That's very interesting. Got a source on that? If so I'll remove the disclaimer from it in the next version if someone finds bugs or similar problems.
[ONE Android Development] blak24:
Well OnePlus always stated that rooting the phone will not void phone's warranty
[ONE Android Development] Consistant:
Yeah, I just Googled it and it seems indeed like the warranty isn't voided by unlocking the bootloader. That's a first, props to OnePlus for doing that.

And thanks to you for pointing out! I'll make sure to get that fixed once someone has properly tested it in case it needs additional changes.
[ONE Android Development] joeg6217:
When I run the toolkit, this happens?

---------- Post added at 11:35 AM ---------- Previous post was at 11:18 AM ----------

Seems to have sorted itself out. It's now working ;)
[ONE Android Development] GuestK003:
When flashing a recovery:

ERROR: could not get pipe properties

rebooting...

Just posting for FYI.
[ONE Android Development] joeg6217:
I've used a few different toolkits for a variety of phones.

This was the best and easiest I've used yet.

Everything worked perfectly.

Brilliant

:good:
[ONE Android Development] belugone:
in my Mac won't start (mavericks )....

---------- Post added at 09:14 PM ---------- Previous post was at 09:08 PM ----------

only a corrupted downloaded file. noow work on my maverick's imac, sorry
[ONE Android Development] Busstop:
Thank you!
[ONE Android Development] sharp2G:
I'm trying to unlock my boot loader, but thing is popping up.

Make sure your phone is inside Android, is connected to your Mac and has

USB Debugging enabled.

After continuing you need to authorize your computer by looking at your phone and tell it to 'Always allow' your computer.

Press any key to continue...

* daemon not running. starting it now on port 5037 *

* daemon started successfully *
[ONE Android Development] Consistant:
Yes, that's ADB starting up it's server as usual. Keep waiting (it looks for your device) for a minute or two. If nothing happens try using the "See all devices connected" in the "basic adb and fastboot commands" menu. If you need to keep waiting forever or it says "No devices" then you need to try with another USB cable as that one might not have data transfer capabilities.

Remember as the instructions tell you, you need to enable USB Debugging and you need to be inside Android (like on the homescreen or something).
[ONE Android Development] sharp2G:
I've managed to get root access thanks to your application for Mac! THANK-YOU!
[ONE Android Development] GuestK003:
Huge bug when flashing to stock. It's flashing userdata instead of userdata_64G. userdata_64G has to be used when you're flashing the 64gb variant. A work around is to delete the userdata file and rename userdata_64G to userdata. then run the install script. You may modify your app so that it asks if you have the 16 or 64 then load the install script associated with the size.
[ONE Android Development] alnova1:
Worked great! Thank you!
[ONE Android Development] Consistant:
Thank you so much for pointing this out, that's an extremely ugly bug that can cause problems. I'll make sure to get that fixed as fast as I can by adding a simple prompt asking for the version.
[ONE Android Development] GuestK003:
Awesome. Thanks for the update. :)
[ONE Android Development] no_username_available:
this should be added to the tool/utilities section great work man, saw this on the oneplus forum too :good::good::good::good::good::good::good:
[ONE Android Development] nanoo-eg:
I have a question. We need to download anything else like sdk, drivers or just the tool kit? I have see that adb drivers and fastboot can be installed from the tool kit. Thats all?

Thanks.
[ONE Android Development] Consistant:
Both the adb and fastboot binaries are inside the application. Nothing in the toolkit requires you to install the binaries, installing them are completely optional, but you can install them from the toolkit if you wish to do so for your own use. If you install them you can write adb and fastboot commands straight in the terminal.

Everything should work straight out of the box. Just choose what you want to do and the application will use it's own fastboot and adb binaries. If it says something like "missing pipeline" or gives off other errors, check your USB cable or try with another one, adb and fastboot can be quite picky at times.
[ONE Android Development] nanoo-eg:
Thanks my friend. I wait the next days my OPO and I want to be ready.

So the first I do is unlock the bootloader, second flash a custom recovery (they are also inside the application) and then root. Correct?
[ONE Android Development] Consistant:
Yeah, currently that's how it works. Unlock -> Flash any custom recovery -> Root.

I'll be releasing the 1.2 version of the toolkit pretty soon which won't require you to install a custom recovery in order to root. Unlocking the bootloader will still be required though.
[ONE Android Development] nanoo-eg:
Thanks its so simple!!!!!
[ONE Android Development] dubbactrumpetmsu:
Jeez, this was one os the easiest toolkits I've ever used, and available on Mac to boot. Props man, this worked fantastically. I'm guessing to take any of the CM updates (I just got prompted for one for the gyroscope and something else) I should unroot first?
[ONE Android Development] Consistant:
Thanks, I'm glad you liked it!

No, you don't need to unroot before installing an OTA, it will work just fine. However if for some reason root doesn't persist after installing the OTA, just root it again through the toolkit.

It should still be rooted after installing the update though, but you never know. If root doesn't survive the update, you could try using the "survival mode" the SuperSU app has which is basically made so that root persists after installing an OTA update.
[ONE Android Development] dubbactrumpetmsu:
Haha I actually just decided to flash it, and it let the OTA flash straight through TWRP. Gotta love CM and openness. This phone is absolutely sick.
[ONE Android Development] rspkt:
Thanks for posting this toolkit

I'll be receiving my OnePlus One 64gb in the mail this week. This will come in handy. Thanks for putting this together for us. I'll report back once I receive the device and get it set up. Thanks again.
[ONE Android Development] xkawsx:
Do I need to download anything else to revert to stock?
[ONE Android Development] Consistant:
New version is released people! Features, features, features!

Ver 1.2

- Added a way to lock the bootloader.

- Added a special way to unlock a relocked bootloader without wiping the phone it can also remove the tamper bit! (Thread)

- Made it possible to root the phone without installing a custom recovery.

- Made it easier to reflash back to stock. It now downloads and the factory image automatically in a designated folder.

- Added locking in the basic adb/fastboot commands.

- Added reflashing the stock image by using a manually downloaded factory image in the basic commands.

- Loads of fixes here and there.

Not anymore you don't! It will now automatically download the factory image, unzip and fix everything. Please download the new version and test it out!
[ONE Android Development] xkawsx:
This tool is amazing!! I also just unlocked bootloader > flashed custom recovery > root! All successfully done with your tool! Weird thing is that it didn't wipe anything!!
[ONE Android Development] cy88:
Good to know!

Can we confirm that this is the normal behaviour? I forgot to unlock the bootloader before starting to use it and wanting to do it now.
[ONE Android Development] Consistant:
Thanks!

It didn't wipe it? That's very strange. It's supposed to wipe it the instant you unlock the bootloader. It's one of the requirements Google has for manufacturers to be allowed to ship with Gapps. It's basically a safety feature to make it impossible/hard for thieves who might steal your phone to just unlock it and start extracting personal information like accounts and pictures.
[ONE Android Development] cy88:
Ha! I did it, and wiped. Lucky I haven't start using it yet.
[ONE Android Development] xkawsx:
Yea I found it very weird.. I was ready for it to be wiped.. First time I unlocked it, rebooted all files were still on there so I thought maybe it wasn't successful. I did it again same thing! So I just follow through and flashed Recovery then root!
[ONE Android Development] cman6453:
Everything went well except for rooting. Tried to root without installing TWRP. It reboots into stock recovery instead of fastboot and just sits there. I hit enter to continue and boot into TWRP... It stays at < waiting for device >. Phone stays in recovery...

EDIT: Couldn't wait so I flashed a custom recovery (CWM), rooted and installed a new ROM. I went thru the above scenario a few times to make sure it wasn't me. I was "inside Android", debugging allowed and connected to my Mac via USB cable. Also, after rooting, your instructions say to install SuperSU from Google Play store. I checked my apps and it was already installed? Other than that, great tool!! Thanks to you and the others!!
[ONE Android Development] Consistant:
That is very interesting, thanks for reporting that. I assume you disabled "Update CM Recovery" before booting, correct?

Could you try the "[Fastboot] Reboot the phone into any custom recovery (without installing)" option from the basic adb/fastboot menu and check if any of the custom recoveries do boot? It would be a great help. Thank you.
[ONE Android Development] cman6453:
Yes.

Tried all 3 and the phone didn't even reboot.

EDIT: Just realized that I relocked the bootloader and went back to stock so that may have invalidated this test.
[ONE Android Development] Consistant:
Remember that you need to be in fastboot first. Hence why it says [Fastboot] before it. I see now that it's sort of misleading with "reboot into". I'll change that later.

1. Use the [ADB] Reboot into fastboot

2. Use the [Fastboot] Reboot into a custom recovery without installing it

Oh and yeah, I don't think it'll work without a unlocked bootloader.
[ONE Android Development] no_username_available:
i downloaded the toolkit and when i clicked to open it it gave me the warning prompt and i clicked open anyway, after that it gave me the opening animation where it zoomes in and like quickly flashes the page (you know what I'm talking about right?) and then nothing, i even tried copying it to my applications folder but still nothing
[ONE Android Development] Consistant:
No, I'm not sure what you're talking about. If you click the "OneToolkit" application (it has a red icon) the terminal is supposed to instantly appear. It's most likely a white window with black text and it's icon in the dock looks like a blackboard with >_ on it.

If that doesn't work, put the "OneToolkit" application inside the Applications folder. Open up the "Terminal" (it's in the utilities folder in Launchpad) and copy paste this:

sh '/Applications/OneToolkit.app/Contents/Resources/Scripts/start.sh'

See if it starts up then. If not, post what error it returns.
[ONE Android Development] nikeman513:
This is great! Thank you! If it doesn't run the first time, eject then go back in the app and it should open.
[ONE Android Development] no_username_available:
thank you i will try that

EDIT: it says permission denied
[ONE Android Development] Consistant:
Looks like you don't have permission to start the script. That is strange, maybe you've enabled a security feature or some firewall/anti-virus are blocking scripts from being ran.

Anyway, to fix it copy paste

sudo chmod 755 -R '/Applications/OneToolkit.app/Contents/Resources/Scripts'

into the terminal and then write the command from the other post again. The password it asks for is the password you sat on your Mac.

If that doesn't work try

sudo chmod 755 '/Applications/OneToolkit.app/Contents/Resources/Scripts/start.sh'

and then the other command.

If that doesn't work either, try

sudo sh '/Applications/OneToolkit.app/Contents/Resources/Scripts/start.sh'
[ONE Android Development] no_username_available:
thank you so much man, ill try these out later as I've decided to hold off on rooting just yet, but i just got my OPO :D I'm so excited
[ONE Android Development] yankees45us:
I am trying to figure out how to use this toolkit without wiping any data since supposedly its possible? Any suggestions or guidance? Thanks