Database Info

Poor battery life since upgrade

Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?

richport29 said:
Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?
Click to expand...
Click to collapse
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p

zilian28 said:
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p
Click to expand...
Click to collapse
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.

PantsDownJedi said:
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.
Click to expand...
Click to collapse
Actually I'm on ICS rooted. But I know that if you wipe data and cache on JB, unfortunately ur gonna loose root. =/
I read people saying that there is a file that if you clear its data, everything gets back to normal and the battery drain stops. I just don't remember which one is. Do a little search here at the forum that you will find. =]

Thanks for both replies; the answer and the instructions.
I'm about to take the leap into the uncertainties surrounding an unlocked boot-loader, I think. Its been inevitable at some point, I guess...

It turns out that I'm one of the incredibly lucky ones. It wiped my internal sd but su was unaffected. All my rooted apps, except for a modifiaction to build.prop, a backup of build prop, and the su binary, were simlinked into root from a folder in data which I can restore from the tarball I'de made. The symlinks are still there, as was the modification to build.prop which meant I had no buttons at the bottom of the screen to start with. Perhaps because of this; no extra apks detected or something, and with the supersu.apk on data. I don't know if having the reinject root option of supersu previously checked mattered or not. In any case, bootloader still locked and everything wiped. Now I have to put it all back to how it was but that was a given, either way.
This had nothing to do with the rootkeeper app btw. When I installed it, it still had the same settings as prior; didn't have re-insert root or anything.
Sorry for posting a useless comment since I don't know what made my situation differant than what other people have had happen, keeping the binary but losing proper file permissions on it from what I had read last night, but I'm happy that it worked out for me and telling my wife would be futile.
Also, I cleared cache and did a wipe data/system restore... twice. The first time, I made it most of the way through the initial Android setup and it popped me back a few selections; opting not to enable to turn on Google+ and then the screen flickered and it pulled me back to entering my Google account again so I powered off and did the clear cache and wipe again. What luck!

Bringing this thread back. Lately I've been getting some poor battery life on my maxx HD. I used to be able to get through the day with around 50% battery left at the end of the night. Now that number has been steadily decreasing over time. Does the recovery method mentioned also wipe my apps? I would love to finally root the phone to remove all the crapware but everything seems to be for the 925 and not the 926.
Sent from my DROID RAZR HD using Tapatalk 2

[Q][HELP] I lost my IMEI! can everybody help?

*D821 (E) - hammerhead
*KTU84M
*HW version: rev_11
*bootloader version: HHZ11k
*baseband version: M8974A-2.0.50.1.13
*carrier info: NONE (is this wrong?)
*signing: production
*secure boot: enabled
*lock state: locked
#I didn't touch this phone's system, still original.
my story:
so it's been 3 weeks since I bought my phone. I was happy with it, nothing was wrong.
a week later, the 4.4.3 came out, I updated it, and nothing was wrong too.
until last night, I turned off my phone, curious to see how the Nexus 5's recovery look like,
I pressed (volume down + power), and I noticed that it enters FASTBOOT mode. and I just learned, navigate with the volume buttons and select with power button.
NOTICE: I'm already familiar with things like this, I was in the Galaxy W forum and Galaxy SIII mini forum. *yes lol I came from Samsuck
so I selected recovery mode and enter it.. I saw the android logo there, the healthy one, not the murdered robot with a red triangle on it.
I saw nothing but that logo, I pressed volume up button and the text showed up. I navigate down with volume down button, until it was down at the "wipe cache partition", I wanted to go up to reboot my phone, but I realized, the up button just a switch to hide or show the recovery text, so there's only one choice, press the power button, *if I press the power button, I wipe the cache because it selects "wipe cache partition"*.
and then it writes "wiping the cache", I was confused why it was so long, until I decided to reboot with holding the power button.
NOTICE: it is strange to wait sooooo long for cache wiping. I know this.
the system turned on. I'm not sure if the cache wiped cleanly, I'm afraid it will make the system error. so I decided to change my runtime from ART to Dalvik, so the cache wiped out and built again, strange process that took only 64 apps to optimize, that before it was around 110 apps. and then after reboot, I decided to go ART again to saw how many apps that optimized, LOL it was again, 64.
I reboot my phone again, and wait the reception, LOL strange I got no signal in my home *usually full*.
NOTICE: the signal has already gone after first cache wipe.
somehow I go to About Phone, Status on the Settings, and I found out the IMEI is UNKNOWN. I tried to check it with *#06# and it shows nothing.
I repeat the process how I get to the recovery and try to wipe cache, and it said, "error: can't mount /cache".
so I think the cache was gone?? I look to the "Explorer" app *the one who makes the root version too (Root Explorer)*, well the cache partition still there.. LOL
MY QUESTION:
1. am I having a defective Nexus 5? or there is a bug?
2. my IMEI lost, I have 2 expectations: my EFS/IMEI is truly lost, or the system just can't detect it? how can I know?
3. I saw a thread that tells me Nexus 5 doesn't have EFS partition backup, so where does the EFS located?
4. if I follow you guys, unlocking bootloader, rooting and etc. can I make my phone's state default again? *I don't mean fix this thing, just go default*
5. most important thing, HOW CAN I GET MY PHONE BACK TO NORMAL?? *peace bro
please help, right now I'm trying to reset my phone as soon as my backup finishes.
thx

