yashsingh1/xdaforums huggingface dataset:
[LeEco Le1 Pro Guides, News, & Discussion] Ibrahim Razu:
Facing the same problem here

Some one plz help, I'm facing the same problem here
[LeEco Le1 Pro Guides, News, & Discussion] rhri3:
After you press the vol - and off the ? shos, then hold vol + and off and you will enter recovery mode (if twrp is installed).
[Android Q&A, Help & Troubleshooting] xdarthanonx:
Thanks to [MENTION=9923878]Pantoflat[/MENTION] this has been solved!

The app referred to is Apk Analyzer by Dinostudio8891:

C:\Users\xdarthanonx\Downloads> [URL="https://www.7-zip.org/"][B]7z[/B][/URL] x -otemp dinostudio.android.apkanalyse.apk

7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21

Scanning the drive for archives:
1 file, 2903319 bytes (2836 KiB)

Extracting archive: dinostudio.android.apkanalyse.apk
--
Path = dinostudio.android.apkanalyse.apk
Type = zip
Physical Size = 2903319

Everything is Ok

Files: 608
Size: 6010897
Compressed: 2903319

C:\Users\xdarthanonx\Downloads> [URL="https://docs.microsoft.com/en-us/sysinternals/downloads/strings"][B]strings[/B][/URL] -o -s temp | [B]find[/B] /i "satdigger"
[highlight]C:\Users\xdarthanonx\Downloads\temp\classes.dex: 3370258:/SatDigger/[/highlight]
[Android Q&A, Help & Troubleshooting] rolfkononen:
Satdigger
[G Pad 8.3 Q&A, Help & Troubleshooting] mazazo:
Hello,

I need yo know what to do in my tablet because once i install the room Cyanogenmod 14 i lose my recovery and my play store.
[G Pad 8.3 Q&A, Help & Troubleshooting] l'irlandais:
you may can try install the root apk and twrp apk. then root your tablet and install recovery. download gapps and flash them in recovery. i did this way the olny difference is that i had the play store.

you ll find the root apk link in a tread in this forum
[G Pad 8.3 Q&A, Help & Troubleshooting] Az Biker:
Por favor publica solo en inglés. Gracias..

