yashsingh1/xdaforums huggingface dataset:
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) ROMs, Ker] KingOfMezi:
[IMG="https://dl.xda-developers.com/4/5/4/1/9/7/7/King1.png?key=AVHD5KJqHvTqzhgyKdN57A&ts=1530742943"]https://dl.xda-developers.com/4/5/4/1/9/7/7/King1.png?key=AVHD5KJqHvTqzhgyKdN57A&ts=1530742943[/IMG]

[B][FONT="Tahoma"][COLOR="Black"]/*
* I Do not Become Responsible For The Bad Installation
* Now Your Warranty Is Mine, Before Flashing Investigate
* You Decide to Make All These Modifications to Your Device
* Under Your Own Risk, If You Spoil Your Device, I Will Laugh At You
*/[/COLOR][/FONT][/B]

Requirements:

-Bootloader Unlocked

-Activate USB Debugging

-Activate Unknown Applications

-Install Recovery Twrp For Mate 10 Lite

-Only For Free Versions (Dual Sim) And (Single Sim)

-Huawei Mate 10 Lite RNE-L23-L03-L22-L02-L21-L01,LXX,Etc :good:

Huawei Mate 10 Lite-Recovery Twrp EMUI 8.0.0

-Decompress File:

We turn Off The Phone And Enter The Fastboot Mode,We Open The Cmd Window And Write These Codes:

https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk

[B][FONT="Tahoma"][COLOR="Black"] fastboot flash recovery_ramdisk RECOVERY-V2.img[/COLOR][/FONT][/B]

INSTALLATION:

We Copy The Frp_Unlock_For Android 7 And 8 And All Hi6250.zip To The SD Card

We Turn Off The Phone,And Enter Recovery Twrp

-Flash Frp Unlock EMUI 8.0.0 (Delay Around 30 Seconds)

-When Finish, We Give In Reboot System...

Initial Configuration,Initial Start And Enjoy.... ;)​

Telegram Group:

Here Will Support for All Hi6250 Devices:

Huawei Mate 10 Lite,Huawei P20-P10 Lite,Honor 6X,Honor 7X,Honor 8 Lite

Honor 5C,Huawei P9 Lite 2017 And 2016 https://t.me/joinchat/HH00UkNvNQYbZDjlDcrhHw

[YOUTUBE]LOPsqqqQpAY[/YOUTUBE]

XDA:DevDB Information

Tool/Utility For The Huawei Mate 10 Lite

Contributors

KingOfMezi

Chisetdel31260

Neondragon1909

vovan1982

ginnocenti

-KangVIP Framework & Team HRT

-Team Win Recovery Project For P10 Lite

-Huawei Technologies Co, Ltd. 华为技术有限公司

ROM OS Version: Android 8.0.0 Oreo

ROM Kernel: Linux 4.4.23+

ROM Firmware Required: EMUI 8.0.0

Version Information

Status: Stable

Current Stable Version: 2018-07-04

Stable Release Date: 2018-07-04

Created: 2018-07-04

Last Updated: 2018-07-04
[Huawei Nova 2i (Mate 10 Lite / Honor 9i) ROMs, Ker] KingOfMezi:
Downloads

Frp Unlock EMUI 8.0.0 https://mega.nz/#!6FxwXQ4T!-pfJaLqWVtLiUDi7-RMZm6J-EZU7wQ8VDE50eDXZruI

;)
[X 2014 Q&A, Help & Troubleshooting] fer_cabgar:
Has anyone fixed that phone's random shutdowns even replacing the battery with a generic one? I want fix that but idk if a generic battery can fix that shutdowns at <30%

I'm have a Xiaomi mi a1 but I'm still love this phone.
[X 2014 Q&A, Help & Troubleshooting] HebaoTM:
I've been suffering with this problem forever now. Actually I just registered to this forum looking to solve this.

What I know so far from my experience & what I've read from brazilian foruns:

-Replacing the battery doesn't fix the problem, maybe gets the % of the shutdown a little down for a while

-Calibrating the battery also doesn't work

-Simply resetting to factory version neither

-Mine will shutdown no matter the %, sometimes even with 90%, so I assume it's lying about the real battery level

-Opening the camera app is almost guaranteed to cause a shutdown, even more if I try to take a pic or film a video. Other apps that take pictures might work properly though

-Switching between the apps too much, conecting to wi-fi, accessing files, waking it up after a long hibernation are also causes of shutdowns for me, so I guess processing too much makes it die

