yashsingh1/xdaforums huggingface dataset:
[Ornate TrueSmart] Lokifish Marz:
EnSec STOCK Secure is a continuation and is based on newer firmware. There may be some sensor fixes and a couple of other things but other than that is very close to the original EnSec. Even though neither are perfect, both are still the best choice for security at this time. I personally would suggest flashing kuronosan's EnSec simply because it is a current and active release.
[Ornate TrueSmart] Lokifish Marz:
I have not tested the current version of monx ROM as every dev that was here prior to monx has quit releasing on xda for this device. I have quit dev support for the device on xda as well. You can pretty much thank monx for that.

So ClearD is gone, kuronosan is only providing support, and Dees wasn't surprised at what happened. Adam Outler is off on other projects. Any other dev I've talked to also found monx's kanging, games and insults a bit offensive. Enjoy your monx flavored icing as, from what we can tell, there is almost no real ROM work and mostly themeing. But what do we know, we are nothing but wannabe devs according to monx anyway.
[Ornate TrueSmart] xcooling:
You guys are so pathetic, NO ONE CARES ABOUT YOUR ISSUES

Focus on your own roms and ignore the rhetoric, because no one actually cares.
[Ornate TrueSmart] Lokifish Marz:
If you want to support somebody that stole Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and my work then calls the very same people whose work he stole fakes and wannabe's go ahead. Enjoy your easily hacked, unoptimized theme being passed off as a ROM.

And it wouldn't have been a problem if he had simply done the proper thing and asked and credited and not called everybody else a fake and wannabe. Not a problem though as of 8/7/2014 I have rescinded any and all permissions for xda and it's members to use my works, reference my works and mirror my works.
[Ornate TrueSmart] xcooling:
awesome, what a helpful person.

Thanks for standing by the community.
[Ornate TrueSmart] Lokifish Marz:
Adam Outler, Dees Troy, kuronosan, ChiefzReloaded, ClearD and myself all work(ed) together on the TrueSmart/x201. Almost all work released on xda and any other forums, English or otherwise, is either based on our work, or authorized mirrors of our work. Some of our work is even in official firmware as we have worked with Omate since October of last year on issues.

I maintained an updated archive of almost every firmware and ROM released for not only the TrueSmart but the entire x201 platform and did security checks on all of it as well as look for any changes that may benefit all x201 users. I was also responsible for the core ROM work as well as being part of the early TWRP development and assisting the other devs with their work. Adam Outler, Dees Troy and kuronosan have all referenced my work at one point or another for their own works. In fact my work was called "amazing" by Adam Outer and "required" buy multiple other devs.

monx STOLE the work of at least five other devs and never even so much as apologized, then have repeated called other devs wannabe's.

And as far as the security and optimizations analysis, those results are after a peer review in which all the results matched. monx has called it b$ and and yet again called multiple devs wannabes.

I have better things to do than be part of a community that allows an ass like monx to kang, distribute an admitted trojan infected ROM and call multiple devs that came before him wannabe's and be a general ass with little repercussions.﻿

In short. This section would not even be here if it was not for myself and a couple others. Also, the vast majority of the work, support and info would not even exist. This is not the first device I've done this for either. I did my part, and more.
[Ornate TrueSmart] kuronosan:
When several MTK developers (who have coded custom ROMs, kernels, and firmwares for MTK devices) tell you that your ROM has issues and you call them wannabes or haters, you really don't deserve any sort of adulation.

Besides, I'm still here providing support. Much of what I've discovered while working with other developers has become commonplace on future firmwares. I don't appreciate being called a "wannabe" or "hater" when calling people out on stupid mistakes.

XDA is not a place for Solid Snakes. It's a place for developers to work together. Not helping others is the peak of asshole-i-tude and accepting contributions to your work while not contributing to that of others is the antithesis of XDA.
[Ornate TrueSmart] xcooling:
Loosers attitude: give up and run away, complain because you were not given enough credit or fame