Please post only in English, Thank you.
[G Pad 8.3 Q&A, Help & Troubleshooting] mazazo:
Sorry, thank you very much
[Xiaomi Mi 5s Questions & Answers] KingApollo:
After I switched to this phone, I miss the root possibilities, I miss playing around with ROMs (I killed my old, really old phone #android 4.3, but it was fun).

Which one is the best option? (I don't want to kill this phone:)).

- The one click rootapps on android?

+ Kingroot

+ Kingoroot

+ Oneclickroot

+ Other...

(And after installing one of them, I will install SuperSU)

- The one click root applications on the pc?

+ iSkysoft toolbox

+ Kingo

+ Other...

- Installing a flash zip with my pc?

- Other options?

I used some of them with my old phones. Which one you prefer?
[Xiaomi Mi 5s Questions & Answers] jigs4wkiller:
The best method is to unlock your bootloader, install TWRP and than flash Magisk
[Xiaomi Mi 5s Questions & Answers] iamnotstanley:
You should only use Magisk (downloaded from the official XDA thread, and flashed via TWRP), and nothing else. Maybe there are some new, opensource root managers but Magisk is the best ATM, and you should stay away from the new versions of SuperSU, a chinese company bought it from Chainfire and now they developing it.
[Xiaomi Mi 5s Questions & Answers] KingApollo:
Really thanks! I didn't know that SuperSu was taken over.
[Xiaomi Mi 5s Questions & Answers] l'irlandais:
first unlock the bootloader, then install twrp (i used adb with my computer) and finally flash magisk.

i tried loads of one click root app and none worked.
[Android Stick & Console Computers General] falciatrice10:
hi all

I want to root my QVIART UNDRO 2 ANDROID TV BOX (with sat tuner) android 4.4.2

this box works with a HISILICON Hi3796Mv100 chip.

its the same box as the AZAMERICA S2010

if you have any informations about it, let me know

thanks
[Android Stick & Console Computers General] Romaric oroumousse:
Good
[Android Stick & Console Computers General] falciatrice10:
View attachment 4398761
[Lenovo A6000/Plus Questions & Answers] Ricky Chrung:
My Lenovo A6000 is bricked. Can anyone help me. Also, my computer said the phone model is Mi 2.

I want to flash the stock rom of lenovo a6000. I had download the stock rom(flash on twrp or cwm zip file).

Thanks!
[Lenovo A6000/Plus Questions & Answers] Mahaadev1717:
Thred available in this section... Read download and try...not big deal...
[Lenovo A6000/Plus Questions & Answers] Ricky Chrung:
My Lenovo A6000 not thing to show...
[Lenovo A6000/Plus Questions & Answers] Ricky Chrung:
It can get in to the fastboot mode...
[Lenovo A6000/Plus Questions & Answers] Ricky Chrung:
It have a led on
[Lenovo P2 Questions & Answers] Sutcliffe9:
I have no HDR option in stock S251 using the stock camera. Can anybody help.
[Lenovo P2 Questions & Answers] onlyvarun.vb:
have you enabled camera 2 api?

if yes then stock camera won't work.

If the camera 2 api is magisk module then you can delete it & it'll work.

If it's system flashes file then clean flash the stock rom.

it'll work...!!
[Lenovo P2 Questions & Answers] holger1308:
in iniro-rom i have the problem, too. When I tap on HDR, the task ist stopped. Camera 2 api is not installed.
[Magisk] ssteward:
I had Magisk v14.0 running on my phone, which was installed using the patched_boot.img method. I had the stock recovery, stock ROM and kernel. But... a Magisk module I wanted to install required me to update Magisk, which I did using the in-app updater. On rebooting, the phone hung with a pulsating Samsung logo. I left it overnight to ensure it wasn't just a very long boot up.

I have seen a number of threads with people with the same solution. A fix appears to be to flash the latest Magisk-uninstaller zip then move back to Magisk 14.0. In order to do this, I flashed TWRP after reading the official thread but didn't swipe right (step 9 of the official guide) to allow system modifications and I didn't install SuperSU. I figured this may interfere with Magisk's systemless root. I did immediately flash no-verity-opt-encrypt-6.0 after flashing TWRP but I was still stuck at the pulsating Samsung logo. Since flashing TWRP, I have tried uninstalling Magisk, flashing no-verity-opt-encrypt-6.0 and reinstalling v14.0, v15.3, or removing Magisk completely. Doing combinations of these in the various sequences as suggested by those who have solved the issue from reading this thread and similar ones.

Should I allow TWRP to modify the system by swiping right and try the steps above again?

Assuming it's my boot.img that's cuasing this, I have tried signing but boot image with Chainfire's .zip that's mentioned here but that zip stopped flashing with an unexpected error.

The last thing I tried was to flash the original unpatched boot.img via TWRP. This gave a boot loop initially but when I reflashed it and immediately flashed no-verity-opt-encrypt-6.0, it progressed a bit further but got stuck at the pulsating Samsung logo again.

This thread shows someone who fixed the issue by installing a custom kernel. I haven't tried that yet. Is this a good idea?

I would be very grateful if you can suggest a way to repair my phone.
[Magisk] teddy0209:
Try flashing magisk 15.3 + no verity stuff as suggested on that thread...
[Magisk] Supreme Genius:
Dont flash unpatched boot images using twrp

flash unpatched boot image or v14 boot image(that you made earlier) using pc ODIN/ any other prefered tool. Just flash the boot.img nothing else or you can use fastboot to only flash boot.img, it works 100% all times,after flashing it should boot normal

then make a new patched boot image for v15.3 from magisk app just as you made for v14 and flash using pc,then it should boot normally

many phones seem to show stuck at boot logo after moving from v14 to v15(especially v15.1 and v15.2) and also some some devices with f2fs storage seems working weirdly with audio mods.
[Magisk] ssteward:
I'm pretty sure that's one of the permutations I tried before but having just flashed those two zips again, after making sure any previous Magisk installations had been removed, I get the same result - stuck at the pulsating Samsung logo.

If someone can tell me what parts of the system the problematic in-app upgrade from v14.0 to v15.0 would have affected then I could perhaps have a better idea of what I need to fix to get my phone starting up again.
[Magisk] Didgeridoohan:
Have you tried flashing your stock boot image or even dirty flashing your entire system with ODIN (as suggested above)? Magisk only edits the boot image, nothing else.
[Magisk] ssteward:
Sorry, my mistake. I did flash boot.img via Odin. It was the original boot.img file that I fed into Magisk v14.0 so it could create patched_boot.img.tar that originally worked. I'm going to try that again now.
[Magisk] ssteward:
That's good to know, thanks. I do have the full system from sammobile from which I extracted boot.img, so could try that if the 'lighter touch' approaches fail.
[Magisk] ssteward:
UPDATE:

After using TWRP to uninstall Magisk v15.3, which restores the stock boot.img, the phone hangs with a pulsating Samsung logo.

Using Odin to flash boot.img.tar (which I extracted from stock ROM) in the AP slot, I get a different behaviour - a boot loop which shows the "Samsung Galaxy S7 | powered by android" screen momentarily before going black and repeating.

So, even with a stock boot.img (assuming I've got the correct .img, which I'm pretty sure I have) and that I flashed it correctly, again, I think I have) then there seems to be more going on than just a corrupted/incorrect boot.img.

What next? A dirty flash of the stock rom?
[Magisk] teddy0209:
Probably try that... Hope it's not a corrupt boot partition...
[Magisk] Supreme Genius:
did you flash the previous v14 patched boot image again using ODIN? this should work

same boot loop problem prevailed on my s7 active and lenevo k8 and flashing the v14 patched boot image and then making new v15.3 boot image gave a perfectly working magisk, although my redmi 3 was showing same boot loop problem and i have to flash the stock rom ( used twrp to restore nandroid backup but boot loop was not solved :mad:)

It seems your lots of permutations and combinations:mad: have damaged post_fs config of the kernel so you have only option left is to dirty flash the ROM.
[Magisk] ssteward:
Sounds ominous. How would I recognise this and fix it?

I don't seem to be able to find the patched_boot.img.tar that I used originally with Odin. I've checked a few different machines and on various SD cards but I only have the unpatched boot.img.
[Magisk] Supreme Genius:
Then you need to flash the ROM , if you got another device then you can make a patched v15.3 image and flash it
[Magisk] ssteward:
I used another phone to created a patched_boot.img.tar for v15.3 and flashed that with Odin but that gave me a boot loop. Trying this again but flashing no-verity-opt-encrypt-6.0 afterwards allowed me to get to the pulsating Samsung logo. So giving up on this approach, I dirty flashed my stock ROM and this worked but I was left looking at a pulsating Samsung logo for a nerve-racking 5 mins or more.

Thank you everyone for your help. I have my phone booting up again!

Now I need to work out install the latest Magisk successfully. If I try using the patched_boot.img.tar method with v15.3 then I'm back to the pulsating Samsung logo. Again. Using TWRP to flash the v15.3 zip gives the pulsating Samsung logo. I did select 'Preserve AVB 2.0/dm-verity. I also tried again with a clean stock ROM install and flashed the v15.3 zip and no-verity-opt-encrypt-6.0, as suggested by someone who'd successfully installed v15.3. I'm at a bit of a loss.

One clue, TWRP couldn't see the internal SD card data (iow /data). I wasn't able to check this option in the 'Mount' menu in TWRP either. I think this points to /data being encrypted. TWRP could see it yesterday, so perhaps I've inadvertently encrypted this. I was careful to uncheck 'Preserve force encryption' in Magisk Manager. I guess now that I've unbricked my phone, I should start another thread for this magisk install issue but any help or pointers to relevant threads that I may have missed would be great.

Thanks again for all your help.
[LeEco Le 2 Questions & Answers] RafaelMelo1:
Hi, how are you? Good morning.

I need help installing TWRP, on my leeco le s3, x626.

I already have a Le max 2, unlocked and with TWRP installed by me, through the tutorials of Yourtube.

But this time, it is not working.

I did the whole process.

Several times, UP TO BRICKEI 2 TIMES on the device, and I came back with the rom stock.

With ADB open, with administrator permission

I already gave the command

Quick boot unlock.

And confirmed that it was unlocked.

More now when you ADB, with the command,

without fast recovery from fast flash twrp.img

Do a count and say that's right.

But when, pressing and holding the Power + Button up a screen does not boot and it restarts, it vibrates normally ....

logo logo below RECOVERY.

More does not carry the TWRP.

What I'm doing wrong.

Note I already tried to change the version - TWRP 3.0, TWRP 3.1, TWRP 3.2.

Nothing happens without default back to Recovery

Help me, it must be such a detail that I'm missing out.

Thank you very much for being able to help me.

And if anyone needs to unbrick a cell phone can talk to me.
[LeEco Le 2 Questions & Answers] onlytanmoy:
Wish i could help you mate.

May I request you to check below thread and see if you can help me?

https://xdaforums.com/le-2/how-to/help-le2-twrp-internal-storage-0-mb-t3737943?goto=newpost
[Moto 360 2015] ghstudio:
If my watch and phone are separated, or one of them loses it's charge, I have to re-pair the phone and the watch. This never happened on my previous Pebble with the same phone....which always just worked. I have the latest updates on both the 360 and my phone. I am completely frustrated with this situation....

Is there a solution, of should I just give up and given that the watch doesn't work with the phone and both are Motorola, should I just avoid all Motorola products in the future
[Moto 360 2015] Pipsname:
I throw my watch in airplane mode before long separation. What seems to be a problem is watch faces with information updates.
[Huawei P9 Plus Questions & Answers] joshxd4:
Hi guys,

it's possibile convert L09 single sim to L29 dual sim changing oem info and firmware and buying a double sim tray?

Someone did it with nougat?

The hardware of p9 plus single sim and dual sim it's the same looking inside.

Thanks,
[Huawei P9 Plus Questions & Answers] xzanium:
I think you can do it with HCU client (without changing oeminfo) but you need a valid IMEI number (I did not try it)
[OnePlus 5T  Questions & Answers] warblad13:
Is OxygenOS's face unlock on any other ROMs out there? If yes which ones.
[Huawei Mate 9 Accessories] Frannny:
Hi,

I want to turn my dumb cover into a semi smart cover = able to switch off and on the screen.

Aparently this can be done with a strategically located magnet in the cover.

Can anyone shed light into where on the flip case I need to add the magnet?

Thanks,

Frannny
[Huawei Mate 9 Accessories] djmvt:
just left from the left soft key (back key)
[Huawei Mate 9 Accessories] dwcasey:
on this flip case, appears on bottom right (when opened) near spine.

https://www.amazon.com/GBSELL-Luxur...35416&sr=8-7&keywords=huawei+mate+9+flip+case
[Huawei Mate 9 Accessories] Frannny:
Thanks guys. I'll try that.
[Huawei Mate 9 Accessories] djmvt:
haha yeah answered to fast: it's on the right on the case, so the sensor is positioned on the left in the phone ;)
[AT&T Samsung Galaxy Note5] redklaver:
Can anybody post the link to the latest update of QJ1? Mine still on QH1.. as i lived outside US region, the Odin files will be best.. thanks before and peace..
[AT&T Samsung Galaxy Note5] huynhlam:
N920A_N920AUCS4EQL1_ATT_USA_7.0.zip

Note : DO NOT USE pit file include
[AT&T Samsung Galaxy Note5] czois:
would this erase everything on phone?
[AT&T Samsung Galaxy Note5] huynhlam:
yes
[AT&T Samsung Galaxy Note5] redklaver:
Is this odin files? Or adb file?
[AT&T Samsung Galaxy Note5] Raihan_Hanafi:
Odin file

---------- Post added at 09:29 AM ---------- Previous post was at 09:27 AM ----------

What a different with the previous version?
[Sony Xperia XA1 Questions & Answers] joyride76:
Hi All,

I'm an happy user of my xa1 g3112 updated with last version Android 7 40.0A.6.175

I suppose after the last update a bug has been triggered and now I'm suffering a battery drain issue

Bluetooth is continuosly eating battery in the listed application is always on top or second place

This is happening despite no devices are connetced

So far that's the list of attempt I've done to fix the issue wihtout luck:

- Reboot in safe mode

- delete all the devices paired

- restore app permission

- Disabled bluetooth scanning

- enable stamina

- as last flag bluetooth processes as not optimized

Anyone has the same exerience, any fix thanks

Stefano
[Sony Xperia XA1 Questions & Answers] simply F:
Hi

You've only to reset your device. You installed an app that drains battery in the background or you've enabled something wrong.

As last chance before resetting cancel the data of Bluetooth on applications settings:highfive:

Wish could be helpful
[Sony Xperia XA1 Questions & Answers] styffmarza:
I have the same problem,

same build but it seems to me that the problem existed before the last update, the bluetooth was used in pairing with the car to play only music.

Are there any solutions?
[Sony Xperia XA1 Questions & Answers] joyride76:
I've bought the smartphone in September 2017 and I didn't had the feeling I had this issue at the beginning.

Is the problem triggered by an update? Or it's present also with stock rom?

Have you the dual or single sim version?

That's really a pain the solution could be wait for oreo or rollback to the factory rom.
[Sony Xperia XA1 Questions & Answers] styffmarza:
Dual sim version

I bought it in December and I updated it as soon as it was turned on. the problem has always been there for me
[Sony Xperia XA1 Questions & Answers] joyride76:
Tried to restore factory setting, issue still present after 4 hours 120 mAh used by bluetooth without any paired device, any advice on how to move forward?

Any foreccast on OREO update? this could be the only one fix
[Sony Xperia XA1 Questions & Answers] Howshall:
Xperia XA1 big battery drain in standby after Android v8 Feb 2019 security updates

Confirm that ever since I received Nov 2018, and then Feb 2019 Android v8 security patch updates, in late Feb 2019. I have been experiencing significant extra battery drain with my Dual SIM Xperia XA1 whenever Bluetooth is enabled.

Currently I'm experiencing this on 48.1.A.2.101 (Android 8.0.0 with 5 February 2019 security patch), but believe the issue started with 48.1.A.2.73 (8.0.0 with 5 November 2018 security patch which I personally received & installed on 26th Feb 2019, Feb security patch then became available shortly after)

Has taken me a while (& I used https://play.google.com/store/apps/details?id=com.gsamlabs.bbm) to track down that I don't believe it's any new or misbehaving apps. And like others here I initially wondered if Bluetooth background scanning (Changed via Settings > Lock screen & security > Location > Scanning) could have been the culprit, but no that's not made a significant difference.

At the moment the only workaround I've found is manually turning on/off Bluetooth from quick actions, but before Feb updates my Xperia had excellent all day battery when in light use, frequently being at 40%+ at end of the day, now with battery drain issue I'm lucky to make 30% by 6pm, often worse!

See attached for screenshot from GSam battery monitor when I was only lightly using my phone, but only switched off Bluetooth between approx 10.30am-1pm today and the slope of battery drain is substantially different!

(I have just recently asked if the developers of that app can add a Bluetooth On/Off orange bar overlay to that graph which would makes things much more definitive to track)
[Xiaomi Mi Mix 2 Questions & Answers] elio321:
Getting a bit obsessed with this device and must own one sooooon!

Just need to source one hopefully in the UK and 128Gb

How many Special Editions have been released ?

Cheers

Mark
[Xiaomi Mi Mix 2 Questions & Answers] scdoyle:
I am aware of three:

- black ceramic unibody

- starck limited edition - same as above but with starck signature on back

- white ceramic unibody

I have the white and love it. It is a thing of beauty.
[Xiaomi Mi Mix 2 Questions & Answers] elio321:
Cool thank you my budget is £450 GBP

Would love the ceramic version either black or white

Think Stark version is above budget having 256Gb

Regards

Mark
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] snoopyghozt:
Do anyone know how to downgrade from the latest marshmallow update on galaxy note 4 to kitkat
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] jam97:
I think with lates boot loader Qi5, you can not downgrade. Otherwise, you can.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] snoopyghozt:
What about downgrading it to lollipop and then to kitkat
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] jam97:
If you are not on QI5, you can downgrade.
[Thunderbolt General] jwillmeng:
How Android Go Can Help Older Android Phones Run Android 8.1 Oreo