I still don't know if the cause is a hardware or software issue. I mean, my phone has been through some falls, many different chargers & cables (some fake), hasn't received any updates in a long time, nor has been reset. I think it's probably the battery circuit board (is this the correct name?), but if someone has a solution, please let us know.

Also I'm about to root and try to mod something for myself, see if something works.
[X 2014 Q&A, Help & Troubleshooting] renzs:
[MENTION=7486136]fer_cabgar[/MENTION]

[MENTION=9295974]HebaoTM[/MENTION]

Actually the problem is the battery and the CPU. Whenever the CPU draws current and the battery voltage drops to below 3.0V, the phone shuts down.

Replacing a new battery would fix this but the "new" original battery is suspect because it was all made in 2014, so that's why it doesn't solve the problem

What I did was, I rooted my phone and used "Kernel Tasker" from Google Play to bring down my max cpu from 2.5 to 2.0 and also using this app can change the governor at a specific battery % automatically.

For example at 40%, I set the governor to Powersave. So at 41% I set it back to Interactive.

So now it's auto and my phone doesn't shut down anymore. :)

You can experiment with what battery %, which governor and what MHz works for your phone.
[X 2014 Q&A, Help & Troubleshooting] aBixler:
Bringing down max cpu didnt help for me, i had to change the battery to fix it :(.
[Galaxy S6 Q&A, Help & Troubleshooting] Anass KD:
Hello Guys , Im Accidentally Make Wipe For EFS And NVM Without Making A Backup, And All Phone's Sensor Has Stopped To Work , And Network Too . So Please Someone Help Me , Or Make Backup Of SEC File In Z3X Box .Thanks For Advance

SM-G920F / SM-G920P
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Colossus96:
hey guys. it hasn't been long since i bought the fire HD 8 2017. it was running good and all. i used it even at noon. but when i wanted to use it again at night the touch wouldn't work. if i shut down the tab and open it after sometime the touch would sometime work and after a few seconds it would stop working. i tried factory reset. still not working. any suggestion?

i don't think the touch is broken. cause it works sometimes. any suggestions?
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] billyt1:
Ive got a HD 10 7th gen, got alittle wet and this happened to me I was able to pop the back off, watched video on youtube bout it getting it off, I was able to remove the battery tray to get to the strip that connects mother board to screen , which runs under the battery tray, held on there with like 9 torx5 screws. cleaned up connections. also cleaned up connections on the cameras one of them had a little corrsion on the connector from getting wet . Slapped everything back together and turned it back on and the screen became responsive to touch again for a few minutes then stopped working again. so popped the back off again. This time I took mother board off to inspect it better,didnt really find anything. put mother board back on. then removed battery to inspect the strip again. This time I took the strip off which is double sided sticky taped used a knife to get up under the tape to help assist it off.re positioned it alittle then reattached the strip. Then I screwed the battery tray back down with only 2 of the screws, the middle ones. Turned it back on all works good. im guessing maybe where the strip was tapped down the battery tray was putting alittle pressure on that strip.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] billyt1:
\/ \/ \/ \/ \/
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Colossus96:
I did not have any water damage or anything like that. if i shutdown the tab for couple of hours (4-6h) and start it again the touch works for couple of minutes and slowly it becomes unresponsive to he point completely unresponsive. I thought it might be digitizer problem. but if it's a digitizer problem then the whole touch wouldn't have worked right?
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] billyt1:
You would think . Seems to be a common issue with the digitizer. I watched a video on YouTube where a guy had the hd 8 and had a blow dryer heating the screen. He says it fixed his unresponsive screen. Seems like it should still be warrantied if you hadn't had it that long,seeing that's it's a hardware issue.mine got pretty wet so I know mine warranty was long gone. That's why I didn't care to bust the back off mine plus had the plastic tool to do it already
[Android Q&A, Help & Troubleshooting] gnubster:
I found this MHS800L on the shelf cleaning the guest room. I activated it as a verizon line of service. I can see the wifi AP and password. I can connect to it. I can see the status page 192.168.1.1.

I cannot login. This requires an admin password. I also don't know the answer to the reset-admin-password security-question. The manual laughably instructs changing the admin password is easy: simply enter the admin password and... yeah, not so helpful. The manual has similar inanity for reset to factory defaults.

The are 2 exterior buttons shown in the FCC photo gallery for FCC ID XHG-R800. One is power. Neither alone nor in combination seem to result in a factory reset.

Verizon wireless support was as useful as expected. The could not remotely reset it either.

