Hi Guys,
I am back with another thread for people who want to downgrade their Android ROM for different reasons from any higher android version, like some of you getting problem with new O.S, some of you might not like the new O.S and as in my case my new o.s marshmallow got crashed/currupted.
As in my case when my new updated O.S 6.0 Marshmallow got crashed, then no way was left to me but to reinstall 6.0 M on my phone, but as stock ROM of marshmalow for HTC Desire 816 dual sim A5_dwg indian version was not available on any portal online, so i need to rollback to any lower version android like kitkat or lollipop.
As you guys must know that if your phone is running on higher android O.S then it doesn't matter whether its corrupted or showing errors, you can't rollback/downgrade to any lower version android.
For finding way to get out of this problem, i am sharing some steps which i followed to rollback my phone to lower android version.
Step 1: First of all please make ready your computer by installing ADB drivers, fastboot utility and drivers for your phone.
Step 2: As i have already made clear that you can't roll back to lower android version from higher one so for doing that you need to unlock your phone's bootloader , ROOT your phone by following this thread
http://forum.xda-developers.com/showthread.php?t=2775801 and install any custom recovery available like CWM or TWRP, i personally prefer TWRP.
IMPORTANT Note: For users who have rooted and un-rooted their phones in past, updated stock ROM to any new stock version and already having Unlock_code.bin file on their e-mail, don't try to use that file now again for unlocking your phones bootloader as it will not work, you need regenerate that unlock_code.bin file from HTC website because with updated stock ROM, code for unlocking bootloader also changes.
Step 3: Once you are done with Rooting and installing custom recovery and Super user app. now it's time to install any custom ROM like cynogenmod or any other custom rom available for you phone. For downloading and installing CM 13 follow links given https://download.cyanogenmod.org/?device=a5dwg
https://wiki.cyanogenmod.org/w/Install_CM_for_a5dwg
Step 4: Once you are done with installing custom ROM CM 13 on your phone now you can start procedure to Un-Root your phone, install stock recovery and flash any lower android version stock ROM on your phone.
for unrooting and rolling back to stock rom you can follow my thread
http://forum.xda-developers.com/desire-816/help/how-to-unroot-roll-to-stock-htc-desire-t3487894
and
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
Wollah....... you are now ready with lower android version ROM on your phone and now you can update your phone O.S with OTA updates released by your phones manufacturer.
Related
So...it's been about 6 months now since first tried to gather the in for I needed in order to get my device back to date.
.When I first got te device...it did an ODA, and I ODINed a root in and installed TWRP.
So I'm essentially on build --info posted below via screenshot-- and am trying to install the New Iron ROM. I've received messages from people whobsaid that I need to flash the boot loader before I can go from stock 5.0.2 to the latest IronROM/Ironkernel.....and I've seen messages that I then purpose of flashing a boot loader for people trying to get on a particular ROM, is so that "they ***can get*** the 5.0.2 boot loader-- if you're on 5.02....you can install 5.0.2 Roms freely...as long as you have the 5.02 boot loader (which you must have because you're running 5.0.2.) The reason this boot loader mess is such a big deal is because some people want to install custom LOLLIPOP ROMs, when they have only Evey installed Kit Kat ROMs. So the first time you flash a lollipop FROM you have to flash the botloader....but once you do that you can flash everything from lollipop and up (because the new lollipopband marshmallow builds use the stock code from lollipop at the moment).
I'm a competitive hearthstone player ad access to a computer and Odin is far away right now.....so if I could do this all through tarp.....or just unfreeze the update app, let it update, and reroot, if possible.....and then I could just flash what I wanted...but I'm notbsure whose right. Most of Tue devices I've handled all my rom flashing through TWRP, with no care I the world for what baseband I had. It was never an issue.
I've posted a screenshot of the build I'm on below (am using a custom kernel for sound boost)....
Would like to install this --
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
So....I'm on a 5.02 FROM. A stock one. Is it a different build than the one that FROM is based on? It looks like it. But should have the right boot loader! Right? In this case... I can just wipe/flash with tarp! No odin /boot loader futzing about needed. And I can use the other some too right? The CM or Pad Man ones? Because they're using the 5.02 code from Samsung for our device to get those build working?
/facepalm.. .
Or.....if every time a new from based on a new 5.0.2 build comes out, I have to odin a new boot loader so that I can now install roms made from a different base...even though what really mattersnis that I have a 5.02 boot loader already....
I though that the version number was what mattered. IF 6.0 came out tomorrow and everyone started making roms based upon the stock 6.0 code, id have to get the same version number boot loader as they had in the source material.
Conflicting messages >.<
I'm on a Completely stock, rooted 5.02 ROM. U1BOCC
The from I want to install appears to be 5.02 based on BOJJ.
What do I do now?
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.
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.
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.