yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
As [MENTION=660462]redpoint73[/MENTION] said .. I suggest to return it to stock AT&T, let the next buyer decides what he wants to do with this device .. just keep it S-Off.

Since you're not on AT&T network .. you have to do a bit more ..

first - flash stock AT&T Marshmallow 6.20.502.5 firmware

second - install 6.20.502.5 RUU

If you don't have any adb/fastboot currently installed on PC, I suggest these 2 drivers - http://xdaforums.com/showpost.php?p=64926362&postcount=4

1. adb installer - choose Y for system-wide and N for drivers

2. install latest HTC USB drivers

Note : you need a Windows PC with USB 2.0

Flash firmware

Download this fw_6.20.502.5.zip - https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU

Put the fw_6.20.502.5.zip in your adb/fastboot folder (if you already have one) or just put on Desktop if you use the adb installer that I mentioned above.

Put your device to bootloader/fastboot mode and connect to PC

Open a command prompt from where you put the fw_6.20.502.5.zip

Run below commands:

fastboot oem rebootRUU

fastboot flash zip fw_6.20.502.5.zip

You'll see -

if failed : FAILED (remote: 90 hboot pre-update! please flush image again immediately)

repeat fastboot flash zip fw_6.20.502.5.zip

fastboot reboot-bootloader

Install RUU

Download 6.20.502.5 RUU.exe - http://www.htc.com/us/support/htc-one-m8-att/news/

Put it on your Desktop for easy access

Right click on it and select run as administrator

Follow the instructions - agree/accept - update, next, next, blablabla until it finish

Done ... you're on stock latest Marshmallow - out of the box state.
[One (M8) Q&A, Help & Troubleshooting] djdigi:
You guys rock, yes I agree as I was going through that guide something didn't feel right. I'm so glad I came here for help. ckpv5, I'm going to follow your guide and report back, thank you thank you!
[One (M8) Q&A, Help & Troubleshooting] djdigi:
ckpv5, your guide worked perfectly. I was spending so much time on this, you literally fixed my phone in 15 minutes.

Sent you a little donation, beer on me =)

Cheers and thank you so much for the expert help!
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
Good to know you solved your problem :good:

Thanks for the donation, highly appreciated :D
[Shield Tablet Q&A, Help & Troubleshooting] jamescable:
OK, so hey guys and girls, I have the nexus 6p and have excellent experience with rooting android....I have actually built my first google stock ROM for nexus 6(shamu) and work on other teams for beta testing etc. In saying all that, I have not strayed away from moto, google, or Sammy software. I am buying a nvidia shield from swappa, but atliitle confused. Is their only 1 nvidia shield tablet? If not, which ROMs are compatible with k1 variant?
[Shield Tablet Q&A, Help & Troubleshooting] jamescable:
Really!!!! 31 views and no help?
[Shield Tablet Q&A, Help & Troubleshooting] Exile1975:
They're all compatible with the k1 is the simple answer
[Shield Tablet Q&A, Help & Troubleshooting] jamescable:
Thank you, but I read a lot about a killswitch....like I said, I know very little about this tablet...is rooting it the same as install drivers, fastboot OEM unlock, fastboot flash recovery twrp?
[Shield Tablet Q&A, Help & Troubleshooting] Exile1975:
The kill switch is a way for Nvidia to kill recalled tablets that have had replacements issued. The original release of the shield tablet had some bad batteries that could catch fire so they did a recall and replaced the affected units. For the rest of your questions I would suggest a lot more reading, although from the first post you should already have a grasp of those concepts...
[Shield Tablet Q&A, Help & Troubleshooting] Deleted member 2943498:
Yep! For root only you can use cf autoroot too. TWRP for the shield tablet is a bit buggy. If you only want to root and don't want to flash custom roms I would not flash it.

And if you need LTE or HDMI video out you must stay away from custom roms anyway. None of them provides them.
[Samsung Galaxy S7 Questions and Answers] javifr:
I want to buy a Samsung Galaxy S7 in Italy, but I will use it in Argentina.

The model code is SM-G930FZWAITV

I´m not sure about nomenclature code.

I know SM-G930F is S7 intenational version and that ITV is the code for Italy, is ok?

What about ZWA?

I want to check GSM, HSDPA and LTE bands and if I can change language to Spanish.

