Does anyone know when Google will start to actually post the images? This is the first phone I can remember having in my hand without any factory images posted.
I was wondering the same thing. Since no factory images are up, I tried the Android Flash Tool, which correctly identified the phone as a 4a, but said it was "unsupported". I've never tried the Flash Tool before, fairly easy to use, but I do wonder how fast the downloads will be. But, yeah, factory images should be up. I never completely trust a phone out of the box, prefer to do a wipe and flash before setup and use. I mean, it was probably built in China, right? I don't need any Chinese spies looking at my porn.
Well, today (Aug 20) was supposed to be the official debut, even though many of us have had these phones at least a couple of days now. If they dont have the images posted by tomorrow, then someone at Google is asleep at the wheel!
Maybe Android 11 is coming so soon they'll wait to post that?
Pig Vomit said:
I mean, it was probably built in China, right? I don't need any Chinese spies looking at my porn.
Click to expand...
Click to collapse
I think I read somewhere that, as Google is moving away from China, they've been producing more in Viet Nam. The Pixel 4a is supposed to be the first phone to be fully produced outside of China. That's cool, right?
i started tweeting at @madebygoogle & @googledevs asking them to upload factory images & kernel source lol maybe itll get someones attention but not counting on it
I emailed google support to ask if unlocking the bootloader and rooting the pixel 4a with magisk would void the warranty. The response was that it would not void the warranty. That convinced me to buy a second Pixel 4A to replace my other moto x4 as well.
I need to root only becaasue I need telephone call recording with bluetooth. I have paid versions of both Call Recorder (skvalex) and BoldBeast, but neither work with bluetooth if the phone is not rooted, so it is good to know I can root as soon as an image is available. Here is the response I got:
" I understand you'd like to know if unlocking the bootloader and rooting the device would void the warranty. Let me help you with the details. Warranty of your device is still covered regardless of whether a device was rooted or unlocked. However, if you are experiencing any issue after rooting the device, we might suggest you to unroot the same in order to get the issue resolved. Android is not against rooting, but we can't guarantee functionality if the source code for the Android OS has been modified hence we might ask you to unroot the device before helping you with the warranty options."
Reacon said:
I think I read somewhere that, as Google is moving away from China, they've been producing more in Viet Nam. The Pixel 4a is supposed to be the first phone to be fully produced outside of China. That's cool, right?
Click to expand...
Click to collapse
Box says phone made in Vietnam, accessories made in China. My problem with China is with human rights more than a concern about spying. My original post was meant to be funny. That having been said, Vietnam's human rights record isn't so great, either.
xenokc said:
Maybe Android 11 is coming so soon they'll wait to post that?
Click to expand...
Click to collapse
I'm kinda thinking this as well. I've got the final/release candidate Android 11 beta on my Pixel 2XL right now. It's pretty good, but there are a few problems I've noticed that should be cleaned up before it goes final. It wouldn't surprise me if they release another beta/Release Candidate #2. Google probably was shooting for a simultaneous launch, but couldn't get 11 finalized in time. I also assume there's a beta version of 11 for the 4a, because there has to be if it's about to be upgraded to 11, right? At least post those images up.
Pig Vomit said:
Box says phone made in Vietnam, accessories made in China. My problem with China is with human rights more than a concern about spying. My original post was meant to be funny. That having been said, Vietnam's human rights record isn't so great, either.
Click to expand...
Click to collapse
China has been throwing its economic weight around to effectively undercut any and all competition. It's just a reality if you want to have a manufacturing-based economy in 2020 that you'll have to make an incentive to drive business your direction. Unfortunately, many companies were in a catch-22 where if they report the rampant IP-theft in connection with the CCP they would either lose their competitive margin or potentially lose the ability to manufacture their product at all, because China also has hoarded the best tooling tech.
If there's one thing that the US' current administration has done correctly, it's to bare China's fangs. Hopefully, with commerce forcefully directed elsewhere, the dire need for profit margin will ease a bit in the poorer countries of the region, giving way for better human rights adherence. At least, that's my wishful thinking.
nogods said:
I emailed google support to ask if unlocking the bootloader and rooting the pixel 4a with magisk would void the warranty. The response was that it would not void the warranty. That convinced me to buy a second Pixel 4A to replace my other moto x4 as well.
" I understand you'd like to know if unlocking the bootloader and rooting the device would void the warranty. Let me help you with the details. Warranty of your device is still covered regardless of whether a device was rooted or unlocked. However, if you are experiencing any issue after rooting the device, we might suggest you to unroot the same in order to get the issue resolved. Android is not against rooting, but we can't guarantee functionality if the source code for the Android OS has been modified hence we might ask you to unroot the device before helping you with the warranty options."
Click to expand...
Click to collapse
Save that e-mail! While that rep said it won't, that doesn't mean it is true as a company policy. But the fact that you have it in writing from a Google rep gives you some ammunition in case they do try and say your warranty is void.
Yeah, I fired off a few tweets to @google asking them about the factory images. I think the more people who ask, more of a problem it will be for them,,,maybe.
renzyyy said:
i started tweeting at @madebygoogle & [URL="https://twitter.com/googledevs" @googledevs[/URL] asking them to upload factory images & kernel source lol maybe itll get someones attention but not counting on it
Click to expand...
Click to collapse
Does make for a September update a big question. Could G just start it on 11? Device rollout was delayed. Maybe a thought. I am hoping for a 10 release of at least our current as released build QD4A.200805.003. Especially if 11 bootloader has issues with . . . .
A nice comparison to my 3a, 3 is side by side the case of a 3 in size and a display more than 3a. Surprised hole punch (which would not think) goes away in most use...
reached out to google support team after making a fuss & finally got a pretty good answer...
In regards to Factory image availability on our developer page, the image would be updated post security patch of Sept. As it's a new device we are shipping the devices with August update, once the device specific builds are released it will reflect on Developer images.
Click to expand...
Click to collapse
kkjb said:
I am hoping for a 10 release of at least our current as released build QD4A.200805.003.
Click to expand...
Click to collapse
This is the build that it was released with. I was surprised, because I had read so many articles saying the phones had been assembled months ago and were in a warehouse waiting for release. I doubt they re-flashed all the phones, so I suspect they were manufactured more recently. I had expected a very old security release to be on them, but it's the August release.
Build # convention for .003 was carrier specific builds on rest of Pixel line...is a wonder.
Since I have a audience I get no Sprint dial code switching on Google Fi Network.
So TMobile here now...no chat messenger!
US Cellular is my other provider same thing. Call screen is working.
Radio sensitivity is better than 3a nice to have in the boonies here.
Yeah I kinda figured they would wait til the Sept patch is out to provide the factory images. Sucks a little that is over two weeks from now.
renzyyy said:
reached out to google support team after making a fuss & finally got a pretty good answer...
Click to expand...
Click to collapse
I'm usually a happy silent observer because the factory images are usually out when the phone comes out, but I am a little annoyed because I have my new phone and I don't want to set it up again in two weeks.
Is there any reliable way to dump the ROM and get the boot image without root?
SexySOnic23 said:
I'm usually a happy silent observer because the factory images are usually out when the phone comes out, but I am a little annoyed because I have my new phone and I don't want to set it up again in two weeks.
Is there any reliable way to dump the ROM and get the boot image without root?
Click to expand...
Click to collapse
Why would you have to set it up again? You can unlock the bootloader now.
digger16309 said:
Why would you have to set it up again? You can unlock the bootloader now.
Click to expand...
Click to collapse
Just because I want to flash Magisk, I can't do that without the boot image. Once I went TitaniumBackup, I never went back. But ya know, I need root for that
SexySOnic23 said:
Just because I want to flash Magisk, I can't do that without the boot image. Once I went TitaniumBackup, I never went back. But ya know, I need root for that
Click to expand...
Click to collapse
Yes, I do, too. But I roughed it out setting up the phone without it. Most of my apps had data in the cloud or their own backup file. I transferred other files manually. I'll root, but I don't need to setup my phone twice because I unlocked the bootloader first.
Related
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
dymmeh said:
You have to wipe the device anyways and send it in. So why not just take the extra minute to lock the bootloader as a precautionary step?
Click to expand...
Click to collapse
The only thing I am worried about is if something happens before locking. I know that locking the bootloader has been heavily advised against by beaups, and I just don't want anything to happen during the locking process.
stompysan said:
So I had an interesting thing happen today. My phone's audio stopped working entirely. Any app that had or used sound causes my device to lock up entirely. Went through the standard steps, all the way to flashing back to stock, with the same issue. Called Google, and they informed me that it is 100% a hardware issue, and I need to RMA. Great. So I am in need of some advice. Since I have to send this to Google, I will want to be stock. I know that locking the bootloader is problematic, and will ultimately cause me to not be able to unlock. Should I lock the bootloader? It is going back to Google, but if they see it is a Verizon device with an unlocked bootloader, they may not like it. Also, while I know the people on XDA aren't mindreaders, maybe someone else will have dealt with this. What are the odds of getting a device with an exploitable build? Has anyone gotten a replacement from Google, and if so, what build was it running? I know I shouldn't expect to be able to unlock, but I can hope.
Click to expand...
Click to collapse
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
jsbeagle said:
Dealing with this exact problem right now on my wife's Verizon Pixel.
It was bootloader unlocked and rooted, but still auto updated for the Feb update. Soon after, audio broke just as you described. I was able to get it back working for a little bit after a couple factory image flashes, but it broke again for good.
I contacted Google and they set me up with an RMA. I flashed an exploitable factory image, relocked the bootloader, and sent it in last Wednesday. The replacement should be delivered tomorrow. I'm really hoping it was on the shelf at Google since launch and depixel. The phone was useless otherwise, so I had no choice but to send it back. I wish they'd just send me a non-Verizon.
"Your replacement Pixel Phone Silver 32 GB (Verizon) was shipped on February 20, 2017 via FXG"
I'll try to update after the replacement comes tomorrow.
Click to expand...
Click to collapse
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
stompysan said:
I went ahead and did the same thing. Let me know what build your replacement is. I still have my fingers crossed.
Click to expand...
Click to collapse
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
PsiPhiDan said:
They all say they're Verizon models but almost everyone on this forum who has done this got a Google Play edition (it just has a Verizon SIM).
When I went through it, they said locking the bootloader was not necessary. Also, I got a brand new device with all accessories but they told me not to send the accessories in since I'd only be getting a phone back. Great experience for me. Props to Google for great service.
Click to expand...
Click to collapse
jsbeagle said:
YES!!!!!
Replacement Pixel just delivered. Appears to be brand new. All accessories included (they told me to only return the phone)
Verizon SIM was installed (I removed before booting it up).
Android Version 7.1
October 5 security patch
Build NDE63P
OEM unlocking toggle was greyed out until I connected to wifi, then I was able to toggle it to allow the bootloader to be unlocked. It does appear to be a google play edition in every way except the sim card that is included.
This is awesome. I'm now jealous of my wife and her non Verizon version. (We both still have the old grandfathered unlimited data and used the best buy trick to get Pixels on subsidized upgrades)
Click to expand...
Click to collapse
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
stompysan said:
You have no idea how excited this makes me. I have been extremely worried, but looks like I didn't need to be. Thanks!
Click to expand...
Click to collapse
For the record, the only person who got a Verizon model still was able to unlock the bootloader (it was a new device with old 7.1 software) using dePixel8 so I think you're set regardless! Google is good!
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
I got a Verizon version in January and it had an issue I haven't seen too many have, but it was audio related and apparently a hardware defect: mine had awful sound through the headphone jack only. Sounded like hissing and scratching beneath all the music. As if you didn't have the connection tight (but I did). Got the replacement and all is well!
UnusualSuspect said:
For those who had the audio-craps-out problem, can I ask when you ordered you phones?
My wife & I have Google Store devices. I ordered mine in the first week after launch, and it's been great. I ordered my wife's in early January and she has audio-craps-out disease.
So I'm wondering if there's a bad batch of Pixels?
Click to expand...
Click to collapse
Mine was ordered through Verizon on November 12, and shipped the next day. I am going to assume that it was a launch device.
Mine was purchased from bestbuy.com in mid November. It actually shipped from a local Best Buy store.
I believe there is a bad batch of pixels. I'm currently on my second one.
A couple weeks ago my pixel crashed and shutdown and well never turned on again. Basically the phone was bricked. Idk how or why. I was running perfectly and I only had the bootloader unlocked.
Long story short. I contacted my provider (Project Fi) and they sent me a new one. Received it the next day. (Great customer service!!)
So yes I believe there is a bad batch of pixels out there.
Xiaomi implemented anti-rollback feature ( more like a headache) with miui 8.7.6. In this thread I will tell you my experience:
So, I was just browsing through mi community and this post about anti-rollback caught my attention. I wasn't much concerned about it and thought why would someone want to downgrade their phone, I didn't read it completely and that was my mistake. So, you see I had flashed miui 8.7.5 from twrp and did ota update of 8.7.12 to save data as ota is smaller. Now I don't know why but I thought of installing Xposed on my phone. I flashed it and my phone entered bootloop. As this was not knew I calmly booted to twrp and flashed the file of 8.7.5 and pressed reboot.... 1 sec nothing, 2 sec nothing, 3 second nothing and in the 4th second I realised what I had done. I had become a victim of the outrageously implemented anti roll back feature. I left my phone and the next day I found it was alarmingly warm. It stayed warm for like 36 hours and then the battery died. I didn't have time so my phone was a paperweight for 1 week. Then on Saturday( this incident happened three weeks earlier on Sunday) I took it to the middle service centre. Actually around the same time as me a YouTuber named "tech star shahrukh" had bricked his device and posted a video telling how he got his motherboard change. I was sure that service center guys would ask me to pay if I told them the actual reason, so I told them my phone got dead when updating to miui 10. The guy told me with great confidence that they will repair it in two hours, I said ok. Here comes the interesting part. Now I being one of the more stupid personality had actually washed my phone under a tap a long time ago and that had lead to water in my charging board. He told me that I will need to pay 800 INR for the repair, thankfully the motherboard had not got water( they have these little white stickers that turn red on water contact). So I paid an advance 500 and waited. After about 3 days I got a call saying my sub board( charging board) was replaced and any further repairs would come under warranty. I was happy. So after exactly one week of submitting my phone and almost 2 weeks after bricking it, I got it back. Motherboard changed and with miui 9.2.4. So, that was my experience with anti roll back. Thankfully I replaced INR 8000 motherboard by paying 800.
Now it is showing 9.2.13 update, but I won't update. I have had enough of xiaomi. 2 weeks without my phone is just not worth a feeble security feature. So, what are your thoughts on this?are you happy with the current implementation (absolutely not). Suggest how do you think this feature should be implemented.
So you washed your phone and what it has to do with ARB?
Or if I do not understand you right, correcr me.
Arb was implemented for people to stay on latest firmware, as any manufacturer wants to owners be, I totally agree with that, except it was introduced silently which lead to many troubles. Personally I think there was major security bug in previous rom, thats why they changed arb to 4 in that firmware.
d1g1m4n said:
So you washed your phone and what it has to do with ARB?
Or if I do not understand you right, correcr me.
Arb was implemented for people to stay on latest firmware, as any manufacturer wants to owners be, I totally agree with that, except it was introduced silently which lead to many troubles. Personally I think there was major security bug in previous rom, thats why they changed arb to 4 in that firmware.
Click to expand...
Click to collapse
Look, actually I had washed my phone a long time ago. So there was no damage but the sticker above the sub board had turned red indicating water damage. My phone was working perfectly even after washing. I bricked it due to anti-rollback when I tried to flash 8.7.5 over 8.7.12. xiaomi has a policy under which if there is liquid damage to a part you need to pay for it to get replaced. There were two stickers in the phone, one over the sub board and another over the motherboard. Only the sub board one had turned red, meaning I had to pay for the sub board replacement(INR 800), So the service centre people first replaced my sub board and then they realised that the phone's motherboard was also messed up, so they replaced it under warranty. I hope you understand now. Washing had nothing to do with arb, just that it made me pay 800 RS.
Okay great, congratulations. But before every flash better be sure what you are doing. And in case of Xiaomi better get full permissions account before any flashing
d1g1m4n said:
Okay great, congratulations. But before every flash better be sure what you are doing. And in case of Xiaomi better get full permissions account before any flashing
Click to expand...
Click to collapse
Right man.
But I still think it wasn't implemented properly. Don't you think that wrecking the motherboard just for a little mistake of flashing a lower version too much? They should at least allow us to disable it. Not everyone is lucky enough to get a motherboard replacement for free...
Same for me. After bricking the device, board was needed to be changed and got it changed under warranty. Something strange happened after change of board, Internal memory got reduced by 4GB and RAM by 40MB. Xiaomi will push update 9.5.19 with ARB V4 even if auto update is off. Check internal storage for downlaod_rom folder. It will get automatically updated during sleep time. Replace the downloaded update file with a text file with same name to stop the updater from triggering it.
I dont understand whats the problem.. In my eyes only mistake by xiaomi was introducing ARB, and only after first bricks releasing official statement.. apart from that its a good feature. Normal users will never face any problems, as they are using official builds, and never go downgrade route.. Users like you, who unlock bootloader, flash beta roms, dev roms, god knows what other roms, should be skilled enough to not break their phone. I mean if you cant follow simple instructions of NOT downgrading bootloader, maybe this whole thing is not for you... By unlocking bootloader you agree with possible damage, no one else is responsible but you. Btw you dont have to change motherboard, all you need is account with permission to flash rom. In the end, all roms gonna be ARB 4, and this whole thing gonna be forgotten. Oh i also was ARB 3 and aware of this whole situation, but updated to .19 ARB 4 rom without fear, because as i said earlier, if you know what you are doing, this brings you no trouble at all..
I unlocked my bootloader and flashed redwolf twrp at 9.5.19.0 stable and after I flashed miui 10 8.6 beta my device is bricked I went to service centre they changed my motherboard
Anutha02 said:
Xiaomi implemented anti-rollback feature ( more like a headache) with miui 8.7.6. In this thread I will tell you my experience:
So, I was just browsing through mi community and this post about anti-rollback caught my attention. I wasn't much concerned about it and thought why would someone want to downgrade their phone, I didn't read it completely and that was my mistake. So, you see I had flashed miui 8.7.5 from twrp and did ota update of 8.7.12 to save data as ota is smaller. Now I don't know why but I thought of installing Xposed on my phone. .
Click to expand...
Click to collapse
Did you flashed xposed through Magisk or twrp?
Why people downgrade the miui rom? Answer is simple. In each and every new update, new bug is being introduced. When I was on 9.2.4 only issue was with audio over headphone. After each new update and now on 9.5.17 the issues I face are heating during youtube through firefox, When Connected to pc through mtp, folder access is limited. I use ADM do download files and it will be inside adm folder. if i need to access the files, First it should be copied to download folder from adm folder using file manager. ChromeCast gets disconnected often during 9.5.17. Screen mirroring gives artifacts. Audio over Bluetooth is low. Now after anti v4 anyone who wants to go back to much stable version such as 9.2.4 will be bricked. Once in anti v4, there is no way to get back to anti v 3. even to work simple fast boot commands of anti 4 , first dummy file is needed to be flashed which is rather annoying. Last miui version with anti v 3 is 9.5.17.
Incogn said:
I dont understand whats the problem.. In my eyes only mistake by xiaomi was introducing ARB, and only after first bricks releasing official statement.. apart from that its a good feature. Normal users will never face any problems, as they are using official builds, and never go downgrade route.. Users like you, who unlock bootloader, flash beta roms, dev roms, god knows what other roms, should be skilled enough to not break their phone. I mean if you cant follow simple instructions of NOT downgrading bootloader, maybe this whole thing is not for you... By unlocking bootloader you agree with possible damage, no one else is responsible but you. Btw you dont have to change motherboard, all you need is account with permission to flash rom. In the end, all roms gonna be ARB 4, and this whole thing gonna be forgotten. Oh i also was ARB 3 and aware of this whole situation, but updated to .19 ARB 4 rom without fear, because as i said earlier, if you know what you are doing, this brings you no trouble at all..
Click to expand...
Click to collapse
I have no problem with arb, I have a problem with the way it is implemented. Agreed that we should be careful while flashing roms but hard bricking the device does not make sense. What if even xiaomi accidentally releases an update with anti lower than 4 or we get a buggy update and want to revert. They should at least allow us to disable it or provide us an easy way to restore our device(using our mi id in some tool like mi flash). I understand that it is a security feature, but it has not been implemented correctly. They should have gone the Google way...
Guys, seriously, let me throw in my two bits for you all to chew on: why would you trust _any_ OEM (Samsung, LG, Sony, Xiaomi, etc.) to build a ROM with the users' best interest at heart? Doesn't make sense. That's why we buy devices that we can unlock, and break free. We should be supporting community ROMs and developers and help them to port features we need. There are lots of open source options out there (LOS, RR, etc.) that don't compromise your data or lock you in under the guise of "stability and security".
Thanks for reading.
temporarium said:
Guys, seriously, let me throw in my two bits for you all to chew on: why would you trust _any_ OEM (Samsung, LG, Sony, Xiaomi, etc.) to build a ROM with the users' best interest at heart? Doesn't make sense. That's why we buy devices that we can unlock, and break free. We should be supporting community ROMs and developers and help them to port features we need. There are lots of open source options out there (LOS, RR, etc.) that don't compromise your data or lock you in under the guise of "stability and security".
Thanks for reading.
Click to expand...
Click to collapse
Because OEMs are strictly regulated by various institutions, unlike developers. And even tho i love LOS, RR or any other custom rom, in 10years of flashing custom roms, i never had one that was more stable and bugfree than original OS that came with phone..
Incogn said:
Because OEMs are strictly regulated by various institutions, unlike developers. And even tho i love LOS, RR or any other custom rom, in 10years of flashing custom roms, i never had one that was more stable and bugfree than original OS that came with phone..
Click to expand...
Click to collapse
"Stable" is a relative term. My current custom ROM (Bootleggers) is very solid and probably has more features/options than MIUI ever will, I'm sure. More importantly, I know it doesn't do things behind my back and will not turn on me (eg. anti-rollback, etc.) down the road. Above all, quite often, custom ROMs get security patches long after the OEM has dropped support for the device. My $0.02.
temporarium said:
"Stable" is a relative term. My current custom ROM (Bootleggers) is very solid and probably has more features/options than MIUI ever will, I'm sure. More importantly, I know it doesn't do things behind my back and will not turn on me (eg. anti-rollback, etc.) down the road. Above all, quite often, custom ROMs get security patches long after the OEM has dropped support for the device. My $0.02.
Click to expand...
Click to collapse
Stable is not a relative term. Stable is stable, with all functions working, not crashing, and not having bugs. Features is different topic, stability and features are different thing. Most often the more features, the more trouble you have. You say its very solid, but if you go to thread and read comments, there are many different bugs and problems. You will never find that many different problems in official miui
Incogn said:
Stable is not a relative term. Stable is stable, with all functions working, not crashing, and not having bugs. Features is different topic, stability and features are different thing. Most often the more features, the more trouble you have. You say its very solid, but if you go to thread and read comments, there are many different bugs and problems. You will never find that many different problems in official miui
Click to expand...
Click to collapse
I have had zero FCs/crashes on my ROM. It's as stable as they get. And I trust it.
temporarium said:
I have had zero FCs/crashes on my ROM. It's as stable as they get. And I trust it.
Click to expand...
Click to collapse
Good for you then Sad about that bug you reported 2 days ago lol. Same for me with official firmware, which was created by same people who designed the phone and chose hardware . I mean i dont understand whats your point. Custom rom is better? If thats it, then 95% of owners will disagree, because they have no idea what custom rom, root, or unlocked bootloader is. Official roms are for casual users, who want phone to be reliable, simple, and functioning. They happen to be the vast majority of buyers. Custom roms are either for tech junkies, or people who like playing around with their tech and dont rely on their phone daily. If you discourage trusting companies like samsung, xiaomi, etc., why are you thrusting google? Its their OS after all, they wrote it. Sure, its based on open source linux, but its still googles code. You use google apps, that have all the permissions in the world. What can OEMs possibly take from you that google already didnt lol?
Incogn said:
Good for you then Sad about that bug you reported 2 days ago lol. Same for me with official firmware, which was created by same people who designed the phone and chose hardware . I mean i dont understand whats your point. Custom rom is better? If thats it, then 95% of owners will disagree, because they have no idea what custom rom, root, or unlocked bootloader is. Official roms are for casual users, who want phone to be reliable, simple, and functioning. They happen to be the vast majority of buyers. Custom roms are either for tech junkies, or people who like playing around with their tech and dont rely on their phone daily. If you discourage trusting companies like samsung, xiaomi, etc., why are you thrusting google? Its their OS after all, they wrote it. Sure, its based on open source linux, but its still googles code. You use google apps, that have all the permissions in the world. What can OEMs possibly take from you that google already didnt lol?
Click to expand...
Click to collapse
Thanks for contributing.
The "bug" was actually a misconfiguration on my part, not the ROM. I rely on my phone and use it daily with no issues.
XDA is geared towards the 5% that know what a custom ROM is and can make the choice.
I don't trust Google. I don't use Google apps. What I use is open. I've got microG installed so I don't leak my info all over the place. Custom ROMs allow you to do that. Official ROMs don't.
temporarium said:
Thanks for contributing.
The "bug" was actually a misconfiguration on my part, not the ROM. I rely on my phone and use it daily with no issues.
XDA is geared towards the 5% that know what a custom ROM is and can make the choice.
I don't trust Google. I don't use Google apps. What I use is open. I've got microG installed so I don't leak my info all over the place. Custom ROMs allow you to do that. Official ROMs don't.
Click to expand...
Click to collapse
Oh i agree to that, but still dont understand what your point was then..? And what does it have to do this topic?
Incogn said:
Oh i agree to that, but still dont understand what your point was then..? And what does it have to do this topic?
Click to expand...
Click to collapse
This is not the first device, nor the first OEM, that does things in an underhanded way, where you can never be sure if the next upgrade is going to take your device to a point of no return. My point being that the experience with ARB will (hopefully) alert other MIUI users to what may lie ahead and show Xiaomi that they don't approve. Just an opinion. ?
Hello everyone!
I have good news for you. After Huawei decided to stop providing the bootloader code, now we have another method to get it.
Unfortunately, it is a method that need to pay.
To the date I'm making this post, the cost is $30€.
Let me be clear:
I do not have a relationship with this people/team/person. I just want to share this method and prove that it works on the Mexican/Canadian model.
A good news, is that they accept PayPal.
If you want to try it, you have to do the following steps:
1.- Go to https://ministryofsolutions.com/huawei-bootloader-unlock-service-all-new-models-new-firmwares.
2. -Click: "Click here to order with PayPal".
3.- Now in your phone, go to the "phone" app and dial *#06#, you will see your IMEI and Serial Number.
3.5.- I suggest to copy those codes, and email you so you won´t have typing errors.
4.- Insert your IMEI and Serial Number into the webpage of ministry of solutions.
5. Make the payment with your paypal account.
6. After 24-48 hours, you will get the bootloader code in the email you used for paypal.
7. Be happy and unlock you bootloader.
I can ensure the web is working correctly. I unlocked mine a few moments ago, now I will rebrand
Thanks.
The guy can only sell 10 code per day, I need to wait tomorrow to order again..
maxfunky said:
The guy can only sell 10 code per day, I need to wait tomorrow to order again..
Click to expand...
Click to collapse
I suspect this means that his solution is not exploit based, but revolves around either working for Huawei, or knowing someone who does and getting the codes via them.
Doesn't bode well.
Whoever they are , fair play to them. There's obviously a market for them and they deserve the money.
That said , president of HUAWEI probably want more money so he closed their page and assigned Mutahhar
So bootloader unlocked , what will you guys do now with it ?
Will you install LOS or ?
mrcaligula said:
So bootloader unlocked , what will you guys do now with it ?
Will you install LOS or ?
Click to expand...
Click to collapse
I will give a chance to Huawei and Android Pie version they will make.
But I like LineageOS so much that I will install it in the future. I unlocked my bootloader (and have this fuc…. message each time I reboot the device) only to be able to install custom roms when I will like to do so.
Saison2018 said:
I will give a chance to Huawei and Android Pie version they will make.
But I like LineageOS so much that I will install it in the future. I unlocked my bootloader (and have this fuc…. message each time I reboot the device) only to be able to install custom roms when I will like to do so.
Click to expand...
Click to collapse
I have run official LOS on at least a half dozen different phones and I have never run a single build that didn't have bugs. Ever. I don't understand all the love for an OS that receives reports of new bugs from users after every single update.
jhs39 said:
I have run official LOS on at least a half dozen different phones and I have never run a single build that didn't have bugs. Ever. I don't understand all the love for an OS that receives reports of new bugs from users after every single update.
Click to expand...
Click to collapse
I fully understand your point and I am sure you have your reasons.
But for my point of view, this is exactly how a community should work. People making development could not do everything good every time.
Even big corporation do mistake. For example, my wife had trouble with her iPhone 7 and 12.0 (unable to connect to 5Ghz Wifi). After 12.0.1 it is correct.
On my devices, only some applications were not working correctly. I was able to use my devices on a daily basis, without restriction (personal mail, corporate mail with Outlook, Maps/Waze, listening to music, some games,...). And for my personal experience, updates went smooth, only some (less than 2 per year) went wrong. But I could always flash back and wait for the correction to be applied by people in charge.
The only drawback for me was the battery, it was difficult to length 1 day.
But again, I fully understand and you have the right to not choose LineageOS and use something else.
Saison2018 said:
I fully understand your point and I am sure you have your reasons.
But for my point of view, this is exactly how a community should work. People making development could not do everything good every time.
Even big corporation do mistake. For example, my wife had trouble with her iPhone 7 and 12.0 (unable to connect to 5Ghz Wifi). After 12.0.1 it is correct.
On my devices, only some applications were not working correctly. I was able to use my devices on a daily basis, without restriction (personal mail, corporate mail with Outlook, Maps/Waze, listening to music, some games,...). And for my personal experience, updates went smooth, only some (less than 2 per year) went wrong. But I could always flash back and wait for the correction to be applied by people in charge.
The only drawback for me was the battery, it was difficult to length 1 day.
But again, I fully understand and you have the right to not choose LineageOS and use something else.
Click to expand...
Click to collapse
I guess it has to do with how long I have been using custom ROMs. When I started using them years ago devs only worked on ROMs for devices they used themselves every day and the ROMs were not only stable enough to use as a daily driver but offered better performance and features than the stock ROM which is why people used them. Since the devs created ROMs for their own phones they were aware of bugs before posting builds. They didn't rely on users telling them what was wrong with every build after it was uploaded. When a custom ROM was labeled as stable it very rarely had any bugs.
Devs now routinely build or maintain ROMs for phones they don't use (or rarely use) so the ROMs always have bugs. I don't think custom ROMs are stable enough to use as daily drivers anymore but a lot of people seem to be fine with using custom ROMs that are slower and way more buggy than the stock ROM that comes on their phone. To each his own.
Why repost something a day later? https://forum.xda-developers.com/huawei-p20-pro/how-to/bootloader-unlock-service-t3852447
Because I can.
try this... good service and low price, tested on mine p20 pro from mexico..... https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
is this the same as unlocking your sim? im on telcell and i got zero updates, so im guessing i need to unlock it from telcel? or can i just unlock the bootloader with the code? and also, what do you do with the code once you have it?
estanenmi said:
try this... good service and low price, tested on mine p20 pro from mexico..... https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Click to expand...
Click to collapse
did you do this to get it off telcel?
DomAlberts said:
did you do this to get it off telcel?
Click to expand...
Click to collapse
yes for telcel
hey guys, i used funky Hauwei for rebranding from L04 to L29 international. and is working fine. im on l29(c636) but im working on erecovery now, im trying to get it to CLT-L29 9.0.0.108 but we will see. and i will let you know.
but the rebranding is a little tricky but works.
Okay update. Had to go back to L04 because when I went from 8 to pie while branded as L29. It wouldn't install due to compatibility issues. So had to rebrand back to L04. Recovery through funky Huawei. First 8 then 9 and worked perfectly. Only issues I have are with the telcel branding on start up. But all the bloatware I removed or disabled in CCleaner. So I don't have to look at the icons all the time. I'm currently running pie and it's awesome. Lots of cool new tweaks
Sent from my CLT-L04 using XDA-Developers Legacy app
hi
https://developers.google.com/android/images
Seems a little heavy for security only but I didn't find any descriptions when hitting the usual sites seeking the same. Guess we'll see...
Updated to may 2020 release and it broke my face unlock. had to call google for a replacement.......
But i still tried fixing this and i believe i may have found a fix, it worked for me anyway. I have an unlocked device so I already had the bootloader unlocked. I reverted the firmware all the way back to the very first release 10.0.0 (QD1A.190821.007, Oct 2019) and was able to set up device with a working face unlock on that release. Make sure to do a factory reset within the OS. After the device is completely set up I flashed the newest May 2020 update but I removed the -w from the flashall.bat so it would not wipe the device. I now have it working face unlock.
Just thought Id share. If anyone else has this issue hopefully this will help..
^^ this did not work for me ..
face unlock worked perfect for me
Is this caused by Android 11 DP3 face unlock broke
I did not have face unlock or any other issues, all went as usual. Install done via full imagine with wipe removed.
PaulPizz said:
Updated to may 2020 release and it broke my face unlock. had to call google for a replacement.......
But i still tried fixing this and i believe i may have found a fix, it worked for me anyway. I have an unlocked device so I already had the bootloader unlocked. I reverted the firmware all the way back to the very first release 10.0.0 (QD1A.190821.007, Oct 2019)and was able to set up device with a working face unlock on that release. Make sure to do a factory reset within the OS. After the device is completely set up I flashed the newest May 2020 update but I removed the -w from the flashall.bat so it would not wipe the device. I now have it working face unlock.
Just thought Id share. If anyone else has this issue hopefully this will help..
Click to expand...
Click to collapse
Do you think after a factory reset the face id will broke again?
deano121 said:
face unlock worked perfect for me
Click to expand...
Click to collapse
What did you do?
me too
all in all is fine and smooth
face unlock is good
soli work after root
PaulPizz said:
Updated to may 2020 release and it broke my face unlock. had to call google for a replacement.......
But i still tried fixing this and i believe i may have found a fix, it worked for me anyway. I have an unlocked device so I already had the bootloader unlocked. I reverted the firmware all the way back to the very first release 10.0.0 (QD1A.190821.007, Oct 2019) and was able to set up device with a working face unlock on that release. Make sure to do a factory reset within the OS. After the device is completely set up I flashed the newest May 2020 update but I removed the -w from the flashall.bat so it would not wipe the device. I now have it working face unlock.
Just thought Id share. If anyone else has this issue hopefully this will help..
Click to expand...
Click to collapse
That's odd. I had the exact same problem with my 4 XL, and the April update. Google replaced it. I know a couple other people had the same issue, and got theirs replaced as well. I wonder what's is going on....
jmartin72 said:
That's odd. I had the exact same problem with my 4 XL, and the April update. Google replaced it. I know a couple other people had the same issue, and got theirs replaced as well. I wonder what's is going on....
Click to expand...
Click to collapse
With how I was able to fix the issue I'm assuming it has to be some sort of software corruption issue. Man I do miss my fingerprint unlock...
Can anyone confirm whether this update has COVID contact tracing tools in the system menu? That stuff is creepy as hell, do not want.
kornesque said:
Can anyone confirm whether this update has COVID contact tracing tools in the system menu? That stuff is creepy as hell, do not want.
Click to expand...
Click to collapse
Can't see anything at the moment. Nothing creepy about it lol what's the worst that can happen
Mackay53 said:
Nothing creepy about it lol what's the worst that can happen
Click to expand...
Click to collapse
HIPPA violations and general surveillance concerns. Thanks for the check.
kornesque said:
Can anyone confirm whether this update has COVID contact tracing tools in the system menu? That stuff is creepy as hell, do not want.
Click to expand...
Click to collapse
Welcome to to NWO. I turn off my location services now. Google is already handing over all our locations data to big brother globally now. They’ve betrayed all our trust and privacy.
If you really want to know what will happen here, all the test runs are taking place in Wuhan. Their police forced them at check points to install a Covid tracking app. They’re currently going to test all 11 million residents there.
Sent from my iPad using Tapatalk Pro
Just remember that is China he is talking about and that stuff is really going
on there. Of course it is, they have a communist government. I watch the special on it a while back and it was crazy how they had everyone like literally locked down. And yes they did have the tracker and there is a lot of shady stuff.. their internet homes is controlled so even their Facebook accounts they aren't allowed to talk about certain things or people have disappeared. Like when they try to investigate what's going on there or oppose anything at the government says. I mean of course they're locked down is very extreme and a bit too much but it also helped them to get it under control and to s certain extent, that is really the only way to.
Our "stay at home orders" were a joke and now they are already over. But anyways, so yeah just normal communism going on over there. They are just being China. It is not a "test run" for the rest of the world. We already know that Trump isnt very keen on following what other countries are doing anyways. We saw first hand how China and Italy quickly got overrun by the coronavirus and had to lock down. we saw how highly contagious it was and how fast it could spread, especially when nothing was done about it. They only way to stop it was to lockdown and we saw how that helped. Trump by no means wad going to follow. He still to this day won't even wear a mask and we all know why, because he associates it with all of the Chinese people wearing them and he's a racist, to just be blunt. We barely did much to try and control the outbreak anyways, I honestly wish things would get more strict here and maybe we would make some actual substantial progress. We just need to stay focused on the real things that are going on and try not to get lead astray by conspiracies and such that will only cause us more unnecessary anxiety and fear.
Ok so I have a good segue, so I just rooted and I'm on DP4 and tried to use magisk modules and had to reflash the system to get it working again.. so there's no known magisk modules that are working on DP4 right now?
MicroMod777 said:
Welcome to to NWO. I turn off my location services now. Google is already handing over all our locations data to big brother globally now. They’ve betrayed all our trust and privacy.
If you really want to know what will happen here, all the test runs are taking place in Wuhan. Their police forced them at check points to install a Covid tracking app. They’re currently going to test all 11 million residents there.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
mrindependent said:
Aaaannnnnddd thats the que to switch back to the topic. Things are getting a little to crazy in here now kids. And just in case that unnecessary comment has gotten anyond thinking about it or maybe a little paranoid, just remember that is China he is talking about and that stuff is really going
on there. Of course it is, they have a communist government. I watch the special on it a while back and it was crazy how they had everyone like literally locked down. And yes they did have the tracker and there is a lot of shady stuff.. their internet homes is controlled so even their Facebook accounts they aren't allowed to talk about certain things or people have disappeared. Like when they try to investigate what's going on there or oppose anything at the government says. I mean of course they're locked down is very extreme and a bit too much but it also helped them to get it under control and to s certain extent, that is really the only way to.
Our "stay at home orders" were a joke and now they are already over. But anyways, so yeah just normal communism going on over there. They are just being China. It is not a "test run" for the rest of the world. We already know that Trump isnt very keen on following what other countries are doing anyways. We saw first hand how China and Italy quickly got overrun by the coronavirus and had to lock down. we saw how highly contagious it was and how fast it could spread, especially when nothing was done about it. They only way to stop it was to lockdown and we saw how that helped. Trump by no means wad going to follow. He still to this day won't even wear a mask and we all know why, because he associates it with all of the Chinese people wearing them and he's a racist, to just be blunt. So yeah let's get back to the topic. Remember there's always someone who has to push it to the next level.. but don't feed into it. We barely did much to try and control the outbreak anyways, I honestly wish things would get more strict here and maybe we would make some actual substantial progress. We need to worry about the real things that are going on, like that, rather than spreading conspiracies that don't even make sense and confuse and push anxiety and fear on others. Very distracting and malelevent.
Ok so I have a good segue, so I just rooted and I'm on DP4 and tried to use magisk modules and had to reflash the system to get it working again.. so there's no known magisk modules that are working on DP4 right now?
Click to expand...
Click to collapse
Well for Google sending an update soon for an embedded Covid tracker is concerning. Especially since they’ve giving this information over to our local governments, CDC, and WHO.
I recently reverted back to full stock, and relocked my bootloader. If and when this new Covid NWO tracking system gets pushed to our phones, I’ll unlock again, root, and delete all that NWO crap. We are the resistance aka, “”.
Sent from my iPad using Tapatalk Pro
Hey guys,
I posted on the other threads but it seems like my concern shifts to be another.
First off: Yes I have tried switching regions with the tutorials. No nothing happened. I switched back to EuEx, no dualism because I don't need it.
Yes I tried every possible EU VPN Tunnel and updating OTA.
Nothing helped.
Now I have searched for my current Firmware, and there is no actual discussion about it. It is CPH2025_11_A.52 I am on the security Patch Level December 2020. So it came to my mind that it could actually be the firmware that prevents the updatingprocess. Is this possible?
With every other EU-Colleague of mine getting at least C59 with EuEX I'm starting to think it's just my phone.
Is there something I can do about it or do I have to wait for a flashable Android 11 zip? Which would ultimately leave me with selling the phone since I purchased it in regards to receiving an android 11 smartphone.
Thanks for reading in advance!
No problem with your version ,its just Oppo s way of doing things.I have cph 2025.11.A50 november security patch.
I reached them and they said i should take my unit to service ,i asked them why?its not broken !
Very wierd solution.
My phone works like a charm ,great performance ,good battery life ,so im happy with the software.
P.s bought phone from Switzerland.
@andreiselegean1984 @CaptainRage while it may not be broken on the hardware level there definitely seems to be something wrong with it, so sending it in is not that weird a solution imho. There surely is some sort of repair service in your country that acts as an official Oppo partner for warranty repairs, so why not just contact them and see if they can help by just flashing the newest software onto it and be done with it. The only hassle being that you'll have to do without it for a couples of days but maybe you still have one of your older phones that you can use instead for the time being...
Well Oppo doesn't seem to be cooperating that much:
We are sorry to know that you didn’t receive the ColorOS 11 update on your Find X2 Pro just yet.
In order to clarify this for you, please allow us to offer you a background explanation.
To make sure everything of the new version can run smoothly and reduce the unnecessary risk of the end-user, the ColorOS 11 update is released in batches. This is a protective measure used in global leave for all the new software versions.That’s why a certain amount of devices don’t receive the update on the announced date. But don’t worry! As your satisfaction is our priority, we at OPPO are doing our best to release the update for your phone as soon as possible. Rest assured that you will receive ColorOS 11 soon.
I appreciate your understanding and wish you a wonderful day!
Click to expand...
Click to collapse
CaptainRage said:
Well Oppo doesn't seem to be cooperating that much:
Click to expand...
Click to collapse
This is just the usual BS the customer service gives you, forget about that. There have to be companies in your country that are official Oppo service partners which do all the repairs that are eligible for warranty. Contact one of them directly and tell them what the problem is and see if they accept it as a warranty repair.