Winners attitude: would be to make your rom better, keep helping the community as you have done.
[Ornate TrueSmart] kuronosan:
Cool story bro
[Ornate TrueSmart] Lokifish Marz:
So you support lying, theft of intellectual property and copyrights and acting like an 3 year old by calling people names? If that's the case then let me steal his work, improve it and call it my own vs trying fixing real problems like the ability to erase the IMEI with nothing more than a webpage or destroy the partition map with an email. Themes are the least of this devices problems.
[Ornate TrueSmart] speedyink:
Awesome. This device already had a bad rep with the devs for various reasons, then this monx guy swoops in to crush any remaining hope we had. Oh well, I'm thankful for what you guys have done, I actually enjoy my TS because of you guys, and that's all I could have asked for.
[Ornate TrueSmart] kuronosan:
I'm still working on quite a few projects. Stay tuned. They likely won't end up here, but you never know.
[Ornate TrueSmart] speedyink:
Glad to hear kuronosan! I understand if you don't want to release it here, maybe you could PM me where you plan to release it or something? I've been interested in what you've been doing, and you have said some things in the past that sound promising (like news of KK and the like).

Thanks for sticking with it, and again to all the devs for all the previous work that helped us get as far as we are.
[Ornate TrueSmart] death_entry:
Could just not ignore him,,, I only flashed the rom to see what the BT tethering was like out of curiosity (its very slow and useable)... will be ditching the ROM when I can get round to it... been annoying me all week I can't wear my watch has it just drains flat with this ROM....
[Ornate TrueSmart] kuronosan:
I've personally approached monx about sharing work and ideas but he clearly has no intention of doing so; he has not responded but he continues to post in his topics.

That's fine. I'm only interested in continuing to better this watch and I have my own things to work on. As far as battery tweaks, I've managed to stabilize that (one of my users mentioned battery life 4-5 days with regular use) and I've managed to make quite a few gains.

Some of the things I would like to share involve making BT more stable and accessible across all ROMs, but again... he has no interest in sharing.

So while some of you hang from his beard as though Loki is the bad guy here, remember the ROM you love so much came from Loki's work and from the relationship I continue to foster with the CEO of this company.

But hey, no worries. Keep on praising a glorified themer who won't share his work with anyone else.

I'll be back here when I get my hands on the KK build.
[Ornate TrueSmart] sirocyl:
Well, I'm gonna stick to my MotoACTV for a little longer. Planned on buying a TS secondhand, but hardware issues, software issues, and the current bout of drama, are very well keeping me from upgrading.

I understand your (TS devs) positions and motives. I know that there's a reason why you left the development on this device, and I'm glad you've simply quit development, rather than fighting and starting a riot.

However, with nearly all of the developers having abandoned the device, I don't see a good future coming from this.

I was hopeful through the kickstarter phase, and it's a pretty cool piece of tech, but, chances are, Omate will support it better than the community, until someone stands up, starts their own thing, and isn't afraid of getting their work ripped off.

Anyway, thanks for the development it did get, and all the cool things you guys do. If it weren't for you, this device would probably be dead in the water unless the OEM goes above and beyond to support it for a while.
[Samsung Galaxy Mega] ArafNN10:
Hello everyone

I have a galaxy mega 5.8 i9152..i want to root it... after i flash the root file using odin after that the phone is dead

i can't turn it on or i can get it on download mode or recovery mode... i try to use the jig method but not working..

I read some info that you can debrick it using a sdcard and special debrick file

Please help!!!!!!!!!!!!!

sorry for my bad English...

Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] ransabag:
Hello everyone,

I have galaxy s4 i9500 and I know the maximum card I can insert is 64 gb (officialy), but I saw some users over the net whose say they have a card of 128 gb on their galaxy s4, it's possible? I need to flash a kernel or a rom for that? (I'm with omega rom 4.4.2 now).

thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] Lennyz1988:
Usually they say like 64 gb because from the moment they release the phone, there was no 128gb card. So it will probably just work.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Hi guys, I think my Nexus is in bootloop another time...

Now I have not time to see anything, but the recovery is unlocked. . can I try something?

What should I do?

Thanks..
[Nexus 5 Q&A, Help & Troubleshooting] vin4yak:
Not sure what you mean by recovery is unlocked.. Do you mean the bootloader?

Download the factory image from google and flash system, boot and cache img files and reboot. If you're still stuck, flash all img files and you will be up and running.
[Nexus 5 Q&A, Help & Troubleshooting] aramil:
Softbrick? No such thing lol.

See/read here for everything you need to do to reflash your phone : http://xdaforums.com/showthread.php?t=2784527
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
I'm finally back, sorry, I mean that the Recovery works, like the bootloader...

I have not understand you Vin4yak, after flashing the factory image what I have to do?

I have to follow this guide? http://xdaforums.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

And I have to flash the factory image from the recovery?

Thanks
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Factory images are flashed via fastboot