Also I want to know what determines the reception of updates?
[Samsung Galaxy S7 Questions and Answers] NoaKauf:
You flash CSC argentina, will good work
[Samsung Galaxy S7 Questions and Answers] dbarmak:
No need to flash CSC of Argentina. I live in argentina and have the United Arab Emirates version and it works fine without any changes.

(No te preocupes que no tenes que cambiar nada, funcionan todas las bandas gsm,3g,LTE de personal, claro, movistar y podes seleccionar español. Cualquier cosa mandame un mensaje personal)
[Moto X Q&A] lipeztti:
I was actualizing my moto X from Android 4.4.4 to Android 5.1 when the cell phone died and it doesn't turns on anymore. I can't enter in bootloader or fastboot because the battery is dead, just the green led turns on. What should I do?
[Moto X Q&A] sd_shadow:
If issue is a low battery, get a Fastboot cable

see Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools

but if you were installing an update or flashing firmware, it's possible the phone is hard bricked
[Moto X Q&A] JulesJam:
If the bootloader is unlocked and you have a copy of the stock firmware for your device for the bootloader version you are running, you are never hardbricked (unless there is a hardware failure of course).

---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------

Leave the phone plugged in and let it charge for a long time - at least 24 hours. Then unplug the device and try again to get into bootloader mode using the buttons.

It is possible the battery has died on you. These phones are now 3 years old or even older.

Is your bootloader unlocked?

What model do you have?
[Moto X Q&A] lipeztti:
I took my cell phone to the technical support and they said that the motherboard is damaged. But how is it possible?
[Moto X Q&A] JulesJam:
You can have a hardware failure at any time. Please answer my questions:

Is your bootloader unlocked?

What model do you have?

Can you get into bootloader (fastboot) mode

Will the device turn on at all?

Have you had the battery tested?
[Moto X Q&A] asusrox:
Hi, my Moto X just died right now, same issue. I was updating my SW to 5.1 from KK and just turned off. As I plug the phone in my pc, the led just blinks twice and gets disconected, and then conect again.

My bootloader is unlocked, I have a Moto X 2014(XT1097 Victara BR) and I can't get into bootloader nor fastboot.
[XDA Assist] Calsaris:
(Sorry For My Bad English)

my xperifirm Program doesn't show old firmware but i want to download old firmware (for a Personal reason i need old firmware)

i looked other phones Firmware but still have this problem it just show latest firmware

Please Help Me:confused:
[Galaxy Tab 4 Android Development] LGMONO:
Based on T530NUUEU1AND4

Here's an update.zip to deodex your KitKat 4.4.2 zipaligned, rooted, link to Xposed for better performance

How to Install - DO NOT WIPE SYSTEM

1. Place update.zip on the root of sdcard

2. Wipe cache/factory reset

3. flash update.zip in TWRP

4.. Reboot ( wait 5 to 10 minutes )

5. Optional - Installed Xposed and Enjoy the life of freedom

Downloads:

Update.zip

Get Xposed

Please as always leave comment or a thank you. :) HappY FlasHing.
[Shield Android Development] Steel01:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

DOWNLOAD:

Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed

1) Download the latest version from our website on your device

2) Reboot to TWRP

3) Hit Install and tap the "Images..." button in the lower right

4) Browse to the location of the TWRP image on your device and select it

5) Select recovery from the partition list and swipe to flash

OR:

You can find more information and download links on our website.

Direct device link

BUGS:

If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

SUPPORT:

Live support is available via #twrp on Freenode with your IRC client or just click this link.

XDA:DevDB Information

TWRP for Shield Portable, Tool/Utility for the Nvidia Shield

Contributors

Steel01

Version Information

Status: Stable

Current Stable Version: 3.0.2-0

Created 2016-06-01

