I'm running a completely stock OP3T with stock recovery and locked bootloader and latest OOS 9.0.6 installed.
Lately the phone has been unbearable to me and keeps hanging a lot with random crashes so im thinking about downgrading to OOS 4.1.7 as it is more stable. (I prefer OOS over custom roms to maintain stability and keep all the phone features intact).
I've downloaded OOS 4.1.7 from [oneplusupdates dot com] (cant post links cause im still new)
My question is : can I use the built in software update to locally select this file and preform the downgrade directly from pie to nougat?
I read somewhere that this could brick the device so i wanted to make sure.
philipemad said:
I'm running a completely stock OP3T with stock recovery and locked bootloader and latest OOS 9.0.6 installed.
Lately the phone has been unbearable to me and keeps hanging a lot with random crashes so im thinking about downgrading to OOS 4.1.7 as it is more stable. (I prefer OOS over custom roms to maintain stability and keep all the phone features intact).
I've downloaded OOS 4.1.7 from [oneplusupdates dot com] (cant post links cause im still new)
My question is : can I use the built in software update to locally select this file and preform the downgrade directly from pie to nougat?
I read somewhere that this could brick the device so i wanted to make sure.
Click to expand...
Click to collapse
Yes, that would surely brick the device. There are other steps involved before and while downgrading. Search on XDA for the steps.
The simplest solution to your problem is to download the current (9.06) OOS ROM and clean install/sideloading it. Your problem is most likely because of OTAs and not because of 9.06
The phone has replaced your bootloader to the point old roms are no longer compatible. Finding the correct zips and flashing order to downgrade the bootloader is a route i would not advise either. The easiest way to downgrade is find the msmdownloadtool unbrick thread of your specific model and download the version you desire or lower. Use this tool to flash the included files in upgrade mode and you will be on a stock, locked bootloader with the version you chose to download. Flashing always carries a risk, but i had no issues downgrading this way while i did run into issues flashing old zips. I switch between 5.0.8 based roms and the latest roms and its never let me down.
Related
Hi,
After doing some reading on here I am a little unsure on the best way to back up my HTC One M9 (GSM) stock recovery/system. My software number is 3.50.710.1 (Android 6.0) and it came from Optus (Australia). I cannot seem to find an RUU file for this firmware anywhere online; only earlier versions are available. My understanding of this is that I need an RUU file for my specific firmware as a fail-safe in case I mess something up and need to return to stock?
My questions are:
1) Can I get my phone back to the current complete stock firmware and be able to receive future OTA updates without turning s-off and without copying anything from my phone before I flash TWRP and a custom ROM?
2) If not is there anyway that I can back up my phone it its current stock state that will allow me to go back to this state if I want to go back to my stock Optus firmware or to install OTA updates? (Including the stock radio/recovery)
3) Reading this post as well as others leads me to believe that I may stop my mobile radio working by flashing a custom ROM (especially as the linked post has the exact same firmware as me). How can I avoid this, or fix it if it happens to everyone?
I am ideally looking for a custom ROM which improves over the stock firmware. My priority is maximum battery life, with customisation and HTC 10 system UI/apps a secondary focus. Any recommendations would be great, as well as tweaks and kernels which help give the maximum battery life.
Cheers!
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Flippy498 said:
You can't backup your firmware (and that includes your radio). However if you read my google sheet you'll find instructions for backing up your current boot.img, your system and the stock recovery. If you do it correctly those files will suffice for recovering the ability of installing OTAs. No personal data will be backed up so maybe you want to share your backup with us afterwards.
Click to expand...
Click to collapse
Thank you so much! I have managed to find the guide you mentioned to backup the stock boot image, system image and recovery. By the looks of it the tab to the right is the guide to return my phone to its original state, which is good. I'm more than happy to share the backup once I do it.
Flippy498 said:
There is a custom kernel for CM/AOSP roms which is said to repair the signal problems. As far as I read some sense rom users reported that flashing the stock boot.img recovered their signal. However this doesn't seem to work for every user. So you'll need to try by yourself.
Click to expand...
Click to collapse
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Thanks again!
Da Doom Lord said:
Okay, well I am planning on keeping s-on at this stage, so I'm left with Sense based ROMs I believe? I have read that LeeDroid is the best for battery life, does this sound right? If so I am unsure if I can flash it as it says "Please make sure you have the latest HTC Hima 3.35.XXX.XX Marshmallow firmware installed prior to installing this ROM" because my software number is 3.50.710.1?
Click to expand...
Click to collapse
I've read that several times in the near past and I actually don't understand it. You never needed S-OFF for flashing none-sense based roms as long as I started using Android/HTC phones and that was back in 2012. Why do so many people think they need S-OFF for AOSP?
I personally prefer the Viper rom. But taste differs and in the end the best advice I can give is try it out by yourself. Everyone has different needs and is using his/her phone in a different way. The best rom for person a might be an awful choice for person b since he/she has completely different needs.
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9). However many things have changed since the M9. There is no hboot anymore, the Download Mode got introduced, google changed the way OTAs are checking whether your system is modified, and so on. (Just to mention a few changes.) Those issues with the lost signal didn't even exist on pre-3.x firmware versions of the M9. Therefore users like you who use a not so common firmware (in comparison to the user numbers of the most common firmware bases: international, taiwanese and the developer firmware) have no other choice but trying out by themselves or getting S-OFF and changing to a more common firmware.
Flippy498 said:
I can't tell you whether you can use Leedroid. Test it and report back. That's how xda works. You might be able to use it after you flashed your stock boot.img but I don't know whether you really are or not. The warning is written so that people don't start flashing that rom with a lower firmware version. On older HTC phones flashing an "older" rom has never been an issue on newer firmware versions whereas flashing a newer rom on an older firmware never goes well (even on the M9).
Click to expand...
Click to collapse
I have followed your guide and now have the latest stable LeeDroid ROM installed and TWRP. Just as I predicted the radio was not originally working. When I restored my stock boot.img from the original backup I performed it began to work. Thanks so much for your help! I'll upload the backup to cloud storage when I get access to a decent internet connection and then I'll share it to help others out.
Hey everyone,
Apologize if this is something that has been asked before, haven't been able to find much information on it using search. Also still a relative newbie to android, so hope you folks will bear with me. I'm seeing the OS version in download mode showing as OS-3.36.709.3, while the software number in software information shows 4.30.617.12. Is this considered normal, or did I mess something up?
I previously had Marshmallow on my phone, and used TWRP to install the developer edition of Nougat. Was trying to do OTA, which unsurprisingly didn't work with TWRP installed. My plan is to reflash the recovery.img, but I'm unsure whether I should be using the recovery.img for 4.30.617.12, or the one for 3.36.709.3? Is there something I should do to get the versions aligned properly? Trying to make sure I avoid bricking the phone
The easiest solution would be downloading the latest version of the rom that you installed in the past and flashing it via TWRP.
Some advices: Please read the ReadMe thread. It explains why the version numbers differ (e.g. in the RUU section). In addition it will explain to you, that installing OTAs with TWRP actually is possible (c.f. the OTA section) but not in your case. Even with the correct stock recovery for your phone (the 709 one) you wouldn't be able to achieve your goal. You're trying to install an update for a completely different firmware than the current one of your phone. That's not possible. OTAs are incremental. That means you need to be using the firmware that the OTA is supposed to update (4.30.617.12) and not 3.36.709.3. You would need to convert your phone if you want to install that update.
You might want to read the article that I called "the difference between rom and firmware" in the further reading section of the ReadMe thread, as well, after you finished reading the ReadMe thread itself.
Be aware that it's always best to use a system that has the same version (or at least the same mayor version - e.g. 3.x for marshmallow or 4.x for nougat) as your phone. This way you can be sure that system and firmware are optimized for each other. Mismatches can cause unforseen side effects like battery drainage, lags or bugs.
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
P.S. will make sure to put questions in the right forum in the future.
e1rond said:
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
Click to expand...
Click to collapse
Correct.
e1rond said:
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
Click to expand...
Click to collapse
Then the phone had been modified before you got it. Since android 5 google is using block-based OTAs. That means re-flashing the stock recovery isn't sufficent if you want to update your phone and modified it, beforehand. You need to restore a completely untouched system image.
Check the ReadMe thread. The RUU section as well as the TWRP section II should contain the files and instructions that you need for restoring the OTA function of your phone. It's up to you which of the methods you prefer to use.
Appreciate the information and the advice. Decided to RUU back to a 3.x version, and use OTA to upgrade to Nougat. Took a lot of updates to get it to the latest version, but everything is working well now
Zenfone 2 Deluxe Special Edition
Model: Z00A
Before I unlocked, rooted, and flashed my current version, I had Android M - I believe it was Asus firmware version: WW-4.21.40.352
Current version: Groovy Android Android N (7.1.2) - GA-N-v7.1.2-20180612-Z00A-Release.zip
Apparently that was a big mistake and I should have downgraded to Android L before flashing Groovy Android Android N because there's a known issue related to the SIMs not being detected.
I can get my LTE connection to work if I physically remove and reinsert the SIM but that's obviously annoying. And I figured out how to play with the data/SIM settings to get it to register on the data network again but it keeps reverting back to having issues with the X over the LTE symbol and having no data connection.
I just picked Groovy Android because I didn't really know where to start and I wanted Android Nougat. I really want a dark themed Android Nougat but I haven't come across any custom ROMs that have that option. Any suggestions?
For now, I need to go back to Android L so I can flash Groovy Android again without SIM issues.
I downloaded UL-Z00A-WW-2.20.40.206-user.zip from Asus's website.
Can I simply go into TWRP, go into sideload mode, and then type adb sideload UL-Z00A-WW-2.20.40.206-user.zip from my PC?
Do I need to wipe any particular partitions before or after?
EDIT:
Oh also one of the reasons I wanted to try a custom ROM is because of all the bluetooth audio issues I was having. Every single ROM I've ever had on this phone, from the one it shipped with, through several OTA and updated firmwares from Asus's website that claim to "fix bluetooth stability", I've always had this issue where the audio just randomly cuts out while connected to my Soundbot SB360 receiver (I've had other devices and phones connected to it without issue). I've seen other people complain about it on Asus's forums with no real resolution.
That does not happen on my device. It's stable except for the crashed pie
I know I need to downgrade to stock Lollipop. So the question is, can I do that from TWRP, and how do I do it?
Did you back up your system partition before flashing Groovy Android?
If not: https://forum.xda-developers.com/zenfone2/help/guide-flash-stock-rom-asus-zenfone-2-t3588276
nastys said:
Did you back up your system partition before flashing Groovy Android?[/url]
Click to expand...
Click to collapse
Yeah, but how does that help me get to Lollipop?
I was on Marshmallow prior to Groovy Android.
download asus flash tool
download raw rom
flash it on stock recovery
flash rom lolipop stock zip
accomplished
Everything you can download and find on the forum
orificium said:
Yeah, but how does that help me get to Lollipop?
I was on Marshmallow prior to Groovy Android.
Click to expand...
Click to collapse
Either flash the firmware directlyhttps://forum.xda-developers.com/zenfone2/help/guide-flash-stock-rom-asus-zenfone-2-t3588276, or restore that backup, flash stock MM recovery, lock the bootloader and downgrade by installing the 2.x "update" zip from ASUS's website.
nastys said:
Either flash the firmware directlyhttps://forum.xda-developers.com/zenfone2/help/guide-flash-stock-rom-asus-zenfone-2-t3588276, or restore that backup, flash stock MM recovery, lock the bootloader and downgrade by installing the 2.x "update" zip from ASUS's website.
Click to expand...
Click to collapse
I was reading over this guide yesterday and I'm going to try METHOD 2 using the Asus Flash Tool to flash WW_ZE551ML_2.20.40.206_20170627.raw which is the latest version of Lollipop.
Got myself a Redmi Note 5 Global version and want to update MIUI and possibly try a custom ROM. Just came here to make sure i'm not falling for any common mistakes before i do anything especially after reading a lot of folks that have bricked these devices due to Anti Roll-back so thats the last thing i want to do. The device came boxed with MIUI 9.5.6.0(OEIMIFA) and i've just ignored the update notification up to now so i presume i've avoided ARB and i would like to keep it that way.
So just to confirm are these the correct steps.
1. Unlock the bootloader
2. Flash a custom recovery (TWRP or the equivalent)
3. Update MIUI / Flash custom rom package without ARB and flash through TWRP
Is there anything i'm missing or anything i need to specifically avoid other than ARB?
drkdeath5000 said:
Got myself a Redmi Note 5 Global version and want to update MIUI and possibly try a custom ROM. Just came here to make sure i'm not falling for any common mistakes before i do anything especially after reading a lot of folks that have bricked these devices due to Anti Roll-back so thats the last thing i want to do. The device came boxed with MIUI 9.5.6.0(OEIMIFA) and i've just ignored the update notification up to now so i presume i've avoided ARB and i would like to keep it that way.
So just to confirm are these the correct steps.
1. Unlock the bootloader
2. Flash a custom recovery (TWRP or the equivalent)
3. Update MIUI / Flash custom rom package without ARB and flash through TWRP
Is there anything i'm missing or anything i need to specifically avoid other than ARB?
Click to expand...
Click to collapse
Just don't update your firmware (or update it with a ARB-less firmware), that's what will trigger ARB. Most of the customs rom don't contain firmware, only LOS advises you to flash a specific version, but MIUI roms do.
So you either steer away from those and flash fw-less roms, or you just delete the firmware-files folder from the rom and flash it without them.
This is my advice, before flashing anything, open the zip and check for the firmware folder. If it has it, delete it (unless is specified by the dev to flash that along the rom, in that case, just avoid it, there's a plethora of custom roms to choose from).
Ok thanks so i'll just stay clear of any roms containing the firmware folder for now. I do like LOS but if theres any risk associated i'll just give it a miss for now.
I also assume its easy to recover from a bad flash following the no firmware folder rule since theres no real risk associated with flashing just a ROM(no firmware)?
Finally, what about kernels and bootloader updates is there anything specific i need to watch out for there? I only ask because my previous device included a sneaky OTA update which locked the bootloader and i'd obviously like to avoid anything like that here.
Sorry for all the questions i'm just a bit behind on the flashing front, my previous device was a Motorola Razr HD and flashing seems to have changed quite a bit since then.
drkdeath5000 said:
Ok thanks so i'll just stay clear of any roms containing the firmware folder for now. I do like LOS but if theres any risk associated i'll just give it a miss for now.
I also assume its easy to recover from a bad flash following the no firmware folder rule since theres no real risk associated with flashing just a ROM(no firmware)?
Finally, what about kernels and bootloader updates is there anything specific i need to watch out for there? I only ask because my previous device included a sneaky OTA update which locked the bootloader and i'd obviously like to avoid anything like that here.
Sorry for all the questions i'm just a bit behind on the flashing front, my previous device was a Motorola Razr HD and flashing seems to have changed quite a bit since then.
Click to expand...
Click to collapse
No problems, happy to help if I can.
And yes, no risk if you don't flash firmware. Worst case scenario, you'll have to reflash a miui rom with MiFlash, which means losing your data, but imo it's better than bricking the device.
As for kernels and bootloader, you're good to go. Nothing will relock your bootloader (except flashing with MiFlash and selecting that specific option) and a kernel in the worst case will just give you a bootloop. Use backups. ?
And as far as LOS goes, you can flash it without the specified firmware (even tho I'm pretty sure it's an ARB3 firmware) but I guess there might be some small issues.
Good luck with unlocking the bootloader, that thing takes from 720 to 1440 hours, just got my rn5p in a week now i have to wait a month before rooting...
Hi everyone,
I would like to know if it is safe to unlock bootloader and flash a custom ROM under MIU 13.0.3 SKHEUXM ?
I've seen people having bugs, hence why I'm asking if anyone has given this a try ?
Furthermore, I was going to do this update in order for the firmware to be updated then switch to a custom ROM, but I could go for custom ROM first then flash the newest firmware (even if I'm more confident on the first option which should work out of the box, and preserve warranty in case something goes wrong during flashing firmware, always gotta keep fingers crossed).
Thanks for any help on this matter.
If you updated to the latest ROM, your firmware is updated along with it, there's no need to flash the firmware again seperately. Flash the ROM of your choosing, Magisk if you absolutely need it, and enjoy. Most ROMs these days also pass SafetyNet if you do not root your phone.
AkechiShiro said:
Hi everyone,
I would like to know if it is safe to unlock bootloader and flash a custom ROM under MIU 13.0.3 SKHEUXM ?
I've seen people having bugs, hence why I'm asking if anyone has given this a try ?
Furthermore, I was going to do this update in order for the firmware to be updated then switch to a custom ROM, but I could go for custom ROM first then flash the newest firmware (even if I'm more confident on the first option which should work out of the box, and preserve warranty in case something goes wrong during flashing firmware, always gotta keep fingers crossed).
Thanks for any help on this matter.
Click to expand...
Click to collapse
It's not very safe, you need to be careful.
Make sure your PC wouldn't crash or that your USB connection may be unstable.
Take your time in setting everything up and reading up some resources on the internet.
If the Flash-process aborts for whatever reason, do not reboot phone. Your phone may not be able to reboot back into Fastboot and turn black.
As for good resources of information, I recommend the YouTube Channel "Munchy". He covers Xiaomi Flashing very well. You can trust him.
https://www.youtube.com/channel/UCDSfvwvAsKE4Nrosu7bTbJw
You might also want to use a Custom ROM with passing SafetyNet, or to use Magisk Root. If SafetyNet fails, you can't use some apps.
I personally use Xiaomi.eu Weekly Android 12 with Magisk Root + SafetyNet Fix Module. No bugs, I'm happy
My only wish was that I had Over-The-Air updates. With most Custom ROMs, you unfortunately still have to download & flash the ZIP-file manually in TWRP Recovery.