Click link to sticky thread in signature. Then read "adb and fastboot. What is it?" thread. Then you'll know everything and can follow the guide you posted

Although before that, you tried a factory reset from recovery, yes?
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
No, like I said I'm back just now and I'haven't tried nothing, so I have to try the factory reset?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Always the first thing to try if you can't boot.. It wipes your personal stuff off the device which could cause issues.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
I've the TWRP, I've done the wipe all/factory reset, reboot but nothing is changed.

So, I've to follow this guide? http://xdaforums.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273

And what I should do? I see only commands like fastboot oem lock that I already know... or it is just a guide to know something more?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
thats an information thread. Its info so you understand how to fastboot flash. Read it all to understand

You'll want to flash system, cache, boot and userdata.. Fyi userdata will wipe sdcard. Adb pull any data you need to kwwp
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Ok.. however, I've already done the installation of adb, I have to do it another time?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
No. Please try to apply logic to the situation
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
But "adb devices" doesn't match the device...
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
What the hell are you talking about. Its either listed and connected or not listed which means it's disconnected. It doesn't match anything.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Sorry, "match" is not the correct verb, however this is the situation:

"adb devices" in the cmd doesn't find the device, and here says "android bootloader interface", but I can't understand if this says it's connected or not...
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
And you're booted into recovery, right?
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
No, I'm booted into Bootloader, I don't have to flash boot, system, userdata and cache via fastboot?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
You've clearly not understood my thread. Adb only works in recovery. Fastboot only works in bootloader. If you're booted into bootloader use "fastboot devices". Please read the thread again. This time in full.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Mmm, sorry, I maybe jump this part...

So, ok, both fastboot and recovery see the device, now I'm gonna flash boot, userdata, cache and system via fastboot, yes? And then I have to do another factory reset like said in the guide "How to flash a factory image"?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
You shouldn't have to do the factory reset but it won't hurt.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Ok, thanks, now unfortunately I have to go, I'll back in 1-2 hours and I try to flash these things.

I have to flash them in the order of this guide or it's the same?

Thanks again, now I really must go.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
I'm back...

So, I have to flash in an order or it's the same?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Order is not important.
[Nexus 5 Q&A, Help & Troubleshooting] theesotericone:
Just follow the guide. I can appreciate you wanting help but you've been given all the help you need. Follow the guide and profit. If you don't profit then ask some more questions. I'm betting you profit though.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Ok, everything is worked, thanks a lot :)

But I have a question... when the Nexus has shut down, I was importing a backup from Titanium Backup... can it be the cause?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Filesystem corruption perhaps.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Mmm.. and what can I do to prevent this?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
Nothing. Its rare
[Nexus 5 Q&A, Help & Troubleshooting] Wakamatsu:
If you're carrying out an operation of that sort, best to make sure you're power is secure (battery topped up or phone plugged in).
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Understood Root, thanks.

Oh, the last thing, with MultiROM is I have more or less problems?

Wakamatsu, I've already done, but thanks anyway :)
[Nexus 5 Q&A, Help & Troubleshooting] Wakamatsu:
I was referring to the data corruption. If you lose power during more intensive operations, there's an increased chance you can have problems afterwards. That's probably what happen to you in the first place. Good job getting up and running again.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Oh, ok, so during the flash is better to charge the Nexus when changing ROM and things like that?

Ok, I'll pay attention the next time.

And for Multirom? It's better or worse?
[Nexus 5 Q&A, Help & Troubleshooting] danarama:
it's irrelevant. Not better. Not worse.
[Nexus 5 Q&A, Help & Troubleshooting] Giolte_:
Ok, thank you both for your help!
[Sony Xperia ZL] ryanrudolf:
TWRP 2.7.1.0 ported for Xperia ZL.

- based on TWRP 2.7.1.0 yuga

- Renovate M7 theme included, no need for UI.ZIP

- tested working on CM11

- flash using Rashr app

- recovery gets flashed in FOTAKernel partition

- enjoy!

Download link - https://www.mediafire.com/?euawwg3lziv8h93
[Sony Xperia ZL] ryanrudolf:
additional screenshots

additional screenshots.....
[Sony Xperia ZL] coolrevi:
Will this work on Stock Kitkat ROM. with Unlocked BL??
[Sony Xperia ZL] qingz:
Will it work with locked boot loader?
[Sony Xperia ZL] Baron1971:
Is there also a never Version available? E.g. 2.8.?
[Sony Xperia ZL] Baron1971:
No one have an Update? :crying:
[Sony Xperia ZL] juniorhxcx:
First thank you.