I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.

There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^

vin4yak said:
There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^
Click to expand...
Click to collapse
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.

BirchBarlow said:
I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.
Click to expand...
Click to collapse
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.

anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway

IvanKurnia said:
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.
Click to expand...
Click to collapse
Strange indeed. Yeah, those errors are common. Just try wiping cache multiple times. If not, factory reset the device.
IvanKurnia said:
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.
Click to expand...
Click to collapse
Since you're responsible for this mishap, I would certainly try to fix it myself if I were you. Wiping cache/factory reset is the only thing you can do with a locked bootloader. If that doesn't fix it, the phone's hosed!
IvanKurnia said:
anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway
Click to expand...
Click to collapse
ADB is used whilst you're in Android OS/custom recovery. You first need to unlock the bootloader, flash/boot a custom recovery and then flash the supersu.zip to gain root. I'm not sure what purpose it will serve in your situation though??

this happened to me too. and I waited for the the wipe cache operation for 15 minutes. After a forced reboot the phone was not connecting to the cell network, had a 1970 date and gave various google errors. I went back to recovery, noticed the comatose android and the missing cache partition messages but again I selected wipe cache and this fixed it. It took just a minute or so to create and format it. After the reboot the phone was fine. phew...

This problem happens when the cache partion is not formated properly. You can't take screenshots either, right? You should try to format the cache partition again, and again until your phone becomes normal, or unlock bootloader and flash the cache.img from the stock images. You can find all the instructions about unlocking bl and flashing cache image in the sticky posts of the general forum.
Tapatalk-kal küldve az én Nexus 5-el

bootloop and no recovery

Good day.
Thanks fore reading my post.
I had root on my phone like for 3 or 4 months. everything was great and all. I did not dwell in any ROM installing or playing with the firmware.
But I am not sure what I did that this happened.
When I restarted my phone, I experienced everything until the Logo faded to the rotating circle(loading). And it stays there. Always.
I did check on many sites and it seems to be a bootloop. I tried going into recovery, used every button combination possible(I have only 3 and also tried and for my phone and for others to work) and I can't.
It just continues normally and to the position I explained before.
I have a Vodafone Smart 4 Max and even though I want the fix for my phone, I know there are other users that also experience/experienced this problem on different phones.
Might there be a way to fix this?
Thank you for your time
EDIT:: I managed to enter in recovery mode and tried a hard reset of the android. The situation is still the same, the bootloop remaining

Go to bootloader and flash factory firmware with fastboot

I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)

andreinit said:
I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)
Click to expand...
Click to collapse
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)

