Related
I thought that this post was best placed on the Lenovo forum but apaarently not, as it mysteriously dissappeared straight after I posted it. Perhaps those ownsers will find this one -
"Why Lenovo P2 is not getting Nougat update in UK?" – 25 pages and counting…
"Update to Android O" – 31 pages and counting…
"Unable to sync gmail contacts properly" – 18 pages and counting…
"Re: P2 - Notification Problem!" – 4 pages and counting…
And that doesn’t include all the other threads relating to these subject, there and on other sites.
Lenovo, or more specifically, the people at Lenovo should be ashamed. Not because they have created something with defects, no-one/nothing is perfect, but because they aren’t willing (or able) to come out and admit it. It would save a great deal of time, effort and possibly money, if someone in a position we could trust would just state, in writing, that –
There won’t be any security or operating software updates for the P2.
There will be/is no software/settings fix for the lack of notification and/or contacts sync.
Software changes are fairly cheap and simple (if anything relating to modern tech could be described as such) whereas hardware is not.
Just admit that, embarrassing as it may be, the P2 is flawed.
Promise your P2 customers that you’ve made changes to the way you do things and that (hopefully) it won’t happen again.
Thank those same customers for buying the P2 in the first place and apologize that you’ve let them down. Maybe then, some of those customers (and new ones) might buy Lenovo products.
Or is it too much to acknowledge that Motorola could do it but they couldn’t?
Or are they too worried that Google, not wanting to be linked with the bugs, will end their agreement to allow them to use Android?
On paper, the P2 is a great piece of kit, that’s why I bought one. However, if all I wanted was something to make and receive calls and to send and receive texts (plus a few extras), I’d still be using my 5310 with its replaceable battery. If I could afford to, I’d buy something else now but, safe to say, when I can, it won’t be a Lenovo, or a Motorola, just in case they get infected by association. Maybe a Google phone, you’d think that they would know how the software and hardware will work together, and I’ll get updates.
I clearly understand why you're fed up with it. Lenovo does really nearly to nothing to support the P2.
In my case, I knew from the get to that I would reflash my phone with a custom rom since stock never came close to them. In any case.
I have used stock AOSP on this phone as well, bugless, fast and stable.
Custom rom can have bugs as well but they are fixable or at least not noticeable. Not all of them though.
Wile_E_Coyote said:
I thought that this post was best placed on the Lenovo forum but apaarently not, as it mysteriously dissappeared straight after I posted it. Perhaps those ownsers will find this one -
"Why Lenovo P2 is not getting Nougat update in UK?" – 25 pages and counting…
"Update to Android O" – 31 pages and counting…
"Unable to sync gmail contacts properly" – 18 pages and counting…
"Re: P2 - Notification Problem!" – 4 pages and counting…
And that doesn’t include all the other threads relating to these subject, there and on other sites.
Lenovo, or more specifically, the people at Lenovo should be ashamed. Not because they have created something with defects, no-one/nothing is perfect, but because they aren’t willing (or able) to come out and admit it. It would save a great deal of time, effort and possibly money, if someone in a position we could trust would just state, in writing, that –
There won’t be any security or operating software updates for the P2.
There will be/is no software/settings fix for the lack of notification and/or contacts sync.
Software changes are fairly cheap and simple (if anything relating to modern tech could be described as such) whereas hardware is not.
Just admit that, embarrassing as it may be, the P2 is flawed.
Promise your P2 customers that you’ve made changes to the way you do things and that (hopefully) it won’t happen again.
Thank those same customers for buying the P2 in the first place and apologize that you’ve let them down. Maybe then, some of those customers (and new ones) might buy Lenovo products.
Or is it too much to acknowledge that Motorola could do it but they couldn’t?
Or are they too worried that Google, not wanting to be linked with the bugs, will end their agreement to allow them to use Android?
On paper, the P2 is a great piece of kit, that’s why I bought one. However, if all I wanted was something to make and receive calls and to send and receive texts (plus a few extras), I’d still be using my 5310 with its replaceable battery. If I could afford to, I’d buy something else now but, safe to say, when I can, it won’t be a Lenovo, or a Motorola, just in case they get infected by association. Maybe a Google phone, you’d think that they would know how the software and hardware will work together, and I’ll get updates.
Click to expand...
Click to collapse
Lucky we have our devs
sm00th4f3 said:
I clearly understand why you're fed up with it. Lenovo does really nearly to nothing to support the P2.
In my case, I knew from the get to that I would reflash my phone with a custom rom since stock never came close to them. In any case.
I have used stock AOSP on this phone as well, bugless, fast and stable.
Custom rom can have bugs as well but they are fixable or at least not noticeable. Not all of them though.
Click to expand...
Click to collapse
Another option to add to the list and something (as a newcomer to Android and mobile phone modding) I'm having to learn and it's a pretty steep learning curve.
After going round in ever decreasing circles until I very nearly disappeared up my own orifice over the last few months, I decided to do nothing and to just put up with things as they are. For every post that says what they did helped, there is another saying it didn’t work for them and for every updated OS there is one asking how to get back to Stock MM.
Stock ROMs, Rooting, 7, 7.1.2, 8, 8.1…the options seem endless and scary! If someone else bricks you phone, at least you can blame them but if you bring the misery on yourself…
You say you used a stock AOSP, If you don't mind, could you say which one and how you did it (with any snags you came across). You also note that there are still some bugs. What are they? If I can live with them instead of the ones I’ve got, I certainly consider doing it.
For first time you can't go wrong with the official LineageOS. Just go to their website and check the wiki, it has a comprehensive guide for flashing from the beginning and it will be fine if you follow it.
XDAquareis said:
For first time you can't go wrong with the official LineageOS. Just go to their website and check the wiki, it has a comprehensive guide for flashing from the beginning and it will be fine if you follow it.
Click to expand...
Click to collapse
Apologies for being so hesitant but having never done it before, it's a big, scary step (where have I heard that before...oh, yes...). You used the word "official", there are lots of LineageOS for the Lenovo P2 but no mention of "official", is one of the nightly builds okay to use?
Wile_E_Coyote said:
Apologies for being so hesitant but having never done it before, it's a big, scary step (where have I heard that before...oh, yes...). You used the word "official", there are lots of LineageOS for the Lenovo P2 but no mention of "official", is one of the nightly builds okay to use?
Click to expand...
Click to collapse
Yes, but I wouldn't recommend los 14.1
Use a Oreo rom by subham or firelord.
sm00th4f3 said:
I clearly understand why you're fed up with it. Lenovo does really nearly to nothing to support the P2.
In my case, I knew from the get to that I would reflash my phone with a custom rom since stock never came close to them. In any case.
I have used stock AOSP on this phone as well, bugless, fast and stable.
Custom rom can have bugs as well but they are fixable or at least not noticeable. Not all of them though.
Click to expand...
Click to collapse
b50corei5 said:
Yes, but I wouldn't recommend los 14.1
Use a Oreo rom by subham or firelord.
Click to expand...
Click to collapse
Many thanks for your time and advice.
[ROM][8.1.x][kuntao][OFFICIAL] Cardinal-AOSP - It's all a bit scary but I'm going for it! :fingers-crossed:
Wile_E_Coyote said:
Many thanks for your time and advice.
[ROM][8.1.x][kuntao][OFFICIAL] Cardinal-AOSP - It's all a bit scary but I'm going for it! :fingers-crossed:
Click to expand...
Click to collapse
Good luck ?
Remember to do a backup before you start
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
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.
My Phone just got a notification again for 2.55.401.3 which is from 28/09/2020
Note: My phone is already on 2.55.401.3 since last year.
Anyone get this notification?
It seems dodgy given its over a year old.
Yes, I got the same update, 1.6 GB update with no changes at all.
HTC.
mm_farahat said:
Yes, I got the same update, 1.6 GB update with no changes at all.
HTC.
Click to expand...
Click to collapse
Seems odd right? - I won't be touching it for the meanwhile.
I've reached out to HTC but god knows if they'll bother getting back.
I don't think they will ever reply, htc has one of the worst community support teams
OTA_IMAGINE_DUGL_P90_SENSE10GP_MR_HTC_Europe_2.55.401.3-2.55.401.1_release_551492 100MB
OTA_IMAGINE_DUGL_P90_SENSE10GP_MR_HTC_Europe_2.55.401.3_R1_sdm845-000041c-1906261449_release_554601 1.65GB
nenebear said:
OTA_IMAGINE_DUGL_P90_SENSE10GP_MR_HTC_Europe_2.55.401.3-2.55.401.1_release_551492 100MB
OTA_IMAGINE_DUGL_P90_SENSE10GP_MR_HTC_Europe_2.55.401.3_R1_sdm845-000041c-1906261449_release_554601 1.65GB
Click to expand...
Click to collapse
Is it legit then? - I couldn't find any info about this online.
No update since 01/09/2019 (2.55.401.1) and today, a new firmware => 2.55.401.3. I made a successful update and after restart => 2.55.401.1 from 01/09/2019 ...
No Android 10, 11 => HTC sucks !!! I bought HTC smartphone since QTEK 1010 (2003, near 20 years) and they **** on their customers 2 lasts years...
I will never buy HTC product !
@ShadowTrader: did HTC reply you?
@nenebear : do you happen to know what is chanfged? Security patch level is still at August 2020?
Maybe it is a patch for Log4J vulnerability?
Also, I tried to contact HTC but the first thing they ask on their support website is my phone's IMEI. As soon as I enter it, I'm told my phone is out of warranty and It won't even let me chat with someone
Is it possible they are coming again for smartphone manufacturing? Maybe they are building teams to develop and continue from where they stopped with u12+... That would be cool to see. I'm not expecting any major update for u12+ but I would like to see them to make smartphones again and keep their word like before.
Being using htc since the m7 and that was the best experience I had with any brand I owned so far! Good software and hardware! No one needs updates every month when it is working as expected! And the updates always had some increment in functionality and usability!
But maybe I'm just daydreaming ahaha
Hello XDA!
First of all, long time lurker, but infrequent poster here. My phone is an Asus ROG Phone 5s Pro running stock and non-beta software and is not rooted. I am reaching out to see if anyone on here who has more technical savvy than me (which is probably most of y'all) can help me figure out how to reinstall a fresh factory image on my Asus ROG Phone 5s Pro or can offer any other possible solutions for my issue.
The reason I am wanting to do this is because I recently installed a software update from Asus that seems to have a persistent issue that is a pretty major problem to me. The issue is that whenever I reboot the phone and plug in headphones and audio plays, but it stutters and BLASTS out of the headphones (multiple sources tried, even happens with system notification sounds). This only happens with wired headphones and never with Bluetooth. I had this happen to me once for less than a half a second and my ears were persistently ringing for about 3+ hours after this and I am certain that it damaged my hearing to a small degree. Because of this I no longer trust to use any headphones with the phone and this is a huge bummer because I use wired headphones A LOT.
I have tried to factory reset the phone several times already and the issue persists through without any restoring of anything during setup (in fact it won't recognize the backup that it created the day before the factory reset), but the issue is still present. I contacted Asus customer support (for which lets just say I have strong feelings on) and explained the issue and they want me to RMA the phone for a hardware issue.
I really do not wish to do this as this means I will have to either switch phones a few times which is always incredibly time consuming or be without a phone for an estimated period of up to 10 days if I do the RMA. I also disagree that this is a hardware issue because of two things: 1) if it were a hardware issue then I would think that the problem would be constant and not happen just once after each reboot and I would think that doing something in the software, i.e. a reboot, wouldn't consistently recreate the problem. Thus I am trying to find a way to "restore" the operating system of this device to see if I can solve what I believe to be a software issue that shouldn't require any RMA.
I have seen that posts that linked official files from Asus before, such as the "AsusUnlock_1.0.0.7_210127_fulldpi.apk" found in the OP of the "Install any custom ROM on ROG Phone 5 / 5s (GSI)" thread here in this very forum. Is anyone aware of any officially sourced files for stock software/firmware for this phone and a process through which I could reinstall it?
I am also open to thoughts and other possible options to consider.
Also I will give bonus points to anyone who can help me figure out how to fix the issue where my Google backup by this very same phone won't restore its own Google backup when going through the setup and can help me restore it. It does recognize a different Google backup for a tablet that is set up for my child to use, so it is not an issue with the restore being completely broken.
Thanks in advance for anyone willing to try and lend a hand.
Hi, here you can find stock firmwares make sure you got for right region.
ROG Phone 5s Pro | Gaming Phones｜ROG - Republic of Gamers｜ROG Global
Fueled for winning by the latest Qualcomm® Snapdragon® 888+ 5G mobile platform, ROG Phone 5s Pro launches your mobile gaming experience into the next dimension. With an unbelievably responsive 360 Hz native touch-sampling rate, the 144 Hz / 1 ms display brings you the smoothest ever viewing...
rog.asus.com
Yeah, just for additional info for anyone who finds this. I've also been working with ASUS customer support. I was given two links on flashing official firmware:
Unofficial guide on flashing - https://www.asus.com/support/FAQ/1009748/
Official firmware images - https://rog.asus.com/phones/rog-phone-5s-pro-model/helpdesk_bios (same as previous comment above; thanks Teddy)
When I asked why my version is newer than any they currently have listed on the site I was told that it "could be a preview release given directly by Google" (I doubt this as this appeared as an official OTA by Asus that had very specific patch notes to this phone in it) and that because my version is newer than any listed on their site would result in trouble if I tried to flash the newest version listed, but an older firmware than what is currently installed and that I should still just RMA my phone.
For reference my current firmware is RKQ1.210303.002.WW_Phone-18.1220.2201.186 and the latest firmware listed on their site at the time of this writing is WW-18.1220.2111.164.
Great phone (aside from the hearing damage), but utterly useless support.
Still open to thoughts and ideas though if anyone still has any.
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Andrologic said:
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Click to expand...
Click to collapse
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
ChrisMills83 said:
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
Click to expand...
Click to collapse
There are links to download RAW images along with guides in the help thread pinned to the top of this forum. You should find what you need there. The RAW's come include flash scripts that does it all for you.
Just curious for opinions while this thread is still going:
Does anyone lean towards my issue being a hardware problem or something else (and if you could be specific and suggest something for me to try about it)?
The reason why I ask is because I personally feel like this is an issue with when the headphone jack initializes output or something because it only ever blasts audio after a reboot and I any audio plays. After it stops and plays again the levels seems to return to normal. I can also reliably make this happen the same way every single time. Finally (and somewhat conspiratorially), the update I installed just before this started to happen had patch notes that included "optimized audio parameters."
My appreciation in advance for any thoughts and insights.