I care because it acts as wifi AP for about 20 minutes before dropping the connection. I want to tinker with settings.
[Android Q&A, Help & Troubleshooting] ceholland2:
Leaving the Jetpack powered up, remove back cover and hold down the "reset" button, recessed in one of the holes, for 15 sec. Let it fully boot and connect to the Jetpacks Now Default "SSID" using the Now Default WiFi password displayed on Jetpack screen. The Now Default "WIFI Password" IS ALSO the "administrator" password used to access and change the Jetpack settings.
[Amazfit] Pasanen927:
Hi all,

In Amazfit app I have selected km in units settings. All distance inormation of my running workouts are shown correctly in km in the app.

But when I start run activity in the watch the distance is shown in miles in the data screen. Also pace is shown as minutes/mile and not minutes/km as I expect.

Watch sw version is 2.3.4.0.

Any ideas how to see km instead of miles during running activity?
[Amazfit] nhedgehog:
Sounds like a bug in the ROM. Guess you have to wait for an update.
[Amazfit] nasosal:
Is it the caption 'mileage' that makes you think it is in miles? Metrics should be denoted in Km since you have selected this in the app. I have exactly the same version Stratos intl 2.3.4.0 and everything is shown correctly.
[Amazfit] SteffenBerlin:
I was wondering the same. For me all is fine.
[Amazfit] Pasanen927:
Thank you for your answers. It is not caption ’mileage’. It is really showing only miles for distance and pace, not kilometers. Also altitude is shown in feet and not meters. Seems like settings in app do not have effect in watch. And in watch there is no way to change units.

But when I sync running workout from watch to app it shows kilometers in app. Any ideas what to do?
[Amazfit] nasosal:
You mean in the watch you log a running activity of 1 mile and when sync to the app you get 1.6 Km?
[Amazfit] Pasanen927:
Yes that is right.
[Amazfit] SteffenBerlin:
Internally it is always metric, just the display is imperial. Like it is with all other modern devices.

---------- Post added at 12:07 PM ---------- Previous post was at 11:56 AM ----------

Contact their support:

http://bbs.huami.com/forum-41-1.html

It requires a WeChat account for registration.

Or use the US support form.

https://us.amazfit.com/
[Amazfit] Pasanen927:
But how to change display to metric? It has to be possible somehow. I want to see the distance and pace in kilometers when I’m running.
[Amazfit] SteffenBerlin:
It is in kilometers. If factory reset does not help contact the support.
[Amazfit] strangera:
I had the same problem on my first run, regardless the fact that everything in the app was set in kilometres. So try restarting the device, and also you can go to run -> settings -> more settings -> auto Lap -> 1 km and also activate the notification for laps (so even if it is in miles, you will get notification on every km).

So I did that and on my next run it still says "mileage" but the numbers are in kilometres not miles. I am not sure that the auto lap setting has anything to do with the info, or it was just the restart, but it doesn't hurt to try. ;)
[Amazfit] Pasanen927:
I have tried restarting the device, factory reset and started running activity several times but nothing seems to help. I tried your Auto Lap tip but Auto Lap seems to be for miles as well. At least it shows Auto Lap (mi).