https://www.xda-developers.com/android-go-old-android-8-1-oreo/amp/
[Thunderbolt General] n0yxl:
Interesting. It would be nice to see some current development happening for this device, but I think that at this point it would be asking a lot out of a 8 year old device I'm afraid. Still, this is Verizon's 1st LTE smartphone so there might be one or two Devs with enough love in their hearts left for the old Mecha to make something happen. You never know!
[Samsung Galaxy Note 8 Questions and Answers] plop12345:
Title says it all. Is there any known way to have root and device encryption still possible?

Thanks a lot.
[Samsung Galaxy Note 8 Questions and Answers] Jammol:
Not currently. Unless you can trick the device into thinking it's fully charged and plugged in at the same time??
[Samsung Galaxy Note 8 Questions and Answers] Nick216ohio:
I never thought of this question, but good question. So root trips knox to stop encryption? Kinda lame if so.
[Samsung Galaxy Note 8 Questions and Answers] plop12345:
Got it working with the stock ROM in the mean time. Just don't use TWRP to flash Magisk. Keep the stock recovery, Use Magisk Manager to patch boot.img (check tar format in settings) , then flash back via Odin, boot and factory reset. Done.

No luck with any custom ROM yet. Desperately looking for help. Would also pay quite a bit to have someone skilled looking into this. I don't want to keep the Korean ROM of my N950N :(
[Samsung Galaxy Note 8 Questions and Answers] plop12345:
No, flashing with TWRP requires to format data. That step loses encryption.