Installed as instructed.

However I can not access the TWRP to install Custom ROMs.

I'm using 4.4.4 Firmware Stock Kernel and 292.

Please, I am grateful if you can help.
[Sony Xperia ZL] peekay2n:
Can you please upload your modded twrp 2.8.5.0? Thanks!
[Sony Xperia ZL] Simeon Petkov:
Will it work with lollipop ?

PS: i tried it. Flashed via rashr. Work perfectly.

I would like to get my hands on 2.8.5, because i was able to put files to the phone while in recovery and this is quite important for me.
[Android Q&A, Help & Troubleshooting] stiphen:
any way to shell root any android device to get root access "#" , may be this might have been discussed many times .. I tried lot of ways but none works ..
[Android Q&A, Help & Troubleshooting] wingoku:
Rooting Android Wear?
[Android Q&A, Help & Troubleshooting] stiphen:
i just want to get # instead of $
[Android Q&A, Help & Troubleshooting] wingoku:
I don't understand what you are trying to say. Kindly define your problem.
[Android Q&A, Help & Troubleshooting] vampirefo:
Sure it's called root, To get full time shell root you unpack your boot.img change the default.prop to insecure repack and flash.

Just like below.

vampirefo@vampirefo-GA-MA78GM-US2H:~/Desktop$ adb shell
root@LEAGOO:/ #
[Android Q&A, Help & Troubleshooting] stiphen:
i tried below commands , superuser.apk gets installed and even devices reboots but i still not get root access "#"

adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
adb shell
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adb reboot
[Android Q&A, Help & Troubleshooting] vampirefo:
Try

adb shell

su
[Android Q&A, Help & Troubleshooting] stiphen:
/system/bin/sh: su: not found
[Android Q&A, Help & Troubleshooting] vampirefo:
you have to have su for # to work.
[Android Q&A, Help & Troubleshooting] stiphen:
ok thanks i rooted my device with Impactor
[Android Q&A, Help & Troubleshooting] SeraphSephiroth:
Adbd insecure app also works. In your shell, just type SU and accept the SuperSU/SuperUser prompt
[8525, TyTN, MDA Vario II, JasJam General] gingerchef:
HELP

Hi i am new to the forum, but have used many Pocket PC phones in the past, actually i'm on my forth!

Just got the new MDA Vario II, was loving it until yesterday.....

I receive calls, and when i answer i can't hear anything and neither can the other person. If i try and make a call, idon't hear anything but i know the other phone rings as i've tried my land line!!!!

The problem seems to be happening more and more...

Anyone any ideas? or has this been covered else where and i've missed it?
[G Pad 8.3 Q&A, Help & Troubleshooting] cc2918:
Hello. I've been flashing/installing customs roms all day..

I can't seem to solve my problem. Wi-fi wont connect in any of 4.4.x custom roms(slimkat,paranoid..etc)

however it works fine on 4.2.2, 4.4.2 stock and LRS rom

full packaged rom seems to be only solution for me.

heres what i did

My device came with 4.4.2.

I downgraded to 4.2.2

rooted

used loki/twrp package to install twrp 2.6.3.2

wiped data/cache/dalvik

installed custom rom

boots device fine but wifi wont connect(i do see list of wifi network)

tried following

higher version of twrp(s)

tried 4.2.2/4.4.2 flashable bootstacks

tried different type of roms from infected website

tried flashing custom roms after flashing 4.2.2 + 4.4.2 flashable stock roms

none seems to be working.

