Develop Bugs

Android OS is sucking up all my mobile data!

Got to work this morning to find out I had no mobile data left (attached image). I thought, how strange, yesterday I'd had about ~1GB usage out of my 4GB available, I of course immediately when and looked to see what had used it all and Android OS was at the top with 2.13GB (WTF?).
This also isn't the first time this has happened, I had the same last month. Can someone please explain what is going on because I know for damn sure I've not used all that, I only browsed a few web pages this morning.
Sent from my Pixel XL using Tapatalk

Stop automatic backup

thenessus said:
Stop automatic backup
Click to expand...
Click to collapse
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Sent from my Pixel XL using Tapatalk

pairedprototype said:
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Click to expand...
Click to collapse
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.

Use Data Saver in settings, works a treat

TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.

Just switch to the unlimited data plan..problem solved

TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
alluringreality said:
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.
Click to expand...
Click to collapse
You are indeed correct, I am due an update, however, I'm not rooted currently although, my bootloader is unlocked as I've been assisting with getting Magisk working on stock for Pixel devices.
And what kind of idiot developer/team thought downloading OS updates over mobile data without question was okay!? I've now got to go for 2 weeks without, I'm royally p*ssed about it. Guess I'd better flash the new update then while I have a (non-cellular) internet connection.
I remember when Google targeted power users with Nexus devices, I guess this is not entirely true for Pixel devices. Big boys like to do what they want, even if that means staying on a particular version of Android because we might be testing things... I'd rather not have OS updates forced down my throat, it's the same thing that bugs me with Windows 10.

lucky_strike33 said:
Just switch to the unlimited data plan..problem solved
Click to expand...
Click to collapse
If you're willing to pay the extra, sure thing!

You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data

lucky_strike33 said:
You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data
Click to expand...
Click to collapse
That's what I usually do! Just not had the time to do it recently.

this is caused by update downloading and failing over and over. I went into the dev options and turned off the auto update but it did not work. I had to update the phone manually and now its fine. I think after rooting the phone and going back to stock rom this happens.

IDK man, I was rooted and was pulling like 10gb+. Flashed stock via adb and I think it's still doing it. Project fi.

This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.

FrostyOrDie said:
This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.
Click to expand...
Click to collapse
When you returned to stock did you get to the latest version?

TonikJDK said:
When you returned to stock did you get to the latest version?
Click to expand...
Click to collapse
No. This all happened since returning to stock. Today I sideloaded the August update with adb and my phone says it's on the current version finally. It seems the support people at project fi are clueless for the most part. You have to do everything yourself but they will at least credit your account for the data used by Android os if you call them and tell them what's up. They want screen shots of the data usage. So save one before you go messing with stuff

Stuck on Bootloop [7.1.1 ]

Hi,
A few hours ago I randomly got into a some kind of bootloop. It's not the "normal" bootloop where simply the boot animation is played forever. Instead my boot continues afterwards like normal until there's this short black screen before entering your SIM's pin card. This never appears and it begins again with the "Your bootloader is unlocked. Please lock it...."-message.
I already flashed the Factory Image twice via the ADB console on my PC and Wugfresh's Toolkit.
Additionally I can't seem to acess the stock recovery, the "red android guy" never appears and it only reboot itself after choosing the recovery in Fastboot Mode.
Any help is appreciated!
Vulkaistos

Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk

dc239 said:
Try to flash TWRP, in TWRP wipe every partition and then try to flash the stock image again
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I already tried that, same problem as Stock Recovery.

Vulkaistos said:
I already tried that, same problem as Stock Recovery.
Click to expand...
Click to collapse
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?

dc239 said:
It seems like your partitions are messed up, did you tried to flash it via the flash-all script that is included in the stock image zip file?
Click to expand...
Click to collapse
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!

Vulkaistos said:
Nope, I flashed them one by one. I may try the flash-all script now. Thanks!
Click to expand...
Click to collapse
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here

Vulkaistos said:
OK, I now tried the flash-all script with the newest factory image drectly from Google but still the same issue.
I'll now contact Lg to at least try to get a RMA because I think I tried the most solutions.
If there's anyone that has another Idea, feel free to post it here
Click to expand...
Click to collapse
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk

dc239 said:
Yea, that would be the best idea. Maybe it's slowly getting into that "classic" bootloop, which everyone talks about
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help

Vulkaistos said:
I got a very interesting update on my issue.
My phone worked for a few minutes now, it booted normally and I could even set it up completely. But now it's the same problem again so I more and more think it could be faulty hardware.
Anyways I contacted LG for a RMA and we'll what happens.
Thanks for your help
Click to expand...
Click to collapse
You'll get the RMA, that is a hardware failure.

Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.

Vulkaistos said:
Last Update:
LG accepted my RMA request and I'll send them it ASAP.
Thank you everyone for helping me!
I'll mark this thread as solved.
Click to expand...
Click to collapse
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk

dc239 said:
Little OT, but how long have you had your 5X? It looks like all the 5x's are just time bombs in case of that hardware bootloop. I'm thinking about selling my 5x and buying something that will not die on me some day.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I bought my Nexus in December 2015 so around 2 1/2 years ago. It's a nice phone never had any serious problems with it except now.

Play Store FC trying to buy app

Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified

mac796 said:
Okay I have two pixels. One with magisk and one running SuperSU with suhide, both pass safety net. Both on Oreo. I'm trying to buy a substratum theme in the Play Store everytime I enter my password to buy it if force closes on either phone. Anyone else have this issue I imagine it still detects the root, but I'm not sure I was hoping somebody new a workaround. Both pixels are on Android o.
Edit. I did try clearing cache and data. I am certified
Click to expand...
Click to collapse
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.

mlin said:
I have this same issue. However, I am stock unrooted. Somebody in the Pixel forum was having the same issue. His problem was solved by reflashing the full Oreo image. A factory reset did not fix it. I'm planning to reflash the Oreo image to both partitions tomorrow to see if it fixes the problem.
Click to expand...
Click to collapse
It's very strange happens on both my pixels so must be a bug on googles side maybe.

mac796 said:
It's very strange happens on both my pixels so must be a bug on googles side maybe.
Click to expand...
Click to collapse
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?

mlin said:
I have the issue but my wife doesn't. She updated to Oreo via OTA, I updated via manually flashing. I was previously rooted with a custom ROM but had returned to stock Nougat long before updating to Oreo. How did you update?
Click to expand...
Click to collapse
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.

mac796 said:
I flashed the factory image with fastboot. I'm on September that's a good idea maybe I'll Flash August and take the OTA see how that goes.
Click to expand...
Click to collapse
I flashed the factory image on release day and OTA'd to September security patch. No dice.

mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So it's still not working for you? Maybe I'll just wait till next update then.

mac796 said:
So it's still not working for you? Maybe I'll just wait till next update then.
Click to expand...
Click to collapse
Nope, still not working. I'll let you know if my efforts tomorrow are successful.

mlin said:
I flashed the factory image on release day and OTA'd to September security patch. No dice.
Click to expand...
Click to collapse
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol

mac796 said:
So I flashed back to August and it let me put in my password and buy an app and then if FC right after that. But it did go through lol
Click to expand...
Click to collapse
Lol, weird. So just reflash before each app purchase and you should be good!

mlin said:
Lol, weird. So just reflash before each app purchase and you should be good!
Click to expand...
Click to collapse
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it

mac796 said:
Geez I hope not. Google sure making things alot harder all around
Edit: ok it took the OTA to September and same thing. No go. I have Verizon, wonder if that has anything to do with it
Click to expand...
Click to collapse
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.

mlin said:
I have Verizon as well. I used fastboot to flash the factory image to both slots and now everything works. Not sure if there was an easier way to get it working but at least it works now. Took the OTA to September and everything is still working.
Click to expand...
Click to collapse
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is

mac796 said:
Yes I did that to. I'm still having the problem kind of glad it didn't work, didn't really want to buy anything lol. I'm not sure what the deal is
Click to expand...
Click to collapse
Did you wipe data as well?

