I'm about to go for it and buy a 7 Pro, do we have an MSM Download Tool available yet here on XDA for the 7 Pro? I'm coming from the 6T and that tool is a MUST. Thanks guys!
No not yet. We have the files but its password protected.
slayerh4x said:
No not yet. We have the files but its password protected.
Click to expand...
Click to collapse
Ah thanks! That's how it all started with the 6T, password protected file. It's a matter of time though! Cool! :good:
You'll be waiting for two weeks or more. I set oem lock to "off" in settings, and then did "fastboot oem lock" like an idiot and I literally can't get into my phone at all now. All fastboot commands fail and I can't reboot into recovery either because it just says "your device is corrupt" every single time. I contacted oneplus support multiple times and they told me "we don't have anything available yet to help you, so you can just return it to us." Huge waste of time speaking to all those useless reps and I'm definitely not going to buy another oneplus product again. It's actually ridiculous that they don't just provide those tools upon release, especially when this issue has PERSISTED across all of their devices. I still have the phone for now, so if anyone finds a useful Oneplus rep who actually has the tools, or if someone figures out how to fix this issue, please let me know.
Lucifer6 said:
You'll be waiting for two weeks or more. I set oem lock to "off" in settings, and then did "fastboot oem lock" like an idiot and I literally can't get into my phone at all now. All fastboot commands fail and I can't reboot into recovery either because it just says "your device is corrupt" every single time. I contacted oneplus support multiple times and they told me "we don't have anything available yet to help you, so you can just return it to us." Huge waste of time speaking to all those useless reps and I'm definitely not going to buy another oneplus product again. It's actually ridiculous that they don't just provide those tools upon release, especially when this issue has PERSISTED across all of their devices. I still have the phone for now, so if anyone finds a useful Oneplus rep who actually has the tools, or if someone figures out how to fix this issue, please let me know.
Click to expand...
Click to collapse
1. If you do your research before just throwing fastboot commands you would have read that others on here have done the same, so do your homework.
2. If it's ridiculous that they don't just provide those tools upon release, especially when the issue has PERSISTED across all of their devices, then why run fastboot oem lock?
Everyone is always so quick to blame OEMs but not their own poor decision making. Take responsibility for your own actions even if you run them in cmd prompt.
T_VASS said:
1. If you do your research before just throwing fastboot commands you would have read that others on here have done the same, so do your homework.
2. If it's ridiculous that they don't just provide those tools upon release, especially when the issue has PERSISTED across all of their devices, then why run fastboot oem lock?
Everyone is always so quick to blame OEMs but not their own poor decision making. Take responsibility for your own actions even if you run them in cmd prompt.
Click to expand...
Click to collapse
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Lucifer6 said:
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Click to expand...
Click to collapse
LOL if I was a OP employee I would be helping out with the MSM tool! I cannot tell you the last device I rooted and installed ROMs on as its probably been close to 5 years and I see many things have changed. This is my first OP device since the original OP. I'll have my bin tonight but I am 99% sure I am going to wait for the MSM tool to come out whenever and do the international conversion that way. I hope you get everything sorted out!
Lucifer6 said:
You'll be waiting for two weeks or more. I set oem lock to "off" in settings, and then did "fastboot oem lock" like an idiot and I literally can't get into my phone at all now. All fastboot commands fail and I can't reboot into recovery either because it just says "your device is corrupt" every single time. I contacted oneplus support multiple times and they told me "we don't have anything available yet to help you, so you can just return it to us." Huge waste of time speaking to all those useless reps and I'm definitely not going to buy another oneplus product again. It's actually ridiculous that they don't just provide those tools upon release, especially when this issue has PERSISTED across all of their devices. I still have the phone for now, so if anyone finds a useful Oneplus rep who actually has the tools, or if someone figures out how to fix this issue, please let me know.
Click to expand...
Click to collapse
OOF! That's awful! I'm going to buy the 7 pro soon here, and as tempted as I am to root the device and start tampering with it, I'm going to wait until we have an MSM tool here to use. It's a must have.
Lucifer6 said:
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Click to expand...
Click to collapse
Really? You have been offered a fix! Send your phone on, and you'll have a working phone back weeks before the MSM tool is available. You are responsible, not OnePlus, SMH.
Sent from my GM1915 using Tapatalk
Anyone figure out the pSswared for the international msm file? Need it to flash my TMobile oneplus 7 pro to international it's getting bad battery life
Lucifer6 said:
Thank you for your reply. This is my first time owning a OnePlus device, so I hadn't looked at anything at on any of the community forums about it except how to root it and install magisk.
My last device was a razer phone 2, which had similar steps towards rooting it, and I actually did use "fastboot flashing lock_critical" to re-lock the bootloader after unlocking it, so I assumed that it would be the same for the oneplus, which in hindsight, obviously I was wrong.
But even if that was a minor screw up, I can't access the device at all, and that's what's bugging me. I do frequent backups, so having an option to erase all my data wouldn't be an issue if that was given, but not having that option at all and then bring told by OnePlus that the only option is to return it is absurd. I appreciate your feedback towards what I said, and if you are a OnePlus employee then I'm still standing by what I said and calling all of the 'support' I received useless, as it was just a waste of time and didn't lead to any sort of fix
Click to expand...
Click to collapse
Bashing OP support reps here is uncalled for. A rep can't help you because the method of trying to do what you want wasn't built into the software. Not the reps fault they can''t fix that they didn't build the software. Also OEM unlocking, rooting, flashing ROMs isn't covered by any type of warranty or support. So you better be thankful they are letting you send it in. If you choose to root, mod, or install software it's at your own risk.
TechOut said:
Bashing OP support reps here is uncalled for. A rep can't help you because the method of trying to do what you want wasn't built into the software. Not the reps fault they can''t fix that they didn't build the software. Also OEM unlocking, rooting, flashing ROMs isn't covered by any type of warranty or support. So you better be thankful they are letting you send it in. If you choose to root, mod, or install software it's at your own risk.
Click to expand...
Click to collapse
Yeah other people already said the same thing, thanks though!
I just need to get rid of the T-Mobile software. between the non fuctioning OnePlus site and the standard wait time it will be a month possibly before I get the unlock bin
Any new information around?
Enddo said:
Any new information around?
Click to expand...
Click to collapse
As far as I know, what we have is for the GM21AA for 9.5.3.
I think I saw one for the T-Mobile variant here as well, just haven't paid much attention there because I have AA model personally.
Not too sure about GM21BA either, someone add info for that here if you want.
Enddo said:
Any new information around?
Click to expand...
Click to collapse
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
Works like a charm, used it myself!
kimpreza said:
https://piunikaweb.com/2019/05/29/how-to-unbrick-oneplus-7-pro-using-msm-download-tool/
Works like a charm, used it myself!
Click to expand...
Click to collapse
NICE! Appreciate the info!
H4X0R46 said:
NICE! Appreciate the info!
Click to expand...
Click to collapse
I thought you had the 7pro already... I'm guessing I seen you on the 6t side
mlock420 said:
I thought you had the 7pro already... I'm guessing I seen you on the 6t side
Click to expand...
Click to collapse
I do! I have the global model so I tend to focus on stuff here that applies to my model lol I had the 6T for a while but did move over to the 7 Pro.
Related
Hey there,
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked. By the magic operation of Jesus maybe, who knows.
It don't boot, I don't see anything on the screen, I don't know if it is turned on or off… It just won't reply. To anything, fastboot, adb or whatever else. I can't boot in recovery or something else.
I think I have a splendid bricked late-2013 phone… I followed some tutorials to unbrick phones, the power + trick, but nothing.
The only thing I have on a windows computer is a "tadam" when I plug the USB, but that's it, no fastboot or adb, no screen, nada. But this sound of a plugged USB device. Knuh…
What the hell can I do ?
Shall I call Google tomorrow for RMA ?
ps: i saw some threads like me, i followed replies, but after a 4 hours searching, I don't wake up my phone
Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937
esskayy said:
Have you given this a try? http://forum.xda-developers.com/showthread.php?t=2513937
Click to expand...
Click to collapse
yap, but no more results…
I think I tried all solutions on xda, no one worked :s
Flayks said:
yap, but no more results…
I think I tried all solutions on xda, no one worked :s
Click to expand...
Click to collapse
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.
esskayy said:
Hmmm... sounds like your bootloader is corrupt dude Weird, you are like the third today who has bricked the Nexus. All you can do now is RMA it and hope for the best.
Click to expand...
Click to collapse
Damned… why
Please, Google, don't be cruel with me
Flayks said:
Damned… why
Please, Google, don't be cruel with me
Click to expand...
Click to collapse
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader
esskayy said:
If the phone is truly bricked, and it seems like it is, then Google won't be able to boot up the phone so they won't know you've unlocked the bootloader
Click to expand...
Click to collapse
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
doesn't boot*
*grammar police*
Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA
Flayks said:
That's what I think too, but how to explain that like someone don't know what is about… "helow my phone won't boot, it is black, I can't do anything… send me another one, please"? :cyclops:
Click to expand...
Click to collapse
That would work. Just don't say "send me another" ask "what do I do now"
apristel said:
doesn't boot*
*grammar police*
Click to expand...
Click to collapse
ups, thx.
esskayy said:
Yh, that will work There are legitimate cases of phones not booting up so they may think you are one of them. Also I doubt the Google representative will care much for the reason. Their job is just to arrange the RMA
Click to expand...
Click to collapse
Yep, I will call the support…
jd1639 said:
That would work. Just don't say "send me another" ask "what do I do now"
Click to expand...
Click to collapse
I would like to…
Thankz!
" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.
apristel said:
" I messed up my phone, even though it was completely fine when I bought it, I'll accuse google of producing a bad / faulty phone. "
Sounds legit.
If you CANNOT afford the risk that comes with modding, DONT do it. You/others who do this are very disgusting. GOOGLE did nothing wrong. YOUR phone was fine when you got it. Don't be a chump. You have to PAY to play.
MODS I'd close this thread due to FRAUD.. I HATE threads like this, People f/up their phones and expect everyone else to pay.
Click to expand...
Click to collapse
How do you know the phone isn't booting due to his bootloader being unlocked? He even said it was fine and it was not booting today....
Sent from my Nexus 5 using XDA Premium 4 mobile app
Because it booted afterwards. Thats how. .
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse
apristel said:
Because it booted afterwards. Thats how.
Quote:
I received my Nexus 5 some days ago, I rooted it with the CF-AutoRoot, it worked fine, but since today, it is bricked.
Click to expand...
Click to collapse
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…
Flayks said:
Maybe I was not clear in my first message but I rooted it, yes, but it worked! Since 3 days it works. But today, I really don't know why, I don't update or something else like changing rom (I'm on stock rom etc), it doesn't boot anymore.
That's it…
Click to expand...
Click to collapse
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.
Dude you need to chill a little. Unlocking your bootloader does not completely null warranty. If you brick your phone via software then you are responsible.
By the sounds of what is happening with the op, he has not changed anything to end up in this predicament. As with the other purple with similar problems (unlocking bootloader resulting in brick) can hardly be pointed at them.
Clearly something is happening which is out of user control which is causing these bricks.
If the ROM fails to boot it will throw you back to the bootloader.
If the bootloader fails you have a brick (not 100% true but not going into that now)
The facts are that the op has unlocked the bootloader which is a legitimate task and has for unknown reasons ended up with a corrupt bootloader.
This should still be covered as the op has not fine anything to solicit what had happened.
Sent from my Nexus 4 using xda app-developers app
apristel said:
I feel for you that your phone isn't working. Fraud isnt the answer. do you HONESTLY feel you'd get the same answer from Google if you told them that you rooted/unlocked and now your phone isn't working?
just saying that those who f up and make everyone pay for it are wrong. I personally like paying 400 for the 32gb device. I'd rather not pay 500 because of people who mess up and now make the cost/device go up due to rma's that are not legit.
Code:
The issuance of an RMA/RGA is a key gatekeeping moment in the reverse logistics cycle, providing the vendor with a final opportunity to diagnose and correct the customer's problem with the product (such as improper installation or configuration) before it is returned. As returns are costly for the vendor and inconvenient for the customer, any return that can be prevented benefits both parties.
Click to expand...
Click to collapse
Personally from my own experience, as the disclaimer on the bootloader unlock screen states 'This MAY void your warranty', telling Google the truth would be his best bet. Call Google, advise that the bootloader was unlocked and worked for 3 days and then it suddenly stopped booting.
If you bought a Nexus 5 and don't plan to do anything to it then that's up to you. However some of us buy Nexus devices because of the ease of development on them. Google facilitate this with the ability to unlock the bootloader and have no justifiable reason to refuse an RMA when all the OP has done is unlock said bootloader.
Why don't YOU stop being a **** and get off this thread. Please.
Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others
daniel.kusy said:
Anyone else bricked their phone like this? Managed to un-brick mine from an identical situation, if anyone is still stuck like I was I'll try and make a little "guide" to help others
Click to expand...
Click to collapse
Apparently yes, I'm not the only one. It would be great if you try to explain your solution!
So I just got a Zenphone6 and I'm following this guide to install LineageOS
https://wiki.lineageos.org/devices/I01WD/install
but got hold up at the "Unlocking the bootloader" step, because while running the app on the device it wanted me to agree to a number of terms and also connect to Asus to report my IMEI and possible other info. As I hadn't setup any network connection the app wouldn't proceed.
This disturbed me quite a bit, I've just parted with a fair amount of hard earned cash to buy a piece of hardware and it turned out I couldn't take full control of it.
So my question is, is there any way to sidestep the official unlocking tool?
No
Marlin79 said:
So I just got a Zenphone6 and I'm following this guide to install LineageOS
but got hold up at the "Unlocking the bootloader" step, because while running the app on the device it wanted me to agree to a number of terms and also connect to Asus to report my IMEI and possible other info. As I hadn't setup any network connection the app wouldn't proceed.
This disturbed me quite a bit, I've just parted with a fair amount of hard earned cash to buy a piece of hardware and it turned out I couldn't take full control of it.
So my question is, is there any way to sidestep the official unlocking tool?
Click to expand...
Click to collapse
I want to join this question, I really disappointed by such ASUS's policy. Too bad I can't give the phone back. If I wanted this kind of policy, I'd buy half priced Xiaomi.
By the way, have you tried 'fastboot oem unlock' command after allowing unlocking in Developer Options?
I don't see "Allow OEM Unlock" anywhere in Developer Settings.
Also interested in this. I figured since Asus is supporting devs, they would make unlocking as easy as Google/Oneplus does with their phones. Guess not.
Anyone tried this "unofficial" method?
https://forum.xda-developers.com/showpost.php?p=80113454&postcount=51
Satoso said:
Also interested in this. I figured since Asus is supporting devs, they would make unlocking as easy as Google/Oneplus does with their phones. Guess not.
Anyone tried this "unofficial" method?
https://forum.xda-developers.com/showpost.php?p=80113454&postcount=51
Click to expand...
Click to collapse
I took a plunge and got the phone, and this method doesn't work. Only the official one does, which as OP says will require an internet connect and probably does transmit the IMEI number and so on.
However, it doesn't require you to connect to a Google account as mentioned in the official Lineage instructions. So I guess that's a partial consolation.
Still, since Asus is in touch with the devs here, it would be great if someone can put forth a suggestion to drop this "phone-home" requirement. It's the only way they can compete with the more dev-friendly Oneplus.
I wish that there was a way. I really want to unlock the bootloader but I'm on the 10 beta and the official unlock tool does not work because of this. There doesn't appear to be a way to roll back to P either unfortunately so I'm stuck for now I guess
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.
I was wondering if anyone else purchased the unlocked version from Samsung and it arrived with Developer options already enabled.
I have never seen that before, so it made me wonder if somehow I was receiving a device that had been returned. There don't appear to be any issues (packaging was sealed, device appeared new, etc).
The alternative would be that it restore the menu as part of the transfer from a Galaxy Note 20 Ultra backup, but this would be the first time. The Note 20 was restored from an S10 Plus, but the settings had to be enabled again on the new device.
twistedumbrella said:
I was wondering if anyone else purchased the unlocked version from Samsung and it arrived with Developer options already enabled.
I have never seen that before, so it made me wonder if somehow I was receiving a device that had been returned. There don't appear to be any major issues (packaging was sealed, device appeared new, etc) beyond the bootloader appearing to possibly be unlocked, as well.
The alternative would be that it restore the menu as part of the transfer from a Galaxy Note 20 Ultra backup, but this would be the first time. The Note 20 was restored from an S10 Plus, but the settings had to be enabled again on the new device. I don't see them whitelisting that.
Click to expand...
Click to collapse
Maybe an engineering build fell into the production line by mistake, please check if it's an engineering build
That would be a game changer, for people developing custom roms and gaming drivers for it
flairepathos.info said:
Maybe an engineering build fell into the production line by mistake, please check if it's an engineering build
That would be a game changer, for people developing custom roms and gaming drivers for it
Click to expand...
Click to collapse
Samsung claimed it was "a new change for the ease of our users" until I questioned it. It then became a software glitch. I don't know
twistedumbrella said:
Samsung claimed it was "a new change for the ease of our users" until I questioned it. It then became a software glitch. I don't know
Click to expand...
Click to collapse
Ohhh yeah remember they are getting pooped on for disabling cameras if you unlock your bootloader LOL this is just fantastic
flairepathos.info said:
Ohhh yeah remember they are getting pooped on for disabling cameras if you unlock your bootloader LOL this is just fantastic
Click to expand...
Click to collapse
That's the Fold, not the Flip.
twistedumbrella said:
That's the Fold, not the Flip.
Click to expand...
Click to collapse
Oh well XD
So Samsung support is a lot like Amazon. If it isn't in the FAQs, they attempt to make up an answer or connect you to someone else. Pretty sure I could have spent an hour getting help trying to make calls on my toaster if I sounded confident it's possible.
I was initially asked for my IMEI to answer the question. I asked how a device that just released would have an expired warranty, but was told it was to verify the device was new. After giving it, I was told about having the premium warranty...
This led to being told how the option was enabled as a new way to make things easier on the user. When asking why they enabled something that could potentially void my warranty, I was sent to someone else who claimed it was a glitch. When asking why the OEM unlock option was missing (which I later found has a time delay on newer devices), I was put on hold for 15 minutes.
I finally said I had somewhere to be and was told they were happy to have helped. I still don't know if it was part of the restore, but i'll be waiting the week to make sure OEM unlock appears before I go back to discuss a defective firmware.
I did a restore from my s21 Ultra and the developer options was not enabled. Also oem unlock was there from the first second I enabled it.
Interesting... I am torn between wiping to find out if that fixes it and trying to fix it first to end up wiping it anyway.
Hello,
Is unlocking bootloader is essential for
1) custom kernel
2) custom recovery
3) custom ROMs ?
The reason I am asking is the ultimately stupid waiting period of 7 days to unlock a bootloader, while my device is plagued with a thoroughly random touch freeze problem that makes using it practically useless. I would like to know if I have to swap this device for another out of the blue or an optimized kernel/ROM will solve my problems however Xiaomi decided that waiting for a week first is a requirement above all.
Thanks in advance.
Yes
Pretended said:
Hello,
Is unlocking bootloader is essential for
1) custom kernel
2) custom recovery
3) custom ROMs ?
The reason I am asking is the ultimately stupid waiting period of 7 days to unlock a bootloader, while my device is plagued with a thoroughly random touch freeze problem that makes using it practically useless. I would like to know if I have to swap this device for another out of the blue or an optimized kernel/ROM will solve my problems however Xiaomi decided that waiting for a week first is a requirement above all.
Thanks in advance.
Click to expand...
Click to collapse
If you have problems with stock device, I would recommend RMA instead of installing custom software. Chances are it won't improve anything.
"The reason I am asking is the ultimately stupid waiting period of 7 days to unlock a bootloader" ... Stupid period of 7 days? 7 days of waiting are great and senseful solution, have a look @huawei, they wont let you unlock bl even after 10 years ..... And Xiaomi is supported by several tools for working with unlocked bl...
borisku said:
"The reason I am asking is the ultimately stupid waiting period of 7 days to unlock a bootloader" ... Stupid period of 7 days? 7 days of waiting are great and senseful solution, have a look @huawei, they wont let you unlock bl even after 10 years ..... And Xiaomi is supported by several tools for working with unlocked bl...
Click to expand...
Click to collapse
Well, having used Samsung devices only prior to this, 7 days of waiting time is utterly frustrating. Didn't know about Huawei - makes me darn sure about not purchasing a Chinese brand again.
The platform I had bought my phone went out of business and apparently I got no electronic invoice to work with. So RMA'ing is effectively out of options. Thank you tho.
Pretended said:
7 days of waiting time is utterly frustrating
Click to expand...
Click to collapse
Not just the waiting period, the whole process is frustrating. This short thread helped me with the issues I was having with their unlock tool.
Thank you too for the reply and the link but apparently 7 days of waiting time is a must. I am at that stage already and was looking for ways to circumvent it, if any.
Getting rid of this garbage called Poco and splashing my hard earned cash on Samsung - at least there is some hope at various ends.
Pretended said:
I am at that stage already and was looking for ways to circumvent it, if any.
Click to expand...
Click to collapse
No way to circumvent it, boot is encrypted and can only be unlocked via the official tool. Just wait...