=( are there any other steps i need to do?

perhaps missing correct kernels?

thanks in advance.
[G Pad 8.3 Q&A, Help & Troubleshooting] muiriddin:
What model gpad do you have? It looks like a v500. Sometimes a factory reset after ROM install helps. Does android settings show the WiFi MAC address?

If it does the kernel at least detects the WiFi hardware on a basic level.

I do know that slimkat after installing seems to require a reboot for things to settle. However as i recall that was for some of the sensors not wifi. Did you reboot after install?

Also did you set the WiFi region in the advanced part of the WiFi settings?
[G Pad 8.3 Q&A, Help & Troubleshooting] cc2918:
v500

did reset/reboot still doesnt work.

mac address/region information(changed to us/can/europe for test) is there.

i did notice that there is no bluetooth address however i did install many other custom rom.

this isn't the only rom with the problem.
[G Pad 8.3 Q&A, Help & Troubleshooting] muiriddin:
What did you use to downgrade to 4.2.2?
[G Pad 8.3 Q&A, Help & Troubleshooting] cc2918:
http://xdaforums.com/showpost.php?p=52029286&postcount=7

used this. then once recovery was installed.

used http://xdaforums.com/showthread.php?t=2762526

to test and fix my above problems.

are there any v50010b kernel download?

i feel that its something to do with 10a
[G Pad 8.3 Q&A, Help & Troubleshooting] muiriddin:
So the second thread you linked to solved your issue?
[G Pad 8.3 Q&A, Help & Troubleshooting] cc2918:
no i tried to fix but no go.

wifi problem remains.
[G Pad 8.3 Q&A, Help & Troubleshooting] muiriddin:
I am using a newer version of recovery than you are. I will have to look around and see what I did differently if I get a chance...
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] vuvkar:
hi i want to upgrade my phone via KDZ, and after that i got error wParam = 100, lParam = 1010, and updater not responding and i can only close that, after that my phone goes emergency mode, pls help

[R&D Test Tools Log File]

10:32:23 : Launching SW update

10:32:23 : Unpacking KDZ

10:32:31 : KDZ file extraced

10:32:41 : Files were extracted.

10:32:41 : LGMobileDL Load.

10:32:41 : Port = -1

10:32:41 : Connecting to phone

10:32:50 : Check Phone mode = 1

10:33:07 : Phone type check.......

10:33:12 : LGMobileDL.DLL Loading....

10:33:12 : _SetAuthMark Fail

10:33:12 : AuthMark°Ў Б¤И®Ич PhoneїЎ Write µЗБц ѕКѕТЅАґПґЩ!

10:33:12 : _SetAuthMark Fail

10:33:12 : LoadCDMAPhoneData() Error

10:33:12 : _DetachDLL Call

10:33:12 : _DetachDLL Call End

10:33:12 : Param : Path = C:\ProgramData\LGMOBILEAX\Phone\LGP700AT-00-V20d-EUR-XX-MAY-02-2013+0.dz

10:33:12 : Param : moduleDir =

10:33:12 : Param : waitTime = 0

10:33:12 : Param : UsbHighSpeed = 1

10:33:12 : Param : PhoneMode = 1

10:33:12 : Param : BinVersion = V20D_00

10:33:12 : Param : AuthMark = 0

10:33:12 : Call fn_StartUpgrade

10:33:12 : Smart : wParam = 206, lParam = 0

i disabled LG modem, enabled windows enableer
[Optimus L3, L5, L7 Q&A, Help & Troubleshooting] IGGYVIP:
;)

THIS GUIDE IS FOR UN-BRICKING ALL KNOWN TO ME LG Lx PHONES ON WINDOWS BASED COMPUTERS

(Virtual Machine Will Work :) )

THIS GUIDE ASSUMES YOU HAVE DRIVERS INSTALLED

>>>>>FOUND HERE IF YOU CAN'T USE GOOGLE<<<<<

THIS GUIDE ASSUMES YOU HAVE KDZ UPDATE PROGRAM

>>>>>FOUND HERE IF YOU CAN'T USE GOOGLE<<<<<

THIS GUIDE ASSUMES YOU HAVE .kdz FIRMWARE DOWNLOADED

>>>>>FOUND HERE IF YOU CAN'T USE GOOGLE<<<<<
​

1. Plug USB cable to PC

2. Take battery out of phone

3. Press and hold VOL- button

4. Plug USB cable to phone

5. Wait few seconds ... (it should display "Download Mode" on black screen)

6. Put battery back in phone

7. UPDATE YOUR KDZ NOW :)

8. navigate to phone settings and security and preform wipe/master reset (not obligatory but ensures "clean rom" )

​

Enjoy your NEW OLD phone :D
[Miscellaneous Android Development] arnabgharay:
All Google Apps included ,no more need to flash gapps zip

YOU NEED TO KNOW BEFORE YOU DOWNLOAD MIUI

[*]i tried a lot but i cant fix compass bug , any help appriciated

[*]you cant move apps to sd card , its not a bug ,its miui deafut setting

[*]theme and few apps you may see chinies , i cant help with that

[*]only 1st sim is 3g

:cowboy:HEY GUYS I WORK ON THIS ROM FOR MANY WEEK , TO MAKE IT COMPLETELY BUG-LESS YOU CAN JUST GIVE ME A LIKE TO SUPPORT MY WORK :cowboy: