yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Questions & Answers] Rkschunk:
in stock? how did you root?

Rkschuk from MotoG4 Plus (XT1640)
[Moto G4 Plus Questions & Answers] ckkbleev:
It would be hard to tell you how because I used several different How-to articles, but from what I can piece together, I used mfastboot to flash TWRP and after that, SuperSU 2.67. It's on the stock rom.
[Moto G4 Plus Questions & Answers] Rkschunk:
install the TWRP stock again and then go TWRP / advanced / terminal, type the command: echo "SYSTEMLESS=true" > /data/.supersu and then install the super su 2.78.

Rkschuk from MotoG4 Plus (XT1640)
[Moto G4 Plus Questions & Answers] ckkbleev:
I just tried it and it still isn't working.
[Moto G4 Plus Questions & Answers] SoNic67:
Did you use the tutorial that requires to flash a "modified" system? Rooting systemless should never require you to touch the system.
[Moto G4 Plus Questions & Answers] ckkbleev:
I just wiped my phone, reinstalled TWRP and SuperSU and the camera and flashlight seem to be working well. Thanks guys!

UPDATE:

I found my problem. When I edited the build.prop file by adding "net.tethering.noprovisioning=true" to enable wifi tethering, it completely disables both the camera and flashlight. When I remove that line and restart the phone, the camera and flashlight are still disabled, but once or twice I received a "this camera is busy" error. I guess I'll have to do a system restore and start over again, without the hopes of enabling wifi hotspot.
[Moto G4 Plus Questions & Answers] Praveen 054:
Mine s xt 1643 even i rooted my phone... But i didn't checked it even i edited build for Google assistant.... My camera and flash light not working :confused:..

.

I got it back by installing stock rom
[X 2014 General] stardestroyer001:
I have made this short post for those who are looking to increase battery life/reduce the impact of Google Play Services on their Moto X 2014.

For starters, you should be rooted. Amplify, ROM Toolbox, Greenify, and other apps require Root to access their full functionality.

Also, get Xposed Framework.

This guide is by far the best guide I have encountered. Alternatively, if you want to conserve even more battery life, use this alternate guide, which disables location services but also has useful information.

However, if you follow either guide to the tee, you'll find that the Moto Actions, such as twist for camera and Moto Display, cease to function. (I believe this is because the sensors required for their operation are only being polled every 24 hours)

This can be fixed by allowing ALARM_WAKEUP_SENSOR_COLLECTOR to run without restrictions (not limited)

I'm not sure what ALARM_WAKEUP_SENSOR_UPLOADER does, but if you have it restricted and Moto Actions isn't working properly, try allowing it to run freely and see if that works.

I hope this helps. If anyone has further suggestions, please post.
[Google Pixel XL Guides, News, & Discussion] jaythenut:
https://m.flickr.com/#/photos/144261017@N08/sets/72157671743739334/with/30347353185/

Just found this one's look very nice
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
Hello everyone,

I have been seeing a lot of bricked phone help requests coming up lately across the forums here and I was able to fix my 16GB Model using the 32GB .TOT file located in

this thread.

In that original thread posted by [MENTION=4325732]bitdomo[/MENTION], he lists all the files necessary for download. The files he provides are working and I used his method to fix my phone with a variation in the repairing process. Specifically after you flash the 32GB .TOT file provided in the thread.

Download TOT file for your device

Download LG usb drivers

Download LGUP tool

Download 8994 dll for LGUP

Install LG usb drivers

Install LGUP tool

Install 8994 dll for LGUP

Turn off your phone

Press and hold the volume_up key while you connect the phone to the PC with usb cable.

Wait for Windows to install the new drivers

Start LGUP

Either select refurbish (will wipe userdata) or upgrade (wont wipe userdata)

Click on the line where it says BIN file to make the button with "..." appear and click on it then select the tot file.

Click on start

THE MAIN DIFFERENCE HERE IS THAT AFTER I FLASHED THE .TOT FILE, I BOOTED MY PHONE INTO BOOTLOADER AND DID AN ADB SIDELOAD OF THIS OTA.ZIP

After flashing the OTA, I cleared the cache and did a factory reset there in the bootloader menu and the phone is working perfectly.

P.S.: I used a USB 3.0 cable in a USB 2.0 slot on a Windows 10 PC. So, if I were you, I would do the same.

I am back to 7.0 rooted and this time won't be making the mistake of locking the bootloader before flashing stock images first.

PLEASE ASK QUESTIONS! I know this will be able to save a lot of people from buying new phones.

Also, this will require you to have some experience using terminal/CMD and have necessary SDK tools downloaded in order to ADB Sideload the given OTA for the 5X.

P.S.S.: Thanks for everyone who was involved in the original thread posted by [MENTION=4325732]bitdomo[/MENTION]. Specifically, [MENTION=2790198]gee one[/MENTION], who initially provided the 32 GB .TOT files for the H790 and H791 variants.

Edit 1: thanks to [MENTION=1299673]sfhub[/MENTION]
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
It is nice to post your specific info on how to fix the 32GB to 16GB userdata partition sizing issue that arises from flashing 32GB TOT file on 16GB phone.

However, perhaps it would be better to lobby for this info to be placed in the original thread rather than create a brand new one with 95% the same info?

The info is buried in that thread already but should be placed in the first post.
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
First, if i need to provide more credit, please show me how. Also, I used most of his original post, because I could not have done it better myself. However, there needs to be some serious editing in the OP in order for people to be able to successfully unbrick their phones. It took me about 12 hours of researching with much trial and error to figure this whole thing out.

And yes, I usually would never just copy most of the steps. Furthermore, I think it should be sticked as a solution as well because the OT is titled as a request and is out-of-date in a lot of ways.

Apologies...
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
It isn't about credit, you gave plenty of that. It is that most people would find the original post so IMO that is the best place to update instructions. In addition if the info is split, when instructions get updated, there will be inconsistent instructions if things aren't synced.

This is unrelated to your post but

If the post is being update it would be useful to add that people should *NOT* flash the TOT file if they are bootlooping because of EFS corruption due to TWRP 3.0.2-1 restore bug.

If they flash the TOT file, it will lock their bootloader but won't fix the EFS corrupt problem since the TOT file doesn't flash EFS.

With bootloader now locked, it becomes impossible to "zero" out the EFS partition to actually fix the problem because you cannot boot into TWRP since bootloader is locked and you only have stock recovery after flashing TOT file.
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
[MENTION=2060915]briandresstoyota[/MENTION] use this tutorial please. Once you have flashed the .TOT file and are inside the recovery where you can ADB sideload, please let me know. Like mentioned above, once flashed, use THIS OTA AND RENAME IT OTA.zip and sideload it.

Wide cache, factory reset and then reboot system.
[Nexus 5X Q&A, Help & Troubleshooting] briandresstoyota:
Ok I will try this out. I will ping you when I get to the adb sideload phase. You wish me to use the exact OTA you linked yes?
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
[MENTION=6166618]MajorSalvat[/MENTION] to enter download mode, have the phone off with the USB cable plugged into the computer but not into the phone.

1. Hold Volume Up + Power Button while plugging the USB cable into the bottom of the phone.

2. Continue holding the Volume Up + Power Button until download mode starts up.

This sometimes takes a long while...
[Nexus 5X Q&A, Help & Troubleshooting] briandresstoyota:
how do i tell which tot file?

---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------

uhm. my phone was dead. i was gonna boot to recovery to try to figure out what tot to download. Plugged in my phone and it charged and then booted and then went to the welcome screen and then rebooted. omg this phone is crazy.

---------- Post added at 09:03 PM ---------- Previous post was at 08:59 PM ----------

ok well now i have made it through welcome setup and to the home screen. annnnnnd now it just rebooted. I guess i really need to do this recovery.
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
H790 U.S.

H791 International models

...usually
[Nexus 5X Q&A, Help & Troubleshooting] MajorSalvat:
Still don't enter in Download mode. I try to do this many times but nothing. Just show the loading page and 2 seconds after restart
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
And this is with your USB plugged into the computer with the correct drivers and SDK files downloaded and properly installed? Is the USB slot a 2.0 or 3.0? Try to stick to 2.0 slots for this fix.
[Nexus 5X Q&A, Help & Troubleshooting] MajorSalvat:
Yes all drivers installed, my PC recognize the device in Fastboot. It's 2.0 to. I think it's the system not the PC
[Nexus 5X Q&A, Help & Troubleshooting] briandresstoyota:
I held down Vol Up and then plugged in usb cable and phone turned on in Download Mode and then brings up the screen that says Firmware Update but when I start LGUP it says no device is connected.

