yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Q&A, Help & Troubleshooting] jsgraphicart:
I just had this happen to me a little while ago. My tablet turned off with the battery not even close to empty and couldn't get it to turn back on. I could get into recovery but not the OS. I tried flashing different things but it kept having issues. I tried leaving it in recovery mode to drain the battery all the way. Then plugged in the charger while it was off and let it charge up again. I flashed a rom again and I got it to turn back on. Everything seems to be back to normal now. But I really don't know what exactly fixed it or what caused it. I was flashing some older ROMs on it when it happened because I wanted to go back to Marshmallow. So, sorry I don't have a real answer but those are some things that I tried. It could be early signs of a bad battery but I don't know for sure
[Nexus 10 Q&A, Help & Troubleshooting] tglaria:
Well I could't enter recovery ao I just let it drain its battery, after some days I plugged the charger, the battery started charging and it booted.

So... I have no idea what it was, but now it's working again.

Yes, I'm guessing the batttery is dying so I'm starting to look for alternatives.

I guess I'll just go for an iPad, dont know what other tablet could be a good replacement for this one.
[Nexus 10 Q&A, Help & Troubleshooting] jsgraphicart:
I've read people replacing their battery and fixing the issue. Could be an option.
[Nexus 10 Q&A, Help & Troubleshooting] tglaria:
I'm evaluating that too, but the tablet is feeling old anyway.

It feels slow
[Nexus 10 Q&A, Help & Troubleshooting] jsgraphicart:
I agree. There's not really any other Android tablet that I think is a good replacement though. I like the size of the Nexus 10 and wouldn't want anything smaller. I thought about the Nexus 9 but even that has issues with running the latest version of Android. I guess tablets are just going out of style.
[Google Pixel 2 Questions & Answers] iridium7777:
For background, I have Verizon pixel 2 and am using a Mac.

I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)

So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.

So -- What are the steps I should take?

1)uninstall magisk from magisk manager?

2)delete magisk manager?

The above will unroot me, correct?

3)Do I push the stock boot image file onto the phone?

4) do I have to repush the latest OTA walleye image and zip file onto the phone again?

5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?

If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.

I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.

Thanks
[Google Pixel 2 Questions & Answers] mcfroah:
Proceed with Caution

I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.

My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.

My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.

My suggestion would be to:

1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with

2. contact Google support on your phone and see if they would replace it

3. wait for an established method to unroot the pixel 2 here

Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.

Note sure this is exactly what you were looking for, but hope this helps you.
[Google Pixel 2 Questions & Answers] iridium7777:
:(

Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
[Google Pixel 2 Questions & Answers] mikeprius:
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.

So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.

Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.

I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.
[Google Pixel 2 Questions & Answers] iridium7777:
[MENTION=5665963]mikeprius[/MENTION] -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.

at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.

(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
[Google Pixel 2 Questions & Answers] mikeprius:
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already
[Google Pixel 2 Questions & Answers] iridium7777:
[MENTION=5665963]mikeprius[/MENTION] you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?

i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
[Google Pixel 2 Questions & Answers] amajamar:
Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.

Is that correct?
[Google Pixel 2 Questions & Answers] mikeprius:
Just flash the stock images. It will auto reset.

Again, don't mess with anything just flash stock images, then go from there.

Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.
[Google Pixel 2 Questions & Answers] iridium7777:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).

1) download the latest ADB tools from google

2) download the latest factory Walleye image

3) unzip files from 1&2 into a common directory

4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]

5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide

6)type " ./adb reboot bootloader"

7) check that your device is still connected by typing "./fastboot devices"

8) type "./flash-all.sh"

===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====

9) check that your phone is connect to your computer by "./adb devices"

10) type "./adb reboot bootloader"

11) check your devices is still connected by "./fastboot devices"

12) type "./fastboot flashing lock"

===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======