minimale_ldz said:
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)
Click to expand...
Click to collapse
Hm, I know what you are saying. For me to enter in recovery mode though, I needed to do the following.
1). Fully shutdown the phone for like 30 seconds
2). Volume UP + power button until the first logo with android appears
3). Let the buttons go and I enter
The problem is that adb and fastboot don't see my device at all. I have been tweaking with the drivers for so long, thinking that may be the cause, but I have no results.
And I can use the backup thing to flash a new rom? It requests an update file though, not an image(a zip file)

I think this is about your phone, maybe it will point you in the right direction:
https://www.youtube.com/watch?v=bKHEZbj4NHo

They are figuring out firmware installation on a similair model here: http://forum.xda-developers.com/android/help/stock-rom-vodafone-888-t3002958

Reset and Stuck on "Checking for updates"

Hi guys, I did the recovery dance and my phone is now stuck on "Checking for updates" at the beginning after wifi verification. Tried resetting a million times and nothing works. So I got adventurous and downloaded a stock ROM, read about the adb sideloading and tried to do that but got this error about invalid signature or something.
So my questions are, how do I make my phone run again? I don't want to mod or anything I just want it to run as a normal phone since it's for my little daughter to use for her games.
Is there a way to make it run again? Do I have to download the original ROM? Where is it? I've tried all Lenovo and Motorola sites but can't find them. Ok, now let's say the original rom doesn't exist, I don't care, I want to make it run, so please help me and tell me what ROM should I download and how to install it. I don't care if it has virus or rootkits, the phone won't be used for anything but playing games, it doesn't even have a sim card.
So, in short, let's make my phone run again, whatever it takes, please.
Moto G3 - XT1540 - 2015 - 1GB RAM

One more thing, here in Venezuela we have the slowest connection in the whole world, so downloading one gigabyte of rom takes a whole day. Could that be a possibility that "checking for updates" actually is checking for updates and taking forever?
Should I leave the phone "checking for updates" for 24 hours at least? Last time I left it for 6 hours and nothing changed. And WHY THE EFFING EFF Android doesn't let us know what is doing and telling us some progress at least so we don't wait like idiots for a EFFING phone that probably is doing nothing?
Sorry, had to vent.

https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
This link will help. Make sure you download the correct rom for your specific device and follow the instructions to the dot.
LostInTheDarkness said:
One more thing, here in Venezuela we have the slowest connection in the whole world, so downloading one gigabyte of rom takes a whole day. Could that be a possibility that "checking for updates" actually is checking for updates and taking forever?
.
Click to expand...
Click to collapse
It is unlikely that the problem is caused by the slow internet. Try a hard reboot maybe?
If your problem is resolved confirm it here and hit Thanks

On the TWRP Terminal:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
this will skip the first setup!
edit: may need to mount /system

M_Maha said:
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
This link will help. Make sure you download the correct rom for your specific device and follow the instructions to the dot.
It is unlikely that the problem is caused by the slow internet. Try a hard reboot maybe?
If your problem is resolved confirm it here and hit Thanks
Click to expand...
Click to collapse
Ok, after 24 hours it's still checking for updates so definitely is not the connection.
I will try the link you posted but before, how do I do a hard reset? Is that the Power+VolDn thing I've done a thousand times to get to the belly up android? Or the Power+VolUp for 120 secs while charging?

michkost858 said:
On the TWRP Terminal:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
this will skip the first setup!
edit: may need to mount /system
Click to expand...
Click to collapse
How do I get to the TWRP terminal with a dead phone? Or is that from the computer connected to USB?

LostInTheDarkness said:
Ok, after 24 hours it's still checking for updates so definitely is not the connection.
I will try the link you posted but before, how do I do a hard reset? Is that the Power+VolDn thing I've done a thousand times to get to the belly up android? Or the Power+VolUp for 120 secs while charging?
Click to expand...
Click to collapse
Press and hold the Power and Volume Up for 30 secs. This won't erase the data but reboot
If that doesn't work, try this
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Press the Volume Down key to highlight Recovery mode.
Press the Power key to restart into Recovery mode.
The screen will display an Android robot with a red exclamation mark.
While holding down the Power key, press and release the Volume Up key, then release Power.
Use the volume keys to scroll to Wipe data/factory reset and press the Power key to select it.
Scroll down to Yes - erase all user data and press the Power key to select it.
Also you kept the unresponsive phone on for 24 hours?