Last Updated 2016-05-31
[Shield Android Development] Steel01:
Well, I finally bit the bullet and took official maintainership of the Shield devices for TWRP. So, here's the pure upstream release. It's sideways due to lack of rotation support, but it should have every feature any other TWRP supported device does. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
[Shield Android Development] r3pwn:
I'm pretty sure there's a sideways TWRP theme. I recall using it to get it to display properly on molly (Google's ADT-1 Developer Kit).

Have you tried setting the TWRP theme like this? :

TW_THEME := landscape_hdpi
[Shield Android Development] Steel01:
Yeah, the only thing that changes is the aspect ratio, not the orientation.
[Shield Android Development] copota:
Thank you! Thank you!

Just updated to 110, and installed TWRP you posted. All went perfect.

Just FYI, sometimes when I flash a new TWRP recovery, it doesn't take the first time, so I just flash it a few times, then test to see if it took, if it didn't take, I flash a few times more until it finally flashes.

Is there a specific key combo you can use to go right into recovery? Right now, I boot into the bootloader by pressing and holding the back, home and nvidia buttons till it boots into the bootloader, then I select recovery to go into TWRP. Just wanted to know if there's was a key combo to go directly into recovery.

Thanks again for providing and posting the latest TWRP for the Portable!!
[Shield Android Development] WPtE:
Hello, quick question. I have a previous version of TWRP installed and want to update to the new one.

Is it possible to apply the OTA to 110 with this TWRP or do I need the stock bootloader?

If I need the stock one, does anyone have a link to it? I didn't make a backup, unfortunately :D
[Shield Android Development] Steel01:
No need to apply the ota, download the recovery image from Nvidia and fastboot flash blob, boot, and system. You'll lose any modifications to system (such as root) as expected, but that's easy enough to restore.

https://developer.nvidia.com/shield-open-source

But there's no real reason not to update twrp. The older multirom based version has screen rotation, but that's no big deal. And the newer updates have current selinux policies, so they'll be much less likely to cause issues with newer android versions (for those using CM13 and hopefully 14 sometime soon).
[Shield Android Development] WPtE:
Ah, I didn't know nvidia published those files like that. That's actually really great!

I'm all up to date now, including the latest TWRP :D
[Shield Android Development] ManiacDC:
Hmm I tried TWRP 3.1 from the TWRP website and the touch interface doesn't work. Also, 3.0.2 seems to have problems mounting and wiping data?
[Shield Android Development] Steel01:
Meh, okay. I saw a similar touch problem on a local twrp build. I've requested that the build be removed from the official site. I'll look into the problem when I have time.

Haven't had any trouble on 3.0.2 myself. Did you enable encryption or adopted storage in your ROM?
[Shield Android Development] ManiacDC:
Great, thanks!

I didn't enable encryption, and it was the latest stock rom. I'm not really sure what happened. It just seemed to be having trouble mounting and wiping a few partitions on the stock system rom, so I flashed the 3.0.0.0 TWRP from the multirom. I seem to recall that having issues wiping too though. However, now that I've flashed LineageOS onto the system partition, I don't get any errors with 3.0.0.0 anymore. I haven't updated to 3.0.2.0 to see if the errors are gone in that build (nor do I want to wipe anything at this point).
[Shield Android Development] Blash85:
As I wrote in the LineageOS thread, I had the same problem with touchscreen. I was hoping to solve the non working touchscreen problem during Aroma OpenGapps install.. is there any hope it gets solved? I think it would be very useful to be able to choose exactly what to install on the Shield, considering its little system partition.
[Shield Android Development] astuermer:
Hmm, seems 3.1.0.0 and 3.1.1.0 don't work on the Shield Portable. After the first start no touch gesture is recognized. If you connect a USB mouse you can get past this...

But after a new start to the recovery everything you select results in "wipe factory settings" - which I assume you won't :)

PS: Landscape would be nice.
[Shield Android Development] min1968:
I too have this issue. Seems they messed up screen as portrait mode.
[Shield Android Development] Steel01:
I see the problem with touch on the newer builds. Would have sworn I had at least one of those removed due to issue, but it apparently came back. Looking into updating all the internal files for 7.1. Working on testing and fixing that right now. The problem is that the touch screen userspace is trying to start before selinux is set to permissive by twrp. So, I have to make sure everything is labelled correctly and that's causing issues. If I'm lucky, I'll be uploading a test build later today. But as with all this type of work, I can't 100% guarantee anything.

The rotation code no longer exists, it was deemed too slow and hacky. I have to set it up in portrait or not at all, unfortunately.

Edit:

So, not having much luck with making it play nice on default settings. Here's a build with selinux explicitly disabled and touch works as expected. As I have time, I will continue to work on this and get it upstreamed. For the moment, use this 3.1.1 build.

twrp-3.1.1-0-unofficial-roth.img
[Shield Android Development] Steel01:
Finally got around to pushing updates to official twrp. So if you've had issues in the past, please try again. Should be easier to test and fix stuff now that I've got all that pushed.

Side Note: This is fully a 7.1.1 recovery and build. Blasted recovery from N works better than the roms themselves...
[Shield Android Development] Steel01:
Some updates have been pushed for this. 3.2.1.0 has been release as of a few hours ago. If any issues are found, please report.
[Shield Android Development] neg2led:
When trying to flash the 2018-02-11 LineageOS nightly with 3.2.1.0, I get the following error;

Updating partition details...
...done
Full SELinux support is present.
Installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Checking for digest file...
Skipping Digest check: no Digest file found
Verifying zip signature...
Zip signature verified successfully,
[B]This package is for device: roth; this device is .[/B]
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-13.0-20180211-nightly-roth-signed.zip'
Updating partition details...
...done

The flash does not proceed beyond this point - apparently can't identify the device type (see bolded text above). If I repeat the process using version 3.1.1-2 or version 3.0.2.0 it works fine, though.

Let me know if you'd like me to pull any logs etc :)
[Verizon Samsung Galaxy S 4] SalmanJohnson2011:
So I found out I could get root on the latest 5.0.1 Lollipop OF1 update.

I downloaded Wondershare MobileGo and installed it.

1. Once you installed it. You'll need to go into your phone and into developers menu and enable usb debugging. Then, go into security and enable "unknown sources".

2. Open up Wondershare on your computer and plug your phone in. Keep your phone screen on. It'll pop up a warning about having access to your computer. Hit always allow.

3. After that, Wondershare will install it's app.

4. Now, once everything is all connected and running, there's something called "ONE CLICK ROOT" on the main page. Click on it, Hit okay, then let it do its thing.

5. Once it's done, it'll say root successfull!

Now, I don't know if anyone else found this method or not, but if they did, mention them down below. I personally prefer this method over "Kingroot".

Let me know if you guys need any help. I'll include a link for Wondershare MobileGo.

http://mobilego.wondershare.com/

MOD EDIT:

Threads of this nature belong in the General section, not Development. Please refer to the sticky at the top of the Development question titled "Rules for Posting in Development."

THREAD MOVED
[Nexus 5 Q&A, Help & Troubleshooting] CutEar5278:
I am getting wild vary of readings I think the ideal is somewhere between 250 to 350. Sometimes it is very high. Right now I have 750!

I use the same outlet I have not done a rigorous analysis with different outlets. I had problem with the phone charging before and I noticed at 250-350am it seemed to be "charging properly" and if it was too high it was not really charging. and too low it would be too slow.

so what ma reading with the Ampere app are you regularly getting with your n5?

thanks! :good:
[Nexus 5 Q&A, Help & Troubleshooting] CutEar5278:
usage vs charging

Seems that the reading will go up as you use apps.. i see. if a lot of apps are running or processes then more ma will be showing. so it's not the current for charging only showing but usage.
[Nexus 5 Q&A, Help & Troubleshooting] Primokorn:
I have 1180 mA with my wall charger when the battery level is at 55%.

When discharging I have between -180 and -200 mA (I don't touch screen).

865Mb free RAM - 856Mb used - 134Mb cached

42 apps used memory in the last 3 hours
[MDA III, XDA III, PDA2k, 9090 ROM Development] btr94:
For some reason, my WiFi shows up as connecting everytime I turn the unit on. If have too shut the wlaN off and then turn it back on for it to connect. Any thoughts?
[MDA III, XDA III, PDA2k, 9090 ROM Development] life owner:
check the thread about wm6 bugs ..

we are discussing all the problems there
[MDA III, XDA III, PDA2k, 9090 ROM Development] life owner:
sorry repeated
[Nexus 6P Q&A, Help & Troubleshooting] tele_jas:
I love my 6P.... Love the updates and all the custom ROMs, love the front facing speakers too.....But have wanted an "Edge" ever since they were first released.

Today, while at work, someone seen my 6P and asked me a few questions and then said he had a 1 month old 32gb S7 edge he'd trade me straight across for my 6P??? I told him I'd have to think it over and let him know later..... So, what's everyone think?

Reasons I'd keep the 6P

* Custom ROMs galore!! One of the best supported phones are NEXUS phones

* Future proof for updates for several years

* Front facing speakers

>>> I'm a HUGE music lover and check out music equipment (I'm a guitar player) on YouTube quite often

>>> On those days when you just want to lay in bed, the front speakers are great for watching NetFlix without having to cup your hand around the bottom of the phone just to hear it

* I already gave away most of my micro-USB cables and replaced them with USB-C cables - EVERYWHERE

Reasons I'd switch (are the same reasons I love it):

* Custom ROMs -

>>> I get too tied up in the whole custom ROM thing and sometimes spend several hours a day flashing custom ROMs.

>>> I am checking XDA 2-6 times per hour for updates or new ROMs, to the point it affects my work some days (when new ROMs come out while I'm at work). I've tried to control it and block XDA, but I am really addicted to it and have thought about going back to a flip phone sometimes just to free up several hours a day and keep me working when I'm supposed to be.

* Front facing speakers -

>>> Lets face it, the speakers aren't that great (compared to the HTC stereo speakers). Sitting on my desk, 3 feet away I really can't hear any stereo separation and might as well have a single speaker

>>> They really don't sound as good as many single speaker phones

* I wouldn't mind having a smaller, lighter phone....I've got tendinitis from years of playing guitar and the heavy phone sometimes hurts to use for long periods... But after a case it'll be about the same.
[Nexus 6P Q&A, Help & Troubleshooting] jaytv:
Take it. If you like it, ok, if not, you can sell it for more than a brand new 64gb 6p. You can come home for free.
[Nexus 6P Q&A, Help & Troubleshooting] boxcar8028:
personally I would keep my 6p. The Edge is kind of gimmicky. the 6p is pure Android it's what I love about it. I love the larger screen, it's kinda hard to go back to a smaller screen after the 6p. can't stand the Samsung bloatware and the delay updates. I love everything about the 6p the only thing I don't like is the button positioning. I keep accidentally hitting the volume button.
[Nexus 6P Q&A, Help & Troubleshooting] MrMarques01:
Lol, what a thread. Why don't you ask your beauty therapist?

Seriously, it's your decision, why even spam the forum with your indecision? There are enough comparisons between the two phones, just do a bit of googling
[Nexus 6P Q&A, Help & Troubleshooting] tele_jas:
She said an iPhone :(
[Nexus 6P Q&A, Help & Troubleshooting] novanosis85:
I just traded my S7 for the 6P. Can't beat the buttery smoothness and customizations. Believe me, S7 is still laggy even with the reviews praising the touch wiz. I took a downgrade in the camera department, S7 really does have an awesome camera. But the itch to have pure Android and butter smoothness wins hands down.
[Nexus 6P Q&A, Help & Troubleshooting] galaxys:
Toss a coin: Head's it's a Nexus6p or Tails it's a Nexus6p! :D

It's a win-win... ;)
[Nexus 6P Q&A, Help & Troubleshooting] tele_jas:
Yeah, after reading so many reviews... The S7 does seem like the clear winner, but I'm not sure I can live with the crappy single speaker?? And most say the speed/smoothness is better on the 6P, but it's just apples vs oranges on most of it.

I really wouldn't use Touchwiz, I'd use Nova launcher, but I guess I'd sill have the Touchwiz menu's and pull-down.

I know some say "get the S7 and sell it", but I only have one phone and can't really do that.. So I'd be stuck with it unless I got another local deal.
[Nexus 6P Q&A, Help & Troubleshooting] joshpdavis80:
I had an s7 edge for about 2 weeks before I got the 6p. The edge was nice, however I prefer the 6p. Stock android is better than touchwiz. Has the edge been rooted yet? It had not been when I had it. I did not like not being able to block ads in chrome. I returned mine to AT&T and lost out on getting a free TV with it. I also lost out on a $150 bill credit because I returned it. I don't regret it. Keep the 6p!
[Nexus 6P Q&A, Help & Troubleshooting] benleonheart:
You're gonna miss the speakers and the stock Android experience.
[Nexus 6P Q&A, Help & Troubleshooting] krolla03:
The edge is dumb. Its gimicky and has almost no useful use. I had the Galaxy S6 edge.

And most of all the edge is hard as FU*K to hold.
[Nexus 6P Q&A, Help & Troubleshooting] ixon2001:
I had a choice of buying either the S7 Edge or Nexus 6P just a couple of weeks ago, one of the main reasons for getting the 6P over the S7 Edge was updates, Android N will be out end of Summer the S7 Edge will not see it until sometime early next year.