side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
[Google Pixel 2 Questions & Answers] asad_23:
hey there. what is the command suppose to look like? every combination I try gives me an error:

first, I don't even enter the Fastboot command the same wayit given me an error:

Asads-MacBook:~ asad$ ./fastboot devices

-bash: ./fastboot: No such file or directory

so I try this: Asads-MacBook:~ asad$ fastboot devices

[serial #]	fastboot

these are all the errors I get:

Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021

Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh

./flash-all.sh: line 21: fastboot./: No such file or directory

...

Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh

./flash-all.sh: line 21: ./fastboot: No such file or directory

...

Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh

fastboot: usage: unknown command ./flash

...

Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh

./flash-all.sh: line 21: fastboot./: No such file or directory

...

how is the command suppose to look that I can edit it the right way?
[Google Pixel 2 Questions & Answers] Rukbat:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)

You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.

Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
[Google Pixel 2 Questions & Answers] asad_23:
yayy! that worked!

so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.

so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.

thanks!
[Google Pixel 2 Questions & Answers] Rukbat:
Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)
[Google Pixel 2 XL Questions & Answers] equlizer:
im on the latest january patch (Thats when i noticed the issue more) and now my fingerprint rarely works. Ive tried cleaning the sensor with a mild soap and a good rinse and its good for half a day. I've tried deleting the prints and re doing them but most of the time it wont even read my finger period!

Anyone else with this issue? Should i go back to december?
[Google Pixel 2 XL Questions & Answers] C5Longhorn:
I have a stutter with mine but it still works. I imagine Google will address in an upcoming release. Also, mine is not related to the Jan security patch.
[Google Pixel 2 XL Questions & Answers] phyl0x:
still on december, works super inconsistently. half the time it doesnt recognize and i get locked out and gotta do the pattern unlock. the other day i tried to reset the finger prints and that UI would tell me the sensor is dirty...but its not. its kinda annoying.
[Android General] Dimitrico:
Here are some recent models which are supposed to have Symbian OS 1.0 and in fact are based on android 5.1. Available on my local store ( Portugal):

https://www.worten.pt/smartphones-e...f5-bless-cork-edition-32gb-light-cork-6430341

https://www.worten.pt/smartphones-e...bile-kf5-bless-cork-edition-dark-cork-6430357

As we know symbian is somehow extinct and yet there are some sparks here ...
[Android General] Dimitrico:
IKI MOBILE KF5 Cork stands for Portuguese Cork phone

It turns out that the main new about this phone is actually using Portuguese Cork in this entire rear and in the front panel ( up and down bezel of the screen).

Source:

https://www.leak.pt/iki-mobile-kf5-cork-edition-o-poder-esta-na-cortica/
[Nexus 5X Q&A, Help & Troubleshooting] GuestK00164:
So I flashed both AICP and ABC January 8.1 ROMs today (one at a time) using 2 different unofficial OpenGApps packages. After setting up the ROMs (re-install backup from the cloud option), I noticed that I was unable to activate the Say 'OK Google' any time in the Google Now app. When I opened the section in settings<voice the switch quickly moves to the off (left). Underneath it says that this is unavailable in my language (UK English - hence the grey not gray in the heading btw!).

I tried many many solutions from Google, clearing data etc but nothing worked. I have since reinstalled stock January 8.1 firmware and it works fine. I re-installed from backup in the cloud option like before.

What is going on? Has this happened to anyone else? Can you offer a solution?

[EDIT] - I tried a different third GApps package (unofficial BeansGApps). Problem solved.
[Nexus 5X Q&A, Help & Troubleshooting] euler_santos:
Hi am2012

I have exactly the same problem. I've tried everything (except changing the gapps).

Which BeansGApps have you installed?

I only found this file to download (BeansGapps-NoGAssistant_arm64-8.1.x-unofficial-December.zip), but "NoGAssistant" is strange...

Could you post the link from you downloaded ???

Thanks...