LostInTheDarkness said:
How do I get to the TWRP terminal with a dead phone? Or is that from the computer connected to USB?
Click to expand...
Click to collapse
Just boot into TWRP by pressing and holding power button+volume down and then choose recovery.
Then you are inside TWRP
Go to Advanced -> Terminal and input the command there (may need to mount /system with Mount -> Tick System)
EDIT: Don't factory reset as another user said above me. It didn't help me at all when I had this issue. Bypassing first setup with this command actually helped me. To force a reboot on your device press an dhold power button+volume down and when the menu pops up roll around the options with the volume buttons until you see Recovery and press the power button to choose it. Then you can do the things I mentioned above.

michkost858 said:
Just boot into TWRP by pressing and holding power button+volume down and then choose recovery.
Then you are inside TWRP
Go to Advanced -> Terminal and input the command there (may need to mount /system with Mount -> Tick System)
EDIT: Don't factory reset as another user said above me. It didn't help me at all when I had this issue. Bypassing first setup with this command actually helped me. To force a reboot on your device press an dhold power button+volume down and when the menu pops up roll around the options with the volume buttons until you see Recovery and press the power button to choose it. Then you can do the things I mentioned above.
Click to expand...
Click to collapse
what is the command sir

gapps problem - re-download gapps from opengapps.org and
wipe advanced
system
data
dalvik/art
cache
then flash ROM
then flash gapps
boot
Be sure to select "set up as new" during install.

Hello. I have this same problem with my Nokia 1 and I don't know how to go about it.

Calvin Dorbu said:
Hello. I have this same problem with my Nokia 1 and I don't know how to go about it.
Click to expand...
Click to collapse
I used a different gapps. reflash clean.

Calvin Dorbu said:
Hello. I have this same problem with my Nokia 1 and I don't know how to go about it.
Click to expand...
Click to collapse
What ROM did you use on Nokia 1?

KrisM22 said:
gapps problem - re-download gapps from opengapps.org and
wipe advanced
system
data
dalvik/art
cache
then flash ROM
then flash gapps
boot
Be sure to select "set up as new" during install.
Click to expand...
Click to collapse
michkost858 said:
On the TWRP Terminal:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
this will skip the first setup!
edit: may need to mount /system
Click to expand...
Click to collapse
I downloaded the ROM from this thread, stuck at "Checking for Updates"... then tried disabling setup wizard method and booted up. However the GApps are nowhere to be found...
That's after a clean flash, with the almost-latest LineageOS14.1 ROM, tried both pico and nano OpenGApps, cleaned cache, and starting up the device.

I have the same problem, I tried different ROMs (all based on Pie). Can someone help me?

I have the same problem. Please help!

alessfd said:
I have the same problem. Please help!
Click to expand...
Click to collapse
Is this a Moto G3 Osprey and what have you done/installed e.g a Custom rom. More info please

Answers in old threads
michkost858 said:
On the TWRP Terminal:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
this will skip the first setup!
edit: may need to mount /system
Click to expand...
Click to collapse
Hi michkost858.
Can I query something? I just flashed Magisk on my wife's oooold Samsung J5 prime. After lots of workarounds, I got it to boot, but I am stuck on the eternal "Checking for updates" screen with the first setup.
Your advice sounds good, but I want to check with you if I am doing something wrong:
1) I boot into TWRP, select advanced, select terminal
2) I then type in the following exactly:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
3) It does not give me any confirmation, it just goes to the next line.
4)I then go to reboot, system, to restart the phone
5)But then it goes straight into the initial setup where it says "Hi there"... (I hate that screen)
Am I doing something wrong or is there another solution/workaround?
Regards,
Stupidrooter

