So my phone is Doogee S90. In the beginning everything started with unlocking the bootloader, root and flashing TWRP recovery mode, but i softbricked it and somehow found an old stock firmware update from 2018. I fixed the phone successfully with it, then removed the root, locked the bootloader and started the phone, it works, but i cant update it to the latest version cuz it just can't find it, my currently version is Doogee_S90_Android8.1-20181116_20181123-1523 and the latest is DOOGEE_S90_Android8.1-20190629_20190629-1831. I searched everywhere, but cant find it and cant update it to the latest version, so if someone can make me backup from the latest one as firmware image will be great or atleast tell me how to fix the "Wireless Update" to get the latest version, please.
btw, if this Thread is not in the correct category, please tell me where it has to be or just move it.
My phone is Chinese variant running miui 11 Android 9 and i installed the anti brick from the mega thread. Now i have an Android 10 update and i downloaded the update for 3 times but Everytime it says update.zip is corrupted during update process. I also tried with choose update package to update manually but same results. How can i overcome this problem?
This thread?
Not sure, since it's pretty long ago that i used to flash custom recovery's and roms, but if you have TWRP as your recovery i don think you're able to flash official firmware. Also read something in that thread about Android 10 and Anti Brick not going along very well. My best guess is; get rid of TWRP and Anti Brick by flashing the correct official firmware for your device via Fastboot.
Try and find a very very VERY clear howto. Lots of reading and caution = not bricking your device.
Update: I managed to figure out that the Beta 08 predated the latest stable release 10.0.13, which I also found by searching. Since 10.0.13 is newer than Beta 08, I'm good.
This 7T is making me feel like I haven't spent the last six years reading XDA threads.
So I bought a 1907 converted to global firmware with the bootloader unlocked from Swappa. Now that it's here I find it has the open beta on it (OP7T_02_BETA_08) which I would prefer to roll back to stable. Something tells me there is not yet a roll back zip for this beta but a preliminary search didn't help. So if you know of a zip, tia.
Android 10 introduced a lot of powerful new tools to the Oneplus space and the only one I am familiar with is the fastboot roms (thanks! They're a lifesaver). I have not used the MSM tool, etc. I have never rolled back an OP beta. I can't even find a page about the OP 7T betas, although I assume the seller has the latest one on this phone. I'm ok using one of these tools if I do it now, since I have not yet put any personal data on the device.
As I see it these are my options from most desirable down:
1) Roll back to 10.0.12 or 10.0.13 assuming there is a roll back zip and I have instructions on how to use it.
2) Use a tool that is new to me to roll back.
3) Live with beta and simply root it via the fastboot flash method.
As for rooting the beta, can I use any of the prepatched boot img's here, which was my intention when I thought I was getting global stable? Or is the easiest thing to do just to boot the unofficial twrp and flash the latest Magisk zip (20.4?)? I think that's probably easiest.
So assuming a roll back to stable isn't possible now, and I root the beta by whatever means, how do I get back to stable eventually? I know this has been answered very often but I have never wanted to deal with betas over 3 different OP phones so if you'd indulge me with basic explanations/links I'd appreciate it. Thanks.
Download the OnePlus 7T - Global
Flash from your phone in the system settings then reboot, it will wipe everything after it boots back up go thru the setup quickly and do a factory reset one more time from the settings and your set. After that just download Oxygen Updater and catch up to the current update.
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.O.10_OTA_010_all_2002022101_downgrade_0ab28576e1914b50.zip
Hi, im on 12.5.11.0.RJSEUXM and I want to upgrade to miui 13, but after downloading the zip, and trying to install it with the updater app (choosing a zip from menu) its says "unable to verify, you cant install this stable rom"
Is there any way to fix that and install the rom? putting that zip as "update.zip" at the root of my internal storage and booting into recovery does nothing (in previos versions an option called "update.zip to system" was there)
Or I need to do something more to update?
Thanks.
Each recovery ROM seems to be verified at Xiaomi servers during upgrade process and if they block the installation for whatever reason, you're out of luck. The reason might be that the ROM is supposed to be used only by selected testers, in a specific region or maybe the ROM was pulled due to major bugs (I saw some complaints about SIM/network incompatibility in Europe). I can't install this update as well. It is possible to force the installation via fastboot, but I believe that Xiaomi has a good reason why they prevent us installing this version. I'm waiting until it arrives on its own as an OTA update..
_mysiak_ said:
Each recovery ROM seems to be verified at Xiaomi servers during upgrade process and if they block the installation for whatever reason, you're out of luck. The reason might be that the ROM is supposed to be used only by selected testers, in a specific region or maybe the ROM was pulled due to major bugs (I saw some complaints about SIM/network incompatibility in Europe). I can't install this update as well. It is possible to force the installation via fastboot, but I believe that Xiaomi has a good reason why they prevent us installing this version. I'm waiting until it arrives on its own as an OTA update..
Click to expand...
Click to collapse
Oh..ok yes its safer to wait. Thanks
Just to confirm - I never received 13.0.2.0 EU ROM, nor I was able to install it via sideload/ROM updater. I couldn't install 13.0.4.0 manually either, but today I got the update over OTA and installation went through without any issues.
Having issues installing beta 3.3 on my 6 pro.. did a factory reset then tried installing it. First time it took forever to install and phone rebooted and had missing operating system so I had to factory reset.. second time I got a failed to install message.. rebooted the phone and it said no operating system please visit this link from another device.. rebooted then phone worked normal.. what is going on here ? Phone is purchased from att, so idk if it's considered global version but whatever either way . Is there something stopping it from being installed? Was trying to do all this OTA.. thanks kinda new to it
I'm not sure if it being an att version has anything to do with it or not.. maybe the version google releases is only working on unlocked global models?? Someone shine some light on this..
You can use https://flash.android.com/ to flash with a computer.
So why would the flash tool work but not the ota method ?? Really curious cause when the official comes out hopefully I can flash that ota without any issues.. right now I opted out of the beta cause I really want the ota method to work and it doesn't ..
Can someone tell me why the ota wouldn't install ? Installed it the way I installed any other update on the phone through check for updates.. Id rather get ota working vs hassling with a computer to install it. That can mess things up if done wrong .
Is it failing to ota install the beta cause of a locked bootloader ? It does fine with install ota security patches on Android 12. Trying to install 13 ota on the phone itself fails.. I don't see why that would be though ?
@Redbeardkevv Welcome to XDA. Instead of posting multiple times in a row, please use the Edit button to edit your post and just add to it, in the future.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
^ That Google site has saved many users on XDA. It has revived or corrected a mistake on their devices (mine too, once) when even flashing the full factory image didn't fix the problem. I have no idea what exactly it does that manually flashing doesn't. I normally use the full factory image zip, and that alone sometimes fixes issues that users have when they have issues flashing via the OTA method.
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Redbeardkevv said:
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Important excerpt:
Android Flash Tool guides you step-by-step through the process of flashing your device—there's no need to have tools installed—but you will need to unlock your device and enable USB Debugging in Developer options.
Click to expand...
Click to collapse
If I remember correctly from other AT&T variant Pixel 6 Pro users in this section, once you pay off the phone and/or own the phone for long enough, AT&T should carrier unlock the phone, and that will likely make it so that you can OEM Unlocking and unlock the bootloader. (this also applies to T-Mobile, but does not apply to Verizon)
Well it's a far ways from being paid off I'll just add that .. what are my flashing options ? Also why would a security patch install just fine, then I enroll into beta ,try to install it, and bam it won't install and is corrupt install. Just doesn't seem right to me.. should I just wait until official release early August and then the OTA install from phone will work ?
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Redbeardkevv said:
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Click to expand...
Click to collapse
Firstly, unlocked bootloader is required to flash custom or beta firmware. While you can sideload OTA packages on a locked bootloader, I would highly recommend against doing so as you may end up with no way to recover your device.
When installing a beta, it is generally best to wipe and perform a clean flash. OTA is not recommended because beta software by nature is not yet suitable for public release, and may not appropriately handle everything correctly coming from older firmware.
As has been mentioned before, I recommend you use the Android Flash Tool to flash the beta. To ensure you have a fresh start, tick the Wipe device and Force flash all partitions boxes. Do not re-lock the bootloader.
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Redbeardkevv said:
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Click to expand...
Click to collapse
Most likely. I doubt the beta will pass signature verification until it is updated to public release.
So not passing signature verification would be the reason it won't install ( ota ) most likely ? I'm just confused why a patch will install ota but the beta cannot .. must have something to do with bootloader being locked and it not being an official verified release or something
Just curious
Redbeardkevv said:
Just curious
Click to expand...
Click to collapse
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
NippleSauce said:
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
Click to expand...
Click to collapse
Well that explains it not installing and saying corrupted install ... Lol
Redbeardkevv said:
Well that explains it not installing and saying corrupted install ... Lol
Click to expand...
Click to collapse
It's a beta, so there will be issues for sure (but your last comment said you are getting an error [device is corrupt] that was common a few months ago so read on). You don't need to have an unlocked bootloader to enroll in the beta. Tons of users on Verizon and AT&T with a locked BL have installed the beta. Most are fine, some have had issues.
I wouldn't install a Beta on a locked BL. Why risk it? If something goes wrong, you'll need to get a warranty replacement. Seems like such a hassle.
For your issue, since you said you're getting a device corrupt message. This message is caused by q few different things (there's a thread on here about it). To fix it, users needed to do a factory reset in recovery mode. If you really wanted to try installing the beta (and you understand the risks), you'd probably need to: go to recovery mode and perform a wipe/factory reset.
From there, you could install the latest stable ota (via recovery mode) then see if the beta will update for you (via beta enrollment like you are trying to do), or directly flash the beta ota (link below). I'm just not sure if you can flash a beta ota image, over a stable build. I haven't tried it but according to xda, you can be on Android 12, and flash the Beta 13 ota (instructions found here).
There's two ways to flash an Android image: ota builds via recovery mode (doesn't require BL unlock) and factory image via fastboot which can be done manually or using Google's web flash tool (flash.android.com) - both if these require BL unlock.
You can find all the latest image downloads here. Google strongly recommends to flash the beta with an unlocked bootloader using their flash web tool. It's a beta so I would stay away until you can unlock your bootloader. Don't risk it. But I still think it might be a good idea for you to eventually perform a factory reset from recovery mode, since you are seeing the device is corrupt error message.
Had same problem, tried installing it twice and gave up