EDIT - Thanks a lot am2012. It's finally solved!!! I intalled the BeansGapps file ( BeansGappsMini-arm64-8.x.x-unofficial-Feb2018.zip ) from the AndroidHostFile site.
[Nexus 5X Q&A, Help & Troubleshooting] petie2106:
i use aroma gappes from nezorflame [GAPPS][ARM][ARM64][8.1] Unofficial OpenGApps builds for Android Oreo.
[Nexus 5X Q&A, Help & Troubleshooting] GuestK00164:
Sorry, I was at work. Yes, the BeansGApps work well.
[Nexus 5X Q&A, Help & Troubleshooting] Beejis:
Do you have a link to the gapps because I can't find an Oreo 8.1 beangapps.
[LG V20 Questions & Answers] tony052034:
Hi, all

I just flash the twrp in the normal way in my US996,

and it turns out cannot get into twrp.

What is the issue when I flash it??????:confused:
[LG V20 Questions & Answers] pistacios:
You probably rebooted into the OS instead of rebooting into twrp after flashing it. You must reboot into twrp using the Volume down and power button sequence after a battery pull.

See this post:

https://xdaforums.com/v20/how-to/v20-us996atn-factory-unlocked-boot-twrp-t3726279/post75004120
[8125, K-JAM, P4300, MDA Vario ROM Development] Cphil1:
Hey guys,

I'm having a bit of trouble with my phone since early this afternoon.

It seems like there's some sort of static or shock bouncing off words when someone is talking to me on the other end. What could be the problem??? I mean it was working perfectly fine yesterday...

Thanks for your help.

Phil
[Samsung Galaxy S5 Neo Questions & Answers] Nuggethead2003:
Hey internet...