---------- Post added at 09:38 PM ---------- Previous post was at 09:34 PM ----------

@bardhi92 i noticed that when i entered download mode windows did not install any new drivers.

---------- Post added at 09:45 PM ---------- Previous post was at 09:38 PM ----------

dang lolol now windows is installing drivers three at a time lmao

---------- Post added at 09:49 PM ---------- Previous post was at 09:45 PM ----------

ok well LGUP says unknown model on COM4

---------- Post added at 09:51 PM ---------- Previous post was at 09:49 PM ----------

sometimes i can get to the DOwnload mode screen and it doesn not move on to the "Firmware Update Screen"

---------- Post added at 10:01 PM ---------- Previous post was at 09:51 PM ----------

ok trying on a different usb port (Not even sure how to see whcih is 2.0 or 3.0) now windows is trying to install drivers but it is taking forever and eventually my device turns off from firmware updat emode.

---------- Post added at 10:22 PM ---------- Previous post was at 10:01 PM ----------

ok i finally got it to connect and am currently going through the TOT process. when it is done i am going to boot into recovery and adb sideload the ota

---------- Post added at 10:40 PM ---------- Previous post was at 10:22 PM ----------

Foloowed your instructions exactly and now i get Google logo and then black screen.

---------- Post added at 10:53 PM ---------- Previous post was at 10:40 PM ----------

sideloading the original ota i had been trying to sideload before taking this advice. see if that helps

---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------

oh cool. got a * failed to read command: no error on the load at 89% and now im still in bootloops at the Google logo
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
Has anyone else tried unbricking using this method with any success? Repeatability is important here.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
IMO given what is included in the TOT file, this method no longer makes a lot of sense.

It originally came out because people were bricked but had their bootloader locked so they couldn't flash the factory image file.

Now that Google publishes FULL OTAs, these can be adb sideloaded using stock recovery and locked bootloader.

If it were me, I would first try the factory reset from recovery.

If that didn't work, I would suggest people try to recover from a bootloop with locked bootloader using the FULL OTA and adb sideload with stock recovery.

If you have unlocked bootloader, can also try flashing factory images from bootloader.

If that didn't work I would see if I have the EFS TWRP restore problem (and unlocked bootloader). If so try to get TWRP running and write zeros to EFS partition.

Only as last resort would I try the LGUP TOT file route.

That's just my opinion.

If this was an official TOT file that came from LG with all the partitions, then I would probably be recommending it more often. As it stands, with what is included in this TOT file, it has limited usage.
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
My last resort was this method. Was shocked it worked.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I would just say that most bootloops today that don't get fixed with factory image or FULL OTA are actually hardware eMMC issues (either chip or solder joint), and this method wouldn't fix that.

I am not saying never try it, but I would really make it last resort rather than first resort.

---------- Post added at 05:34 PM ---------- Previous post was at 05:24 PM ----------

I think you meant to say you booted your phone into "recovery" not "bootloader"?

Also had you tried flashing the FULL OTA from recovery (adb sideload) prior to using LGUP and that didn't work?
[Nexus 5X Q&A, Help & Troubleshooting] briandresstoyota:
hey sfhub I am curious what you mean by full OTA. I tried the LGUP method and im stuck in a bootloop.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
In the beginning we only got DIFFERENTIAL OTAs which were basically the monthly security patches. These are something 30-50MB and are only the *differences* from the previous version. They depend on you being on a specific version of software so the diffs can be applied. They are not FULL updates with every partition and all the contents to restore to a complete system.

A couple of months back, Google started letting us download FULL OTAs. These are much larger 700MB-1.2GB, basically almost the same size as factory image. They contain a FULL OS and can flash over anything, Nougat back to MM, MM to Nougat, bricked, etc.

https://developers.google.com/android/nexus/ota

The advantage of the FULL OTAs is they can be flashed on stock recovery with locked bootloader and they won't wipe your userdata partition.

If you needed to flash the factory images before, you needed to unlock your bootloader if it wasn't already unlocked, and unlocking would force a format of the userdata partition.

