yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] Alexurso:
Could anyone give your feedback?

We will have update or not for Mi Note 2.
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] kabong88:
i want to flash with pie version, is it ver 4?

if we have version 5 would be nice also, thanks
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] Alexurso:
I left the link on the previous page

This ROM is in my opinion the best for the Xiaomi Mi Note 2.

Very stable, fast ... Besides being very beautiful.
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] filipr13:
The rom becomes very unstable and laggy for me after few days of usage, I love the rom, but the performance issues always force me to switch back to miui :(

anyone else having superb performance at first, but after 2-3 days awful?
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] Alexurso:
Which MIUI are you currently using?
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] Gianluk99:
Dude the developer has stopped updating all the builds he did for scorpio for a long time now...

The Mi Note 2 is even EOL (end of life) from new miui updates, so from a devolper aspect i think it's useless to keep working on it.

Maybe he has a new device or just doesnt want to wok on the Mi Note 2 anymore. Sure it's sad as almost all his roms were relly good especially bootleegers but that's how it is.

If you want something updated for scorpio, the only option is Pixel Experience which is rly good too.
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] jack1969:
You can try lineageos 17.1 based on Android 10, too.

Lineageos is very stable.

And there is mokee os, android 10, based on lineageos.
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] tribual:
Sorry guys, but not read here for long time.

There will sadly be no more updates, as the screen of my phone got broken. So I switched to a new phone.

Sad, but true, was a nice time with the Note 2 and the community here!

If anyone has a broken phone with working screen, ping me, and I will take a look to continue.

So bye bye here...

Gesendet von meinem Mi 9 mit Tapatalk
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] schlubbi:
Which country are you located? Im in China at the moment. I migh find some cheap spareparts.

Depending on shipping cost me might find a solution :)
[Xiaomi Mi Note 2  ROMs, Kernels, Recoveries, & Oth] tribual:
Iam from Germany. Let us talk in pm for more. Maybe we find a solution...

Gesendet von meinem Mi 9 mit Tapatalk
[Google Pixel Questions & Answers] tomatosmoothie:
I got LineageOS installed, restarted to bootloader and locked bootloader.

I can now:

Get into LineageOS Recovery

Boot to LineageOS ROM

I cannot:

Unlock bootloader

Unlock flashing

Unlock OEM from developer options (Option is greyed out)

What I tried, rooting and trying the following adb commands.

adb root
adb shell setprop ro.oem_unlock_supported 1

Got the error:

setprop: failed to set property 'ro.oem_unlock_supported' to '1'

I can only run LineageOS and go into LineageOS recovery and Adb sideload from recovery and install rooting apps.

Help! Want to 'fastboot flashing unlock'

Video:

https://vimeo.com/304615053

UPDATE:

UPDATE: Solution given by the dev razorloves(https://xdaforums.com/member.php?u=614507) the dev who mantains the LineageOS ROM for Pixel details here:

https://xdaforums.com/showpost.php?p=78361157&postcount=32
[Google Pixel Questions & Answers] Archangel:
I am not sure, and I think someone else can chime in but, I have always heard that you never ever relock the bootloader with anything custom for the Pixel. Have you tried the fastboot flashing unlock critical command? I am not sure the exact command but if you Google it you will see. I think thats about your only hope.
[Google Pixel Questions & Answers] tomatosmoothie:
Yeah, I goofed up.

Tried unlock_critical

htpc@linux:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.029s
htpc@linux:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.013s
htpc@linux:~$

What I cannot understand is I have a perfectly working LineageOS ROM and LineageOS Custom Recovery. There should ideally be a way :(
[Google Pixel Questions & Answers] Archangel:
I guess on the bright side at least you have a working phone and a custom rom. But as far as removing it or going back to stock I am not that sure because I believe you need to be unlocked to do that and the system is locked down tight now. I am sure someone else smarter than me will help with an answer, sorry brother wish I could help more.
[Google Pixel Questions & Answers] tomatosmoothie:
Nah man, thanks for looking in, sometimes, when your banging your head against a wall, it's nice if at least someone looks in lol, I would feel so alone if no one replied :) Thank you!

Pondering of flashing the Unofficial LOS 16 which has been created by the same dev as the Official LOS 15 via LOS Recovery. to change things up.
[Google Pixel Questions & Answers] Archangel:
I hearya nothings worse than having a problem and your the only one. Did that on a few phones. I have the Pixel 3 too now and I stay stock with some small edits and my Substratum themes running. I love the custom roms but sometimes they can be a real pain. Yeah I would give LOS 16 a try I guess what do you have to lose.
[Google Pixel Questions & Answers] bafforosso:
Sorry I don't have experience with that situation and hope someone with the knowledge will be able to help you, but in the meantime I just wanted to chime in because you are pretty lucky in your misfortune to have a working phone, usually relocking bootloader while on a custom ROM results in a bootloop 99.9% of the time. So I would advise not tinkering with your ROM but focusing on finding a way either to unlock bootloader or to get back to stock firmware.
[Google Pixel Questions & Answers] tomatosmoothie:
Thanks, I was thinking the same thing, also, the idea was to flash a ROM that would be able to allow OEM unlocking in dev options, but I feel maybe LOS Recovery is not allowing me to unlock.

Also thinking of flashing stock factory image via LOS Recovery.

I will tread carefully though, thanks.
[Google Pixel Questions & Answers] lafester:
No way your bl is locked.
[Google Pixel Questions & Answers] bafforosso:
Hmm yeah I was wondering the same as it would be a pretty serious security bug if a locked bootloader let's a device with LOS boot. Could it be that only the "unlockability" switch was switched off but it did not really locked your bootloader, just the ability to modify it's status?

Don't you get the "open padlock" / "your device software can't be checked for corruption..." screen when you boot?

I think you really should try flashing stock firmware.
[Google Pixel Questions & Answers] tomatosmoothie:
"Your device has loaded a different operating system" is what I get at boot and a "OS fingerprint" below that.

No padlock on the google screen.

I'm waiting for a factory image to download and will try flashing.

LOS Recovery is flashing LOS Nightlies so there is some flashing happening, only question is will LOS Recovery flash a Pixel Factory Image.
[Google Pixel Questions & Answers] bafforosso:
Sorry I mixed things up : use the flash-all.sh (or flash-all.bat if using Windows) script with your device in fastboot mode as described on the stock firmwares download page.

[Correct but not for flashing stock firmware]

No idea, never used, but you should be able to "fastboot boot" into twrp and flash.

Don't flash twrp afterwards as it is known to cause bootloops under some circumstances with the December update, and as a rule of thumb with A/B partition devices just keep stock recovery and use a computer to "fastboot boot" into TWRP when you need to flash something, it is a lot safer (still talking about stock firmware as I don't know anything about LOS/LOS recovery).
[Google Pixel Questions & Answers] tomatosmoothie:
Tried that earlier, didn't work. Trying now.

Advanced Restart is enabled in Dev options.

Restarted to bootloader.

htpc@linux:~$ fastboot boot '/media/twrp-3.2.3-1-sailfish.img'
Downloading 'boot.img' OKAY [ 1.064s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 9.237s
htpc@linux:~$
[Google Pixel Questions & Answers] bafforosso:
Sorry edited my post because I mixed up things, my bad.

No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page
[Google Pixel Questions & Answers] tomatosmoothie:
Yeah, that page says flash unlock is required :(

Hoping, LOS Recovery will flash it, since it's flashing LOS Nightlies.

htpc@linux:~$ fastboot flashing unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.025s
htpc@linux:~$ fastboot flashing unlock_critical
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.034s
htpc@linux:~$ fastboot oem unlock
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.027s
htpc@linux:~$
[Google Pixel Questions & Answers] bafforosso:
If what I suspect - that the bootloader is not the original one but a modded one from LOS and in fact it is not really enforcing the locked state but just locks use of the fastboot unlock/lock instructions or some similar behaviour - then you have to try steps 5. and 6. no matter what is the output of the previous commands.

As you wish, it is your phone but if you don't try we'll never know...
[Google Pixel Questions & Answers] tomatosmoothie:
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.

So the only choice is "adb sideloar file.zip" :(
[Google Pixel Questions & Answers] tomatosmoothie:
Yeah, there is one more catch. You cannot choose a file in LOS Recovery, it is encrypted.

So the only choice is "adb sideload file.zip" :(
[Google Pixel Questions & Answers] bafforosso:
Come on man please, I know you're probably tired of this but I stated that "No recovery needed to flash stock firmware, just use instructions from the Stock Firmware Download Page" and nowhere does it states anything about recovery, adb push, sideload or what not...

Here is a simplification of the part of the instructions on that page you should follow, everything has to be done from your computer with your phone plugged to it in fastboot mode :

On your computer, download stock firmware full image for your device.

Unzip the stock firmware image just downloaded.

Open a terminal and navigate to the unzipped stock firmware image directory.

Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system

P.S.: Forgot to warn but this will delete all your data from your phone.
[Google Pixel Questions & Answers] tomatosmoothie:
Got a Permission denied.

htpc@linux:/media/disk2/LineageOS/Pie/Pie_Official_Factory/sailfish-ppr2.181005.003.a1$ ./flash-all.sh
bash: ./flash-all.sh: Permission denied
[Google Pixel Questions & Answers] tomatosmoothie:
Made a video:

https://vimeo.com/304615053
[Google Pixel Questions & Answers] bafforosso:
You probably just need to execute it with superuser permissions :

sudo ./flash-all.sh
[Google Pixel Questions & Answers] tomatosmoothie:
That was my initial thought as well, tried that!

Also opened the script file and tried the first command

fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img

htpc@linux:/media/disk2/LineageOS/Pie/Pie_Official_Factory/sailfish-ppr2.181005.003.a1$ fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Sending 'bootloader_b' (32384 KB) OKAY [ 1.111s]
Writing 'bootloader_b' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.331s
htpc@linux:/media/disk2/LineageOS/Pie/Pie_Official_Factory/sailfish-ppr2.181005.003.a1$
[Google Pixel Questions & Answers] Sgace:
Have u tried flashing the LOS root package? Usually after optaining root the OEM unlock switch will be able to toggle.

Just a thought.

Cheers
[Google Pixel Questions & Answers] tomatosmoothie:
Thanks, tried that, and the commands in the OP to change to unlock

What's weird is if I follow the LOS instructions to install via LOS recovery using ADB sideload, they all work.

I can adb sideload the LOS Nightly reboot to bootloader from recovery, then choose recovery again and boot to that (the slot thinge) and install Mindthegaaps, it all woks, guess I'm just stuck on LineageOS :)
[Google Pixel Questions & Answers] bafforosso:
Thanks for the video and all details, so your bootloader is definitely locked and LOS spoofed recovery and rom signature to allow boot, frak!

So now we need to find a way to reenable the OEM Unlock switch in your Developer Options as it is the only solution remaining (I'll be glad if someone can prove me wrong here).

I could swear I read somewhere a few months ago here on XDA some instructions that a guy used to reenable the "Allow OEM Unlock" switch but I cannot seem to find them back.

In the meantime let's check the basics :

- Can you wipe cache in LOS recovery? If you can, do so

- Is your phone connected to Wifi (many report greyed out switch when not connected)

- Do you have a SIM card in? If not try with one

- Do you have a Google account set up? If not try doing so

- Did you try clicking on the switch even when greyed out? (found some weird reports of people finding their switch active even if greyed out)

- Seems that sometimes after turning that switch some people experienced grace period of multiple days before they could use it again (source)
[Google Pixel Questions & Answers] tomatosmoothie:
Will wait patiently ;)

Yeah, I'm gonna just setup my phone now, lesson learnt, LOS for life! :D

Thanks for your time!
[Google Pixel Questions & Answers] razorloves:
run these adb commands, then you should be able to enable oem unlock in settings and reboot into bootloader mode and unlock your bootloader.

adb root

adb shell setprop ro.oem_unlock_supported true

adb shell pkill -9 settings
[Google Pixel Questions & Answers] tomatosmoothie:
Thank you so much for replying, I appreciate help from you, the developer and maintainer of the LOS for the Pixel.

I tried the above commands and got the following:

debian@linux:~$ adb root
restarting adbd as root
debian@linux:~$ adb shell setprop ro.oem_unlock_supported true
setprop: failed to set property 'ro.oem_unlock_supported' to 'true'
debian@linux:~$ adb shell pkill -9 settings
[Google Pixel Questions & Answers] razorloves:
open this file:

/data/system/users/0.xml

then change the value for no_oem_unlock from true to false.

then reboot and check dev options. oem unlocking should be enabled.
[Google Pixel Questions & Answers] tomatosmoothie:
[MENTION=614507]razorloves[/MENTION]

You are a genius kind Sir.

Thank you!

adb root

adb shell

nano /data/system/users/0.xml

changed no_oem_unlock from true to false

Saved the change

adb reboot

OEM UNlocking was not greyed out, turned it on

Rebooted to bootloader

fastboot flashing unlock

bootloader unlocked

Thank you so much :) lots of love and good vibes :D
[OnePlus 3 Questions & Answers] Raednor:
Hi guys,I asked several times this question with no luck or answer :

a custom rom this feat working?
[OnePlus 3 Questions & Answers] TNSMANI:
Screen mirroring works in SkyDragon.
[OnePlus 3 Questions & Answers] bumbum.droid:
Works in LineageOS 15.1, too.
[OnePlus 3 Questions & Answers] Raednor:
I tried november builds and the latest one,NOT working,soft reboot every time.
[OnePlus 3 Questions & Answers] TNSMANI:
Means something is wrong with your setup or your phone, nothing wrong with the ROM.

Ofcourse you are not alone in this. I have seen multiple posts that screen mirroring is not working on Pie ROMs including on SkyDragon. But it works on my phone and on others' also.
[OnePlus 3 Questions & Answers] Raednor:
I don't know what you mean,I tried It after formatting and doesn't work on PIE,but works on Oreo OOS after a simple wipe...same story on msm extended
[OnePlus 3 Questions & Answers] TNSMANI:
As I said, screen mirroring works but not casting, in Pie. The dev of Nitrogen OS said that Mircast is not available in Pixel 2XL on stock ROM since Google removed it. He says that Chromecast will work but not Miracast.
[Xiaomi Poco F1 Questions & Answers] robo1337:
Hello there!

I received my Poco F1 yesterday and set it up with all the apps and settings I wanted to use (including WhatsApp and Signal Backups with private keys). Unfortunately the phone didn't survive the day - after less than three hours the screen went black and since then stayed like that. Additionally, it heats up like nothing else whenever it is turned on. I tried holding power, power + vol up etc. - the phone seems to reboot and booting up again but the screen stays dark. As I live in the EU and bought the phone here I contacted the seller, who agreed on shipping a new device, but I still have to send back the old and broken one. That's where my problem begins:

- There's already a load of private data and information on the phone I do not want to give to the seller and everyone who might gets the phone in their hands afterwards

- The phone itself still seems to work. I can reach it via adb, reboot to bootloader, reach it via fastboot and reboot back to the operating system

-

adb shell pm clear xxx

and

adb shell am broadcast -a android.intent.action.MASTER_CLEAR

both yield a SecurityException

-

fastboot -w

yields

FAILED (remote: 'Erase is not allowed in Lock State')

- I do not want to unlock the device, as I don't want to give anyone any reasons to refuse this guarantee case.

Do you have an idea?

Thanks in advance!
[Xiaomi Poco F1 Questions & Answers] SamyakJ:
Your warranty doesn't void on this device. It was confirmed by CEO Jai Mani. If you still concern for warranty you can later relock it. Use this command - "fastboot oem lock". So stay calm and try this.
[Xiaomi Poco F1 Questions & Answers] robo1337:
Hi and thanks for your suggestion! It looks like I don't have any other choice. Could maybe anyone guide me through what happens when (my screen is completely dark after all :( )?

So, I can easily go into fastboot mode by doing a "adb reboot bootloader". I will then use the unlock tool to unlock the phone. Does anyone have an exact idea of what will happen next?

Will it reboot automatically or do I have to do it by myself? Will it stay in fastboot mode?

Will it try to set something up or anything else I should not abort after rebooting? How long will this take approximately?

Will all data be lost by only unlocking the phone or will I still be able to "adb shell" into the system after unlocking (w/o accepting the computer's key again of course)?

In case I got stuck, is there a reliable way to go from anywhere into fastboot mode again (to "fastboot -w" and relock)? Which button combo can I use for "completely turn the phone off" - is it the "3min power button" or the "power button and volume up" one? After "fastboot -w", how does the phone behave? Does it reboot automatically and does it do something after that I should not abort? If yes, how long will it take approximately?

I see that these are kind of difficult questions for people who could see what's going on, but after all it's pretty important for me because I can't ;)

Thanks for your help!
[Xiaomi Poco F1 Questions & Answers] SamyakJ:
First unlocking bootloader takes 3 days. Then after unlocking your all data will be wiped and you automatically boot into the system. If anything goes wrong you can use Mi flash tool to flash miui again in fastboot mode. The most reliable way to boot into fastboot mode is to boot into recovery by pressing volume+ button + power button at the same time and then boot from there. I have never encountered that prob so I can't surely tell about that. Please tell me if it works.
[Xiaomi Poco F1 Questions & Answers] TNSMANI:
As you seem to be interested in only removing the data (not recovering it), the bootloader unlock will wipe your phone completely and it will automatically boot again into the initial Setup screen where the first screen will be asking for the country. At that point simply power off the phone and you will be done. I am saying this from the personal experience of unlocking the bootloader of this phone.
[Xiaomi Poco F1 Questions & Answers] robo1337:
Hi and thanks for your help! The unlocking & relocking process was completely flawless. Vol + Power Up seems to be the "Turn off"-Combo, by the way :)

Thanks again!
[Xiaomi Poco F1 Questions & Answers] diamant3:
nokia c100 doesnt seem to recovery.img to boot recovery only fastboot mode
[Xiaomi Mi A2 Lite Questions & Answers] NICO38:
Hi,

Anyone test an app who work with root device for increase vibration intensity on our MI A2 Lite ?

As same as others users I found that's the vibration of my Mi A2 Lite is too low.

Thanks in advance and sorry for my bad English speaking.

Nicolas (from France).
[Google Pixel 2 XL Questions & Answers] AwkwardUberHero:
Anyone else seen this? Using the stock navigation gestures, swing up on the right to bring up recent applications. I only get one white screen, no recent apps showing.

Pixel 2 XL on Google Fi.

I just opened Reddit, XDA, Gmail and Spotify a second or to before the screenshot.
[Google Pixel 2 XL Questions & Answers] EeZeEpEe:
I use gestures as well and no issues here after the December update.
[Google Pixel 2 XL Questions & Answers] _weber:
I am seeing the same issue.
[Google Pixel 2 XL Questions & Answers] cobrajet7:
Fine here
[Fire General] Gill:
Hello

My Amazon Fire Tablet 7" 16GB which is only two years old. The Tablet works really well. However, it keeps switching off. There is no consistency to this. Sometimes, I am using the device and it goes off. Other times, I leave it on and it switches off. It's driving me mad. Amazon were not at all helpful. I have done a factory reset already. Does anyone have a solution for this problem? Thanks.
[Fire General] DB126:
Likely a hardware problem - failing battery or loose battery connection. Little you can do unless willing to crack open the case (search YouTube for video guidance). Replacement batteries are rarely authentic even when touted as new/original; approach with skepticism. Loose connections (or main board with a micro fizzure) are tough to track down unless obvious.

These inexpensive Amazon gizmos are pretty much a throw-away when they start acting up. Sorry for the bad news.
[Fire General] AmznUser444 Dev:
Can you open your fire tablet to measure the voltage

Requirements:

Amazon Fire tablet

A repairing toolkit for mobile

Multimeter (use for voltmeter)

1. Open your Fire tablet

2. Prepare the multimeter to mean the battery voltage

3. Connect the probe to battery socket to pin 1-2 positive, 5-6 negative

Pin 1-2 red

Pin 3-4 white

Pin 5-6 black

4. The voltage is higher to 3.8v or lower to 3.4, replace the battery with new battery
[G 2014 Q&A, Help & Troubleshooting] aetamachi:
Hello;

i've got a moto xt1068; suck on bootloader unlocked message

i tried flashing it a few times, with success but it still suck on bootloader.

i flashed twrp but cant boot to it; unless i do:

fastboot boot recovery.img

Thank you.
[G 2014 Q&A, Help & Troubleshooting] mini2015:
This was after unlocking boot-loader or flashing custom ROM ?

I remember facing this issue when i rooted device 1st time ...

to resolve this i followed this steps;

1. Unlocked boot-loader

2. Flashed twrp

Now instead of restarting the device, i used to go straight away to recovery ...
[G 2014 Q&A, Help & Troubleshooting] aetamachi:
Nothing changes; it still just stock recovery

i can boot to twrp using the fastboot boot twrp.img

but i get an error 7 installing the zip.

also; i use twrp to connect the phone; delete files from internal storage; but when i reboot i find it there; memory protected somehow? weird.
[HTC Startrek] Wyverex:
Hi there,

So i have a question, which roms with wm6 or wm6.1 are with mobile office?

Thank you for the answer.

regards

René