For some reason it's then impossible with Magisk or pph root to just reencrypt the phone from a custom ROM. It dies with invalid encryption and looses all your data when you try.

It's a bit different with SuperSU. Here it thinks encryption went well and tries to mount it on next boot, but then fails.

From my current knowledge it seems it needs stock recovery to recreate an encrypted data partition that actually works. That's the bit I'm stuck now...
[Samsung Galaxy Note 8 Questions and Answers] Jammol:
On the Snap version, using SamFail gets rid of encryption. There's no way to encrypt for us with root because of the 80% short coming.
[Samsung Galaxy Note 8 Questions and Answers] plop12345:
Ah crap, didn't even think of that issue :(
[Samsung Galaxy Note 8 Questions and Answers] plop12345:
Anyway, at least to me a phone without reliable encryption is not usable as daily driver. I wonder why this gets so little attention. I spend some days now trying to resolve this, but there is not much information out there or I'm not capable to dig it up.

I couldn't even find a clear statement, what it actually is that prevents TWRP to mount encrypted /data on modern Samsung phones.

I known they do their own SOC based hardware encryption, but what is it that TWRP can't get? Does the trusted zone not release the key if a custom binary boots? I really like to understand a bit more on how this actually works.

Thanks
[Samsung Galaxy Note 8 Questions and Answers] plop12345:
Figured it out: https://xdaforums.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493