mlin said:
Did you wipe data as well?
Click to expand...
Click to collapse
Yes I wiped everything except internal storage

mac796 said:
Yes I wiped everything except internal storage
Click to expand...
Click to collapse
I did wipe internal storage, though hard to say if that difference made it work. I'd be curious to hear if you do get it working eventually or if you find a different solution. Best of luck, hope you get it resolved eventually though I get the appeal of being unable to buy apps lol.

Ascend XT2 B130 Update and CleanRom Rom's

Well here we go
This is the First Update for the XT2 in a flashable rom​
This is for those who unlocked their bootloader and installed TWRP and can not take OTA update on their phones
As most here know ower version of TWRP is not complete and cannot decrypt the /data partition
so unfortunately you'll have to wipe your phone to install this update (sorry)
Note This also Removes TWRP and restores Stock Recovery
Flashing instructions
download and copy the Stock_B130_ XT2_H1711.zip to your ex_sdcard
copy Magisk-v16.0.zip to your ex_sdcard (just in case you need to patch the boot.img)
Boot into TWRP swipe to allow system access
Go to Settings check Use rm -fr instead of formatting
next choose Wipe / Format Data / Type "yes" to confirm
Now choose Home / Install /Select storage Micro sd /Stock_B130_ XT2_H1711.zip and Flash it (watch the flash for any Red Errors)
choose wipe cache and then reboot.
If everything went well you should be on B130 and ready to setup your phone
Huge thanks go to @m0000 for sharing his updated files
If you have any problems you'll need to reflash TWRP and Try patching the boot.img with Magisk or restore your last backup or simply flash my B120 stock rom
XT2 B130 CleanRom​
Now that you have a Stock updated phone you may want to remove all the AT&T Bloat
Here's my CleanRom that removes around 350mb of useless junk from the phone.
First you'll need to flash TWRP back to your phone from fastboot
download recoveryV3_Fixed.zip > https://androidfilehost.com/?fid=673956719939832036
and extract it to your fastboot folder
Shutdown the phone
reboot to the bootloader (power + volume down + plugged in to the PC)
and flash it from command prompt with
fastboot flash recovery recoveryV3_Fixed.img
next reboot to TWRP (power + volume up )
Now you can Download the CleanRom and copy it to your ext_sdcard from your pc.
Flashing instructions are the same as above, but you can do a dirty flash by not formatting data like above if you want to keep your current apps
Here's the list of whats removed
Apps deleted from System:
Amazon shopping
App select
Call Protect
Protect Plus
Device Help
Setup & Transfer
CricketWiFiManager
Facebook
Facebook App Installer
Facebook app manager
Gmail
Google Duo
Google Chrome
Google Drive
Google Maps
Google Play Photos
Google Play Video
Google Play Music
Google Text to Speach Engine
Ignite
Lookout
myCricket
Apps deleted from /Data/hwinit/: (If you dirty flashed these will still be on your phone)
Google Editor Slides
Google Editor Sheets
Google Editor Docs
Firefox
Apps deleted from Cust:
AT&T Remote Support
myAT&T
AT&T Hot Spots
Google Talkback
everything in the H1711z folder
The rom includes the patched boot.img from magisk v16 (it's rooted)
This will probably be the only rom I release for this phone because I don't own one.

Awesome. Thank you! So if I flash magisk after I should be able to keep my root then?

clsA said:
Huge thanks go to @m0000 for sharing his updated files
Click to expand...
Click to collapse
No thanks needed. You did all the work I only followed clear directions

freedomwarrior said:
Awesome. Thank you! So if I flash magisk after I should be able to keep my root then?
Click to expand...
Click to collapse
Yes will need to start over ( TWRP & Magisk )
Your phone will be bone stock after flashing the rom
Sent from my LG-H910 using Tapatalk

Alright. I just want to confirm that the update was successful
Out of curiosity I wanted to see if I could relock the bootloader and that finally worked too. (see screenshot) I was never able to do that before on the B120 stock rom so this is great news if I ever decide to sell the phone or just wanna get SafetyNet working correctly.
I went ahead and unlocked my bootloader again and I flashed TWRP through fastboot, Booted into TWRP and flashed magisk v16 in the OP, rebooted and I am enjoying root again with an updated phone.
Thanks again guys!

freedomwarrior said:
Alright. I just want to confirm that the update was successful
Click to expand...
Click to collapse
thanks for the update! All we need now is a @clsA CleanRom for this version

So does anybody know how hard it would be to compile lineage os 14.1 for the elate/ xt2?

903tex said:
So does anybody know how hard it would be to compile lineage os 14.1 for the elate/ xt2?
Click to expand...
Click to collapse
I have no idea but that sure would be awesome! I am guessing it would be a real pain due to the fact Huawei has not released the source code for this phone.

freedomwarrior said:
I have no idea but that sure would be awesome! I am guessing it would be a real pain due to the fact Huawei has not released the source code for this phone.
Click to expand...
Click to collapse
What about the h1611?

MaxxTwo said:
What about the h1611?
Click to expand...
Click to collapse
I am not sure. I don't own that phone.

First post updated

clsA said:
This will probably be the only rom I release for this phone because I don't own one.
Click to expand...
Click to collapse
If you need a guinea pig for future testing let me know. I have one with your CleanRom and a stock unlocked one for any and all future updates.
Thanks!

I really liked this phone, i was actually impressed. I had money to spend on a new budget phone and I was between a ZTE blade spark and this huawei.
ZTE was ok for me because a couple of years ago i bought one of their big phones but their camera sucked a lot of blur and never had focus. sometimes i even had to touch the screen again and again to make it focus, while capturing video. So i gave a shot to this Huawei, went to walmart, they wanted 89 for the phone, told them to check online because it was 69 online and they lowered me the price right away.
then used the huawei for about an hour and damn, the camera is awesome, and the LCD screen is beautiful.
I have to research on how to unlock the bootloader and pay the 5bucks to make that happen.
One thing i noticed is that altho the phone has a 16gb capacity, i was looking at the storage area and you actually end up having something like 7.3gigs free. Is that normal? most of the space is taken by the rom. Your clean rom would help a lot at least to get more space, but how come it only frees 300megs.
and thank you very much for the update. i do know how damn hard it is to update at&t gophones because those assholes only let you update the phone if you have an att simcard inserted that is also activated and you have to be with an IP that is inside USA, and have celular data ON, and sometimes even having all that.. it doesnt even update

ZeldaWW said:
I really liked this phone, i was actually impressed. I had money to spend on a new budget phone and I was between a ZTE blade spark and this huawei.
ZTE was ok for me because a couple of years ago i bought one of their big phones but their camera sucked a lot of blur and never had focus. sometimes i even had to touch the screen again and again to make it focus, while capturing video. So i gave a shot to this Huawei, went to walmart, they wanted 89 for the phone, told them to check online because it was 69 online and they lowered me the price right away.
then used the huawei for about an hour and damn, the camera is awesome, and the LCD screen is beautiful.
I have to research on how to unlock the bootloader and pay the 5bucks to make that happen.
One thing i noticed is that altho the phone has a 16gb capacity, i was looking at the storage area and you actually end up having something like 7.3gigs free. Is that normal? most of the space is taken by the rom. Your clean rom would help a lot at least to get more space, but how come it only frees 300megs.
and thank you very much for the update. i do know how damn hard it is to update at&t gophones because those assholes only let you update the phone if you have an att simcard inserted that is also activated and you have to be with an IP that is inside USA, and have celular data ON, and sometimes even having all that.. it doesnt even update
Click to expand...
Click to collapse
Instructions for DC Unlocker are here
https://r.tapatalk.com/shareLink?ur...share_tid=3780903&share_fid=3793&share_type=t
Sent from my LG-H910 using Tapatalk

@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?

freedomwarrior said:
@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?
Click to expand...
Click to collapse
Looks like b173
You would need to return to stock b130
To attempt the update
Sent from my LG-H910 using Tapatalk

freedomwarrior said:
@clsA
At&t is trying to push another software update to my phone. Is this the B130 we already have or a new one?
Click to expand...
Click to collapse
clsA said:
Looks like b173
You would need to return to stock b130
To attempt the update
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
B130_B173_ATT is the files i sent to clsA for his b130 rom. i've not received any notification on a newer update yet.
@freedomwarrior nice dark theme btw. what are you using?
Thanks

m0000 said:
B130_B173_ATT is the files i sent to clsA for his b130 rom. i've not received any notification on a newer update yet.
@freedomwarrior nice dark theme btw. what are you using?
Thanks
Click to expand...
Click to collapse
Awe ok. That would just be att update being stupid then.
I am using Pure Dark 5.0. So far it is the best dark theme I have come across.
https://play.google.com/store/apps/details?id=sk.hanni.emuithemes.puredark

freedomwarrior said:
Awe ok. That would just be att update being stupid then.
I am using Pure Dark 5.0. So far it is the best dark theme I have come across.
https://play.google.com/store/apps/details?id=sk.hanni.emuithemes.puredark
Click to expand...
Click to collapse
Awesome, i'll check it out. Are the ads annoying? or can disable with a proper ad blocker?
Thanks

m0000 said:
Awesome, i'll check it out. Are the ads annoying? or can disable with a proper ad blocker?
Thanks
Click to expand...
Click to collapse
No ads so far that I have noticed.

bootloop

My pixel xl started bootlooping. I can get into fastboot but that's it. If I try to boot twrp, bootloop, if I flash stock, bootloop. I've tried Oreo, pie. This came out of nowhere. I tried a gsi, bootloop. I'm very confused. The memory works because its flashing. Something has to be triggering a reboot. Only thing I know of that forces restart is unencrypted internal storage

same here... any updates?

ferydaboss said:
same here... any updates?
Click to expand...
Click to collapse
I just sat down to try again, I will keep you posted. this is a dev device for me so its kind of annoying it would randomly brick for no reason. luckily I always keep the bootloader unlocked

godkingofcanada said:
I just sat down to try again, I will keep you posted. this is a dev device for me so its kind of annoying it would randomly brick for no reason. luckily I always keep the bootloader unlocked
Click to expand...
Click to collapse
This was my personal device, got out of warranty, no google store or any other youbreakwefixit stores near me, and it just bricked by itself. No root,no custom rom, nothing i can barely get into Recovery mode, and when i do, i install the latest OTA, and hope for the best Thanks

ferydaboss said:
This was my personal device, got out of warranty, no google store or any other youbreakwefixit stores near me, and it just bricked by itself. No root,no custom rom, nothing i can barely get into Recovery mode, and when i do, i install the latest OTA, and hope for the best Thanks
Click to expand...
Click to collapse
I bought a one plus literally a week ago. Lucky on my end. Whatever google did it is bad. I opened up the kernel and disabled the securities. Unencrypted the data. Still nothing. I've manually flashed over every partition 1 by 1, switched to the other slot and tried there. This looks like its going to be a battle. I've got a feeling what we flash isn't copying over some things because it keeps the newest version, which is why we can flash but not overwrite the problem

godkingofcanada said:
I bought a one plus literally a week ago. Lucky on my end. Whatever google did it is bad. I opened up the kernel and disabled the securities. Unencrypted the data. Still nothing. I've manually flashed over every partition 1 by 1, switched to the other slot and tried there. This looks like its going to be a battle. I've got a feeling what we flash isn't copying over some things because it keeps the newest version, which is why we can flash but not overwrite the problem
Click to expand...
Click to collapse
So... there may be a solution in the near future? seeing that google themselves did this? because it is a coincidence, that i see literally 5 pots about the same problem under 4 days..

ferydaboss said:
So... there may be a solution in the near future? seeing that google themselves did this? because it is a coincidence, that i see literally 5 pots about the same problem under 4 days..
Click to expand...
Click to collapse
Google's update hurt some pixel devices, but they expect us to RMA repair the device... I went the other direction and opened it up to tinker with instead

mi wifes pixel is having the exact same issue.
google says im out of warranty so some of the patches ****ed us up....