I have an Galaxy S5 Neo (SM-G903W) and i rooted it. So i then wanted to go back and unroot it. I usually do that by flashing its own ROM. When i was doing that the cable disconnected from the phone and the stage was at preloader ( or boot loader I'm not sure). So after that it showed me that the software has been damaged. I was like :victory: i didn't brick it. So then i tried to go in download mode and it let me but then just turned off and wouldn't turn back on. I searched on the web for help and i tried building a usb jig ( still working on that;) ) but they didn't help at all. I'm gonna take it to a shop tomorrow to ask someone what's wrong with it. Any suggestions?

More Info

Used CF Root method

SM-G903W

Serial # :RF8H80D1JWT

Regards, A.G
[Samsung Galaxy S5 Neo Questions & Answers] drunx:
remove battery 30 seconds, push cable on PC and PHONE wait 30 sec, after 30sec put battery back, and open volume down + home + power , work?
[Samsung Galaxy S5 Neo Questions & Answers] Nuggethead2003:
About that,

when I took it to the shop the guy told me that its not bricked, the battery is damaged. so I went and replaced the battery and flashed my rom and it booted up and charged but it started heating up. it was at 16 percent when suddenly It went to 0 and turned off. Right now its charging but I don't know what to do about the phone.

Any Help?
[OnePlus 3 Questions & Answers] Reploid:
hello

i have a problem with my one plus 3

first of all i can access to the bootloader and the menu of the sideload

( it has : install from internal storage, install from adb, wipe data from cache , advanced and exit)

the phone wasn't root properly when it has nougat ( i saw this when i installed and execute super su ) ,

i installed and flashed recovery stock and twrp ( the most recent file)

but i forget root & unroot the phone , so i think it could have traces of the root ..

( for this reason appears dm verity is not started in enforcing mode and may not work properly ?)

on the other hand i can't enter on the twrp recovery ..

it appears the dm verity alert and it doesn't let me enter to the recovery , when i choose recovery the phone loads the dm verity again and later i'm in the menu of the adb sideload

what should i do ?

i bricked definitely the phone ?

thank you so much
[OnePlus 3 Questions & Answers] Sir Mohd:
I believe this problem happened to me before

try with blu_spark recovery it should work fine

https://xdaforums.com/devdb/project/dl/?id=27655
[X Style (Pure) Q&A, Help & Troubleshooting] hometech99:
64GB USA XT1575.

Unlocked bootloader. Loaded TWRP 3.1.1.

Loaded AICP 10/8/2017, and OpenGapps mini.

No root; No Magisk.

Functioned fine.

Did dirty upgrade to a November version.

Phone had been glitch since in function, and reboots.

It has deteriorated to reboots and never finishes animation.

I cannot get the phone off, then to bootloader.

If I disconnect battery, wait a few hours, and reconnect:

I cant connect the battery and quickly hold power and vol down and get bootloader.

I get warning Boot loader unlocked screen, then an AICP loading animation that never ends.

If I hold in power button, it reboots to the same scenario.

Even holding in power/vol down during process wont get to bootloader .

What would deteriorate phone into not being able to get into bootloader, but phone is not hard-bricked with no boot at all?

I need to get to TWRP so I can fully wipe this phone and whatever is causing all of this.

Any ideas?

Do we have an unbrick "loader" for the sdcard like the XT1572 folks do?
[X Style (Pure) Q&A, Help & Troubleshooting] Optimusman:
IDK about the unbrick tool, but I have had a constant boot up, turn the phone off and it quickly reboots again. For me what worked is all about timing! I power the phone off and as soon as the screen powers down I hold power and volume down until bootloader screen! It takes some time to get it right on time, but it's worked for me in the past on my moto x pure edition. I'm stock 7.0 now but the issues occurred running custom roms, so really the same situation. Good luck and hope you get it. And I hope you have a backup to restore once you get into twrp?!?!
[X Style (Pure) Q&A, Help & Troubleshooting] dzidexx:
"If I hold in power button, it reboots to the same scenario.

Even holding in power/vol down during process wont get to bootloader ."

On bootloop:

Hold power key only, when screen goes black - hold vol- only. It should go to BL screen.

AICP doesn't work at Nougat modem(radio/baseband).

You need to flash MM modem or reflash full Stock Nougat and stay on it.

[MENTION=6014979]hometech99[/MENTION]
[X Style (Pure) Q&A, Help & Troubleshooting] hometech99:
I never went ota 7.0, root, or Magisk.
[X Style (Pure) Q&A, Help & Troubleshooting] dzidexx:
On bootloop:

Hold power key only, when screen goes black - hold vol- only. It should go to BL screen.

/It always work, sometimes it's hard to find the right moment - vol-/

Go to twrp, wipe all and restore or flash last good version.

---------- Post added at 06:45 AM ---------- Previous post was at 06:44 AM ----------

@hometech99

Why didn't you ask in aicp thread?

---------- Post added at 06:49 AM ---------- Previous post was at 06:45 AM ----------

Here you wrote that you updated to stock N:

https://xdaforums.com/showpost.php?p=75009801&postcount=129

AICP doesn't work at N modem.
[X Style (Pure) Q&A, Help & Troubleshooting] hometech99:
I have 3+ of these phones. MY personal one works fine . This is a different unit of mine with this problem that was working fine before.
[X Style (Pure) Q&A, Help & Troubleshooting] hometech99:
Fixed--one of the issues (others reported also) with later AICP is cant charge phone. We had that issue with this phone also.

On a hunch, I went to my Moto X Pure graveyard basket, and took out another battery, and put it in.

Viola--I can get into boot loader. The original battery must have deep-cycled so bad, it was dead, and even plugged in, cant get to bootloader.
[Huawei Mediapad M3 Questions & Answers] notwo:
Hi everyone,

I can't find move to sd option on my tablet (Huawei Mediapad M3 lite 8" (32/3GB)).

Android version - 7 / EMUI - 5.1 / Build CPN-L09C210B003

Can i move without root? if so, please help me. I just bought 128GB sd (class 10).

Thanks in advance!