I didn't know where to post, so, here I am.
I am surprised to see that there are no ROMs for this device. Is making a ROM for this device truly impossible or what?
I read that the stock Lollipop update has many issues like lags, freezes, etc., so I didn't upgrade.
My current Kitkat firmware: WW_V11.2.3.21.5
I'll try to help, although I am a complete noob, in the making of a ROM if someone takes it up!
Hope someone can make one.
And can I directly upgrade to the Lollipop Firmware without the intermediate Kitkat updates,i.e.,
directly from WW_V11.2.3.21.5 to WW_12.8.1.38 without any problems?
Answer to your first question is impossible. If you want reasons: locked bootloader, no device and vendor trees and so on.
To your question, it's possible. To do that just download the correct firmware file from the following list:
TR
WW
TW
CN
BEWARE it's 600MB. Then copy it to the root of your sd or extsd card. You'll get a notification about an update file being detected.
Related
I've searched the forum and havent found a specific answer to my question. I am currently running 5.0 with the viper rom and its pretty damn sweet. my problem is a lot of my apps and some of the xposed modules wont work on lollipop but are compatible with KitKat. so obviously i want to go back.
is there any way to go back to kitkat without having to plug my M8 into a computer?? i would basically like to do it remotely and on demand, you know flash OS back and forth like you can do with a rom. can somebody help me out with the process if it is at all possible.
You should be able to run a KK version of Viper (or other ROM) with Lollipop firmware, as least from what I've read from reports by others. While old firmware causes problems with current ROMs; the opposite has been found to be a a different matter: firmware has been found to usually be backwards compatible.
You can always make a TWRP backup of your current setup. Then try a KK ROM, and if you have issues, just restore back to LP.
If you do run into issues, then you probably do need to downgrade your firmware to KK (need s-off to downgrade firmware; and not sure if there is a computer-free way to flash back to KK firmware).
I'm seriously stressed from thrawling through forums making posts and as of yet I've got no answers, hopefully someone here can help me or discuss my problems.
Yesterday I tried rooting the ZF2 Z00A , Originally a CN 2.20.40.63. It went into bootloop.
At this point ADB does not recognize the phone but fastboot does.
I tried installing a non rooted rom via SD Card but I got a signature verification error.
Now it looks like my only option is to flash a pre-rooted rom via Fastboot as that still recognizes the device. However I cannot find a CN 2.20.40.63 or newer pre rooted rom, I can only find CN 2.20.40.61 ....... am I right in believing that this would not work due to .61 being older than .63? Would it matter if I flashed a WW rom that was .63 or later? Even if it meant the phone was buggy but then allowed me to unroot and install a stock rom I wouldn't mind, I just would like my phone to work again (I only rooted because there was random webpages and apps opening and downloading the whole time).
Please somebody help. Also my brother who is in another country has a rooted CN 2.20.40.63 phone, is there anything he can do?
Due to a series of unfortunate events(user error), I just purchased my third ZenFone 2. Each time I have purchased the same model Z3560, simply with different color and capacity just due to the pricing at each time. I just received the third one and I have found some oddities with it that I just want to share or ask about. I noticed on the gsmarena page that it says that the Z3560 is supposed to have 2GB of RAM but mine has 4GB. Also as I would usually do with a new phone, I went to update it but there is no update button where it was on the previous two ZenFone 2s I have owned, I simply cannot work out where to update this phone. Any ideas as to how to do that? I'm on build number ASUS_Z00A-2.18.40.12_20150529. Finally, when looking in CPU-Z to see the hardware it was reporting I noticed it said I already had root access which is odd? This has literally just been opened in the last 30 minutes and does not seem to be tampered with or a preowned model as the box was still in the shrink wrap plastic packaging that the box comes in. This isn't an issue, I just find it odd as I had to root my previous devices, zenfones included.
Z3560 with 4GB of ram comes from China wit China software,sellers in other countries changing it to EU ROM which is pre rooted,it was with mine but before I bought it seller has info in advertisements about it,I do not have any errors yet and I hope I won't get but I have problem with overheating it is warm on the top of the phone...
Did you stay on the rom that yours came with? Do you know if I am still able to flash other WW firmware onto this? I would like to be on the latest update for my device and this doesn't give me the option so I'm missing out on some of the newer features that I'm used to like disabling the bloat on the device
SnakeBiteScares said:
Did you stay on the rom that yours came with? Do you know if I am still able to flash other WW firmware onto this? I would like to be on the latest update for my device and this doesn't give me the option so I'm missing out on some of the newer features that I'm used to like disabling the bloat on the device
Click to expand...
Click to collapse
I have a 32gb 4gb 3560 zenfone 2, 2 actually. I followed the change to ww from cn guide to make sure everything was ok and have no issue with getting OTA's...
Everything works fine and one is on the latest stock 165 rom, the other is on a custom rom. Both had bootloader unlocked and both are rooted.
If you wish to find the latest pre-rooted rom, go to the pre-rooted rom thread made by Shakalaka, thanks again, and download from there, the latest is on Mega however.... Flash using fastboot...
He also provides recovery, boot and droidboot images,again, flash using fastboot BUT make sure you don't just copy and paste the same thing repeatedly, flashing the system image on the recovery partition after flashing the boot and droidboot image there already can really bork your phone...
Would suggest unlocking bootloader, seems to be easier flashing new roms and no issue with OTA's either. Bit more flexible if things go screwy...
ultramag69 said:
I have a 32gb 4gb 3560 zenfone 2, 2 actually. I followed the change to ww from cn guide to make sure everything was ok and have no issue with getting OTA's...
Everything works fine and one is on the latest stock 165 rom, the other is on a custom rom. Both had bootloader unlocked and both are rooted.
If you wish to find the latest pre-rooted rom, go to the pre-rooted rom thread made by Shakalaka, thanks again, and download from there, the latest is on Mega however.... Flash using fastboot...
He also provides recovery, boot and droidboot images,again, flash using fastboot BUT make sure you don't just copy and paste the same thing repeatedly, flashing the system image on the recovery partition after flashing the boot and droidboot image there already can really bork your phone...
Would suggest unlocking bootloader, seems to be easier flashing new roms and no issue with OTA's either. Bit more flexible if things go screwy...
Click to expand...
Click to collapse
Thanks, I'll unlock the bootloader and flash the latest preroot WW rom
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
Hi all - I received a brand new VS986 today with 5.1 installed (VS98611A specifically). I followed the UsU procedure to unlock the bootloader and installed Magisk.
Basically I'd like to either remove some of the bloatware on 5.1 / Lollipop or upgrade to 6 / Marshmallow. If I choose to upgrade, is there a recommended ROM to flash that won't undo the UsU I already performed? Can I use my existing SALT flash drive to manually disable / remove unwanted apps in download mode?
I had a custom ROM on my previous phone (Galaxy S5) but I think I'll stick with a vanilla ROM this time, at least for now, unless there's a highly recommended M/N/O custom ROM that doesn't have any glaring issues, and will be an easy upgrade path from my current Lollipop installation.
Thanks for any advice here.
After further research, it appears I did a no-no and applied UsU to a Lollipop bootloader. Now that that's done, is flashing a stock Nougat ROM (e.g. as described here) safe to do? Or should I go through the procedure listed in #20 of the FAQ from steadfasterX and try to flash elements from a MM .ndz file first? If so, I downloaded a VS98626A kdz file - should that work to pull the necessary MM boot files from?
Sorry for the newbie-ish questions, I'm just trying to avoid bricking my new phone.