Also if you couldn't boot into Android and you didn't already have Allow OEM Unlocking set to true, then you were basically SOL because the factory image requires bootloader unlocking, but you couldn't do that until you booted into Android and set Allow OEM unlocking to true, but you can't boot into android because you have a bootloop problem.

Hence that is why this method with the TOT file and LGUP came out, so you could do a full image flash even without bootloader unlocked (in cases where you couldn't unlock the bootloader anymore)

At the time, I didn't even realize it didn't include the vendor partition. If you were on Nougat and just flashed this TOT file, your phone wouldn't boot because it would have the wrong vendor partition and it wouldn't be able to decrypt your userdata. By flashing a Nougat FULL OTA after the TOT file, you'll restore all the original partitions that you actually needed but were missing from the TOT file.

---------- Post added at 05:51 PM ---------- Previous post was at 05:43 PM ----------

From what I read of your problem, I think you have hardware eMMC problem, either chip or solder.
[Nexus 5X Q&A, Help & Troubleshooting] briandresstoyota:
F*** bro you are so right! I was on nougat and did the tot thing and i was screwed. Just sideloaded the OTA i had downloaded from Google a couple days ago and the son of a gun booted right up. This is what i was trying to do last week but adb couldnt read my OTA zip file. Maybe in the process of doing the LGUP i changed up my drivers or something because i just loaded it fine now and everything seems great.
[Nexus 5X Q&A, Help & Troubleshooting] andreak:
Hi guys...in our Italian n5x community some of us are getting troubles from lg assistance... bootloaders are locked and it seems people are not allowed to unlock bootloader anymore, wich obviously means people are not allowed anymore to unlock, root and flash custom roms....

Booting in fastboot mode there is a "secure boot=enabled(no rpmb)'

Why is that possible? Is there any way to bypass this kind of "security lock" ?

Phones are working, not bricked but it's not possible to flash custom roms anymore

Any help or advise would be really appreciated...

So if we try this procedure as described with international tot file (where can we find it?) could this no rpmb issue be fixed? Thanks in advance
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
So it seems as if he decided to flash the .TOT and instead of using the OTA I provided he used a FULL OTA from 7.0?

To be sure, I flashed the .TOT, sideloaded a 6.0 FULL OTA, and then allowed Google to install N through OTA.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I think he flashed the TOT file but things weren't working then he flashed a Nougat FULL OTA to get boot/system/vendor to match up and it booted, however I think he has a hardware problem and it'll eventually go bad again.
[Nexus 5X Q&A, Help & Troubleshooting] ophirharran:
can anyone confirm whether this solves the problem for good?

After first time this happened, phone was replaced by Google, but that was painful and lengthy. :eek:

now have a replaced unit (refurbished, IMEI traces to factory date for Oct'15) - still undecided on the update from marshmallow to nougat.

let's say OTA to nougat has been installed and now bootloops happen

can anyone confirm if after doing the method in this thread that the bootloops never come back again??
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
If you have a bootloop of the type where you have everything stock with locked bootloader, then in the middle of doing something innocuous it just reboots and is stuck in a bootloop, it is likely this is a hardware problem either with eMMC chip or solder joints for chip. In that case, this thread will do nothing for you.

If you were actively flashing custom ROMs, locked your bootloader by accident, playing with different kernels, etc, then this can help you, but you should probably try the flashing the factory image from bootloader or the FULL OTA from stock recovery as those actually contain complete system image.

This TOT file only contains GPT partition table, boot, recovery, system, modem.

It doesn't contain bootloader and more importantly vendor partition.
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
OTA cannot be used on a locked bootloader. Locking bootloader will require flashing .TOT and then a full 6.0 OTA.

Edit: not confirmed for 7.0...
[Nexus 5X Q&A, Help & Troubleshooting] briandresstoyota:
Ok well my device is still jacked so let's not say I confirmed anything.
[Nexus 5X Q&A, Help & Troubleshooting] questionquince:
So, after flashed TOT, did you reboot into system first (to enable adb debugging on the phone settings) or just directly continue to boot into bootloader and sideloading?
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
No. I immediately put the phone into recovery mode and sideloaded.
[Nexus 5X Q&A, Help & Troubleshooting] questionquince:
My TOT flashing is success. But, This happen after I rebooted to bootloader and enter recovery mode
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
Hold Power and then hold Volume Up until the menu opens.
[Nexus 5X Q&A, Help & Troubleshooting] questionquince:
From bootloader or from the blank android screen?
[Nexus 5X Q&A, Help & Troubleshooting] bardhi92:
From the screen in the photo you posted.
[Nexus 5X Q&A, Help & Troubleshooting] questionquince:
Tried many times, but it stuck on Google logo
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I don't understand this statement, maybe I lost the context.

OTAs, both differential and FULL OTAs do flash with locked bootloader.

There are FULL OTAs for both MM(6.0.1) and N(7.0)

Otherwise most people wouldn't be getting the Android security updates nor Android Betas, as most people have locked bootloader.
[Nexus 5X Q&A, Help & Troubleshooting] questionquince:
Succesfully alive

Finally, I manage to bring back my Bullhead alive. Last time i followed procedure in this thread, I got stuck on bootloop. Turns out, it was really hard to enter the android recovery (hold the power button + volume up). Everytime I pressed the buttons, they always bring me to reboot/restart to system and had bootloop. Until one time, It worked, I can enter the recovery through the combo buttons.

After adb sideloading with full ota MHC19Q, my LGH791 16 GB comes alive.

Guys, if you find the same possible problem on your N5X, just follow exactly the procedure from OP. The crucial step, since there's no TOT for 16 GB varian yet, is to sideload the ota zip.

:good::cowboy:
[Nexus 5X Q&A, Help & Troubleshooting] ThisIsSpartah:
Any ideas if Nexus is not able to even boot in fastboot?
[Nexus 5X Q&A, Help & Troubleshooting] :
You said hold power + vol-up... was that a typo? To get into fastboot, you use vol-down. Using vol-up puts you in download mode to start the TOT process. Did you do something different that finally made it work?

Also, before you started this whole process, was your phone able to get into fastboot? able to get into recovery mode? Because I cannot get mine to go into recovery from fastboot.

- DCK
[Nexus 5X Q&A, Help & Troubleshooting] questionquince:
No it is not a typo. There's a difference between normal recovery mode and android system recovery. It goes something like this: www.howtogeek.com/130611/how-to-factory-reset-your-android-phone-or-tablet-when-it-wont-boot

At first i did put my device into download mode, which is by pressing volume up while plugging into usb. After finished the TOT flashing, in fastboot mode I entered recovery mode but it didn't work. I had a red triangle sign with dead android (scroll back few above). Well entering this Android system recovery is a little bit tricky. I tried few times but it didn't just worked. Until one time the system recovery was opened.

Before this whole process, yes I can get my N5X into bootloader, with bootloader locked. But I cannot get into recovery mode from bootloader menu.
[Nexus 5X Q&A, Help & Troubleshooting] :
Cool

Thanks! I'll give it a try tomorrow.

- DCK
[Nexus 5X Q&A, Help & Troubleshooting] jadu45:
I don't how to thank you. I literally cried when I got my phone back. You will always be in my memory stranger. God bless you :)
[Nexus 5X Q&A, Help & Troubleshooting] IonutGherman:
If my phone is unable to enter in download mode, only in fastboot mode and nothing else? I sent it to warranty and they told me that I need to change the motherboard, but I'm sure that exists a solution for it...
[Nexus 5X Q&A, Help & Troubleshooting] jadu45:
Entering download mode; I got that wrong in the first time, don't know about you. Make sure you are pressing only the volume+ key nothing else and connect usb cable.

If you did exactly that, then I guess there is some other solution. Don't lose hope!
[Nexus 5X Q&A, Help & Troubleshooting] IonutGherman:
I am unable to install drivers for my phone :( Windows finds my phone as Android but I cannot install drivers on my laptop and I cannot use anything
[Nexus 5X Q&A, Help & Troubleshooting] jadu45:
Try this:

In the device manager menu right click that Android device and go to update driver, then "browse my computer for update". Then select "let me pick from a list". There should be something with ADB device. Select that. I'm not sure about the exact process. I tried one or twice and my PC detected my phone. Good luck!
[Nexus 5X Q&A, Help & Troubleshooting] rminy:
hey guys,I flashed the TOT file,first question.Should it stuck on google logo or it should reboot or something?second question how should I flash the OTA file?I cant go to the recovery(I mean there is nothing in recovery to flash OTA)what should I do?