Stupidrooter said:
Hi michkost858.
Can I query something? I just flashed Magisk on my wife's oooold Samsung J5 prime. After lots of workarounds, I got it to boot, but I am stuck on the eternal "Checking for updates" screen with the first setup.
Your advice sounds good, but I want to check with you if I am doing something wrong:
1) I boot into TWRP, select advanced, select terminal
2) I then type in the following exactly:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
3) It does not give me any confirmation, it just goes to the next line.
4)I then go to reboot, system, to restart the phone
5)But then it goes straight into the initial setup where it says "Hi there"... (I hate that screen)
Am I doing something wrong or is there another solution/workaround?
Regards,
Stupidrooter
Click to expand...
Click to collapse
Try this.
Boot to Recovery mode and do a Factory reset. Now when the phone boots up SKIP everything. You can setup the WiFi etc a bit later and then see if it will update.?
And or find the Updater app and disable background data so it doesn't call home.
HTH :

michkost858 said:
On the TWRP Terminal:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
this will skip the first setup!
edit: may need to mount /system
Click to expand...
Click to collapse
This most certainly fixed my problem.
Thank you.

Stuck on 'Checking for updates' after upgrade to Android P Beta DP3 and userdata wipe

So I decided to upgrade to the Android P beta DP3 right from stock (most recent version) and all went seemingly well. I downloaded the ROM, installed it with the local upgrade, pressed the restart button that appeared (instead of manually shutting it down) and booted right into P.
I noticed that everything was still installed, and I'd rather start fresh, so I booted to recovery and selected the wipe data option, which removes all userdata, as suggested in the official installation guide.
After wiping I booted back into Android and got the normal popup to enter my pin, accept license agreement and accept/decline a bunch of things like notification offer and stuff. After this, however, I end up in the 'Checking for updates...' screen which is taking ages (25+ minutes) and never seems to finish.
At this point I don't really know what to do. I've tried both wifi and though the mobile network, neither seem to work. There also isn't a skip button or anything as far as I can see.
Given that all data is wiped debugging also isn't enabled so adb appears to be out of the question. Booting into recovery also doesn't appear to work, as I always end up just starting Android. And last but not least the bootloader was still locked as this wasn't needed for the P beta.
I've tried making a thread on the official OnePlus forums, but it seems I'm still lacking in rep over there.
Any suggestions?

and i m pretty sure before trying that u should have atleast enabled oem unlock just to be safe T_T

Yup, I guess so too. Ah well, I posted the issue in multiple places, including as a bug report on the OnePlus forums. I'll just wait a few more days to see if anyone has an idea and otherwise I'll send it back for repairs and see if they can do something.

Hi,
reboot into Recovery and wipe data.
After a further reboot follow the setup wizard to the point where you can login to your Google Acc. Skip everything from this point on and you will get to the Homescreen. Wait a couple of minutes an you will be asked to finish the setup wizard.
I always have this annoying bug, too...

Thanks for the suggestion. Unfortunately I can't seem to boot into recovery anymore. No matter what I do, no matter the order of volume down+power (volume first then power, power first then volume, or pressing them exactly at the same time), nothing seems to actually get me into recovery. In each and every case it just boots straight to the Android setup. It also doesn't appear that I'm doing anything wrong, because I've got a few older Android phones here and on each one of them I can easily get into recovery.
I've also made an official bug report, so lets see how that pans out. But if anyone has any other suggestions in the meantime, I'm all ears.

Xylon- said:
Thanks for the suggestion. Unfortunately I can't seem to boot into recovery anymore. No matter what I do, no matter the order of volume down+power (volume first then power, power first then volume, or pressing them exactly at the same time), nothing seems to actually get me into recovery. In each and every case it just boots straight to the Android setup. It also doesn't appear that I'm doing anything wrong, because I've got a few older Android phones here and on each one of them I can easily get into recovery.
I've also made an official bug report, so lets see how that pans out. But if anyone has any other suggestions in the meantime, I'm all ears.
Click to expand...
Click to collapse
U have corrupted u r data partition. You have to flash fastboot flashable rom via fastboot mode but u will loose u r all internal data too.
https://www.google.co.in/amp/s/foru...m-stock-fastboot-roms-oneplus-6-t3796665/amp/