I found instructions from Amazfit web page for changing units in watch setting but this option is missing at least from my watch. I have now sent this problem to Amazfit support and waiting for answer.
[Amazfit] strangera:
:( Hopefully they will offer some-kind of solution.

BTW I know it is kind of dumb, but have you tried switching to miles in the app, restarting and then switching to kilometres again?

PS: I also don't have the Units option in the "Common" section of the watch.
[Amazfit] Pasanen927:
This one solved the problem. Switched to miles in app, restarted watch, switched back to km and restarted the watch again. Thank you very much for your help!
[Amazfit] colaglas:
Thank you. This also solved it for me.
[Amazfit] jkjelds:
My watch shows MILAGE but messures in km is that surpose to be like that see photo

ibb.co/ma6ZB9

https://ibb.co/ma6ZB9
[Amazfit] endriklos977:
That's normal, it's just the title. Same for me at least.
[Amazfit] jkjelds:
Ok great thought that should change to kilometers or distance or something. Milage usually refers to a measurement of miles not distance in general.
[Amazfit] jkjelds:
I have asked Amazfit to change this is exy update let's see if they do.
[Amazfit] Toja80:
How I fixed it

Just got "Amazfit Stratos 3" few days ago, set km and kg in the app, however the watch still showed miles insted of km (on the app it was km, but not on the watch). Tried switching from kg to imperial, reseting the watch, etc. - nothing worked. HOWEVER then I found how to fix it. So here it goes: Open on your watch Settings>>>Data sync (it showed that my Data sync was set on Manual sync - so I tapped it again. Was asked to enter my Wi Fi password - did it). The watch started syncing - and in 15 secs. everything was fine - it started showing km insted of miles. Pretty obvious if to think about it now :D
[Huawei Mate 10  Questions & Answers] elderap:
Personally, yesterday came a update via ota for the mate 10 and then I updated the device. When it was the night he started to lose the signal of the routers, there is a time as in the image that is with the wi-fi connected and no network, then back, there it is in that of falling and coming back. I did a factory reset today and it worked fine during the day, when it was night in the same situation, did it again, has anyone ever had something like that?View attachment 4542714View attachment 4542715

Enviado de meu ALP-L29 usando o Tapatalk
[8525, TyTN, MDA Vario II, JasJam ROM Development] dmj1973:
Hi,

I had the following issue recently with bootloader:

http://xdaforums.com/showthread.php?t=375685

Thanks to all those of you who replyed.

Well I now have some further info but the problem is slightly different. The fix for my problem last time seemed random, I hooked up to my pc and the phone started booting fine.

So I have been using my phone fine for X number of weeks, no changes software adds updates or anything applied.

I have been using SPB Backup (A+ s/w) to do nightly scheduled backups, followed by a reboot. Two nights ago I found my phone on the bootloader screen !!

I hooked my phone up to my pc ready to re-flash it, and switched it on (the phone). Low and behold the phone booted fine. So off I trundled with a "working" phone.

This morning I woke up to a bootloader screen ! As a side niote the phone is on charge all throughout the night so as I get no issue during backups.

I hooked my phone up to my pc and switched the phone on and voila, it booted. So I set about doing the mtty.exe tasks listed in the above post. I ran "info 8" as suggested in the above thread and my output was identical (barring checksum values) to that described here:

http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader

Nothing strange that I could see and when I ran "task 2a" it appeared to do nothing.

I have re-flashed my ROM (Schaps 4.31) and the flash worked fine except when it re-booted, it went to bootloader. A quick phoen switch on with it hooked up to the pc via USB and it booted fine.

So quick summary:

Reboot of device causes bootloader screen to appear. Hooking it up to PC via USB and switching it on allows normal boot and the phone is fine then as long as it doesn't reboot.

Anyone have any ideas how I can fix this problem ??

ps Sorry it was a long post, thought I had better explain everything!

Dave

HARDSPL7 Olipro 2.10

HERM 300 - T-Mobile MDA Vario II

Schaps 4.31
[8525, TyTN, MDA Vario II, JasJam ROM Development] dmj1973:
Someone else has the same issue on this thread:

http://xdaforums.com/showthread.php?t=381279

But, I think I have solved my problem (not sure if it is permanent) by powering the phone off and on. Not resetting, just a simple power off. I spoke to a colleague who said the way it shuts down is different to soft reset (makes sense) and I haven't powered my phone off properly for a long time.

I have tried soft reset a couple of times since doing this and it hasn't gone to the bootloader screen once.

Maybe this is the simple fix.

I will keep you posted.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dmj1973:
My fix didn't work.

Can someone give me some idea what I should see when I run "task 2a" in mtty ? I ran it and it just gave a blank line and then went back to the prompt.

Help
[8525, TyTN, MDA Vario II, JasJam ROM Development] ultramag69:
might be dumb question but did you try reinstalling hard spl? might fix. also I would try to reflash to stock rom. wouldnt hurt, then flash to rom of choice. Cheers....:)
[8525, TyTN, MDA Vario II, JasJam ROM Development] ultramag69:
as for mtty it will flash up the bad blocks and tell you if its repaired or not. if there was no response then it means there were no bad blocks...
[Android Q&A, Help & Troubleshooting] Bahamut23:
Hi, everyone. I've successfully rooted several Android phones in the past, but this one's got me stumped. Has anyone successfully rooted this specific model, and if so, how?

I have a J1 mini prime, specifically a J106M. It is running Marshmallow 6.0.1 with a pending update that I've paused. I was under the impression the bootloader would be unlocked since it's not tied to a carrier. I now assume it isn't because I've tried:

kingoroot, kingroot, iRoot, towelroot (doesn't work with modstring codes either), latest framaroot (device not vulnerable to exploits error), framaroot 1.5.3 (same error), chainfire (causes soft brick bootloop, but has since been restored).

I can't even figure out how to verify if the bootloader is unlocked for sure. I tried using ADB. cd fastboot command simplay restarts the phone, and fastboot oem unlock command my phone or just sits there saying "waiting for device."

When I boot the phone holding down the volume, home, and power buttons, it brings me to a blue screen that I believe is Odin mode. Others seem to get a different screen that has the bootloader info right there.

It's been a few weeks since I've had time to mess with this. I'm pretty sure that's everything I attempted.

To verify, I have developer mode on, OEM unlocking on, debugging on, allow unknown sources on.

Other specs:

Baseband version : J106MUBU0AQF1

Kernel: 3.10.65-11653963

Build: MMB29Q_J106MUBU0AQF2

Thanks in advance to anyone who can assist a semi-noob. I've never posted on a forum before, and I'm not usually one to ask for help, but I'm out of ideas here lol.
[Android Q&A, Help & Troubleshooting] chankk0101:
Hello Bahamut,

Are you familar with the Odin tool flashing Samsung firmware? If yes, there is a universal root method Magisk root. There are two ways to root using Magisk:

1. install a TWRP recovery (flash by Odin) & install Magisk Root using TWRP recovery

2. Extract boot.img from the firmware; modify it by Magisk apk; flash the modified img by Odin.

Both ways successfully rooted my Samsung J3 Pro. I've google search for a while & see firmware/TWRP are available for your device J106M.

You should study Odin, Magisk before you go ahead.
[Android Q&A, Help & Troubleshooting] Bahamut23:
Thanks. Somewhat familiar, I was saving that as a last resort out of apprehension that I completely brick the device lol I used Odin when attempting the chainfire files.

I forgot I had downloaded TWRP at one point, but I must be missing something because it appears to be a catch 22 as TWRP was asking for root access in the first place to perform this function. Is there a work around such as using a PC version instead of the app or am I just way off base here?
[Android Q&A, Help & Troubleshooting] chankk0101:
If TWRP recovery has a problem, you could try method 2 which involve Odin flashing only.
[Android Q&A, Help & Troubleshooting] Bahamut23:
Unfortunately, the Odin flashing is how I wound up soft-bricking it twice and decided I'd need assistance on this model. I was hoping someone could walk me through it with the specifics, but I guess this isn't a very popular phone.: :(
[Android Q&A, Help & Troubleshooting] itsmefaisal:
I have about 5 new NeuTab N9 pro. It has Android 4.2 which is kind of old. That tablet is pretty good. Can someone help me with how to install Android 6 (if not at least 5) on that tablet. I tried on one and rooted it. but i couldn't find a custom rom for that. I used dr.fone to root it. It discovered device as "SMARTIC w51090wvga". I searched for ROM with this term as well but couldn't find anything. I would appreciate if anyone can help.
[Samsung Galaxy S8+ Questions & Answers] david050613:
hola a todos tengo un problema con mi s8+ sm-g955f, le instale twrp y root con magisk pero al reiniciar me apareció este mensaje " only official released binary are allowed to be flashed" mi celular no enciende que a quedado inservible. necesito ayuda por favor.:llorando:

Auto Translate :-

hi to everyone I have a problem with my s8+ sm-g955f

I installed twrp and root with magisk but when I rebooted this message appeared "only official released binary are allowed to be flashed"

my cell phone does not turn and its bricked. I need help please
[Samsung Galaxy S8+ Questions & Answers] SacredDeviL666:
Hi,

Kindly go through our forum rules before posting/creating new threads in future.

Thread moved to Q&A section of that device.

Thanks
[Samsung Galaxy S8+ Questions & Answers] paolol788:
Try downloading the official version from here https://xdaforums.com/galaxy-s8+/development/rom-galaxy-s8-t3749444 and then flash it using odin.

Descargate la versión oficial desde el link que puse más arriba y luego instala mediante odin (en el mismo link esta el tutorial para hacerlo).
[Samsung Galaxy S8+ Questions & Answers] david050613:
hello good afternoon, I want to know a method to get root in my sm-g955f because when flashing the updated stock room to the latest version of android I do not see the OEM option.

hola buenas tardes, quiero saber un metodo para poder obtener root en mi sm-g955f ya que al flashear la room stock actualizada al la ultima version de android no me aparece la opcion de OEM.
[Asus ZenFone 4 Max Questions & Answers] Celludroid:
Hi! I'm very much interested in pro video recording camera apps so I was wondering what Camera2 API support level the Asus Zenfone 4 Max has. Can someone who has the phone install the free app "Camera2 probe" and post a screen shot of the test results here? Main thing is the "hardware level support category", hoping for either "Full" or "Level 3" but my guess would be "Limited" ...

Cheers!